Develop Bugs

[Q] Malfunctioning Device? Internal Damage?

Well, to sum things up, my phone has never been so slow and laggy ever since flashing Faux's ultimate kernel (v0.0.6u). (Not blaming anyone other than myself, just sayin)... Anyway, I have the feeling something internal went horribly wrong. Seeing that no other kernel other than Faux's ultimate had GPU turbo boost @ 320/220Mhz, I thought it would be nice to try it out with BeastMod 4.2. After using OC Daemon to set my CPU gov to ONDEMAND and stock clock speeds, I did the usual and tested the rom throughout the day. Battery live was insanely awful. The phone seemed to draining at a rate comparable to using YouTube on 4G, EVEN WHEN THE SCREEN WAS OFF!. Oh, and it got pretty warm, not hot, but noticeably warmer than usual. Knowing I would not be able to flash a new rom/kernel till later that day, I simply shut my phone off for the time being. When I got home, I discovered the problem. Even after switching back to... let's say Bullet w/ Juggernaut, I noticed that scrolling through anything, playing a game, running a benchmark (especially this one), caused the phone to slow down, hiccup, pause, lag, whatever you want to call it. In Quadrant, the fps for the 2d test was hitting high 20's before, and now, it jumps about the teens goes as low as 8fps. Score: 1801...2130... Am I running a dual core? Not anymore it seems... Feels like the second I touch my phone, thermal protection kicks in or something else is choking it and preventing my phone from being smooth like it used to be. Even tried underclocking to sensation speeds (1188). No help at all. Still craps out on me. I'm beginning to think I fried something inside. Broken Adreno? Hope not... Any ideas?
Note: Yes, I followed all ROM and kernel flashing procedures. I may be a noob (literally), but I do know how to flash properly.

Maybe try a factory reset and Odin back to stock to start from scratch.
Sent from my SGH-T989 using xda premium

Exodian said:
Maybe try a factory reset and Odin back to stock to start from scratch.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I'll give it a shot. Hoping Christmas Eve is lucky this year.

[Q] Desire overheating - Need to deroot?

Hey,
I have had an HTC Desire for about 18 months now and I rooted it about 6 months ago with a CyanogenMod ROM. It has developed major overheating issue and continuously shut downs when it gets too hot or run a processor-intensive application. I have heard that de-rooting the device could help solve these issues and am ignorant to the steps involved as I am unable to connect my phone via HTC sync to install a factory ROM on it.
I have read several topics and have come up blank. Maybe I haven't looked hard enough but any help and information anyone could provide me with would be much appreciated.
Thanks.

have you overclocked your phone ? (can you check your cpu settings )
maybe your cpu settings are to high , high cpu set may cause overheating and instability , have you tried other cm roms ? i find if i overclock my phone it warms up faster etc and becomes unstable

There are 2 things here.
Is it rebooting at intense activity and NOT overheating? If so, Overclocked at too high a frequency for your CPU to take -Take the overclocking down a Notch.
Is it rebooting at intense activity and IS overheating? If so, most likely hardware fault (PVT1 Faulty Motherboard most likely) - Return to stock and send to HTC for repair.
Overclocking itself should not cause overheating as most kernels are UNDERvolted, meaning even at overclocked frequencies, they are not using more power, meaning they are not generating more heat. An exception to this is ManU kernels, where it uses 1350mA at the high end, where stock kernels use 1300

rootSU said:
There are 2 things here.
Is it rebooting at intense activity and NOT overheating? If so, Overclocked at too high a frequency for your CPU to take -Take the overclocking down a Notch.
Is it rebooting at intense activity and IS overheating? If so, most likely hardware fault (PVT1 Faulty Motherboard most likely) - Return to stock and send to HTC for repair.
Overclocking itself should not cause overheating as most kernels are UNDERvolted, meaning even at overclocked frequencies, they are not using more power, meaning they are not generating more heat. An exception to this is ManU kernels, where it uses 1350mA at the high end, where stock kernels use 1300
Click to expand...
Click to collapse
Most likely a motherboard fault. I encountered the same thing.

seriously? ****... i've dropped mine once so they won't repair the damage probably... I'm having a similar problem.. though after i've flashed a recovery image, there's no problem!

