yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] CosmicBlue2000:
Sure, but I changed it already some time ago and after running fine, I deleted the backup.

If I had those values you have and all apps i want were downloadable, I had written nothing. But there weren't after a fresh install of GBX0C. That's why I'm curious.

I can wipe my all set up and well running GBX0C for you, only to look at the stock build.prop, if you want or if you don't believe me.

We are looking at the same thing and believe me when I say, the values in build.prop were different to yours before I changed them.

---------- Post added at 11:09 PM ---------- Previous post was at 11:06 PM ----------

In most cases it's related to model, manufacturer, device, name...as I said before, those values with ro.product in front. Only for few apps you have to change more.

But I don't know about chrome.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
If you have specific problem, and have found a solution then feel free to post that info. Perhaps someone else can make use of the info. The info I have is from GBX0*, and works just fine for me. I don't have any personal interest vested in what you put into your build prop, and I have no way to change the one info in the hosted here.
[Touch Pro2, Tilt 2 Android Development] latinohot:
nope, it didn't work I changed it to 200 and then 220 but it didn't work,

got to say that 220 looks rather good on the screen
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Might try 210, or 240.
[Touch Pro2, Tilt 2 Android Development] CosmicBlue2000:
Hehe, a specific problem? Ever searched for "Incompatible device google play" with Google? It's not XDA related, it's Googles stupid ways to restrict certain apps to certain devices. And there are as many solutions to that "problem", I just used one of them and only one of hunderts possible devices, that could be faked by changing ro.product.*

I have no problem with changing them after installing a nre XDA release. As I said, I just wanted to know, why these values were set up the way I found them.

As you have other values...perhaps you have another Rhod? Rhod400 perhaps? I'm running on a Rhod100de. Is build.prop created on first boot? Perhaps that's why we have different values. I don't know.

I don't meant to say those values have to be set up specific, I don't care if someone has named his Tilt2 "Galaxy S2", "OneX", "Rhodium" or "XDA".

Who am I to dictate what has to be in that file?

I just wanted to know...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Not in this case. The Chrome Browser app only works on ICS+...

http://en.wikipedia.org/wiki/Google_Chrome_for_Android
[Touch Pro2, Tilt 2 Android Development] latinohot:
Yeah I was reading that a few days back, thanks
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Dolphin Browser is very Chrome-like, and Dolphin Mini works pretty well on the Rhodium.
[Touch Pro2, Tilt 2 Android Development] pauldow:
Private Text Messages Going Out As Public Tweets

Hi. I've got a weird one. I've been using this build, but have still had to go back to Win 6.5 when I need better speed or reliability. The biggest problem I have is that when I reply to, or create, a text message, it gets sent as a Twitter message; not a private message. I didn't see any other comment about this behavior, so I was wondering is there's an Android setting I don't have correct.

It's a good thing I'm not Ashton Kutcher with a million followers, but it's still something I have to watch out for.

Thanks for all the work on keeping this phone alive,

Paul
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What the...? Really?

What app are you using to send texts? The built-in messaging app or something else?

Do you have Twitter set as an account in "Accounts & Sync"? I don't really use Twitter, so I have no clue how this could get tangled with the built-in messaging app, other than Accounts & Sync...
[Touch Pro2, Tilt 2 Android Development] pauldow:
That's funny. "What the...?" was the exact thing I said when I saw the message details saying they were being sent to Twitter. I am using the built-in messaging application.

Thanks for pointing me to Accounts & Settings. I deleted, and then recreated the account for Twitter; and it seems to be working fine now.

Einstein's definition of insanity doesn't apply to computers. Things do change when doing the exact same thing over again.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm. Strange that happened, but glad it's resolved. I didn't realize Twitter integrated to that... ahem... level?
[Touch Pro2, Tilt 2 Android Development] baikal2:
I have a RHOD400 (Sprint) and have been trying to install GBX0C on my phone. I have followed all the steps given in the first post. The phone goes through the boot process and comes upto the initial screen of GB and then the phone goes back into WinMo.

