Eris msm_pm_wait_state reboot syndrome? - Droid Eris Android Development

Hi folks,
Long time since I popped in here.
I'm wondering if you've seen behavior similar to this before:
Spontaneous reboots during suspend/resumes (that is, an app running but the screen is off) which *sometimes* result in output like this at the tail end of /proc/last_kmsg
Code:
[ 2331.773132] msm_pm_wait_state(80, 0, 0, 0) failed 10d29
[ 2331.773132] msm_sleep(): msm_pm_wait_state failed, 10d29
[ 2331.929382] msm_pm_wait_state(80, 0, 0, 0) failed 10d29
[ 2331.929382] msm_sleep(): msm_pm_wait_state failed, 10d29
No errors detected
I can manage to run logcat as a background process (the syndrome seems to involve the kernel PM (Power Management) suspend/resume function, as it refuses to occur when plugged in to USB); sometimes I also see
Code:
09-01 21:07:58.371 273 416 E RPC : error writing RPC packet: 22 (Invalid argument)
as the last line in the logcat. I don't know what is lost in the logcat output after that due to buffering, but the "No errors detected" in /proc/last_kmsg seems to point away from a kernel panic. And yet the phone reboots in a decidedly ungraceful fashion... if all filesystems were flushed I would expect to see something in the logcat about a reboot.
Test conditions:
Kernel: 2.6.29-DecaFuctCFS-dirty-9ff84b92 ([email protected]) (gcc version 4.4.0 (GCC) ) #5 PREEMPT Thu Jan 27 22:14:44 EST 2011
ROM: Condemned Soul's CCM7-V21 Vanilla
CM CPU min/max: 245/729 (* I don't think this matters)
Governor: ondemand
Other: Screen must be off and phone disconnected from external (USB) power for this reboot to occur; my test condition also includes the phone in Airplane mode. (I do not know if the latter is necessary for bug expression).
I can add more detail, but I didn't want my post to get too long. I can cause this to happen deterministically (a delay of one to several minutes before the phone reboots). The app involved uses the GPS hardware...
Anyhow... does this syndrome sound familiar at all?
bftb0
PS Yes this is a real-world scenario - I want to do GPS track recording in areas without cell/wifi service, so... running without USB power and no radios (for battery conservation) is a priority.

Related

Looking for kernel / build Without Audio stuttering on Blackstone!

Trying to solve audio stuttering...
I'm currently running the Eclair build from Kenia from
http://forum.xda-developers.com/showthread.php?t=827537
Like the speed, most things working fine.
... but playing media results in audio stutter.
Problem is apparently well known and affects more devices, see also
http://forum.xda-developers.com/showthread.php?t=711692&page=364
Indeed, killing battery service solves stuttering, but I'd like to keep it running, of course
Any build/kernel out there that does not suffer from this?
I'd like to find out what's different, since in the past it seemed to have worked, but with pushing more accurate battery readout in the latest kernels, this problem was introduced...
Maybe just putting an old battery service in a current kernel could work?
Cheers,
Robbert
I can confirm that audio shuttering is a common problem, but I wasn't aware it can be related to the battery code. Can anyone check if killing battery service helps with shuttering audio (youtube maybe?) on other build (e.g. FRX03)?
TBH battery code is unfinished since Camro (the guy who did most of it) bricked his phone. If it's really a kernel issue maybe I'd could build test kernel w/o battery code sometime next week.
g3rm0 said:
I can confirm that audio shuttering is a common problem, but I wasn't aware it can be related to the battery code. Can anyone check if killing battery service helps with shuttering audio (youtube maybe?) on other build (e.g. FRX03)?
TBH battery code is unfinished since Camro (the guy who did most of it) bricked his phone. If it's really a kernel issue maybe I'd could build test kernel w/o battery code sometime next week.
Click to expand...
Click to collapse
Hi, g3rm0,
Always happy to do some more testing!
Took me some time to get a FRX03 build back working (not my daily build, Froyo is just too slow on blackstone, I'm afraid)
Anyway: Using the FRX03 build from
http://forum.xda-developers.com/showthread.php?t=711692
(full package, so using the included rootfs, zimage and modules.)
I can *confirm* that audio still stutters, and also on this build stuttering immediately disappears when battery service is killed!
Hope it helps?
If there's need to test different rootfs/zimage/modules/startup/..., just let me know!
Actually, for me, I just want to disable battery service so I can listen to music on my 15min bike ride to work!
But I am a linux Noob, so although "kill -9" is in my power to stop the service, actually restarting a service is momentarily out of reach...
Any help with restarting the [battery] service would be greatly appreciated!
Cheers,
Robbert
You don't need to compile a kernel tbh, why don't you just create an init script which includes the "kill -9 28" command? The init script will get launched on startup therefore killing the battery service as desired.
Best Regards,
ST1Cl<^^aN
Stickman89 said:
You don't need to compile a kernel tbh, why don't you just create an init script which includes the "kill -9 28" command? The init script will get launched on startup therefore killing the battery service as desired.
Best Regards,
ST1Cl<^^aN
Click to expand...
Click to collapse
Hi, Stickman89,
Yes, I read this also somewhere, thanks for reminding me!
My bigger wish is to be able to restart the battery service after finishing listening to music, not having to restart Android (and first WinMo) because that takes way too much time.
How do I restart the service, any idea?
Cheers,
Robbert
well to do that you would need to install a mobile terminal app from the market and create two scripts, one to disable the service and the other to enable it. Only problem is this would not be automated and you would need to execute the script via the terminal app installed.
Best Regards,
ST1Cl<^^aN
Stickman89 said:
well to do that you would need to install a mobile terminal app from the market and create two scripts, one to disable the service and the other to enable it. Only problem is this would not be automated and you would need to execute the script via the terminal app installed.
Best Regards,
ST1Cl<^^aN
Click to expand...
Click to collapse
I could live with that (still hoping for a proper fix, of course!)
Most builds come with a terminal app (Busybox is popular, if I remember correctly) that's what you mean?
But still I need the command line / script lines to execute, and that's where I'm stuck, since I know how to kill the service from the prompt of my terminal in the phone, but not how to "unkill" it!
"Disable/enable" sounds much better than "kill/unkill", but how???
As a side note, I also get the impression that the android terminal does not give me full access to a shell environment, since, for example, the "ps" command is severely limited! (wanted to find out more information on process "[battery]", but no chance with the crippled "ps" command...)
Maybe there are better (more functional) terminals out there?
Or do we actaully have access to "enable/disable service" commands in this "busybox" and I just don't know the proper command?
(just for reference: I'm running Kenia's eclair build that includes busybox 1.5 as terminal)
Cheers, Robbert
Even better, look what I just found for you: http://forum.xda-developers.com/showthread.php?t=486486
Basically you can create a homescreen icon and assign a shell command to it, simply create an icon and assign the "kill -9 28" command to it which will kill the battery service, I would have to check out the process name to be able to start it again. Let me take a look for you (I don't think "start -9 28" will work as we have only issued the process ID and since it is no longer running will be useless)
Best Regards,
ST1Cl<^^aN
If you have a working adb setup then type: "adb shell ps -w"
or download a mobile terminal and type: "ps -w"
Ok here are the processes running, PID 28 is krpcserversd in our case which is incorrect so we need to look for the battery service which is PID 29 for me.
Code:
# ps
ps
PID USER VSZ STAT COMMAND
1 0 312 S /init.android
2 0 0 SW [kthreadd]
3 0 0 SW [ksoftirqd/0]
4 0 0 SW [watchdog/0]
5 0 0 SW [events/0]
6 0 0 SW [khelper]
7 0 0 SW [suspend]
8 0 0 SW [kblockd/0]
9 0 0 SW [cqueue]
10 0 0 SW [kmmcd]
11 0 0 SW [btaddconn]
12 0 0 SW [btdelconn]
13 0 0 SW [kondemand/0]
14 0 0 SW [smd_tty]
15 0 0 DW [rpcrouter]
16 0 0 SW [kadspd]
17 0 0 SW [detection/0]
18 0 0 SW [button/0]
21 0 0 SW [kswapd0]
22 0 0 SW [aio/0]
23 0 0 SW [panel_on/0]
24 0 0 SW [tty_wq/0]
25 0 0 SW [usb_mass_storag]
26 0 0 SW [kstriped]
27 0 0 SW< [krfcommd]
28 0 0 SW [krpcserversd]
29 0 0 DW [battery]
54 0 0 SW [mmcqd]
71 0 0 SW< [loop2]
90 0 0 SW< [loop0]
94 0 0 SW< [loop1]
133 0 1736 S busybox telnetd -b 192.168.20.1 -l /bin/sh
1168 0 1740 S /bin/sh /bin/userinit.sh -c /sdcard/conf/froyo.user.
1226 0 1740 S /bin/sh
1227 1000 812 S /system/bin/servicemanager
1228 0 3728 S /system/bin/vold
1229 0 1736 S /bin/sh /bin/netd
1231 0 668 S /system/bin/debuggerd
1232 1001 5464 S /system/bin/rild -l /lib/froyo/libhtcgeneric-ril.so
1233 0 87964 S zygote /bin/app_process -Xzygote /system/bin --zygot
1234 1013 26664 S < /system/bin/mediaserver
1238 1002 1260 S /system/bin/dbus-daemon --system --nofork
1239 0 824 S /system/bin/installd
1240 1017 1612 S /system/bin/keystore /data/misc/keystore
1241 0 3340 R /sbin/adbd
1243 0 3720 S /system/bin/netd
1258 1000 246m S system_server
1330 10054 124m S com.swype.android.inputmethod
1345 10011 129m S N com.google.process.gapps
1434 1001 134m S < com.android.phone
1685 1000 123m S com.android.settings
2847 0 0 DW [audmgr_rpc]
3391 0 0 DW [ksdiorqd]
3392 0 0 SW [tiwlan_wifi_wq]
3400 1010 3004 S /system/bin/wpa_supplicant -Dtiwlan0 -itiwlan0 -c/da
3588 10007 107m S com.android.quicksearchbox
4937 10053 159m S android.process.acore
5076 10058 108m S com.appspot.swisscodemonkeys.apps
5083 10023 105m S com.android.voicedialer
5095 10004 110m S com.android.vending
5106 10026 114m S com.google.android.googlequicksearchbox
5113 10002 126m S android.process.acore
5233 10037 105m S com.android.defcontainer
5243 10030 112m S com.google.android.apps.genie.geniewidget
5273 10010 111m S < android.process.media
5284 10014 114m S com.google.android.gm
5338 0 0 SW [pdflush]
5462 10064 106m S mobi.infolife.taskmanager
5524 0 0 SW [pdflush]
5532 10070 123m S stericson.busybox
5584 10061 115m S com.facebook.katana
5631 0 1736 S sleep 500
5635 10059 114m S cn.miren.browser
5662 0 740 S /system/bin/sh -
5665 10060 122m S com.voxmobili.phonebook2
5691 10056 108m S com.miui.player
5697 10028 108m S com.google.android.apps.uploader
5705 0 1740 R ps
Once the battery service has been located so in my case PID 29 then to kill that PID via adb simply issue "adb shell kill 29" (PID number may vary so please check) and to start the PID issue "command-removed".
So if you want to use the application i linked you to over at the G1 thread then simply assign the commands "kill 29" to kill the service and "command-removed" (remember that the PID number may vary so please check) to start the service again.
FYI charging will stop at this point and battery stats will freeze at there current percentage.
Best Regards,
ST1Cl<^^aN
Stickman89 said:
Ok here are the processes running, PID 28 is krpcserversd, interestingly we also have the PID 29 which is battery.
Click to expand...
Click to collapse
Same here for me: PID is 29 (it may different in some builds) but... when I killed battery service (kill -9 29) audio shuttering stopped. It also solved "audpp: DMA missed" messages in dmesg so maybe we're on the right track.
IMHO killing battery service every time is not a solution. Maybe code just needs to be cleaned up a little.
Anyway, for now kill -9 is the only (known) way to achieve smooth playback.
Ok then all we need to do is adjust the scheduling priority until we find the sweet spot via renice
That way we wouldn't need to kill anything and that can be added to init fairly easy, we would have to test some values first.
Best Regards,
ST1Cl<^^aN
Stickman89 said:
Ok then all we need to do is adjust the scheduling priority until we find the sweet spot via renice
That way we wouldn't need to kill anything and that can be added to init fairly easy, we would have to test some values first.
Best Regards,
ST1Cl<^^aN
Click to expand...
Click to collapse
Tried that already, afraid it might not be so easy...
Gave the audiomanager -20 or so, and the battery service +20 or so, no effect, still stuttering...
But maybe your mileage may vary, did you try this on your build?
Cheers,
Robbert
Stickman89 said:
If you have a working adb setup then type: "adb shell ps -w"
or download a mobile terminal and type: "ps -w"
Ok here are the processes running, PID 28 is krpcserversd in our case which is incorrect so we need to look for the battery service which is PID 29 for me.
Click to expand...
Click to collapse
Also for me, number 29 it is.
Stickman89 said:
Once the battery service has been located so in my case PID 29 then to kill that PID via adb simply issue "adb shell kill 29" (PID number may vary so please check) and to start the PID issue "--locating-process--".
So if you want to use the application i linked you to over at the G1 thread then simply assign the commands "kill 29" to kill the service and "--locating-process--" (remember that the PID number may vary so please check) to start the service again.
Click to expand...
Click to collapse
Huh?
Something must have gotten "lost in translation" here, I have really no idea what is meant by the command "--locating-process--", I guess it's not literally typing in this phrase, what am I missing?
Ah, just noticed your statement in an earlier post "I would have to check out the process name to be able to start it again", I guess that's what you meant by "--locating-process--" in the next post...?
Well, to be continued...
Cheers,
Robbert
The service isn't successfully starting after being killed, I initially thought it had but it appears it failed to kill on first try therefore it was still running. I will keep looking into this though, stuttering isn't that bad on my build. I will upload it soon, it is there but isn't too bad.
Best Regards,
ST1Cl<^^aN
Stickman89 said:
The service isn't successfully starting after being killed, I initially though it had but it appears it failed to kill on first try therefore it was still running. I will keep looking into this though, stuttering isn't that bad on my build. I will upload it soon, it is there but isn't too bad.
Best Regards,
ST1Cl<^^aN
Click to expand...
Click to collapse
Yeah, noticed that too, sometimes the service takes a few seconds to unload (or at least "ps" still shows it.)
Maybe someone else has some bright ideas, posted it also at Neopeek, some good guys over there, too
I just hoped someone had a quick solution, but we may have to wait for some more kernel development. I'll keep my eyes open, if something pops up I'll update.
Cheers,
Robbert
May I ask what application you guys are using to kill the process? I downloaded the terminal emulator app, however when I type "kill 29" it says operation not allowed.
I'm assuming this is because of a rights issue. I am using Android 2.2 (FroYo) by the Brilliant Mistake [03 Sep 2010] (V1.6) with the latest kernel, zimage, rootfs along with FRX03 update.
I'm a bit confuse as to how I can "root" my device in order kill the battery process so I too can listen to my music without the annoying stuttering.
Any info would be appreciated. Thanks
Just type "su" first
g3rm0 said:
Just type "su" first
Click to expand...
Click to collapse
Thank you for your reply.
I type "su" then enter...
I get a "#" prompt
then I type "kill 29" enter
I don't get any type of confirmation just another "#" prompt
I try listening to my music, stuttering is still there... What am I doing wrong?
James62370 said:
Thank you for your reply.
I type "su" then enter...
I get a "#" prompt
then I type "kill 29" enter
I don't get any type of confirmation just another "#" prompt
I try listening to my music, stuttering is still there... What am I doing wrong?
Click to expand...
Click to collapse
"kill -9 29" has a better chance
Did you check before killing it, that [battery] is process 29 for you? (use "ps" command in shell)
Did you check afterwards that process 29 [battery] is indeed gone?
Just wait for viruscrazy submit the patch to phh to be merge in the main tree.It already in Jerome tree HERE
Code:
/* Patch to fix "audpp DMA missed" messages on AMSS version 52.62.25.34 */
1423 if ( machine_is_htcdiamond() || machine_is_htcblackstone() ) {
1424 if( !(snd_state & SND_STATE_PLAYBACK) ) {
1425 dex.cmd = PCOM_GET_BATTERY_DATA;
1426 msm_proc_comm_wince(&dex, 0);
1427 } /* else {
1428 printk("Skipping battery pcom call to avoid audppp DMA miss\n");
1429 } */
1430 }

[Q] Wifi problem: failed to load Wifi driver. Anyone else seen this?

Hi,
I have tested all possible ROMS (Beast, Utopian, NI, CyanogemMod, EdenX,...) and I encounter the same problem: the interface goes in Error after some time. When I flash and start using it, it's woking fine, but after some time (counted in minutes, not in days), network is down and in the Network settings panel, I get the message "error". Sometimes the interface comes back up, but at some point, it stays in error and in logcat I have
E/WifiService( 1242): Failed to load Wi-Fi driver.​
Dmesg gives:
Code:
[<4>[ 1190.039532] Dongle Host Driver, version 4.218.223.1
<4>[ 1198.044261] __ratelimit: 17 callbacks suppressed
<4>[ 1198.048915] dhd_module_init: sdio_register_driver timeout
I also see other errors in the dmesg output:
Code:
<4>[ 1180.754089] dhdsdio_dpc: FAILEDnewstatusREAD, LINE 4092
<4>[ 1180.836536] dhdsdio_dpc: failed backplane access over SDIO, halting operation 1
<4>[ 1180.844034] dhdsdio_dpc: failed backplane access over SDIO, halting operation 1
<4>[ 1180.851469] dhdcdc_query_ioctl: dhdcdc_msg failed w/status -5
<4>[ 1180.871027] dhd_ioctl_entry DONGLE_DOWN,__FUNCTION__
<4>[ 1180.954228] dhd_start_xmit: xmit rejected pub.up=1 busstate=0
<4>[ 1180.960068] dhd_start_xmit: Event RELOAD send up
<4>[ 1180.964706] BUG wlan0 code -19 qlen 0
<4>[ 1186.978451] dhd_ioctl_entry DONGLE_DOWN,__FUNCTION__
<4>[ 1190.019110] bcmsdh_sdmmc: probe of mmc0:0001:1 failed with error -5
I attached logcat and dmesg files.
Before I send my unit to repair, anyone having seen the same problem? Is this really a hardware problem, and if yes, how comes it works fine for some time before breaking?
I've just seen in the dmesg that there are badblocks on mtdblock4. Could that be the reason?
Code:
<4>[ 35.143702] yaffs: Attempting MTD mount on 31.4, "mtdblock4"
<6>[ 35.163593] tegra_nand tegra_nand: Block 0x92d is bad [chip=0,offset=0x125a0000]
<3>[ 35.170984] tegra_nand tegra_nand: Reading OOB data of bad block
I hope someone can help me as I'd rather not send my adam back for repair!
Thanks
Raph
Try the unbricking procedure (not sure it will actually help though). A fresh flash with NVFlash might get you up and running again though the bad sectors do concern me.

[Android] TouchPad Android kernel mini howto

It seems there is little information on the internet regarding how to compile the kernel and how to convert to the correct image format so the boot loader will recognise and how to transfer it over to the touchpad. I ended up spent a few hours and finally figured out. I hope this will be useful for someone. I will try to make it concise as this is mainly aimed for developers.
What you will need
A linux development machine with uboot mkimage tool installed.
Sourcery G++ Lite 2010q1-188 for ARM EABI cross compile tool chain
https://sourcery.mentor.com/sgpp/lite/arm/portal/release1294
Touchpad kernel source
https://github.com/CyanogenMod/hp-kernel-tenderloin
CM7 Alpha 3 image (zip file)
http://goo-inside.me/roms/cmtouchpad/alpha3/update-cm-7.1.0-tenderloin-a3-fullofbugs-signed.zip
Prepare
Download CM7 Alpha 3 image and extract the boot.img to a temporary place.
Download Sourcery G++ Lite and install it. Add the G++ Lite tool chain binaray path to the PATH env variable. Get the kernel source from git hub and extract to local disk and change directory to the kernel source.
Compile the kernel
Still in the kernel source directory run
Code:
make ARCH=arm CROSS_COMPILE=arm-none-eabi- tenderloin_android_defconfig
make ARCH=arm CROSS_COMPILE=arm-none-eabi- uImage
Prepare the initramfs U-boot image
Extract the initramfs from the boot.img saved in temporary folder and convert it to uboot-image format
Code:
dd if=boot.img bs=1 skip=3577748 of=img.gz
mkimage -A arm -O linux -T ramdisk -C none -a 0x60000000 -e 0x60000000 -n "Image" -d ./img.gz arch/arm/boot/uRamdisk
(The dd offset for alpha 2.1 image is 3561152)
Combine the kernel and initramfs into a single U-boot image
Create a combined U-boot image (kernel and initramfs)
Code:
mkimage -A arm -O linux -T multi -a 0x40208000 -e 0x40208000 -C none -n "multi image" -d arch/arm/boot/uImage:arch/arm/boot/uRamdisk uImage.CyanogenMod.new
Transfer it to the device
Boot your touchpad into recovery mode and run
Code:
adb shell mount /dev/block/mmcblk0p13 /boot
adb push uImage.CyanogenMod.new /boot/uImage.CyanogenMod.new
adb shell umount /boot
adb shell reboot
After it reboot you should be able to see a new CyanogenMod.new item from the boot menu.
That's it!
Optimisation
For those who wants to experiment with GCC build options you can update the entry "arch-$(CONFIG_CPU_32v7" in file arch/arm/Makefile and I set mine to
Code:
arch-$(CONFIG_CPU_32v7) :=-D__LINUX_ARM_ARCH__=7 -mtune=cortex-a8 -mfpu=neon -ftree-vectorize -mfloat-abi=softfp -O2 $(call cc-option,-march=armv7-a,-march=armv5t -Wa$(comma)-march=armv7-a)
Warning
Please be aware you are working on the bleeding edge kernel for touchpad and there is no guarantee that the latest git version will work for you. Please try an earlier version if that's the case.
As of 2011-11-23 you will need the latest kernel source to build kernel for alpha 3. Please do not mix the kernel with an initramfs from a different version, i.e. don't use initramfs extracted from alpha 2.1 and use it with alpha3.
Thanks for this. Last weekend spent a while trying to figure this out.
Sent from my HP Touchpad using Tapatalk
x2. Huge thanks
Thank you soooooo much for this guide. Quick question if you don't mind though.. I am using an mkimage that goes back to my nook kernel days. Is there anything newer out, or would this still be ok,?
Divine_Madcat said:
Thank you soooooo much for this guide. Quick question if you don't mind though.. I am using an mkimage that goes back to my nook kernel days. Is there anything newer out, or would this still be ok,?
Click to expand...
Click to collapse
As long as the mkimage can generate a standard U-boot image it should be fine.
You can always try it yourself. In worst case you have to hard reboot the touchpad by pressing the power button and home button at the same time for more than 10 minutes. As long as you keep the original image files (UImage.*) untouched I don't think you can brick it even if you want to.
S7
I have been trying to compile the kernel for some time now, and was hopeful reading your guide (and this last post) However, still following the steps to merge the ramdisk, i cannot make a booting kernel. I can get it flashed, as i am using the update.zip method, but moboot always gives me a crc error when booting it.
Though, before i totally go nuts, i think i need to try the source forgery toolchain, as i am using the Android ndk r6b...
Divine_Madcat said:
S7
I have been trying to compile the kernel for some time now, and was hopeful reading your guide (and this last post) However, still following the steps to merge the ramdisk, i cannot make a booting kernel. I can get it flashed, as i am using the update.zip method, but moboot always gives me a crc error when booting it.
Though, before i totally go nuts, i think i need to try the source forgery toolchain, as i am using the Android ndk r6b...
Click to expand...
Click to collapse
Could you check the md5sum of the u-boot image crated on disk and the one installed by update.zip file? Do they match? If they do then you probably will need to upgrade your mkimage tool.
s7mx1 said:
Could you check the md5sum of the u-boot image crated on disk and the one installed by update.zip file? Do they match? If they do then you probably will need to upgrade your mkimage tool.
Click to expand...
Click to collapse
I will give it a check; just in case, know where to get a newer mkimage?
Thanks so much for this guide
s7mx1 said:
You can always try it yourself. In worst case you have to hard reboot the touchpad by pressing the power button and home button at the same time for more than 10 minutes.
Click to expand...
Click to collapse
It feels like 10 mins.. doesn't it
WEll, i checked the MD5 sums, and it looks good. So, i guess it is time to try again with the toolchain listed here, and perhaps a new mkimage (if there is a "modern" one i should using, please point me to it...)
edit: Never mind.. in all my looking, i never saw that ubuntu had a nice one waiting for me.... doh
edit2: Woo! After getting the probably correct mkimage, and the CS toolchain, looks like i finally got it to pass the crc check. Now, lets see if it finishes booting. Thanks again for the guide!
Nope.. no boot. I get a dmesg with this:
<3>[ 69.978716] init: untracked pid 224 exited
<6>[ 70.086076] android_usb gadget: high speed config #1: android
<6>[ 70.086209] gadget_event: schedule host_connected
<6>[ 70.096953] max8903b_current_setup: CURRENT_500MA
<6>[ 70.097040] gadget_event: source=bus mA=500 (no change)
<4>[ 70.910953] UDC-CHG (2-2-2): usb_multi_chg_detect (591) : USB host Adaptor
(500mA)!
<6>[ 70.912805] gadget_event: schedule host_disconnected
<6>[ 70.925482] max8903b_current_setup: CURRENT_ZERO
<6>[ 71.164066] android_usb gadget: high speed config #1: android
<6>[ 71.164220] gadget_event: schedule host_connected
<6>[ 71.173640] max8903b_current_setup: CURRENT_500MA
<6>[ 71.178212] gadget_event: source=bus mA=500 (no change)
<6>[ 72.160955] gadget_event: host_connected=1 (no change)
<6>[ 74.142224] request_suspend_state: wakeup (0->0) at 74121495501 (2011-11-1
1 22:49:33.378031648 UTC)
<3>[ 74.143675] init: untracked pid 266 exited
<3>[ 74.155217] init: untracked pid 273 exited
<6>[ 79.285016] request_suspend_state: wakeup (0->0) at 79264287462 (2011-11-1
1 22:49:38.520824942 UTC)
The last three lines repeat alot, with different pid's .
Alrighty.. figured this one out - You cannot use the latest repository commits with the 2.1 alpha build. However, i was able to build commit fd70bb7aae, and it builds and actually boots. Now, i can actually play around and tweak it. Thank you again for the guide, and sorry for the edit spamming.. heh.
myn said:
x2. Huge thanks
Click to expand...
Click to collapse
Myn, do you have a touchpad???!!!? God I hope so!
vinscuzzy said:
Myn, do you have a touchpad???!!!? God I hope so!
Click to expand...
Click to collapse
He does
Sent from my PG86100 using Tapatalk
Divine_Madcat said:
WEll, i checked the MD5 sums, and it looks good. So, i guess it is time to try again with the toolchain listed here, and perhaps a new mkimage (if there is a "modern" one i should using, please point me to it...)
edit: Never mind.. in all my looking, i never saw that ubuntu had a nice one waiting for me.... doh
edit2: Woo! After getting the probably correct mkimage, and the CS toolchain, looks like i finally got it to pass the crc check. Now, lets see if it finishes booting. Thanks again for the guide!
Nope.. no boot. I get a dmesg with this:
<3>[ 69.978716] init: untracked pid 224 exited
<6>[ 70.086076] android_usb gadget: high speed config #1: android
<6>[ 70.086209] gadget_event: schedule host_connected
<6>[ 70.096953] max8903b_current_setup: CURRENT_500MA
<6>[ 70.097040] gadget_event: source=bus mA=500 (no change)
<4>[ 70.910953] UDC-CHG (2-2-2): usb_multi_chg_detect (591) : USB host Adaptor
(500mA)!
<6>[ 70.912805] gadget_event: schedule host_disconnected
<6>[ 70.925482] max8903b_current_setup: CURRENT_ZERO
<6>[ 71.164066] android_usb gadget: high speed config #1: android
<6>[ 71.164220] gadget_event: schedule host_connected
<6>[ 71.173640] max8903b_current_setup: CURRENT_500MA
<6>[ 71.178212] gadget_event: source=bus mA=500 (no change)
<6>[ 72.160955] gadget_event: host_connected=1 (no change)
<6>[ 74.142224] request_suspend_state: wakeup (0->0) at 74121495501 (2011-11-1
1 22:49:33.378031648 UTC)
<3>[ 74.143675] init: untracked pid 266 exited
<3>[ 74.155217] init: untracked pid 273 exited
<6>[ 79.285016] request_suspend_state: wakeup (0->0) at 79264287462 (2011-11-1
1 22:49:38.520824942 UTC)
The last three lines repeat alot, with different pid's .
Alrighty.. figured this one out - You cannot use the latest repository commits with the 2.1 alpha build. However, i was able to build commit fd70bb7aae, and it builds and actually boots. Now, i can actually play around and tweak it. Thank you again for the guide, and sorry for the edit spamming.. heh.
Click to expand...
Click to collapse
That's because dalingrin has updated the default configuration to use the HIGHMEM which seems to kill all the apps. The latest git actually works if you disable all the HIGHMEM related stuff.
decalex said:
Thanks so much for this guide
It feels like 10 mins.. doesn't it
Click to expand...
Click to collapse
Absolutely
I just hope there is a rest button as the touchscreen occasionally will not respond at all after wake up and I have to reboot to webos and then reboot back to get the touchscreen back.
Great guide and I got the kernel all built, but how do you change the kernel arguments for booting? e.g. where does moboot get its whole root=/dev/ram0 ro fb...stuff, and how does the CyanogenMod kernel know where to look for the rootfs partition?
crimsonredmk said:
Great guide and I got the kernel all built, but how do you change the kernel arguments for booting? e.g. where does moboot get its whole root=/dev/ram0 ro fb...stuff, and how does the CyanogenMod kernel know where to look for the rootfs partition?
Click to expand...
Click to collapse
The root parameter (root=/dev/ram0) that passed to kernel is not useful to you. The root / is mere extracted initramfs in memory. I assume you are looking for system, data partitions etc. With TP we have LVM partitions which you can do really fancy stuff with. The actual mount device and mount point is defined (hard coded) in file init.tenderloin.rc which you can find in the initramfs (i.e. the img.gz which is a gzipped cpio file). You can extract all the contents out from img.gz and modify init.tenderloin.rc to suit your need and then create an updated initramfs file to go with the kernel.
Since Android (at least CM7 on TP) does not use pivot_root any changes made to the initramfs will appear automatically when you boot up the device.
You can google if you are not sure how to work with initramfs file.

phone not being recognized in download mode by OS X Lion

So here's the rundown:
Flashing with odin on my whitebox has become unstable (hangs and freezes during flashing unless it it something small like just the recovery has been working but full rom flashes fail almost everytime), so i wanted to try heimdall on my mac and i can't get heimdall or odin through parallels to recognize my phone when it is in download mode. When the phone is on it will recognize and mount just fine.
i was reading around and someone said to see what console.app would say when the phone is plugged in in dl mode, this is what i got back:
Code:
12/12/11 10:03:16.000 PM kernel: USBF: 1464367.352 AppleUSBEHCI[0xffffff8024fc4000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfa, timing out! (Addr: 6, EP: 0)
12/12/11 10:03:16.000 PM kernel: USBF: 1464367.422 USB Device Gadget Serial is violating Section 9.3.5 of the USB Specification -- Error in GetConfigDescriptor( wLength = 4)
12/12/11 10:03:22.000 PM kernel: USBF: 1464373.356 AppleUSBEHCI[0xffffff8024fc4000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfa, timing out! (Addr: 6, EP: 0)
12/12/11 10:03:22.000 PM kernel: USBF: 1464373.357 AppleUSBComposite[0xffffff8047348a00](Gadget Serial) GetFullConfigDescriptor(0) returned NULL
12/12/11 10:03:28.000 PM kernel: USBF: 1464379.358 AppleUSBEHCI[0xffffff8024fc4000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfa, timing out! (Addr: 6, EP: 0)
12/12/11 10:03:28.000 PM kernel: 0 0 AppleUSBCDC: start - initDevice failed
now i googled this line as i think it is the culprit so to speak:
Code:
12/12/11 10:03:16.000 PM kernel: USBF: 1464367.422 USB Device Gadget Serial is violating Section 9.3.5 of the USB Specification -- Error in GetConfigDescriptor( wLength = 4)
and found a similar problem documented HERE
does any one know what bootloaders he is talking about? and if so where i can get them and the process to update them if it differs from the normal flashing process.

TWRP random reboots

I am not sure how to file a bug report or what all that entails, so I'll just post here.
TWRP randomly reboots. One minute, five minutes, whenever. Even if I just leave the screen on and touch nothing, it still happens. Rebooting has even happened while flashing, which is no good. Other's have confirmed this behavior in the i777 thread:
http://forum.xda-developers.com/showthread.php?t=2544790 I've tried wiping and reflashing the rom a few times (and just boot.img as well), but the behavior always exists.
i777 build. currently on 12/27 nightly. I am now using RenderBroken's kernel for Omni & the rebooting does not happen.
Thanks. :good:
bleggy said:
I am not sure how to file a bug report or what all that entails, so I'll just post here.
TWRP randomly reboots. One minute, five minutes, whenever. Even if I just leave the screen on and touch nothing, it still happens. Rebooting has even happened while flashing, which is no good. Other's have confirmed this behavior in the i777 thread:
http://forum.xda-developers.com/showthread.php?t=2544790 I've tried wiping and reflashing the rom a few times (and just boot.img as well), but the behavior always exists.
i777 build. currently on 12/27 nightly. I am now using RenderBroken's kernel for Omni & the rebooting does not happen.
Thanks. :good:
Click to expand...
Click to collapse
pull /proc/last_kmsg after a reboot please
ok. currently on renders omni kernel. after I flash the next nightly, I'll have twrp reboot itself & upload that log.
cat /proc/last_kmsg > last_kmsg.txt with a terminal emulator, correct?
Sent from my SGH-I777 using XDA Premium 4 mobile app
Here is one I prepared earlier, probably around Dec 20th: http://paste.ubuntu.com/6654443/
Code:
$ egrep ' 12[01]\.|kadapt' last_kmsg
<6>[ 120.185215] c0 sec-battery sec-battery: sec_bat_check_vf: Battery Health (1)
<6>[ 120.185765] c0 smb328-charger 19-0034: smb328_get_charging_health : charging status A(0x02)
<6>[ 120.186305] c0 smb328-charger 19-0034: smb328_get_charging_health : charging status B(0x00)
<6>[ 120.186843] c0 smb328-charger 19-0034: smb328_get_charging_health : charging status C(0x05)
<6>[ 120.186889] c0 smb328-charger 19-0034: smb328_get_property: smb328_get_property (2,1)
<6>[ 121.005248] c0 sec-thermistor sec-thermistor: notify_change_of_temperature: uevent: TEMPERATURE=510
<6>[ 121.805308] c0 cpu1 turnning off!
<4>[ 121.811130] c1 IRQ112 no longer affine to CPU1
<5>[ 121.811478] c0 CPU1: shutdown
<6>[ 121.812313] c0 cpu1 off!
<3>[ 240.170095] c0 INFO: task kadaptiveup:1058 blocked for more than 120 seconds.
<6>[ 240.194448] c0 kadaptiveup D c0c436fc 0 1058 2 0x00000000
$
Regression seemed to happen for me between Dec 15 & 18, which coincided with gerrit saying there were some scheduler patches for smdk4412 around that time, along with the defconfig & dock patches. I haven't figured out enough about kernel building and what I need to insert where and how, to do any testing myself as yet.
I found this initially when I tried to enable compression for TWRP backups. With compression enabled I can usually trigger a panic.
Entropy512 said:
pull /proc/last_kmsg after a reboot please
Click to expand...
Click to collapse
updated to the 12/29 nightly.
omni version: 4.4.2-20131229-i777-nightly
kernel version: 3.0.64-CM-g1f99098
build number: omni_i777-userdebug 4.4.2 KOT49H 96 test-keys
went back into recovery & let sit without touching anything.
rebooted itself after 3 minutues.
attached is the last_kmsg. if there is anything else I can do, let me know.
Omni 1229 => panic @ 240 seconds as usual, cpu1 shutdown at 120 sec, cpu1 won't start by 240 sec, kadaptiveup kernel task hung still, seems just to be time based, don't need to do anything. I have last_kmsg if required.
Omni Asylum kernel 1227 from @chasmodo, cpu1 stop/start OK, no problem, @chasmodo said he rolled back to Dec 16.
@chasmodo build comment here: http://forum.xda-developers.com/showpost.php?p=48864227&postcount=11241
Kernel here: http://forum.xda-developers.com/showpost.php?p=35551986&postcount=2
Omni Asylum ROM 1229 from @chasmodo, OK too.
****. It's those extra governors.
I've seen this before.
Time to rip those ****ers out.

Categories

Resources