yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Hmmmm, I'll wait for Arrrghhh to answer that. But that's the only thread for SCBS that I recall.
[Touch Pro2, Tilt 2 Android Development] argenisaz:
These are RHOD500 csv's. Pulled them from my wife's phone. She's running a stock ROM.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I think the .39+ autobuild kernels all have it... I could be wrong tho, those patches may not be making it into the newest 3.x kernels.

Also, there's a rootfs change that's necessary. SCBS was kinda left out to pasture (unfortunately, it's a great concept) because it only ran on RHOD. Never got it working on any other device...
[Touch Pro2, Tilt 2 Android Development] r0mka:
Hey there. I have a problem. I am using TP2 and it can't boot with any other kernel except .35. It would be ok but with .35 i can't get wifi to work. Tried the method with mac address change and nothing. Also camera not working. With any other kernel i get an error "can't access tty" or "not syncing". I did everything correctly, doublechecked 5 times. Under the battery i found that it's RHOD300C, but when i use with RHOD300 startup, my keyboard is wrong so i am using RHOD100 and then it is normal. What could be the problem to make these panics?
[Touch Pro2, Tilt 2 Android Development] Raul^:
You were right the 0C works with the same kernel.
[Touch Pro2, Tilt 2 Android Development] GFX:
Thanks for your wonderful work! The GBX0C is the most stable Android release ever!

Everything is working as it should, the speed is very good considering the modest specs on the TP2, and it's easy on the battery too! I'm getting a full day out of it with moderate to heavy use (WiFi on for 3 hours, gaming, music playback, web browsing, and a little bit of GPS).

I can confirm that the camera works correctly on my RHOD100, Camera360 makes it even better with touch-to-focus, image stabilizer, and many beautiful effects.

I have yet to see any significant bugs. Sometimes the device hangs when I stress it with heavy multi-tasking and rapid app switching, but I guess it's due to the overclock (running stable @ 700MHz) so it's not a big deal.

I have noticed something strange though, in FRX releases the speakerphone used to be MUCH louder than GBX! But now it's the opposite story as WinMo became louder than GBX!! This is frustrating, since the volume in WinMo is now very loud, and really made me proud of my TP2! It has an excellent set of speakers.

So, do you know of any way to make the volume a bit louder? I tried downloading tweaked CSV files and placing them in the SD card but it made no difference! What am I doing wrong? And is there any other way to boost the volume other than CSV modifications?

Thank you arrrghhh, detule, and every other member who helped build this awesome release. Your work is much appreciated!

P.S. I'm running the 3.3.4 kernel.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So .27 doesn't even boot...? Post your startup.txt.

.35 is pretty old, won't get any new updates. .27 is probably going to rot as well at this point, gotta go with 3.x. So you run 3.3.4 and it fails to boot? I don't know how many times I've gone over this, but you have literally everything from my bundle? HaRET.exe, startup.txt, etc? Don't re-use anything!!

The CSV modifications should work just fine... I'd assume you're not employing them correctly? Which CSV's did you replace? If you try booting with no CSV's, does sound still work?
[Touch Pro2, Tilt 2 Android Development] r0mka:
this is my startup.txt:

set ramsize 0x10000000

set ramaddr 0x10000000

set mtype 2292

set KERNEL zImage

set initrd initrd.gz

set initrd_offset 0x00a00000

set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod100_uk"

boot

I tried completely stock ROM and with updated rootfs and i've got the same - either it even does not come to part where bootloader states that it's starting to run android or to the part it states that it's starting to run android but then it kernel panics. I've got 11 *.csvs from custom winmo ROM maybe this is the case?

To the person who needs more sound - try voodoo sound app from app market if it's supported
[Touch Pro2, Tilt 2 Android Development] GFX:
I replaced "AudioFilter.csv" and "AudioPara3.csv" in SD root.

I also tried replacing them manually in "system\etc" folder, the system files were "AudioPara4.csv" and "AudioPreProcess.csv" which I got from another package.

I double checked the AudioPara3.csv and all the gain params are set to FFFF at level 5! So the volume should be set to maximum already! I think I'm replacing/editing the wrong files, because no matter what I do I can see no difference!

I didn't try booting with no csv files in SD root, but I don't understand how could it affect the volume? I'll try it anyway and tell you how it goes.

Thanks for the help arrrghhh..

EDIT: I tried rebooting with no csv files, and I had no sound from the speaker. Only the earpiece worked.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well wait, let's not mince words here. When you say completely stock ROM you mean WinMo? You flashed stock WinMo, then "updated rootfs"... that's odd. You should be using EVERYTHING from the first post as far as running this build. So you wipe your SD card using the HP Tool - full format, FAT32. Then, you download the link in the first post. You don't change A THING. You reuse your ts-calibration, and use my provided startup.txt for your device. Boots?

Now, you follow the Incremental Updates process for updating the zImage/kernel to 3.3.4. If this fails to boot, but .27 does boot OK then something else is going on.

Yea, I just wanted to make sure the CSV's were actually being processed. Interesting that sound worked at all, but I guess if it didn't work out of the speaker at all they're doing _something_...

I'm not sure why it's so quiet to be honest. Again, the only thing I can speculate is something particular with your device model (these RHOD100's are so tricky) that is different from every other RHOD. There's got to be some other value that needs to change...

I have heard some apps in Android that will boost volume. I heard some of them work... Now I've never felt the need as my RHOD400 always seems almost too loud in Android... But this was suggested:
[Touch Pro2, Tilt 2 Android Development] r0mka:
no i meant i have tries both - stock android from the opening post and with updated rootfs, i've already tried everything you have posted - full formad and no change and it does not boot, it hangs almost at the end - at that point where it should start booting android. Then it gives me 7 seconds to read everything..
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You've formatted using the aforementioned tool...? Do not use the built-in WinMo or Windows format utilities.

This should wipe out any partitions on the card, if they exist... I can't think of anything else that would hang up the boot process. You've been able to run FRX OK?

Edit - it makes absolutely no sense that only .35 works/boots on your device... What RHOD is this again? Please check under the battery, near the FCC ID.
[Touch Pro2, Tilt 2 Android Development] r0mka:
tried both - windows 7 and the other formation tools. First time i did fast format with the tool which you gave me, but when i did second full format of my sd card it stopped at the end and the card is unusable now so later i've used built in windows format tool with other card. What is FRX?

I've found only RHOD300C under the battery but that can't bee because when i use RHOD300 startup buttons are different from what i have. If there is any other method to check which device it is i could try it
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Not to sound rude, but if you've read any of this thread you will note a recurring theme regarding formatting sd cards for this build... Do not use any windows formatting tools.... I'm no expert but if your card didn't tolerate a format using one of the tools that Arrrghhh linked to, there was a problem with the card. Using any sort of windows formatting tools will lead to more problems... Use the tools Arrrghhh linked to and if you need a new card, get one. You'll thank yourself when the build runs as it's supposed to.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
RHOD300C sounds odd. As it states in the FAQ, the RHODXXX should be near the FCC ID. Is it hard to see, as it's usually printed in gray not black.

As for the card, it sounds like the card is bad. See the previous post. Also, this thread assumes you've run FRX before. Perhaps look around this section of the forum? There's this sticky section of important threads, highly recommended.
[Touch Pro2, Tilt 2 Android Development] agibby5:
I was reporting issues with battery and sleep issues a few pages back. I hope you all forgot because I thought the phone wasn't sleeping but it turned out I was using the old version of the LED app. Anyway, the phone is indeed getting into sleep when running the new LED app. Thanks for that!

Anyway, I was just wondering if anyone can explain why I get about 12 hours on Xdandroid with the phone literally sitting idle in Airplane mode overnight and into the morning. However, wehn running Windows, I get just over 24 hours doing the same thing. For example, on the weekends I'm busy and let the phone sit and 24 hours later, it's still running on the same charge. I know that I should only expect 12 hours or so on Xdandroid, but I was just wondering if there's a concrete reason for this when the phone is literally idle the entire time.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
It depends on what you are running in the background and how often it is running? Do you have email and other things syncing in Android that you don't have in WM, or do you have it checking more often then in WM? Do you have more apps installed (and potentially running) in Android that might wake the device and poll the internet or something? Are you overclocking in Android when you aren't in WM?

If you haven't already, you should follow the Speed Improvement thread where it talks about using ADB to "pm disable" all apps you don't need running at startup by looking at your logs to see what is running.

If you don't have anything different going on in Android versus WM, then you can just chalk it up to Android just takes more juice to run (even in sleep) than WM does. I learned to live with it by buying more batteries and extended life batteries, where I can get 18-20 hours with moderate use with my extended life batteries. I tend to not even charge the batteries using Android anymore, I use my external charger to have one ready when the other one dies. My other OEM batteries were old and not holding a good charge anymore, so I replaced them with the ones I have now.
[Touch Pro2, Tilt 2 Android Development] r0mka:
I am attaching some pictures. If you download them everything is clearly seen, except for the back cover of the phone, but if you zoom in you will see that it's RHOD300C. I've taken picture of my keyboard too, because RHOD300 have numeric keyboard on some letter buttons, but mine doesn't. This is an error i get. If it helps i can post a video to everything what's going on. I've tried android with .35 kernel and it is amazing so i am willing to do anything to get it running on this device :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
That's so ridiculously blurry, I have no clue. Perhaps you have a clone? Someone in the Topaz forum thought they had a Topaz, but it turned out to be a cheap Chinese clone which didn't use the same hardware.

Logs are going to be your only savior at this point. Have you been able to run FRX before? I've asked this, and you just responded with something like "what's FRX" :rolleyes:
[Touch Pro2, Tilt 2 Android Development] r0mka:
Oh sorry i've forgot to reply. Yes, i have booted FRX but also with specific kernel i don't remember which one but it does not produced any sound and camera was not working. Well if it was a china phone then it wouldn't be capable of running official touch pro 2 firmware. Could it be that it gives errors because of unofficial modded wimo? I'll try full format it again and use everything only from opening post. I've read somewhere that from nth time it worked :D what about error pics? they are clear and readable maybe you can say something from them?

Oh and huge THANK YOU for helping me with this and spending your time!
[Touch Pro2, Tilt 2 Android Development] GFX:
Well, I'm sure the RHOD100 are cursed or something! First we had the front panel glitches and now the sound issues.

Anyway, I tried many programs from the market, "Voodoo Sound" didn't work because my kernel wasn't supported! Other programs failed to have any effects on the volume.

I have a couple of questions before I give up on this:

- Could it be kernel related?

- What is the role of SD csv files? Are they copied to Android's file system? Are they copied once or every time I launch HARET?

- Do you have any idea what files I should modify? (I have 11 csv files)

- Do you know of any reference or guide that explains what those csv files do and how do they work?

Thanks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
The error pics were too blurry to make anything useful out of. Please post some logs, or find the combination that actually works for you on FRX. We can work from there... Sorry, I'd be doing the same crap if your phone was in front of me. It's part of the triage process - you have to do this.

Could be kernel related, but doubtful. Have you tried different kernels? lol

The SD CSV files are provided to Android for setup of the acoustic libraries. I assume they're copied everytime, but I really have no clue... I'd have to look at the code.

No clue which needs modification, kinda up to you if you want to tweak them...

Unfortunately I've never seen such a reference guide. Perhaps looking at the code would help here as well...?
[Touch Pro2, Tilt 2 Android Development] AkumaX:
hi aarrggghhh, your name is red now? haha

just d/led the new GBX0C - still noticed that there needs to be a carriage return in the startup.txt for some of the files (example: RHOD400)

instead of:

set initrd initrd.gzset initrd_offset 0x00a00000

should be:

set initrd initrd.gz

set initrd_offset 0x00a00000

just letting you know in case some people come in and complain about startup.txt :P
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Blame the job...

It's not an issue with the startup.txt, the issue is with your editor as I previously stated. Look at the file in an editor that respects line feeds from Linux, IE Notepad++ (or Linux itself, lol), and it'll show up just fine.
[Touch Pro2, Tilt 2 Android Development] auburnham:
No Sleep in GBX0C + 3.X kernel w/ Wifi ON

My device will not sleep in GBX0C with the 3.x kernels while Wifi is on. If I turn Wifi off, the device sleeps as it should. Also, with the older .27 & .35 kernels, the device sleeps with Wifi on. I've been doing most of my testing with the 3.3.4 kernel, but I've experienced the same problem with 3.0 & 3.2. Any suggestions to troubleshoot? Would a logfile help?

Another problem that seems to be related (since it happens with the same kernels) is that the device freezes when I try to shutdown/reboot. It freezes at the "Shutting down..." screen. I have to pull the battery to turn it off. This happens whether Wifi is on or off.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Shutdown is a known issue in 3.x. If you want kexec to work, it breaks shutdown. On .27 this should work fine.

Not sure about wifi. I think it depends on your settings - you can set it so wifi disables sleep, but I thought people were having issues with that as well, ironically.
[Touch Pro2, Tilt 2 Android Development] mowglilp:
Hi everyone.I have issues with my RHOD100.Here are my problems.

On FRX06 everything works fine except camera, didn't try BT or WIFI, but the led stays on, and phone acts wierd and i find that GBX0C is much better, and it's gingerbread, i like the way it is but i have lots of issues.With the bundle pack these issues are:

1.Screen brightness, it's too dimmed, increasing setting doesn't affect anything.

2.End call button doesn't end the call.

3.Camera doesn't work, however it does with kernel pack 3.3.6.

4.Apps don't download through android market.

I tried adding data.img from FRX06 and it works out the screen brightness problem and end call button, however i cant connect using my data plan.

How can i find that datalog or whatever you guys post, sorry but i'm pretty noob about this.Also, if one of the dev's can PM me with a Y!M id so i can post more questions as i'm sure there are many more isssues with it that i haven't found yet, i spent 3 days, more than 8 hours a day trying different setups and nothing seems to work the way it should as it does to other lucky RHODIUM owners.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Don't reuse old data.img's.

The end call button doesn't end calls... Most native Android devices don't have an end call button, so we re-used ours as the home key. There's an on-screen end call button.

Screen brightness... auto backlight disabled in WinMo? Have you tried auto or manual brightness in Android? Which kernels have you tried? I would recommend the newest 3.x kernel, as .27 is not getting updates at this point. Looks like you already have in fact, as you found that fixes the cam (which I was going to suggest as well...) So screen brightness still broken in 3.3.6?

For the Market, some apps won't work. Are you saying ALL apps fail? Over wifi, 3g? Do you get an error? Do you have logs?

The forums are here for support and development information... I suggest you read thru them, and that search button helps a lot as well. Hand-holding is not really condoned or encouraged... Like I said we're here to help, if you have a specific question or issue search for a bit, then post up if you can't find an answer. No worries.
[Touch Pro2, Tilt 2 Android Development] mowglilp:
Thank you for your reply, i searched a lot of topics but can't find anything that helps me.There are too many versions of rhodium, one fix doesn't apply to all terminals i guess.

I found that the kernel i'm using is actually working fine and added *.csv and now calls work great.

End call button issue can be fixed by going in "accessibility" and ticking a checkbox with "power button ends calls", i know it's not the original end call button, but it's a good enough fix for someone who is used to ending a call with a button.

Apps do indeed download and install just fine since adding the *.csv files and new 3.3.6 kernel, all works fine.

Idk if BT works or Wi-Fi, i did get the WI-FI networks available but could not connect to it.

So only one remaining problem: screen brightness.It's set to maximum in WinMo and also in Android, but it's too dimm, i like it much better on FX06 where the brightness is much more powerful.So anything i can mod, or maybe an app i can use to boost the brightness?Even in cloudy weather outside, i can't see a thing, it's like the phone is off.
[Touch Pro2, Tilt 2 Android Development] numero9:
Phone is running pretty decently under the new kernel just posted yesterday. One big issue I still have is updating from the Play Store though. It seems like my updates are always stuck "downloading" and the phone will reboot after trying to run the updates, then when checking the status nothing new is installed and all the up datable apps are still waiting to be updated. This goes for both automatic and manual updated apps. Any ideas on what to do to make upgrading a bit easier?
[Touch Pro2, Tilt 2 Android Development] moparfreak426:
how does one speed up the uber laggyness of Android on this device? rhod500....
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Make sure you're running the best sd card for the build, don't bog it down with a ton of apps (if you want state of the art cutting edge you're on the wrong device) and take a glance at the speed tweaks thread.... there's plenty of stuff to do to make it a bit snappier. I for one am pretty happy with my TP2 running android, def not uber laggy (WTF does uber even mean????)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You still haven't posted any logs.

No clue what made FRX06 work better, but that's really, REALLY old. What kernel were you using? You can try using it on this build, I can guarantee you'll have all sorts of issues (like audio, would not work).

You said brightness is max in WinMo, I asked if you disabled auto backlight... Oy.

Are you using manual brightness or auto in Android?

Please, take some time and don't ramble. Just answer the questions I ask.

Wifi or 3g?

New data.img fix the issue? Obviously it'll wipe out all your apps installed, but I'm curious if you have an ancient data.img or ancient app backups that you're restoring ancient data from as well... I've had issues with that, so I always make sure my Titanium backups are current if I even want to think about restoring from 'em ;).
[Touch Pro2, Tilt 2 Android Development] mowglilp:
"You said brightness is max in WinMo, I asked if you disabled auto backlight... Oy.

Are you using manual brightness or auto in Android?

Please, take some time and don't ramble. Just answer the questions I ask."

Please take some time and pay attention to what i'm saying, i'm only asking for some help.If brightness is set to max, that means auto backlight is disabled.Both in Android and WinMo....Oy.

When i first boot android brightness is great, even in the load screen, after android loads up it still looks good, until i push the power button and to enter stand-by and then start it again.After that, brightness never recovers to maximum and i think it has something to do with the fact that the screen light turns off in 2 stages if you don't press anything.It also staggers when i push the power button, both to turn it on and off.Screen goes dark first but there is still some backlight adjusting, i have to press the power button again to just put the phone in standby or power it up.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
How can I assume that you've disabled auto backlight in both OSes when you didn't state that clearly? If there's one thing I've learned at work and on the forums, it's never assume. People do all sorts of insane things, never ceases to amaze...

No clue, I don't have that issue. Probably another RHOD100 AUO panel problem. Did you post any logs? How many kernels have you tried? Have any of them worked? You said it worked fine in FRX06, what kernel? If you could provide logs from it working and not working that would be ideal.

Either way, you haven't posted any information to go off of, just a lot of drivel about how it's not working. Without logs, or at least detail on what you've tried to do to fix it (which kernels you've tried, etc) then no one can help you.