I had mine repaired...3 times. Was constantly overheating and shutting down. Was a major let down when was using it as a car navigation. 10mins and it goes off just in front of a crossroad So after all it just turned off and..that's it. So my first repair was made in official Czech centre - got it back after a few weeks and it did work for a whole day..Then I plugged it into a wall charger, opened a game and just noticed the temp rising up to 43C..couldn't do anything, the next moment it was dead. Sent to repairs, got back after..a week. It didn't even turn on (sic!), so the guys at UK repair centre didn't even test it. But after another trial it's all good. I've rooted it, installed MIUI and just today S-OFF'ed it and flashed a custom HBOOT and now have a "BONUS" 130 megs. That's my story.

I've had similar problems and from what I read it is a hardware issue related to the motherboard that they will fix if your under warantee but programs like angry birds and navigation make it happen every time I use them with most roms. Some roms are heavier and more prone to reboots the roms I experience the least overheating reboots with are miui and oxygen but I love sense so just use a sense Rom and don't use games and navigation. A bit cr*?$%p I know.
Sent from my HTC Desire using Tapatalk

Ok wel I'm on MIUI now, let's see what happens. Use it now for a day and have been safe still
Edit: aaaaaannnnnnnndddd it's gone....
This is going to be fun now that outside temperatures are rising...

What were you doing when it overheated, playing games or just watching it?
Sent from my HTC Desire using Tapatalk

DutchDisturbed said:
Ok wel I'm on MIUI now, let's see what happens. Use it now for a day and have been safe still
Edit: aaaaaannnnnnnndddd it's gone....
This is going to be fun now that outside temperatures are rising...
Click to expand...
Click to collapse
you are soo right lol ) if i use the phone outside where are @ +2°C the damn phone works like new... well, when i go inside, the whole story changes... the phone start rebooting and soo on... soo yeah.. it will be interesting to use this phone in the spring

It eventually crashed and never came back! Tears were cried, but I'm still happy with the nexus 4 followup.
Verstuurd vanaf mijn Nexus 4 met Tapatalk

[Q] Defy+ Temporary bricking due to overheating?

Yeah, got a major issue: My Defy+ is overheating and I usually end up with a blocked phone, which ends up being useless for about 4-5 hours. And it's becoming more often.
I have 2.3.4 on it, but I seriously doubt 2.3.6 solves this issue.
Any tips?

Deformat said:
Any tips?
Click to expand...
Click to collapse
Try custom ROM's and DO NOT flash 2.3.6 full sbf as it's quite buggy and you'll be stuck with it.

You could also try to undervolt the CPU. In what conditions do you get an overheated phone?

vap_66 said:
You could also try to undervolt the CPU. In what conditions do you get an overheated phone?
Click to expand...
Click to collapse
How could I do that?
Also, I get it for no reason whatsoever. It gets overheated and that's it. I left it to cool about 4 God damn hours, and yet when I open it it works a bit, then it gets stuck. It's as if the memory isn't well processed.
To give ya an example, I left it over night and even charged it. Everything went fine.Then, got to school, got a break, wanted to listen to a song. Fine, listened to a song. A guy wanted to waste some time on Opera Mini with his Ikariam game. Fine, let him waste that 1 tab and browse online.
But then, when he gave it to me it was stuck.
Wait a lot of time to stop it via Android's button, did it eventually. Left it to cool 2 hours, tried again. Again, after less than 3 minutes of usage (wanted to share a file via bluetooth, but got to the folder only) it got stuck again. This time it was pointless, 30 minutes later I wasn't able to stop it so I took the battery off.
I kinda don't know if I should change it or still have faith in it.
Right now stuff seems worse. Sometimes it reboots itself, but that doesn't help with anything IMO.
BTW, would the 1% battery patch help? Might put that 720p functionality in there as well.

As Auris said, try flashing a custom ROM (CM7.2 is a good choice, stable and fast enough). For undervolting (if you are on a stock ROM only - because CM7 has a built-in CPU manager, accessible from the bootmenu) ), install SetVsel from the Play Store. Like PC overclocking/undervolting, be careful about the values you choose. You'll find a thread in the General section about SetVsel values.
If these ideas don't help you solve your problem, I think it might be hardware related.
Trimis de pe Defy CM9

My defy+ gets really hot on just about everything except stock! Undervolting didn't help, nor underclocking. Putting it in the fridge temporarily helped, but when I started using it again the temp climbed again!
What should I do? :-/
Sent from my Defy+ using Tapatalk 2 Beta

