yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Android will probably never be as good as wm in reguards to battery life. Signal strength, data use, GPS, wifi, bluetooth, all have heavy impact on battery life. Even turning everything off, and having the phone in sleep mode will only net you 24h max.

Probably.

Maybe.

As noted in the first post we only have RHOD400s to test with.

No. Our physic powers are not very good. We only know what you tell us.

Depends on what your end goal is, and what you started with.

For CDMA phone users, installing the 8-15-12 RIL breaks the radio. You will not be able to use the phone to make calls or transmit data until the older ril is put back or you reflash the rom. Like the comments say... if you don't get a cell signal, and you installed that RIL, you may have issues getting a cell signal. Not much more that can be said about it. Are you unable to get a cell signal? Did you do a dirty upgrade on a rom that might have had this installed?

Probably. Never tried.

---------- Post added at 10:43 AM ---------- Previous post was at 10:27 AM ----------

Works fine for me side loaded or installed from Google play. Had to install it yesterday as a mater of fact. Maybe it is not compatible with your phone, but no one else has reported an issue.

Try again?
[Touch Pro2, Tilt 2 Android Development] Stijnjits:
The first 24 hours with this release are done, so I guess it's time for a report with my experiences. :)

- GPS: Working (I use Copilot Live)

- Battery: As bad as it is in Windows Mobile (my battery is worthless), 16 hours when lightly used (some texting, checking time...) without a problem (still 40% left)

- Camera: Working fine

- Headphones (through USB): Working

- Speed: Feels faster than Windows Mobile, especially with some overclocking (using SetCPU)

Conclusion: XDA has proven they have better developers than HTC or Microsoft ;)

I only wish HTC had put a better CPU and more ram in this phone... :)
[Touch Pro2, Tilt 2 Android Development] jacktackle:
every one is like having a good time with this release. but my wifi is still not working even after this release. it gives a force close and than keep restarting.

wizardkignt, do you have any solution or fix for this kind of problem? i badly need wifi to sync my contacts and stuff.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
You are the only one reporting such an issue. Honestly I don't know anything about your setup. I don't even know what phone you have. So for the moment I would suggest running an older release. That is why they are still there. You could always try reinstalling too. The wifi has not been touched in the last release.
[Touch Pro2, Tilt 2 Android Development] jacktackle:
i'm using rhod100. i tried cm7 built also but same problem. i re flashed 3 times. same problem. it connects the wifi but before searching available networks, it gives a force close error. some problem with wpa suppliment. tried giving it a full rights but no hope.

i never faced this problem with haret built.

btw, upto what extent we can overclock this rom?

i wanted to test the MIUI build but the link is broken :P

is there any sense nand build for TP2?
[Touch Pro2, Tilt 2 Android Development] wizardknight:
The RHOD100s are known to have all kinds of trouble with any android rom. As noted in the first post we do not have any way to test the RHOD100s and do not support them. We are glad to accept patches if someone has one to offer. CM7 with kernel 3.X uses almost the same code we do. Try the OMGB.

If haret works, use it.

Overclocking is a hardware dependent thing. The rom has almost nothing to do with it.

Did you post asking for help in that thread?

Yes, but it is a WM build.
[Touch Pro2, Tilt 2 Android Development] Slipdoozy:
this one?

miui_rhodium_gsm_0.3.1-03102012

I have on my hard drive. never tried don't have gsm device per say.

---------- Post added at 01:30 AM ---------- Previous post was at 01:10 AM ----------

try this

back your old wpa_supplicant.conf rename it whatever then make a new one

copy and paste if you like from ctrl to the bottom } and edit what needs to be edited "stuff in red"

ctrl_interface=eth0

update_config=1

network={

ssid="open network" <------------------- put your name of the open network here

key_mgmt=NONE

priority=1

}

network={

ssid="wep network" <------------------- put your name of the wep network here

scan_ssid=1

key_mgmt=NONE

auth_alg=OPEN SHARED LEAP

wep_key0=0531209769 <--------------------these I would put in all your passwords same till end

wep_key1=0531209769

wep_key2=0531209769

wep_key3=0531209769

priority=2

}

