yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] sykosoft:
So far, so good, but I'm currently travelling, and this in the middle of a large city. I'll know for sure when I return to spottier areas of signal (but, it at least has not lost signal requiring a reboot in 2 days).

Michael
[Touch Pro2, Tilt 2 Android Development] sykosoft:
I have not yet had any repeats of the issue where I was required to reboot in order to get a signal back. It loses signal occasionally, but gets it back without any intervention (this is very good, it wasn't doing this previously).

Now that it's not constantly signal searching, battery life is acceptable (though still lacking in comparison to say, Windows Mobile). All in all, the new RIL works well for my use case, but I am unable to test it on a CDMA network at this time.

Michael
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Wow, that's awesome. As usual, highlandsun swoops in and saves the day. Nice work on compiling that too sykosoft.

This is great! I love seeing this pretty much nearly feature complete. I still do pine for ACL's battery driver, but it seems like that might not port over to 3.x so well...
[Touch Pro2, Tilt 2 Android Development] sykosoft:
I've actually been looking (high level) at porting the battery driver over (no promises). Why do you say it won't port over well?

Michael
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
It's well above my pay-grade, but I think detule said something about the battery driver changes pretty significantly in .39+.

Of course, that could all be leftovers of SCBS... which probably should be removed from the kernel side as I don't think anyone is using the userland piece of that software anymore.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I swore that Detule said it would be an easy port, but wasn't going to do it right away as he felt ACL deserved to have time with his build being the only one with the code as he wrote it.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
He said that BEFORE he looked into porting it... IIRC.

Hopefully he chimes in, as I am referencing my horrible memory.
[Touch Pro2, Tilt 2 Android Development] detule:
Both are correct.

The battery code in +.39 is different than .27.

Porting acl's battery driver should be easy, though I still hate to do it for the same reasons as before. Though I've always tried to give credit where credit is due, I feel like at some point kanging is still kanging.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
ACL has never had a problem giving permission when people ask. You've worked with him enough, I really don't think he would care if you ported it...

Just my .02. I can always shoot him an email to pop in here and grace us with his presence :p.

I see it from a perspective of 'completeness'. Just something to polish it all off... put the nail in the coffin if you will?

I guess there are still things like tv-out and BT isn't so hot. But meh. The battery meter is more of a 'core' thing, and honestly that patch to 3.x would mean people would have no reason to run .27 anymore. Isn't that reason enough? ;)
[Touch Pro2, Tilt 2 Android Development] sykosoft:
I did not know the reasons why it hadn't been ported. I was under the (mistaken) impression that the work wasn't meant for just one build, but was available for anyone who desired it (giving complete credit, etc, abiding by relevant licenses, and the like). I will refrain from doing anything until I hear back from ACL.

Michael
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I think that the issue is that detule did not want to reuse code quickly rather than ACL wanting to limit it's use. When I asked about offering up mods to OMGB over on the PPC forms ACL

said.

"No, in the beginning we didnt want this because of we were developing. So obviously no one would want to contaminate the precious logs with something unrelated. So I think now its safe to let the community run wild since unless its something major, i really wont release another omgb. Also in order to carry the Label OMGB i tried to stick as close as possible to the original source and give respects to the omgb team. "

So I think he is ok with the community using OMGB code (with due credit of course). After all that is the whole point of open source. Give credit where credit is due, and then make things better for everyone. :)

I guess we should have arrrghhh get ACL in here to settle the matter once and for all if there is still a significant doubt. At this point, and with all the chatter I don't know of anyway that ACL isn't getting the credit. :)

Oh, and if you do decide to patch it up, could you try to use the 3.3.8 kernel? I bet the needed changes are almost the same. That would be even sweeter!
[Touch Pro2, Tilt 2 Android Development] sykosoft:
I'll wait to hear from ACL.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Sounds like it is time. :)
[Touch Pro2, Tilt 2 Android Development] [ACL]:
Sup fellas.. you know what happens, if you say ACL three times then i'll show up :-p