Well, since you flashed custom ROMs (unlike the OP), how about the baseband? I remember that when I flashed CM7 for the first time I didn't get 3G signal and the phone was overheating because the signal was too poor for the baseband that I used. Switched between a few and finally managed to get one with good signal and 2G/3G/3.5G working fine.

I never use 3G, so I've never bothered changing it. By the way... what are the differences between basebands with the same frequencies?
Could flashing a different kernel solve it?
Sent from my Defy+ using Tapatalk 2 Beta

Well, there are different regions - I don't know the technical details, but maybe some basebands work better with certain network operators. It's a trial&error method, you could choose one that works better or one that performs worse.
Regarding the kernel: I have no idea about the heat dissipation, but from what I've read there is a GB kernel that supposedly has better battery life. Ask Auris, he uses it (it's the kernel by walter79).

Okay, seems the issue solved itself, since now it works perfectly :|
I didn't play a game, which was kinda retarded: low quality, a simple Android game, and playing Temple Run/Angry Birds/ Angry Birds Space didn't give you me any issue.
I don't get it.

[FIX] Pops and crackles in headphone output.

Hey everyone, just thought I would let it be known that (at least on my phone) overclocking past 1.8GHz causes horrible clicks and pops when listening through the headphone jack. I am using the Rogers Stock ROM with the latest KT747 kernel, and the issue appears when clocked to 1.89GHz, even though the rest of the phone runs stable. Took me a while to track down the problem!
I was hoping people with other kernels/roms/configurations could weigh in to see if this is an isolated or a widespread issue. For the time being I have just decided to overclock manually when it is needed.
EDIT: It appears after more testing that it was the kernel itself. Switching to stock kernel fixed the problem.

MatinatorX said:
Hey everyone, just thought I would let it be known that (at least on my phone) overclocking past 1.8GHz causes horrible clicks and pops when listening through the headphone jack. I am using the Rogers Stock ROM with the latest KT747 kernel, and the issue appears when clocked to 1.89GHz, even though the rest of the phone runs stable. Took me a while to track down the problem!
I was hoping people with other kernels/roms/configurations could weigh in to see if this is an isolated or a widespread issue. For the time being I have just decided to overclock manually when it is needed.
Click to expand...
Click to collapse
isn't your phone blazing hot to the hand?

Death&co said:
isn't your phone blazing hot to the hand?
Click to expand...
Click to collapse
Suprisingly the temperature increase is hardly noticeable. I tested while playing N. O. V. A. 3 and a few other games. My One XL got burning hot while overclocked to 1.7GHz, even though it's the same chip, which I find strange.

I had this probelm as well on my SGS3, ended up exchanging my phone for another reason and the new phone doesnt do it anymore.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

The galaxy s3 explodes with stock temps, I would be afraid to oc to 1.9GHz Oh, and I would edit the title from [FIX] it's kind of misleading since there isn't a fix here.

MatinatorX said:
For the time being I have just decided to overclock manually when it is needed.
Click to expand...
Click to collapse
I'm still trying to figure out when you would "need" to overclock.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

americasteam said:
I'm still trying to figure out when you would "need" to overclock.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I'm a power user. I do just about everything with my phone, including lots of gaming with emulators. Perhaps I got a higher than normal quality chunk of silicon, but the phone didn't overheat at all, even when overclocked. The only time it got noticeably warm was while overclocked, gaming and charging all at once.
To those having this problem, it appears it wasn't related to overclocking after all, as the issue appeared a day later on stock frequencies. Changing back to a stock kernel fixed the problem.
In the end I sold it and bought an international SGS3 from eBay. I don't care for LTE, but the Wolfson DAC and Mali-400 GPU appeal to my usage case nicely.

MatinatorX said:
Perhaps I got a higher than normal quality chunk of silicon, but the phone didn't overheat at all, even when overclocked. The only time it got noticeably warm was while overclocked, gaming and charging all at once./QUOTE]
Seeing posts like this just make me cry inside...from the day I first got my phone and activated it, I have been having overheating problems. No one would take my device back so after my 30 day "return" period or whatever, I decided to root my phone to underclock/undervolt to solve my problem....but even know, my phone gets warm by just using stock Browser after a fresh install (not Chrome or anything else) WITH underclocking.
Click to expand...
Click to collapse

Puzzling Random Reboot Issue

