[TESTING] Updated 5/14/11 New Kernel - Temp Test - SOD Fix!

[arrrghhh]

New kernel folks, panel detect! Please read the first post...

I have gotten responses back from a bunch of different 100's, a 300 and a couple of 400's.

So if you have a RHOD210 (TMobile) or RHOD500 (VZW) please grab your dmesg and look for those two lines about the type of panel. Thanks!

[fishingmedic]

I'm gonna try d/l'ing this one from work, been having a hell of a time even getting android working again on my phone, regardless of which build I'm using. Even tried older builds that I moved off my card and keep getting reboots, SOD's, etc, hell half the time I'm getting errors saying the system is screwed before I can even do anything, so I've got no logs or anything to pull. I'm about to throw this freaking phone through a wall right now, except that winmo is still working fine! And I'm trying on my 6 month old 8G class 8 card, 4G class 2 and a brand spanking new 8G class 4, they're all doing the same thing, all reformatted, new builds, etc.

[arrrghhh]

Originally Posted by fishingmedic

I'm gonna try d/l'ing this one from work, been having a hell of a time even getting android working again on my phone, regardless of which build I'm using. Even tried older builds that I moved off my card and keep getting reboots, SOD's, etc, hell half the time I'm getting errors saying the system is screwed before I can even do anything, so I've got no logs or anything to pull. I'm about to throw this freaking phone through a wall right now, except that winmo is still working fine! And I'm trying on my 6 month old 8G class 8 card, 4G class 2 and a brand spanking new 8G class 4, they're all doing the same thing, all reformatted, new builds, etc.

Dang guy. If you want, we can try to hash it out on IRC or gtalk or something... I was going to suggest trying a different card, but you've more than covered that.

[fishingmedic]

I may take you up on your offer, I'm gonna keep trying, reformat and put nothing else on there except for the build and go from there and see what happens. I'm starting to wonder if the phone has developed some sort of hardware issue, but like I said, winmo seems to be working ok. Let me try to get the new kernel d/l'd and go from there, but again, I may take you up on your offer soon!

[arrrghhh]

Originally Posted by fishingmedic

I may take you up on your offer, I'm gonna keep trying, reformat and put nothing else on there except for the build and go from there and see what happens. I'm starting to wonder if the phone has developed some sort of hardware issue, but like I said, winmo seems to be working ok. Let me try to get the new kernel d/l'd and go from there, but again, I may take you up on your offer soon!

np man, just shoot me a pm .

[fishingmedic]

Alright, just tried this again, put a brand new clean FRX04 build w/ the latest rootfs that was just released last night and this kernel, let it boot, and just sit for a few, at which time, without me touching it, it booted back to winmo. Before I do anything further (like run the freaking phone over with my truck...) do you want me to attempt to get a log on it or will one have not even been created as I'm not sure exactly how far the process went?

Edit: I changed a couple of things in the startup.txt and played around with it a bit and giving it another shot. Maybe I should try with the actual package first, then after it boots, go back to winmo, swap in the new rootfs and test kernel?

Edit part 2: Still reboots back to winmo and reboots back before I can get a log or anything. forget it, I just threw it at my neighbor, I'm going back to a freaking flip phone... lol. I'm gonna try booting just FRX04 out of the box and then make changes with rootfs and kernel.

So far so good with clean FRX04...

[ndno]

Originally Posted by fishingmedic

Alright, just tried this again, put a brand new clean FRX04 build w/ the latest rootfs that was just released last night and this kernel, let it boot, and just sit for a few, at which time, without me touching it, it booted back to winmo. Before I do anything further (like run the freaking phone over with my truck...) do you want me to attempt to get a log on it or will one have not even been created as I'm not sure exactly how far the process went?

Edit: I changed a couple of things in the startup.txt and played around with it a bit and giving it another shot. Maybe I should try with the actual package first, then after it boots, go back to winmo, swap in the new rootfs and test kernel?

Edit part 2: Still reboots back to winmo and reboots back before I can get a log or anything. forget it, I just threw it at my neighbor, I'm going back to a freaking flip phone... lol. I'm gonna try booting just FRX04 out of the box and then make changes with rootfs and kernel.

So far so good with clean FRX04...

Fish, seems like you have been getting a lot of resets to WinMo issue lately, with Tiad8's build and FRX04. Hmmm... I had that issue the first time I tried FRX04 with 1253 OC'ed on first boot but it works fine after the first boot. I'm currently using FRX04, with 2/9 rootfs, and this kernel OCed at 614Mhz and it's pretty solid. Got the panel 14 type in my dmesg. When my phone goes to sleep, I still have to press the button several times to really wake it up. I'm using an app called nolock because I can't stand the slider to unlock screen that occurs everytime my phone wakes up; saves me a couple precious seconds so I can use my phone right away .

arrrghhh, besides ADB, DroidExplorer or the other debugging methods you guys are using, is there a way we can set up a telnetd or sshd daemon with which we log into? The builtin terminal is good but the lack of some keys (>, |, tab, etc) makes it hard to play with (I guess I can use manekineko's rootfs with the added key functions).

[rpierce99]

Originally Posted by ndno

Fish, seems like you have been getting a lot of resets to WinMo issue lately, with Tiad8's build and FRX04. Hmmm... I had that issue the first time I tried FRX04 with 1253 OC'ed on first boot but it works fine after the first boot. I'm currently using FRX04, with 2/9 rootfs, and this kernel OCed at 614Mhz and it's pretty solid. Got the panel 14 type in my dmesg. When my phone goes to sleep, I still have to press the button several times to really wake it up. I'm using an app called nolock because I can't stand the slider to unlock screen that occurs everytime my phone wakes up; saves me a couple precious seconds so I can use my phone right away .

arrrghhh, besides ADB, DroidExplorer or the other debugging methods you guys are using, is there a way we can set up a telnetd or sshd daemon with which we log into? The builtin terminal is good but the lack of some keys (>, |, tab, etc) makes it hard to play with (I guess I can use manekineko's rootfs with the added key functions).

The most effective way to guarantee a good wake is to touch the screen after you've hit the power button and waiting about a second.

If you prefer the END=HOME button layout check out F22's ROOTFS over on XDA, it also adds in the missing keys for effectively running shell commands.

[ndno]

Originally Posted by rpierce99

The most effective way to guarantee a good wake is to touch the screen after you've hit the power button and waiting about a second.

If you prefer the END=HOME button layout check out F22's ROOTFS over on XDA, it also adds in the missing keys for effectively running shell commands.

Thanks, I'll keep that in mind. Does F22's rootfs have the system_server bug fix in it?

[arrrghhh]

Originally Posted by ndno

Thanks, I'll keep that in mind. Does F22's rootfs have the system_server bug fix in it?

Indeed it does, he just updated it last night.

There is ssh into the phone, search for 'dropbear'.

Plus, you can get a full-featured shell using adb... just need to enable it.

/bin/sh

should do it.