So this is about the batt code? I say go for it and port it over. Unfortunately it's not 100% but its enough to work for us. I think you have given me more than enough credit just by mentioning me so go on and get that bad boy over to other kernels. The linux-msm elders would have wanted it this way.. :)

I have to admit, it was tons of fun porting it over. I still have 4 pages full of math function and addresses during the reverse process but I'm glad we have something with some accuracy.

best of luck everyone.. :cowboy:
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Thank you very much. You are awesome!

Ok Sykosoft and Detule we have it from the horse's mouth so to speak. Blessings and permission granted.
[Touch Pro2, Tilt 2 Android Development] sykosoft:
It will probably take me much longer than it will detule, as I'm not yet up on the changes between 2.6.27 and 3.x (a lot of things got moved around by the looks of it). I'll be looking into it, but if detule wants to get it done, I imagine it will happen very quickly.

Michael
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Well Detule did say he was traveling for 3 weeks, so he might not have access to be work on it. I guess he will have to chime in on that. I wish this was not way above my pay grade. Maybe when I get done reteaching myself cell biology for a potential job I should try building out a dev box to compile some rhod kernels with. Either way, my eternal thanks to anyone who spends time on this.
[Touch Pro2, Tilt 2 Android Development] milda25:
Is this RIL also applicable for NAND OMGB 2.3.7? Once installed via CWM recovery I got repeated cycle restarts on the splash screen with a burning android during the boot. What's wrong? Thanks in advance for for your help.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
There are a lot of differences between the builds. I personally wouldn't suggest trying to mix RILs as they are mostly build specific. The two ROMS don't even use the same kernel.

For your issues with OMGB you would be best served by asking in that thread.

Also we have no idea about anything you have done. So providing more info like what kind of phone you have, and the trouble shooting steps so far would be very helpful (read mandatory).
[Touch Pro2, Tilt 2 Android Development] boneskid1:
i am flashing this build as i type but for those that have used omgb and this gbx0* which is better performance wise? my battery already is good but i need it to be somewhat speedy.

Thanks,

Boneskid1
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Performance is about the same either way. I think the 3.x kernels are a tiny bit faster. There are no huge optimizations though. I prefer GBX0* because I want native tethering. Speedy, well you could try the following the optimization thread. Try both, and see what you like.
[Touch Pro2, Tilt 2 Android Development] boneskid1:
i cant seem to run set cpu on either build it freezes and i have many of the optimizations set up already like supercharger and such
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Logs please. SetCPU should work fine.
[Touch Pro2, Tilt 2 Android Development] Caldair:
As long as boneskid has applied the kernel update from post 1... right??
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Yep, got to have the newest kernel update to get the overclocking to work from an app.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
That's just for manual backlight adjustment AFAIK...

I would think this stuff has made it into the flashable ZIP, but perhaps not? Either way, I don't think that would be his issue.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
You have to have the 3.3.6 kernel update in the first post to be able to overclock this rom. Before that the overclock patch was not applied.

http://bit.ly/JymX2o

The auto backlight issue was never resolved. It was just set to allow for manual adjustment around the 3.3.4 kernel.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks, I was perusing thru the thread to jog my memory... got a little bored after 8 pages :p.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
No worries. :) To much for any one person to keep track of it all.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Anyone make progress on this?

What do you do?

I'm finding that OMGB does in fact have audio routing issues (unless perhaps I missed a kernel update, I'll doublecheck that...) on ringer.

This ROM is great, but the issue with the SD card failure is pretty prevalent. I'm wondering if it's something residual from being a HaRET build previously...
[Touch Pro2, Tilt 2 Android Development] wizardknight:
[Fix] Micro SD card unexpectedly removed error

My fix. Might work for you.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks, not sure how I missed that... :o

