yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] teemo:
It is probably reception. I find that Android choose 2g/gsm too often. You can try to force 3g on. If signal is too weak you will get an unresponsive phone I guess.

Enter *#*#INFO#*#*

Enter the Phone menu, scroll down and pick your poison.

I put mine on WCDMA to force 3g.
[Touch Pro2, Tilt 2 Android Development] nasapunk88:
1x just means ur running at 1xRTT speed, which is about 153 Kbit/s. Usually just referred to as 2.5G.

3G is around 2.4 Mbps. Much much faster and better.

All it has to do is your reception, whether you have good or bad and if 3G is offered in that area.

For the most part not much you can do about it other then move phone into 3G, Force 3g (could be 1 or no bars period then) or let it auto switch from 3G to 1x when needed to get best # of bars.
[Touch Pro2, Tilt 2 Android Development] reckert:
What class is the SD card? A lot of people have reported issues with class 10 cards - maybe that can take care of that issue.
[Touch Pro2, Tilt 2 Android Development] latinohot:
i have the same problem with my tilt2, after a call i have no 3G connection where i know there should be, after a while it comes back to 3G.

Also sometimes while in a call i can't browse the internet like i can with WM

but that happens not to often only everynow and then
[Touch Pro2, Tilt 2 Android Development] avionix:
Lo and behold, that did the trick. Renamed the data.img file, let it create a new one and camera worked. Went back to my original data.img file and camera still works (video too)!

U DA MAN!
[Touch Pro2, Tilt 2 Android Development] coolwater22:
alright guys thank you..i will try to force 3g and see what happens.
[Touch Pro2, Tilt 2 Android Development] benutne:
I'm having issues with my wife's Rhod 400 while in Android. It will just randomly lock and reboot. I've tried at least three different SD cards and they all exhibit the same problems so I've ruled that out.

Is there anything else that I should check before telling her she can't have Android on her phone? Settings that need to be tweaked? Apps that cause lockups?
[Touch Pro2, Tilt 2 Android Development] Enigmatik_best:
What type of device/phone have you: witch version of Rhodium?

I have Rhod100_FR and doesn't works by me :confused:
[Touch Pro2, Tilt 2 Android Development] detule:
You need to post logs. Follow the directions in this post and attach the relevant dmesg output.
[Touch Pro2, Tilt 2 Android Development] benutne:
I'll do that. Thanks for the tip. I'll post the logs tomorrow when I can get a hold of her phone again.
[Touch Pro2, Tilt 2 Android Development] benutne:
I've attached the log file from my wife's phone. It sure is a lot to dig through. I hope you guys know what to look for because I sure don't.
[Touch Pro2, Tilt 2 Android Development] detule:
I don't think it has to do with the SD you are using, rather It's a modem related crash - all those smd_close(7) should not be occurring so frequently. That "ARM9 has crashed" tag comes from a function supposed to handle a modem crash.

I would make sure you are using the latest Sprint radio (2.32) on your Rhod400, and using the latest RIL (already incorporated in frx07.1). Are you in a low service coverage area?

There's a modem/smd bug that's been causing reboots, one I've been looking for test subjects to test a patch on, but your dmesg output is not quite the same as that one, so I don't think it will do you much good. Post a few more logs as these reboots occur and you find yourself around a computer, I wonder if it's the same story in your dmesg every time.
[Touch Pro2, Tilt 2 Android Development] benutne:
Two more dmesg logs for you. I don't think its the modem bug you're talking about but she still has WinMo to use as her daily driver so I can test crap out to my hearts content. If it makes any difference it feels like the phone locks up when using any kind of wireless. Locks up almost any time I'm installing apps in the Market. I'll mess around with it more and post a dmesg log anytime it reboots.

Also, we aren't in a very low coverage area. Third largest city in my state.
[Touch Pro2, Tilt 2 Android Development] detule:
Update to frx07.1 which includes the latest ril and make sure your radio version is 2.32, something is wrong with your data stream.
[Touch Pro2, Tilt 2 Android Development] benutne:
Already on 7.1. Had the same issues with 6 and 7.0. Her phone isn't unlocked in WinMo. Is there a way to flash the radio otherwise? She won't let me make any (noticeable) permanent changes.

