yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] igor45:
...researching the usb issue, found the CDMA fix for it at the PPCG thread and so far seems beyond my scope alone, however will try a few things and willing to test suggestions. lol.

I'll try the SD method and likely assist in other areas once I'm running, thanks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
That USB patch on PPCG is completely unrelated to the issue with LK...

I don't remember what the problem was, but muziling reverted a patch in LK and got it working every time - I don't remember the downside? Something about how the nbh is actually built. ACL can elaborate on this.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
All hell breaks loose on my phone, this is a video of me attempting to send recovery.img and boot it. http://uppit.com/8zmfgh34nlw0/RHOD110_NAND_FAIL.AVI
[Touch Pro2, Tilt 2 Android Development] muziling:
I compiled which can flash via USB cable.
[Touch Pro2, Tilt 2 Android Development] sunyakun420:
Working On RHOD400 Sprint Touch Pro 2 on GSM mode

First thanks ACL, this is really a working ROM, I had already used it as my work phone.

Just want feed back some info, hope it will help.

I am using Sprint Touch Pro2, with GSM mode. I guess this is RHOD400 right?

Good things:

1, it's fast, I remember when I was using FRX07.1 from SD card, it always eating memory and I have to clear it very offen.

2, bluetooth file tranferation tested, works very good.

3, GSM phone works(absolutly)

4, GPRS data works.

5, Most software works smooth.

6, Memory control is good.

Some small problem:

1, ts-calibration is not very correct after first boot. But I had find out a HTC Calibrate app which can fix it from the project download page. And it works now.

2, sometimes, if you have missed call, then the phone will lose sound. Any further incoming call will not have ringtone, only vibrate. And you can hear electric sound very loud, the only way to fix is reboot.

but this only happens sometime, not each boot. Still not sure what is the reason.

thanks ACL again
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This is the 'classic' acoustic failure.

If you can get logs immediately after this occurs, that would be great. Although I haven't really kept up so well lately - I know there was going to be some attempt to unify at least acoustic code between HaRET and NAND.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
Been so busy that i figured i'd just upload what i have now instead of waiting for some free time.

http://rhodium-nand.googlecode.com/f...E-01312012.zip

Latest sound stuff is on there as well as some kernel test changes. Mostly to kill those bugs that cause panics. Ive yet to find a solution, but ive changed stuff a bit so if it does happen again, we should have more info. So keep posting logs (i see them but wont get to reply at times).

Thanks fellas.

Edit: Forgot to mention that you can OC to a little above 800 with this new kernel. Serial number is reporting properly and h2w headset microphone is working again. Unfortunately 3.5mm mic still does not work. It's weird because the Kernel itself detects the mic, but userland seems to just ignore it.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
Yeah, the issue is with the way we make the NBH. Back in the good ol days Lance got it to work via the usb flasher but we had to change it since it would break SDcard flash. There is really no downside to how its done but eventually i'm hoping i can make LK update itself and almost eliminate the need for the NBHs. :p
[Touch Pro2, Tilt 2 Android Development] n2rjt:
Just checking . . .

You mentioned a new kernel, but posted a link to a ROM update of acoustic .so files. Was there supposed to be a new kernel posted too, or am I just reading too much into this?

And thank you much! The progress has been awesome.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
the update i posted includes the new test kernel plus some acoustic updates. So its all in that 1 file.
[Touch Pro2, Tilt 2 Android Development] n2rjt:
Yes thanks for the quick update. I was getting ready to correct my post after noticing same.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
I have some homework for some of you guys. If anyone has a verizon branded Rhod500 or any of the Rhod100 that need custom kb layouts.

cat /sys/class/htc_hw/machine_hwinfo

Then type dmesg and look atht the dump on the screen. The last 5 lines will have something like this.

<6>[ 1882.704223] Hardware Board ID is 4
<6>[ 1882.704284] SKUID PCBA PN is 0 1 f1
<6>[ 1882.704315] SKUID SKU Num is 0
<6>[ 1882.704345] SKUID PCB ID is 4
<6>[ 1882.704376] SKUID RF SKU ID is <6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>1<6>0<6>0<6>3<6>2<6>0<6>0<6>d4<6>0<6>0<6>0<6>2<6>

I'm hoping your data is different since this is all from the rhod400. This way we can better identify sub variants. :p
[Touch Pro2, Tilt 2 Android Development] milda25:
r

