[CAB] GSM&CDMA Project Android Port and Startup Utility [01/23] FRX04 Reference!

[Opranger]

I have been lurking for a month or so now and have successfully been using the FRX03 reference build as well as the FRX04 build. I also have used Tiad8's Froyo X builds. In all of these I notice that after some period of time, usually about an hour, all the signal strength bars go away and I can not place a call or receive one, no texting either. I turn on airplane mode and then turn airplane mode back off and signal is back everything works fine. One thing a different than most everybody else is I do not have the data package enabled on this phone. This is a Sprint Touch Pro 2 Win Mo 6.5. Once I'm satisfied that everything work well I plan on turning data on and making this my primary phone. Thanks for any help.

[fishingmedic]

Originally Posted by ndno

OK, I got an all-in-one FRX04 package with the 1253 kernel OCed at 710Mhz if anyone wants to try out. It resides in the "andboot.frx04" folder and is setup based on that folder so don't rename it. Here's the link: andboot.frx04.kernel1253.oc.camera.7z

With findings and hints from Tiad8 and manekineko, I finally got it to work with fast speed and without the sluggishness and FCs. The default APN xml enclosed in the FRX04 system.ext2 seems to have settings (at least for Sprint) that is causing the sluggishness after booting up; I edited that xml file for Sprint to set the APN name to "sprint" and APN to "#777" and it's no longer sluggish nor getting FCs after booting up. For Verizon and other carriers, if it's sluggish, do the voicemail dialing trick and go change the APN settings (you can search Tiad8's threads for APN settings to use for your carrier) to get rid of the sluggishness. Here are the simple instructions for the package I uploaded:

1. Download andboot.frx04.kernel1253.oc.camera.7z to temporary folder on your PC
2. Extract it; it will contain the folder "andboot.frx04"
3. Copy the "andboot.frx04" folder to your SD card
4. In WinMo, navigate to the "andboot.frx04" folder and run haret.exe
5. That's it, if you're on Sprint, the APN is already set to the values I described above and you "shouldn't" get any sluggishness. Be patient on the first boot and let it settle before attempting to use it.

UPDATE: I just added viruscrazy's 01/23/2011 latest test camera kernel/library to the all-in-one package. It's not active at all but if you want to try it (remember this is just a test kernel so it won't be as fast or stable as the 1253 kernel above), just follow these instructions:

1. Do the setup above first to get everything stable and solid
2. Boot back into WinMo and use Total Commander to go to the "andboot.frx04" folder and do the following:
   • Rename startup.txt to startup.1253.txt
   • Rename startup.camera.txt to startup.txt
   • Rename conf/froyo.user.conf to conf/froyo.user.conf.1253
   • Rename conf/froyo.user.conf.camera to conf/froyo.user.conf
3. Run haret.exe under "andboot.frx04" folder and you now have camera capability (use the Vignette software)

@Tiad8, I borrowed a few APKs (Vignette, TitaniumBackup, Angry Birds) from one of your system.ext2. Hope you don't mind

This package is not as fast as the Jan.12.2011 Froyo X distribution by Tiad8 but it's almost there and is pure FRX04 based (except for a couple of very minor settings change - a change in build.prop mentioned by manekineko for speed, a Sprint entry change in the APN xml to resolve the sluggishness problem). It's pretty stable and responsive.

NOTE: Again, the package is tailored for Sprint so adjust the STARTUP.TXT for your carrier.

ndno, there are two zimages in your package just inside the folder, along with two modules. Are we to leave them both in there when we boot???

[ndno]

Originally Posted by fishingmedic

ndno, there are two zimages in your package just inside the folder, along with two modules. Are we to leave them both in there when we boot???

fish, it's very simple. Those were left there as intended. Just extract, copy to your SD card, and boot as is (I mentioned that in the first section), it will boot with the 1253 kernel, which is the latest stable kernel (no camera). Do your normal setup (you don't need to touch the APN settings for Sprint, it's already there, I tweaked them to prevent the sluggishness and FCs).

If you want to use the camera capability, follow the directions in the second section (UPDATE bold part) to rename the STARTUP.TXT and froyo.user.conf files and you will boot up with viruscrazy latest camera kernel/library. That's it.

Don't worry, they can both reside in the same folder. That the reason I have 2 STARTUP.TXT files, one for the 1253 kernel (just references zImage) and one for the camera kernel (which references zImage.camera). Like I say, just do the steps in the first set of instructions with the andboot.frx04 folder as is to get stuff going; then if you want to use the camera, follow the renaming steps in the second section to swap to the camera kernel.

[arrrghhh]

Originally Posted by ndno

OK, I got an all-in-one FRX04 package with the 1253 kernel OCed at 710Mhz if anyone wants to try out.

Holy cow. If you fixed the system_server issue because of an incorrect APN... that's amazing.

I need to test this, but of course my work won't let me click on that multiupload link... oy. Stupid proxy, need to find a good way around it!

[ndno]

Originally Posted by arrrghhh

Holy cow. If you fixed the system_server issue because of an incorrect APN... that's amazing.

I need to test this, but of course my work won't let me click on that multiupload link... oy. Stupid proxy, need to find a good way around it!

Hey arrrghhh, not sure if that "really fixes it" but it seems to work (like the voicmail dialing trick); I also let my phone sit for a couple minutes after booting up before I use it. If FRX04 is already on your TP2 and you're getting FCs/sluggishness after booting up (even after waiting several minutes), try editing your sprint APN settings as follows:

Name: Sprint
APN: #777
Proxy, Port, Username,Password, Server, MMS proxy, MMS port: leave all blank
MCC: 310
MNC: 995
Authenication type, APN type: leave blank

I'm probably just guessing it works but it does seem to be no longer sluggish. It seems like some process is hogging all the CPU after bootup; Tiad8 thinks it may be related to the APN settings.
I did that and am no longer getting sluggishness/FCs after booting up and waiting for a couple minutes.

[fishingmedic]

Originally Posted by ndno

fish, it's very simple. Those were left there as intended. Just extract, copy to your SD card, and boot as is (I mentioned that in the first section), it will boot with the 1253 kernel, which is the latest stable kernel (no camera). Do your normal setup (you don't need to touch the APN settings for Sprint, it's already there, I tweaked them to prevent the sluggishness and FCs).

If you want to use the camera capability, follow the directions in the second section (UPDATE bold part) to rename the STARTUP.TXT and froyo.user.conf files and you will boot up with viruscrazy latest camera kernel/library. That's it.

Don't worry, they can both reside in the same folder. That the reason I have 2 STARTUP.TXT files, one for the 1253 kernel (just references zImage) and one for the camera kernel (which references zImage.camera). Like I say, just do the steps in the first set of instructions with the andboot.frx04 folder as is to get stuff going; then if you want to use the camera, follow the renaming steps in the second section to swap to the camera kernel.

Thanks much bud, that's what I assumed knowing how thorough you are with your stuff, so that's exactly what I did. It was a little sluggish which is why I asked, but I'll keep playing around with it. Thanks again for putting it together (Seeing I haven't a clue how to do that stuff!!!).

Originally Posted by arrrghhh

Holy cow. If you fixed the system_server issue because of an incorrect APN... that's amazing.

I need to test this, but of course my work won't let me click on that multiupload link... oy. Stupid proxy, need to find a good way around it!

Want me to upload it to dropbox?

[arrrghhh]

Originally Posted by fishingmedic

Want me to upload it to dropbox?

Nah, they block that too. We have an external comcast connection for vendors, I'll just hop on that real quick.

[ndno]

Originally Posted by fishingmedic

Thanks much bud, that's what I assumed knowing how thorough you are with your stuff, so that's exactly what I did. It was a little sluggish which is why I asked, but I'll keep playing around with it. Thanks again for putting it together (Seeing I haven't a clue how to do that stuff!!!).

