yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] rdhalla:
I remember in my case when i flashed and i checked mine was XXLPH and for quiet a while i kept thinking that my stock was XXLPH but not really. My stock was DDKL1, i didnt knew that >:/ I used FUS and later on i checked my packaging box and it said the stock was DDKL1 >.< face plam.. I was less bothers what my phone displayed to be honest as long as everything is working....

So.. Now our phone is being detected by kies and Does kies says anything about software updating error ?
[Galaxy S II Q&A, Help & Troubleshooting] E-Nigma:
No Kies itself appears to be fine. Just noticing that my Google Play account still says I'm registered with a T-Mobile phone though and I can't seem to sign in with my Samsung account. It just says "Processing failed"...
[Galaxy S II Q&A, Help & Troubleshooting] rdhalla:
Go to your apps and try to clear data on both .. Market and Samsung account...
[Galaxy S II Q&A, Help & Troubleshooting] E-Nigma:
Well I just tried doing that and it doesn't seem to have changed anything. I can't seem to change the device listed via the Google Play site either.
[Galaxy S II Q&A, Help & Troubleshooting] E-Nigma:
Just a quick post to say I've got everything back to normal and sorted. The firmware I should have been looking for was

MODEL NUMBER

GT-I9100

ANDROID VERSION

2.3.4

BASEBAND VERSION

I9100XXKI1

KERNEL VERSION

2.6.35.7-I9100XWKI4-CL575468 ROOT@DELL143#2

BUILD NUMBER

GINGERBREAD.XWKI4

PDA: I9100XWKI4

PHONE: I9100XXKI1

CSC: I9100XEUKH2

Build Info: Wed Sep 14 20:34:11 KST 2011

I got rid of the CPW I installed and Kies has no problem with this one. It just says this is the latest version now. I don't want to go through anything like that again so lesson is painfully learnt. I'm curious though to when the official UK ICS is released tomorrow, would it come through Kies now I have my original unbranded XEU back?

Thanks again to those who helped me out. :)
[Xperia Play Q&A, Help & Troubleshooting] netizenmt:
I have an r800x with locked bootloader, 2.3.3. I have successfully rooted and installed CWM, and have used several ROMS, with my favorite being the UK Firmware version and Darkforest 3.0.5.

My question is, besides the ability to use custom kernels to overclock, would there be any real difference in performance or whatever running those on an unlocked bootloader versus a locked bootloader?
[Xperia Play Q&A, Help & Troubleshooting] jacklebott:
If the rom works on a locked bootloader, it's not going to be any better on an unlocked bootloader
[Xperia Play Q&A, Help & Troubleshooting] netizenmt:
So, with respect to the CDMA versions of the Play, unless you want to use a custom kernel for overclocking, or you want to run Cyanogenmod, there's no real reason to unlock the bootloader.
[Xperia Play Q&A, Help & Troubleshooting] jacklebott:
Yeah, pretty much. CDMA can't install GSM firmware with a locked bootloader though
[Xperia Play Q&A, Help & Troubleshooting] netizenmt:
GSM wouldn't work right anyway.
[T-Mobile LG G2x] timothy7732:
OK just updated to singh- UI 2.3.9 and Bluetooth work but I can't get it to play media from music or Pandora any suggestions?
[T-Mobile LG G2x] atb1183:
go to bluetooth settings

menu > setting > wireless something > bluetooth

long click on whatever device you're connected to

choose option

make sure it's connected to for media playback

i had that a few times. try unpair and repair as well

this phone's bluetooth is the worst i've had compared to: htc mytouch 3g (32B), htc nexus one, samsung galaxy s 4g, htc radar. bad connection n uses LOTS of battery
[Droid Incredible Q&A, Help & Troubleshooting] NYC Coyote:
Ok... so the insurance on the phone.. I have had it since day 1... 1 year contract. so out of it for A LONG TIME...

Not planning on a new phone til at least end of year (waiting for lte on the same chip as well as other things)....

So... do I keep the insurance or kill it?
[Droid Incredible Q&A, Help & Troubleshooting] krelvinaz:
Depends on whether you need it or not, or if it is still a value to you.

I moved to the HTC Rezound the end of Feb... was a pre-launch Dinc user. Very nice move... the Rezound is an awesome phone.
[Droid Incredible Q&A, Help & Troubleshooting] POQbum:
Depends how careful you are with the phone. I usually never have insurance and it worked out fine. I cracked the screen- replaced easily and cheaply and installed it myself. Same with speaker. Really the only thing to worry about unless you drop it in water, in that case, it often will dry out and work fine even then.
[Droid 2 Global General] winoz:
I am using stock ROM, with Widgetlocker, installed ADWnotifier, I want to display unread SMS and missed call on my lock screen, but didn't work.
[Droid 2 Global General] eatatjoe69:
Hi go to android market an search 'Missed It'. That will do the trick
[Nexus S Q&A, Help & Troubleshooting] arianR10:
Hi folks,

