Develop Bugs

[Q] Poor Response Time and Reboots?

Hi all
I'm running DeFroST 6.1a, stock DF kernel, and radio 5.11.05.14. Please bear with me because this might be a little long, as I try to explain everything I have done which landed me into a somewhat sticky situation.
A few weeks ago, I flashed the JAMT theme by ClassicalGas, and what I noted was the sudden loss of LED notification (and I don't seem to be the only one, actually). So I poke around, search the forum, and one user said he had gotten the LED notifications to work again by extracting the theme files from the JAMT framework-res.apk into the DF's framework-res and flashing the whole DF again.
I decided to try my hand at it, did a NAND, wiped, then flashed the "modified" DF - which caused my phone to be stuck in a bootloop. No biggie, just have to restore my NAND. I wipe, then when I'm about to restore my NAND, I get hit with
Code:
Error : run 'nandroid-mobile.sh' via adb!
Which, after some googling, could mean a couple of things, like the checksum is wrong, or battery is low, etc. But before I do anything, I hit the wrong button in recovery, then my ROM boots up (wiped). The first thing I realize during the starting phone set up application is that about half of my screen is not responding, but once I get out of the initial set-up, all functionality returns
I power down, charge my phone a good bit, _wiped_, then I did a NAND restore , without any problems this time, restoring my original problem free-state, and everything seemed fine
A couple of days later, on vacation, I was playing a Tower Defence game on my phone, and the whole thing froze on me. I popped out the battery. This is real strange because that game had always worked fine before.
I then try a bit of Zenonia. At certain points, my phone freezes up. Characters on screen, monsters, etc are all still moving around mind you. All EXCEPT me. There seems to be no response from touch whatsoever. I get a little frustrated and press the "home" button as well as the "power" button.
After some waiting, my phone screen goes off. I find out that it has went back to the lock screen, and when I unlock, its back to the home screen, with Zenonia still running in the background.
I inferred that my phone's response has been super delayed for some reason. It happens for over a week, sometimes, seemingly to resolve itself after a good wait, and sometimes never (which requires me to pop out the battery). Sometimes, it "hangs" so badly that my phone itself began force restart. Also, out of all the times it restarted, there was _once_ it was stuck in the bootanimation.
And I also have noticed, if my phone has been on the whole day, at night, my SMS app (stock) seems to move very slowly - in terms of when I type out my reply, the phone seems to lag behind and cannot keep up with my usual typing speed. Even pressing the "reply area" requires me to wait for some time until the keyboard pops out (not stock, but never had problems with it before).
Sometimes, unlocking the phone when I last left it as the SMS screen would also cause some lag when I unlock. Reboots from the power menu seems to clear it up (until the next time it happens again).
Last night I tried some Kongregate Arcade, which needed flash. At some point of playing, whenever I was about to receive an SMS, the phone seem to _not_ response to my touch once again, while baddies on the flash game still continued to move around and hit me.
At first I thought it might have been a problem with SetCPU's governor (does interactive cause problems? Regardless, SetCPU was not a problem before the NAND). No matter, I changed the governor of my screen off AND my "normal" profile, but still no dice.
Also, could it be a memory issue? I doubt it, I hadn't installed anything else before and after the NAND, and I manually clear any unwanted running processes (and I have been, since I've gotten the phone).
So, dear XDA, what exactly is wrong with my phone? I hope its not hardware, and I'm hoping that flashing a new ROM might help, but I haven't done so until I have heard some opinions :/
P/S: Probably at wit's end here...
Edit: I'm not sure if its related, but once when I pressed the home button when all forms of input didn't work (buttons, touch screen) when I was playing Zenonia, Launcher Pro was "about" to FC, giving me the option to kill it or to wait.

le bump with a summarized, easy on the eyes version.
1 )Bad attempt at theming DF 6.1a leads to bootloop.
2 )Wiped in preparation to restore nandroid, but accidentally boot up the device instead (boots to a "wiped" Defrost without all the bells and whistles). Top half of screen during the google account setup, wifi setup, time zone set up not responding. Problem goes away after exiting set up.
3 ) Wipe again in recovery, tried to restore NAND once more, but "Error : run 'nandroid-mobile.sh' via adb!"
4 ) Power down, charge phone, successfully restored NAND.
5 ) Phone is fine until I play games (which worked fine before). Some games totally freeze up the phone, while others are still running (monsters moving on screen and attack my unmoving character), but all forms of input is not recognized (button pressing, touch screen pressing, etc).
6) These "half-freezes" (inputs do not work, but the game still is running) also occur when playing flash games, right around the time I'm about to receive an SMS.
6 ) Whatever commands I pressed while the phone was "frozen" registers when the phone "unfreezes".
7 ) Sometimes freezes cause the phone to reboot, sometimes have to pull out the battery.
8 ) If phone has been on the whole day (regardless of heavy or light usage), stock SMS app seems to slow down and become unresponsive around late evening. A reboot fixes this.
9 ) Once, launcher pro was not responding, and I was given the choice to wait or kill it, when the phone recovered from a "half-freeze" (unrelated?)
Not a setcpu problem, because I have been using the same profiles since I got the phone, but I did play around with the governors to see if that changed anything.
Not a memory issue, because I dont install much, and I regularly manually kill unwanted processes.

