yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] wizardknight:
If you want to be able to remove the SD card while the phone is on, I suggest that you look at the NAND type builds.
[Touch Pro2, Tilt 2 Android Development] mk27:
I'm getting reboot loops (DIAM100) if i keep the GPS active for about a day.

The only way out of that is to press the reset button/remove battery.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Don't keep the GPS active for a day?

This is also the RHOD section, not DIAM. Thanks.
[Touch Pro2, Tilt 2 Android Development] mk27:
Is DIAM not supported by this release?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I can't support the DIAM very well, as I don't have one... I do my best tho.

However, again, this is the Rhodium section. People assume you have a Rhodium if you're posting in this section. Please post in the DIAM section if you have issues/questions pertaining to that device.
[Touch Pro2, Tilt 2 Android Development] blydude:
A few questions...

I recently purchased a used US Cellular Touch Pro 2 to use as a primary phone after selling my Inspire 4G (needed money for a car). I have plenty of experience with Android, so I got this up in running and mostly got it set up, with the exception of a few questions:

1. Video player - is there any way to watch AVI, MP4, etc. on here? I tried RockPlayer Lite and MX Player along with the default, but none of them work. Is there a fix for this?

2. GSM unlock - I have a standard talk/text AT&T plan. I put my SIM in, changed the settings to GSM, and rebooted, but it still gets no signal. Any suggestions?

3. Headset compatibility - I have a pair of SkullCandy Ink'd that I would like to use with this with headset functionality, I have yet to play with it much, but does anyone have a solid fix for this?

4. MP3 tag reading - Is there any way for the default music player to read MP3 tags as opposed to going off of the folders and file names? It's just reading the folders and file names right now, and WinAMP did the same.

If anyone can offer some advice for any of this I'd really appreciate it.

And thanks to all those who worked on this awesome project, I can't thank you enough! Great work! :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well first, I would move to GBX0C if you're going to stick with SD builds.

Second, you have to keep in mind this is not a native Android device. So it's not going to act like one...

1. Video players *should* work fine, assuming the video is the right resolution.

2. GSM again, should work fine. Which RHOD do you have? RHOD300?

3. Headset should work fine as well, but only the CDMA RHOD's have this port - so perhaps you have a CDMA RHOD? RHOD400/500?

4. What did you use before to play MP3's? I always stream, I've never tried to play any local files. I know there was some discussion about MP3 ID3 tags a while back, but I don't remember where it left off.

I guess I can try #4, but I'm surprised more people haven't brought it up if it is an issue. Perhaps it's the type of tag - make sure you have v1 and v2 tags populated. Just a guess...
[Touch Pro2, Tilt 2 Android Development] blydude:
I understand that, I just thought I'd give this a shot. I really appreciate your work on this.

1. I'll see what I can do with video.

2. RHOD400. Still no luck with GSM.

3. It is a RHOD400, but from what I've heard it is still unlockable due to the SIM port. I may be wrong on this though..

4. I was able to fix the MP3 issue - I eventually found a Market app that fixes the database for ID3 tags, so that's working now.

Thanks again!
[Touch Pro2, Tilt 2 Android Development] wizardknight:
2. RHOD400. Still no luck with GSM.

I think that phone carrier is CDMA. You will need to change out the radio/unlock the sim card if you are trying to get it onto a GSM network. There are a few threads talking about that process.

3. It is a RHOD400, but from what I've heard it is still unlockable due to the SIM port. I may be wrong on this though..

RHOD400s are unlockable. There are two things to unlock for. 1 Roms, 2 Carriers. Unlocking for one does not unlock for the other.

4. I was able to fix the MP3 issue - I eventually found a Market app that fixes the database for ID3 tags, so that's working now.

Cool. Care to share what app worked for you?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So the RHOD400 is a CDMA device first (it is a Sprint device after all...), and a GSM device second.

You have to keep in mind - the SIM slot is locked from US carrier's. Not sure how exactly, but from what I've gleaned the SIM slot will only work on oversea carriers.

Unless, of course, you unlock the SIM slot - which is off-topic for this thread and section. Assuming GSM works fine in WinMo, it should work fine in Android. Please ensure service works in WinMo before ever attempting in Android.