Edit - now that I read it... crap. I was hoping it wasn't something like that :p. I've tried a couple of different cards/brands, and I never use a card reader per se... It's a little USB-to-mSD plug. So you slide the mSD card in the back and the other end is just a USB port.

I have a couple of these, and a couple of laptops with SD readers... I'll see if anything makes a difference.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
The usb-to-mSD card read plug thing is the kind of device I had. I highly recommend junking it in favor of some built-in or high end reader (at least for formatting). It resolved 95% of these kind of errors for me when I started using the on built into my lcd panel attached to my pc. The cheep ones I got off ebay seemed to be good for a month or so of reasonable use, then I would see things like this happening.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Did you have any luck with your sd card problems? I picked up a used tp2 that seemed to be working fine, and it is now doing the unexpected removed sd card thing. :P I tried formatting the cards, and using cards that worked ok in my other TP2. I have found 1 old 1gb Sandisk card that it does not hate. For some reason all of my 8,16, and 32gb cards keep removing themselves. It also only does it after it has gone into sleep mode. Is there anyway to find out what reader is in these things, and see if there is an updated driver for android?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm... I don't know, other than I don't experience this issue on other ROM's.

And no, unfortunately I did not find a fix yet. Haven't dug that deep either to be honest...
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I did come across an issue that effected other roms. Basically the sd card driver response time by default and some standard was set to 250ms before it times out. However for some cards they need just a little bit longer, and when patched for more ms it resolved most of the issues. I wonder if that could be related.

Look at the comments line 537
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Detule. Any chance that you could look at the timeout setting on the sd card? Maybe compile a kernel where the timeout is bumped up to 500ms from the 250, so we can see if it resolves the sd card removed issue?

Thank you. :)
[Touch Pro2, Tilt 2 Android Development] detule:
There really is no time-out setting per-se, to be tweaked. Oh, I see what you are talking about.

I was curious about these reports when I was using my tp2, but I never could reproduce them so it was hard for me to debug.

One of you guys that has a vested interest will have to sit down and try to figure this out. What better way to learn about kernel/android hacking than to have an open problem to tackle?
[Touch Pro2, Tilt 2 Android Development] imohtep:
Hi master Detule, exist anyway for go into the EPST config in any rom NAND? i do this question for change the service number, well i roll back to winmo becase the battery life for me with data on was 4 hours life left; i hope you can find any twaeks for this, thanks for this great work..! :good:
[Touch Pro2, Tilt 2 Android Development] wizardknight:
It will not work. You have to have a Sence based rom for EPST to work. We have an AOSP I believe. :( Sorry.

So you will have to do a nandroid backup and load WM to get EPST changes loaded, and then load android back again.

---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------

Is there a how-to guide to building out these nand kernels anywhere?
[Touch Pro2, Tilt 2 Android Development] detule:
Same instructions as building the xdandroid kernel (make sure you use 2011.q3 codesourcery toolchain). To create a flash-able package you'll need to splice my boot.img and append the new zImage you compile to the ramdisk.

There is a bit of a learning curve, but the beginning is the steepest part.

P.S. You have more logs of this failure? One where you are not using wifi. Also an older post of yours seemed to suggest that building an gbx0c-for-sdcard card, and using that card for nand solved your problems.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Sadly it does not sound like a learning curve, but a a learning cliff for me.

I have two recently purchased TP2 that both show this behavior. If I use a SD based android I do not see the sd card removed error. If I use the nand version all but one card I have causes the issue.

Ok. Pulled out the spare TP2, put in my 32gb cl4 sandisk card that is very good at causing this issue. Booted, let it go to sleep, and then I got the sd card removed error (vs the unexpectedly removed error I see sometimes)

I put in an 8gb card I have that has slightly less issues, and did a get logs. Let me know if this has what you need, or what else I can do.

I was able to get an unexpected removal error log too. So I uploaded that too.
[Touch Pro2, Tilt 2 Android Development] detule:
PM'ed.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yo... I can only assume you PM'd him the kernel you threw me. It's been running solid for a few days now - but the battery is pretty awful. It's not charging to 100% (even tho it says it is) and the phone just dies at random...

So perhaps one last hurrah and port ACL's battery code? I'd love to do it, but I'm sure I would be so very lost... I'm getting the hang of building kernels and making boot.imgs/flashable zips... but porting battery code is a bit above me at this point.

I know ACL has given his graces, so no worries there mate. As he always said, we're all on the same team...

:fingers-crossed:
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I have been playing with Bluetooth lately. I noticed that if I left the Bluetooth running, and rebooted the phone that it would hard lock during the boot animation. I had to wipe and reload the phone to get it working again. Is this a known issue, or had anyone else seen this issue?

*edit*

Been working on the problem some more, and I found that if the ril update is not installed everything boots as expected if the phone is rebooted with bluetooth enabled. I tried the one from the first post, and the updated 8-15 one also. Same results.

I would be happy to pull any logs I can if someone could tell me how to get them from the phone in this state.

Do CDMA devices have to have the ril update? I am not that familiar with it.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Hmm. Glad I didn't try it on my 210 then. (Truthfully I'm specifically waiting on the backlight controls before I flash. I actually make a LOT of use of it.)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Honestly posts like this are really quite useless. This is a developer forum, I don't really care that you didn't try it out. I only care if you tried it out and are willing to help...
[Touch Pro2, Tilt 2 Android Development] erick29:
No, did not see any flying droids, and no boot animation, just stays on black screen, here is what happened, after passing the LK/mini pooploader screen and then some flying text and after that stays on black screen..that is for without the kernel update..

