yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
"good enuff to run daily" - it's a TESTING thread, so that's on you. I did run it daily. You should know how to pull logs and report issues tho... again, TESTING thread.

v6 supercharger works fine.

"has anyone tried build prop tweakz"

Funny guy... Such as? This sounds dubious to say in the least. I don't exactly encourage people to muck around in the build.prop, and I don't see anyone else recommending that either. Never a good idea to just blindly change crap in there (or anywhere for that matter) without knowing what it does.
[Touch Pro2, Tilt 2 Android Development] dswaggz:
They have a the thread for it an I read a post by a Kaiser dude who used some only reason I asked an what ever happened to magdlr

via SWAGG GANGG ™
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
MAGLDR is closed source... so who the hell knows? Why are you asking about it. Please don't derail this thread...
[Touch Pro2, Tilt 2 Android Development] Raimon93:
is there a fix for the rhod 100 camera?

Verstuurd van mijn Touch Pro 2 met Tapatalk
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes. I don't think it's been implemented yet... Not sure where ACL left that patch, I know he was trying to get it in so it wouldn't break every other device in the process.
[Touch Pro2, Tilt 2 Android Development] hashtowent:
http://xdaforums.com/showthread.php?t=1485848

just few treaths under this one!

for me it works sometimes, sometimes it kills my android so that i have to remove battery =)

