yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
*scratches head* I'm somewhat confused. Is it something with my RHOD500? On CM7 the power button(screen on/off) on press brought up the shutdown, reboot, etc dialog (as opposed to having to hold it down). I figured if I switch to this ROM, that issue wouldn't persist. Seems I was wrong. I know you can set it so the End button doesn't turn the screen off, but what about getting the power button back to its old setup?

I'm also still struggling with the same SD Unexpectedly removed, etc, crap. I can't find my 2GB either, but the SD was working just fine on GBX0C (sd version). Once my brother get's back with my SDHC reader, I'll give it another go with HPUSBTool (dad's laptop can read SDHC via built in reader, but won't label it as a USB device, ergo the format tool doesn't see it). I'll log it later. My guess is that it's the same error from CM7, but you never know

The usual Wifi problem is persisting for me too. Fire up wifi and get kicked to the boot animation. I can't seem to avoid this issue no matter how hard I try lol. Thankfully I had an old nvram.txt lying around, so at least that issue has been sorted out.

---------- Post added at 09:47 PM ---------- Previous post was at 09:42 PM ----------

This is awesome. Our hardware could definitely benefit from something like this.
[Touch Pro2, Tilt 2 Android Development] sykosoft:
My wife and I both own RHOD400 (on Sprint in the USA). We're currently travelling abroad, and have both flashed to NAND GBX0*. We are both currently using our RHOD400's in GSM Mode. I have a list of issues we're both experiencing, I will list them below. If they are known issues, then I'll simply wait, if they are not, I'm happy to getlogs, and any information necessary.

1. In GSM mode, if the phone loses a signal, quite frequently, a reboot is needed to get it back. It is usually the only way to get a signal back. We've tried changing modes, airplane mode is attempted, but it too has a problem, detailed below, we've tried scanning for networks. Only a reboot fixes it.

2. If we try to turn on airplane mode, sometimes it will enable (plane symbol appears where signal bars used to be), sometimes it does not. If it does not, no amount of trying will get airplane mode to come on. A reboot is necessary, as there is no way to restore signal otherwise. After reboot, it comes up in airplane mode, which then must be disabled.

3. Quite frequently (sometimes several times a day), the phone switches network mode. Sometimes it switches to ev-do, sometimes it will switch to wcdma only, sometimes wcdma pref, where we choose either GSM only, or GSM/WDCMA auto. It never stays selected for more than a day.

4. Similarly, use only 2g networks will not stay selected.

5. Battery life when the cell radio is enabled is very bad (sub 12 hours). This is with no syncing, strong signal, etc. Perhaps (due to mode selection) it's trying to look for a 3g network constantly (there is no 2100mhz umts here). With only wifi on, the phone lasts more like 2 days.

6. Battery charging is very odd. I can plug up my completely dead phone, and it immediately reports 96% charged when fully booted. It will report charging/charged several times while charging. (I couldn't find a concrete answer, did ACL's battery charging code make it in this yet? It seemed to work better on OMGB).

If these are known issues, I'll leave it alone, and hope for a fix. If they are not (as perhaps there are very few RHOD400 running in GSM mode internationally), I'll be happy to getlogs.

Michael
[Touch Pro2, Tilt 2 Android Development] Muhownage:
I started using this rom (yay working camera with RHOD100) but it looks i need some help with the german keymaps.

As there are no keymaps supplied here i tried to flash the zip from the OMGB thread (http://xdaforums.com/showpost.php?p=26098358&postcount=566). flashing gave no error but Keymaps are still the american one (switched y/z etc).

then i even tried to overwrite the files via hand in total commander (with root access ofc). but this gave me the error that su could not create the files either.

any help pushing me in the right direction would be highly appreciated :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You can modify the .zip file manually, then reflash the modified ROM...

However, I find it odd that you weren't able to flash or manually replace the files on your own. Try over writing using ADB, and rename the old file. Make sure you reboot the phone after making such a change.
[Touch Pro2, Tilt 2 Android Development] detule:
The keymaps are over-written on every boot (alas, this is a left-over of the way we do things in haret).

I think I made it so that after the keymaps are copied over, the init script parses /system/etc/init.gingerbread.conf. So with a few shell script lines in that file you could force your own keymaps/layouts.

Hope this helps.
[Touch Pro2, Tilt 2 Android Development] sykosoft:
Any thoughts on my issues listed above? Are they known issues, or would you like getlogs? Also, do you have a donate link?

Michael
[Touch Pro2, Tilt 2 Android Development] detule:
Michael, no donate link (but the thought counts!)

Anyway, hard for me to debug your issue since I can't throw my 400 in gsm mode. It's likely an issue with our RIL, and the guy who wrote our RIL has moved on to another device. Logs are always good but unlikely to lead anywhere unless another member of the community steps up ---> starting to realize that a build maintained by a single person has no chance at ever being 100%.
[Touch Pro2, Tilt 2 Android Development] jakiej:
thanks for a great rom! but my battery life is not good (<12hours)

i tried XdaLedRegime.apk, Led regime 1, and the led is always amber (awake). getlogs is at http://pastebin.com/vXzXb0Su

can somebody take a look and help me improve the battery life?

thanks! btw, my device is a rhod210 and is my daily use phone.
[Touch Pro2, Tilt 2 Android Development] detule:
12 hours is not necessarily bad for this device. Your log shows your device is indeed suspending - perhaps you are using the wrong version of XdaLedRegime? Make sure you are using this one.

Also, it didn't look as if you were using wifi in your log, but this build (GBX in general) will not suspend when wifi is on.
[Touch Pro2, Tilt 2 Android Development] Slipdoozy:
battery life?

i use http://xdaforums.com/showthread.php?t=1218458

all credit goes to arrrghhh on this one

and

https://play.google.com/store/apps/details?id=com.elsdoerfer.android.autostarts&hl=en

i use this one to STOP all the stupid apps from running whenever they want. cause when "I" want the app to stop it does and wont restart till "I" say so lol.

and

http://xdaforums.com/showthread.php?t=1621808

i understand this one is for DInc. but it works for our phones and i get easy ~24 hours use.

good luck with above things.
[Touch Pro2, Tilt 2 Android Development] jakiej:
Thanks much for checking it for me!

i am not using wifi and i was indeed using a wrong version.

in window, the phone lasts about 4 days though. is there some new kernel that i can try?

i'll check those out, thanks!
[Touch Pro2, Tilt 2 Android Development] Muhownage:
Thanks that explains why it did not work. But digging that deep was too much for me atm. Also i moved on because of the battery life on my RHOD100DE (1-2 hours till force shutdown. charging 10 min displayed 100% again etc).

Hopefully at some time the battery changes from ACL are ported to the new kernels so i have more roms to choose from (for example camera here works much better then on omgb) :)
[Touch Pro2, Tilt 2 Android Development] argenisaz:
Hi detule,

I can't find the file init.gingerbread.conf. I've looked in the zip file and on the phone.

Am I missing something? :confused:
[Touch Pro2, Tilt 2 Android Development] PeteBest:
This build is looking great, sadly I'm still having problems on my RHOD100 with data connections. I've performed a fresh flash after task29 with main zip, then ril, then updated kernel.

Then after booting, I went to internet options and added my apn, disabled data and roaming data, then re-enabled both. No luck, so gave it a reboot and no change :( Getting full signal strength, but no data icon so no data connections work. Wifi works as expected

Getlogs file attached just incase anyone needs it, any pointers would be greatly appreciated! All earlier talks in this thread seem to indicate this would fix it, but it's not working for me :(

/edit smaller getlog attached, just powered on phone, went to settings, disabled and re-enabled mobile data and data roaming then tried opening browser to see if it worked

/edit2 really weird, just received a call, looked down afterwards and data was suddenly working.. Ah well, I'm not going to complain! Thanks for all the hard work with this build guys, looks like it's working well enough for me to dump WM!
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I know that with my RHOD400 on Sprint I have to set it up with data working on the WM side before I install GBX0* otherwise my data will not work due to the lack of it's ability to update profile. Makes swapping my phones out a pain.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm curious if data works for you in other instances PeteBest in light of this information...

Does it work in WinMo? Other Android ROM's?
[Touch Pro2, Tilt 2 Android Development] PeteBest:
This is the first Android rom that I've had data problems with, just very weird it suddenly clicked in after I got a call. On the NAND side omgb didn't work properly with my carkit Nokia CK-7 BT, just a loud screeching noise. Not sure if the CM7 is meant for the RHOD100, but the launcher kept crashing continually so it wasn't really usable. I'm on Vodafone in the UK, so luckily I don't have to deal with any of these activation type issues that verizon people suffer with.

With haret builds like GBX0C I had some speed problems and my BT was a bit dodgy, it would work fine for a few days then simply refuse to connect etc. Didn't really need WM, so was just searching for a good replacement that had BT and data, looks like I've finally found it with this rom :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
BT is flaky in general. I seriously doubt BT will perform any better here than OMGB.

Good luck.

06-26 16:30:11.489 D/RILJ ( 1463): [0065]< SETUP_DATA_CALL error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
06-26 16:30:11.529 D/GSM ( 1463): [GsmDataConnection-1] DcActivatingState msg.what=EVENT_SETUP_DATA_CONNECTION_DONE
06-26 16:30:11.529 D/GSM ( 1463): [GsmDataConnection-1] DataConnection Init failed com.android.internal.telephony.CommandException: GENERIC_FAILURE
06-26 16:30:11.529 D/GSM ( 1463): [GsmDataConnection-1] DataConnection setup result='Other error' on cid=-1

I would try airplane mode on/off, and a reboot if that doesn't fix it. Still broken? Makes no sense as you said it was working before!
[Touch Pro2, Tilt 2 Android Development] PeteBest:
Thanks arrrghhh, kinda forgot about trying airplane mode on/off will remember that for next time it decides to go weird. Thanks for the pointers!
[Touch Pro2, Tilt 2 Android Development] detule:
You have to create it. Or better yet, steal it from the haret build (it's in /conf) and add your custom command in the "custom shell commands" section.
[Touch Pro2, Tilt 2 Android Development] detule:
Sounds like you may have this resolved or are on your way. At any rate, one of the consequences of the new SMD driver in these kernels is that sometimes, data takes a while to come up. I had boots when it took better part of ten minutes, but it_did_always come up. Nothing in the log you supplied, other than the failures that I see on my device, right before it actually comes up.
[Touch Pro2, Tilt 2 Android Development] Eric Z:
Yes I can comfirm that data is not always come up right the way, but it will ALWAYS come up after sometime. 1, 2, 5, 10 minutes are all normal for me(in most cases around 1-3 minutes). Both on NAND as well as on SD. Some times I can't even get GSM signal connection(just phone signal) before the data shows connected.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I was trying to use the last tweak you listed, but step 3 requires a file to be created in /system/etc/init.d. I can't seem to find this in our rom zip. What did you do?

Thanks. :)
[Touch Pro2, Tilt 2 Android Development] PeteBest:
Yep, after a few days of usage, I have to confirm that you're right again arrrghhh. Had several hard lockups requiring battery pulls when going in/out of the BT menu after enabling it. A few garbled calls and several times where it just refused to connect no matter what I done. Problem is my BT is a built in carkit and I've had to pull over a few times and kill the ignition just to get it to talk to the mobile again

Reluctantly, I've had to go back to WM. Will keep a better eye on the haret builds to see if any progress gets made on BT.
[Touch Pro2, Tilt 2 Android Development] Caldair:
If you want to play around with that sysctl.conf there is a free program from the market called System Tuner by 3C that allows you to tweak many of these settings (haven't actually gone through to see if all the settings from those scripts are in it, but there are many). Tweaks have to reapplied at boot, there is a setting to accomplish this.

Actually this is quite a handy little tuning program, allows tweaking OOM limits, SD readahead cache, you can clear your caches, OC, uninstall system programs, freeze programs (like titanium), control startups, and even change/remove the receivers that cause programs to start when certain events take place (like stopping google messaging service from starting everytime the network state changes). Has a task killer too, but I wouldn't recommend using that feature, just change your OOM settings. It has replaced a couple of other utilities for me.

Didn't know what to make of Sysctl.conf tweaks until i read the thread that Slipdoozy posted, now I have a starting point at least

Credit for finding this app goes to teemo who posted it in the Speed Improvements thread!

EDIT: On a closer look at those scripts I see at least one head scratcher: Early in the script there is

vm.oom_kill_allocating_task=[B]1[/B]

... and then later...

vm.oom_kill_allocating_task=[B]0[/B]

So which does he want? on or off? I went with 1.

Also the app that I posted is definitely missing about 4 of those settings for me on SD version with 3.4 modules, but I don't know how essential the missing ones are to the battery gains.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Op. I was hoping you might consider this wish list for an update to your great rom.

The new 3.4 kernel, ACLS sweet new battery driver, and Init.d

I stumbled across this guide for adding Init.d

http://www.neopeek.com/viewtopic.php?f=24&t=6801

Thanks for your amazing work.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
There's not much reason for GBX to have init.d...
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Unless you consider the scripts, and apps that make use of it.;)
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
There are other ways to do it, you know. Ways that don't involve hacking on the boot process. :P
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Yep. That is what is nice about init.d. It is not hacking. You are using something as designed. It works nicely with OMGB. Sadly OMGB is lacking in some other areas like newer kernels and tethering ability otherwise I would be inclined to run it.

Anyway it is a wish list. It is up to detule. If he feels it is beneficial, and has the time I am sure he will give it the proper consideration.
[Touch Pro2, Tilt 2 Android Development] Slipdoozy:
im sorry thought i was in OMGB thread when i added the last "tweak". but the init.d is just a script to tell the tweaks to start from what ive read in that thread. you just have to create a file and put it in that "/system/etc/init.d" place, plus change your Sysctl.conf. ill try and flash this [ROM][NAND] GBX0* + 3.3.x kernel and see what i/it can do. will try to post what i find out. thanks to detule, ACL and arrrgh for there contrabutions to our "old arse" phones.

off topic: With ACL new rom OMGB_rhodium-1.2.3-05072012 i get less battery life than his previous rom OMGB_rhodium-1.2.3-01162012 w/update fyi. So thats why im gonna try [ROM][NAND] GBX0* + 3.3.x kernel before i go back to the older OMGB.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Disable accent mark promting.

Does anyone know where to disable the special key prompt that comes up if you hold down or press the same key on the physical keyboard to quickly. Example if you press the e key you get a screen prompt with all the various e's that use various accent marks. Sometimes I type to quickly and they keep prompting me for what non-English character I want. I would love to know if there is a way to disable it. I looked under the keyboard settings, but couldn't find anything that looked like it might help resolve my issue.:confused:
[Touch Pro2, Tilt 2 Android Development] Slipdoozy:
i too would like to know how to do this. really annoying. seems likes this build does it more than OMGB. must be a setting or a tweak to change. like "hold key for special chracters" 100 milliseconds to 1000 miliiseconds.
[Touch Pro2, Tilt 2 Android Development] sykosoft:
Logs are attached. I'm very hopeful that you can help. I'll be happy to get any information you need, or give you control over my phone with wifi, etc. Kernel mods I can handle, but RIL is outside my area of expertise.

Michael
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I think I found a way to do it. I installed Go Keyboard from Google market and bumped the long key press to 1s. Seems to behave in a fashion I can live with now.
[Touch Pro2, Tilt 2 Android Development] sykosoft:
Anyone have any thoughts on my issues?

Michael
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Unfortunately the previous answer is probably all you're going to get.

It's almost certainly a RIL issue, and the gentleman who kindly rewrote basically the entire RIL (and wrote the CDMA portion from nothing) has moved on. detule, being pretty much what is a one-man-band on the XDAndroid scene, really doesn't have a lot of hope fixing any of the remaining issues on his own.

Good luck. All the code is obviously open and available... If you do fix something, all that we ask is that you provide a patch back :)
[Touch Pro2, Tilt 2 Android Development] sykosoft:
I struggled with it, and struggled with it, but was not able to get it resolved, trying a number of different things. I hated to do it, but I had to switch back to Windows Mobile (an Android phone without a network is basically not so useful). It just loses signal, and NEVER gets it back, you can't switch it into airplane mode, and back out, etc. Unfortunately, the only fix was to reboot, and I was rebooting 10+ times a day. We couldn't rely on our phones at all.

Michael
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Perhaps you should try the OMGB nand build.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
It looks like the code in the RIL for automatic detection of CDMA vs GSM mode is getting confused when the GSM signal drops out, the reaction from the radio is the same as when the phone is operating in CDMA mode.

Probably this particular detection should only be done when the network type is set to GSM/CDMA Auto.

edit: I've pushed a patch for this to gitorious. Don't have a current build env any more, so I cannot provide a test binary here.
[Touch Pro2, Tilt 2 Android Development] sykosoft:
Thank you very much! I'll give it a look. To be honest, I don't have a build environment laying around anymore (and even then, it was for haret). I'm not even sure where all the pieces for the nand builds ARE (which repos to use, etc). Perhaps detule is willing to make another release with this ril update and (if they didn't make them in, I never verified) the ACL battery changes?