I don't know, if you didn't overlook my post on ppcgeeks forum. There I posted requested 5 lines from my Rhod100 a few days ago :-)
[Touch Pro2, Tilt 2 Android Development] zapbrannigan00:
Thanks for update!

Mine running stable at 787Mhz (806Mhz is just a little bit unstable for me)...

Seems to be a bit more responsive, every little helps (just wishing for GPU overclock now :))
[Touch Pro2, Tilt 2 Android Development] LightC:
GPS lock

Anyone have any issues getting GPS to lock post the gps update? Assisted GPS seems to be working great for yelp lookups but it would be nice to get GPS navigation working. I've left it trying to lock for over 30 minutes near a window and had no luck.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Sounds like you tried it indoors - that's pretty useless.

Keep in mind, ALL of the niceties that help GPS lock times are not available. This is just plane jane GPS, with no warm injection, XTRA, nothing. So it will take an exceedingly long time to get that first lock, and I can pretty much guarantee it won't lock indoors.

I was able to get a lock after about 10 minutes or so of driving around. Try it yourself.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
Yep, i saw it. But now we need your other rhod100 brethren to start posting.
[Touch Pro2, Tilt 2 Android Development] walter79:
RHODIUM 100 de

Hardware Board ID is 80
SKUID PCBA PN is 0 1 f2
SKUID SKU Num is c
SKUID PCB ID is 80
SKUID RF SKU ID is <6>ff<6
[Touch Pro2, Tilt 2 Android Development] hashtowent:
same here!

problem with german layout:

ü ö are written in capital letters!

(with howto i would fix this in the existing package!)

