juiczek | 13 Dec 08:41 2013
Picon

Full documentation for init process.

Hi,
Because I was digging sources and Internet for long time with this topic and didn't find some full documentation for this I dare to ask someone here.
I'm having some troubles with porting Android to some new device so that's why I choose this group.

During the study of init.rc doc (https://android.googlesource.com/platform/system/core/+/master/init/readme.txt) I had feeling that no one care about proper documentation.
Let see some example:
In readme.txt is written:
"Actions and Services implicitly declare a new section. All commands
or options belong to the section most recently declared. Commands or options before the first section are ignored."
Then I look into example file (from: https://android.googlesource.com/platform/system/core/+/master/rootdir/init.rc) and see, that firs command is the "include" but it is command (placed in section commands in readme.txt) so it should be ignored. Why is not ignored? Why is not proper described? What happen if I include file which is on partition which isn't mounted at beginning?
Then I started looking closer and deeper and here is another example of lack of lack of consistency: Triggers.readme.txt:"Actions take the form of:on <trigger> <command> ...
Triggers ...boot ...<name>=<value> ...device-added-<path> device-removed-<path> ...service-exited-<name> ..."
So what is that in example init.rc like:on early-initon initon fson post-fs
There is no documentation for this (even "do not touch this sections"), no definition in keywords.h or init_parser.c after digging more finally I have it! In file init.c function main there is section of parsing those "Triggers" but when this is triggered? Which goes first? How init recognizing that now is "init" part of process, or "fs".
Then looking closer I see some another crucial label for init process called: "charger". Where it is came from? Why some boot has "charger" option. When?Why this is not documented if this is important part of init process?

So is there any real, I mean REAL documentation for whole Android init process?
Because this what is provided by AOSP is really poorly written. To not say "slovenly".

I will be really thankful for giving me some ideas and "breadcrumbs" for understanding whole booting process in init part as well as what I should care most with porting Android to new device.

Thanks
Kamil

--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
website: http://groups.google.com/group/android-porting
 
---
You received this message because you are subscribed to the Google Groups "android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Sasidhar | 13 Dec 14:00 2013
Picon

errors when porting android on IMX6 reg.

Hi,

           I am trying to port android on imx6 i followed the steps mentioned in Android_User_Guide.pdf provided by freescale. And below mentioned are the steps i followed to build the image.

# Build Android images for i.MX6 SABRE-SD boards
$ cd ~/myandroid
$ source build/envsetup.sh
$ lunch sabresd_6dq-user
$ make

During the make i faced with few error

  Image arch/arm/boot/uImage is ready
make[1]: Leaving directory `/home/sasidhar/competency_imx/android/myandroid/kernel_imx'
install -D kernel_imx/arch/arm/boot/uImage  out/target/product/sabresd_6dq/uImage
install -D kernel_imx/arch/arm/boot/zImage  out/target/product/sabresd_6dq/kernel
host C++: libclangStaticAnalyzerCheckers <= external/clang/lib/StaticAnalyzer/Checkers/VirtualCallChecker.cpp
make: *** [out/host/linux-x86/obj/STATIC_LIBRARIES/libclangStaticAnalyzerCheckers_intermediates/VirtualCallChecker.o] Error 1

Kidly, help me to fix this error.

Thanks & Regards,
Sasidhar

--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
website: http://groups.google.com/group/android-porting
 
---
You received this message because you are subscribed to the Google Groups "android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Bruno De Paoli | 13 Dec 11:46 2013
Picon

Android PPP data session not starting.

Hi,

I've ported a third-party RIL driver to our platform which is running Gingerbread. The GSM functionality appears to be basically working in that the device registers with the network but, as far as I can see, the data connection is not being setup. My understanding is that PPP does not start automatically but only on certain events (such as an attempt to start browsing). However when I start the browser it does not connect and I do not see any obvious attempts to start the connection and no error events when I do logcat -b radio.

I've included here what I believe to be the relevant part from the init.rc script.  init.gprs-pppd is marked as disabled and I think this is correct because it is not started automatically but is started by another event.

# Prepare  RIL repository
service rril-repo /system/bin/rril-repo.sh
    user root
    group radio
    oneshot

# Load RIL
service ril-daemon /system/bin/rild -l /system/lib/librapid-ril-core.so -- -a /dev/ttyACM0 -n /dev/ttyACM1
   socket rild stream 660 root radio
   socket rild-debug stream 660 radio system
   user root
   group radio cache inet misc audio

service pppd_gprs /system/bin/init.gprs-pppd
   user root radio
   group radio cache inet misc
   disabled
   oneshot

service pppd_term /system/bin/stop_pppd 15
   disabled
   oneshot

service pppd_kill /system/bin/stop_pppd 9
   disabled
   oneshot


Can anyone explain how this is supposed to work and suggest where I might look for the problem. What starts the data session and what/where can I look to see why it is not starting. I've had a look around some of the forums but could not find any obvious answers. I'm relatively new to Android so your help would be appreciated.

Thanks,
Bruno

--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
website: http://groups.google.com/group/android-porting
 
---
You received this message because you are subscribed to the Google Groups "android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Suresh Pachiyappan | 12 Dec 15:15 2013
Picon

Android Porting -- Encryption Problem-- Jellybean Android-4.1.1_r6


Hi Team,

I have issues in Android Encryption while porting Jellybean4.1.1_r6.

First i have bring the UI side.Then started the Encryption from UI side. In adb logcat shows encryption in progress as well as getprop shows in progress with percentage.after reached 100%. device is rebooted. Its check for crypto completed and getprop state show encrypted.

After that device trying to decrypt the encryped /data partition and ask password .

I have typed correct password and its shows failed mount tmp mount point

Error temp mounting decrypted block device

Please look into Logs for more info

Adb Logcat
---------
...
 V/CryptKeeper( 1632): Encryption progress: 100
...
D/CryptKeeper(  299): Validating encryption state.
D/VoldCmdListener(  101): cryptfs cryptocomplete
...

D/CryptKeeper(  483): Attempting to send command to decrypt
D/VoldCmdListener(  101): cryptfs checkpw {}
E/Cryptfs (  101): return value /fstab.omap4blazeboard
E/Cryptfs (  101): return value /fstab.omap4blazeboard
D/Cryptfs (  101): crypt_ftr->fs_size = 120717312
E/Cryptfs (  101): /data/tmp_mnt
E/Cryptfs (  101):  crypto_blkdev/dev/block/dm-0
E/Cryptfs (  101): Data mount point /data
E/Cryptfs (  101): tmp mount point /data/tmp_mnt
E/Cryptfs (  101): Real Blkdev /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata
E/Cryptfs (  101): return value /fstab.omap4blazeboard
E/Cryptfs (  101): Error temp mounting decrypted block device
E/Cryptfs (  101): ERROR REPORT Invalid argument
E/Cryptfs (  101): return value /fstab.omap4blazeboard

..

fstab.device name
------------------
/dev/block/platform/omap/omap_hsmmc.1/by-name/system       /system             ext4      ro                                                    wait
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache      /cache              ext4      noatime,nosuid,nodev,barrier=1,data=ordered                     wait,check
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata      /data               ext4      noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc     wait,check,encryptable=/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata


init..rc
--------
  mount_all /fstab.omap4blazeboard
  setprop ro.crypto.fuse_sdcard true



Please let me know where i am going wrong.

Thank in advance
Suresh

--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
website: http://groups.google.com/group/android-porting
 
---
You received this message because you are subscribed to the Google Groups "android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
kshongmo | 12 Dec 12:14 2013
Picon

Question on USB driver. How many uevents will be sent when device plugged in

We are currently working on a portable device based on OMAP4460.
When plugged into PC, there will be multiple uevents sent, even ADB is turned off. Is it normal?
I'm not so familiar with USB driver. Could anybody help explain it for me?
Thanks in advance.

The log is as below:
  651.111175] PC detected
[  651.345611] android_work: sent uevent USB_STATE=CONNECTED
[  651.352996] android_work: sent uevent USB_STATE=DISCONNECTED
[  651.429107] android_work: sent uevent USB_STATE=CONNECTED
[  651.455627] android_usb gadget: high speed config #1: android
[  651.464385] android_work: sent uevent USB_STATE=CONFIGURED
[  655.198364] omap_hdq omap_hdq.0: TX wait elapsed
[  655.331176] omap_hdq omap_hdq.0: TX wait elapsed
[  655.463165] omap_hdq omap_hdq.0: TX wait elapsed
[  655.596038] omap_hdq omap_hdq.0: TX wait elapsed
[  655.729553] omap_hdq omap_hdq.0: TX wait elapsed
[  655.862335] omap_hdq omap_hdq.0: TX wait elapsed
[  655.995208] omap_hdq omap_hdq.0: TX wait elapsed
[  656.128143] omap_hdq omap_hdq.0: TX wait elapsed
[  656.215637] android_work: sent uevent USB_STATE=DISCONNECTED
[  656.275207] android_work: sent uevent USB_STATE=CONNECTED
[  656.283355] android_work: sent uevent USB_STATE=DISCONNECTED
[  656.356811] android_work: sent uevent USB_STATE=CONNECTED
[  656.825592] android_usb gadget: high speed config #1: android
[  656.832855] android_work: sent uevent USB_STATE=CONFIGURED

--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
website: http://groups.google.com/group/android-porting
 
---
You received this message because you are subscribed to the Google Groups "android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Subodh Nijsure | 11 Dec 17:20 2013

AOSP porting and maintaining local changes

Hi,

Not specifically code "porting" question but more question of managing
local changes to AOSP repo for specific hardware platforms.

We are porting AOSP to our custom hardware and we need to maintain our
changes in our local repository. Our baseline code comes from
code-aurora project for Qualcomm chips. Unfortunately our changes are
hardware specific and folks maintaining code-aurora will see no value
in allowing us to push those changes upstream.

Is there a good document that describes, recommends workflow for
cloning the AOSP  repo,  local commit  & push so changes can be shared
across a team of engineers?

Or if you follow some kind of process in your team environment for
maintaining local changes to AOSP tree please send it my way, would
much appreciate it.

-Subodh

-- 
--

-- 
unsubscribe: android-porting+unsubscribe@...
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups "android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscribe@...
For more options, visit https://groups.google.com/groups/opt_out.

Kamil Nawrot | 11 Dec 15:57 2013

Documentation for init.rc

Hi,
I want to ask somebody about proper documentation of init process and init.rc scripts.
Right now I'm trying to port 4.2.2 Android to some new device and I had faced some problem with init.rc.

Looking to /system/core/init/readme.txt I can be informed that there are few triggers for actions: boot, <name>=<value>, device-added-<path>, device-removed-<path>, service-exited-<name>.
Also I was informed that:
"Actions and Services implicitly declare a new section.  All commands or options belong to the section most recently declared.  Commands or options before the first section are ignored"
For reference: https://android.googlesource.com/platform/system/core/+/android-4.2.2_r1.2/init/readme.txt

Then I looked to example file:
https://android.googlesource.com/platform/system/core/+/android-4.2.2_r1.2/rootdir/init.rc

And I can see some triggers:
init
fs
post-fs
...

Which even doesn't exists in keywords.h or init_parser.c - how those actions are triggered (I know what means post-fs but I wan't to know what kind of action IS the "post-fs" and why?, how to extend those actions?).
More over - "include" section which is in readme.txt described as "commands" is _before_ first action so should be ignored according documentation... (!?!) So why it's at the beginning of example file?

Can somebody point me to real, I mean REAL documentation for init process in Andorid?
Because this what is provided by AOSP is really poorly written. To not say "slovenly".

Thanks
Kamil

--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
website: http://groups.google.com/group/android-porting
 
---
You received this message because you are subscribed to the Google Groups "android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Mayank Agarwal | 11 Dec 03:11 2013
Picon

Join android wilhelm project


Hi,

I would like to join android wilhelm project.Any pointers on that.
 
I would like to understand how OpenMax al processes audio/video data before sending it down to hw/soc

Regards,
Mayank

--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
website: http://groups.google.com/group/android-porting
 
---
You received this message because you are subscribed to the Google Groups "android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Chris Johnson | 7 Dec 00:35 2013
Picon

Dithering on Android 4.4

I was wondering how I could enable dithering on 4.4 for my 16bit display device (i9100). Without it, I am getting major color banding. Pre 4.4, it could be turned on using glEnable in (surfaceflinger/layer.cpp). How would I turn it on in 4.4?

--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
website: http://groups.google.com/group/android-porting
 
---
You received this message because you are subscribed to the Google Groups "android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Shivanand Naik | 6 Dec 15:58 2013
Picon

Removing blank screen between Boot Splash screen and boot animation

Hi,
I am working on NVidia tegra 3 platform  and working on Jelly Bean 4.1.2r1 release of AOSP. I am trying to customize boot splash screen along with boot animation. I want to provide an effect that the splash screen and boot animation are one part. Currently I observed on most of the android devices available in market, that the screen goes blank after splash screen and before starting boot animation. The splash screen is loaded by bootloader and the boot animation is in the form of ZIP file stored in /system partition. The surface flinger loads the animation from zip file.

I browsed the code in surface flinger to locate the place where the screen is cleared out after splash screen. I think if I can avoid clearing of the screen, then the boot animation will be started immediately after splash screen without a blank effect in between.

Any pointers on which part of surface flinger is doing this?

Cheers
Shivanand

--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
website: http://groups.google.com/group/android-porting
 
---
You received this message because you are subscribed to the Google Groups "android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Picon

porting android accelerometer - android src 4.1.1_r6

Hello,

I 'm currently trying to modify android accelerometer into android src 4.1.1. as mentioned in the subject.

Well, i know how sensors data is read. Specifically, on the Kernel data is read by the driver (obviously Linux driver) and 
then, HAL driver is responsible for sending the data to the API.

Can anyone guide me on how to start modifying sensors in this version of android 4.1.1_r6?

--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
website: http://groups.google.com/group/android-porting
 
---
You received this message because you are subscribed to the Google Groups "android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.

Gmane