yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] sjabbie88:
Jeah they truly where..that`s why my kernel version is so far behind XD

Well, I`m installing the 1253 kernel directly then =D

THNX!
[Touch Pro2, Tilt 2 Android Development] skimike02:
Ah, that's probably it. Thanks. And I was calling them by their windows functions, but yes, those keys.
[Touch Pro2, Tilt 2 Android Development] Bld-:
Yes, I use that app also, but I haven't enabled the auto-kill function.

I'll try that.

Hm, I would like to try that also, can you link the kernel?

Thx
[Touch Pro2, Tilt 2 Android Development] arucard98:
Hey thanks! That worked perfectly! Did exactly as you said, and voila!

Now I'm having a seperate problem I'm finding no info on. Android boots up but does not prompt me to do any kind of setup like seen here:

http://www.youtube.com/watch?v=-nymxSmjL7E&feature=related

I can't seem to get anything to connect, no internet no phone signal.

Am I missing something dumb?
[Touch Pro2, Tilt 2 Android Development] dcmedic:
Question?????

Is anyone else having issues with the device freezing after stopping wifi-tether?
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
Sounds to me like you dont have force_cdma=1 or force_cdma=0 in your startup.txt in the /andboot folder you can open with any text editor. Just make sure you put it between the quotes " " with the other commands.
[Touch Pro2, Tilt 2 Android Development] arucard98:
It worked! Thanks alot!
[Touch Pro2, Tilt 2 Android Development] manekineko:
Yes, that's a known issue with the built-in wifi tethering on XDAndroid.

Must be an error in the userland, because wifi tethering with 3rd party programs works fine.
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
look in the stickies, its right there.

what I have notice is that after I installed ADVANCE TASK MANAGER/KILLER that's when the SOD started happening.

Do you guys think this app has something to do with it???:confused:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
It certainly could, Google has said up and down that in Froyo you shouldn't be using these apps as they can cause data loss and other problems.

Run vanilla (no apps installed other than what comes with it) and see if the issue persists.
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
Vanilla???
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I put what I meant by that in parentheses... did that not make sense?

No apps, other than what comes with FRX04.
[Touch Pro2, Tilt 2 Android Development] trusa1:
I use Advanced Task Killer, but without auto-kill function and haven't SOD.

Try to disable auto-kill function.
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
sorry, multitasking! working and reading the forums. :D

thanks a lot for the info.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
I have to admit I was skeptical about tiad8's suggestion that setting up the APN manually would fix the system_server bug. My phone previously would system_server lag 9 out of every 10 boots into Android, if not more. Since setting up the APN as he describes in his Froyo X thread, I've rebooted twice and haven't had the lag one time. I'm going to keep rebooting to make sure, but so far it's actually working.

Sorry for doubting you tiad :)

EDIT: 3 times now, no issues.

Just so others don't have to go digging for it, here are the APN instructions (SPRINT ONLY):

App drawer -> Settings -> Wireless & Networks -> Mobile Networks -> Access Point Names -> Press the Menu button (win key by default on mine) -> New APN

For the "Name" put "sprint" (no quotes on any of these)

For the "APN" put "#777"

For the "Username" put "Sprint"

Leave all other settings at their defaults.

Menu button (win key) again -> Save

Select the circle next to your new APN to select it as the default.

You are done.

Please, if you try this and it works or doesn't work post back here so we can prove either way whether this is the fix.

4th Boot: SYSTEM_SERVER - 86.5% Darn.

Maybe we can describe this as reducing the odds of getting the system_server bug, or I just got lucky 3 times in a row.

5th Boot: Good again. The only thing I can remember doing differently the 4th time was I attempted the slide to unlock before the phone had a signal from sprint. That may have been because signal acquisition was taking longer due to the system_server bug though, so I'm not sure which is the cause and which is the effect.
[Touch Pro2, Tilt 2 Android Development] coolwater22:
i know this is a noob question,but what is a "system_server bug" in sprint... is it when it doesnt want to connect or what?? again srry if it has been answered
[Touch Pro2, Tilt 2 Android Development] tennisfreak:
Is there a fix for the tilt 2 keyboard? i am so confused with the touch pro 2 keyboard
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Fix...? What's wrong with it?

system_server is a core process to Android, and sometimes it runs out of control. It will steal all of the processor cycles the phone's processor has to give, thus making the phone nearly unusable. I get it almost every time I boot, even with the correct APN info...
[Touch Pro2, Tilt 2 Android Development] tennisfreak:
I have the Tilt 2, but the system is registering the keyboard as the verizon touch pro 2 keyboard. So the numbers symbols most of the keys are wrong

