yashsingh1/xdaforums huggingface dataset:
[Sony Xperia T, TL, TX, V] smardu:
Is anyone using corporate mail, messenger and 3G on all day? Because with JB my battery drains in max 6h. Same scenario but with ICS and the battery drains in 9-10h and i see in here 1 or 2 days of battery life.
[Sony Xperia T, TL, TX, V] phreax9802:
Try disabling Google Now. I found that it's causing excessive wakelock through Google Maps.
[Sony Xperia T, TL, TX, V] PippeR_678:
2 weeks with the V

Ok, so I've had my Xperia V for two weeks now after waiting a long time since it has only been released with jelly bean here in Switzerland. So I got no experience and comparison with ICS.

The first week I was quite disappointed by the battery performance as wasn't able to get through the day without charging it midday. But now after the last weekend it suddenly runs for more than a day! Does Android have to be broken in for a week?! Of course I also used to do some uncharge, full charge cycles on my former Android devices to achieve best battery performance, but the difference was never that serious...

Besides that I really like it :o of course there are quite a few bugs I hope Sony will sort out soon. First of all I also noticed the Walkman issue of pausing up to 30 seconds between tracks. Another quirk is the speaker not always reactivating after unplugging the headphones. In that case I need to replug and try again until the speaker plays sounds again... mostly one or two times :eek:

Oh, I always get the "no SIM card" warning on the lockscreen. And today after loosing mobile reception in a tunnel it didn't reconnect and turning on and off plane mode also did not help. But then while trying to run a manual scan of networks the phone dimmed out and warm booted on its own!
[Sony Xperia T, TL, TX, V] vokkE:
I got the update tonight, but havent updated yet. When updating, should I back up my images and apps? And should I even update? Can I root etc after the update? :) Haven't rooted or unlocked bootloader yet, cos I've done great so far