Michael
[Touch Pro2, Tilt 2 Android Development] argenisaz:
+1 :D
[Touch Pro2, Tilt 2 Android Development] detule:
I am travelling for the next three weeks, but I should be able to put together a patched RIL when I get back.

The haret vs. nand xdandroid RIL has a minor change - if someone wants to put a patched binary before then I could probably recall semi-coherently what it is.
[Touch Pro2, Tilt 2 Android Development] sykosoft:
I'm happy to setup a build environment for all of this, if you can point me to the proper repos. As I remember it, there are hacks in things like the RAMDISK, and the kernel isn't the haret kernel (so I don't know where the repo for it is). Having not built a NAND build (only the ext2 builds), what else is special? I've got several servers (large beasts) that I (or we, I can provide access) can do this on.

Michael
[Touch Pro2, Tilt 2 Android Development] detule:
No need to mess with the ramdisk/kernel. To build the ril binary, you need to be able to build the gingerbread branch of xdandroid.

I think these instructions should be up-to-date.

Once you get that going, you need to patch the RIL for nand. Otherwise I remember the radio causing kernel panics on gsm rhods at boot. I think what we had to do was to add

at_send_command("AT@BRIC=0", NULL);

in this if-bracket.

Or better yet, just copy that if-else block from ACL's RIL.

Once there, apply hyc's new patch from his gitorious repo.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Could you include the ACL battery code if you rebuild on a 3.x kernel? That would be so awesome. :)
[Touch Pro2, Tilt 2 Android Development] highlandsun:
How strange. I have that added to a local copy in my code, never committed it. Now I don't remember what it's for. Who came up with that change, and why? I don't see why it shouldn't work identically for the haret build.

Here are my uncommitted diffs. Some of these I was working on when I had my rhod210 in Ireland, it seemed there was a stability issue with sending SMSs. Or, the phone would report the SMS failed to send even though it was actually sent.
[Touch Pro2, Tilt 2 Android Development] sykosoft:
Are the pieces under dependencies still needed? http://www.mediafire.com/file/zh095lc3czburai/hw3d-20111216.zip is broken. Otherwise, I'm ready to build.

Michael
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Might want hw3d... Assuming you're planning on building a complete image. You can always get a build env setup and only build the RIL. Although I'm not positive on the steps required to do that... :o

hw3d-20111216.zip
[Touch Pro2, Tilt 2 Android Development] sykosoft:
Thanks, downloading now. I've heard rumors of a newer kernel, are they ready for the primetime (building)?

Michael
[Touch Pro2, Tilt 2 Android Development] detule:
Probably works just fine for haret builds as well, it was just never needed as winmo issues it first.

Think leo folks came up with it to begin with and likely abel spent some sleepless nights before figuring out this is what was needed to prevent a9 form blowing up on boot on gsm rhods running nand builds.
[Touch Pro2, Tilt 2 Android Development] sykosoft:
It I wanted to create a fully packaged NAND build, what are the steps to do that? I'm only familiar with haret building, I'm not even sure which kernel we're using for NAND (repo-wise). I want to add some custom patches to the kernel, and possibly toy with some things like using the linaro toolchain.

(Currently building the patched RIL)

Michael
[Touch Pro2, Tilt 2 Android Development] sykosoft:
New patched RIL attached (no promises, but I see no reason why it wouldn't work as expected).

Michael
[Touch Pro2, Tilt 2 Android Development] detule:
Did you test this - does it fix the issues you were having?

Care to post logs for hyc to see if his patch does what it's supposed to be doing?

The nand kernel repo is here.

Ramdisk should be here.
[Touch Pro2, Tilt 2 Android Development] sykosoft:
Haven't tested it yet, as I had to (until this was resolved) switch back to Windows Mobile for business reasons. I intend to put my Android build back on my phone within the next day. I'll report back then.

Michael