Hi guys, I have a very irritating issue with my international Galaxy S6 Edge (SM-G925F) and hopefully someone could help me fixing it. I know that this is the forum for the flat Galaxy S6, but since the main hardware components are the same I guess that both devices could suffer from the same problems.
I'm experiencing frequent lockups mostly when trying to wake up/unlock the phone. The device becomes totally unresponsive to screen or home, back, window button taps and eventually after lots of tries it comes back to life and behaves as normal. The problem becomes way less frequent (almost disappears) if I connect it to a charger.
What I tried up to now with no luck fixing the problem is:
Disabled all the TouchWiz smart features, location services, wifi and radio broadcasts, rotation, nfc, sound, bluetooth, fingerprint scanner,
Checked all the sensors from the *#0*# menu and they seem fine,
Flashed through Odin, Smart Switch, TWRP official and custom roms (5.1.1, 6.0.1),
Tried rooted and non-rooted roms,
Tried odin's NAND erase all option and repartioned the phone using the ZEROLTE_EUR_OPEN.pit file,
Wiped the persistent partitions (sda11, 13) using the ADB commands dd if=/dev/zero of=/dev/block/sda11, dd if=/dev/zero of=/dev/block/sda13, which however gave me:
dd: /dev/block/sda11 (sda13): No space left on device,
so I don't know if it was successful or not,
Updated (PASS) the TSP FW version from the *#2663# menu,
Opened the phone and powered it up after disconnecting all components apart from screen and battery,
Tried different battery.
Does anyone have a similar problem and knows how to fix it? Unfortunately, my device is out of warranty so I wouldn't like to visit a Samsung service centre.
I haven't tried alternative PIT files with hidden partitions of various sizes yet. Do you think that it will make any difference or, furthermore, is there a chance of further damaging my phone?
Could someone please with a similar device dial the *#2663# code and give me the following information? Phone's and part's TSP FW version, TSP threshold.
Is there a Phone's and Part's Touch key FW version available? In my phone I cannot see the Phone's, Part's Touch key FW version paragraph at all and I'm curious if this is related to the problem.
Looking forward for your tips! Thanks!
I had this too, but *seem* to have it solved.
Maybe I did some unnecessary step, but it now flawlessly works for half a day, compared to reboot/freeze every few minutes.
- calibrate battery (use an app from play store, or L Speed (has an option for that, too))
- backup stuff to pc
- re-install stock firmware using Kies (works with knox trip, too)
- don't activate wifi, accounts in first start wizard
- do factory reset
- restart
- again no wifi, accounts in first start wizard
- factory reset again
- restart
- again no wifi, accounts in first start wizard
- go to stock recovery (adb reboot recovery or phone off, then power+home+vol up)
- clean cache
- factory reset
- clean cache again
- reboot
- setup normally (ie with wifi et all)
- profit (?)
- optional: install twrp through ODIN
- optional: flash custom rom (let the aroma installer do the wipe)/or supersu if you plan to stay on stock [I'm on PureStock Extra Lite by ambassadii, mist stable ROM from my personal experience]
- additionally you want to disable account sync or play/galaxy auto updates (known to increase issues, but likely not required once phone works again normally)
I know that excessive factory resetting sounds stupid...
But a single factory reset or single cache clean did NOT fix it for me. Also FXR and other options did not do the trick for me.
You might aswell try with just one factory reset, but mine worked normally again upon third + manual in stock recovery... (might aswell just be bad luck).
I hope my device is over with it.
I hope this may help you to solve your problem aswell.
Gesendet von meinem SM-G920F mit Tapatalk
Thanks for your help mate, but unfortunately it didn't fix the problem. Perhaps it seems a bit better, but not fixed for sure. Could you please dial in *#2663# and give me the info that I mentioned in the first post?
Screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It happened for me again, too, once late at night. But during day it seemes fine.
Might be a deep sleep issue?
Gesendet von meinem SM-G920F mit Tapatalk
It seems an external problem, not a software problem...i had similar issues with Arter kernel (galaxy s3 l9300), then i changed to boeffla and now it works without any minimal lag.
I suggest changing your kernel instead of the rom...
Always do a backup before doing anything!
After finishing all the updates my phone returned back to the unusable condition. It seems that it is related to deep sleep issues, but not sure if it's a software or hardware problem though. As long as I keep my phone "warm", ie browsing, playing or any other sort of activity it runs smoothly. The problem appears when I try to wake it up from deep sleep.
Now, regarding the *#2663# menu, I thought you had the edge variant and wanted to see if you had the "Touch key FW" version menu. As I said, in my phone the "Touch key FW" version menu is not appearing at all, but maybe it has to do with the fact that it is the Edge version and not the flat one. A colleague's "healty" flat S6 reports the same info like yours, so everything seems fine there. In any case try the update thing and see if it helps you solving the issue. In my case it didn't, but you can still try!
Regarding, the kernels I tried plenty of them - stock, custom, 5.1.1, 6.0.1, (un)rooted - and the problem was always there.
I'll check how arter97 kernel with system less root behaves.
Gesendet von meinem SM-G920F mit Tapatalk
Wait... You said this problem almost disappears if you put your phone to charge...
Try changing the voltage settings of your CPU at first higher and then lower...
Try also to turn off some cores and overclock the others...
I'm saying this because it seems the only way to see if the problem is the hardware or the software.
(Always backup first!)
I have to admit that this is something I haven't tried yet. At the moment I have turned my wifi off, removed the sim card and rebooted the phone. 4 hours running on battery with not a single problem. I'll check is behaviour for the rest of the day and then I'll try to fiddle with the cpu settings!
Unfortunately, I didn't manage to get rid of the problem. I tried to overvolt cpus, gpus, busses and it didn't make any difference. I repartitioned the phone with a different PIT file and it didn't help either. If you have anything else to suggest please do so.
I tried that, too and also updated to Pure Stock ROM v5.4 with hacker kernel.
No more issues for me since ~24 hours, compared to twice before. I hope it'll stay like that.
Gesendet von meinem SM-G920F mit Tapatalk
Just a small update for ppl that are having similar issues. The only thing that seems to bring my phone back to normal state is heat: if I heat my phone from both sides with a hairdryer for 10-20 seconds it comes back to life with no problem at all. Nothing else seemed to help.
Apart from that, @Setialpha recently published a ROM that hopefully solves the random lockups, reboots etc. I'll try it and report back.
Give it a go and if it works thank the dev!
Wait...you heat it up and it works?
Could it be the multicore powersave?
(Saves energy shutting off cores)
Sent from my GT-I9300 using XDA-Developers mobile app
Problem found
Hello guys i found a temporary fix for this problem i think its a software bug, a cpu gouvernor related bug.
What i did ??
I flashed a custom rom based on mashmallow then i flashed hacker kernel i tried changing different kernel settings but it didnt fix the problem...what it actually worked was changing the cpu governor from the stock interactive to ondemandplus and the problem never came back ! Please try that and get back to me
PSndemandplus governor drains battery more than stock interactive because it keeps the cpu cores awake.
Related
Hi all,
After updating my One S I have this issue. When turning on the phone in the morning, the phone will stay in airplane mode. It also doesn't ask for my PIN. After a restart the phone does ask for a PIN and my security pattern.
Anyone else experiencing this?
Some other Dutch users from Androidworld report the same issue.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Best regards,
Verstuurd van mijn HTC One S met Tapatalk
I had some problems with this using the viperOneS rom, and in the previous stock version it was working good for me too
RichJo86 said:
Hi all,
After updating my One S I have this issue. When turning on the phone in the morning, the phone will stay in airplane mode. It also doesn't ask for my PIN. After a restart the phone does ask for a PIN and my security pattern.
Anyone else experiencing this?
Some other Dutch users from Androidworld report the same issue.
Best regards,
Verstuurd van mijn HTC One S met Tapatalk
Click to expand...
Click to collapse
Same here... i use lama to togggle off/on airplane mode during the night. Since the update the phone can't connect to the network when lama wants to disable airplane mode.
PS: I have PIN disabled, but it doesn't work either, even manually, until i restart the phone...
Hope this gets fixed soon...
PS: I'm on the german htc stock rom, never rooted or unlocked...
RichJo86 said:
After updating my One S I have this issue.
Click to expand...
Click to collapse
If you're on an old hboot (1.09 or older) you can try a few different radios and see if the problem goes away. (If you used an RUU or OTA to update your device, you're now on hboot 1.14. Sorry.)
Alternatively, you can try going into the Phone Information menu (*#*#4636#*#* in dialer) and turn the radio off and back on.
I just tested, and I do not have the same issue. I can go in and out of flight mode no problem. Which status icon do you get when you come out of flight mode? The plane or the zero bars with an X?
touch of jobo said:
If you're on an old hboot (1.09 or older) you can try a few different radios and see if the problem goes away. (If you used an RUU or OTA to update your device, you're now on hboot 1.14. Sorry.)
Alternatively, you can try going into the Phone Information menu (*#*#4636#*#* in dialer) and turn the radio off and back on.
I just tested, and I do not have the same issue. I can go in and out of flight mode no problem. Which status icon do you get when you come out of flight mode? The plane or the zero bars with an X?
Click to expand...
Click to collapse
Turning airplane mode off and on again within a few minutes also works for me just fine... But after about 5 hours at night (1 to 6 am) i can't disable airplane mode.
When trying to turn it on manually the button icon (airplane) stays animated but the network icon stays on disconnected.
Seems you have to turn on airplane mode a certain time...
touch of jobo said:
If you're on an old hboot (1.09 or older) you can try a few different radios and see if the problem goes away. (If you used an RUU or OTA to update your device, you're now on hboot 1.14. Sorry.)
Alternatively, you can try going into the Phone Information menu (*#*#4636#*#* in dialer) and turn the radio off and back on.
I just tested, and I do not have the same issue. I can go in and out of flight mode no problem. Which status icon do you get when you come out of flight mode? The plane or the zero bars with an X?
Click to expand...
Click to collapse
My phone is stock, never unlocked or flashed it. This issue was not present on stock 4.0.x which came with the phones release. After updating via OTA (WiFi) to 4.0.4 this flight mode problem comes up. What you see is that the phone is trying to disable flight mode to enable the radio, it's stuck and won't go further. Restarting is the only thing that works.
At Androidworld I got the tip to turn off fast booting, if this is turned off the phone will boot normally when coming from a cold boot that is.
Verstuurd van mijn HTC One S met Tapatalk
Hello, just to mention that I got this problem too.
RichJo86 said:
My phone is stock, never unlocked or flashed it. This issue was not present on stock 4.0.x which came with the phones release. After updating via OTA (WiFi) to 4.0.4 this flight mode problem comes up. What you see is that the phone is trying to disable flight mode to enable the radio, it's stuck and won't go further. Restarting is the only thing that works.
At Androidworld I got the tip to turn off fast booting, if this is turned off the phone will boot normally when coming from a cold boot that is.
Verstuurd van mijn HTC One S met Tapatalk
Click to expand...
Click to collapse
Same here...
Never happened 'till the last update. Upon boot the phone is stuck trying to disable airplane mode and won't go further. Happened to me just once, since I immediately disabled fastboot and the problem never reappeared.
Fastboot appears to be very buggy now after the update: when I had it enabled I used to receive error messages upon reboot saying that the phone hadn't been properly shut down...
I ask you guys: by keeping fastboot disabled can you toggle airplane mode on/off without problems?
nor-ric said:
Same here...
Never happened 'till the last update. Upon boot the phone is stuck trying to disable airplane mode and won't go further. Happened to me just once, since I immediately disabled fastboot and the problem never reappeared.
Fastboot appears to be very buggy now after the update: when I had it enabled I used to receive error messages upon reboot saying that the phone hadn't been properly shut down...
I ask you guys: by keeping fastboot disabled can you toggle airplane mode on/off without problems?
Click to expand...
Click to collapse
I can confirm u that i have still the problem wih fastboot disabled.
Have also the problem with 2.31 Stock Rom, no root.
I trigger the Airplanemode with JuiceDefender at night to on and at the morning to off. Sometimes it's failed to get the Airplanemode completely off. Must reboot and then it works. I doesn't use pin or pattern!
Possible Solution???
I didn't want to do a hard reset so i first tried to wipe the android cache partition... (no data lost, as it seems...)
For the last two days llama worked how it should. (disable airplane mode in the morning, triggered by time)
Perhaps this also works for someone else...
Here is explained how to wipe your cache partition (without losing data):
http://support.t-mobile.com/docs/DOC-2265
Tom
same problem here
Just to say I have the same problem after the update (htc stock rom). Turning on in the morning airplane mode is stuck on "turning off": the wi-fi connection is working while the phone connection is not. Also a quick turn on/turn off of the airplane mode does not show the same problem. A soft reset did help the first days then the problem reappeared.
Exactly the same problem
I've been suffering from the "stuck in airplane mode" error for a couple of weeks now. I tried multiple cache and factory resets, nothing seems to work.
For me it works if you choose standby mode by longpressing the power button. In order to disable standby, I sometimes have to do it twice though.
But at least it doesn't hang.
One more here having the same issue, maybe will be fixed with the JB update.
Well I'm running BAKED, but when I updated to 2.35 You just had to long press the power button and toggle airplane mode. That worked for me back in the days.
Qs5 said:
Well I'm running BAKED, but when I updated to 2.35 You just had to long press the power button and toggle airplane mode. That worked for me back in the days.
Click to expand...
Click to collapse
Not in my case
Sent from my HTC One S using Tapatalk 2
The only thing that works for me when it happens is to reboot the phone. Turning it off and then turning it on again does not work, however.
Hi Guys!
I'm developer of the app "good night, android!" and one of my users reported a problem with his One S getting stuck in airplane mode.
He is on 4.1.1 stock rom, i wanted to ask if this issue still persists?
Thanks for you answers!
superkoal said:
Hi Guys!
I'm developer of the app "good night, android!" and one of my users reported a problem with his One S getting stuck in airplane mode.
He is on 4.1.1 stock rom, i wanted to ask if this issue still persists?
Thanks for you answers!
Click to expand...
Click to collapse
Anyone? No one using stock rom any more?
Hey guys, I have an HD that I updated with SamuraiHL's RSDlite Keep Data script process, rooted, and unlocked currently on the CM11 nightlies. The issue I'm having is that a lot of times I send or receive a call the other end is unable to hear me. Sometimes turning on the speakerphone or plugging in the audio jack will suddenly allow me to be heard but if I go back to normal then they hear nothing again. Also this isn't always the case, sometimes they hear me fine without me doing anything but when I go to speakerphone or plug in headphones they aren't able to hear me.
Other times it works as it should. So far I've gotten this on every rom I've tried so far, namely Gummy rom the past week or so and I noticed it today on the CM11 nightly I'm on.
So does anyone have an idea on what could be causing this? I've not seen mention of this being a common issue for the new 3.4 bootloader, like the BT or popping sound issues for example.
Side note
Now I do use Xposed but I'm not sure if that is affecting it or not. I've not tested it with Xposed off for prolong periods of time but just turning off and making a few calls didn't repeat the issue so I reinstalled it which I was able to make some normal calls right after.
I have noticed that there are some issues between CM11 and Xposed that aren't there for Gummy, like CM's softkeys aren't themeable or able to have long press action set by Gravity Box and the Nav ring's 4th and 5th targets make the systemUI crash. I can't go without Xposed ( ) just for GB's app launcher (back button double press) and Xblast's Appbar which I find a lot better to use than some of the other apps of a similar nature.
here is a screenshot of my About Phone info if that helps
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
using the GB custom key as I can't set recent button long press to open last app.
Jaysp656 said:
Hey guys, I have an HD that I updated with SamuraiHL's RSDlite Keep Data script process, rooted, and unlocked currently on the CM11 nightlies. The issue I'm having is that a lot of times I send or receive a call the other end is unable to hear me. Sometimes turning on the speakerphone or plugging in the audio jack will suddenly allow me to be heard but if I go back to normal then they hear nothing again. Also this isn't always the case, sometimes they hear me fine without me doing anything but when I go to speakerphone or plug in headphones they aren't able to hear me.
Other times it works as it should. So far I've gotten this on every rom I've tried so far, namely Gummy rom the past week or so and I noticed it today on the CM11 nightly I'm on.
So does anyone have an idea on what could be causing this? I've not seen mention of this being a common issue for the new 3.4 bootloader, like the BT or popping sound issues for example.
Side note
Now I do use Xposed but I'm not sure if that is affecting it or not. I've not tested it with Xposed off for prolong periods of time but just turning off and making a few calls didn't repeat the issue so I reinstalled it which I was able to make some normal calls right after.
I have noticed that there are some issues between CM11 and Xposed that aren't there for Gummy, like CM's softkeys aren't themeable or able to have long press action set by Gravity Box and the Nav ring's 4th and 5th targets make the systemUI crash. I can't go without Xposed ( ) just for GB's app launcher (back button double press) and Xblast's Appbar which I find a lot better to use than some of the other apps of a similar nature.
here is a screenshot of my About Phone info if that helps
using the GB custom key as I can't set recent button long press to open last app.
Click to expand...
Click to collapse
As of 7/17 the nightlies have BT fixed. as far as the mic issue that happened to me once after a dirty nightly flash. i didnt even reflash i wiped davlic and let apps restart and all was fixed. I dont use exposed so im not sure of the effect.
Jaysp656 said:
Hey guys, I have an HD that I updated with SamuraiHL's RSDlite Keep Data script process, rooted, and unlocked currently on the CM11 nightlies. The issue I'm having is that a lot of times I send or receive a call the other end is unable to hear me. Sometimes turning on the speakerphone or plugging in the audio jack will suddenly allow me to be heard but if I go back to normal then they hear nothing again. Also this isn't always the case, sometimes they hear me fine without me doing anything but when I go to speakerphone or plug in headphones they aren't able to hear me.
Other times it works as it should. So far I've gotten this on every rom I've tried so far, namely Gummy rom the past week or so and I noticed it today on the CM11 nightly I'm on.
So does anyone have an idea on what could be causing this? I've not seen mention of this being a common issue for the new 3.4 bootloader, like the BT or popping sound issues for example.
Side note
Now I do use Xposed but I'm not sure if that is affecting it or not. I've not tested it with Xposed off for prolong periods of time but just turning off and making a few calls didn't repeat the issue so I reinstalled it which I was able to make some normal calls right after.
I have noticed that there are some issues between CM11 and Xposed that aren't there for Gummy, like CM's softkeys aren't themeable or able to have long press action set by Gravity Box and the Nav ring's 4th and 5th targets make the systemUI crash. I can't go without Xposed ( ) just for GB's app launcher (back button double press) and Xblast's Appbar which I find a lot better to use than some of the other apps of a similar nature.
here is a screenshot of my About Phone info if that helps
using the GB custom key as I can't set recent button long press to open last app.
Click to expand...
Click to collapse
This happened to me as well tonight. I'm on the CM-11 7/22 nightly. I was talking to my wife just fine, and then switched to the speakerphone. The mic was working in both modes initially, but when I switched speakerphone off, she couldn't hear me. However, when I switched it back on, she was able to hear me again. I hung up, and called her back, and mic was working fine again with speakerphone off. Hopefully the issue is resolved in the next build or 2!
Now we have this issue on all ROMs with KK BL... ((
It happens if you connect headphones to device or switch to speaker during call...
St.Noigel said:
Now we have this issue on all ROMs with KK BL... ((
It happens if you connect headphones to device or switch to speaker during call...
Click to expand...
Click to collapse
Any idea what the source of the problem is? I wonder if it's hardware related or bootloader related since it's happening to all ROMs. That's a pretty huge bug lol.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
So my Nexus 5 starting to have some crazy redraws on the launcher and really began to stutter and lag. i wasn't sure what it was so i did some searched online and found out that there was a memory leak bug in the developer preview of L. It appears at least in my experience the bug is still there.
What happens is if you go to your settings/apps and look at what's "running" you'll find that "system" hogs up a MASSIVE amount of ram after 1-2 days of usage. If you do a reboot you'll find it starts off ~200mb which seems reasonable. the screenshot i've attached is after about 14 hours of usage after a reboot and i'm at roughly 540mb of usage. I'm sure by tonight i'll be at roughly 800mb and the redraws are going to start as the OS starts to close apps etc. Which is when a reboot will be needed.
Curious to see what your system ram usage's are after a few days use and if you're experiencing similar lag/stuttering/redraws as well.
Star here if you experience this as well:
https://code.google.com/p/android/issues/detail?id=79729
UPDATE 11/28/2014 - 73 hours uptime
Ram usage now around 900-1gb for system. Redraws are occurring on launcher here and there now. Issue still present or working as intended I have no idea at this point.
UPDATE 11/26/2014 - 27 hours uptime
Ram usage hovering around 600mb for system. Still no redraws. Looks as if the services update changed the priorities so that launcher doesn't redraw at least. Haven't noticed any slowdowns either.
UPDATE 11/25/2014 - 14 hours uptime
Ram usage now at 700mb for system. No redraws yet.
UPDATE 11/25/2014 - 6 hours uptime
I updated today to google play services 6.5 and I know it's still early, but as of 6 hours uptime, my system is still hovering only around 180mb-250mb ram usage. Much more normal! yay. fingers crossed to see after a few days.
UPDATE
Coming up on close to two days uptime, 33 hours and system ram usage is now close to 800mb.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I haven't noticed this, mine is using 359M of RAM I have been running for 36 hrs now. Did you factory reset after updating to Lollipop?
I didn't want to factory reset since that would defeat the purpose of the OTA....what I did do was clear cache.
Sometimes OTA's makes a factory reset necessary unfortunately. It can cause issues. Specially such a big update as this.
Perhaps I will do a factory reset and see what happens, but in the meantime still curious to see if anyone else is having this issue as well.
rogerchew said:
Perhaps I will do a factory reset and see what happens, but in the meantime still curious to see if anyone else is having this issue as well.
Click to expand...
Click to collapse
Oh hell yes.
http://forum.xda-developers.com/showthread.php?t=2947525
http://www.reddit.com/r/Android/comments/2me1m8/serious_memory_leak_in_android_lollipop/
http://www.reddit.com/r/Android/comments/2jwi5x/memory_leak_on_lollipop_if_background_apps_are/
yup, those were the exact sources I was reading that there were issues. I was surprised there wasn't a separate thread about it more recently since the official deployment of L so wondered if it was only isolated cases.
I've read very few that has had the issue. Definitely not a widespead issue as we would had been flooded with threads by now then. So I would try a reset and that will most likely fix it.
I believe my device has memory leak issue too. I did a fresh flash from factory image and launcher will start to redraw everytime i press home after about 1 day usage.
I mainly only use it to play boom beach and hay day and surf webs.
ubcjack said:
I believe my device has memory leak issue too. I did a fresh flash from factory image and launcher will start to redraw everytime i press home after about 1 day usage.
Click to expand...
Click to collapse
Check your system ram usage when it starts to redraw and report back.
I can't believe this only effects a few people. This has to be a bug everyone is experiencing sooner or later. Maybe many people don't even notice. But for me it's the most annoying thing about lollipop. I hope a fix is coming soon.
Sent from my Nexus 5 using XDA Free mobile app
This honestly may be a strange solution to this problem buuuut.... Out of curiosity when I noticed on android police's website that there was a new play services update. Keep in mind im on official lollipop with all the terrible lag and battery issues too, but once I updated to the latest services apk and rebooted everything was buttery smooth again just like (or even better the kk) seems like the nexus really is a "google" phone now. Hope it helps!!
sidekickingjorge said:
This honestly may be a strange solution to this problem buuuut.... Out of curiosity when I noticed on android police's website that there was a new play services update. Keep in mind im on official lollipop with all the terrible lag and battery issues too, but once I updated to the latest services apk and rebooted everything was buttery smooth again just like (or even better the kk) seems like the nexus really is a "google" phone now. Hope it helps!!
Click to expand...
Click to collapse
I'm also really looking forward to the new services update! unfortunately, you did reboot your phone. Not sure if it's the update that fixed it or the reboot cause rebooting does temporarily fix it for now.
I understand where your coming from. I did reboot and actually reflashed the images several times and still had the issues everyone else seems to have. Updated the apk and wallah! Weird I know but worked for me ha
I did a manual flash from google factory images. I even have the latest google play services. A reboot does fix the problem temporarily. It seems like whenever I drive in my car (nav, waze music ect) I lose memory like crazy and many things in the apps menu including the launcher says restarting and everything is laggy as crap until I restart my phone again. I'll grab screen shots next time to show.
sidekickingjorge said:
I understand where your coming from. I did reboot and actually reflashed the images several times and still had the issues everyone else seems to have. Updated the apk and wallah! Weird I know but worked for me ha
Click to expand...
Click to collapse
Dang just looked for the apk and my version isn't available yet.
Memory Leak
HOLY COW..!! This is true after one day of usage ,if i check for available ram is shows only 500mb...YES System eats about 1GB RAM....I hav upgraded my cell with OTA..But no luck....When i was on KITKAT i always used to get 1.2GB FREE RAM..Lollipop sucks about this RAM issue...lets hope google will fix this issue soon!!
I have this ****ing and anooying issue and don't know how to solve. I have sometimes popups of clean master app saying "your memory is 85% full". After a reboot it works well for a few hours
I have it to.. Google is joking.
Waiting for Android 5.1
sidekickingjorge said:
This honestly may be a strange solution to this problem buuuut.... Out of curiosity when I noticed on android police's website that there was a new play services update. Keep in mind im on official lollipop with all the terrible lag and battery issues too, but once I updated to the latest services apk and rebooted everything was buttery smooth again just like (or even better the kk) seems like the nexus really is a "google" phone now. Hope it helps!!
Click to expand...
Click to collapse
What version of play services have you installed? For Nexus t with Lollipop we need version 738 but it is not available yet
Hi,
I have a Moto G XT1032 (2013, 1st gen) with Lollipop 5.0.2
Stock Firmware: 220.27.1.falcon_umts.Retail.en.GB
On Sunday the phone began suddenly rebooting itself (it did so almost constantly at times). Sometimes I was able to get past the boot animation (which itself "lagged" on some of the boots/reboots) and be able to navigate menus or apps for 30 seconds and then another reboot would occur.
I decided to do factory reset (from the phones menu, one time I was able to navigate there without the device rebooting). Once I set up the phone, a few moments later (before the apps I had previously would download from my accounts synch) it began rebooting again... I gave up hope until the next day.
I followed to clear cache and Wipe data through the phone's stock recovery. Once I set it up, it began working fairly better. But the "hangs" and "lags" during normal operation were still occurring. The phone now rebooted rarely, but it still happened.
Yesterday and today the phone seems to be working better, and suffered no reboots, but for some reason I wake up and my phone is turned off... When turning it on again the battery was half-full.
I would like to know if this could be a hardware or software issue. In case of the former, I will have a bad time (money wise). In case of the latter, what should I do? Reflash stock firmware? Or what other thing would you recommend?
Thanks in advance.
My brother has the 8GB version, enGB-retail from Amazon.co.uk and for the last two days, the phone is unusable! It restarts all the time until the battery dies and when you put it on the charger, the phone resumes the boot loop (( I've managed to boot it and do a factory reset, then it was fine for like an hour, then it started lagging hard and after that the boot loop came again. And the phone is turned off right now, because it won't boot and it won't charge. Could this be due to a hardware failure? 'Cause if there's a chance I have to ship it back to Amazon... The phone is pure stock, 5.0.2 Lollipop, no rooting and stuff ever performed! And I don't know if an app was recently updated, something that might be causing the issue...
I have the 16GB version and it is working fine.
Any idea why this happened? :/
Right now it seems to be working well... For the whole day... Including phone calls(half an hour call with no issues). Even lags are not happening... I will check if the phone is off when I wake up... I don't have a clue of could make it turn off during the night.
How could this be happening? Suddenly fixing it by itself? This could mean the device's software is somehow sorting itself out? Or an intermittent hardware issue?
Ok so I'll post my problems :/
My phone was rebooting like crazy lately. I don't know what was causing it. My normally working system which was the optimized stock rom from here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Was working great for some time. Then suddenly it started to reboot like every 5 to 10 minutes...
Now I clean installed the stock rom, then TWRP recovery and every thing was working great through the day. Then when I was browsing the net in chrome at night the phone froze for like 10 seconds, restarted and froze at the "bootloader unlocked" screen. Also if that's any help here you have battery stats:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hop you can help because now I'll try to flash CM12 or some other rom to see if it'll help anything :/
XT1032 gets powered off randomly after lollipop 5.0.2 update
Hi,
My issue is similar but not exactly same.
My 1st Gen Moto G has undergone system upgrade (as Motorola made it available) to lollipop 5.0.2 by end of April 2015. Everything was fine after this upgrade, except I noticed 3-4 times that the mobile just simply powers off when it was in standby mode. Suppose, I wake up in the morning and tried to make the screen on by pressing the power button, but it did not start. Then I realised the phone is switched off. It happened in the first week after upgrade and only 3-4 times which then I forgot as by 20th May it didn't happen. Then suddenly for last 7 days it became rampant. On 21st, it happened 4 times. - mostly when it is on standby mode. Once it happened as the mobile was just restarted - so it happens when not in standby mode as well. Then once I rebooted it by holding power and vol lower button together for 120 sec. Then it ran for almost 2 and half days without the issue. Then suddenly yesterday it was powered off again
Can anyone suggest anything? It seems to be software issue as this issue was not there before the upgrade. Is it a bug of Lollipop 5.0.2? Is there any resolution for this? Can I downgrade my phone OS to Kitkat 4.4.4 as it was before the issue?
Model :
XT1032
Baseband version :
MSM8626BP_1032.3105.93.00R TESCOGB_CUST
Karnel Version :
3.4.42-gdd242b0
[email protected] #1
Fri Jan 23 08:12:33 CST 2015
System Version :
220.27.1.falcon_umts.TescoSL.en.GB
Build Number :
LXB22.46-28.1
Any suggestion would be helpful. Due to rampant shutdown - the phone has become unreliable. I frantically check after every 5 min if the phone is switched on.
Thanks in advance,
Bijitesh
Advise please
It seems the issue is not wide spread and there is no solution. Is there any crash report stored in Android which we can check to get to root of the issue? Just for info, the handset is not rooted yet. So advise accordingly.
Thanks,
wrbl said:
Ok so I'll post my problems :/
My phone was rebooting like crazy lately. I don't know what was causing it. My normally working system which was the optimized stock rom from here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Was working great for some time. Then suddenly it started to reboot like every 5 to 10 minutes...
Now I clean installed the stock rom, then TWRP recovery and every thing was working great through the day. Then when I was browsing the net in chrome at night the phone froze for like 10 seconds, restarted and froze at the "bootloader unlocked" screen. Also if that's any help here you have battery stats:
Hop you can help because now I'll try to flash CM12 or some other rom to see if it'll help anything :/
Click to expand...
Click to collapse
Its weird how your WiFi stays running while every other stops at the freeze. Mine did it the other day while I was browsing chrome screen went white then black for about 15 minutes, then rebooted. And sometimes when I start a app it takes ages for the app to load. Motorola defiantly need to sort it out with this memory bug with an update. They can't just leave users with this mess of a lollipop update, can they?
Hello everybody,
I am enjoying my S22 Ultra which is almost 2 days old now.
Something strange happened.
I have also raised this in another topic but by then, i didn't know the reasons and i didn't give much details.
Today i had some testing.
Yesterday night, after i set up the phone 99% (with the apps i used but not fine tuned), i charged the phone to 100% for the first time (the only 100% was when i got the phone before first starting) and as it hit 100% i removed from the charge and went to sleep.
This morning, to check notifications and take notes of some of the items, when i got Spen out and used it, the phone (touchscreen) got laggish and phone started acting a bit late and weird in terms of response to open apps or make actions in them.
Anyways, after like 5 minutes the phone made a soft restart itself and drained around 6-8% of battery.
I wasn't pleased but didn't make a big fuss out of it.
This happened when i tried to resize the note app size with Spen drawn out. First instead of resizing, the note (right and bottom quarters) were dragged out of the screen making the right end and bottom sides unusable and also made the resizing impossible.
After the reset, some hours later, i tried the same and got the crash report of notes. Literally the notes app crashed when i resized the note screen with the Spen.
Did this happen to somebody else?
Any recommendations?
I thought of removing Samsung Notes and reinstalling but also thought maybe Spen also need to be formatted etc.
Otherwise the phone seems to be acting pretty good with just some minor milisecond lags/stutters once in a long while, battery still has 17% with around 4,5hrs SoT (and this is as said the 2nd day, battery is still learning, didn't do any power saving, never turned bluetooth off etc. So using it as it must be used) with a total of 22hrs battery usage.
Have around 100 apps that i use installed etc.
So it would say otherwise it is holding pretty good.
Would appreciate if you guys can help me pinpoint and solve this issue.
Thank you in advance
First thing I would do is check if any updates are available and install them to get up to the latest version.
Clear system cache.
Try a hard reboot (NOT factory reset).
Try in safe mode as a 3rd party app may be the cause.
Return Samsung apps to their factory load version; undo updates. Clear related app cache then data if the former doesn't work.
Try to find the root cause rather than doing a factory reset as the issue is likely to reoccur.
Factory reset if you did a major OTA upgrade.
If you used SmartSwitch, if suspect malware or if you can not resolve it (if so use discretion loading 3rd party apps after the reset!).
I did and didn't see any updates.
The device is SD 512 btw if that matters
Rubby1025 said:
First thing I would do is check if any updates are available and install them to get up to the latest version.
Click to expand...
Click to collapse
blackhawk said:
Clear system cache.
Try a hard reboot (NOT factory reset).
Try in safe mode as a 3rd party app may be the cause.
Return Samsung apps to their factory load version; undo updates. Clear related app cache then data if the former doesn't work.
Try to find the root cause rather than doing a factory reset as the issue is likely to reoccur.
Factory reset if you did a major OTA upgrade.
If you used SmartSwitch, if suspect malware or if you can not resolve it (if so use discretion loading 3rd party apps after the reset!).
Click to expand...
Click to collapse
I didn't do smart switch. Downloaded everything from scratch.
The data was mostly on cloud anyway (OneDrive and Google).
Only thing i did was to increase additional RAM to 8gb rather than 4 (12+8 now rather than 12+4).
Do you think it is fixable or shall i return/replace it?
However, mimicing the same for the service would be hard.
Also, tbh, worried if i replace and get a phone with bad battery or bad cpu etc.
Man, i h8 this situation Samsung put which make us think 3 times before doing something with the phone.
Digie said:
I didn't do smart switch. Downloaded everything from scratch.
The data was mostly on cloud anyway (OneDrive and Google).
Only thing i did was to increase additional RAM to 8gb rather than 4 (12+8 now rather than 12+4).
Do you think it is fixable or shall i return/replace it?
However, mimicing the same for the service would be hard.
Also, tbh, worried if i replace and get a phone with bad battery or bad cpu etc.
Man, i h8 this situation Samsung put which make us think 3 times before doing something with the phone.
Click to expand...
Click to collapse
Your call on returning. Since you don't know the cause it's hard to say. It's likely not hardware but that can't be completely rules out. Many apps aren't compatible with Android 11 and especially 12, that's probably the cause or a bug on the Samsung side.
Personally I haven't found a keeper in any of the Samsung post N10+ releases... my N10+'s will likely be in use for years. Between Samsung and Gookill Android I no desire to deal with their substandard bs... hype walks, functionality talks.
They haven't given more than they took away since the N10+. Not having an SD card causes many issues and is not acceptable. It's far more important than 5G or variable refresh rates, the latter two contribute to reduced battery life. Scoped storage and forced encryption has also degraded performance and battery life. When I add the known excellent build quality, form factor and reliability of the N10+, it became the logical choice. Bought my second new one 5 months ago.
I use whatever comes in handy.
blackhawk said:
Your call on returning. Since you don't know the cause it's hard to say. It's likely not hardware but that can't be completely rules out. Many apps aren't compatible with Android 11 and especially 12, that's probably the cause or a bug on the Samsung side.
Personally I haven't found a keeper in any of the Samsung post N10+ releases... my N10+'s will likely be in use for years. Between Samsung and Gookill Android I no desire to deal with their substandard bs... hype walks, functionality talks.
They haven't given more than they took away since the N10+. Not having an SD card causes many issues and is not acceptable. It's far more important than 5G or variable refresh rates, the latter two contribute to reduced battery life. Scoped storage and forced encryption has also degraded performance and battery life. When I add the known excellent build quality, form factor and reliability of the N10+, it became the logical choice. Bought my second new one 5 months ago.
I use whatever comes in handy.
Click to expand...
Click to collapse
I was asking about your opinion since you are more experienced in Samsung than me.
The battery drain occured after the Spen issue happened.
And today i got the "Notes stopped working" error when i was playing with Spen/notes to see if i could replicate the error.
And just now, i tried to replicate it again and moved the window around aggressively.
Only issue is time to time Spen stopped dragging it as if i have lifted.
Other than that, the phone acts/reacts normal.
The only differences are as follows;
1) The note screen is smaller than the beginning if it may have an impact
2) I think the first time it rebooted, i was dragging it aggressively while it was giving (or trying to give) the first time tips for the Spen notes
Did it fix itself, maybe?
Maybe shall i try increasing the size of note window and test again?
I got burned by snotes so I never have used them in their latest incarnation.
If that's the only issue with the spen/display it's likely nothing serious. Most issues on my N10+'s I fix by playing with them; play & learn.
Go to Device Care>memory and clear the cache, now open the app giving you trouble, and see what populates in that cache screen when it loads or when there's trouble. The apps at the top have most recently loaded. Developer options>running/cache services too.
You can also see ram usage in Developer options and running services, check for memory leaks, etc.
Further down, open Standby apps, do all buckets show as active? If so global power management is not enabled. However if you can change the bucket state it means power management is running, if so disable it. It's a know trouble maker.
Global power management is disabled. You can not turn it on/off here, it's found in Device Care>battery. Only enable fast/super charging there on the switch toggles.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}