Thanks for the reply though :)
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Sounds like someone needs to just compile a copy of system_server with -g and all debug symbols intact, then attach to it with gdb when one of these berserk cycles occurs, and get a stack trace of wth it's doing.
[Touch Pro2, Tilt 2 Android Development] sf49er:
Is the camera working/not working?

Sorry if this has been answered but 1200 pages is a hell of a lot to get through.

I have installed FRX04 and it runs great. Had a slight issue with network btu that was sorted out.

I can see the camera app and when I click on it the camera app starts, but it cant 'see' anything from the lens. Some of the threads outside of this indicate that people have the camera working to take photos (I want to try the barcode reader on it), but Im having trouble figuring out how.

Can anyone help?
[Touch Pro2, Tilt 2 Android Development] rcgators:
Verify your startup.txt has the right keyboard specifed. For the tilt2 it should be: physkeyboard=tilt2
[Touch Pro2, Tilt 2 Android Development] Qmaster11:
FAQ

Can you update de FAQ?

A lot of things are not right.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
That's unfortunate. Would still be nice to have a larger sample size of users to determine if it has any effect or if it is some sort of fluke for tiad & I.

EDIT: I just remembered that the same boot that I changed the APN settings I also disabled both location options. On a hunch I re-enabled both location options and rebooted. system_server bug struck me 2 times in a row. I'm rebooting now with both of them off to see if the bug goes away again.

1st Boot after turning location back off: no system_server lag. I'm going to try with just GPS. I'm wondering if it is a combination of APN + Network location.

After turning GPS back on: system_server lag is back.

After turning GPS back off: system_server lag is gone again.

After turning Network location on: system_server lag is back.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Interesting... I usually have both disabled since a) netloc doesn't work on CDMA and b) GPS enabled kills sleep.

I'll do some more testing with this and double-check my APN settings. You do seem to be on to something - I had a few boots with no system_server issues, it's just I've had several with the issue present. Like I said I need to go thru all my settings, build crap changes so fast for me sometimes I lose track :p
[Touch Pro2, Tilt 2 Android Development] rpierce99:
Yeah maybe not, last 3 boots all with all location options off have resulted in total system_server slowdown. Back to square 1 I guess, it was working so well for a while!

EDIT: BTW you should put together a tips & tricks of all the random stuff like this:

I've been lurking this thread for a long time, even lurking in other forums and threads for a while, and never knew those for sure. The netloc thing I was pretty sure of because of, well because of it not working - ever, but I still kept enabling them thinking maybe it was just something silly I was doing.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Something is looping in the RIL and just bringing the process to its knees I think... Our RIL code probably is not optimized, I'm really excited to hear what WisTilt2's radio monkey has to say about the code... Really hoping to get CDMA netloc fixed, and this system_server issue fixed - maybe even improve the radio drops ;).
[Touch Pro2, Tilt 2 Android Development] rpierce99:
Not optimized doesn't seem to match the symptoms. Based on the processor usage it seems more like a while(true) { //don't do anything, including sleep the processor, maybe it does something do something but it's not doing anything successfully enough to break out of the loop. } and based on how it happens (primarily at initial boot, seemingly randomized with a tendancy towards occuring) I'd guess it is something to do with network being unavailable when something tries to use data. But whatever loop it gets stuck in, making a call breaks out of it. I obviously haven't seen any of the code and could be way off base, but just based on symptoms it seems plausible. The only thing I really know is what top and strace tell me, which isn't much. IOCTL with one specific address over and over again. I don't even know what that is, haha.
[Touch Pro2, Tilt 2 Android Development] manekineko:
I maintain a thread like that on PPCGeeks:

http://forum.ppcgeeks.com/tp2-andro...-1-26-workaround-available-usb-tethering.html

It's sad, though, because even there no one ever reads it and the forums are swamped with people asking about the same non-working things over and ovver.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
Yeah that is an extremely comprehensive list. Thank you. I had never seen it.

EDIT: Wow this whole forum is basically duplicated over there on ppcgeeks. Interesting. I'll have to keep an eye on both from now on.
[Touch Pro2, Tilt 2 Android Development] coolwater22:
thnx arrrghhh you have been thanked for answering my question :)....