Not sure why your phone acts like this and don't know a simple solution. But before tracking down the error, it's mostly and surely faster to install another ROM or just reflash this ROM and only install the apps you want to try - saves you some headaches... Also try to repartition/reformat your sdcard. I too had some issues with lagging system but i was only able to resolve it by flashing another ROM. I don't think it's an hardware related issue though...

Thanks for the response
Just flashed a new ROM. Gonna poke around and see what happens. Will report back.
Whats the best way to repartition an SD? Instead of Gparted of course. I'm not on Linux (my ubuntu installation went bad).
There are definitely thread about this, but before I flashed DF 6.1a (coming from DF 6.0e), I switched my recovery to AmonRa, selected ext2 partition of 0mb (because I had a 256 partition before, and then I wanted a 512mb) and then partitioned it again with a 512mb.
Honestly, it doesn't sound like the best way to do it, but that was what some threads said.
EDIT: Phone seems fine now on GV 1.1 How could a nandroid affect the phone so badly? hrm.

Partitioning with AmonRa's recovery works perfectly fine for me. You just have to set the ext2 partition to the desired size (i use 1024 as recommended on other threads - at least for sense roms). Afterwards upgrade ext2 to etx3 and maybe ext3 to ext4 (i have done this).
I too had to throw away some nandroid backups and start clean. Don't know why. I thought it has something to do with my "experience"...

Evo 4G randomly resets itself

Hey all,
I've been using my HTC EVO 4G for quite some time now (nearly a year), and just recently it started acting up. As the title implies, my phone randomly shuts itself off and starts itself back up-- for reasons I cannot determine. Usually when it does it once, I find that it goes on a rampage and shuts itself off before the phone even starts up. It will continue to reset itself for 3 or 4 times before it starts working properly.
I've honestly no idea what could be wrong with it. When this first started happening, I was running Fresh ROM 4.2 (but I've already been running it for a while-- it couldn't have been the ROM), and the default kernel for Fresh. I decided to boot into recovery for an earlier version of the ROM, but to no avail.
Finally, I decided to get a whole new ROM (am currently running on Synergy) and kernel altogether (currently running on netarchy kernel), but again to no avail.
Of course, I did a complete data wipe upon installing Synergy, so it can't have anything to do with phone's software, can it? I'm assuming it must be something physical; and am seriously considering purchasing a whole new SD card. (About the SD card: whenever I try mounting my EVO as a disk drive, immediately after I select the 'Mount' option, a notification saying 'Preparing SD card' pops up, and fails to ever mount it. This, I believe, is due to the fact that I'm not on a .92 Hboot, but it is nevertheless worth noting.)
Has anyone else ever had this problem? Any help would be greatly appreciated.

Edit: The fact that I can't mount my phone as a disk drive is actually a problem in itself... I need to convert to Hboot .92, but my file system isn't FAT32 (at least, I'm assuming so, since it doesn't load my PB31I.zip IMG in Hboot) and I can't convert it if it doesn't connect to my computer... Guess I'll go back to Fresh.

Does your phone kind of heat up sometimes? Like in the front of the screen? My did and it turned out to be a physical problem. Bad charger port, sounds weird but thats what I was told. You might need to buy another one.

ruben1221 said:
Does your phone kind of heat up sometimes? Like in the front of the screen? My did and it turned out to be a physical problem. Bad charger port, sounds weird but thats what I was told. You might need to buy another one.
Click to expand...
Click to collapse
Yeah, I had originally thought it was an over-heating problem as well. It used to happen most of the time while I was driving-- with the sun hitting the phone directly. However, it's been doing it in-doors with A/C and virtually every other place . I just took notice of it in the car because that's when music was playing.
Ultimately, I might just consider transitioning to the Galaxy SII.
Thanks for reply. <3