I'll check the radio. Will that show up correctly in Android or do I need to reboot to be sure? I know it shows during the boot process.
[Touch Pro2, Tilt 2 Android Development] benutne:
Already on 7.1. Had the same issues with 6 and 7.0. Her phone isn't unlocked in WinMo. Is there a way to flash the radio otherwise? She won't let me make any (noticeable) permanent changes.

She's already on 2.32 radio. I've made sure her WinMo system is completely up to date. Sprint/HTC stopped making updates for that phone some time ago..
[Touch Pro2, Tilt 2 Android Development] detule:
(I think) the correct radio version should be displayed in Android in About Phone->Baseband Version.
[Touch Pro2, Tilt 2 Android Development] benutne:
Yeah, sorry, browser locked up while posting. Its on the latest already.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well if you're on the newest radio (I put my phone on 2.37, which is a Verizon radio and works fine... but 2.32 ran fine for a long time) then there's not a whole lot you can do. Android isn't exactly flawless on this device yet...
[Touch Pro2, Tilt 2 Android Development] benutne:
Ugh, that's too bad. She really likes the android platform. At least so far the battery life is much better than 7.0.
[Touch Pro2, Tilt 2 Android Development] detule:
Benutne, the man has spoken. Both arrrghhh and I have the same device as you and we are able to use xdandroid without too much trouble. Other than the SD card, the Radio version/quality of coverage, all of which we seem to have ruled out, i'm drawing a blank on how else your particular device can differ from ours.

A last solution is always re-installing and making sure you start with a fresh data.img, but you sound like you know what you are doing and have tried this before.
[Touch Pro2, Tilt 2 Android Development] benutne:
Well crap. I really wanted to keep her on Android. She has an upgrade coming next year so I might get her a Shift if they're cheap then. It seems like she might be having some hardware issues which doesn't show up in WinMo. I'll keep messing with things and if you guys want to test anything out, please let me know.

Thanks for all the help. I mean that.
[Touch Pro2, Tilt 2 Android Development] AkumaX:
did you flash to the latest MR (3/19/10), and update the PRL + profile in WinMo?
[Touch Pro2, Tilt 2 Android Development] benutne:
PRL and profile in WinMo yeah. Not sure what "MR" means but I have updated to the latest version of Windows Mobile. Pretty much every damn update there is in WinMo. If you're talking about the radio it is up to date for the Sprint radio. There is a Verizon radio that I can try but I'd have to root her phone first.
[Touch Pro2, Tilt 2 Android Development] webvan:
Running it for the second time on my DM100 and the touchscreen is still unresponsive. I was keeping an eye open for the 5 point calibration mentioned in the instructions, but no luck. Thanks for any help!
[Touch Pro2, Tilt 2 Android Development] jonners59:
Interesting. I use Rhod100 in the UK on the Vodafone network. I am also using 7.1. I reported a couple of weeks ago that since my upgrade to 7.1 I was having trouble with Upgrades and Installing apps in Market Place and I too also felt it was a Market Place app issue. I still have difficulties, but as I have all I currently need it only affects when Upgrades come in. My machine boots back in to XDANDROID boot screen and when it returns I have no radio and need a complete reboot... of the install hangs during the process, download or install.

Maybe totally unrelated, but the info may help.

benutne, with you on treading carefully with the wife, but whilst it is not flawless, and may never be, it's well worth the perseverance.
[Touch Pro2, Tilt 2 Android Development] dsramesh:
Yes, both of the 16gb and 32gb are Class 10 SD cards. They are very unreliable at 4k block format and more reliable with 32k blocks. 16GB is pretty solid at 32k block size. Still seeing issues with 32GB at 32k Block size but lot more reliable than 4k Block size.
[Touch Pro2, Tilt 2 Android Development] benutne:
Yeah, I'll keep trying. It only seems like it locks while in the Market a lot but really it can just be sitting there asleep and I'll come back to it and it has booted back into WinMo. I wish it were one simple thing that were causing it but so far it seems to be random which makes me think it is a hardware issue that isn't showing in WinMo.
[Touch Pro2, Tilt 2 Android Development] BowenRacing:
Almost too scared to post two question here, in case it's the wrong thread or I upset the experts with n00b questions, but here goes...

1. Should I use an 8GB card or a 16GB card?

2. Should I use a certain 'class' of card?