thnx to all the devs for their great work, keep it up
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ah, I meant 'not optimized' in the sense that no one has really taken a good hard look at the code in a while, as I don't think we have any RIL experts on the dev team. AFAIK, phh and MrPippy just ported dzo's RIL work on the Vogue. So it's not exactly copied and pasted from the Vogue, just copied, pasted and slightly modified :p. Basically getting it done when no one else is sure how to...

Either way, only good things can come from WisTilt2 letting his paid radio dev look at the RIL code...
[Touch Pro2, Tilt 2 Android Development] ryannathans:
I don't believe there is currently a keyboard layout for me, or I just can't seem to get it to work.

RHOD110
[Touch Pro2, Tilt 2 Android Development] geminix2:
That thread is a good idea.

Some might find it interesting that while the note about USB only working in debug mode is correct in that it's all one can 'turn on' on the phone the PC app "MyPhoneExplorer" works over USB (debug on) once one has an ADB driver, which can be had by installing PdaNet. Both install a client on the phone.

That gives one a fairly decent set of user tools like sync, contacts, calendar, file explorer, backup, etc. Oh, and you can access the 'internal' memory too.

It also works over WiFi.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
I think you'll find that is the model of your battery. Take the battery out, and have a look at the light grey text in the battery compartment, not the battery.

Hope that helps.
[Touch Pro2, Tilt 2 Android Development] leatherman:
SOD is killing me...HELP please

I'm having SOD alot, I mean ALOT, is there any way to get around it or a solution? I have gone throug the forum and read all the posts regarding the SOD, to put you in the picture, I have tried the following:

1- formatted my SD card long format and apdated the startup OTA and load fresh haret FRX04 from the rar.

2- put "pm.sleep_mode=2" with and without OC.

3- put "pm.sleep_mode=1,2" with OC.

and sometimes after I boot to android the mobile suddenly restart, any advice will be appreciated, thanks.

Edit1: I have just noticed that the "pm.sleep_mode" has changed automatically back to =2, I have no idea why?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You haven't tried a new kernel.

You haven't tried sleep_mode=1.

Assuming you have a newer kernel with bzo's PLL2 commits, you can use sleep_mode=1 while overclocking...

If you say things in the startup.txt are 'changing automatically' - are you using the startup utility that updates the kernel and rootfs...? If so, then you're changing it - with that app.
[Touch Pro2, Tilt 2 Android Development] manekineko:
Thanks for the support and the tip. I updated the section on USB to clarify about MyPhoneExplorer.
[Touch Pro2, Tilt 2 Android Development] leatherman:
Further question on same case

Thank you for your quick reply. As you said, I didn't try pm.sleep_mode=1, which I will do shortly. But execuse my ignorance, what do you mean by "bzo's PLL2"...?

For the startup utility, I used the one came with the XDANDROID rar file of the first page download link " http://sites.google.com/site/androidport/downloads " but before the first boot to Android I did an update OTA after running the startup utility which updates kernel and rootfs... here under is a copy of my startup.txt:

set ramsize 0x10000000

set ramaddr 0x10000000

set mtype 2292

set KERNEL zImage

set initrd initrd.gz

set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 rel_path=andboot north_am_dialing=0 force_cdma=0 pm.sleep_mode=2 acpuclock.oc_freq_khz=716800 hw3d.force=1 physkeyboard=rhod100_uk"

boot
[Touch Pro2, Tilt 2 Android Development] rpierce99:
The update utility doesn't provide updated kernels anymore, there was a service running that provided those updates, it is not running any longer. To run the newest kernels pick a kernel update thread (I'd recommend wistilt2s 1/30 kernel, great battery life), download the zImage and modules, and replace the zImage and modules you have currently in andboot with the new ones. The reason startup utility changed your pm.sleep_mode to 2 is because with it set to 1,2 it was invalid, basically android would just use whatever the default value of that setting is because it doesn't understand 1,2.

Long story short, update your kernel manually, set pm.sleep_mode to 1 manually, consider disabling overclock (remove acpuclock.oc_freq_khz=716800) because not all rhods can handle overclocks, and launch haret.exe itself instead of using the launcher.

If after all that you're still getting the SOD let us know.
[Touch Pro2, Tilt 2 Android Development] geminix2:
You're welcome. Just glad I could contribute something.

