I tried forcing the Tango update on my Lumia 800 and it took me an hour of disconnecting to get the useless 8112. Tried again for another hour for the next update and still nothing.
Is this how updates are supposed to be done ? Or should I just wait 3 months for the phone to realize there's an update ? (legit questions)
Notice it became available a week ago (not on the promised 27th June; also, some people are still waiting) and magically the phone and Zune are both still unaware of it.
This is some really dumb stuff, Microsoft.
June 27 (or whatever date they announced) is when they begin roll out, not when it will be instantly available for your region.
There could be many reasons why they chose the dates they have for rolling out the update.
Some of the few:
1) Limit problems, if they release it to everyone and find out after many testing that it manages to brick phones, everyone will come in and complain. For assurance and risk reduction, its safer to release it in small markets to large markets.
2) Waiting for carriers, some carriers won't allow an update through until they do their own testing that the phone works on their networks (since they will be the one contacted by angry customers if something were to go wrong)
The disconnect trick is for those who want the update asap. If you can't wait a few weeks then by all means continue wasting time to get an update you consider useless. You could have even forced the install through the cab method. And it shouldn't have taken you an hour to do it; an easy misstep would be to forget to put the phone in airplane mode with wifi off.
You may think their process is dumb, but not many people know (including me) in full detail what Microsoft has to go through to get an update out. There could be regulation (FCC), legal ramifications and all sorts of headache that made Microsoft do what they do.
inket said:
I tried forcing the Tango update on my Lumia 800 and it took me an hour of disconnecting to get the useless 8112. Tried again for another hour for the next update and still nothing.
Is this how updates are supposed to be done ? Or should I just wait 3 months for the phone to realize there's an update ? (legit questions)
Notice it became available a week ago (not on the promised 27th June; also, some people are still waiting) and magically the phone and Zune are both still unaware of it.
This is some really dumb stuff, Microsoft.
Click to expand...
Click to collapse
You're complaining because a trick isn't working for you. The trick is not the intended method of updating.
Updates are rolled out in stages. The normal process is to wait for your phone to be updated as and when the companies choose.
@ekw: I had Wi-Fi and Data connection disabled and kept trying with no luck.
I cabbed 8773 today and it finally installed. Weirdly, the phone detected the Nokia update moments after the restart. Why can't OS updates be like that ?
That's what I meant by this thread. Microsoft seems to be either really dumb or just doing it on purpose.
Apple always releases updates on time, and they have no problems with server limits (even though there's 300m active iOS users) or carriers.
Seems to me like an easy problem with a difficult solution. The fact that we all could update using cab sender proves that there's an easy solution, yet, sadly, unofficial.
Blame the carriers. Only Apple has the market clout to force carriers to do things their way.
Related
I have been having this problem pretty much since day 1, I've also searched the Nokia Support Discussions and it seems quite a lot of people are experiencing this. I was actually surprised that my Go-To forum here at XDA doesn't have a thread on it.
My Black Lumia 920 (EE, Phones4U, Unlocked) reboots on average about 5 times a day. Yesterday was probably the worst yet with roughly 8 reboots. That may have been more noticeable to me because I used a SIM which requires a pin though.
What I've noticed:
-The device is roughly 10 days old.
-It has been rebooting an average of 5-8 times a day
-It mostly reboots when idle (so when I'm not using it)
-I've had it reboot only twice while in use when making a call
-I've had it reboot only once when playing music.
-I've only ever noticed it rebooting when it is face up
-Rebooting happens regardless of the SIM (although I have not used it without a SIM at all) (Used both a micro SIM and a SIM cut down to size, used the original carrier SIM and other SIM, no difference to rebooting behaviour)
-I only turn on the radios I need when I need them, so 2G active 100%, 3G/4G, WiFi, Bluetooth, GPS, NFC off for 70% of the time.
-It is not due to battery drain as I usually have about 40% battery at the end of the day.
This has been my experience with the rebooting problem. The figures and estimates I'm giving are not over stating and I've tried giving as much detail so as to try and provide useful information for a solution.
Has anyone else been having this problem?
Has anyone found a working solution?
Has anyone heard or read anything concerning a fix for this?
nope - blue one on AT&T
I'd look at your installed apps, apps enabled to run in the background, etc. It should not be rebooting at all.
I have seen some posts like yours on the internets, but its not a "common" as in most 920s do it problem. Which leads me to think its some issue with an app or apps installed on some phones.
Possible solution
Hi kyrirhcp
I had a similar problem. I reset the phone which bricked it and then used this tutorial to un-brick it:
http://forums.wpcentral.com/nokia-l...after-reset-flash-process-defined-inside.html
The only difference is that I downloaded the "Nokia Data Package Manager" (not sure where from but I'm sure you can find it). This software allows you to download the firmware files directly into the correct folder. You could also look at this tutorial:
http://aydon.wordpress.com/2012/11/29/how-to-flash-your-lumia-920english/
The ROM you want is the EE specific one. It even specifies the colour of the phone. The version number is: 1232.2110.1244.3011
If you reset the device and it does not brick (i.e. freeze up on reformat) then the problem is solved and you don't need to worry. If it bricks (which it probably will) then you need to flash to recover the phone.
God bless
andrew-in-woking
Hi Andrew, thanks for your suggestions but I'm avoiding it like the plague if I'm honest. Resetting my phone and risking a brick, even with your added fix tutorial really doesn't seem worth it. Also I'm assuming that the problem you PM'd me with regarding the loss of some functionality is a result of the fix you suggest. I'm not yet willing or ready to f with my device the same way as I did with my SGNote, even more so since developers haven't yet gotten the experience they have with android. Anyway, i seem to have perhaps solved the problem at least for my device. I changed the regional settings for a completely unrelated matter and I have not since had a single reset or the accompanying massive battery drain. It's now been 3 days. The only other change was that I removed tunein radio an reinstalled it. So it seems that my problem has been solved (fingers crossed, knock on wood, ftou ftou ftou, wearing an evil eye). I hope this helps others with their problems and makes this amazing device useable to those that had this problem.
Sent from my RM-821_eu_euro1_342 using XDA Windows Phone 7 App
Try removing Whatsapp if you've got that installed.
I have had a lot of the same problems. My phone locks up a few times per day. This is the 2nd Lumia 920 I've had. After getting the second with the same problem, I decided to wait for the Portico update that was supposed to address random restarts.
Since then, I've been communicating with Nokia and Windows Phone support on twitter. All they suggest is uninstalling apps, disabling radios, contacting individual developers, and resetting your phone.
I have a hard time wrapping my mind around that. How is it possible for a user level application to take down the whole operating system/firmware?? There are plenty of crappy apps on the Windows Phone Store, I don't think it should be up to me to figure out which is destroying my experience.
I used to root/hack all my old Windows Mobile phones/android phones. When it locked up, it really was up to me to fix it and figure it out!! I chose Windows Phone since it had the locked ecosystem similar to Apple. While that may not appeal to everyone, I have a very busy life and I don't want to spend more time screwing with my phone. It just needs to work! This is my 3rd Windows phone and it's been the worst so far.
Hi,
Does anyone have any info or idea if the AMBER update will be available OTA for L920s with the DEV ROM? I don't see that entry in the update schedule page from Nokia. I just chatted with them and they said they have nothing scheduled at the moment, and suggested instead to go back to my ROGERS ROM (not even in my wildest dreams!).
I know I can flash it, but I don't want to go through the pain of doing everything again, including re-setting all my apps et al. If the OTA update comes out in a couple of weeks or so, I don't mind waiting, but I don't want to wait and then realise in a couple of months that it is not coming out and have to flash it anyhow.
Any news? Do we have to start making some noise on Nokia's forums and social media?
Thanks.
--
ARG
abelitin said:
Hi,
Does anyone have any info or idea if the AMBER update will be available OTA for L920s with the DEV ROM? I don't see that entry in the update schedule page from Nokia. I just chatted with them and they said they have nothing scheduled at the moment, and suggested instead to go back to my ROGERS ROM (not even in my wildest dreams!).
I know I can flash it, but I don't want to go through the pain of doing everything again, including re-setting all my apps et al. If the OTA update comes out in a couple of weeks or so, I don't mind waiting, but I don't want to wait and then realise in a couple of months that it is not coming out and have to flash it anyhow.
Any news? Do we have to start making some noise on Nokia's forums and social media?
Thanks.
--
ARG
Click to expand...
Click to collapse
In case anyone else is wondering, I started getting the update OTA last week. I wasn't expecting it so my connection was very slow and I just soft reset it... Apparently, the download got somehow messed up upon resuming. To make a long story short, after it was installed, the screen lock didn't work properly: I could only unlock my phone right after it turned on; after that, it would not respond at all, so I had to soft-reset every time I wanted to unlock the screen -the other option being deactivating the screen lock altogether, but that doesn't look very promising, especially for battery consumption and pocket dials.
As it turns out, I ended up flashing the firmware, which is ironic because I could have done it a while ago when it came out, but didn't want to go through all the hassle.
My only problem now is that some apps that should work, like Nokia Pro Camera, do not allow me to install them. My firmware does say it is the latest version, and it also identifies the Lumia Amber in Details, but the app is not available.
Has anyone else had this issue?
Thanks
--
ARG
abelitin said:
In case anyone else is wondering, I started getting the update OTA last week. I wasn't expecting it so my connection was very slow and I just soft reset it... Apparently, the download got somehow messed up upon resuming. To make a long story short, after it was installed, the screen lock didn't work properly: I could only unlock my phone right after it turned on; after that, it would not respond at all, so I had to soft-reset every time I wanted to unlock the screen -the other option being deactivating the screen lock altogether, but that doesn't look very promising, especially for battery consumption and pocket dials.
As it turns out, I ended up flashing the firmware, which is ironic because I could have done it a while ago when it came out, but didn't want to go through all the hassle.
My only problem now is that some apps that should work, like Nokia Pro Camera, do not allow me to install them. My firmware does say it is the latest version, and it also identifies the Lumia Amber in Details, but the app is not available.
Has anyone else had this issue?
Thanks
--
ARG
Click to expand...
Click to collapse
Nokia Pro was pulled from Market for few days it was due some bugs...Try again now.
What I can see from Navifirm Plus latest ROM version for RM-821 059R4H6 is 3047.0000.1326.2002
boril said:
Nokia Pro was pulled from Market for few days it was due some bugs...Try again now.
What I can see from Navifirm Plus latest ROM version for RM-821 059R4H6 is 3047.0000.1326.2002
Click to expand...
Click to collapse
Thanks. So I did and now it's there...
--
ARG
Hi, I recently updated my phone to Android 4.4.4 and now I am having this issue: Every time the phone acquires a cell signal, GPS turns on about 10 seconds later and stays on for a long time. This happens even if the GPS and location services are turned off. As a result my battery drains in half the time that it used to. If I stop IQ Agent process, GPS icon immediately goes away until the next time phone reacquires the signal. This happens multiple times a day. I can easily reproduce the problem by toggling airplane mode. I don’t think it’s a conflict with any of the apps because the problem exists if I boot into safe mode. I called HTS but they never heard of it, said they will escalate the problem to the developers, but I don’t know if anything will be done. Does anyone else experiencing the same problem? My phone is not rooted and locked.
Thanks…
madelman99 said:
I called HTS but they never heard of it, said they will escalate the problem to the developers, but I don’t know if anything will be done.
Click to expand...
Click to collapse
That usually means nothing will be done.
I haven't heard of this. I typically recommend backing up your data, and doing a factory reset; as this often (although not always) clears up random bugs after an OTA. Smart of you to eliminate the possibility of 3rd party apps by trying Safe Mode. But there may still be some migrated user settings causing a conflict.
redpoint73 said:
That usually means nothing will be done.
I haven't heard of this. I typically recommend backing up your data, and doing a factory reset; as this often (although not always) clears up random bugs after an OTA.
Click to expand...
Click to collapse
I was hoping to figure this out without doing a factory reset. I know I am not the only one with this issue, I've seen others with the same problem on different forums...
redpoint73 said:
That usually means nothing will be done.
I haven't heard of this. I typically recommend backing up your data, and doing a factory reset; as this often (although not always) clears up random bugs after an OTA. Smart of you to eliminate the possibility of 3rd party apps by trying Safe Mode. But there may still be some migrated user settings causing a conflict.
Click to expand...
Click to collapse
Some (including myself) have noted that this has something to do with carrier IQ services.
GPS
I just got off the phone with ATT just yesterday, and I can confirm they are aware of the issue. But seeing how Lollipop is just around the corner, you might want to wait a bit, unless of course you're in dire straits.
o0RaidR0o said:
I just got off the phone with ATT just yesterday, and I can confirm they are aware of the issue. But seeing how Lollipop is just around the corner, you might want to wait a bit, unless of course you're in dire straits.
Click to expand...
Click to collapse
The HTC tech also said that Lollipop will be out soon, in fact he said they are in stage 2 testing (whatever that means). I just hope that the problem will not migrate to Lollipop.
I'm having a similar issue with my phone. Been sitting on my desk trying to charge, but it can't because the GPS is sucking away the battery.
Others over at AndroidCentral are complaining about the same thing.
Unfortunately I'm new here, so I can't post a link, but you can search for android central 494182-massive-battery-drain-gps-constantly
Also on Android Central: 494174-how-do-i-stop-my-gps-icon-flashing-att-htc-one-m8
Douglas_D said:
I'm having a similar issue with my phone. Been sitting on my desk trying to charge, but it can't because the GPS is sucking away the battery.
Click to expand...
Click to collapse
You can turn off the GPS by stopping IQ Agent Service. It should stay off until the cell data connection is lost.
I think everyone should call them so they know it is happening to a lot of people. Otherwise nothing will get done. I am surprised that there is not that much chatter out there. It was hard to even find forum discussions.
Funny I just posted the same question in the generic M8 Q and A section. I just noticed it too. My battery life has not been affected that I can see after going through the data. I've gone and disabled any app that uses the GPS service but it's still coming on so it's not an app or app update that I can tell. I guess I can wait until LP comes out.
So far so good since I've stopped IQ Agent Service. It hasn't popped back up and I've made 5 or 6 phone calls since then.
I think I solved it…
I think I solved it… I believe the app DriveMode was causing an issue. Here is what I think happened. When I got my phone a year ago, I immediately disabled few apps, DriveMode was one of them. I believe the recent update was designed to more closely interact with DriveMode and even though the app was disabled, it appeared that as soon as the phone acquired data connection, it tried to determine whether or not the user was moving. When I re-enabled the app, I disabled it internally (within the app) and I guess that told the OS not to bother determining if the user was moving anymore. Here are the steps: I re-enabled DriveMode, I then went to google play and updated it to the latest version, I opened the app and immediately noticed GPS icon turned on, the screen appeared telling me to enable GPS, I checked ignore check box and left the location service running in battery save mode. I closed the Drive mode app and left it along without disabling it. I did this yesterday and haven’t noticed GPS turning on even once since then.
I hope this helps everyone solve this annoying problem; please let me know if this works for anyone…
madelman99 said:
I think I solved it… I believe the app DriveMode was causing an issue. Here is what I think happened. When I got my phone a year ago, I immediately disabled few apps, DriveMode was one of them. I believe the recent update was designed to more closely interact with DriveMode and even though the app was disabled, it appeared that as soon as the phone acquired data connection, it tried to determine whether or not the user was moving. When I re-enabled the app, I disabled it internally (within the app) and I guess that told the OS not to bother determining if the user was moving anymore. Here are the steps: I re-enabled DriveMode, I then went to google play and updated it to the latest version, I opened the app and immediately noticed GPS icon turned on, the screen appeared telling me to enable GPS, I checked ignore check box and left the location service running in battery save mode. I closed the Drive mode app and left it along without disabling it. I did this yesterday and haven’t noticed GPS turning on even once since then.
I hope this helps everyone solve this annoying problem; please let me know if this works for anyone…
Click to expand...
Click to collapse
I like this idea -
However, I was able to get rid of this issue by disabling the carrier IQ service. I did this using an application called Disable Service from the Google Play store.
Works like a charm, and has the added advantage of disabling the IQ service intrusion.
DanGeorges said:
However, I was able to get rid of this issue by disabling the carrier IQ service. I did this using an application called Disable Service from the Google Play store.
Works like a charm, and has the added advantage of disabling the IQ service intrusion.
Click to expand...
Click to collapse
Unfortunately this only will work on rooted phones, mine is not.
madelman99 said:
Unfortunately this only will work on rooted phones, mine is not.
Click to expand...
Click to collapse
Just want to throw my $0.02 in here....I'm having hte same issues noted in the thread, and it's murdering my battery life. I typically get 24-30 hours of battery life easily on this phone, but now if i dont spend all day killing IQ Agent, i get about 7. I can't root my M8 due to some work restrictions, so it's all manual IQ Agent task killing fo rme. although I was EXTREMELY active yesterday in killing the service ~30 times throughout the day yesterday, Android System (where IQ Agent lies) still managed to run 2hr 24 minutes of GPS on, according to two different battery/service monitoring apps. This, mind you, all occurred without my actual GPS toggle ever being switched on.
I'm waiting for a call back from HTC, and AT&T punted completely and denied any knowledge of why it would happen (although ironically offering to remote into my phone to "diagnose" the issue, which I could not do becuase I was in transit when I called and they required I remain stationary...)
I'm 100% convinced it's entirely due to the IQ Agent task, or another involuntary watchdog service trigging IQ agent. This task is started under at least two distinct condition, with no fail:
my phone goes between 4G and LTE (Subway, between towers/coverage zones, all flipping day long in my concrete-and-steel office building...)
I make or receive a phone call (can feel teh phone get hot in ~2 minutes while on the phone).
switching in or out of airplane mode (which is really an extension of #1).
I love my M8 like crazy, but I cannot wait until my next phone because I absolutely refuse to purchase anything associated with a cell carrier ever again. Fvck that.
Agreed...DriveMode part of the problem
madelman99 said:
I think I solved it… I believe the app DriveMode was causing an issue. Here is what I think happened. When I got my phone a year ago, I immediately disabled few apps, DriveMode was one of them. I believe the recent update was designed to more closely interact with DriveMode and even though the app was disabled, it appeared that as soon as the phone acquired data connection, it tried to determine whether or not the user was moving. When I re-enabled the app, I disabled it internally (within the app) and I guess that told the OS not to bother determining if the user was moving anymore. Here are the steps: I re-enabled DriveMode, I then went to google play and updated it to the latest version, I opened the app and immediately noticed GPS icon turned on, the screen appeared telling me to enable GPS, I checked ignore check box and left the location service running in battery save mode. I closed the Drive mode app and left it along without disabling it. I did this yesterday and haven’t noticed GPS turning on even once since then.
I hope this helps everyone solve this annoying problem; please let me know if this works for anyone…
Click to expand...
Click to collapse
Agreed. I mostly followed these steps by downloading the latest DriveMode, walking through DriveMode setup, then disabling DriveMode and then stopping the IQ Agent Service. SInce then, GPS has performed as it should, only on demand. I did notice that when switching from mobile to a wi-fi network that requires a sign in that the GPS fires up. But again, killing the service stops the random GPS after logging into the wi-fi. So overall, much better than the constant on/off, but still ATT needs to resolve this at some point.
Have a carrieriq blocked/inactive build in testing so we shall see if it is indeed the culprit by end of day.
I've been testing this build for a couple of days now, and so far the GPS has stayed off like a good little app should. It only turns on when I expect.
Update/Reply From AT&T as of 03/23
Finally!!! An admission from AT&T that they jacked up our phones with their software update back in January. It's only taken a month and a half, 4 calls to text support, 3 attempts to reach their urgent care department (by the way... they are completely incompetent. They call from an unknown number, I normally don't answer but I also couldn't answer anyway due to being at work. They leave a message requesting you call a number in KY and leave a message. Left a message on two different occasions and provided the days and hours they could reach me. Of course they call whenever they want and the process starts all over) in addition to all this, I filed a complaint with the Better Business Bureau that resulted in a call back from a corporate executive. Now the only problem is they don't have a solution for the issue yet and probably won't do anything with the Lollipop update that "SHOULD" be released within the next 15 days. No one should have to go through this but I honestly think everyone should file a BBB complaint just to show AT&T a lesson.
Rebel3085 said:
Finally!!! An admission from AT&T that they jacked up our phones with their software update back in January. It's only taken a month and a half, 4 calls to text support, 3 attempts to reach their urgent care department (by the way... they are completely incompetent. They call from an unknown number, I normally don't answer but I also couldn't answer anyway due to being at work. They leave a message requesting you call a number in KY and leave a message. Left a message on two different occasions and provided the days and hours they could reach me. Of course they call whenever they want and the process starts all over) in addition to all this, I filed a complaint with the Better Business Bureau that resulted in a call back from a corporate executive. Now the only problem is they don't have a solution for the issue yet and probably won't do anything with the Lollipop update that "SHOULD" be released within the next 15 days. No one should have to go through this but I honestly think everyone should file a BBB complaint just to show AT&T a lesson.
Click to expand...
Click to collapse
So - was it Carrier IQ? Did they say what was going on?
I know they said they don't have a solution, but it would be useful to know what is causing this. I found that disabling the carrier iq service does the trick, and WNC's ROM, which has it disabled by default, also does the trick.
Thanks for the update. My phone started doing the GPS thing a couple of weeks ago and my battery life has been shot.
The weirdest thing is that my issues only started 2 weeks ago, instead of when the update occurred in January, so ATT must be doing something weird on their network as well
Hi all,
Every time my phone automatically downloads an OEM update, it's telling me to update my phone, and I can defer the updates after 4 times. After that, I can't defer the updates. It just updates automatically, and each time, my phone is getting slower and slower and slower which I don't want at all.
Also, auto-update system is off on developer options. So I am at a loss now.
Not sure if there is really anything you can do about it. My phone doesn't seem any slower.
Are you absolutely sure it's the update that is slowing down the phone?
yep
kenbo111 said:
Are you absolutely sure it's the update that is slowing down the phone?
Click to expand...
Click to collapse
Sorry for the late reply. I'll admit I do have a good chunk of apps in my phone, but it's an experience thing that I have with samsung phones.
When I had the S9 (from verizon, not sure on model), I still kept Android Oreo because I took use of a software bug that let's you keep your android version without updating your phone, and one of my relatives, same phone model, was updating their phone to the latest version because they have to after a certain number of defers. Note that I do have a good chunk of apps on my old phone, but my phone was a lot faster and responsive than my relatives phone, being that their phone only had a few apps and mine having more apps than theirs.
If I have to update the phone, then I will update the phone. I don't want an automatic update, and then all of a sudden, different problems occur that has never happened on the last build.
As I'm rooted, I have to manually check for updates via xperifirm. There was an upsated released: version 64.1.A.0.913.
Anybody updated and tested? Apparently camera apps have been updated! Any new features?
I wont get time to update yet, just thought I'd ask.
Thanks
Unless I'm mistaken, this update allows you to switch from android 12 to android 13
Huh we have android 13 for months now ...so i would say no .
Its for sure a security patch.
Chinese 72 got it 2 weeks ago , european 54 got it a week ago and US has to wait for another two weeks , i wish it would be all at the same time .
Hello,
The only feature I expericence since the upgraded is the "phone too hot warning" issue. I use the phone since late november without any trouble.
For the latest week, the phone displayed the orange warning sign and closed the camera app maybe 10 times. It couldn't even go through a 10 minutes google meet call...
It may not be related to the latest release, and I may be the only one having this issue...
viper. said:
Huh we have android 13 for months now ...so i would say no .
Its for sure a security patch.
Chinese 72 got it 2 weeks ago , european 54 got it a week ago and US has to wait for another two weeks , i wish it would be all at the same time .
Click to expand...
Click to collapse
Yeah, you're right about security patch. Thought perhaps something has trickled down from the new phone releases, like improved camera apps as they have changed their version numbers. Thanks
arthurham said:
Hello,
The only feature I expericence since the upgraded is the "phone too hot warning" issue. I use the phone since late november without any trouble.
For the latest week, the phone displayed the orange warning sign and closed the camera app maybe 10 times. It couldn't even go through a 10 minutes google meet call...
It may not be related to the latest release, and I may be the only one having this issue...
Click to expand...
Click to collapse
Ouch, sorry to hear that. I will update in a few days and see if I have the same issue. Though tbh, I havent had as many issues as some have, perhaps because of root and cleaning up some bloat and adding in adblockers etc.
You should do a full all apps cache wipe and see if that helps.
arthurham said:
Hello,
The only feature I expericence since the upgraded is the "phone too hot warning" issue. I use the phone since late november without any trouble.
For the latest week, the phone displayed the orange warning sign and closed the camera app maybe 10 times. It couldn't even go through a 10 minutes google meet call...
It may not be related to the latest release, and I may be the only one having this issue...
Click to expand...
Click to collapse
I had overheating problems with meet and 5g i was outside but on older different firmware.
You also have to understand now its summer time (probably in your country too) so you cant really compare november temperatures with current ones unless you did that in room with AC on.
I'm on the latest US version so still waiting for our update for this cycle. But since my last update, the phone has been very warm to the touch during normal use and I've seen the heat warning many times while using camera. I have never seen it before. Battery life is crap now too and used to be fantastic. Maybe you guys lucked out last month and the US version got whatever it was to cause the heating issues first? My last update was around 300mb so it was bigger that usual I think.
.913 QR reader from statusbar dont work. only black screen.
hasztagL said:
.913 QR reader from statusbar dont work. only black screen.
Click to expand...
Click to collapse
I had that sometimes on .891 ,couldnt get it to work no matter what but it goes away eventually with restarts .
Edit: i just got the .913 and qr reader works fine. Been using my phone before that for 2 hrs and no overheating ,after installing 913 and checking camera apps for 1 minute my top part of the screen got extremly hot but didnt show any overheating warnings.nothing changed so far in camera related apps (no portrait mode)