Reading parts of this huge thread, I see there are issues about block size and class of card, but I don't fully understand it all. I searched, but there were over 125 results.

I hope the two questions above are phrased in such a way that someone can give a concise answer which won't trouble you too much.

Thanks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This isn't really the right section for DIAM. I post in the RAPH section, and cover that device as well. See what I said about DIAM on 7.1 -

Don't be scared :p.

1. Doesn't matter the size of the card, so long as it's at least 512mb... You can use a 32gb if you wish (although this is the largest type of card the phone can handle!)

2. Now I have heard C10 cards have issues. Some have reported problems with C6 cards. C4 cards seem to be the "sweet spot" but this is all just from what I've gleaned from others. I've personally only used a C4 8gb Kingston card. Other cards at random, but all older/crappier cards. Never tried a C10 card myself, but I've definitely heard bad things about using them for Android.
[Touch Pro2, Tilt 2 Android Development] BowenRacing:
Thanks very much for the reply.

Would a Class 2 card be too slow? My 8GB Class 2 card failed and will be replaced under warranty. If a Class 4 or higher would offer a speed improvement, then I would be happy to buy one. I had been running FRX04 before then and it was too slow to be useful for me, but FRX07 seemed much better until the card failed just after I got all my settings right :/
[Touch Pro2, Tilt 2 Android Development] BowenRacing:
Answer from a n00b here, so proceed with caution.

Go to the root folder of the card and delete or rename the file "ts-calibration"

Reboot into Android and as it loads you will see the text scrolling up the screen. Look out for a small square at the top left of the screen, this is the screen calibration. It is easy to miss because it is overlaid on the text you see when it boots. Tap the small square and the subsequent squares in the other corners and the centre, then the phone will continue to boot into Android.

Gotta go, baby crying :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I don't think a higher class card would effect performance in Android in any way, shape, or form. I've used classless cards and Android feels just as smooth as on my C4 card.

No offense, but this doesn't quite cover it. The first post covers it completely - in order to manually calibrate you must use an older kernel. Plus, the file name is ts-calibration - if there's still a .zip on the end you need to extract it!!.

Edit - Either way, webvan - read what I posted earlier. I believe that's your issue..
[Touch Pro2, Tilt 2 Android Development] fortunz:
I've got a friend who just installed FRX7.1 (vanilla, as is) and it is his first experience with xdandroid. He has a RHOD400, and he confirmed that he has the latest sprint radio, 2.32.

His issue that even when he knows a call is incoming, his phone does nothing to indicate he has an incoming call. He can call out, send/receive texts and data works fine too.

Any ideas? I've asked him to install getlogs, so holler if you believe those logs would be helpful.
[Touch Pro2, Tilt 2 Android Development] coolwater22:
sorry for this post,but didnt know where to ask.......

.......but someone i know is selling an evo 4g for $135, somewhat used..i was wondering if you guys think thats a good price for it. she said she found it at the mall and that its locked( i think she ment it needs a password) but a hard reset will help that..

should i try it?? and would i be able to use it as my regular phone or not?

and i currently have a tp2 so..would they,meaning sprint, charge me 10 dollars for the 4g..or would they not know?

and would i be able to switch my current phone network to the evo manually at the sprint website??

thnx for the help guys..sorry i didnt know where to post..and you guys are the smart ones here :)
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
I'm on a RHOD400 and have the same issues. I've pulled logs and had arrrghhh and Rpierce99 look at them, and IIRC Arrrghhh had some others look at them also, can't see what the heck is going on. My logs don't even show that a call is even coming in, nothing at all, nada, zilch. Although the past few days it appears to be better, but for how long who knows. And I've tried everything to get it to work right. The screwed up thing is that FRX06 works fine for me and hyc's FRX06+ build does as well. Hopefully someone can figure something out on it, but what are they to look at to fix it since the logs don't show squat.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
First off this is the wrong forum. now let's not even begin to talk about the moral aspect of what your trying to do, if it's reported as lost/stolen it will have a bad ESN, you will not be able to activate it even if it was a good ESN without paying the additional $10. So... tell your friend to call Sprint and give them the phone or try to locate the legitimate owner and keep playing with your TP2 until you can afford a new phone. Remember, karmas a *****...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm almost happy someone else is experiencing this bug.