Thanks.
[Touch Pro2, Tilt 2 Android Development] blydude:
2. Could you be so kind to direct me to a thread with US Cellular SIM unlocks? Not really having too much luck here..

3. I need to use it with AT&T. It was already flashed with HardSPL with a custom ROM, and it works well enough for my not-so-often-WinMo needs, so I'm good there.

4. My bad for not posting that. It's called ID3Fixer.

Thanks!

EDIT: With ID3Fixer, if you want to fix a large amount of files (1500+ for me), make sure you set your screen timeout to 30 min/off - it's a memory hog and it seems to crash if the device goes into standby/lock!

---------- Post added at 01:23 AM ---------- Previous post was at 01:14 AM ----------

Got it. I'll work on the radio. Thanks for all the help and the awesome work!
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Try this.

http://xdaforums.com/showthread.php?t=555339
[Touch Pro2, Tilt 2 Android Development] Trantastic:
Virtual Keyboard is still showing up with the newest build (September 1 2011)

First off - This is a beauty and thank you for your hard work!! The only problem that I'm still having is that darn virtual keyboard will not go away while loading and finished loading. I've found that the command is in the startup text file. Any idea on why it's not going away?? Thanks!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You have to change that command in your startup.txt to disable it...

Please paste your startup.txt in

braces. I can show you what needs to be fixed.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
See my edit, that's what I meant by

braces. At the start put [ code ] and end [ /code ] (w/o the spaces).

But the virtual keyboard is disabled with this command, which you have in there "msmvkeyb_toggle=off"

Is set cmdline all on one line? It appears like it is. Did you edit the startup.txt at all, or are you just using what has been provided? It appears to be untouched, which should work just fine. Can you take a screenshot of the virtual keyboard you're talking about? Perhaps we're talking about different things.
[Touch Pro2, Tilt 2 Android Development] Trantastic:
Nevermind... Sorry for the confusion. Must of been how I was messing with the text and trying to put it in subfolders at first. I just put it all on the root of the SD card and the "virtual keyboard" disappeared. I'm glad it works! Thanks for your help!! :good:
[Touch Pro2, Tilt 2 Android Development] heart_crafter:
Worked on first shot :D

Thanks!
[Touch Pro2, Tilt 2 Android Development] socialdavid:
Complete Android/Linux newbie question. I have this install, ran perfectly until I ran out of memory space. I don't have a Linux machine, so is there another way (command console on phone?) to resize data.img? Sorry if this has been asked before.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, read the FAQ...
[Touch Pro2, Tilt 2 Android Development] Jemmauk:
Weird error

I've managed to install this without problems to the Diamond and the overclocking trick works great (running at 691mhz stable).

However its like swimming through molasses and I think I have found why I have a problem. The phone is reporting 100mb memory *in total* when as far as I understand it it should have 192mb in total. I am not really up on how to adjust this but it looks like its set in the startup file. Is it possible to get the full 192mb available because I suspect that it would make the phone worlds quicker and actually useable.

Is this a case of putting another kernel onto the phone and trying that?

Thanks in advance

Jemma
[Touch Pro2, Tilt 2 Android Development] wizardknight:
1st FroYo is very old, and unsupported now. Try something that has been worked on more recently like GBX0C.

2nd. These are the RHOD forums not the Diamond. We don't have your device, so we can't really be much help.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Indeed...

Lastly, the DIAM had 192mb physically available. Things like SPL and graphics take up that memory, so 192mb is not available to the OS.

RHOD has 288mb RAM, but in Android I believe something like 171mb is shown as available? I can't remember.
[Touch Pro2, Tilt 2 Android Development] :
you *could* increase memory available by breaking certain functions that you never use, such as camera.
[Touch Pro2, Tilt 2 Android Development] xmarkom:
Please help me.

My back button does not work, can i assign somehow from some program.

And also, my qwerty is weird (A and C for example doesnt work)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I guess don't use the physical qwerty, use an on-screen kb like swiftkey or something.

As for remapping the back button, perhaps there's some app that can do it - but it may or may not work. Otherwise you'll have to edit the source, keymap stuff is in the rootfs.img.
[Touch Pro2, Tilt 2 Android Development] xmarkom:
i dont know how now after reboot everything is fine.