I guess the sluggishness didn't go away I guess the APN edit didn't fix it. It worked fine on mine. The only time I may get sluggishness/FCs now if I try to use it immediately after booting up. If I wait a few minutes, it's fine. Before the APN change, it's sluggish/has FC's regardless of how long I wait. Remember, try letting your phone sit for a few minutes after you see the home screen before attempting to use it.

fish, to get rid of the sluggishness, do arrrghhh's infamous voicemail dialing trick; just dial your voicemail, hangup, and the sluggishness (even FCs) will disappear. Works all the time.

[ndno]

OK, I take it back. I tried reboot a few times and, like fishingmedic said, it's still sluggish after booting up; I'm not getting FCs though. So I guess the voicemail dialing trick will have to do for now. I wonder what Tiad8's has in his 1.12.2011 that gets rid of the sluggishness/FCs.

[arrrghhh]

Originally Posted by ndno

OK, I take it back. I tried reboot a few times and, like fishingmedic said, it's still sluggish after booting up; I'm not getting FCs though. So I guess the voicemail dialing trick will have to do for now. I wonder what Tiad8's has in his 1.12.2011 that gets rid of the sluggishness/FCs.

Let's be more methodical about this. adb into the phone as soon as you can and look at top to see what the proc is doing.

On my first boot, system_server was not an issue - which is great. However, a couple of other processes were hogging most of the phone's resources - [mmcqd] and a media process. This was my first boot of your build however. Going for #2 now...

I do think you're onto something - WisTilt2 seems to think something is looping in the RIL, so a bad APN would be along those lines.

Bah, second boot system_server is pegging. Oh well, it was a nice thought.