More particularly, there is no signal initially . Then the phone locks a signal and then the 3G symbol shows up and after a few(1 or 2) seconds the phone crashes reboots back into Winmo.

Could anyone help with whats going on. Not even sure how to get Logs when the phone reboots back into WinMo so quickly. The phone was running Froyo previously.

Would definitely appreciate some help. I have tried other kernels and they also seem to have the same behavior. I have tried 3 other cards without any luck.

TIA
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Did you full format the sd card with the hp tool? Did you try another sd card? Did you use the correct startup.txt file?

Did you use a new data file? Did you try re-downloading the install files?

Maybe you should try the nand GBX.

http://xdaforums.com/showthread.php?t=1965459
[Touch Pro2, Tilt 2 Android Development] baikal2:
Thanks for the quick response. I have tried everything you suggested before asking for help. Is there anything else I can do to figure out whats going on. I would not prefer trying to use NAND GBX yet at this time.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
In the future is helpful if you list everything you have tried. Sadly many of us lack physic powers.

Have you tried froyo again to see if it still works?

Maybe your phone's card read is on the blink.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm wondering if FroYo works as well.

Also, baikal2, which kernels have you tried? You said you have tried many, but which ones?

If FroYo works, then we know your hardware is at least OK. If you made it all the way to the lock screen, that's a pretty good sign... Perhaps remove the SIM card? Especially if you're not using it, remove it.
[Touch Pro2, Tilt 2 Android Development] baikal2:
Froyo is working good. I reinstalled Froyo and it is working swell. I tried kernels 3.0.18 and 3.3.8 and they exhibit the same behaviour (Once the 3G symbol comes on,the phone reboots back into WinMo). I have tried 3 different SD cards (all Formatted with the HP tool) and ended up with similar results.

I have been able to install GB on another TP2 and that is working well. I have tried using the same SD card on the problematic TP2 ,but it reboots back into WinMo.

Have tried re-downloading the files from the OP,without much success. Also tried booting without the SIM card. Nothing changed.

The phone goes all the way to the lock screen. Once I get there, I get the " com.android.phone closed...." message. once I click OK on it ,the

phone starts to acuire the cell signal. the signal bars light up , the 3G signal symbol lights up and the phone reboots into WinMo.

Please let me know if the signature seems familiar or If I can do anything else to get it to work.

TIA