I just wonder is there some software for better screen calibration, i cant type letters and numbers with 100% precise. it double down my sms texting speed. i used this ts-calibration file here in forum but it is unprecise.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
http://bit.ly/VLIYTx
[Touch Pro2, Tilt 2 Android Development] xmarkom:
funny but says for GBX0C i have other version , thx anyway
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Sigh... if you can't make the leap of logic (or experimentation) that would allow you to just use the same file then you don't get to have an easy way to calibrate your screen.

You know this place is called XDA developers. You are expected to be able to do a little bit of tinkering on your own.
[Touch Pro2, Tilt 2 Android Development] xmarkom:
same maybe worst with this apk :(
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Not sure what that is suppose to mean.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Seriously, what does this mean it's worse maybe the same?

Also, I'm not surprised wizardknight is suggesting this app - it is the first userland fix for calibration.

I don't think it will work for FRX, at least not without some hax.

What I am a little bothered by is xmarkom's inability to read the first post. Did you look at step #4?

.....
[Touch Pro2, Tilt 2 Android Development] xmarkom:
i mean with this software for calibration it works the same as usual (as the first time) maybe even worse...

I followed that instructions you've mentioned but still nothing, Sometimes when i press for example A it types A, ok but sometime it types totally different, not near button, for example O or L or SPACE...

sorry about my english, i typed this in a sec.

this android is ok, but is useless until i solve this problem with calibration

thx anyway :silly: even if i made you nervous
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I wasn't nervous, just annoyed that you seemingly didn't read that section of the first post - at least your post indicated like you didn't read it at all.

Regardless, it sounds like you're not calibrating properly. You're using a stylus and are being VERY careful right? Calibration is very important on resistive screens.
[Touch Pro2, Tilt 2 Android Development] BiggSnoop:
cannot toggle small screen-keyboard off

Hello,

today i installed latest bundle on my still Windows6.5 running Touch Pro 2 (RHOD100), all works fine.

I only have the problem that the small keyboard is switched on and cannot be removed.

In the startup.txt for the RHOD100 in the cmdline its already written

set cmdline "msmvkeyb_toggle=off"

i also put it in there seperately but still this annoying small keyboard is there....so whats wrong with my startup.txt?

Even inserting another "rel_path" for using subdirectory instead of root was working but this keyboard is not going away

now i installed it on the root and have no rel_path and use original startup.txt from the bundle....why this keyboard still is switched on

May the startup.txt for RHOD100 incorrect?

Thanks in advance!

Snoop
[Touch Pro2, Tilt 2 Android Development] BiggSnoop:
edit: Problem surprisingly solved, just took another SD-Card....crazy!
[Touch Pro2, Tilt 2 Android Development] BiggSnoop:
Oh....by the way...will it be possible to make a XDANDROID-Version of later versions than Android 2.2.2.

i could image with the speed of JellyBean even a XDANDROID version have a nice speed.

This would also be cool so we can use dualboot, using Win6.5 and Android at same device.

Oh is there a guide how to install a dualboot with XDANDROID and Win6.5...i saw video of this on youtube.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
No it will not be possible, as it has already been done. Well you could build a time machine. Then due to the fact that everything is relative it could be in your future, and our past. But then you would probably just end up being your own grandfather. I hate paradoxes.

You will have to keep imagining. Development stopped at GB

Or the at the same time... oh, wait you can do that now.

Cool story bro.
[Touch Pro2, Tilt 2 Android Development] BiggSnoop:
i dowloaded and installed 07.1 bundle from first page and after installation my phone says it´s Android 2.2.2, so please tell me where to get a later working (no testing) version of XDANDROID.

@wizardnight: its clear that it must be very boring for such a genius like you, but hey especially as "bro´s" you could give a helpful answer instead of a reply sounding a lil bit arrogant.

Sorry in advance if i am wrong but your answer had no value for me and did not help out.

So, again, is there a thread guiding to the mentioned dualboot option for WinMob6.5 and working XDANDROID?
[Touch Pro2, Tilt 2 Android Development] pfc_m_drake:
I actually ran GBX0C from the testing thread with the 3.3.8 kernal all the way up until December when I finally upgraded to a Motorola Photon Q.

In my opinion, GBX0C with 3.3.8 was the 'best' build for dual-booting (e.g. running XDA off the SDcard).

I know that thread is marked [TESTING] and not [BUILD] like this one, but I think that's probably due to the additional setup steps required (specifically, copying .csv files to get audio working properly).

My advice would be to try that build - read the thread and follow the instructions carefully. There's more setup required, but the final results are pretty much as close to 'flawless' as you're going to find with a 3rd party build. arrghhh and the others really did a great job on that one, and detule's 3.x kernals for GBX0C were just brilliant....magical even.

Good luck.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
And?

Read the threads. Not that hard to find... only about the fifth one down on the first page of this section.

*Gets out spoon*

Yes, we expect you to read the threads here. There is a reason it is called XDA Developers. These forums are for Developers.

When I arrived I knew nothing about android. Then I read the threads, and asked specific questions to get the answers I needed. Now I am helping to release a rom. Reading is good for you.It cures all kinds of things.

Ask the right questions, and you will get the right answers. Ask the wrong questions, and you will not get the answers you are looking for.

Not my fault you didn't ask the right questions.

Um, ya. The first post of each thread that covers booting an SD based version of android. There are instructions and everything about that build there. AKA... a guide.

So in a nut shell, ask specific questions and you will likely get specific / useful answers. If you want us to know about a specific video you are looking for more information about, start a thread in Android general, and put a link to the video.

Tell us a story about a random video you saw on YouTube, and you will get random cool story comments. We don't have physic powers, and there are lots of videos about android on YouTube.

Use proper capitalization, punctuation, and sentence structure and you may get people's respect a little more quickly.
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
I second the 3.3.8 build and the comments about the authors, as I am still running it. I am one of few remaining SERO holdouts...

Good luck as well.

OM
[Touch Pro2, Tilt 2 Android Development] mike_san:
I've Running Android on my SD. but i cant via Android install it in the NAND?. Since the driver for ADB didnt work for me it says that i need it for x64. So in tricolor mode i couldnt reflash the recovery.

But this Android its not running, its not what i thought. i think on the NAND memory will me smooth than SD.

Running Android i cannot flash the recovery? to install clockworkmod or something like that?
[Samsung Infuse 4G] carhigh:
Just the external speaker stopped working. Phone is 35 days old. The other 2 are still working fine. Any ideas to try before i try resetting?

The sale rep is real nice, so if i cant remedy this tonight i may see if he will swap it for me. If not, after that im clueless with dealing with samsungs repair stuff.

Im stock, rooted, so i will have to unroot!
[Samsung Infuse 4G] carhigh:
It just started working again. After copying all my stuff off and restarting several times
[Samsung Infuse 4G] keithr1475:
Me too

I had my Infuse since day one and I was running InFused. All of a sudden my external speaker would not work. I tried everything and could not fix it. Finally went to ATT and they replaced it under warrenty. Hopefully it won't break again.
[EVO 4G General] smc333:
Looks official and hope it is. Exciting stuff, definitely my next phone.. Evos been good to me but can't wait for this! Also looks like it's coming equipped with 2.3.4:D

Source:

http://www.androidcentral.com/samsung-galaxy-s-2-within-sprint

Check it out and share your thoughts!
[EVO 4G General] reddragon72:
there is no 4G stamp after Sprint on the back so it is a nice fake.

also word on the street is that all the US variants of the SGS2 will have the Nvidia Tegra2 chipset, so not much of a difference from other phones on the market. I personally wont own another Samsung for awhile, as they have little to no support for the community , and really just suck for delivering stuff that satisfies US carriers so updates coming to the US take forever!
[EVO 4G General] SoraX64:
Uh.. As far as I know, the phone won't have 4G...
[EVO 4G General] GrimReaper24:
Move to the SAMSUNG FORUMS

Isn't there a samsung thread for a post like this :( I know there is so please put it over there. It doesn't belong in the EVO forums. :(
[EVO 4G General] bkrodgers:
I don't have any info one way or the other, but that wouldn't make a lot of sense. The Epic has it. The two current phones it will sit next to (Photon and E3D) have it. This is flagship phone, and it wouldn't make sense for it to lack 4G.

Not saying you're wrong, just saying it wouldn't make sense.
[EVO 4G General] Android 17:
It wouldn't make any sense for this phone to NOT have 4G, what are you smoking?

Even if Sprint switches to LTE, it won't happen anytime soon, so that surely won't impact this phone.

Also, the rumor about the U.S. variants having Tegra 2 processors isn't entirely right, it was rumored other territories might have the Tegra 2 included, but the U.S. is the least likely to have the Tegra 2. Not saying there's no chance, but it seems pretty slim.
[EVO 4G General] mlin:
The E3D doesn't say 4G either and its not fake.

tapa tapa tapa
[EVO 4G General] Beejis:
If this is legit then it looks like I found my upgrade!

Pocket posted...
[EVO 4G General] m4rk0358:
Ditto

Swyped from my EVO
[EVO 4G General] captblaze:
looking at the back shows sprint, but i want to see the front.

specifically whether it will have 4 capacitive buttons or will have the dpad (looks like one at least) of the european versions
[EVO 4G General] m4rk0358:
via Android Central
[Atrix 4G General] guitarcrazy188:
I noticed today that the 4 capacitive buttons at the bottom of the phone were not all lit up as they're supposed to be. There seems to be light coming from the search button and starts to carry over into the back button but the home and menu buttons are an off white color and dont seem to be getting lit up. Any suggestions?
[Atrix 4G General] ka3yan:
I seem to have the same problem. I'm on OTA 2.3.4. It could be a model that I did, but I can't remember doing anything that might have done it.
[Atrix 4G General] guitarcrazy188:
Im on kenns beta 4 of 2.3.4 and I have the problem I don't know
[Atrix 4G General] Viamonte:
There are reasons why this build is called "beta". I'm on official 4.1.83 and have no such issue, anyone does?
[Atrix 4G General] drumercalzone09:
Mine seem to be working fine. I know that they work with the light sensor. Try covering it up for a few seconds (to the right of the earpiece) to see if they work.
[Desire HD Q&A, Help & Troubleshooting] kiwiandy:
So I had a DHD from Softbank Japan that I (foolishly) ran the OTA update to Gingerbread.

I followed the steps in this thread http://xdaforums.com/showthread.php?t=905003 on how to Downgrade, including the "prerequisites for downloading from 2.37." in the second post.

Everything worked fine.. no errors, but when I finish I still have 2.37.762.2 on my phone?? ( which from memory is the same version ROM I started with?) and I still cannot get Temp Root using visionary?
[Desire HD Q&A, Help & Troubleshooting] descenpet:
if you have that softbank version, you don't need to do the prerequisite since you already met the prerequisite.

there must be something else you missed from first post.
[Desire HD Q&A, Help & Troubleshooting] kiwiandy:
Well I thought that might be the case, however I decided to follow all the instructions just to be safe!

Since my previous post I have followed the steps in this Thread http://xdaforums.com/showthread.php?t=1152233 .... as it seemed more specific to 2.37.xxx however I cant get it to load the image at the final step... It always says "CID incorrect".. I have re-made the GC several times using both mmc2 (which had been working previously when I followed the steps in the other downgrade thread) and also mmc1.

I have reformatted the GC again just to make sure there wasnt any corruption there.

this phone just likes Gingerbread, and hates Froyo??
[Desire HD Q&A, Help & Troubleshooting] ProreX:
When I was rooting from 2.36 I used GC borrowed from my dughter (maybe that was a success ;) ), but this GC was only 1GB. I formatted it completely, not just quick format (could be a problem). Maybe you wrote down wrong number, forgot to overwrite new file... something trivial.
[Desire HD Q&A, Help & Troubleshooting] kiwiandy:
but I successfully used this GC when I tried to downgrade using the method in the thread I mentioned in my first post, and also when I loaded the first image in the method in the second post. :((
[Desire HD Q&A, Help & Troubleshooting] kiwiandy:
GC helper

Another thing I have noticed.. as I have "made" a GC several times now... mostly I reuse the img file that i was sent from the website that generates it.. however in an attempt to recheck that I have doen everything correctly.. I have re-done this several times... I just noticed on my last attempt that the Reverse CID's reported by the GC helper app on my phone are different to what it was generating previously (when I had the same 2.32. rom image ) ?? is this normal.. how often or how random are the reverse cids?