I've been having same problem had my evo since day 1 and never any problems up unitl a few months ago.but now i definetly know i need a replacement mine phone gets super hot as well originally thought it was the rom but went back to stock all for nothing because the problem still remained

Is call power cycle the only way to fix it is to get a refurbish phone from sprint they know about it, they will do a test on it and order you another phone with the new 2.3.3 that cant be rooted, is not the sd card it is something on the hardware motherboard

Galaxy Nexus - Reboots when trying to move through screens quickly.

I had a bone stock Verizon Samsung Galaxy Nexus which suddenly began to boot loop last week after receiving a text message.
(1 year warranty is 1 month past)
Upon attempting to do do a factory reset via fastboot - clear everything. start from scratch. I am presented with what seems to be a working phone however if you move through the screens too quickly the phone will reboot.
I have since tried putting several different roms on the phone including flashing back to the stock original all present the same results.
When the phone finally comes up. I wait approximately 10 seconds in between each screen tap otherwise the phone will restart.
does anyone have any insight on this. I have been searching since Saturday night for similar issues/fixes but nobody seems to have mentioned this.
Is there a way to do a hardware test on the phone to see if it is in fact hardware related vs software related?
Thanks in advance for your time and help.
-Nick

focusedonsound said:
I had a bone stock Verizon Samsung Galaxy Nexus which suddenly began to boot loop last week after receiving a text message.
(1 year warranty is 1 month past)
Upon attempting to do do a factory reset via fastboot - clear everything. start from scratch. I am presented with what seems to be a working phone however if you move through the screens too quickly the phone will reboot.
I have since tried putting several different roms on the phone including flashing back to the stock original all present the same results.
When the phone finally comes up. I wait approximately 10 seconds in between each screen tap otherwise the phone will restart.
does anyone have any insight on this. I have been searching since Saturday night for similar issues/fixes but nobody seems to have mentioned this.
Is there a way to do a hardware test on the phone to see if it is in fact hardware related vs software related?
Thanks in advance for your time and help.
-Nick
Click to expand...
Click to collapse
Anyone have any ideas.

focusedonsound said:
Anyone have any ideas.
Click to expand...
Click to collapse
I think it's just an hardware problem.
Something happens when a part of code is executed and the hardware does not respond correctly.
Similar problems happen with desktop computers, a faulty memory module, for example may create a reboot due to the error, or making a driver to crash. These smartphones are little computers...
This is what i think IMHO. I'm a computer technician.
PS. Maybe when you scroll faster the cpu goes at an higher frequency an becomes instable, did you overclocked it in the past? Try to lock the frequency as lower as possible with a custom kernel and verify if the issue appears anyway.
Anyway I'll pay a lot of attention flashing a new kernel or recovery on an instable phone, if it reboots during flash you may brick your device!
I hope this helps.

Thanks for the reply,
This is kind of the theory that I had but I didn't want to make any assumptions. With my computer background I am very familiar and understand how to trouble shoot problems with a computer. However phones area whole new cup of tea.
The phone resided in an otterbox which could have led to overheating and ultimately the processor going bad. I am no so quick to flash a new kernal etc to restrict the frequency.
The thing that I find most odd though is that there have been no similar functionality reports.
-Nick

The slow death of my Note 4

Hello!
Everything was working fine until my phone started acting up about 6 months ago. The screen began to become unresponsive, apps crashed when switching between them and random reboots occurred frequently. I thought back then it had to be software related, so I completed multiple factory resets, and completely removed everything on my phone. It became slightly more usable, but these crashed and random reboots still occurred.
Last week, my phone continued to reboot, but a new problem occurred-it no longer would turn on after the reboot. I tried plugging it into the wall, pressing the volume down + home + power to force bootloader mode, but it wouldn't turn on at all. The fix was I had to remove the entire case, take out the battery and put it back in the phone. After that it would turn on, but only for a few minutes before another random reboot occurred and I had to remove the entire battery again. My phone is now virtually useless as I cant before even the basic functions, calling and texting without it becoming unresponsive or shutting off and not turning on.
I narrowed it down to the eMMC chip. I am almost certain that is corrupt, because during some of the reboots it would fail and throw me into download mode with the error:
mmc0_read_fail
or something along those lines. My last attempt at recovering the phone was to the stock rom PE2 with a PIT file (I had created before I started flashing custom roms). Each time I would attempt to flash with ODIN it would result in a:
mmc0_write_fail
However, I was finally able to get the PIT and PE2 firmware to flash. Now I have a half-working phone that will randomly reboot still and in order to turn it back on, the battery has to be pulled out for a minimum of 15 seconds.
New Issue I just noticed: When the screen turns off when the phone is inactive, it won't turn on again after pressing the power or home buttons. Only solution to this is once again, pull battery and hope I boot into system again.
I am pretty sure there is no fix to this problem on the software side, but let me know if you have a suggestion! Thanks!