Also booting into Android after turning off radio(Airplane Mode) in WinMo
[Touch Pro2, Tilt 2 Android Development] wizardknight:
If I assume that both phones are using the same radio software, and if the same sd card works in one phone but not another, and they are the same make of phone, I would have to guess that there is something wrong with the phone giving you issues. Perhaps you have a lemon.
[Touch Pro2, Tilt 2 Android Development] baikal2:
I was kinda coming to the same conclusion. The phones are the same RHOD 400`s. The only difference I can make between them is the ROM version. The problematic one is 1.21.651.3 , while the working one is 1.26.651.4. Not even sure if there is anything to be had from that.

Is there any way to grab logs as the phone is booting up ,maybe giving us a clue as to what is causing the phone to reboot.

---------- Post added at 05:35 AM ---------- Previous post was at 05:32 AM ----------

I probably wouldnt go so far as to call it a lemon. The phone is a working phone on the Winmo side and was working on FRX07. Not sure what is causing to break on GBX.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Load the newest stock rom, and it should reload the radio too.

If the hardware is identical and the rom is different, the rom must be the source of your issues. Assuming that the phone is not a lemon of course.

Good luck.
[Touch Pro2, Tilt 2 Android Development] baikal2:
Flashed the latest Verizon radio(2.37) and that seems to have fixed the problem.
[Touch Pro2, Tilt 2 Android Development] bla0258:
On my HTC rohdium 100 Camera don´t work why?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Are you using the provided .27 kernel?

If yes, then update your kernel please. There are a few to choose from.
[Touch Pro2, Tilt 2 Android Development] imeio:
Hi, the last update was in May ? there is XDANdroid of ice crean 4.0 ?

thanks.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Yes

No.
[Touch Pro2, Tilt 2 Android Development] Johnsmith41junk:
got a quick question

can you link me to a

working

android nand install for the verizon htc touch pro (raph500)? i cant find it anywhere, and search gives me results for touch pro 2 nand nbhs. unless i can use a rhodimg on a touch pro 1...? i dont want to try, until you tell me it might work. and can you PM me? im afraid i dont spend all the time on the forums, and PM will email me, so i can get on when i get the answer. thanks!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This is the Touch Pro2 / RHOD / Rhodium section.

You want the Touch Pro1 / RAPH / Raphael section. Those folks can't flash NAND - Android can't be flashed to that device (no one has built the framework).

Regardless, this thread is for SD, not NAND. It's also for RHOD, not RAPH, so please don't derail this old thread...
[Touch Pro2, Tilt 2 Android Development] crownvn:
I don't know why my phone off the sound (all phone coming & go out. test the sound SMS, ring tone) although I increased

volume to max. level .The sound 's working normally in WM and hearing sound when it 's booting at begin adroid.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Are you using the correct startup txt file?

Did you copy the cvs files?

What troubleshooting have you done?
[Touch Pro2, Tilt 2 Android Development] crownvn:
Thks for your infor,

I had done and fixed it.(re-do from sep1 to end as guide at 1st post )

now it 's running good with sound.:laugh:
[Touch Pro2, Tilt 2 Android Development] jacktackle:
is it taking like 50 minutes to 1 hour for the first boot? after reading and extracting all the files in linux mode?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Uhm, is this a question?

It should only take about 10 minutes to boot. If it's taking longer, there's something wrong - either you didn't place EVERYTHING at the root of the SD, or you placed everything in a folder and didn't adjust rel_path.

Please see the FRX07.1 thread for better directions. They're basically identical directions, the only difference in the setup is the CSV step for GBX.
[Touch Pro2, Tilt 2 Android Development] xmarkom:
working failed

i copied this rom on sd card.

everything is fine, calibration, calls, wifi,... but everytime when i enter main menu it reboots and i have to copy all files again after formating sd card.

where is market?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Everytime you enter main menu it reboots...? I'm not sure what you mean. Reboots within Android - back to the XDAndroid splash screen, or reboots back to WinMo? Tis a strange behavior, all I know is the phone takes a while to "settle". What I mean by this is the first time you install Android - literally, let the phone sit for a while. As in, you see the lock screen - you probably have another 10-15 minutes before it's done "thinking". Especially when you first configure a sync account, I have had that create the reboots-within-Android effect.

The Market *should* be there - sometimes it doesn't show up, I never really figured out why. Usually after a reboot (back to WinMo, then back to Android) it will show up.

If you don't blow everything away and let it settle I think it will work much better for you.
[Touch Pro2, Tilt 2 Android Development] xmarkom:
I installed this version and also NAND version and everytimes i connect to a wireless network it goes to reboot loop and nothing i can do except installing other ROM, for anything else is ok.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So glad you posted this in every thread with very little info. Some threads you gave no info other than 'reboot loop', and others you at least mention it's related to wifi...

At any rate, there's a few things you can try. First, did you read the FAQ? There's a few trick's there for wifi. You might need to do the wifi-nvram.txt trick...

But, your issue also might be more serious. Can you describe the reboot loop? As in, does it reboot within Android or does it reboot back to WinMo and then you have to start HaRET to get back to Android?

Also, you state "nothing I can do except installing other ROM" - so that means to me "if I install something else it works" - is that true, or not? Has wifi EVER worked for you in Android?

Have you tried different kernels? Any other troubleshooting steps you've performed?

Thanks.
[Touch Pro2, Tilt 2 Android Development] xmarkom:
i provide answers in other section.

yes, wifi connecting work on every other rom except this one (xandroid and nand).

that you ve mentioned isnt a solution. my wifi works that moment i connect to it but phone reboots after going back to home screen (after connecting)
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Putting the answers in another thread for the questions in this one is an amazingly bad idea.

How many roms are you trying to install at the same time?

Pick one, and stick with it till it works. Or better yet use WM.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Please re-read my post and try answering my questions.

Otherwise, I guess you should just use WinMo. I hear it's made for the device.
[Touch Pro2, Tilt 2 Android Development] sera:
Proximity sensor problem

I think I am having a problem with the proximity sensor (sprint tp2). When I place or answer an incoming call the screen turns off. It can not be turned back on. Pressing the power button during the call will not turn it back on. Even after the call ends (other party hangs up) screen still can not be turned on by pressing the power button. Sliding the keyboard will turn the screen on in-call or after call. Power button will turn on the screen as expected until the next call is made or answered. Is there a way to force screen on power button?

I don't see this in WinMo but I have noticed that each time I make a call while phone is in upright position the screen will turnoff for a second then it comes back on.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Sometimes the prox sensor is a little finnicky...

Can you test it? There's an app in the Play store called AndroSensor. Should report prox - I think it says near / far or perhaps a distance?

On my new phone, it just shows 2 distances - basically 1 near, 1 far. When it senses something near, screen should turn off. Senses something far, on. But only in call...

So in WinMo, does the prox sensor work as expected in call?
[Touch Pro2, Tilt 2 Android Development] sera:
Thanks for the help. AndroSensor always reports prox = 0.0 in regardless of placing the finger near the ear speaker. I have tried both sides. Other sensors are working except the light sensor. It either says failed to start unknown error or waiting for an event. I never paid attention to prox in WinMo but now you mentioned it is also not working in Winmo. Like I mentioned earlier, screen does turns off momentarily when call is connected. Screen remains on until timeout in backlight settings kicks in. Pressing the power button will toggle screen in Winmo while a call is in progress. Is there a way to force the same in android?
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I had a phone with this issue. You have to replace the ribbon cable behind the LCD (or the whole LCD assembly) which has the light sensor on it to fix it it.

You can try pressing and holding the power button which should bring up the shutdown screen and force the phone to wake, but I am not sure if that will work for this version of android.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Prox sensor is broken. FRX07.1 doesn't use the prox sensor at all, so I guess you can use that build.....

Otherwise, I'm not sure what the best course of action is to disable the prox sensor. mweirauch had to do this for his device way back in the day...

Search around, you at least know what the issue is now. Good luck.
[Touch Pro2, Tilt 2 Android Development] kentc:
Do you use a protective case? I had a very similar issue and I was able to resolve it by taking the case off (and drilling a hole in the protective case where the proximity sensor was placed). There are 2 possible positions for the sensor (on the left or right side of the phone by the ear piece depending on your model... Sprint's sensor should be on the left side). If you are not using a protective case, then I would follow the other excellent advice.
[Touch Pro2, Tilt 2 Android Development] sera:
Fix in-call screen-off problem if proximity sensor is broken

Yours and wizardknight responses encouraged me to look further. Actually I started playing with gbx0c last year and saw this problem but never got around posting question in the forum. This time searching around led to hardware disabler app https://play.google.com/store/apps/details?id=com.hatcyl.android.Hardware_Disabler&hl=en. But I did not know which sensor to disable so I kept searching. It led to another app Proximity screen off lite https://play.google.com/store/apps/details?id=com.itsme4ucz.screenoff&hl=en. It did not work because it does the opposite of what I was trying to do but it gave me a clue. The name of the proximity sensor used in TP2. It is Capella CM3602. It combines proximity and light sensor and notorious for breaking down. I tried disabling the sensor using hw disabler app but it did not work. Also I had to scan for one level up as by default it only searches for drivers in i2c directory. I kept looking then I found this solution http://xdaforums.com/showthread.php?t=1626611. But it did not work either.

Finally I found this http://xdaforums.com/showthread.php?t=1870297 and it did the trick. The corresponding file in gbx0c is sensors.xdandroid.so. Also remember to enable root permission in hex editor settings.

There is one more method http://xdaforums.com/showpost.php?p=25506531&postcount=44 but I did not try it.

On a side note in WinMo the light sensor works perfectly even though the proximity part of the same sensor is broken. In gbx0c both are not working. Probably due the way android sensor driver is implemented. It needs both sensors to work correctly to be functional. In WinMo I have to disable the auto brightness and keep it to maximum otherwise in Android the screen brightness is limited to the level before launching haret.

---------- Post added at 01:40 PM ---------- Previous post was at 01:34 PM ----------

Thanks for the tip but I am not using a case.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Bravo, good work! I'm glad you got it workin. This is one of the reasons I love xda-devs :D
[Touch Pro2, Tilt 2 Android Development] bla0258:
GPS Probem ROD 100

I have installed TOMTOM Navigator and i can´t get a gps fix .

What is the problem?

On winmo work the built in gps very good
[Touch Pro2, Tilt 2 Android Development] eurohunter:
Off topic. It's been about 9 months that i've switched to a newer phone, and i still have the tp2 thread subscribed out of nostalgy. Just wanted to say thanks to arrrghhh, ACL, and detule for making my TP2 better. I really enjoyed it while i had it. :beer: :)
[Touch Pro2, Tilt 2 Android Development] td4guy:
Go to the /AndroidApps/Other/ folder and install the LeoAGpsInjector_v0.5.apk.

Then add the widget to your home screen and tap it. You will see a notification that it has done its work. That will assist your phone in getting a gps fix.
[Touch Pro2, Tilt 2 Android Development] bla0258:
GPS

I have try it too but no fix.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
GPS works great for me here. First time you are using this? Have you ever gotten a fix in Android? Any other builds that have gotten a fix for you?

I don't think this is necessary, but have you tried leaving the GPS on while booting Android? Again, I don't remember that ever being a requirement to bring up GPS.

So you need to give us more information. Is the icon popping up in the notification bar? Have you used the GPS Status / Toolkit app that shows you how many sats it sees and how many sats are locked? Does it see any sats?

Give us more detail!! Have you tried rebooting? Have you tried reinstalling? Have you tried using any other apps other than TOMTOM?

Do you have any logs?
[Touch Pro2, Tilt 2 Android Development] bla0258:
GPS

I had tried with app GPSTest And maybe it was also FRX07.1 tried but same problem.And in Android i never see a sat.

With windows mobile, I always get sat fix.

The icon is comoing but blink only.

The krenel ver is 2.6.35
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This is your problem.

Don't use 2.6.35. Use something newer... 3.4 is the latest stable kernel.
[Touch Pro2, Tilt 2 Android Development] bla0258:
Thank you i will test it tommorow
[Touch Pro2, Tilt 2 Android Development] fulrosa:
Black Screen in Games?

Hi to all, I've installed this release in my tp2 RHOD100 device (Dual Boot with WMO) using kernel 3.4.35 and i try to install some games (Angry Birds, Plants vs Zombies, etc.). For most of them the result is a black screen, some has "encountered a problem" and crashes. Someone have experience about this? I've found a post with various version of 3d driver (gralloc and libGLES); may the problem to be solved with a couple of this driver? Other Issue?

Google play reports that all of them are compatible with this Android Version (generally 2.1 or above) than i think they can run with low FPS but they have to start. Thanks to all for reply and sorry for my english.

Have a nice day
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
A lot of advanced games will simply not work. Sure you are running Android 2.3, but on an adreno130.

I would recommend buying a new device if you want to play games.
[Touch Pro2, Tilt 2 Android Development] fulrosa:
ah, ok... the problem was an older GPU... i already want to get a new device... i'll try it for hobby... Thanks for your answer and your good work...

Have a nice day...
[Touch Pro2, Tilt 2 Android Development] keraunos:
Can anyone make this project on NAND version?With 3.3.8 kernel.Or how can i do it my self if it is easy?
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Um.... well....

or....
[Touch Pro2, Tilt 2 Android Development] nightcrawler218:
phone heats up a bit.

cant input selected numbers during calling to IVR or voicemail services. key press/ touch doesn't count as input. no joy.

Any help?