With the backup & restore function turned on, the Market automatically restores ALL of the applications I have ever installed using my associated Gmail account. I have been downloading applications using this account since 2010 and I have a large collection of applications, many of which I do not need, which are restored every time by the Market. What I want to know is how I can permanently uninstall or disable these apps from restoring. I want to restore only a select few of my apps, and not all. I have explored the different settings of the Market and I unfortunately could not come up with a solution to this problem. Hopefully someone here knows the answer to this problem.
[Nexus S Q&A, Help & Troubleshooting] arianR10:
may someone kindly help out. :)
[Nexus S Q&A, Help & Troubleshooting] mabry:
Since I flash my phone alot, I had that happen to me. Now what I do is UNCHECK the backup and restore option in settings. If that don't work, then back up your apps, etc, and do a factory reset. Go through the welcome setup and when it comes to the part where it asks if you want to backup and restore then uncheck it.

Before you do the factory reset though, clear your market history and cache, first.

Hope this helps.
[Samsung Epic 4G Touch] Darrien13:
OK I get my device tomorrow and I'm so happy! I plan to root it and I just wanted to know if flashing an ICS can potentially harm the device? Say that I flash back to a GB rom will everything still be perfect and work? Thanks:D

Sorry for all the questions just want to be sure for my device's arrival!
[Samsung Epic 4G Touch] docmarioce:
Do a nandroid backup first and if something goes wrong you can allways restore the back up and voila everything working perfect again. I do it all the time
[Samsung Epic 4G Touch] Toleraen:
Any flash can potentially harm a device...like docmarioce stated nandroid first. You can always pull one of the GB recovery ROMs from the Dev forum to go completely back to GB.

I'd highly, highly recommend watching some of qbking77's youtube videos on flashing, he's done an amazing job putting these together.
[Samsung Epic 4G Touch] nitro_c4:
^^^ yeah, QBKing is awesome!

You have to Odin back to EL29 if you are on an ICS ROM and want to go back to GB.

Read, read, read before flashing any ROM :)

Enjoy your new phone!
[Samsung Epic 4G Touch] darkfire2024:
Don't use the recovery found on ANY ICS ROM. That means if you flash CM9, Calk's, Blendz, Venum (any ICS Rom leak), you will have ICS Rogue Repack Recovery which is known for BRICKING so many phones.

Note that, it's not the creator of the Rogue Recovery repack to blame, it is that Samsung is packing faulty kernels; Steady Hawkin, the creator, has even bricked his phone using his own tried and true methods. For some reason, the samsung kernels for ICS mess up the partitions on the phone when the recovery on an ICS leak is used.

So to sum things up.

1. DO NOT FLASH/WIPE/ RESTORE anything with the recovery repacked with the ICS leak ROMs.

2. If you want to flash, odin stock EL26 CWM.

(You might want to use the autoroot method by sfhub to install because odin'ing stuff gives you a yellow triangle on boot—Don't trust me on this, just a guess)

3. DO NOT FLASH/WIPE/RESTORE or even think of using the recovery found on any ICS ROM. Some CM9 users have bricked their phone simply by wiping cache on the recovery in CM9.

When you boot into recovery on an ICS ROM LEAK, and you see ROGUE, DO NOT FLASH/WIPE RESTORE! Run away!

My tone might be overexaggerated, but there have been many bricks reported on the CM9 dev thread here that I frequent. Those who used the rogue repack kernels found on ICS rom leaks instead of taking the safer route of odin'ing stock EL26 CWM and flashing/wiping/restoring on that, have bricked their phones.

CM9 thread

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

More info:

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

Be safe, and read read read.
[Samsung Epic 4G Touch] Paden32:
Flashing ICS

I have successfully flashed a ICS ROM and then restored a backup to GB. This was before I was warned I have seen many of my friends hard brick there phone. I am waiting for a stable ICS ROM with a stable CWM.
[Samsung Epic 4G Touch] M1nze:
same here. i actually wiped everything and it didnt brick. works just fine now! GB >>>> ICS
[Samsung Epic 4G Touch] Paden32:
Flashing ICS

I have been hearing from people that the official ICS rom comes out March 15 I hope it does cant wait.
[Samsung Epic 4G Touch] cidica:
ICS is actually being pushed to the International version now in some places. I don't honestly thing we will see a March 15th date for us however (but hey I could be wrong)