And with kernel update it stays on LK/mini pooploader screen.

I restored my back-up now..

Sorry can't post some logs..

Edit, tried again: stucked on black screen but when I slide the keyboard I saw that there's light on the keyboard..
[Touch Pro2, Tilt 2 Android Development] milda25:
Tried it last night, but no success, same problems reported in my previous post.

---------- Post added at 08:51 PM ---------- Previous post was at 08:44 PM ----------

Hi Detule, yes, I wiped data/cache, Dalvik cache, Battery stats and all partition (/system, /data, /cache) formatted. All using the Recovery mode.

In any case thanks for your work.

---------- Post added at 08:57 PM ---------- Previous post was at 08:51 PM ----------

Device is essentially starts, even if you can see only black screen, the background is still working, but many sets FCs, the display turns on one of the twenty attempt. If you're patient enough, you'll see that sometimes light up the four front buttons. Or eject the qwerty keyboard, you'll see that is backlight, so the device at that moment lives, though in a strange state.
[Touch Pro2, Tilt 2 Android Development] detule:
Hey no problem, thanks to your radio log and good log collecting we have a very good idea (try a new ril for gsm)....Should have an update later today or tomorrow. Thanks again for your logs.
[Touch Pro2, Tilt 2 Android Development] detule:
In first post: checkout ril_update.zip

Probably all should update but absolutely critical for GSM folks -> should get you off the ground.

Thanks to walter79 and especially milda25 for the logs, and to rpierce99 for testing the new ril.
[Touch Pro2, Tilt 2 Android Development] n2rjt:
This build works on my Tilt2. Details follow since they might help someone to at least know what not to do at a couple of places.

Using Tilt2, which I've pretty much retired from active use.

Two weeks ago I installed WinMo 6.5 + GBX0C Haret build.

Tonight I went back to this NAND GBX0C build.

I copied the files to sdcard, and installed RHODIMG, then cleared the partitions and installed cwm_recovery.img. When I tried to "fastboot erase data" it said no such partition. So I went ahead without that step <mistake, as you see later>.

Then after rebooting into recovery and flashing GBX0C, kernel update, and ril update, I rebooted. After the blue linux boot screen, then the white-on-black linux screen, the screen went black. No boot animation. I thought it was dead, and hooked up USB to capture logs. I captured dmesg, then logcat where I saw that it was busy populating the dalvik cache. So I patiently waited, and it eventually gave me the lock screen. Good.