I've been trying to figure this out for months and have had no luck so I wanted to see if any of you had any recommendations.
I used to run Sense roms like the stock one and the sense 2.1 mctwist rom and they had no issues.
When CM9 came out, I decided to switch over to that. It functioned fine except I would get random reboots about 1-2 times each day. Tried clean installs, etc but nothing work.
Then CM10 came out and I upgraded. Once again, it works excellent except I still get random reboots once or twice a day.
And just recently I tried the AOKP Jelly Bean ROM, hoping it was a CM issue, but I also got the random reboots on AOKP.
What could be causing this? Occasionally I can go through the day without a reboot, but 9 out of 10 times, I get at least one reboot each day. Sometimes it happens while it's in my pocket and I don't even notice for a few hours.
These reboots are basically the phone starts showing the boot animation, but with a very dim screen and it just stays stuck with the spinning boot animation. It won't reboot until I pull the battery or do the 3 button reset.
Any advice? Should I try a different radio or...? I don't even know. I love JB so much so I'd hate to have to go back to a sense rom, but I can't take these reboots anymore.
Thanks

jpzsports said:
I've been trying to figure this out for months and have had no luck so I wanted to see if any of you had any recommendations.
I used to run Sense roms like the stock one and the sense 2.1 mctwist rom and they had no issues.
When CM9 came out, I decided to switch over to that. It functioned fine except I would get random reboots about 1-2 times each day. Tried clean installs, etc but nothing work.
Then CM10 came out and I upgraded. Once again, it works excellent except I still get random reboots once or twice a day.
And just recently I tried the AOKP Jelly Bean ROM, hoping it was a CM issue, but I also got the random reboots on AOKP.
What could be causing this? Occasionally I can go through the day without a reboot, but 9 out of 10 times, I get at least one reboot each day. Sometimes it happens while it's in my pocket and I don't even notice for a few hours.
These reboots are basically the phone starts showing the boot animation, but with a very dim screen and it just stays stuck with the spinning boot animation. It won't reboot until I pull the battery or do the 3 button reset.
Any advice? Should I try a different radio or...? I don't even know. I love JB so much so I'd hate to have to go back to a sense rom, but I can't take these reboots anymore.
Thanks
Click to expand...
Click to collapse
It could be an app causing it, or overheating. Do you over/under clock/volt? You may want to try underclocking a little, or raising the voltage a little. You may also want to check the system and kernel logs to see if they reveal the issue.

cmlusco said:
It could be an app causing it, or overheating. Do you over/under clock/volt? You may want to try underclocking a little, or raising the voltage a little. You may also want to check the system and kernel logs to see if they reveal the issue.
Click to expand...
Click to collapse
I used to overclock on my sense roms with no issue. But on CM10 I just have it set to stock speeds with no overclocking or adjusting the voltage. Could my phone be getting old and so even stock speed is causing overheating? My phone doesn't feel noticeably hot, unless it gets stuck in one of these reboots. Then it feels rather warm. What would you recommend I change my voltage to?
And I tried doing logs but they get wiped when I restart
EDIT: Odd thing I just discovered. I borrowed my friend's seido extended battery for the dinc and popped it in my phone. After charging it up for a bit, I used the phone and within 10 minutes it started acting weird and rebooted. And after restarting, it rebooted again a few minutes later. So basically it was even worse. Any correlation here? Does the extended battery = more heat = that's why my phone is rebooting?