What I would like both of you to do is grab the RIL from FRX06+ and shoehorn it into FRX07.1, and see if it improves. If it does, I probably need to downgrade the RIL that is in 7.1, because evidently the newest RIL has introduced a new bug... I'm still baffled as to why it only effects some, but this should fix it for good.

I'm at work right now, and can't seem to find an image from FRX06+, but if you folks can find an older version of the RIL that works with FRX07, just bind mount it using the froyo.user.conf file.

mount --bind /sdcard/libhtcgeneric-ril.so /system/lib/libhtcgeneric-ril.so
[Touch Pro2, Tilt 2 Android Development] fortunz:
Thanks fishingmedic. I had no idea that was an issue. I've recommended my friend grab frx06 given him instructions on how to update the rootfs ril etc.

Edit, thanks arrrgggh. I've passed along those instructions to him with the ril I was using my frx06 build. If he tries it, I'll report back.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
I've got a FRX06+ image here. I'm working too, but let me see if I can disect this beotch and grab the RIL. If so I'll shoot a link over to Fortunz for his buddy.

See Arrrghhh, I told you I wasn't lying and trying to make you crazy!! lmfao

But also note, lately my phones been receiving inbound calls, so IDK what the hell this thing is doing. And still on the old phone, never picked up the new one lol.

Fortunz and arrrghh: http://dl.dropbox.com/u/6838526/libhtcgeneric-ril.so
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
fortunz, wait for fishingmedic to grab the RIL from 06+. The problem with plain vanilla 06 is the RIL was designed to go in the rootfs - /lib/froyo. I don't remember the exact date when it changed, but a change was made to put the RIL into the system image, in /system/lib. I know FRX06 had the 'old' way of doing it, so fortunz it won't work to just take that RIL and put it in 7.1. I'm hoping just taking the 06+ RIL will work, but time will tell. I'm working with fishingmedic on IRC if you want to join in the fun ;).
[Touch Pro2, Tilt 2 Android Development] fortunz:
Gotcha, will wait
[Touch Pro2, Tilt 2 Android Development] le1t00:
Hi.

I tried to boot android on my Diamond but only I can see is Android logo and after while phone is rebooting to WM 6.5

What i need to do?

I copied ts-calibration from zip. Startup.txt is with haret...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
First, this is the TP2 section. Please see my thread here for RAPH/DIAM.

It *should* work OK on FRX07.1, but I heard the newest kernel doesn't work for DIAM users. See my post:

Deja vu, I just said this on the last page... lol.
[Touch Pro2, Tilt 2 Android Development] coolwater22:
yeah i figured thnx...alright ill tell her that..i know karma is a *****, i dont like doing this type of stuff because i would feel horrible if i was to lose my phone and not use it.
[Touch Pro2, Tilt 2 Android Development] Alvaster:
Been using this for a while,

Gotta say, I'm loving this build and FRX07 in General.

A huge thanks to those who developed this. I'm only now learning about programming in college and it must've been quite a feat to complete this.

Here's my summary:

I have the latest build on my RHOD400, on Boost, using 8GB SD.

So far, its been stable for days. Most of everything works as it should, except for some obvious things, like

-High Qual Video

-High Qual Vid (youtube)

-Some calls start on both earpiece and speakerphone, takes a toggle of speakphone to fix

-When playing music after a wakeup, it wont play, required removing headphones, playing music on speaker, then replugging headphones.

-Many apps dont work/crash instantly, like FB and office, which sucks, but HELL, I dont have WM anymore, so thats always a plus.

-Keyboard lights tend to activate at random when you toggle brightness/auto brightness. I could be on auto, no KB light, then switch to manual and theyll work, and vice versa.

After a quick APN change, Boost MMS is working, which is just awesome.

Camera really slow to boot and switch to gallery, but thats not a complaint, just a statement. Don't know if it's the build, or whatever.

Other than that, the build is stable. I have had to restart maybe once a week? VERY rarely does it crash, maybe twice since FRX07 initially was released and I booted up into it. I'm amazed my device can do what it does only now that I have android. Thank again!
[Touch Pro2, Tilt 2 Android Development] großa:
Yes. Tried it too. Running better than before.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You asked quite a few questions, so I'm going to break down your post. Hopefully it makes it easier to read, it might do the opposite....