And another thing: where are all the devs on Xperia V? Coming from HTC Desire, it's very sad that such an awesome phone like this only has like 1 custom rom, and there's hardly anything "custom" about it... :(
[Sony Xperia T, TL, TX, V] papped:
One of the fixes reported by various people for fixing the JB Maps massive wakelocks in several different threads...

Maps > Settings > Location Settings > Report from this device > uncheck

Tired of having to freeze/defrost maps all the time with it eating up 30-40% of the battery life doing nothing, so giving it a go.
[Sony Xperia T, TL, TX, V] Ferrero Rocher:
what difference does it make if i move my apps to my SD card?
[T-Mobile LG G2x] abccg:
So my g2x front screen glass was broken. Replaced it with a new one and after reassembly and powering the phone on, its responding to all my touches but the screen is very distorted. It looks like a 90's crt tv going crazy, with the noise on the screen if you know what I mean.

Any ideas? Or did I just seat the digitizer wrong or the ribbon on the screen is off by a pin or two?
[T-Mobile LG G2x] redmonke255:
Try resetting the connections. If it's still like that it's a low quality digitizer and I would try to return it.
[T-Mobile LG G2x] edekalil:
If the digitizer is responding fine then make sure there is nothing pushing against the LCD (anything between the LCD and digitizer) and the connections are seated correctly.

Eddie
[T-Mobile LG G2x] abccg:
Thanks for the replies. I cant find the rubber seperator thing could that be the problem? I looked at the LCD and nothing is in between it and the digitizer but it appears to be loose. All connections are seated correctly.

If the LCD was being pushed from the backside thats metal would that be a problem?
[T-Mobile LG G2x] redmonke255:
If the LCD is being pushed it shouldn't be a problem. If a piece of metal was touching the digitizer, then you'd have interference which would cause ghost touches and poor accuracy.
[T-Mobile LG G2x] abccg:
Okay so I took it apart and reassembled it like 5 times and I'm getting frustrated.

Basically the issue is the screen is all wonky after I power it up. The picture was perfect with the old digitizer that was cracked and had water damage, how is this possible? But when I plug everything in I get the wonky picture.

So is it my LCD or the digitizer?

By the way all touch functionality works 100% so whats the deal... because the LCD was working before with the broken digitizer that had no touch working lol.
[T-Mobile LG G2x] mansa_noob:
You could try to unplug the digitizer and see if the picture becomes normal. If so, it is the digitizer.
[T-Mobile LG G2x] abccg:
Tried that and no luck. :(
[T-Mobile LG G2x] mansa_noob:
It seems then either bad LCD or connector, or even hardware... IMHO you need another phone to further rule out any possibilities.
[Samsung Galaxy Nexus] simple23227:
Hello,

A bit about my Nexus: Bought it online, it's the Domoco version, unlocked, rooted and been using just fine with many custom ROMs.

So yesterday morning, I was talking on the phone with a friend without any problem. After hanging up for a few hours, when I was about to call someone else, I realized my phone didn't have any signal at all. And it has been like that until now, about 48 hours.

It happened so suddenly without any warning. The phone has never been dropped and everything else working just fine.

So here's what I have tried:

- Restart the phone (multiple times)

- Batter pull (multiple times)

- Factory reset the phone (multiple times)

- Wipe cache and dalvik cache in CWM (multiple times)

- Downloaded SetCPU and set the minimum to 700Mhz (instead of 350Mhz)

- Reflash the ROM and tried with other Custom ROMs (I tried Xenon, Xylon, PA, and Carbon ROMs)

- Reflash the Radio and tried with other Radios too (I tried UILH1, XXLH1, SC04DOMLE3 and some others ...)

- I also went to Tmobile and request a new sim card - same problem.

- I borrowed a sim card from another Tmobile customer to try it on my phone - no signal - but the sim card works just fine on his phone.

I ran out of thing to try and I dont understand what happened ... anyone has an idea or something else for me to try ?

Anyone experience this before ?
[Samsung Galaxy Nexus] JediDru:
Welcome too my hell. I have a playstore one now but my first Gnex was an international one and it has this same issue. Its a PCB problem a warranty would fix. I'm near Chicago and a few people have told me there is an electrical engineer downtown that fixes stuff like this. I don't have a price but I think something like this is your only option. Mine sadly is still a battery charger:thumbdown:
[Samsung Galaxy Nexus] bodh:
I know it sounds stupid, but have you tried toggling airplane mode? I run into the occasional loss of signal when im at work [fair to weak signal in the big metal box], and a reboot is the only thing that fixes it for me. Mines a play store model.
[Samsung Galaxy Nexus] simple23227:
Ah yes, I actually did try that too but forgot to mention. I tried toggle airplane mode on and off, also the 2G only mode on and off. But it didn't help with anything.

Thanks for the suggestion.

So I guess I have to look for an electrician then, cause I have this phone just a little bit over a year so warranty is a no go for me.

Thanks for the idea.

PS: anyone else has more option for me ? I just wondered if I have bricked my phone ... cause I flashed lots of diff. ROMs to try out but never gotten a bricked phone before, could this be a bricked phone ?
[Samsung Galaxy Nexus] bodh:
Bricked refers to a phone that does what a brick does: nothing. It doesn't boot, it does not light or attempt to boot, it does nothing. This is a signal issue..I have no prior experience with docomo, but this thread came up on search: http://xdaforums.com/showthread.php?t=1574018, maybe it'd be helpful. Have you converted it to yakju or takju and tried a google factory image?

And this: http://xdaforums.com/showthread.php?t=1554150. If it is a circuit board, it kinda looks like s.o.l., and im sad to say that to you.
[Samsung Galaxy Nexus] chowabbajack:
I wanted to let you know that I experienced the same issue. I bought the unlocked Docomo Galaxy Nexus, and had it working fine on T-Mobile for half a year, and then suddenly had no signal on Tuesday. Nothing I did - factory reset, battery in and out, sim card in and out - could fix it. Have you tried using different sim cards in your phone to see what works and what doesn't?

I figured out that my phone will accept AT&T, and actually does connect to T-Mobile while roaming (I used an international sim card). But, my phone will say "Cannot find mobile network" when any T-Mobile sim card is inserted.
[Samsung Galaxy Nexus] wocman:
I also have the same problem with the docomo phone. ATT Sim card works. Tried other's T-mobile sim cards and it doesn't work. I wonder if somehow the IMEI has been blocked by T-mobile.
[Samsung Galaxy Nexus] chowabbajack:
I know others who bought their GNEX through the Play Store and those work just fine with T-mobile. I tried their sim cards in my phone and it doesn't work. I don't think T-mobile is intentionally blocking the docomo phones, because I'm getting T-mobile through roaming, when I use an international sim. My guess is they're doing something to the cell network that just somehow leaves our configuration out. Hopefully it's temporary, but who knows.

Worse case, I'll just purchase a Nexus 4, because I love 4G data for just $30/month with T-mobile. Anyone else got suggestions?
[Samsung Galaxy Nexus] simple23227:
Alright, update on this and there' good news. I called Tmobile and they said my IMEI is actually Blocked. The reason, according to him, is that Tmobile usually sweep the network to clean up all "un-supported" devices, so my device is apparently one of them and therefore got blocked about 2 days ago.

So he said for this, he needs to escalate it to business support and they surely can unblock it for me, but I have to wait until Monday since they don't work on weekend. But well, that's surely a good news. phewwwwwwwwwwwwww !!!

So to all of you guys who are in the same situation, make sure you call Tmobile first before flashing crazy like I did LOL.

Thanks for all the help.
[Samsung Galaxy Nexus] alexwinsberg:
I'd love to know if you are able to get this unblocked and working as I have the same problem as of Tuesday. I was traveling and went into a TMO store, and they told me it was NOT IMEI blocked. In fact they looked at the IMEI and read the page and said 'it was not eligible for blocking'.
[Samsung Galaxy Nexus] alexwinsberg:
I called TMO to see if my phone is IMEI blocked, and through three levels of support the universal answer was no. I'm now fully confused because if it's a hardware issue, why did several people all have the same problem all on Tuesday. For those others who are having issues, can you see the TMO network but not connect to it? That's what I have, I can see TMO and AT&T but haven't been able to connect to either one since Tuesday.
[Samsung Galaxy Nexus] chowabbajack:
I'll call up T-Mobile tomorrow and ask if they IMEI blocked my device. I had them reset my signal and give me a new SIM card, but didn't realize it could have been IMEI blocked. I'll give them a call on Monday and let you know what the result is. Maybe it won't be too late to cancel my order on that Nexus 4...
[Samsung Galaxy Nexus] alexwinsberg:
I'm quite confused. I've been told last Thursday in a TMO store and with tech support that I didn't have an IMEI block, and the same with three reps tonight. I know the Sim Card is good, and so I'm being told its a hardware issue. However, several of the same phones had the same issue on the same day, so I can't buy it's a hardware issue. Has anyone with this issue flashed a new or different radio into the phone, either before or after the service loss? I have not, running it as it came out of the box.
[Samsung Galaxy Nexus] chowabbajack:
I just got off the phone with T-Mobile Support, and they told me the device is not blocked. The reason is that T-Mobile cannot block or unblock devices that are not registered to T-Mobile. So I'm back to square one on this.
[Samsung Galaxy Nexus] alexwinsberg:
chowabbajack - When did you first have a problem, last Tuesday? Did you prior to that do any flashing or radio changes to the phone?

We're in the same spot....
[Samsung Galaxy Nexus] chowabbajack:
I did not do any kind of flashing or radio changes prior to Tuesday, when I lost signal.
[Samsung Galaxy Nexus] alexwinsberg:
That makes me think its something to do with the radio software, because I am the same the problem overall doesn't seem as large as the number of phones I perceive were bought on the Docomo deal.
[Samsung Galaxy Nexus] vanessax17:
Ive been using the docomo version of the nexus as well on tmobile for almost a year and it was since last tuesday when it no longer recieved any singal. with some digging around and too many phone calls, I found that the imei number on the phone is not the same as the one under the battery. i have the generic 004999010640000 imei right now and it not sure how i got it. as i bought it unlocked.

what i have tried:

reboot, battery plug, reinsert sim, factory reset, root and flash, got a new sim card, relocked, unlocked

sim card works on other phones.

also i have called tmobile and samsung endlessly and this is what i got:

tmobile cannot unblock the imei since it is not from them.

samsung is redirecting me to their japan branch.

docomo i cannot reach.

my phone before last tuesday:

unrooted stock 4.2.1

been testing different things to see if there is any way to restore the imei

also using root explorer, i cannot find my efs folder....
[Samsung Galaxy Nexus] :
I've got the same problem since last Tuesday with my GNex and T-Mobile.

Mine is not from docomo though, but the French phone provider SFR, unlocked through FDocomo apk.

Rooted phone, running 4.2.1., no changes whatsoever in the past month and it worked fine until Tuesday, so I don't think I'm responsible for having no signal.

Honestly, I am relieved to see we are quite a few to have this problem, and also very pissed at T-Mobile for causing all this. What should be the next step then? Is there any chances they fix the issue quickly? If not, I might just go to the competition. I've tried AT&T sim cards and they work fine.
[Samsung Galaxy Nexus] alexwinsberg:
I have the exact same generic IMEI number as you, which does not match the number under the battery. I'm not liking the news that you did flash and still no go. I'm a novice at this stuff so please keep us posted.
[Samsung Galaxy Nexus] :
Forgot to mention, I also flashed my GNex several times to both stock and customs ROMs, going back to ICS 4.0.4. No chance and my guess is flashing is useless.

Has anyone try to install new radiobands? It comes out of my looking around as the only possible DIY solution, but I'm not very hopeful.
[Samsung Galaxy Nexus] alexwinsberg:
TBH, not sure how to install the radiobands, but that is not good news you had.....
[Samsung Galaxy Nexus] papi92:
Rerun the new Docomo unlock app and it fixes it. Be on 4.0.4 when you run it tho
[Samsung Galaxy Nexus] JediDru:
I started looking at both of my phones tonight and noticed one thing very weird. The IMEI SV numbers are different. The good phones being 04, the Bad phone is 01. Looked online and found very little info. Any ideas?
[Samsung Galaxy Nexus] alexwinsberg:
I don't think I ever ran the docomo unlock app....anynidea where to get t?
[Samsung Galaxy Nexus] :
You can find it here : http://xdaforums.com/showthread.php?t=1548210

I have already reran FDocomo apk several times, including on 4.1.2 (not 4.0.4 though) and it made no change.

Btw my T-Mobile sim card worked whether or not FDocomo had run, I guess because TMO sold Galaxy Nexuses too.
[Samsung Galaxy Nexus] chowabbajack:
Looks like we just got the short end of the stick. I've ordered a Nexus 4, and will try to unload my GNEX. If anyone has managed to get their phone to work, let us know!
[Samsung Galaxy Nexus] alexwinsberg:
So, somehow our phones got locked out of TMO? I'm quite confused because I've not spent a lot of time looking at rooting and flashing my phone.
[Samsung Galaxy Nexus] :
New developments!

I flashed my device back to stock 4.0.4 and ran FDocomo. I managed to have network for a couple minutes. Needless to say, I was excited about that! Unfortunately it went back to the same situation very quickly.

What I think happens is TMO has blocked the generic IMEI number FDocomo gives to devices. Does anyone have an original IMEI and still encounters this problem?

If I'm right, I think I'll just purchase an IMEI unlock number. That would suck, but the situation wouldn't be as bas as I thought, and I would just end up having a genuinely unlocked phone, which is a plus.
[Samsung Galaxy Nexus] alexwinsberg:
I have the generic IMEI number, haven't flashed or unlocked or rooted, yet.

---------- Post added at 10:42 PM ---------- Previous post was at 10:19 PM ----------

How do you do this part?
[Samsung Galaxy Nexus] :
How did you end up with a generic IMEI then? I'm just curious
[Samsung Galaxy Nexus] alexwinsberg:
No idea. I got the phone last April from a deal that was going on via a Las Vegas seller (not sure I can use their name), opened it up, dropped my SIM in and have been happily using it ever since. Then, Tuesday, nothing and I noticed when trying to troubleshoot that I have the same generic IMEI that was listed elsewhere in this thread.
[Samsung Galaxy Nexus] :
I think you just bought off a Nexus that has been unlocked through the **** Docomo app then.

For an actual (and legal) sim unlock, you can enter your IMEI number (actual one, that is) on certain websites and get an unlock code for $20. It's still way cheaper than what most phone service providers charge for it, so it's not too bad a deal.
[Samsung Galaxy Nexus] alexwinsberg:
Well, it was a big sale, so did they run the app on all of them? I really need my phone back....
[Samsung Galaxy Nexus] :
I bought my unlock code and my GNex works perfectly on TMO network now. So TMO has definitely blocked phones with default IMEI.

What you might want to do is to flash your phone back to stock ROM (4.0.4.) in the hope that your original IMEI will replace your current one (for example if FDocomo was run, that will work). If that fails, I'm afraid you have a corrupted IMEI and really don't know how to fix that on GNex.
[Samsung Galaxy Nexus] alexwinsberg:
I appreciate the advice....flashing and such feels quite foreign to me. I do have downloaded the Samsung Galaxy Toolkit V10.1.0, but really don't know what to do. Also, do you think an unlock code will work for me?
[Samsung Galaxy Nexus] wocman:
Where did you get the unlock? The only one I found was cell unlocker but it is $30.
[Samsung Galaxy Nexus] :
There, 20 dollars: http://www.samsungimeiunlock.com/samsung-galaxy-nexus-unlock
[Samsung Galaxy Nexus] alexwinsberg:
I went to this site, input the IMEI under the battery (not the generic one), and the site told me they don't have a SIM unlock for me.....uh oh...
[Samsung Galaxy Nexus] testamentg:
This is good news.

Btw, I'm using Docomo GNex and havent seen any signal prob with it.
[Samsung Galaxy Nexus] alexwinsberg:
Still can't get an unlock code for my GNex....I must be doing something wrong. Any advice?
[Samsung Galaxy Nexus] tdy2kn1:
BUMP same problem. HELP!!
[Samsung Galaxy Nexus] bodh:
http://www.xda-developers.com/andro...tting-the-us-cell-phone-market-back-10-years/
[Samsung Galaxy Nexus] alexwinsberg:
Now I am so confused. I am in fastboot mode, and it says the LOCK STATE is unlocked. I'm trying to flash to it, but am getting errors. Ugh.

Well, no I've flashed the phone back to 4.0.4, and I still get the generic IMEI, and still am unable to connect to the TMO or ATT networks.

I have no idea what to do now.
[Samsung Galaxy Nexus] bodh:
in fastboot, locked state refers to bootloader, i.e. yours is unlocked meaning you can flash partitions.. so the errors have to do with something else. According to the above thread, it seems your generic imei is the problem. there was a thread on recovering imeis on the sii, let me see if i can find it..

This is what i was talking about: http://xdaforums.com/showthread.php?t=1264021

Btw, do you have an early nandroid?
[Samsung Galaxy Nexus] alexwinsberg:
Thanks! I'm going to check it out. I found a thread about the generic IMEI on my phone here:

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

My issue, I have no idea how to apply the theory described in that thread.
[Samsung Galaxy Nexus] bodh:
The grand theory of sim unlock thread, that you cited, may offer you some help if you read through it. But I believe that would mostly apply beforehand if you still had your imei, rather than a generic. DO YOU HAVE AN EARLY NANDROID? Backup is rule #1, and that may be your true saving grace.
[Samsung Galaxy Nexus] alexwinsberg:
I don't know what an early Nandroid is, and its unlikely I have a back-up if I had to do something.

Very frustrating, as I can't even get the ABD tools to try the IMEI theory because it won't properly unpack.....ugh again.
[Samsung Galaxy Nexus] alexwinsberg:
Well, it seems to me that the generic IMEI is the issue, and I am stuck trying to run the fix suggested in the thread above. I get to the terminal services, but when I try to log at the log file, I get Permission Denied. I can't sort out where to go from here.
[Samsung Galaxy Nexus] bodh:
Did you get adb working? http://xdaforums.com/showthread.php?t=1626895 Part A should help with that. Didn't quite understand what log file you're looking at.
[Samsung Galaxy Nexus] alexwinsberg:
Well, with certain toolkits, ABD is working, but off of just the command prompt, no, it is not working. This is the problem with not knowing what I am doing....I don't know what I am doing.

I'm trying Option 1 from this thread, but I can't even get to the third step of the first part, the "cat nv.log" portion. That is where I get permission denied.

http://xdaforums.com/showthread.php?t=1606982
[Samsung Galaxy Nexus] bodh:
Probably because you have to cd, or change directory to where adb is in your path. I do not believe you have satisfied the needs of that thread: a rooted phone, first and foremost. As someone else suggested higher up in the thread, your best bet may be to learn to unlock and fastboot flash the 4.0.3 or original images to see if it recovers. http://xdaforums.com/showthread.php?t=1626895 If you unlock the bootloader, you can always root easily and then maybe these other tools would work for you, but there's also the chance of just losing the imei of the phone and its capabilities completely, which is what it would be anyway if you continued to be stuck without a connection.
[Samsung Galaxy Nexus] alexwinsberg:
I did do that, its unlocked and rooted using the GNex Toolkit. I went back to 4.0.4, no luck, still generic IMEI. Quite frustrating, for sure.
[Samsung Galaxy Nexus] bodh:
Okay so after actually reading docomo's sim unlock thread, I believe it would work for you. First off, get root checker and make sure it shows rooted. Next, download terminal emulator and grant it root permissions. Then SKIP ADB SHELL and run these commands directly on your phone terminal [if you're still having adb issues]. I'd personally use fdocomoV2 of app, since that it the version mentioned in the guide and current to the guide's last edit. Read it several times first! Do the first method to verify it'll work for you, then do the second. If it does work and sticks after factory reset, backup that /factory folder, in several places. I know this is gonna be intense for you to do, but again: a paperweight, or a working gnex?
[Samsung Galaxy Nexus] chowabbajack:
I'm looking at the site, and it's costing me $30 to unlock my GNEX for the T-Mobile network. What I'm wondering is if that would make any sense, since I can plug an AT&T sim card in the phone and it would work no problem. Maybe I should just consider selling it?
[Samsung Galaxy Nexus] :
I guess that's another solution indeed. However, you would probably be able to sell your phone faster and for more money if it were to be unlocked.