now that your done with the code put this in the same place in your phone where the original is (with root). I had to do this with OMG awhile ago. not the same rom but who knows maybe? ALOT of these questions have been asked and gone over and over. some people will yell about wep not being secure but at least it works lol.
[Touch Pro2, Tilt 2 Android Development] jacktackle:
thats something cool. i'll try edit wpa. i have a positive vibe that it should work. if not going back to SD build.

people here are really handful of help :P and why not? people who still run this mobile are trouble lovers :) who like challenges in life. thanks guys for keeping TP2 still alive.
[Touch Pro2, Tilt 2 Android Development] QkTreasures:
battery life?

Well so battery is still kinda of crapy-ish I did do a wipe battery stats in cwm recovery & it seemed to help a bit? but my question is this phone had a stock win mo rom & then I flashed a energy rom with different radio rom but when i put android on it I did a task 29 & then flashed android according to steps, but left different radio rom on it with android. after i flashed android & when battery life was bad I flashed stock t mo us radio rom from stock t mo win mo 6.5 rom with android on it. So my real question is should i of actually flashed stock t mo us win mo 6.5 rom with stock t mo radio rom after i did task 29 instead of flashing android with non stock rom or radio rom instead of flashing radio rom after or does it make any difference either way. thanks ron.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Shouldn't make a difference when you flash the radio. On the RHOD400, the VZ2.37 radio is recommended - no clue what is recommended for the GSM-only devices.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
What Arrrghh said.

And I will say it again, and again, and again. We only have RHOD400s to test with. We can not tell you what works with other phones. If you do the testing yourself, we are glad to add any info and patches you come up with.
[Touch Pro2, Tilt 2 Android Development] QkTreasures:
Well i'm still new @ most of this so I really don't know how to do patches n stuff or test/play with other stuff? I would love to learn but i feel as tho it would be a lot of time involved tho unless someone could kinda give/teach me a crash course? Thanks Ron.
[Touch Pro2, Tilt 2 Android Development] xmarkom:
Rhod400 CDMA - Wireless network connection does not work, result: reboot loop.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Can you please provide more information. No one else has reported any issues with the wifi connection on the RHOD400 causing reboots. I am using it right now without issue.

Please provide your troubleshooting steps, and how to reproduce the issue.

Just saying that it does not work is insufficient information.
[Touch Pro2, Tilt 2 Android Development] xmarkom:
first of all that bug/error is in both versions Xdandroid and this one NAND version.

1. When i press connect to wifi (scanning wifi) ok.

2. When i press connect to wifi it is ok

3. When i back to the home screen (call end button or multi back button) it reboots *** but only after connecting to wireless network

(i tried again to install ROM, everything is fine until i do this above)

great work, but for mi it is useless without wireless, i will be here checking out what you have done... :)

btw I have unlocked CDMA version of RHOD400 phone (US Cellular)
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Did you do any other troubleshooting?

Did you try different kinds of network security, to see if a specific type causes your issues?

Like I said before, I am connected to wifi right now with no issues.

Have you considered posting logs? Maybe someone who can read them will see a problem with your setup.
[Touch Pro2, Tilt 2 Android Development] jacktackle:
i change my network security to wpa2 still the problem persist in this rom also. wi-fi connection force close mobile. restarts and keep on restarting until remove the battery

i don't know how it works with some. i'm on rodh 300 at&t
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Try another rom like OMGB, and see if your problem is rom specific.

Your last post said you were using a RHOD100. Have you changed your phone?
[Touch Pro2, Tilt 2 Android Development] jacktackle:
yes exchanged to run nand android. but the same ditto problem. all the nand rom's same problem. even sd roms same problem. tried them all. no wifi connection. do you think coping the wifi cabs from winmo to the root of the sd can solve this problem? like how you solve the audio problems. if so which are the files i got to extract from winmo?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Some phones have wifi issues in Android. Usually related to the wifi-nvram.txt issue. I assume you've tried that trick already and it didn't work?