flashed it under cwm! version 1a
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Derp, I don't know how I forgot about that thread. Thanks!
[Touch Pro2, Tilt 2 Android Development] hashtowent:
for me rhod100, bluetooth works but it is not staple (so it seitches on and off automatically :( audio route for musik and youtube is working (with these interrupts) but calling is not supported atm. no sound.
[Touch Pro2, Tilt 2 Android Development] Bones2374:
Yes, V6/V8 256HP Super, OOM, and Kernelizer is a must, its so much more snappier now. However, 3G Tweak (tried 1-4 and flashed latest radio) made my connection so slow, almost unusable, and it also broke WiFi profiles too everytime I tested, so I just Uninstalled 3G tweaks and all returned to normal. =)

As far as OMGB NAND itself, everything has been rock solid except for the camera. (Known issue) Cam dies after 1-3 uses, then battery drains in a few hours (nosleep, orange LED, hot battery) unless you reboot. I've been using it as my daily ROM for three weeks. I LOVE IT so much that I've started buying Market Apps, and I'm going to donate to ACL & XDA as soon as I get paid.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Where does this stand stability and functionality wise compared to GBX0B? The reason I ask is my TP2 is my phone, so I booted Android from the SD in case I needed to switch back to WinMo for some reason. I suppose the only things I really care about are battery life, GPS, Phone/SMS, and CDMA Data
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Those items that you care about are functional. However, if you still feel WinMo is needed, this may not be the best experiment..

I'd at least give it a shot.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Originally, I kept WinMo in case Android had any mission critical bugs. That hasn't been the case in sometime and I find it a hassle to wait for WinMo to boot before getting into Android. (I have that quick boot thing that selects Android for me but the whole booting process still takes a considerable amount of time). If everything is functional then good. Suppose I should get a tad more specific though. How is the overall battery life? Charging too. That was always an issue for me (had to leave the phone powered down to get a proper charge). Haven't heard anything so I can only assume it still isn't great.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
One thing we don't have yet (unless this has changed and I missed the memo) is warm injection for GPS; that still requires booting to Windows in order to use QuickGPS. Since GPS is important to you, that's something to think about. You can still use the GPS under Android without using QuickGPS first but it may take some time to get a lock.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Actually, I believe that works now. http://forum.ppcgeeks.com/android-tp2-development/149104-testing-cdma-rhod-agps-xtra-support.html
[Touch Pro2, Tilt 2 Android Development] walter79:
Is it possible to disable LED for sleepmode in next build?

Or is there a way to disable it with a different lib (lights.rhodium.so) ?
[Touch Pro2, Tilt 2 Android Development] walter79:
It works on my Rhodium 100

- copy gps.xdandroid.so /system/lib/hw and rename to gps.rhodium.so

- enable GPS

- enable data connection

- shutdown phone and pull battery

- wait min 10 min

- replace battery

- boot phone

Update:

This way works for me.

- replace the gps.rhodium.so

- install LeoAGpsInjector_v0.5.apk http://xdaforums.com/showpost.php?p=16384028&postcount=1907

- reboot

- enable data connection or wifi

- enable GPS

- run LeoAgpsInjector
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Oh REALLY. That's some good news and I'm going to have to try that out on my 210. I'm not running omgb because I DO still want my WinMo dual-boot around, but if it works on GBX0B from SD I'm all over this. I'll give it a try and report back later today.
[Touch Pro2, Tilt 2 Android Development] walter79:
How can i fix this on a froyo nand build?

everything is working only wifi is missing.

DMESG:

bcm4329: version magic '2.6.27.46-01393-g018bd74-dirty preempt
mod_unload ARMv6 ' should be '2.6.27.46-01399-g6a073c7-dirty preempt mod_unload
ARMv6 '
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I thought this was CDMA-only at this stage. Did someone with a GSM device successfully test it?
[Touch Pro2, Tilt 2 Android Development] walter79:
Rhodium 100 = GSM
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Why have I not heard of this before :eek: I am painfully GPS dependent. Especially since moving to a new state and the fact that I don't do a whole lot of driving.
[Touch Pro2, Tilt 2 Android Development] Bones2374:
Question: Is there an easy way to get the fade-to-black "Task Switcher" screen functionality like XDAndroid has on Long Pressing the End button? (Was this an add-on .apk or built-in userland function? I miss it so much)

Currently by default on Rhod300/Tilt2, the power button on top of the phone and the End button do the same thing... Short Press: Sleep, Long Press: Phone Options
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, I am well-aware that the RHOD100 is GSM only. Hence why I asked, if you took the time to read that thread title it says CDMA only... :rolleyes:

Derp.

You can remap home to end key, however the long press functionality you want is not there. I asked ACL about adding this, and I don't recall if there was a legitimate reason why he didn't want to add/change that, or if it just got lost in the ether.

If he doesn't respond to this, I'll ping him about it and let you know.
[Touch Pro2, Tilt 2 Android Development] Starfox:
I have the b4-home layout and long-press task switcher works fine. For whatever reason the Rhod powers-that-be like having a call button instead of a home button.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well of course you can change the layout yourself.

As for the "RHOD powers-that-be", c'mon guy. Really? lol. AFAIK it's just the default, and it's often forgotten. Like I said I mentioned this to ACL a while ago, and I can't remember what the answer was on that.
[Touch Pro2, Tilt 2 Android Development] walter79:
[B]
14:45:24.835 Error wpa_supplicant 602 Line 652: unknown network field 'network'.
14:45:24.836 Error wpa_supplicant 602 Line 745: network block was not terminated properly.
14:45:24.836 Error wpa_supplicant 602 Line 745: WPA-PSK accepted for key management, but no PSK configured.
14:45:24.836 Error wpa_supplicant 602 Line 745: failed to parse network block.
14:45:24.947 Debug WifiService 118 ACTION_BATTERY_CHANGED pluggedType: 1
14:45:25.058 Debug WifiService 118 acquireWifiLockLocked: WifiLock{NetworkLocationProvider type=2 binder=android.os.Binder@451af490} 14:45:25.164 Debug dalvikvm 456 GC_FOR_MALLOC freed 3825 objects / 231232 bytes in 150ms
14:45:25.384 Info wpa_supplicant 602 CTRL-EVENT-STATE-CHANGE id=-1 state=0
14:45:25.385 Error wpa_supplicant 602 Failed to disable WPA in the driver.
14:45:30.079 Debug WifiService 118 releaseWifiLockLocked: WifiLock{NetworkLocationProvider type=2 binder=android.os.Binder@451af490} 14:45:32.499 Info ActivityManager 118 Starting activity: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.wifi.WifiSettings }
14:45:36.102 Info ActivityManager 118 Displayed activity com.android.settings/.wifi.WifiSettings: 3570 ms (total 3570 ms)
14:45:36.864 Debug WifiService 118 ACTION_BATTERY_CHANGED pluggedType: 1
14:45:39.925 Debug WifiService 118 ACTION_BATTERY_CHANGED pluggedType: 1
14:45:40.048 Error WifiHW 118 Supplicant not running, cannot connect
14:45:44.965 Error WifiHW 118 Supplicant not running, cannot connect
14:45:45.085 Debug dalvikvm 428 GC_EXPLICIT freed 2887 objects / 221296 bytes in 160ms
14:45:50.001 Error WifiHW 118 Supplicant not running, cannot connect
14:45:50.006 Verbose WifiStateTracker 118 Supplicant died unexpectedly
14:45:50.006 Debug WifiStateTracker 118 Reset connections and stopping DHCP
14:45:55.038 Error WifiStateTracker 118 Could not stop DHCP
14:45:55.162 Debug WifiStateTracker 118 Disabling interface[/B]

