UPDATE: SOLVED
Here I am again,
Story
I've been using a HTC One since April , but I keep maintaining my GS3 (I9300) that my girlfriend uses now.
I keep maintaining it because it keeps needing maintenance. I always use stable ROM's and no custom kernels or other modifications, because she just wants a normal working phone. Sadly, it's been problems after problems. First of all, after using CM10 for months starting in April, the phone just stopped working. I still don't understand what happened. It started performing worse and worse, until it wouldn't even boot up anymore. Anyway, I managed to get a stock ROM on it after sadly deleting everything of her phone. The phone at least worked again.
Recently, I decided to flash something different for her because it was such a laggy old ROM. I flashed ARHD 40 (android 4.3) since I use ARHD on my HTC One as well and it's usually very stable. The performance was way better now, her phone was as fast as my HTC One. Though she became aware of one problem quite quickly: the phone takes anywhere from 5 seconds to 1 minute to wake up from sleep. I even called her and it wouldn't appear because the phone was not waking up.
Now here comes the problem
Running ARHD 40 (android 4.3), I decided to flash Boeffla-Kernel 5.1beta12 (newest I could find). As far as I read, this would fix the slow/not waking up from sleep.
Now here comes the real problem
I needed to boot into recovery to flash this kernel. Since this ROM didn't have a quick boot into recovery shortcut, I decided to download ROM Toolbox Lite. First of all to see what it's about, since I recalled hearing nice things about it. And it had a boot into recovery option, so that would be easy.
I pressed the button to go into recovery.
Since then, my phone is completely stuck, constantly trying to boot into recovery but failing. You see it's trying (the 4 buttons at the bottom appearing from the recovery) and sometimes even the wallpaper shows up. But it always stops, after which it reboots and I see the logo. And this keeps repeating over and over again.
I removed the battery a few times, I tried holding down the power button a long time, to force it to just boot itself up normally again. I can enter download mode, though I have nothing there to help me. Phone is basically completely useless.
My question
Does anybody know anything about this? Is it a known problem? Is my first experience with this ROM Toolbox Lite the most horrible one ever, or does it play no role in the problem?
It was to late to start searching for solutions yesterday evening, I had to work early again today and I was so pissed I would have broken the damn plastic thing in two. So I just decided to leave it and my girlfriend is passing this day without one. But I'm really sure I want to fix the damn thing when I get home in a few hours. If possible, to just make it stable, fast and NORMAL, with no more weird problems in the future...
Thanks in advance!
Kind regards
XDA mark said:
Here I am again,
Story
I've been using a HTC One since April , but I keep maintaining my GS3 (I9300) that my girlfriend uses now.
I keep maintaining it because it keeps needing maintenance. I always use stable ROM's and no custom kernels or other modifications, because she just wants a normal working phone. Sadly, it's been problems after problems. First of all, after using CM10 for months starting in April, the phone just stopped working. I still don't understand what happened. It started performing worse and worse, until it wouldn't even boot up anymore. Anyway, I managed to get a stock ROM on it after sadly deleting everything of her phone. The phone at least worked again.
Recently, I decided to flash something different for her because it was such a laggy old ROM. I flashed ARHD 40 (android 4.3) since I use ARHD on my HTC One as well and it's usually very stable. The performance was way better now, her phone was as fast as my HTC One. Though she became aware of one problem quite quickly: the phone takes anywhere from 5 seconds to 1 minute to wake up from sleep. I even called her and it wouldn't appear because the phone was not waking up.
Now here comes the problem
Running ARHD 40 (android 4.3), I decided to flash Boeffla-Kernel 5.1beta12 (newest I could find). As far as I read, this would fix the slow/not waking up from sleep.
Now here comes the real problem
I needed to boot into recovery to flash this kernel. Since this ROM didn't have a quick boot into recovery shortcut, I decided to download ROM Toolbox Lite. First of all to see what it's about, since I recalled hearing nice things about it. And it had a boot into recovery option, so that would be easy.
I pressed the button to go into recovery.
Since then, my phone is completely stuck, constantly trying to boot into recovery but failing. You see it's trying (the 4 buttons at the bottom appearing from the recovery) and sometimes even the wallpaper shows up. But it always stops, after which it reboots and I see the logo. And this keeps repeating over and over again.
I removed the battery a few times, I tried holding down the power button a long time, to force it to just boot itself up normally again. I can enter download mode, though I have nothing there to help me. Phone is basically completely useless.
My question
Does anybody know anything about this? Is it a known problem? Is my first experience with this ROM Toolbox Lite the most horrible one ever, or does it play no role in the problem?
It was to late to start searching for solutions yesterday evening, I had to work early again today and I was so pissed I would have broken the damn plastic thing in two. So I just decided to leave it and my girlfriend is passing this day without one. But I'm really sure I want to fix the damn thing when I get home in a few hours. If possible, to just make it stable, fast and NORMAL, with no more weird problems in the future...
Thanks in advance!
Kind regards
Click to expand...
Click to collapse
What do you mean "can enter download mode, though I have nothing there to help me" What happens exactly when you enter download mode....Can't you just flash back to stock with odin in download mode ?
Edit:..Have you tried ADB into recovery or tried this >>> http://forum.xda-developers.com/showthread.php?t=1703488 <<< toolkit
tallman43 said:
What do you mean "can enter download mode, though I have nothing there to help me" What happens exactly when you enter download mode....Can't you just flash back to stock with odin in download mode ?
Edit:..Have you tried ADB into recovery or tried this >>> http://forum.xda-developers.com/showthread.php?t=1703488 <<< toolkit
Click to expand...
Click to collapse
I can enter download mode normally, so I can use Odin to flash stuff.
I just flashed that kernel I wanted to flash before my phone went trippin, but after flash the same continues. Re-downloading ARHD 40 via my laptop now and going to reflash it via odin, hope that my phone can then let go of it's obsession of trying to get into recovery.
There must be a way to fix this, I didn't make a Titanium Backup for a while. Don't want to lose stuff just because I got some super rare weird problem... again. Why does tech hate me
EDIT:
Realized that I can't flash ARHD 40 because it only comes in zip not tar... anyway, tried flashing the newest version of philz touch recovery, still didn't change anything.
EDIT 2:
Flashed TWRP recovery via ODIN, now everything is fine again. It rebooted into TWRP normally, then choose to reboot the device. Everything is still there, like nothing ever happened.
THANK you lord!
Out of interest, how do you find the HTC 1 compared to the S3?
gsw5700 said:
Out of interest, how do you find the HTC 1 compared to the S3?
Click to expand...
Click to collapse
It's an entirely different phone, especially how it feels and looks. After using the One for such a long time, I find it super weird to hold a S3.. it feels so light and "cheap", though ergonomically the S3 is a tad easier to hold then the One. Overall I enjoy using the HTC One much more as it feels really solid.
Besides that it's fast and stable, what you would expect, but not much faster then a S3 with a good ROM. Screen is really excellent, this is also a big difference from the S3. It's a different type of screen and you can really notice. The speakers are the nicest you can get on a phone and compared to the S3 they are really a league above. The camera is average, sometimes it's great sometimes it isn't. Battery life is comparable to the S3.
Not that I didn't enjoy my S2 and S3 at the time, but I'm not really interested in the Galaxy line anymore at the moment. Samsung really has to do something amazing to get my attention again Will see what HTC brings with the successor of the HTC One, might upgrade to that one. I'm also curious about the iPhone 6 to be honest, the small screen is the main reason I haven't owned an iPhone in my life, if that changes I might want to try it. Or I might just use my current device for a second year for a change, since it's excellent
Many thanks for that, I now intend to take a look at the new HTC m8 - hoping the camera is better!
Me too. If they make a big leap with the camera and bring it on par with the iPhone 5S for example, it would be fantastic. Battery life should also be brought to the new higher standards of the LG G2.
If these 2 things happen they already got me, since it's a near perfect phone. Add some bonuses like making the bezels smaller/screen larger in the same body... don't think I could resist
Related
My note started doing this after it went through airport security. It was in a bag and went through the x-ray machine. It randomly reboots very often, probably between 20-60 second intervals. I was on CM10, then I flashed back to stock ICS, and then finally up to the official JB update. None of which has solved this problem.
i posted in here.. this may help.
http://forum.xda-developers.com/showthread.php?t=1854944
Good Luck
Still need help
dweeezy said:
i posted in here.. this may help.
http://forum.xda-developers.com/showthread.php?t=1854944
Good Luck
Click to expand...
Click to collapse
Phone is stuck in a boot loop and this is what I know so far. Phone is on stock ROM, power button is working fine, I can get to recovery and OS and download mode, and while phone was charging I took the battery out and the phone keeps vibrating. I now know it's a hardware problem for me (I think), but I can not pin point where. Any advise would be helpful cause I really love my note and this is just breaking my heart.:crying:
I have been having issues where my phone have been freezing up at seemingly random times and then getting into a bootloop until i do a hard power off and turn it back on. I've attempted a clean reinstall of the ROM but no luck.
I was going to flash RUU but my USB port doesn't work for data anymore so fastboot is out. (I tried to use fastboot on 2 computers running Win 7/ 8.1 with a couple different USB cables)
Can anyone recommend any sort of troubleshooting solutions to get this ROM (or possibly a different 4.4 AOSP ROM) to run a bit more stable?
admiral licorice chaps said:
I have been having issues where my phone have been freezing up at seemingly random times and then getting into a bootloop until i do a hard power off and turn it back on. I've attempted a clean reinstall of the ROM but no luck.
I was going to flash RUU but my USB port doesn't work for data anymore so fastboot is out. (I tried to use fastboot on 2 computers running Win 7/ 8.1 with a couple different USB cables)
Can anyone recommend any sort of troubleshooting solutions to get this ROM (or possibly a different 4.4 AOSP ROM) to run a bit more stable?
Click to expand...
Click to collapse
Hi, sorry, I don't have an answer necessarily, but I was having the same issue with OmniRom before I moved over to the new partition layout. One thing you might try, though, is going back to stock (or at least some Sense based Rom) and see if you can get ADB/Fastboot working on it then. I noticed that I wasn't able to get it working on AOSP Rom (I think it was PAC-Rom specifically) but when I restored back to my Initial Stock nandroid, I was able to do it (Run the RUU for new partitions). So give that a try before giving up.
But I also had the random freeze, and boot which could only be stopped by the simulated battery pull like you described, and then it would work. A couple times, I would just be using it and it would freeze. A couple other times I would pull it out of my pocked and it was sitting there with the little android dude sitting there in the circle, staring at me. One time I just left it there for a while, and noticed that it actually was booting (kind of) but super slowly. It would sit there for like a minute, and then the antennae would twitch a little, wait 3 seconds, twitch again, wait 3 seconds twitch again. It was like it was running on extreme slow motion on the boot animation. I don't know if it ever would have finished, given enough time, because I never gave it enough time.
Anyway, if anybody has ideas on why AOSP roms seem to do that, I'd appreciate it. Had a similar experience with PAC-Rom, on the old partitions, with random freezes that couldn't be recovered from.
bpaulien said:
Hi, sorry, I don't have an answer necessarily, but I was having the same issue with OmniRom before I moved over to the new partition layout. One thing you might try, though, is going back to stock (or at least some Sense based Rom) and see if you can get ADB/Fastboot working on it then. I noticed that I wasn't able to get it working on AOSP Rom (I think it was PAC-Rom specifically) but when I restored back to my Initial Stock nandroid, I was able to do it (Run the RUU for new partitions). So give that a try before giving up.
But I also had the random freeze, and boot which could only be stopped by the simulated battery pull like you described, and then it would work. A couple times, I would just be using it and it would freeze. A couple other times I would pull it out of my pocked and it was sitting there with the little android dude sitting there in the circle, staring at me. One time I just left it there for a while, and noticed that it actually was booting (kind of) but super slowly. It would sit there for like a minute, and then the antennae would twitch a little, wait 3 seconds, twitch again, wait 3 seconds twitch again. It was like it was running on extreme slow motion on the boot animation. I don't know if it ever would have finished, given enough time, because I never gave it enough time.
Anyway, if anybody has ideas on why AOSP roms seem to do that, I'd appreciate it. Had a similar experience with PAC-Rom, on the old partitions, with random freezes that couldn't be recovered from.
Click to expand...
Click to collapse
Nah, installing a Sense ROM didn't work out for recognizing data over USB. I'm hesitant to flash RUU over wifi ADB (if thats even possible) because I wouldn't be able to use fastboot if something goes wrong.
admiral licorice chaps said:
Nah, installing a Sense ROM didn't work out for recognizing data over USB. I'm hesitant to flash RUU over wifi ADB (if thats even possible) because I wouldn't be able to use fastboot if something goes wrong.
Click to expand...
Click to collapse
That's good you didn't try it over wireless, because as part of the RUU process, it reboots to fastboot, and if all you had was a wireless connection at that point, the process would fail.
bpaulien said:
That's good you didn't try it over wireless, because as part of the RUU process, it reboots to fastboot, and if all you had was a wireless connection at that point, the process would fail.
Click to expand...
Click to collapse
Hmmm.... I may be out of luck then. I'll just deal with the issues until a new Nexus phone is released (if one ever is).
Thanks for the suggestions though.
[Q&A] [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014
Q&A for [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
gpz1100 said:
I gave up trying to calibrate my compass. I have issues with it in any rom including stock TW. Some of these chips are just broken.
Click to expand...
Click to collapse
After trying many of the suggestions on this thread to fix the compass (my GPS lock is fine), I thought I might have messed up the hardware somehow. However, last night I flashed the 7/12 KT GE kernel, and the compass now correctly points in the right direction.
Germany?
Hi Dan (or whoever else reads this). Love the ROM! It's amazing. Do you know if it will work in Germany? I went to Mexico a few months ago, and the latest build at the time would not get reception anywhere. Flashing a TW ROM solved the problem, but I would much rather use yours.
Thanks!
TheSt33v said:
Hi Dan (or whoever else reads this). Love the ROM! It's amazing. Do you know if it will work in Germany? I went to Mexico a few months ago, and the latest build at the time would not get reception anywhere. Flashing a TW ROM solved the problem, but I would much rather use yours.
Thanks!
Click to expand...
Click to collapse
Well in case anyone is curious, this ROM gives me great cell service (full signal on Vodaphone.de) but no data in Munich. I tried airplane mode, disabling/enabling data roaming several times and setting the network mode to GSM preferred, but no luck. Flashing the latest release of Hyperdrive ROM allowed me to use data. Oh well.
flashing google edition on verizon s4 on nc5
I'm a noob and can't figure out if i can use safestrap to flash the dandvh google play edition rom.
verizon galaxy s4 on nc5 build, rooted with towel root and running safestrap 3.75
Viper Audio Working?
Does anyone else use Viper Audio with this rom? I find that the audio driver frequently stops processing when I stop playing music and then come back and play again. It will start processing again if I reboot the phone or even kill the Viper gui process. I've tried installing it as a user or system app but hasn't seemed to matter. Anyway, just curious if anyone else was having the same kind of results.
Hi everyone, hoping you all can help me with a problem I'm having with my phone. First, some specs:
ROM: Danvdh GPE 9/30
I am one of those lucky MDK users, I got the phone in May 2013 and rooted early
I had been running the NC5 modem for a while now with no issue. The problem started after I flashed the NG6 modem (from Surge1223's thread) in TWRP. Just fyi, here are the steps I took to flash the modem. Within TWRP, I flashed the zip file, cleared Dalvik/cache, then rebooted.
Almost immediately I started getting random reboots. It rebooted twice, then seemed to settle down, so I decided to wait a day or so to see what my phone would do. Sadly enough, it started rebooting again, so I gave up last night and reflashed the NC5 modem in TWRP using the same method as before. The phone was fine after that, until this afternoon. About an hour ago, my phone froze, and rebooted, but the screen cut off at the Samsung custom padlock boot screen. It seems to be off at this point, but I can't power on the phone without pulling the battery. After pulling and replacing the battery, the phone powers on by itself, but again cuts off at the Samsung boot screen, about 3-4 seconds into the boot process. I've tried booting into TWRP and download mode, with the screen turning off and the device seemingly freezing after 3-4 seconds. I'm at a loss as to what to do at this point.
I'm at work right now, but when I get home, I will see if Odin3 can make some sort of contact with the phone. Any help in the meantime would be greatly appreciated!
Sounds like you may have a bad dl. Re download. Turn phone off. Then boot into TWRP and reflash the modem zip. Not the non-halos.zip.
Alxoom33 said:
Sounds like you may have a bad dl. Re download. Turn phone off. Then boot into TWRP and reflash the modem zip. Not the non-halos.zip.
Click to expand...
Click to collapse
I would love to, but I can't.
I put a video up on Youtube showing what the phone is doing right now. I don't have 10 posts yet, so I can't post links, but if you go to youtube.com then add "/watch?v=3ey5xD9LodY" at the end of the URL, you can see what the phone is doing.
It is the only thing the phone will do. I've tried doing a hard reset by holding the power button, but nothing happens. All I can do is pull the battery and start this process again. If I hold the correct button combos, I can begin to boot into TWRP or download mode, but the phone cuts off/freezes like clockwork after 3 seconds.
I tried to get Odin3 to recognize the phone, but my desktop doesn't recognize that anything is plugged in when I connect my phone to it, so Odin3 by extension doesn't see anything.
Did you install the Samsung apps on your computer? You need them for the computer to recognize your phone.
To hard boot into recovery you need to hold power button and volume up at the same time, then let go of power button once blue writing appears on upper corner of phone.
Sent from my Xoom Wifi using Tapatalk
I'm sure I have. I've been able to send adb commands to the phone in the past. Now however, my PC doesn't even see that a device has been connected to it (nothing shows up in the device manager, not even an unrecognized device).
The phone will no longer charge when I plug it into an AC adapter either (or at least the LED no longer lights up indicating it's charging).
I have tried booting into recovery several times. Each time, it will begin to boot into TWRP, the blue text, "RECOVERY BOOTING...", will display, then immediately afterwards, the screen will cut off and the phone will freeze, just like in the Youtube video I posted.
I'm afraid the thing is bricked...
So, I was talking to a friend about what's been going on with my phone. During the conversation, I started goofing around and smacking the back of the phone like 4-year-old me would an NES to try and make it work (ah, good times...). Believe it or not (and I did not touch the power button while doing this), the phone powered up and successfully booted!!!
It showed only 2% battery life, so I connected it to the AC adapter, but then a few seconds later the phone died again.
This occurrence leads me to believe there is something wrong with the battery, and leads me to another question. Can the S4 (or any other smartphone) run solely on USB power?
My roommate has a Galaxy SIII, I read the SIII battery can be used in the S4, so I will test the phone out with his battery when he gets back tomorrow, and update you then.
marioluigi64 said:
So, I was talking to a friend about what's been going on with my phone. During the conversation, I started goofing around and smacking the back of the phone like 4-year-old me would an NES to try and make it work (ah, good times...). Believe it or not (and I did not touch the power button while doing this), the phone powered up and successfully booted!!!
It showed only 2% battery life, so I connected it to the AC adapter, but then a few seconds later the phone died again.
This occurrence leads me to believe there is something wrong with the battery, and leads me to another question. Can the S4 (or any other smartphone) run solely on USB power?
My roommate has a Galaxy SIII, I read the SIII battery can be used in the S4, so I will test the phone out with his battery when he gets back tomorrow, and update you then.
Click to expand...
Click to collapse
Have you tried a different USB cable/transformer? It sounds like you might just have a charging issue. Not enough juice to get it started.
Allowing a battery to cool down will give it more usable power, which as it heats back up will deplete again. This sounds like your situation... Power off for a few, restart it has enough to begin booting, then depleted again.
The phone cannot run on USB alone it needs the battery to sustain it's operation.
I have tried 3 USB cables, 2 AC adapters, and 2 PCs.
When this started on Friday, my phone was hooked up to my PC at work and showing about 50% battery, but it's possible something went wrong with the battery and it's stopped delivering any significant amount of power or accepting a charge.
So it turns out it wasn't the rom or new modem that was the problem, my battery has decided to kick the bucket. I tried my roommate's battery in my phone and it booted right up as if nothing was ever wrong! Strange that an OEM battery would just die like that, but I suppose that does happen from time to time. Thanks for the help!
matycakes said:
Does anyone else use Viper Audio with this rom? I find that the audio driver frequently stops processing when I stop playing music and then come back and play again. It will start processing again if I reboot the phone or even kill the Viper gui process. I've tried installing it as a user or system app but hasn't seemed to matter. Anyway, just curious if anyone else was having the same kind of results.
Click to expand...
Click to collapse
I use it, and I've never had any issues with it. I would recommend reinstalling, but you've probably tried that already. Are you using the latest version of the app?
TheSt33v said:
I use it, and I've never had any issues with it. I would recommend reinstalling, but you've probably tried that already. Are you using the latest version of the app?
Click to expand...
Click to collapse
Yeah, I have tried reinstalling it, and I am using the latest version of the app. The fact that you haven't had any issues is encouraging. I'll continue to troubleshoot and see what I can find.
I keep getting this (in CWM touch)
Flashing Google Play Edition
Android 4.4.4
Enjoy!
format() expects 5 args, got 4
E: Error in /storage/sdcard1/danvdh-GE-4.4.4-09-30-2014-VZW.zip
(status 7)
installation aborted
Is it just a bad DL?
EDIT: Tried a new DL, same issue. I want to get this fixed asap
Is cm11 theme manager included in this rom?
brd912 said:
Is cm11 theme manager included in this rom?
Click to expand...
Click to collapse
It is not.
Hi all. I am hoping you guys an help as I am about to go back to my Nexus 6 at this point. I got a 64gb Galaxy S6 edge shipped to me at the end of March. On the first day I activated it I got the pop up that there was a software update so I did that. Every single review I've read talk to how the lag is almost gone, no overheating issues, etc. I stayed away from Samsung for so long because TouchWiz completely destroyed the Android experience for me, causing intense lag and slow down. If there is anything I can't stand when using a smartphone it is lag. Anyway, it seemed to work ok at first but I quickly noticed that it would get extremely hot for absolutely no reason at all. It will also completely lag out for no reason. For example. I'll go to unlock the phone from the lock screen and the animation will show it was swiped but it will just sit there for up to 20 seconds before doing anything. Often it just goes back to a black screen and I have to press the home button to try and unlock it again. If I try to use Google Maps many times it just hangs there for what seems like forever before it will move forward to actually start the navigation process. Navigating between music apps is painstakingly slow. I have powered off the unit multiple times, closed all open apps multiple times, etc and it doesn't seem to do anything. It will work better for a short time and then does it again. When I try to launch the camera it is supposed to launch super fast. At times I just sit there and wait. It is extremely frustrating. The longest I've had it sit there and freeze or lag has been close to a minute.
It also always seems like it is reallllllly warm, even after just a short while of using it. Again, it isn't every time I use it but more like 70% of the time. It could be resting in my pocket and get really hot, for example. It makes no sense.
Is my unit boned, or is this a common issue? I asked my developer friend and he suggested I turn off animations, etc. but why would I need to do this? I bought the phone with some crazy octa-core processor and tons of memory so it should breeze through all of this like nothing. My Nexus 6 almost never had any lag whatsoever and I would really like to think this phone is capable of more than what it is doing right now.
Any suggestions you guys have are more than welcome. I really like the phone but am at the point where if I can't get this awful lag/hanging issues fixed it is going on eBay =(.
Thanks for your time .
svenb352 said:
Hi all. I am hoping you guys an help as I am about to go back to my Nexus 6 at this point. I got a 64gb Galaxy S6 edge shipped to me at the end of March. On the first day I activated it I got the pop up that there was a software update so I did that. Every single review I've read talk to how the lag is almost gone, no overheating issues, etc. I stayed away from Samsung for so long because TouchWiz completely destroyed the Android experience for me, causing intense lag and slow down. If there is anything I can't stand when using a smartphone it is lag. Anyway, it seemed to work ok at first but I quickly noticed that it would get extremely hot for absolutely no reason at all. It will also completely lag out for no reason. For example. I'll go to unlock the phone from the lock screen and the animation will show it was swiped but it will just sit there for up to 20 seconds before doing anything. Often it just goes back to a black screen and I have to press the home button to try and unlock it again. If I try to use Google Maps many times it just hangs there for what seems like forever before it will move forward to actually start the navigation process. Navigating between music apps is painstakingly slow. I have powered off the unit multiple times, closed all open apps multiple times, etc and it doesn't seem to do anything. It will work better for a short time and then does it again. When I try to launch the camera it is supposed to launch super fast. At times I just sit there and wait. It is extremely frustrating. The longest I've had it sit there and freeze or lag has been close to a minute.
It also always seems like it is reallllllly warm, even after just a short while of using it. Again, it isn't every time I use it but more like 70% of the time. It could be resting in my pocket and get really hot, for example. It makes no sense.
Is my unit boned, or is this a common issue? I asked my developer friend and he suggested I turn off animations, etc. but why would I need to do this? I bought the phone with some crazy octa-core processor and tons of memory so it should breeze through all of this like nothing. My Nexus 6 almost never had any lag whatsoever and I would really like to think this phone is capable of more than what it is doing right now.
Any suggestions you guys have are more than welcome. I really like the phone but am at the point where if I can't get this awful lag/hanging issues fixed it is going on eBay =(.
Thanks for your time .
Click to expand...
Click to collapse
Quick answer factory reset see if that helps if not take it back to the store
I have no lag at all
I do have Lookout Mobile Security enabled, but it is only using like 7MB of ram. That wouldn't be causing this would it? I checked online at forum sites and it doesn't appear as though it would.
My first (S6 not edge) was like that. Turned into a handwarmer, got so hot it was literally burning hot! Took it back to the TMO store. Manager could not believe how hot the phone was, the box was warm and the phone inside was like a hot potato! Still frozen on the white TMobile splash screen from where it locked and stayed for hours. The phone was never really right. Got it exchanged for an Edge and it has been problem free, hardware wise.
Sounds like you have a bad one.
The Nexus 6 is a good phone, was going to sell mine but I need it to work with Google-Fi.
As suggested above, I would try factory reset first. Mine is very responsive even in power savings mode. It's just fast. I leave animation on at the default 1x. Did you look to see which apps are running the CPU up?
before a factory reset, try to go into recovery mode and clear cache. I've found on the tmobile version that once i got into recovery mode it did something of a small update automatically (in reading the scripts) and that doing that and then clearing cache really helped my battery drain i was having- might fix your lag too.
Clearing cache and factory reset after the update stopped my lag.
The battery though, just sucks. I'm down to 35% in 6 hours with less than 30 minutes of use.
I'm missing my nexus 6 at the moment. I hope I didn't mess up buying this.
Sent from my SM-G925T using Tapatalk
Guys I'm fairly certain this is just the typical 5.0.1 problem... I'm experiencing it too and factory wipes only fix temporarily.
Had same thing on my Moto X 2014 and went away with 5.1 update.
dominante58 said:
before a factory reset, try to go into recovery mode and clear cache. I've found on the tmobile version that once i got into recovery mode it did something of a small update automatically (in reading the scripts) and that doing that and then clearing cache really helped my battery drain i was having- might fix your lag too.
Click to expand...
Click to collapse
Hi there. Thanks for this tip. I went ahead and did this and it did a software update as soon as I went into recovery. I cleared out the cache as well and it seems to be much zippier now. What I have found with Samsung phones, though, is that usually they work fine for a few days and then end up going to hell. Thanks for your help and I will keep an eye on this. If it keeps ending up working poorly I will go back to the Nexus 6.
diaa08 said:
Guys I'm fairly certain this is just the typical 5.0.1 problem... I'm experiencing it too and factory wipes only fix temporarily.
Had same thing on my Moto X 2014 and went away with 5.1 update.
Click to expand...
Click to collapse
I really hope that's not the case since Samsung takes 10 times longer than any other OEM to update Android
Encountered a bit of lag again earlier. Cleared out cache again via recovery and resolved it. Definitely think I have a bum unit or something with this version of Android
Sent from my Galaxy S6 edge on T-Mobile via Tapatalk
I thought the main lollipop memory issue was tracked down to boot up animation and Touchwiz devices are not meant to have this, therefore the fix Google has made to stock devices has no bearing on Touchwiz. Basically the issues we have are Touchwiz related not Lollipop specific, though Samsung must be delighted as we all throw blame at Google it diverts blame.
One such bug is the*boot animation memory leak*bug which consumes greater amounts of memory during boot forcing the kernel to kill few process (might be core services as well) causing severe lags.*arter97*of XDA has found a work around for this issue and according to him*“the current Lollipop boot animation implementation does not releases the resources held to*playprevious frames”*which might be the root cause of the issue.
According to the developer’s research, almost all the devices (except for the Touchwiz based Samsung device) fall prey to this bug causing highly unstable UI.
Click to expand...
Click to collapse
http://www.droidviews.com/fix-android-5-0-lollipop-boot-animation-memory-leak/
Factory reset did it for me.
Hi there! Long time reader, first time poster (TL;DR below...but it should be a quick read anyways )
So I've been using this S2 of mine for almost 4 years now, haven't had any trouble (other than a couple of battery swaps). For the past 6 months or so I've been using CM 12.1 nightlies without issue.
The events:
- The other day, my phone froze (I wasn't using it when it froze, it was when I went to use it that I noticed...it was on the wifi selection screen if it matters), so I held the power button to shut it down, and when I powered it back up, it just froze at the Samsung boot screen (with the usual yellow triangle).
- At this point, I was able to reboot into download mode at will, but any attempt to boot to recovery just led to the freeze at the Samsung boot screen. Also, the phone would automatically reboot itself at this point any time I inserted the battery (I was of course putting the battery in and out trying everything I could).
- I would have reflashed from Odin at this point, but since I was away for a few days I just kept trying to reboot into recovery, to no avail. On one of these attempts (power+vol up+ home) it showed the Samsung boot screen, and then immediately shut down and I haven't been able to get anything onto the screen since
I'm now home, and I can't seem to fix it. If I plug the phone into a charger, the top half or so of the phone gets warm, and it also seems to get warm if it isn't plugged in and I try to power it up. I was thinking maybe the phone was maybe doing the same thing as before and just not showing anything on screen, but I blindly do the steps to get it into download mode, and Odin doesn't recognize anything (drivers are definitely installed). I have also tried other batteries, no luck.
Any ideas of what I might try? I'm willing to do anything. For the record nothing happened to the phone at all when this all happened (no dropping or water damage or anything, just my attempts at booting into recovery). Maybe I should try a jig? I'm also open to opening the phone if there's something I can do, though I don't have experience with this.
Thanks so much for any suggestions!
TL;DR: phone froze (running CM 12.1 nightly), held power to shut it down, and then consistently froze at the boot screen on any attempts to power it on. After a few attempts at booting into recovery (the phone would only freeze or enter download mode) the screen suddenly shut off and I haven't seen anything on it since no matter what I try. I can't think of anything that happened to the phone I'm open to any and all suggestions! Thanks
One sentence amongst your description stands out like a 'sore thumb'.....
That the device heats up towards the top when you attempt to charge it.......
Until you try a jig I can't be certain, but that heating coupled with a dead/unresponsive screen along with a lack of recovery and/or download modes (download mode is 'hardwired' into the device, and NOTHING should be able to corrupt it) are the primary symptoms of a failed motherboard.......
That is my opinion based on my experience in these forums and personal experience with a (now dead) S2 (one of two that I own).........
Get the jig just to be sure, but I'd be surprised if it had any effect.....sorry to be typing something you don't want to read, but you said it yourself, the device is 4 years old....it's been in service roughly twice as long as most smartphones, and they don't last forever....
http://i.imgur.com/rVnFwJM.jpg
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
smacsmac said:
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
Click to expand...
Click to collapse
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Sorry it took me a while...the jig was in the post haha. It didn't do anything at all (no response when I plugged it in) so I think it's safe to say you were bang-on and the motherboard failed! Happily using a new S2 (with CM13.0 now ) on behalf of my friend though.
Thanks again.
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Elaias said:
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Click to expand...
Click to collapse
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Its hard to tell you and hard to accept. You can almost give up the hope, your NAND Chip is just what we call " wear-out ". In the most cases no write is possible anymore, the funny part is -> sometimes read is still fine. If that is the case: The system is booting and working, but saving just nothing. The NAND is frozen to its state before it broke.
At our local store, customers come to us with issues like " Factory Reset impossible ", "Can't delete my Files" "Can't create files". All these Devices have inaccessible NAND's and inaccessible Recovery. Only Bootloader is working, but as the NAND is broken, flashing doesn't change anything.
smacsmac said:
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Click to expand...
Click to collapse
yeah, flashing with odin did the trick. now running cm13 and everything works fine. sorry to hear that your phone turned to brick.