led is now off with latest update! (now working like in windows?

-> phone is snappier w/o more oc! 748 still good

BUG: some mp3 files can't play properly they just jump to end after a few seconds!

(some show no artist some play properly)

OVERALL: THANKS TO ACL KEEP UP THIS GREAT WORK!

---------- Post added at 08:23 PM ---------- Previous post was at 08:18 PM ----------

GREAT FEATURE:

END CALL with POWERBUTTON

for all those who can't end a call with red/home button!

its found in accessibillity settings at the bottom!

works fine!
[Touch Pro2, Tilt 2 Android Development] [ACL]:
Booo

<6>[35600.850830] Hardware Board ID is 80
<6>[35600.850891] SKUID PCBA PN is 0 1 f2
<6>[35600.850921] SKUID SKU Num is c
<6>[35600.850952] SKUID PCB ID is 80
<6>[35600.850982] SKUID RF SKU ID is <6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>ff<6>0<6>0<6>1<6>2<6>2<6>0<6>0<6>d4<6>

this is identical to what milda reported :-(.. this means all this information does not tell us anything about the specific language setup. I'll have to keep digging into memory to figure out the best way to automatically detect sub variants.

Maybe you guys know this, but is there anything on winmo itself that identifies your device with the language? perhaps there is something on the properties or the phone information that mentions this?

edit: last chance is to see if the CID has this info. guess ill see for next release
[Touch Pro2, Tilt 2 Android Development] walter79:
We can easy make a update.zip for each keyboard. I replaced only 3 files and have full german keyboard + call end = home
[Touch Pro2, Tilt 2 Android Development] Bones2374:
NICE work on this ROM, [ACL]!

Unbelievable, this 1.2.3 build or the preperation instructions CURED the Screen Brightness problem that my Tilt2 had going on for a year now!! :D

I thought I was having a hardware problem, and over the course of the past year, I tried all of this:

Task29

Stock AT&T ROM from the CD

HTC's Website ROM

Countless EnergyROM builds (primarily 2900)

FRX7.1

GBX0B

AT&T's Dallas repair shop

HTC phone support ($90 minimum estimate for repair? No thanks!)

Nothing would ever allow me to adjust the screen brightness, it was always stuck at half-bright, and only under WinMo if the phone went to sleep or I took a call (proximity sensor active), the backlight would never come back on until a reset. Who knows, maybe it was a corrupted flash block and the "Fastboot erase" commands finally cured it. I'm golden!

Nice Ringtone and Wallpaper additions too by the way, I've clicked "Thanks" on both your first posts here and I'm actually going to Donate to this and the XDAndroid project.

Tilt2 Rhodium user since 2009

8525 Hermes since 2007

XV6600 Harrier since 2005
[Touch Pro2, Tilt 2 Android Development] walter79:
What can we do to improve GPS fix time. 25 min for a fix is long. And it works only sometimes. Is there a way to port libgps.so from froyo. Google G1 phone use this one in GB-builds.
[Touch Pro2, Tilt 2 Android Development] hashtowent:
i assume we have to get xtra files working, injection, hot start etc all the common gps helpers are inactive for now. (am i right acl?)

---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------

can you please check weather your ä ö ü are in capital letters?

for me they are (i have to press u long and select ü to get normal "ü" instead of "Ü")

thank you.

-> a simple apk that lets the user choose the right profile would be best i assume!

---------- Post added at 10:20 PM ---------- Previous post was at 10:17 PM ----------

CID is one problem:

isn't it set to 0000000 by hardspl?

isn't hardspl giving us all the same cid?

maybe the shown serial in LK can give information about the subtype!

in general the phonesupdates check carrier and language by the cid. (the phone checks if the update has his CID i assume)

-> thats why we need hardspl if i'm right.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
IMHO if it can't easily/consistently be detected, letting the user choose in some way is obviously the best option. Perhaps the easiest for all would be an update.zip - creating an APK just to choose initial keyboard layout is a lot of work for little reward IMHO.

Flashable zips after the fact aren't a big deal...

This answer below is spot-on. We only have GPS - none of the 'advanced' niceties that help improve lock times. No one has gone thru the chore of porting back the HD2 work on this...
[Touch Pro2, Tilt 2 Android Development] milda25:
I agree with Walter79 and arrrghhh. Automatic detection of kb layout is minority problem and there is some higher priority issues which should be solved. Your time is too expensive for solving this stuff, ACL. Instalable .zip should be great for all of us.
[Touch Pro2, Tilt 2 Android Development] Bones2374:
Future Feature Suggestion: Any chance of getting hardware/chipset FM Radio support in Rhodium300 (Tilt2) like the HTC Vivid has?

I noticed there's an unrelated "Bluetooth" FM Radio app pre-installed, but it just FC crashes before it finishes opening from a straight Factory Reset install.

Great work, I'm sure you're incredibly busy fixing bugs, so I have no complaints.
[Touch Pro2, Tilt 2 Android Development] n2rjt:
CSV files?

Question: should we have the WinMo CSV files on our SDCARD for this ROM? I have them, from when I was using GBX from haret. Are they hurting anything? I have had a few audio problems from time to time, but usually it works okay.

Except bluetooth: I paired with my car, but when I try to play music or answer phone, the bluetooth on the phone stops and starts. I know you need logs, I'll post them after I sanitize them.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
a) not necessary and b) I'm not sure - I think ACL said they override what's in the build, but I could be wrong.

Bluetooth is kinda flaky, some people say it works great, others.. not so much. AFAIK certain apps still make it go crazy like Pandora.
[Touch Pro2, Tilt 2 Android Development] Bones2374:
Bug: Gallery included in the ROM package freaks out if you do an orientation change. (Auto-Orientation, or slideout the keyboard). Video gets badly distorted interlaced lines & echoes.

Fix: Uninstalled Gallery system app with Titanium Backup (free), and restored the one from my previous GBX0B backup. :D

Sent from my Touch Pro 2 using the XDA mobile application powered by Tapatalk
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Weird, so what about Maps?

The same thing happens in Google Maps.
[Touch Pro2, Tilt 2 Android Development] walter79:
German keyboard layout

- put *.kl files to /system/usr/keylayout

- put *.bin file to /system/usr/keychars

- set permissions for all files to 644 (rw r r)
[Touch Pro2, Tilt 2 Android Development] [ACL]:
No, the rom includes all the csv. I posted a few pages back on how to change these from inside the rom itself.

On nand, the sdcard is not mounted until android is fully up and by the libacoustic would fail if we relied on the sdcard for csvs. So we load it from Nand directly.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
thats not a fix and dont mix and match apks until the rom is stable. God know what kinda nonsense goes on behind the scenes and its going to make it a nightmare to troubleshoot. The distortion is a known issue on the issues list, just havent had a chance to dive into it.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
http://rhodium-nand.googlecode.com/files/OMGB_UPDATE-02012012.zip