It's hard to even guess unless you can get a log. If you give one of the stock based ROMs another trial for a few days, and the phone does not reboot, then it is safe to say it is not hardware. I'd start by at least ruling out the hardware possibility.
Do not use Titanium or some other app to restore any sort of data from one ROM to another. That often seems to cause a lot of people problems.
If your phone isn't that hot, I agree that heat isn't likely the problem. Mine absolutely roasts while navigating (while charging, screen on, gps and 3g antennas on, music playing, overclocked, weak original stock battery, otterbox case so it can't breathe, etc.) and it doesn't ever reboot from heat.
Everyone uses their phones differently. So what may be stable for one person might not be for others. I've come to the conclusion that there is only one person who can determine if a ROM is stable... that is the one person who uses it everyday. Just because some other people are using a ROM and getting good results, it doesn't mean that you ever will (even with you wiping/flashing/installing apps by the book).
CM9, CM10, or any and all ICS and JB roms are going to have things that aren't working right for some time still. It's just the nature of the beast. App compatibility, especially, is just one of those things. It's a testament to how good those awesome devs are that anything works on our Dinc running JB and ICS.
I never ran the ICS and JB ports for long (in fact only very short periods of time) because my problems far outweighed the benefits. There is no shame in GB working better for you. I run a variant of CM7 (which is gingerbread)... it is definitely different than stock-sense. Then I use alternate launchers (Go launcher is my favorite) to change it up even more. You can do so much customization that isn't dependent on the ROM. Then I can use something like ROM TOOLBOX PRO for even more customization.
Software is not fashion. What actually works never goes out of style (despite what the hipster kids on xda might be saying ...get off my lawn... grumble...)

jpzsports said:
I used to overclock on my sense roms with no issue. But on CM10 I just have it set to stock speeds with no overclocking or adjusting the voltage. Could my phone be getting old and so even stock speed is causing overheating? My phone doesn't feel noticeably hot, unless it gets stuck in one of these reboots. Then it feels rather warm. What would you recommend I change my voltage to?
And I tried doing logs but they get wiped when I restart
Click to expand...
Click to collapse
I would use incredicontrol and raise all max voltages by 25 or one push of the plus button. Sometimes as phones get older the processors get worn , and have issues with not enough power or even with the stock max frequencie of 998mhz. If raising the max voltage dosent help, i would underclock down from max 998.

Thank you both for the replies. I really appreciate it. I'll try overvolting and see how it goes tomorrow. If I still get reboots, I'll try running a stock rom for a few days and see how it performs.

jpzsports said:
Thank you both for the replies. I really appreciate it. I'll try overvolting and see how it goes tomorrow. If I still get reboots, I'll try running a stock rom for a few days and see how it performs.
Click to expand...
Click to collapse
Pardon me harping on my pet issue, but my phone does that if I underclock the CPU minimum to 128MHz. If I leave it at 245 I can go for days on end (I've seen uptimes of over 200 hours). For whatever that's worth...

musical_chairs said:
Pardon me harping on my pet issue, but my phone does that if I underclock the CPU minimum to 128MHz. If I leave it at 245 I can go for days on end (I've seen uptimes of over 200 hours). For whatever that's worth...
Click to expand...
Click to collapse
That is true, if i go down to 128 i have screen on freezing issues, and random reboots.

EDIT: Odd thing I just discovered. I borrowed my friend's seido extended battery for the dinc and popped it in my phone. After charging it up for a bit, I used the phone and within 10 minutes it started acting weird and rebooted. And after restarting, it rebooted again a few minutes later. So basically it was even worse. Any correlation here? Does the extended battery = more heat = that's why my phone is rebooting?
Click to expand...
Click to collapse
This is certainly a clue... but I don't know what it means...
I would not think the the extended battery would produce more heat. Since both batteries should be discharging at the same rates the heat output should be the same (just that the bigger one would take longer since it has more reserve). I've ran across stories of people who had phones that went completely wonky when they tried swapping batteries or getting a new one. I really don't know anything about it, I'm still on my stock battery.
It certainly couldn't hurt to try wiping your battery stats in clockwork. There is apparently some magic methodology to do it "correctly". I don't know about that either... here is a thread.
http://forum.xda-developers.com/showthread.php?t=1359395

Well just as an update, I tried the overvolting and clearing the battery stats but still got the reboots. I installed one of the Stock Sense ROMs and it's been running great with no reboots. Apparently my phone just doesn't like non-Sense ROMs for some reason. Oh well. At least I have a working phone. Pretty amazing how fast the stock rom runs!

Well, I guess it's good to hear the hardware is ok.
You still could try out the CM10s (or other JB roms) by starting off without installing your apps (if you can live without them). App compatibility might be your problem. Let it run for a while with no additional apps added. Then, add them back slowly (one or two a day or every couple of days) from the market only. If the reboots start up later on... you will probably recognize the one that is the source of trouble.
Of course you still have plenty of options in the gingerbread family to choose from. If you've never tried out some GB AOSP/CM roms, that would be worth a try. You've got stock roms, stock roms with sense removed, and the whole variety of AOSP/CM7 (official and unofficial) to choose from. Launchers...themes... mods... etc... all kinds of ways to change from whatever you start with. The only GB roms that I ever had problems with were the official "stable" CM7.0 and CM7.1 ROMs. I've been running one unofficial CM7 build (about 99.99% of the time...except to test drive newer stuff) for almost a year. Its been the best thing that's ever happened to my phone.