Most vids should now play on 7.1. Not all, and no guarantees. Before 7.1, no HQ vids would work. There's a certain resolution where it just... fails. I can't remember what it was, 480x640 I think? We can't play videos that are "full" resolution, 480x800. Those will fail.

That is the fix, until the new audio routing code is stable and implemented.

Probably same as above... I know ACL said you have to WAIT when unplugging and replugging, but your issue may be different. Not sure. Patience is always a virtue when using this device in Android.

FaceBook is a horribly written app which crashes constantly on native devices. ***** at them, seriously - a ton of people have issues with this app, and they're not just people that use our port. Ironically the G+ app works fine :p.

Dunno about Office. Which app are you using for that? QuickOffice? I use Google Docs, again no issue...

Disable auto-brightness in the display settings, kb backlight will return to being sane. As in, keep it on manual brightness. Auto brightness causes the kb backlights to die.

Enjoy!
[Touch Pro2, Tilt 2 Android Development] rpierce99:
For what it's worth the facebook app works perfectly for me, and now with 7.1 syncs contact photos into my contact list.
[Touch Pro2, Tilt 2 Android Development] koriotto:
Hi, just a question... is it MY particular rhodium... or does android on this phone drains battery INSANELY? like i mean 100 to 60% in 25 minutes... thanks

Rhodium400 CDMA
[Touch Pro2, Tilt 2 Android Development] wmg316:
Amazing! LOL

That did the trick!

With all of your omniscient knowledge...why (does this work)?? :D
[Touch Pro2, Tilt 2 Android Development] fortunz:
That does sound extreme. XDAndroid isn't known for having the most accurate meter. Some of us have had some luck using an app called battery calibration from the market. It basically just clears android's own battery statistics and lets it start from scratch. Doesn't seem like a permanent solution, as I imagine it will just get out of whack again eventually, but it's work a try. I just used it when I upgraded to an extended life battery, did a full discharge, and I have to say, the metering feels more on the mark. To avoid having issues again, I'm trying battery left, a widget in the market that keeps its own statistics. I haven't used it long enough to know if it will work, but I'm hopeful that even if/when my system meter starts misreporting, the widget will remain accurate.
[Touch Pro2, Tilt 2 Android Development] mikereidis:
arrrghhh should give you the definitive answer. But with my experience with FM audio routing:

Setting audio paths also often requires mute parameters for microphone and earphone. So I'd guess the mute parameter is getting set right in this case.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Like Fortunz said that is very extreme. What is running on the phone, i.e. apps, gmail? Is the phone constantly searching for a signal? Ever since using battery calibration I've actually seen decent battery life and fairly decent accuracy but I've also shut down most apps that are constantly updating.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Like others have said, this is extreme. However, when using the phone actively, the battery meter will dip ridiculously low. It'll actually climb back up as it sleeps... kinda silly. Perhaps this battery calibration app fixes this effect - which I think is what you're experiencing.

So this is a WinMo device. The kernel is far from flawless, and perhaps there's something that Linux isn't properly initializing (hardwarewise) on its own. Back in the day, we had to do that trick in order to get the mic to work at all... If you go back to the early days of the port ;).
[Touch Pro2, Tilt 2 Android Development] koriotto:
Yeah i know its extreme... since im actually using my samsung Infuse as main phone... i just removed the dust out of the rhodium since i read the porting was complete! so i am used to insane batteryduration i can get 14-35 hours of the Infuse and about 8 hours of intense use... yeah i did the NeMa battery calibration drained battery to 0 and charged non stop to 100... and downloaded serie of widget and apps like juice defender i use on my other "100%" android phones... but yet :S i still get like 1 hour of battery life... no apps running on background...=/ maybe i got a faulty battery... since 1600 mAh sould give me at least 5 hours i guess i know the android porting on a wm 6 phone its not optimized... but 1 hour seems ridiculous for a 1600 mAh battery.... thanks for the reply anyways ill check with a new battery to see if it improves the life at least to 4-6 hours.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Also, JuiceDefender is a horrible app that a lot of people have said drastically reduces battery life. DO NOT USE IT!

You could also have a bad battery, or perhaps the phone isn't sleeping properly? See the changelog for 7.1 to see how to diagnose sleep.