Also, do you have any logs? Quite often log files will point out exactly what the issue is.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
You are out of luck unless someone else can help you out by looking at logs you post, or you are willing to try the wifi fixes in the FAQ that Arrrghhh pointed out.

We don't have your RHOD100 or RHOD300 phones to test with, and no one else has reported this issue before.

No. Wifi and voice audio are completely unrelated, and setup in totally different ways.

No specific problems are solved this way. The audio files are copied as part of the ported design in the SD builds.

N/A
[Touch Pro2, Tilt 2 Android Development] jacktackle:
did not tried wifi-nvram trick. searched every where could not fine a thread on that. can you please give me a link? with the file to downlod?

thanks
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
There's an entire section of the official FAQ dedicated to it...

http://xdandroid.com/wiki/FAQ#WiFi_doesn.27t_work_at_all.3F

Keep in mind, that FAQ was written for FRX07, and modified for GBX. The wifi-nvram trick more applies to those builds although I'm sure if the issue is resolved on those builds using this trick, then it can also be resolved in NAND doing this trick...

Either way, why haven't you posted any logs?
[Touch Pro2, Tilt 2 Android Development] mazak23:
How to boot to recovery.

Sorry if that was questioned before, but I cannot find that.

How do boot to recovery mode, I want to backup everything.

Do I need to :

5. Copy the RHODIMG.NBH, rom (GBX0*+3.4.26 Full), and the gapps (optional) files to the sd card and put it in your phone with the phone turned off.

6. Press the hold down the volume down button while pressing the power button. This will bring up the tri colored screen. It will then automatically go to the white rom update screen.

7. Follow the directions (press the power button on the RHOD400) to start the update. This should take less than 1min. .....

8. If the phone reboots automatically, that is fine. Otherwise when the phone says Update Success you can pull the battery to shut it off.

9. Turn the phone back on. You should see a blue miniPooploader screen with a lot of white text scrolling for a moment. When it gets done, pull the battery to shut it off. Then replace the battery (it should still be off)

10. Connect the usb cable between the phone and the PC, and turn the phone on. The PC should see the device, and may or may not assign drivers to it.

And then:

fastboot boot recovery.img

???

Or any different way - I don't want to make a mess as it looks my NAND is working fine now.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
1 Remove battery.

2. Plug usb cable into pc & phone.

3. Replace battery.

4. Press and hold power button until the blue mini pooploader stops (if it does not stop, start at step 1 again).

5.

fastboot boot recovery.img
[Touch Pro2, Tilt 2 Android Development] Slipdoozy:
request?

ive been greatly pleased with "GBX0*+3.4.26.13 Full".

in fact been using the GBX0 since the beginning on one phone.

so here goes my request could it be possible to add shortcuts or buttons in the notifications dropdown.

on my droid incredible is installed cm-7-20130101-NIGHTLY-inc and I love that the pull down on notifications I have options to put any buttons there I would need for a shortcut. like on mine its wifi/gps/brightness.

I figure its in SystemUI.apk but it cant be just that easily to say copy/paste from a similar device? (maybe heroc)

CyanogenMod 7 uses other apks I see in the system folder CMParts.apk and CMStats.apk...

its just a request :D

btw, thank you again for keeping our rhods running with latest stuff. :good:
[Touch Pro2, Tilt 2 Android Development] mazak23:
I tried that 20 times and no joy. Maybe windows issue, maybe cable. Once I got unknown device under devices and printers tried to install provided drivers (both) and cannot. Windows even not allow me to choose a driver saying that this driver is up to date (for unknown device - how come). By the way it was OK 2 days ago as I was flashing my TP2 on that cable and laptop.

So the question is that - after step 3 should the phone be visible in Windows as a android device or unvisible for system?

Once i got blue pooploader stopped - have no communication with ADB (fastboot devices show nothing and phone not visible for Windows).

