Firstly, the kernel does boots up in case of power-of charge.
Its booted in a special mode (maybe with different .rc file) such that
only the charging related process is spawned up (but kernel and drivers are
loaded).
Secondly, the power-off wake up can be done by RTC clock. As a RTC clock is
HI Shavi,
I had a quick word with my office friend regarding this.
I guess you dont need to set the governor per-core. As the governor policy
is per CPU not per core entity.
And to set , no need to call in loop for each core. Just set it for cpu0
(main core) , and then corss-check by readin
HI Guru,
Also, if you can use RTC hardware to do so , infact the android alarm
manager internally uses the RTC hw to wakeup from suspend.
(As that is one of the area of board that is still powered , when we in
suspend. )
Usually the RTC is exposed as an sys file entry with name like RTC0 or R
The Qualcomm MDM9216 might be using a USB HSIC type of interface to
communicate with the modem. The messages sent over this ( hsic device
driver) are often wrapped in propriety packet formats to be understood
between the RIL (user space) and the modem only.
Also nowadays the AT commands might
Try changing the values of TCP and UDP buffers manually by echo the values
on the sys file entries and see if the situation is improved. Later these
tweaks can be added in the init.rc .
rmem and wmen are the buffers :
*/proc/sys/net/ipv4/tcp_wmem* and */proc/sys/net/ipv4/tcp_rmem*
*
*
Also tw
Adding to that sometimes during boottime if the cpu activity is high
sometimes some logs are jumbled or missed...Its often better to ( i always)
do a # cat /proc/kmsg to see total logs when on adb shell,specially when
dmesg is unsatisfactory.
Also in serial logs make sure ur serial bus is at 1
It can be that the kernel boot but failed or it can be that bootloader
didnt start the uncompressing of kernel...
This can be seen with the Serial (UART) logs.. search hot it can be seen..
often to see kernel logs over UART.. the CMDLINE variables of the
bootloader has to be set (right ttyxxx
Doing a dmesg or cat /proc/kmsg over adb after few seconds (considering no
screen task is there) after screen has hit off (this is called ealy
suspend).
Note : you will not hit suspend if you connected over adb (usb is active)
so connect after suspend might have hit and got failed.
Check for the
Hi
It looks with the bootloader param's passed to Kernel in the "ATAG_CMDLINE:
3d 54410009 ': loglevel=8 console=ram " is configured with 'console=ram'.
Try changing console to a valid serial port (tty).
Anirudh
On Wednesday, June 5, 2013 2:41:43 PM UTC+5:30, Dilshad Alam wrote:
>
> Hi,
>