Can someone help with this problem?

I am running xdandroid - android 2.2.2 nand build with ACL latest kernel and modules. Only wifi is not working. I can start wifi but i can`t scan for network or connect to a wifi network. Bluetooth and 3g are working.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
If you're on 2.2.2 you're in the wrong thread; this is a 2.3.7 thread, and specifically a specific build of it. Try the general FRX thread if you really do mean 2.2.2, or try updating to GBX to see if it solves your problems.

That said, there's some updated wifi firmware in one of the threads around here. Try searching for it.
[Touch Pro2, Tilt 2 Android Development] walter79:
FRX thread is for sdcard builds and this is the only active thread for nand android.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
That doesn't answer the question of "why are you on Froyo still?" -- this IS a GBX thread, and this IS a developer's forum, and FRX IS outdated. Perhaps there's a reason there's no living thread for FRX+NAND. Gingerbread is superior in every way. It's faster, it's more stable, it's where all the development attention is so it's where the bugfixes are going.
[Touch Pro2, Tilt 2 Android Development] walter79:
Froyo nand build is faster then the GB build and need less ram.

Instead of asking me why I use froyo, you could help me with my pending wifi issues.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
I already gave you a suggestion: find the updated firmware.
[Touch Pro2, Tilt 2 Android Development] walter79:
I use files from GB nand rom.
[Touch Pro2, Tilt 2 Android Development] milda25:
I have followed Walter's crazy idea to apply GPS patch for CDMA and confirming - working great on my Rhod100 :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You can't just take XDAndroid builds and make them NAND. There was quite a bit that needed to change in order to get 'em up and running on NAND.

What's the point anyways? I find GB faster than FroYo... More features... Newer base... Really there's no reason to run FroYo. Might as well go back to Donut :p.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
There are newer firmware files than that unless I'm mistaken. Check the GBX thread a few pages back; I installed them on my own RHOD210 and wifi has been a lot more stable.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
That's for newer kernels than .27. Not sure if that firmware will work on .27 at all - doubtful.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
All the more reason to follow the advice of not running that older version if you want to solve the problems.
[Touch Pro2, Tilt 2 Android Development] pcgg:
Much thanks for the build, it works perfectly on my Rhod100 !!:D

I will feedback as soon as I find any bug which is not listed.
[Touch Pro2, Tilt 2 Android Development] n2rjt:
Agps working well on my Tilt2 too!
[Touch Pro2, Tilt 2 Android Development] obsanity:
I just flashed it. Works OK. Just a bit sluggish until I installed launcher pro. Much better on speed. Any kernels for this?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, the one that's included.
[Touch Pro2, Tilt 2 Android Development] obsanity:
Hehe. That's funny. Yeah I figured it won't but it doesn't hurt to ask. I'm kind of new to this phone. I have the att GSM version.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
There's not a huge selection of kernels for NAND unfortunately. There's one floating around that fixes the RHOD100 cam issues, but those don't apply to you...
[Touch Pro2, Tilt 2 Android Development] siulmagic:
do any of have a working key mapped to home? it seems both end call and power, both will turn on/off the screen, essentially there both power buttons.
[Touch Pro2, Tilt 2 Android Development] walter79:
yes. but can't upload it yet.
[Touch Pro2, Tilt 2 Android Development] siulmagic:
ah k good to know, im just here for a friend of mine, he had an old rhodium, and i told him he could flash android on to it heh. this reminds me of my htc kaiser days.
[Touch Pro2, Tilt 2 Android Development] obsanity:
There is a spare parts utility to change the end call behavior.
[Touch Pro2, Tilt 2 Android Development] walter79:
Is it possible to use this NAND build with a 3.2 kernel? Repacking boot.img with new zImage + ramdisk from Nand boot.img + new modules?
[Touch Pro2, Tilt 2 Android Development] hashtowent:
have a look here

kernels

its treath next to this.

=)
[Touch Pro2, Tilt 2 Android Development] pfc_m_drake:
Those kernels are NOT for NAND. They are only for GBX0B. See detule's post in that thread:

http://xdaforums.com/showpost.php?p=23502508&postcount=154
[Touch Pro2, Tilt 2 Android Development] walter79:
AGPS patch:

Flash via CWM-recovery.

based on this:

It works on my Rhodium 100

- copy gps.xdandroid.so /system/lib/hw and rename to gps.rhodium.so

- enable GPS

- enable data connection

- shutdown phone and pull battery

- wait min 10 min

- replace battery

- boot phone

Update:

This way works for me.

- replace the gps.rhodium.so

- install LeoAGpsInjector_v0.5.apk http://xdaforums.com/showpost.php?p=16384028&postcount=1907

- reboot

- enable data connection or wifi

- enable GPS

- run LeoAgpsInjector
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Only .27 works on NAND. No other kernel is NAND-worthy.

Did you even bother reading what thread you're in!?!? This couldn't be a more incorrect response.

Is this detule's patch? Don't just post stuff like it's yours, if it's not. Please say where the heck it came from, at the very least!
[Touch Pro2, Tilt 2 Android Development] walter79:
My post from 06.03.2012

It works on my Rhodium 100

- copy gps.xdandroid.so /system/lib/hw and rename to gps.rhodium.so

- enable GPS

- enable data connection

- shutdown phone and pull battery

- wait min 10 min

- replace battery

- boot phone

Update:

This way works for me.

- replace the gps.rhodium.so

- install LeoAGpsInjector_v0.5.apk http://xdaforums.com/showpost.php?p=16384028&postcount=1907

- reboot

- enable data connection or wifi

- enable GPS

- run LeoAgpsInjector
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks. I remember your post, but some might come across your post and not know they need to go read some other post for a backstory :p.
[Touch Pro2, Tilt 2 Android Development] detule:
I don't really care if you redistribute the lib, though alternative delivery methods encourage users not to read the original instructions and often lead to confusion. Not to mention that updating the lib in one post will lead to multiple copies floating around further complicating things.

However you are also bundling tytung's app, and though I may not care that you are re-packaging my lib, common courtesy at least says you should check with him if that's ok. I see that Tytung accepts donations and redirecting traffic from his post is not quite fair, imo.

Oh yeah, there's also something in tytung's post addressing redistribution of his code as it relates to GPL. As our lib contains chunks of his code these instructions are still relevant. You may want to read it and make sure you are not in violation in any way.
[Touch Pro2, Tilt 2 Android Development] walter79:
I removed my patch. GPL = you can use it (+ link to source) and if you change some code you have to make it public.

For me XDA-developers.com is not a place to make money. It is a place to make mobile phones better. Everyone said i like open source. But if they can make money a lot of people will publish it closed source.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
No, GPL = you can use it, and if you give it to someone else you have to include the source, and if you make changes you have to include the source to the modified version if you share the modified version. If you don't share it, you don't have to make the changes public.

Linking is not sufficient. You have to distribute the source AND the binary through the same means. If you offer downloads of the binary, you have to include a download of the source. If you offer a link to the binary, the source has to be hosted in the same place. Specifically, you CANNOT redistribute it and just link to the original source! You also CANNOT just link patches against the original source; while offering patches is NICE, the obligation is to provide the entire source as it was used to build the binary as distributed.

Also, attribution is a must. If you distribute something you MUST include a visible copyright notice that cites the creator. If you modify it you MUST NOT say that it's by the original creator -- you have to say what the original was and say you modified it.

Long story short: If you're using the GPL as why it's okay for you to be doing something, you have to do what the GPL says you have to do.

Here's the official stance of the XDA moderators: http://xdaforums.com/showthread.php?t=1159302
[Touch Pro2, Tilt 2 Android Development] walter79:
I have made only a CWM flashable zip with 1 lib and 1 app. I did not change anything in this files. Next time everybody can copy this files and set permissions by his own.

And we can go back to nand topic now.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Then you haven't violated anything related to the GPL, just say where it came from and you're fine. You haven't made any modifications to the code.

I didn't mean to beat up on you, just wanted everyone to know what that post meant. If someone came back and jumped straight to that post, they would be so horribly lost.
[Touch Pro2, Tilt 2 Android Development] Starfox:
I had a WOD earlier today. I was scrolling in Opera Mini, the screen froze, and everything became unresponsive. I saved tail -500 /proc/last_kmsg, right before I encountered a SOD. I've been in an area with 0-1 bar signal this week and noticed that SOD has been occuring a lot more. I have a feeling it has to do with the arm9 processor because prior to this week I rarely if ever SODed.

I looked at the WOD kmsg, and noticed a lot of errors about vsync. Hopefully this will help track it down.

http://db.tt/dwOglPt8

-- Starfox
[Touch Pro2, Tilt 2 Android Development] jherbold:
Thanks

Just wanted to say thanks for this ACL. I kind of retired my tilt2 but it had been so reliable and faithful it hurt to put it away.

With your android port, a Google Voice acct, and Groove IP, it is now a wifi based communicator and will be used daily as our "house" phone.
[Touch Pro2, Tilt 2 Android Development] n2rjt:
I totally agree! My Tilt2 is my backup phone and is very reliable with this build. I used it all day yesterday after my N1 battery died and had no problem at all.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
I've probably asked a dozen times and a half, but where does the battery life here compare to GBX0B?

As in, worse, about the same, better?

(I've never gotten a reply to this particular question)
[Touch Pro2, Tilt 2 Android Development] vinceweis:
Yes to all of the above. Now you have a reply. :confused:
[Touch Pro2, Tilt 2 Android Development] hashtowent:
for me it doesn't hold a day normal usage...

so quite unuseable for daily use, at home no problem, on the road -.-

maybe its the inaccurate batterycharge detection but without 2nd battery it won't stand a whole day with calls and sms.
[Touch Pro2, Tilt 2 Android Development] eurohunter:
You probably never bothered to read after posting the question those dozen times because the answer has been posted countless times. GBX0B has a slightly better battery life than OMGB. With normal use (short calls every now and then, sms every now and then, and a little web browsing), OMGB will give u about 5-6 hours, and GBX0B will give you about 7-9 hours.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
I read everything posted to me fairly well. As far as I know I've never gotten a satisfactory answer. That's not to say I didn't forget the answer, I am fairly forgetfull, but it was important-ish to me so that isn't likely. If I did miss it, then I apologize for posting again.

And thank you for answering my question.
[Touch Pro2, Tilt 2 Android Development] solnt:
Hi,

Could i using this build for normal daily tasks: sms, call, 3G ...etc with a battery life that acceptable?(1 days or more i guess)

I think that the change log in post 2 is outdated compare with many things were fixed in this thread so far.

So, i hope someone, with "right", could edit it so that we could know what we have/not have in this build.

Thanks
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
18 hours is about the longest battery life I've seen reported from any Rhodium Android build, with 12 being more common, but 6-8 isn't unheard of; it largely depends on your usage patterns. (Background data is a real killer.) SMS, voice, and 3G should work fine.
[Touch Pro2, Tilt 2 Android Development] mbellot:
I doubled that (once) while running OMGB and documented the 38.5 hour run on PPCGeeks.

Link

Since then I've seen battery life as low as six hours and as high as 30, with no real rhyme or reason, but I seem to average 12-14 hours.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
It all seems to be related to radio activity and data traffic. Try turning off mobile data, you'll see huge battery life then.
[Touch Pro2, Tilt 2 Android Development] mbellot:
That 38.5 hours was with data on, polling three pop accounts every 15 minutes.

Like I said, I've never been able to repeat it, but it did happen.
[Touch Pro2, Tilt 2 Android Development] solnt:
Thank for your info. Guess i will waiting for a little more :D.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Don't hold your breath. Android will probably always consume more battery life than WinMo. I seriously doubt we'll ever get it so that Android consumes less power - mainly because most people have Android doing a lot more in the background. I know I do.

That's not to say that it'll never get better. Just don't expect days on end of usage.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
The rumors of my death have been greatly exaggerated

I've been MIA for a while but i'll come back soon. I'm in the process if finalizing a new batt driver for the rhod so i'll post the details once its ready for testing. :D
[Touch Pro2, Tilt 2 Android Development] walter79:
Sounds good.
[Touch Pro2, Tilt 2 Android Development] sam_1421:
I'm currently on the FRX07.1 build, and I'm wondering if it's worth changing for this one... FRX07.1 is a bit slow but still usable, and I get a correct battery life with average to low use.

Do you think it's worth it or I should stay with Froyo?

[edit]

I'm on the rhod400

[/edit]