As for Flashing ICS please read carefully there have been a ton of Bricks flashing ICS roms with ICS based kernels that have a recovery added to them. Your best bet honestly is to relax and chill read for awhile or a bit and when you feel confident in doing it then do so. My words for you ALWAYS keep Odin handy and if you do want to go back to a GB based rom then Odin a GB rom (like sfhub's EL29 Stock rooted) and push a GB based kernel with his auto root package.
[Samsung Epic 4G Touch] darkfire2024:
Some people are lucky when using the ICS kernel recovery; in fact I am one of them :D. But eventually that luck will run out. I'm fortunate that I learned about its dangers before I could get a chance to brick my phone.
[Samsung Epic 4G Touch] cidica:
Yes some have been lucky this is true. But when I see one of our own devs Brick their device from doing it not just users (thought they do count as well) I tend to be on the safe side and give people the way not only myself but others have done things for flashing between different roms and have so far always been safe :)
[Samsung Epic 4G Touch] dante32278:
Here is what worked for me...

Download stock rom for ics fc07

Download rogue stock fc07 kernel

Place both on external SD card

Use sfhub's one click root method

Use sfhub's clockwork method

Make a backup

Wipe everything and run calks format all zip

Flash the rom and kernel (and modem) in the same setting and ur gtg
[Samsung Epic 4G Touch] Darrien13:
Would you guys recommend not flashing anything ICS?
[Samsung Epic 4G Touch] JohnCorleone:
I would say as long as you have Odin and take your time (whether its going to ICS or back to Gingerbread) then you will have no problems. If you want to be really safe, make it a rule that you flash ICS from a Gingerbread EL26 kernel w/CWM Recovery and if you want to flash something else once on ICS, Odin flash back to stock Gingerbread, Odin flash kernel with recovery and go from there. You can always PM me and I can shoot you links as well. Some people aren't having problems flashing from ICS w/ custom recovery but many have..including some devs
[Samsung Epic 4G Touch] C3jay:
Mobile odin??

Edit... Never mind
[Vibrant Android Development] FaultException:
CyanogenMod for the Vibrant currently contains intermittent issues with the emergency dialing system. I strongly urge you NOT to use CyanogenMod on the Vibrant until they can be fixed.

Help by testing a test CM9 build for it​
[Vibrant Android Development] akfelipe:
awesome! nice to have you as "The bringer of CyanogenMod", if it wasn't for this great community, vibrant would be dead!
[Vibrant Android Development] jvpde:
I know you aren't in charge of these things Fault but any idea when we'll get a new nightly?
[Vibrant Android Development] FaultException:
By the looks of it, we might get one tonight.

http://jenkins.cyanogenmod.com/job/android/
[Vibrant Android Development] lems111:
The latest nightly link seems down. Would someone else confirm?
[Vibrant Android Development] flapane:
Working atm
[Vibrant Android Development] flapane:
I don't even know who the specific cm7 vibrantmtd mantainer is (if any), that's why I asked if the project had been declared dead. No sign of activity since late February, while other phones have been getting constantly updated nightly builds. There will be a reason for sure.
[Vibrant Android Development] akfelipe:
°_° The OP guy is the maintainer, and we will have cm7 nightlies either this week or next. Cm servers are being upgraded...
[Vibrant Android Development] FaultException:
Glacier hasn't had any since ours.

Captivate has had 1 since ours.

Fascinate hasn't had any since ours.

Galaxy S hasn't had any since Feb 16th.

It doesn't mean that it's dead...
[Vibrant Android Development] akfelipe:
does this mean what i think it means :)

cm: Tag 7.2.0-RC1​

looks like cm7/gingerbread is reaching its ripeness!
[Vibrant Android Development] Stevethegreat:
It still lacks proper TV out (no hardware decoding). And I'm not sure whether the mute/unmute bug has been solved or even whether the GPS is truly functional... apart from those, yep, the ROM seems quite stable...
[Vibrant Android Development] akfelipe:
O never really use TV out or GPS so I wouldn't know, but the mute/unmute should be fixed by now,

the mainteiner is that one who deals with device specific bugs...ask him what's the status with those two.
[Vibrant Android Development] FaultException:
I'm not sure if the mute-unmute bug is localized to Vibrant. (The changelog was copied from Captivate, which said the mute-unmute was hopefully fixed, Galaxy S also says it.)