there has been some good feedback so far. Make sure yall have the latest version. This fixes some sound issues and small tweaks to the kernel.
[Touch Pro2, Tilt 2 Android Development] sunyakun420:
Found another possible issue about "Network Mode"

I am using Sprint Touch Pro2 RHOD400 with GSM mode.

Issue description:

No matter I set network mode to "GSM only","GSM/WCDMA preferred" or "GSM/WCDMA auto", when I arrive some area with no signal, and then I came out to signal area, the phone signal will not recover.

And I found the reason is when GSM has no signal, it will try CDMA mode, and won't switch back to GSM again automatically.

If I switch the network mode manually, then it works fine.

This issue mostly happen but sometimes it's not.
[Touch Pro2, Tilt 2 Android Development] hashtowent:
same issue here!

another one:

try pushing your battery to almost nothing (phone goes off): it will change your time! (after charing and powering on my clock is late =( ) not bad if know but if not...

no fix needed (because batterystatusindicator needs to be fixed first)

but please take care of this ;) [users]
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I don't see why it would go into CDMA mode if you had it in GSM only - are you certain?

Please leave it in a GSM only mode, and see what happens. Take logs of when you "think" it's switching to CDMA mode - because that's really the only way to confirm.

Clocksync.
[Touch Pro2, Tilt 2 Android Development] boggsie:
Interesting situation. I (now) have a second TP2 (both are Sprint).

My primary phone is Windows Mobile with GB Build running off of SD card.

This second (just received phone) I finished setting install and setup via WiFi, as I don't have two lines of service. After setting it up, I wanted to see how calls would be handled so I went into the online Sprint settings and activated the phone.

Both phones were off, the activation online in the Sprint site was completed at which time I turned on the Activated (NAND) phone. It cannot connect to data. It is almost like there is some low-level setup that I have to complete in WinMo in order to get the phone to be recognized.

Thoughts?

Best regards,

-boggsie
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Keep in mind, it does sometimes take longer to get data service. They say up to 4 hours sometimes...

Assuming you have waited long enough, you might be right. I have no clue what kinds of handshakes happen during provisioning - and they might be sending one for WinMo, since they are probably assuming that's what you're running lol.

Not sure, but I'd be interested to see some logs! ;)
[Touch Pro2, Tilt 2 Android Development] boggsie:
arrrghhh !!! I cannot believe I forgot to attach logs!

Best regards,

-boggsie
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol.

Did you use GetLogs to pull 'em?

This just seems to be logcat, w/o timestamps...
[Touch Pro2, Tilt 2 Android Development] boggsie:
Get Logs by DBREESE from Android Market ... wrong one? Lemme check!

This is obviously easy enough to reproduce.

Oh and no doggin' on all my widgets!

Best regards,

-boggsie
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Oh, no... GetLogs from rpierce99.

Not sure what one you got, but that output is horrible! rpierce99 should sell his app, and do an ad-supported free version that doesn't allow custom masking...

oO I shall propose that :D.

Anyhoo, Logs.
[Touch Pro2, Tilt 2 Android Development] boggsie:
I didn't know what to mask for and I reviewed for what I thought would be important. If you see anything I should pull out, do me a big favor and let me know.

Best regards,

-boggsie
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I've honestly never used the custom masks. What it masks by default has always been sufficient for me...

Edit - bashed thru the logs quickly, I don't see anything that stands out... I see the radio trying to connect to data (#777). Do you have a SIM card in it? Not sure if that would cause issues with data provisioning/registration...

I'll try to compare your logs to mine to see what is different.
[Touch Pro2, Tilt 2 Android Development] boggsie:
Two logs included in the xip. One with and one without the SIM inserted.

In both cases, I could not get data.

For that matter, I cannot complete a call, either. Get a "call support" recorded message. :(

Best regards,

-boggsie
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
oO I thought you could make/receive calls. Since you only complained about data, I assumed that regular calls were fine :p.

You might have to flash back to WinMo to provision...
[Touch Pro2, Tilt 2 Android Development] boggsie:
Does anyone have that on an SD card that I can launch from Android? :D :eek: :rolleyes: :confused:

Best regards,

-boggsie
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Uh, what?

You just go to the tri-color screen and flash via SD or USB...

Also, looking thru your logs I definitely see data failure requests. Did you try to make a call on any of the logs? What happens when you try to call the number?
[Touch Pro2, Tilt 2 Android Development] Starfox:
If you swap devices on Sprint, even if the device was previously activated on that line, the data profile needs to be updated.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] boggsie:
Hmm ... I wonder if there are some generic (non-device specific) utilities on Sprint ROMs for Android, which would help with this?