Same situation. This thing is a lemon!

Sounds like hardware failure.
Replaced the battery yet? My original didn't last fifteen months before it started shutting the phone down. It's the first thing I think of when someone reports having to pull the battery.
Are you checking battery capacity before the battery pull by plugging in when it shuts down? Mine showed 0%. Before the shutdown, it may have indicated as high as 30%. It gets worse.
You didn't mention capacity when plugged so I thought I'd ask.
Sent from my SM-N910P using Tapatalk

One of my note 4 had same issue. Its a hardware issue. I was able to get the phone working by using a heatgun on the motherboard to try and reflow the solder on the chips. The phone works like brand new after the heatgun but the phone would only work for like 3 or 4 days before crapping out again. Ultimately ended up buying a used motherboard on ebay with a clean esn and its working perfectly again.

My wife's Note 4 started the random reboot thing and screen being unresponsive thing last week. She said it randomly started after installing Snapchat, so she uninstalled it hoping that would fix it. It didnt. I put a new battery in it thinking the original was bad, but still same issues. Then did a factory reset but that didnt work. After a lot of searching I stumbled on to someone who mentioned downloading an app called Wakelock. I did and phone has been running smoothly for several days now.
I also recently did the most recent update hoping that would fix the issue, it didnt but during the install I did get one error of emmc read failure or something like that. May just order a used/new motherboard just in case.

Just be careful when swapping out the motherboard as it essentially is taking apart the whole phone including the removal of the LCD.

LG G3 Keeps shutting down - is it hardware?

Few days ago my phone began to shutdown either immediately or after a short freeze of the system. This happens in many situations, although mostly outside/when I'm on the move (I tried disabling GPS but it didn't help). Usually when I switch it on again it either shutdowns just as the lockscreen appears or doesn't work at all until I remove the battery for at least 10 seconds. The latter sometimes helps and the phone works properly for a couple of hours and the whole thing start over. I tried clearing cache, restoring factory defaults, changing the software completely (Fullmics, LineageOS) but nothing helps. I made sure that this is NOT battery related - I have a spare one and it's all the same.
I'm not sure whether the issue is hardware or software related. Here are my suspicions:
Why it might be a software issue:
- Just before the phone shut down for the first time I noticed that the upper part of the display stopped working - I simply could not pull down the notification bar. I rotated the screen and noticed that the same thing happens to the menu buttons which obviously replaced notification bar in the upper part of the screen. Eventually it turned out that this is not a defect of the screen and that part of the screen simply froze. After reboot it worked normally for a while and then froze again. After changing the software the problem seems to be gone.
- When I'm in recovery mode (TWRP) the phone usually is stable, it shut down only once or twice
Reasons for hardware:
- For a couple of months now the Wi-Fi is not working properly. It disconnects and whenever I try to reestablish the connection it goes into "Saved->Connecting->Saved". Maybe this is just the next step towards the graveyard?
- It's about 6 months since the warranty has expired
Have you experienced this and/or have any idea what's going on?
EDIT: With time it was more and more difficult to turn the phone on and keep it running and right now it's not turning on at all.
EDIT 2: I made it run again. TWRP works perfectly but once I reboot to System it shuts down almost immediately.

Nobody has any idea?

I'd guess it's the battery.
When I bought my G3 in Oct 2015, I had random reboots aswell, nothing helped (turning off mediascan, restore kdz via LGFlashtool 2014 etc.).
So I went ahead and bought another battery (7000mha) from ebay.
Never again suffered from those annoying random reboots
(Inserting the old battery, makes the reboots reappear, so that is postivie proof for the battery thesis).

-Rye- said:
I'd guess it's the battery.
When I bought my G3 in Oct 2015, I had random reboots aswell, nothing helped (turning off mediascan, restore kdz via LGFlashtool 2014 etc.).
So I went ahead and bought another battery (7000mha) from ebay.
Never again suffered from those annoying random reboots
(Inserting the old battery, makes the reboots reappear, so that is postivie proof for the battery thesis).
Click to expand...
Click to collapse
As I wrote above, I have two batteries and the problems exists with both of them.

In that case try this:
https://forum.xda-developers.com/lg-g3/general/g3-hardware-problems-solved-bsod-screen-t3597086
Regarding your battery: You didn't only get "original" batteries ? I have a third party one... All original ones I had so far failed me...