I noticed you also included DroidExplorer. Might be my lack of experience but I never could make it work on Vista x64. Nor could I get ADB working till someone (forgive my poor memory as to who) suggested using PdaNet. (The driver is all I use PdaNet for as I don't need tethering.)

The 32 bit verison of DroidExplorer might work since it isn't supposed to have the registry bug but I can't speak to that as it won't even try to install on a 64 bit machine.

Another note, it seems that here lately Android, on my Tilt2 anyway, crashes and (successfully) restarts if USB is plugged in during boot up.

(follow up)

Forget USB plugged in causing the reboots. FRX04 on my TIlt2 seems to be missbehaving more over time and now reboots whether USB is connected or not. Worse yet, last time I shut down it took three tries because the dern thing rebooted twice rather than turning off. Was about to pull the battery when it finally took.

Since I brought up DroidExplorer I ran a quick test with a Win7 32 bit machine and, while the install looked flawless, it could never find the phone despite Device Manager reporting 'Android Phone' (ADB) working properly. The 'DroidExplorer' driver also didn't work with MyPhoneExplorer.

Could very well be I'm doing something 'wrong' (improper plug sequence or whatever) but the only combination that worked during the admittedly quick and dirty test was MyPhoneExplorer with PdaNet.

Well shoot, it just dawned on me that I didn't uninstall the PdaNet and MyPhoneExplorer clients on the phone before testing so maybe they interfered with DroidExplorer.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
This is the light grey text under the battery.

Under the bluetooth logo and to the left of 5VDC.
[Touch Pro2, Tilt 2 Android Development] geminix2:
If I'm not mistaken that's an Australia Telstra version of the Touch Pro II: T7381

http://www.exeltek.com.au/htc-touch-pro-telstra-next-mobile-phone-t7381-australian-stock-unlocked-pro2-p-1787.html

Also New Zealand.

http://www.telecom.co.nz/documents/htc-touch-pro2.pdf

"Regulatory Agency Identifications

For regulatory identification purposes, your product is assigned a model number of RHOD110.

.

.

The Battery Pack has been assigned a model number of RHOD160."
[Touch Pro2, Tilt 2 Android Development] F22:
rhod110 keyboard

Thanks for posting the pics. Judging by that last pic, your rhod110's keyboard is identical to that of the rhod100_uk. I'll update my test rootfs with an entry for the 110 tomorrow and that will eventually make it's way into the official tree. Until then placing physkeyboard=rhod100_uk in your startup.txt will work just fine for you.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Oops. It was 160 I was thinking of, as the other poster pointed out. However, at least now you know to use rhod100.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Rhod100 so you could be getting SOD because you have the AUO (?) screen that most rhod100s have but none of the other models have. In which case you'll be better off with an older kernel (November 24th) until the issues have been fixed with our panel.
[Touch Pro2, Tilt 2 Android Development] Bld-:
Concerning phone hangs during standby:

I've been testing with several settings, but unfortunatelly my phone keeps hanging at random times during standby.

So I can't get it out of standby and have to soft-reset the phone each time (happens >1 times a day).

I've tried without any advanced taskkiller installed.

I've tried with Advanced Task killer installed (Auto kill on (half hour) and off).

My Startup.txt cmdline looks like this:

lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 relpath=andboot north_am_dialing=0 force_cdma=0 hw3dforce=1 pm.sleep_mode=1 physkeyboard=rhod100_uk msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave"

Could hw3dforce be the cause?

Anyone else got idea's? :(
[Touch Pro2, Tilt 2 Android Development] Eodun:
I think pmem.extra is deprecated in the current FRX04, try removing it. Also, you could remove "msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave" if you don't have the "waiting for SD card" without it.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
I have been looking for the individual parts and putting it together myself but I just can't seem to get it to work.

I would really appreciate it if someone could bring all the 'parts' together into one package for me and my rhod100. Every android 'combo' I try just wont boot, or keeps crashing (freezes inuse or in standby) once booted.
[Touch Pro2, Tilt 2 Android Development] Bld-:
Yeh, I need the last two parameters else he won't boot.

I'll try the pmem.extra.

Hopefully this will work.

Thx
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
pmem.extra is deprecated, but it won't cause the SoD... I've highlighted the deprecated commands:

lcd.density=240 [b][color=red]msmts_calib=0x9f.0x39a.0x35c.0x78[/b][/color] msmvkeyb_toggle=off [b][color=red]pmem.extra=1[/b][/color] gsensor_axis=2,1,3 relpath=andboot [color=blue]north_am_dialing=0 force_cdma=0[/color] hw3dforce=1 pm.sleep_mode=1 physkeyboard=rhod100_uk msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave"

The ones in blue you have set to =0, so there's no reason to include them. They can be safely removed as well.

We're trying to track down the reason for the SoD, but we haven't been able to figure it out. That last_kmsg after a soft reset may be useful, you just need to use adb to pull it.

cat /proc/last_kmsg
[Touch Pro2, Tilt 2 Android Development] tiad8:
Ok, guys

i'm going to start atacking this server bug today.

First i will try my settings, on frx03 and frx04. I made have to look deeper into the system.ext2

lets see what happen today. I will let you gusy know today

thanks
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hey man, hop on IRC sometime. We've been hashing this out for a while, the theory is RIL - something is looping and making a phone call breaks the loop...
[Touch Pro2, Tilt 2 Android Development] tiad8:
Thanks. When I get home I'm going to boot frx04. I was writing on a Notepad some info on this. It's a very good possibility that I will fix this today. I'll let you know

FROYO X/SPRINT TOUCH PRO 2/RHOD
[Touch Pro2, Tilt 2 Android Development] vnes1984:
I love the optimism Tiad!
[Touch Pro2, Tilt 2 Android Development] AkumaX:
hehe ya, fix it today, then do bluetooth tomorrow, then by the end of the week, you'll have NAND flashing all figured out and finished :D

no but really, thank you and every other dev working on this!
[Touch Pro2, Tilt 2 Android Development] leatherman:
I have no signal...can't get it back

Thank youfor your reply, I've taken your advice but I have full formatted my SD card in order to make the test result clear, got a fresh transfer of the FRX04 and dwnloaded the "wistilt2s 1/30 kernel" as you recommended and replaced the zimage and module manually, of course didn't use the startup utility and no OC..after booting up, I can't get a signal, I tried to switch the airplane mode on/off but no use, btw, I'm a GSM user....kindly your advice to get me back on track..:p thanks.

Edit1: I've just checked my startup.txt file and I found the CDMA mode=1 and I'm a GSM user so I just changed it to 0 and TaDa, I'm back on track, I will post any note I will observe..thanks to all..
[Touch Pro2, Tilt 2 Android Development] tiad8:
ok, guys first boot with my setting is a success.

I change some libs driver. etc files and xml files

now let's see if I can get that server bug. so far it looks great. very fast, very smooth.

edit.. wuuuuuaaaaooo. this baby can fly now.

I will continue testing. I will let you guys know

thanks
[Touch Pro2, Tilt 2 Android Development] slapshot30:
I am also having SOD issues with my tilt2, frx04, 1/29 wistilt2 kernal. It only happens when sleeping for long periods of time (overnight charging, in my pocket for 5+ hours). Tonight I will switch to the 1/30 kernal and see if my phone wakes in the morning.
[Touch Pro2, Tilt 2 Android Development] tiad8:
update frx04

FIRST BOOT

I have completed, my first boot settings. it was perfect. NO LAGG, NO FC, NO CONNECTION ISSUES, ALL APPS OPEN WITH NO ISSUES. PLUS THE NEW MARKET LOOKS GREAT. GPS, CAMERA, 3D, GRALLOC. THEY ALL WORK.

SECOND BOOT. IT COMING. SO STAY TUNE
[Touch Pro2, Tilt 2 Android Development] tiad8:
update frx04

SECOND BOOT. IT A SUCCESS

WHAT I HAVE TEST IT SO FAR

GPS, CAMERA TOOK 7 PICTURES WORKS GREAT, 3D NEOCORE 19.9-20.2 NO O/C, QUADRANT 631 NO O/C.TEXTING, VOICE, NEW MARKET FAST, ALL APPS WORKS, AND STILL NO LAGS, NO FC, WIFI WORKS, DATA, 3G WORKS,

1- FOR THE 3D DRIVER. ADD IT THE ONE THAT SAY OPENGLE 1.1 AND GRALLOC FROM ACL.

2- FOR THE CAMERA. I ADD 5 CAMERA DRIVERS TO THE SYSTEM/LIB.

3- FOR APN. EVERYONE HAVE TO SET IT UP MANUALLY.

4- I ADD IT A RIL DRIVER TO SYSTEM/LIB.

5- I ADD IT MORE XML TO SYSTEM/ETC/PERMISSION

6- I TOOK OUT A FEW APPS FROM SYSTEM/APP

SO THE 3D STUFF AND THE CAMERA STUFF. NEVER GETS IN EACH OTHERS WAY. TO GET FULL PERFORMANCE.

KERNELS. THE GOOD THINGS ABOUT THIS. YOU CAN USE ANY KERNELS UPDATE.

I WILL TAKE THIS BABY FOR SPIN TONIGHT AND TOMORROW. JUST MAKE SURE.

THANKS