Best regards,

-boggsie
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
AFAIK that's something that only comes with carrier ROM's w/Sense for HTC devices...

I remember reading a lot of stuff about EPST not working on AOSP ROM's, and users would have to flash back to stock to do EPST.
[Touch Pro2, Tilt 2 Android Development] Bones2374:
No problem, just letting you know that the video orientation issue exists in the Gallery v1.1.30682 in the Jan. 15th NAND ROM package, even without using the GAPPS.zip update. (I started over from scratch with Task29 just to test this)

And your right about mixing the .apk's, Voice Search quit accepting audio so that was another good reason to start over with a clean slate and stay true to your testing. :D

Great work so far, I'm about Task29 again and load your 02012012 update.
[Touch Pro2, Tilt 2 Android Development] boggsie:
Sprint Rhodium 400

January 16th build.

January 18th GPS add-on.

February 1st update.

Pairing with Jawbone without issue.

Attempt a call by tapping button on Jawbone.

Phone recognizes tap displays call (voice command) screen.

It does not recognize any commands.

Went ahead and made a call with handset.

Earpiece was static but I could tell it was the automated weather line that I had dialed.

Went to speaker phone and call was completely legible.

Went back to BT / Jawbone and static remained.

Best regards,

-boggsie
[Touch Pro2, Tilt 2 Android Development] 4dn4n:
Hello;

I use software update 24.12.2011 and 01.02.2012. works fine. but when I press the fn key on the keyboard, "@" comes out and does not process the fn key.

Can you help me?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Which keyboard layout are you using?

I assume you have a RHOD100, but again which one? Does this happen on HaRET builds as well...?
[Touch Pro2, Tilt 2 Android Development] [ACL]:
i'm trying to cookup a way to do this whole sub variant thiing manually via LK. I'm thinking of carving out a sliver of nand for persistent changes. Not sure if it will work but im thinking of something people can do while flashing that will force specific settings.

Like "fastboot oem writekb rhod100_de"

Then they can flash peacefully and update knowing their LK will pass DE specific settings. Its all good in theory, now i just need a weekend to write the code. I bought a new coffee maker so now i just need time.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol, you're awesome.

What's wrong with flashable zips tho? It seems like that would be easiest for you to do, and really you'd only have to make flashable zips for the random RHOD100 variants since the detection seems to work for everyone else.

Just my .02. No sense in beating yourself over something that can easily be solved with a flashable zip...
[Touch Pro2, Tilt 2 Android Development] 4dn4n:
uk array using the keyboard. There was such a problem with the version published by the sd.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This isn't very helpful.

So you have a RHOD100_UK, and this was always an issue? Did anyone resolve it on HaRET? What was the solution? I'm sure that someone just hasn't finished the keylayout. Can't do this stuff for you guys, if we don't have the device how can we ensure the layout is accurate? It's been accurate for my RHOD400 for... years? lol.
[Touch Pro2, Tilt 2 Android Development] hashtowent:
dialerbug

all of you on gsm! (rhod 100 for me)

please test:

make a call to a bussy phone! (phoneline used)

for me i can't end the call other then enableling flightmode!

all other situations work (connection lost, not answered, normal, etc)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What happens when you try to call a phone that's in-use...? It should go to voicemail if you don't have call waiting.
[Touch Pro2, Tilt 2 Android Development] milda25:
Release from 01162012 contains rhod100_uk as default key layout. In this key layout have Fn key expected sense.

If you have a special reason to use the 12242011 release, you must manually copy the map keys. Get the files microp-keypad.kl and microp-keypad.kcm.bin from the SD card build (Haret) and copy it to /etc/keymaps / (I think)

Edit: It means all builds released from 01162012 and later has rhod100_uk as default key layout.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
There should be absolutely no reason for staying on old builds.

If you do, you will get left behind. This is how a lot of the older devices dropped off from support - they stayed on old builds, and found when they tried to update a lot of things didn't work!

So please, don't leave your phone on an old build. Update as soon as you can...