But I looked at the dmesg I had captured, and saw many very sad yaffs errors. So, not trusting things, I rebooted into recovery and erased data using recovery. Then I rebooted. Again no boot animation - I actually never see that on this build unless Android restarts.

WIFI works for me. The screen is a bit dim, and as reported in the first post, brightness control doesn't work. I tried to switch to Tilt2 keyboard by cp /system/etc/keymaps/tilt2/* /system/etc/keymaps/default, but that is obviously the wrong way to do it since it didn't work.

Screen orientation switching works. I haven't tried GPS or GSM yet.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I think there is a typo, and "fastboot erase data" should be "fastboot erase userdata". That might be what caused the no partition error.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Initial observations. Installed onto my TP2 cdma with no issues. Was able to call out no issues. Found that when the system first booted the brightness level was at 100%, but as soon as some function caused the lcd to dim (or turn off) it stuck at low light settings. Reset function hangs the unit, power off rebooted it. Wifi is good. My screen needed to be calabrated so I triedhttp://rhodium-nand.googlecode.com/files/tscalib.apk, and it seemed to work. Overclocking seems to be disabled. Tried to get a gps lock, but didn't happen. Didn't spend to much time trying. Did try leo's agps injector too. Good start.
[Touch Pro2, Tilt 2 Android Development] walter79:
With updated ril rom work on my Rhodium now. Thanks
[Touch Pro2, Tilt 2 Android Development] walter79:
To get a log you need to boot your phone with data or wifi and GPS enabled.

gps.conf is set to north-america.

This is my europe configuration.

NTP_SERVER=europe.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
[Touch Pro2, Tilt 2 Android Development] detule:
Correct

Incorrect.
[Touch Pro2, Tilt 2 Android Development] walter79:
I changed my post you are right.

What are your next steps for 3.3.4 kernel?

Maybe this:

- backlight

- battery

- bt
[Touch Pro2, Tilt 2 Android Development] detule:
This already "works" for me to the extent that bluetooth works in .27. I can certainly enable it, and after much pain, pair with a device as well.
[Touch Pro2, Tilt 2 Android Development] walter79:
Ok. For me it did not work well. Can`t pair or sent/receive files. I can sent you logs if you need it.
[Touch Pro2, Tilt 2 Android Development] erick29:
Hi just want to report, I tried the ril update on my Rhod210, the result is still the same stuck on black screen..
[Touch Pro2, Tilt 2 Android Development] detule:
You must provide logs (dmesg, logcat -v time, logcat -v time -b radio) if you want to see any progress.

Having said that make sure you wipe /data/cache. Also on gsm it seems you see no bootanimation -> so make sure you try waiting it out, that first boot can take a long time.
[Touch Pro2, Tilt 2 Android Development] n2rjt:
For me GPS is good yet slow, GSM voice is perfect, but data doesn't work. No 2g, 3g, or H indicator, no connection. I will regression test winmo and haret to be sure hardware is good; I haven't had a sim card in this phone for a few months until this test.
[Touch Pro2, Tilt 2 Android Development] djcrosstunez:
It is booting now on rhod100! Yeaah, gonna test it now. Will provide logs later!

Nice work again!
[Touch Pro2, Tilt 2 Android Development] djcrosstunez:
First impression, speed is oke, crash on wifi first time, works oke now, but no data:(. back to GBX0C for now..

http://pastebin.com/8kchExDv
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
We should probably remove that. I've never had an issue installing fastboot, and then doing a factory data wipe/reset after flashing the ROM.
[Touch Pro2, Tilt 2 Android Development] erick29:
Yes I did wiped all data/factory reset, cache, also dalvik-cache, how long would that be the first boot? Coz I've waited for more than 20 minutes..

thanks for hardwork..
[Touch Pro2, Tilt 2 Android Development] walter79:
max. 10 min