(I'm not saying I won't I'll look into it though)

The mute-unmute bug is not fixed. I don't know about TV out, my cable is faulty. raymonddull tested it for me, he got black and white, which is more than I got, but his cable was faulty too!

GPS is most likely poo. Just flash YAGF2 or what ever works for you.
[Vibrant Android Development] Mostdef:
update-cm-7-20120226-NIGHTLY-vibrantmtd. Never work on my vibrant cause of the systemUI error. Are they going to build another nightly or is this the end of the nightly build?
[Vibrant Android Development] Stevethegreat:
TV out works but only partially. Its quality is worse than Froyo's (Samsung's official) and it shows a black screen when someone tries to play a hardware accelerated video.

The mute/unmute bug most of the times is there.

GPS may work to some, it won't to most and the fixes are hit or miss on equal measure. Personally I have last had my GPS working on Froyo days. I know it's not a big deal for most people here on XDA, but for the rest of the world (outside XDA) GPS is kind of a big deal and it's one of those modules that makes smartphones to be "smart"...

Anyhow the situation for CM7 (on our Vibrant) is about the same as in those GB ports from i9000; i.e. most things work, not all. If one needs the full experience of the phone *has to* go back to Froyo ... sadly.
[Vibrant Android Development] FaultException:
Can you play hardware accelerated video on Froyo via TV out?
[Vibrant Android Development] Stevethegreat:
Yes, everything works on Froyo as intended... in fact because TV out is a feauture I often use (useful for presentations and such) I often have to go back to Froyo...
[Vibrant Android Development] ginzberg:
update-cm-7.2.0-RC1-vibrantmtd-signed.zip is up now on get.cm

Btw, anyone else not seeing "CyanogenMod Nightlies" in Premium Rom Manager? I used to, but it was quite some time ago.
[Vibrant Android Development] jvpde:
10char....
[Vibrant Android Development] FaultException:
New nightly cooking now: http://jenkins.cyanogenmod.com/job/android/304/

I'll start a build each night for one, until automatic nightlies are sorted out.

EDIT: Hmm, looks like there is a problem right now. I'll try again tomorrow.
[Vibrant Android Development] FaultException:
New nightly is up.

http://get.cm/?device=vibrantmtd
[Vibrant Android Development] creeve4:
Any progress on the mute/unmute bug?
[Vibrant Android Development] FaultException:
No solution yet.

I'm cooking a build with NS libaudio per raymonddull's idea, so we can try that.
[Vibrant Android Development] ipnekgs:
There's a bug with the lockscreen:

I have a PIN to unlock the screen. Then I enable "Skip on security" to disable the lock screen if security screen lock is enabled (PIN).

Settings>CyanogenMod>Lockscreen>Unlock options>Skip on security

After enabling that option the normal lockscreen still shows up, in my case the rotary style (It happens with all styles)

If this is a known bug already reported or a new feature then please disregard.
[Vibrant Android Development] FaultException:
Try this: http://androtransfer.com/faultexception/tests/ns-test.zip

And this: http://androtransfer.com/faultexception/tests/cc-test.zip

And let me know if you get tunnel voice please.

There may be UI bugs on both, (on lockscreen, etc), ignore them and test tunnel voice.

Thanks.
[Vibrant Android Development] creeve4:
Results:

ns-test: 10 trials and no tunnel voice!

cc-test: several trials, definite tunnel voice.
[Vibrant Android Development] FaultException:
Can you try 10 more times to make sure on NS-test?
[Vibrant Android Development] creeve4:
I received 20 more test calls, none had the tunnel voice.

During 1 of the 20 calls I could not hear the caller from the beginning to the end of the conversation, but they could hear me (may have been a fluke? )
[Vibrant Android Development] FaultException:
https://plus.google.com/117352190296689076821/posts/P7e2SWTYpA2

Thanks.
[Vibrant Android Development] FaultException:
Creeve4, can you run that as a daily for a few days to test further?

Sent from my Vibrant
[Vibrant Android Development] Dougfresh:
Dan do you want me test. I'm on ics but I have a spare vib.nvm I'm dl....
[Vibrant Android Development] FaultException:
Doug, yes please.

Creeve4, I'll be posting a few more for testing today.

It's a weird situation right now, the nexus libaudio is probably not the fix.

Sent from my Vibrant
[Vibrant Android Development] creeve4:
I'll be watching for your posts, I'm happy to test for you.

Does the Nexus libaudio break other things?
[Vibrant Android Development] FaultException:
No, that build shouldn't even have the NS libaudio.
[Vibrant Android Development] creeve4:
My mistake, I assumed the "ns" in the file name stood for nexus s
[Vibrant Android Development] FaultException:
It does. I found out afterwards it shouldn't be the Nexus. I need to find out why it does work.
[Vibrant Android Development] FaultException:
creeve4, is it still working for you? That's bizarre if it does... see story here:

https://plus.google.com/117352190296689076821/posts/Td4tGUSXjEz

Are you sure you're not using cc-test?
[Vibrant Android Development] creeve4:
Strange...

I'm positive it was the ns-test that I flashed, but just to be sure, I flashed it again. It is still working for me.
[Vibrant Android Development] FaultException:
Wipe and test flash this one please:

http://androtransfer.com/faultexception/tests/ac-test.zip

Thanks

EDIT: original post said cc-test.zip, but it's ac-test.zip.
[Vibrant Android Development] creeve4:
Flashing tonight, I'll report back
[Vibrant Android Development] Stevethegreat:
May I ask what is the purpose of the new nightlies as long as they don't solve the 3 prime bugs been left of on Vibrant's CM (i.e. TV-out, mute/unmute, GPS)?

I'm not trying to be rude by the way, I honestly do want to know what's the puprose of (the) new nightlies. The ROM is more than robust already as it is (as long as you don't want to use TV-out, GPS and have no problem with muting and umuting in each and every call).
[Vibrant Android Development] FaultException:
Nightlies also include common changes, not necessarily a bug fix or changes for the specific device.
[Vibrant Android Development] ginzberg:
Nightlies are just that, automated daily builds based on the latest source [generally, built at night]. Nightlies are built independent of a major issue being resolved, they are built independent of even a single line of code being altered.
[Vibrant Android Development] Stevethegreat:
Yes I'm aware of this, sorry if I was a bit unclear. Let me rephrase: There can be little or no practical reason for someone to flash the new(er) nightlies, correct?

By the way is there's a plan for the remaining major bugs to be worked or are they unfixable? Thanks.
[Vibrant Android Development] creeve4:
Tested with 10 incoming calls. All calls had minor tunnel voice.

When I answered the call and first spoke my voice was clear, but after the caller spoke my voice became "robotic" but then gradually returned to a clear voice.
[Vibrant Android Development] FaultException:
If you only flash nightlies for bug fixes, then yes, you have no reason to flash them. If you flash nightlies for bleeding edge CyanogenMod changes, and to be the closest you can to the next release, then no, you do have reason to flash them.

Concerning the second part; they are bugs, so hopefully a fix will be found. Besides GPS, if no GPS flashables work for you.
[Vibrant Android Development] FaultException:
Edit: nvm 10ch
[Vibrant Android Development] FaultException:
Can you try this please: http://androtransfer.com/faultexception/tests/aries-nocp.zip

Thanks.
[Vibrant Android Development] creeve4:
Tests Results

20 Incoming calls from several sources: Consistently clear, no tunnel voice.

10 Outgoing calls to several sources: Consistently clear, no tunnel voice.
[Vibrant Android Development] Stevethegreat:
First of let me be clear and say that I wish to ignore none of your hard work which *actually* made this phone (mostly) usable. Many thanks won't be enough for all that you (and the CM team in general) had offered us...

Having said that, I often think that I have first have to have my device fully working before starting to care about/have new features. In other words everything new (added) is welcome, but the major functions with which the phone came with are/were even more so...

Anyhow, like I said thanks for your great work. I'll certainly keep an eye for future development on CM7...
[Vibrant Android Development] FaultException:
I understand.

A tunnel voice fix will hopefully come soon. (I still need to find out if the lines I commented out are necessary, if it works for others, if this is an acceptable fix and make sure it doesn't break E911)

Try this zip if you want to, in the mean time:

http://androtransfer.com/faultexception/tests/aries-nocp.zip

About the GPS, have you tried YAGF2? (link: http://goo.gl/IpQpR)

Has your GPS worked on any other custom ROM? If so, which?

Does your GPS work on stock?

About the TV out, how worse is the quality than stock? The TV out cable I ordered from Amazon is broken, and doesn't even work on stock. I'm not sure how much can be done, AFAIK, the TV out is done via proprietary blobs. (Besides how it accesses the frame buffer. Which I don't know.)
[Vibrant Android Development] FaultException:
Anyone interested, please flash this .zip and test it for tunnel voice, please report back on this thread.

http://androtransfer.com/faultexception/tests/aries-movcp.zip
[Vibrant Android Development] flapane:
Latest nightly installed, will report any strange behaviour (tunnel voice included) here.
[Vibrant Android Development] creeve4:
Does having the "light sensor filter" in Cyanogenmod settings enabled have much effect on battery life?
[Vibrant Android Development] c-pimp:
Man, in loving my cm 7 ! Thank you FE :-) using Eugene streamline I still get GPS locks after deep sleep and I get over two days with basic phone use.... And best of all no tunnel voice on calls... Perfection

That's on the stock battery by the way