I am on Windows 7 64 bit.
[Touch Pro2, Tilt 2 Android Development] Alchedin:
Try using the usb port u used previously with ADB, noticed this myself. Also don't use USB 3.0 port's since they tend to have problems communicating with the phone.

When it is an unknown device right-click "My Computer" use manage, select device manager from the box on the left (somewhere at the bottom), look for your unknown device and right click it and select "update driver software".

In the popup window select the 'browse my computer for driver software' and on the next screen select 'Let me pick from a list of device drivers on my computer' then in the next screen you will see a list of drivers, press the 'have disk' button and use 'browse' to find your driver. Go to where you downloaded the driver for the TP2 and you will find some .inf for your device.

This should let you use and force the driver to update the unknown device.

Good luck.:good:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Why is this required?

When the phone is in Android, plug it in and make sure usb debugging is enabled / working. Then, adb reboot recovery.

You should boot straight into reco.

The other way is with an app, or I think if you hold vol up when it's booting, it will go to reco? The adb method is sure fire, assuming you can get adb working ;)
[Touch Pro2, Tilt 2 Android Development] wizardknight:
No one said it was required, but it is a full proof method for entering recovery 100% of the time regardless of what state the phone is in. Well... assuming that adb/fastboot can talk to the device.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Try reading the P.S. on the install guide.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
At this time there are no plans for adding these kinds of features. We would like to see what we have working 99% correctly first.

Feel free to run the CM7 posted here, if you want CM7 features.
[Touch Pro2, Tilt 2 Android Development] mazak23:
I am trying all your suggestion, but as far as for now Windows see HTC and its like that:

But none of my effort taking me to adb working, always see no devices when:

fasboot devices

I am clicking on XDA device choosing Properties then tab Hardware so I can see:

So which drivers should go with which device:

ADB_fastboot - ??

RNDIS - ??

In TP2 I can see - connected with USB and debugging mode.

Regards

Mac
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Well if you are following my suggestion, this question is irrelevant as is all the other stuff you listed above.

If you are trying to do it manually.... it depends on what you are trying to accomplish. I would use ADB drivers for ADB and RNDIS drivers for RNDIS related activities, but I guess that just seems obvious to me.
[Touch Pro2, Tilt 2 Android Development] mazak23:
I tried your previous suggestion to do it by removing battery etc... never even visible for windows if stop on blue pooploader.

So now I want to work under working Android.

Second cable and the same, Windows cannot communicate with TP2, is there a way to do it under Linux?

Any guide how to do it?
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Sigh.... the previous suggestion which refers to the PS section of my install guide... the one you quoted in your previous post....

Ok. Wishing you the best.

Yes.... refer to my first comment in this post.

Yes

To the best of my knowledge, no.

All of the relevant guides that exist, of which I am aware, are included in the first post of this thread.
[Touch Pro2, Tilt 2 Android Development] QkTreasures:
battery drain issue's with 3.4.26.13 kernel on rhodium 210?

hi so i have gbxo rom with kernel update 3.4.26.13 & i think its super awesome except for the horrible battery drain which I can't figure out why? But if i use kernel_update-3.3.6-gc0a8f35.zip by detule from [ROM][NAND] GBX0* + 3.3.x kernel, http://xdaforums.com/showthread.php?t=1641555 then battery use & drain is much better with this rom but the zoom bar don't work then? so my question is what is the difference between these kernels that would make such a big difference on battery use for my t mobile us htc touch pro 2 rhodium 210 & then is there anyway I can somehow get 3.4.26.13 kernel to not drain or consume battery? Also the 2 roms seem very similar to each other & wondering what is the difference between them too besides the actual battery percentage with is great!!! I also tryed reflashing to win mo 6.5 & started all over from scratch but same results? I would appreciate all & any comments or questions on this? love my tp2 with this rom but gotta have good battery life tho & full charge with barely using last couple hours only? If somebody can help me figure this out I would even pay or make a donate for there time! Thanking in advance! Ron. :p
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Turn off wifi, bluetooth, gps, and data. Those are the largest users of the battery.

Yes, I guess you will have to choose which you like more.

