yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] mazak23:
3.4.41 Experimental Rhod400 Kernel.

I did that update to my RHOD 100 and it is working fine for now!.

It charging with no hassle.

I couldnt found any procedure how to update kernels only, so I did it myself.

1. Quick boot - reboot to recovery partition.

2. Update from zip file.

3. Choose file experimental-bootimg-3.4.41-g6917bf9.zip

4. Reboot.

But cannot see big difference in fps in some video files (maybe cos I'm trying to watch some adobe flash videos in Puffin browser :D).

Edit:

There is a problem with charging, sometimes it does only after reboot, but then its charging to full with no problem.
[Touch Pro2, Tilt 2 Android Development] -Jonny-:
This ROM has CrossBreeder (3.4.35 Kernel), does that mean I shouldn't use Seeder? I didn't realise this and installed Seeder then CrossBreeder - can I just uninstall it or would I need to reflash the ROM?

And another noob question, I want to use a terminal emulator. Is there one on the ROM - I see it in system\app\term.apk, but nothing in my Apps or do I have to download connect bot?
[Touch Pro2, Tilt 2 Android Development] nightcrawler218:
This is the most stable & bug-free ROM that I found among the NAND versions. everything works great. I downloaded the GBX_3.4.35_Full.ZIP ROM & got some rebooting issue, switched to the experimental 3.4.41 kernel & holla. My phone is up & running without any glitch. This GUIDE helps me to setup the SWAPPER2 application. Everything is ok.

But still there is a minor issue regarding BOOT into Recovery option. I installed quick-boot app as directed but when I tap to boot in recovery it reboots & stuck in the blue screen

.................

............

.......................

Error: cannot read boot image header

Error: Could not do normal boot. Reverting to fastboot mode.

USB init ept @ 0x1c4000

USB ID 002fa05

fastboot_init()

udc_start()

The above is the last thing shown in the pooploader page. BUT I can boot into recovery by connecting the phone to PC & using CMD prompt.

Installed ROM Manager. Tapped boot into recovery mode, and the result is same as above, same error & USB details. I have to connect the phone with my PC every time I want to boot into recovery mode. Any suggestions please.?

Thanking you in anticipation.

good day
[Touch Pro2, Tilt 2 Android Development] wizardknight:
You could try re-flashing the recovery. Might be a bug. I left the TP2 when 3.4.41 was released, so it was not tested. Don't have the hardware or anyone developing any longer. You may have to live with using the fastboot command to enter recovery if that doesn't work.

Be sure to play with the overclocking if you haven't yet. It costs a little battery life, but makes the phone useable.
[Touch Pro2, Tilt 2 Android Development] nightcrawler218:
Best bug free / stable rom

Yahooo...! I found the fix. I did wrong in the flashing procedure. Thanks for the troubleshooting guide. Modified the reload_recovery.bat file & installed the old ACL cwm version. Now everything is absolutely OK. USB mass storage, Recovery mode, GPRS, phone calls. Need to check the wifi & the bluetooth. And ya, the phone lags. Need to try some overclocking apps. Will update you soon regarding the wifi, BT & overclocking tests.

The internal memory of RHOD is about 260MB, so cannot install more apps as it already says "low memory, free up some space". The swapper2 GUIDE says to create an EXT3 partition on SD card. Did it around 1GB size partition. How to link the partition with my internal memory? Will Apps2SD send the apps directly to the EXT3 partition automatically or should I have to make some modifications.?

Thanks for your support & suggestions.

Cheers

:good:
[Touch Pro2, Tilt 2 Android Development] wizardknight:
You are confusing ram with storage. The swapper app is not for storage it is to create virtual ram to run the apps in, and allow for better swapping among the apps.

The EXT3 partition will not be used by any apps directly, and anything much bigger than 256mb is not needed. It also CAN NOT be used for storage. It is lost in lue of more ram.

I never used the A2SD programs because I kept my phone with as few apps as was reasonably possible, so I am not sure if you can use the swapper ram mod while running A2SD stored programs without a huge performance hit.

I would not mix the two personally. It would just be asking for issues considering the over stability of the phone.
[Touch Pro2, Tilt 2 Android Development] nightcrawler218:
Thanks for these suggestions. Downloaded AnTuTu CPU Master Pro & set the speed Min~245Mhz Max~691Mhz. Phone performance is much better now. Gotta check the wifi & BT.

This Link2SD Guide is very helpful. I got exactly what I needed. Xda-Developers Forum makes our lives easier. Thanks to all the developers & members.

Cheers:good::good::good:

\m/

---------- Post added at 02:39 AM ---------- Previous post was at 02:01 AM ----------

Just Checked the BT functionality. I have a SidekickLX2009. Tried to send a contact.vcf file from the sidekick to the HTC TP2. RHOD is dicovered by the sidekick but while transfering file an error occurred & it is displayed in the LX2009 screen....

========================================================================================

Your file could not be successfully delivered since the recipient's device does not support this service.

(Code: BT18)

========================================================================================

This is the error detail.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I guess you could research adding bluetooth file transfer protocol support. Might be doable.:confused:
[Touch Pro2, Tilt 2 Android Development] nightcrawler218:
BT :(

Hello,

Tried a few BT apps from google market. No improvement. Tried a basic forum search, now I am a little bit confused. Any clue for the BT fix? or should I update the RIL in my device?

Thanks & greetings

:)
[Touch Pro2, Tilt 2 Android Development] wizardknight:
If it was an easy fix, we would have done it long ago. It is almost guaranteed to not be just a matter of just adding an app. That is why I said you would have to research adding a protocol. Odds are that will be much more intense than reading forum posts.

Ril updating is upto you. I never experimented with the most recent ril, so I can't say what it's impact will be.
[Touch Pro2, Tilt 2 Android Development] CRISTIIAN:
NO Sound

Hi, i installed this rom today, with the 3.4.35 kernel, but i have not sound, and wifi, dont work too, any idea?

i used the SDCARD partition method with tiad recovery 5.4. :(
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Yes. I have ideas. You could....

Try another rom.

Follow the guide exactly and get your phone working before you start experimenting.

Give us more details.

Tell us what phone you are installing this rom on.

Tell us was tiad recovery 5.4 is.
[Touch Pro2, Tilt 2 Android Development] CRISTIIAN:
Hi, im using an sprint HTC Touch Pro 2 (RHOD400), with Haret Running, i got yesterday this ROM working, but no sound on, and found wifi issues, cant connect to a WIFI network.

ROM: [ROM][NAND] [No longer being developed] GBX0* + 3.4.41 kernel - update 04/25/13 , it says NAND; but seems to be working with SDCARD method.

Kernel: 3.4.35 Kernel for XDAndroid GBX0C 2.3.7 Build 3/15/13

Recovery: Tiad v5.5.0.4 or Tiad V6.0 downloaded from the same page, allows to install ROMS of format partitions.

SDCARD size: 3.69GB

sdcard:2.81GB

System: 200MB

Data: 450MB

Cache: 249MB

npkboot configuración:

im not sure about how to configure this part.

also i put on SDcard root the cvs files.

these are the requeriments?, do you think i need another thing?

i didnt try the NAND guide because i dont want to lose WM yet.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
If you are trying to install a Nand rom to and SD card, that would be your problem. :silly:

There is a reason it says just nand in the title. Unless you want to be a dev you have to install nand roms to nand, and SD cards to the sd card. You can not just mix and match and expect it to work.

You need to either follow the provided guide, swtich to an sd card rom, or start developing your own sd card rom.
[Touch Pro2, Tilt 2 Android Development] CRISTIIAN:
ok, thanks, i noticed about the rom is only for gsm versión?. i found one rom with almost all working, except for usb mount, it only Works the first time.

:)
[Touch Pro2, Tilt 2 Android Development] CRISTIIAN:
Disable Zoom Bar

Hi, its me again :p , any one can say me how can i disable the zoom bar?, it mades random clics for me .

the rom is perfect!.

thanks in advance. :laugh:

pd. also any one can say how can enter into recovery? which keys i must to press ? before or after the blue screen?
[Touch Pro2, Tilt 2 Android Development] mynameisjonas:
99% of the way there

Hello everyone,

Hope some of you are around and can help me with this. I need a GSM phone for a european trip coming up, and decided to undust my HTC TP2 (RHOD2100). Now, I am able to do every single step in the guide, I am able to install the rom, the gApps, but then at restart, minipooploader comes up with the following errors:

Flash_read_image: success (1 errors)

Flash_read_image: failed (0 errors)

ERROR: Cannot read RAMDISK image

ERROR: Could not do normal boot, reverting to fastboot mode

After this it is stuck there until i connect back to the computer and force it to reboot into recovery through ADB

Anyone have any input? thank you in advance
[Touch Pro2, Tilt 2 Android Development] sykosoft:
I wasn't aware that the 8-15-12 RIL broke radio. It doesn't break GSM radio, that much I can confirm (as that's where I'm currently at). Does it 100% consistently break CDMA radio? If so, I can integrate the other hyc updates without the GSM fix, and re-package.

Michael
[Touch Pro2, Tilt 2 Android Development] wizardknight:
It didn't break the radio on 3.3.6 (CDMA), but I gave up trying to install it after two failed attempts in a row on 3.4.15. It is my impression that it is broken 100% of the time with this build. The signal bar shows 0 signal (grey bar & little x) on a CDMA phone. I can provide screenshots if you would like. Same build with the an older RIL showed no issues.

If you would like to PM me a test file, I would be happy to test it and push it into the next release if it works.
[Touch Pro2, Tilt 2 Android Development] sykosoft:
Let me try 3.4 with this RIL first, and I'll report back.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Coolness. Thanks for anything you can provide. :fingers-crossed:

Did the RIL work with 3.4 for you? :confused: If it worked on GSM phones I can add that to the info above.
[Touch Pro2, Tilt 2 Android Development] vinceweis:
Would like to give this a try again. Last time I tried, the keyboard was set up for the rhod 400, I think. I have a rhod300. Is there an easy way to change this on this rom? I run OMGB and it works well including re-booting, but like to run and test potentially better stuff.
[Touch Pro2, Tilt 2 Android Development] Bart31:
Hi,

I installed it on my RHOD100. Had 2.3.7 OMG123 installed first. Did NOT do any cleanup or format. Just copied the ZIP and installed it from the minipooploader.

All seems to work and batterylife looks better than with OMG123. Will see if that stays like that.

Shutdown does give the bootoptions, but is crashes while shutting down. I see some message (vaguely) that it is OK to safely to remove SD card. Need to take out battery to shutdown. Could that be because I did not format my SD first or ran some cleaning userdata and stuff?

Will report if I see more issues. For now things look fine.

Mainsplash and Secondarysplash end up giving an 'install aborted' message on my RHOD100.

Booting gives a black screen with white messages scrolling... until screen fades out. After 5 seconds the Android logo is displayed and boot looks fine. It's a little slower booting than the OMG123.

Bart
[Touch Pro2, Tilt 2 Android Development] wizardknight:
The keyboard should be auto detected, and setup correctly. If not, you would have to edit the key map manually unless there is an app from the play store that will do the job for you. As I only have Rhod400s to work with I have no way to test it for you.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I assume you are talking about the OMGB rom. Your braver than I would be. Seems like begging for trouble.

Shutdown menu is covered under known bug issues. - Known bug issues is a good thing to read. Then again reading everything in the first post is a good idea.

As noted in the text, they are only known to work on Rhod400s. Be glad it didn't brick your phone.

Sounds normal.
[Touch Pro2, Tilt 2 Android Development] Warrior4Jah:
Wow, I'm impressed that such an old phone is still supported.

I made the switch from stock WM 6.5 to unofficial 2.3.7 (nand version based on cyanogen 7.2) yesterday. Now booting up this rom on my Rhodium 100. Keep up the good work; I'll press some thank buttons and see if I can oc this device :).

[edit]I had issues with screen time-out in android, at button press it never came on. Removed all the usual partitions/folders with fastboot and started from there, seems fine now after reflashing! Also flashed the gapps package; but missing play store... seems I need to adb it :P.
[Touch Pro2, Tilt 2 Android Development] agibby5:
So am I understanding that this ROM will not work for CDMA Rhods?
[Touch Pro2, Tilt 2 Android Development] vinceweis:
It does not seem to auto detect. Can you point me in the right direction for the file to edit? It's been a long time since I fooled with hacking the Rhod and a quick search is not helping me find the right place to edit nand builds. Thanks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Uhm, what? The OP just stated 2 posts above yours that he has only tested this on RHOD400's. So if anything, the ROM is only "officially" supported on the RHOD400...
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Instructions do tell you to wipe everything at install time, so if you had issues without wiping I am not surprised.

Play store is part of the gapps package, so not sure why you are missing it. That is not a rom install related thing. Also be sure you are not looking at the old name. Play store used to be called Google Market.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Try \system\usr\keylayout\qwerty.kl

If you make a working keyboard map, and provide a copy, I can add it to the first post for other RHOD300 users.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I hope that is not what you are understanding. I thought I was very clear in saying that this had only been tested on CDMA RHOD400s. It might work on others too, but we have no way to test it.
[Touch Pro2, Tilt 2 Android Development] vinceweis:
Thank you. What is odd is that the qwerty.kl file is exactly the same in OMBG and this rom. In OMBG, my keyboard is recognized correctly but in this one, it acts like a different layout. I'm not sure editing that file will do me much good. On the other hand, what is in the files do not seem to represent my keyboard so I might try editing it anyway. It's like OMBG might be picking up the keyboard from somewhere else.

Edit: it appears that OMGB handles it completely different with a whole folder of dedicated stuff in system\etc\keymaps\ . I was able to find info on what the keymaps should look like for this ROM. I might give it a try sometime.

Thanks for the assistance and for efforts on these old devices.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
If you can figure out which kl and bin file you need from the OMGB rom. I can probably whip up a install zip that will make it work with this one.
[Touch Pro2, Tilt 2 Android Development] vinceweis:
These are the ones labeled as Tilt2. I almost had to give up the device today to my wife. Her old flip phone gave out. She went out and bought a Galaxy Note instead, so I still have this to fool with. Appreciate the help. I love the old device for it's keyboard.
[Touch Pro2, Tilt 2 Android Development] vinceweis:
These worked great on the Rhod300 (Tilt2) The Android only shows up for about a second, but both are there and working. Thanks for something new.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
So these files resolved your issue?
[Touch Pro2, Tilt 2 Android Development] wizardknight:
The second splash screen does not show for long. Mostly just done for fun.
[Touch Pro2, Tilt 2 Android Development] vinceweis:
No, sorry I was not clear. Those are the files from OMBG that apply to my phone. I still have to cross reference what from these could be used to edit the file in this GBX*. You offered that you might be able to whip up an install zip, so I was just putting these out there.
[Touch Pro2, Tilt 2 Android Development] MrPib:
Anyone tried this on a RHOD500 (Verizon CDMA)? I'd like some idea if it'll work before taking the NAND plunge!

Thanks!
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I can make up a install zip, once you know what files need to be used and where to put them. I do not have a RHOD300 to test with.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Just a heads-up, guys, OMGB uses a different keymap system than GBX. I don't know the details but I do know that you can't just port the files between them. I tried once and didn't get anywhere. (Correct me if I'm wrong and someone knows for certain you CAN do it.)
[Touch Pro2, Tilt 2 Android Development] vinceweis:
Discovering that now. Not having any luck with porting them and gave up on that. Thanks for the heads up and confirmation that I shouldn't spend much more time on that approach. Trying to just edit the qwerty.kl now but can't get that to "take" either. Still playing around.
[Touch Pro2, Tilt 2 Android Development] detule:
You boys using my ramdisk from the other gbx thread (hacked up xdandroid rootfs)?

