[BUILD] **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes

[arrrghhh]

Originally Posted by jamesgoof

I'm having trouble getting past the Linux boot sequence. It freezes at "Unable to handle kernel NULL pointer dereference at virtual address 00000014". I have the Rhod400. I placed all files in a Androids/TP2Ref just like arrrghhh did. I duplicated his setup to try to resolve the issue. Does anyone know what the issue would be and how I can fix it. Thank you.

I'm assuming you have the rel_path= statement in the startup.txt after the set cmdline in between the quotes? One space between each command?

I don't have enough to go off of just that virtual address error, there must be more. Perhaps a format of the SD is in order? Full format, FAT32 - the tool I recommend in the HP tool, link in the first post. Don't use any built-in Windows or WinMo tools to format...

[jamesgoof]

Originally Posted by arrrghhh

I'm assuming you have the rel_path= statement in the startup.txt after the set cmdline in between the quotes? One space between each command?

I don't have enough to go off of just that virtual address error, there must be more. Perhaps a format of the SD is in order? Full format, FAT32 - the tool I recommend in the HP tool, link in the first post. Don't use any built-in Windows or WinMo tools to format...

Yes I have the atatement in the startup.txt and I dbl checked and verified that there is only one space between each command. I have been using the FRX04 build and it works ok. I completely removed it to eliminate conflicts.

I know you dont have much to go off of, I will try the Full format using the tool you have suggested.

Thank you for the help I will let you know what I find out.

Here is what my startup.txt file reads incase I am missing something;

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 force_cdma=1 pm.sleep_mode=1 rel_path=Androids/TP2Ref physkeyboard=rhod400"
boot

[arrrghhh]

Originally Posted by jamesgoof

Yes I have the atatement in the startup.txt and I dbl checked and verified that there is only one space between each command. I have been using the FRX04 build and it works ok. I completely removed it to eliminate conflicts.

I know you dont have much to go off of, I will try the Full format using the tool you have suggested.

Thank you for the help I will let you know what I find out.

Here is what my startup.txt file reads incase I am missing something;

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 force_cdma=1 pm.sleep_mode=1 rel_path=Androids/TP2Ref physkeyboard=rhod400"
boot

Nothing jumping out of that. Perhaps just download the full bundle and start over? Not sure what's wrong...

[trhinehart]

This has probably already been mentioned before but I wanted to share an observation and find out if there is a possible solution. I'm currently running FRX06 with the latest wistilt2 test kernel (but what I'm experiencing is happening with other kernels as well.) After I boot into Android my phone will go into deep sleep (solid green) very quickly (I'm talking 1 second.) I can surf the web run programs turn it on and off and it will continue to go into deep sleep very fast. However, as soon as the phone is used to either make or recieve a call then it will no longer go into deep sleep very fast. It will always try to sleep (blinking green) for about 30 seconds then go into deep sleep (solid green.) There is nothing I can do to make it sleep any faster once the phone has been used for a call except for reboot. The reason this is a pain is because I use a holster with a magnetic flap. Unless the phone is in deep sleep the magnets will turn the phone on when I try to put it in the holster so I end up having to hold the phone for 30 seconds every time I turn it off before I can put it away. Any ideas?

btw, I am really enjoying Android on my TP2 and the wealth of information that can be found on the forums in great.

Thank

[rpierce99]

Originally Posted by trhinehart

This has probably already been mentioned before but I wanted to share an observation and find out if there is a possible solution. I'm currently running FRX06 with the latest wistilt2 test kernel (but what I'm experiencing is happening with other kernels as well.) After I boot into Android my phone will go into deep sleep (solid green) very quickly (I'm talking 1 second.) I can surf the web run programs turn it on and off and it will continue to go into deep sleep very fast. However, as soon as the phone is used to either make or recieve a call then it will no longer go into deep sleep very fast. It will always try to sleep (blinking green) for about 30 seconds then go into deep sleep (solid green.) There is nothing I can do to make it sleep any faster once the phone has been used for a call except for reboot. The reason this is a pain is because I use a holster with a magnetic flap. Unless the phone is in deep sleep the magnets will turn the phone on when I try to put it in the holster so I end up having to hold the phone for 30 seconds every time I turn it off before I can put it away. Any ideas?

btw, I am really enjoying Android on my TP2 and the wealth of information that can be found on the forums in great.

Thank

highlandsun's test ril over on xda has resolved this issue, but by using a test ril and not waiting for the changes to go mainline, you sign up for other bugs that may pop up and helping troubleshoot them.
http://forum.xda-developers.com/show....php?t=1009112

[arrrghhh]

Originally Posted by rpierce99

highlandsun's test ril over on xda has resolved this issue, but by using a test ril and not waiting for the changes to go mainline, you sign up for other bugs that may pop up and helping troubleshoot them.
[TESTING] New more stable ril - xda-developers

I can attest to this test RIL - 30s sleep issue is resolved.

RIL seems very promising, I've been running it for about a day now. Just a ton of changes all at once, and there will be more to come - lots of stuff was (and still is) missing for CDMA.

[trhinehart]

Originally Posted by arrrghhh

I can attest to this test RIL - 30s sleep issue is resolved.

RIL seems very promising, I've been running it for about a day now. Just a ton of changes all at once, and there will be more to come - lots of stuff was (and still is) missing for CDMA.

Thanks to both of you for replying. It's getting so close, I can hardly wait for it all to come together. I thought about trying the test RIL but I think I'll hold off a little longer.

[ashthrey]

i have everything downloaded, what rhod do I use? I have a sprint touch pro 2. I used rhod400 but when i start android os i boot up in airplane mode. cant get to connect?

[arrrghhh]

Originally Posted by ashthrey

i have everything downloaded, what rhod do I use? I have a sprint touch pro 2. I used rhod400 but when i start android os i boot up in airplane mode. cant get to connect?

RHOD400 is Sprint's TP2. If you're unsure, read the FAQ, it details how to figure out which phone you have for sure.

The important piece is the force_cdma= value - needs to be 1 for CDMA.

[Rob6722]

Is there an android app that I can download to reboot my TP2 so I can easily reboot the phone back into my Windows Mobile system?