No idea. Like I keep saying, this rom is for Rhod400 users, by Rhod400 users. We only have Rhod400 phones to test with.

We were kind, and didn't remove the support for anyone else. So if it works for any other that is a bonus.

Turn it off, or plug it into a charger.

You could read the first post....It might have something about that.

I don't know the answer to this question. Maybe you did.

With WiFi, Bluetooth, gps all runing my battery will only last a couple of hours at the most. With them all turned off I get 8-12 hours.

No idea how you are using your phone.

If you need someplace to donate your money to XDA is a good option.

You might consider posting logs, someone else might be able to help you.

You could go find the old led app that showed if your phone was in sleep mode or not. I think it is in the old GBX thread somewhere.
[Touch Pro2, Tilt 2 Android Development] Muhownage:
I wanted to share my experience with the newest build and a RHOD100DE:

Display: With the latest fix the Display works fine. Big thanks for merging the display changes.

Battery life: Only had a quick test today but it seems to be the same than OMGB which is used before (because of display problems).

Stability/Perfomance: In my tests everything works as good as on OMGB BUT seems faster. Less stuttering.

Only thing left to figure out is the keylayout for the german keyboard and i hope you can help me with it.

I already found out that the script "/init" copies the layout files during boot so i tried to edit it to point to the right folder (/init.etc/keylayout/RHOD100_DE).

But it seems that even if you remount / with write rights the init file gets reverted on reboot.

Is there any way i can edit the init file or is it only possible before creating the boot image file?
[Touch Pro2, Tilt 2 Android Development] wizardknight:
As noted in the first post, this rom is not recommended for RHOD100s due to various issues.

In order to permanently change your keyboard map properly you will need to open up the boot.img file, edit the init there before the coping occurs, and merge the new part with the kernel blob.

I can't remember off the top of my head where the keyboard files are copied from, but you might be able to just move/rename your keyboard map files into the directory for the RHOD100s currently being used, for a dirty hack.
[Touch Pro2, Tilt 2 Android Development] Muhownage:
Yes i know its not recommended for RHOD100 Users but except for the layout everything works fine for me.

the layouts are copied from /init.etc/keylayout/ folder so also inside the boot.img and are names like the english ones. so if i just copy them over they still get overwritten next boot by the default layouts.

looks like the only way is to unpack/repack the boot.img and edit the init file then but thanks for pointing it out.
[Touch Pro2, Tilt 2 Android Development] Slipdoozy:
cant you just rename files in RHOD100_DE to their English names and copy them to the /usr/ folder before flashing so the the rom just thinks that the English files are there? So on reboot nothing gets changed.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
The boot.img file overwrites these on every boot I believe. I think it is a leftover from the SD card days.
[Touch Pro2, Tilt 2 Android Development] Slipdoozy:
sorry that was confusing...

what I meant was to change the English files for the German counterparts well before ever flashing

Like renaming "rhod100_qwerty_microp-keypad.kl" to "microp-keypad.kl" and overwrite what is in the rom before you ever flash it?

edit: or just edit rhod100_qwerty_microp-keypad.kl before you flash it :good:
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Yes, you would need to edit the boot.img file before you flash it to accomplish what you are trying to do. I believe all that is stored in the file, and copied from the boot.img file to the system every time regardless.
[Touch Pro2, Tilt 2 Android Development] mazak23:
Bluetooth report about crash and charging battery.

So for me it is sometimes crashing with bluetooth switched on. I tried to find some relation with battery state, as was thinking that maybe if battery is less than 50 % for example it crash more often. But I get some crashes also when battery was nearly full. After crash Android is not starting properly.

My solution for now is to remove SD card and SIM card then Android is starting as normall, then I need to shutdown and put back both cards. It works fine then.

Anyway, there is a problem with charging or maybe with my battery, as charging time is about 30 minutes from empty to full.

And browsing time - connected to wifi is maybe 1 hour.

My Rhodium is 100.

I know some people report issues with this type, but for me is the only problem battery/charging time.

(Resolved other problem myslef, reading here and there).