I can see how I mucked up the rhod 300 layout. In particular:

This block seems incorrect.

Note there no init.etc/rhod300, rather init.etc/tilt2

Couple of options here, Stinger*/Wizard* makes the change and packages a new ramdisk for you. Option 2 is perhaps better, and this is what I was suggesting people do in the original thread: note

This block

In theory, you should be able to throw a few cp commands in system/etc/gingerbread.user.conf and you could customize your layout as you wish.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Yes. The ramdisk was used from the other GBX thread.

Should it read like this?

if [ $LAYOUT = "TILT2" ] ; then
echo "USING EXPERIMENTAL TILT2 LAYOUT"
cp /init.etc/keymaps/tilt2/*.kl /system/usr/keylayout/
cp /init.etc/keymaps/tilt2/*.kcm* /system/usr/keychars/

or

if [ $LAYOUT = "RHOD300" ] ; then
echo "USING EXPERIMENTAL TILT2 LAYOUT"
cp /init.etc/keymaps/tilt2/*.kl /system/usr/keylayout/
cp /init.etc/keymaps/tilt2/*.kcm* /system/usr/keychars/

Not sure what I should be expecting from the layout variable.
[Touch Pro2, Tilt 2 Android Development] detule:
For future reference, here's where you can find the description of the variable.

At any rate, I've pushed the rhod300->tilt2 correction to my repository.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I made the changes to the ram disk based upon detule's comments. Try this update zip, and let me know if that works.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I was looking at the code some more, and I think I found another typo.

Do you think

echo "USING EXPERIMENTAL RHOD100 LAYOUT (UK DEFAULT)"
cp /init.etc/keymaps/rhod100/*.kl /system/usr/keylayout/
cp /init.etc/keymaps/rhod100/*.kcm* /system/usr/keychars/

should read

echo "USING EXPERIMENTAL RHOD100 LAYOUT (UK DEFAULT)"
cp /init.etc/keymaps/rhod100_uk/*.kl /system/usr/keylayout/
cp /init.etc/keymaps/rhod100_uk/*.kcm* /system/usr/keychars/

?
[Touch Pro2, Tilt 2 Android Development] detule:
Sure I saw the post in general: The text is misleading that it's using UK default when it's using some generic rhod 100 default (btw all of that is lifted from ACL's scripts). That's not to say that rhod100_uk *should* be the default. I am not a 100 user but I can imagine a scenario where upon making that change you will mess up the layout for rhod100 users that are not on the uk layout.

Like I said before, the smart solution would be for users to personalize their layout using the /system/etc/*.conf script.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
The issue I saw was that there is not a rhod100 directory only rhod100_XX. I am guessing that the default keyboard was being used rather than any of the ones for the RHOD100 variants.
[Touch Pro2, Tilt 2 Android Development] detule:
Ugh, yeah, rhod100_* must be better than "default".

Looking forward, the entire audio/keyboard layout logic needs to be moved out of the ramdisk. Perhaps move all of it to /system/etc/*.conf. This way, you can tinker with the scripts in /system and make changes that are orthogonal to anything done by the ramdisk across reboots.
[Touch Pro2, Tilt 2 Android Development] vinceweis:
It appears to work perfect. I am off to the races. I have to try and start fresh in a little while. I ran the update on top of a Rom that I changed so much, I could have screwed up other things, or just added a lot of useless junk.

Thank you, thank you. I wasn't expecting the quick support you guys gave. I am testing at lunch in my car now. When I get back to my desk later after a meeting, I will reinstall fresh and play some more.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I've pushed the changes for the Rhod100, and 300 keyboards to the main/full install file.
[Touch Pro2, Tilt 2 Android Development] vinceweis:
When I got back to my desk, you had already pushed the fix to the main file, so rather than re-install the old one plus the update, I tried the new file from the OP. On first install, I still had the problem with the wrong keymap for the RHOD300. I ran the update on top of it, and it fixed the keymap. Maybe I still got the old file again, even though it was a different file size, so I will try the download from the OP again, but at this point it looks like the update works but the change to the main/full install does not. Will let you know after a couple more tests.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I make up the boot.img file, and re-uploaded it to the main install file. Maybe dropbox didn't update it right. Can you try it again?
[Touch Pro2, Tilt 2 Android Development] vinceweis:
It is downloading now but is slow on this end and has been downloading for about 20 minutes. Should I abort this one and try again or should this have the newest fix? i.e., when did you upload it?
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I re-uploaded at 3:29pst.
[Touch Pro2, Tilt 2 Android Development] vinceweis:
I probably better abort and start again to make sure I have the right one. Thanks.
[Touch Pro2, Tilt 2 Android Development] vinceweis:
Oops. Now it does not boot. I wiped the cache twice, factory reset twice, then loaded the one I downloaded 10 minutes ago. Tried booting from recovery, booting by reset button, and battery pulls. It gets stuck on the blue screen at:

...bunch of stuff...

flash read: WIFI 0 2000

flash_read misc partition

flash_read: misc 800 800

flash_read_image:success (0 errors)

flash_read misc partition done

flash_read: boot 0 800

flash_read_image: success (0 errors)

flash_read: boot 800 287800

It dies there. Not sure how to capture logs, or anything without catching up on old stuff. I will test other stuff later.

I am able to get back to recovery by holding the power button down. Tried flashing the update you provided earlier on top of this, and it boots fine.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Something broke in the boot.img file. I will go beat on it with a stick for a few. :P
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Whipped up a new boot.img file, and uploaded a full rom again. It should work now. :fingers-crossed:
[Touch Pro2, Tilt 2 Android Development] vinceweis:
Thank you. Just got home from work. I will try it in a couple hours.