Develop Bugs

[Q] Defy grinds to a halt

Really hoping someone can help me. I have had my Defy for a few months and have always been on a custom SBF but continue to experience problems with the Defy working amazingly for hours and then sometimes I turn the screen on and the Defy is working in some kind of super slow mode and opening anything takes ages, everything does eventually open so it’s not crashed but just going super slow!
I am currently on SBF 3.4.2-177 Nordic but have had the same problem on different SBF’s so either my phone has a hardware issue or its some software I have on my phone, I am currently on Beta 6 of CM7 and have had this issue on other betas of CM7 but have never heard of anyone else with this issue. The phone will sometimes go a whole day without the issue also which is weird. It is not overclocked either. When it goes into what I now call superslow mode I have checked to see what the processor and memory usage are and both are around 60% used not being topped out at all. I have even used StabiltyTest to test the memory and CPU when the problem is occurring and both run through fine.
I really would love to know if anyone else had a similar problem or if they know what is causing it or how I can find out what is causing it without removing every bit of software I use. The only piece of software I use regularly that runs in the background is Juicedefender so I am going to remove this now and see what happens over a few days.
Any help would be amazing
Many Thanks
Bob

Did you install the latest patch for the auto-brightness issue? or Did you turn off the auto-brightness?

Thanks for the fast reply I have already installed the latest patch for auto-brightness issue but still have the problem

Was the phone slow in the stock ROM? I mean that's really wired that the problem appears on each SBF

Hi mys_721x, I only had the stock ROM for a matter of days when I first had the phone so really cant remember but I am thinking I may have to go back to see if I do still have problems if no one else can suggest anything else. Cheers

I have this same problem. Only fix seems to be a reboot whenever it happens

bobdigby said:
Hi mys_721x, I only had the stock ROM for a matter of days when I first had the phone so really cant remember but I am thinking I may have to go back to see if I do still have problems if no one else can suggest anything else. Cheers
Click to expand...
Click to collapse
Same here, my phone suddenly becomes sluggish and unusable. Yesterday it was stuck on 100% cpu usage, I entered the task manager to see what was wrong and there wasn't any application that was using the cpu.
Only solution is to reboot everyday.

Glad to see I am not the only one, yea a reboot does the job sometimes it can be twice a day sometimes I don't see it for a few days, do you guys have juice defender installed by any chance as thats the only real program which stays running in my background which is extra to the roms I have used, cheers for your input, lets hope we can figure out whats going on.
Bob
Sent from my MB525 using XDA Premium App

I had it to in the past. When i tried to lock the phone it took long time and it wouldn't unlock for a wile 1-2min what is verry long if your waiting and afterwards scrolling was lame.
Don't know what I did, but it's gone now. Now only when out of memory(dhuu!)
I think I wiped it cleen, went to a 2.2 and didn't have it again, now on CM.
Do you see in spare parts any apps using mutch cpu?

Weirdest thing that happens to me..
Every hour/day the phone loads up some applications prepared to start when I turn on the phone..
That means that if I close say, tigertext or Skype, the following day, without turning off the phone, hey are running again.. wtf?
EDIT: A way of checking what's using the CPU, if you're on Froyo, is check the application manager to check for services CPU usage

Yea I have no idea what is causing it but little to no cpu usage when it happens, when I lock on cm7 the tv effect for screen off is super slow motion its really strange, did a clean wipe yesterday and did its first slow down today just before post, cheers
Sent from my MB525 using XDA Premium App

Anyone have any luck with this? Mine just seems to be getting worse and worse on CM7.
Update: I've opened a issue for this on Github. You can go there to post new information / symptoms so that hopefully it can be fixed: https://github.com/Quarx2k/android_device_motorola_umts_jordan/issues/204

Hi dasbin,
Since uninstalling Juicedefender from my phone I have not had this issue once, it has now been 3 days which is probably a record for me so I would say that it was causing me the issue, do you have juicedefender installed? I am now using green power it is much better so far.
Cheers

[Q] Device becomes unresponsive after several minutes of use.

Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN

The problem is coming from the magnetometer. I have the same issue, please check this thread: http://forum.xda-developers.com/showthread.php?t=1394264
The only workaround I found is to disable screen rotation and do a couple of restarts (not switch off). Of course, no compass in the end, but at least I can use the phone.

KaRsKiN said:
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
Click to expand...
Click to collapse
It is possible that your battery could be failing. See if att has one they will let you exchange.
If its not the battery then it could be a hardware issue. Just send it in for warranty if that is the case. You should still be covered as the phone is not yet a year old.
Sent from my Inspire 4G using xda premium

Gizmoe said:
It is possible that your battery could be failing. See if att has one they will let you exchange.
Click to expand...
Click to collapse
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.

Flussen said:
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Click to expand...
Click to collapse
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium

Gizmoe said:
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Thanks for your help! My dad has the same device as me so I'll try swapping out the battery to see if this solves the problem. If not I'll try calling HTC to arrange a repair.

Any news? Was it the battery issue?

Bluetooth not turning off

Hi guys
I've been getting fairly decent battery life, however am now connecting my phone to the car daily via bluetooth.
I've noticed some battery drain and after checking the built in battery stats and also better battery stats app, my Bluetooth is not turning off when I'm selecting it.
IE, connected on the drive to work, get to work, disconnected then turned off, but showing as constantly on.
Any ideas what could cause this?
Sent from my HTC One X using xda app-developers app

I have noticed the same thing when viewing battery stats although I never use bluetooth and it's always off.
Sent from my HTC One X using xda premium

Any updates or anyone else having the same problem?
I also noticed it just a minute ago. gsam monitor tells that bt was on for 6hrs+ which is the exact same time with phone radio.
Earlier this week connected to my boss' car radio for bt aux, this is the first and last time I used bt. Switched it on&off from settings, nothing changed.
SH26CW, running 4.0.4
Might be useful to give the serial no's since it is useful information about the production site and date.
Sent from my HOX via xdapp

thekillingroad said:
I also noticed it just a minute ago. gsam monitor tells that bt was on for 6hrs+ which is the exact same time with phone radio.
Sent from my HOX via xdapp
Click to expand...
Click to collapse
Same issue here, and same Android version. GSam always reports the same Bluetooth on time as the time unplugged, ie. it's saying that BT has been on all the time, while it's clearly off. I've tried different ways to switch off BT (using widget, using settings, going into Airplane mode and back) but to no avail.
Part of me is suspecting that GSam might be reading the wrong value and falsely reporting it as Bluetooth. But perhaps someone with a different battery monitoring app could check on this and confirm?

It is a bug, to solve it you will need to restart your phone.
This is the only way I find to solve this on stock 2.17/Android 4.0.4.
This bug is caused by turning your Bluetooth on and off.

I faced the same problem? But does that use battery? Actually.the Bluetooth is off.
Sent from my HTC One X using xda app-developers app

neuTrue said:
It is a bug, to solve it you will need to restart your phone.
This is the only way I find to solve this on stock 2.17/Android 4.0.4.
This bug is caused by turning your Bluetooth on and off.
Click to expand...
Click to collapse
Hmm, user fault then hheheheueh
the strange thing is, it does not consume battery at all. ok it's not connected to any device but I would think it would consume more than just %1.
may be non-discoverable makes it use less. not broadcasting anything.

neuTrue said:
It is a bug, to solve it you will need to restart your phone.
This is the only way I find to solve this on stock 2.17/Android 4.0.4.
This bug is caused by turning your Bluetooth on and off.
Click to expand...
Click to collapse
A restart sometimes fix the problem but not always. Today I had bluetooth turned off then after restarting by four hours my device reports that bluetooth has been on for 4 hours even though I didn't turn it on and it shows that it's off.
Sent from my HTC One X using xda premium

Glad I'm not the only one
I do find a reboot fixes it, but I don't want to have to reboot my phone every time I get out the car.
I'll get my serial number when I'm home and see if its the same
Sent from my Nexus 7 using xda app-developers app

I'm now having a chat with HTC live support about JB update and also asked the question about BT off issue.
He said, please follow the following steps.. Waiting for what he'll say..
So he suggested booting in safe mode, going to applications? >> manage, uncheck.. ? I'm not familiar with safe mode so I cannot surely say what he is talking about.
Has anyone tried this? Did it work?
So he sad that this will solve if an application is triggering the problem, but I haven't used any applications that use BT.
So, the next suggestion is factory reset, bullsh*t. sorry guys =)
useless post may be, but confirms that HTC official support has no fixing for this.

thekillingroad said:
Hmm, user fault then hheheheueh
the strange thing is, it does not consume battery at all. ok it's not connected to any device but I would think it would consume more than just %1.
may be non-discoverable makes it use less. not broadcasting anything.
Click to expand...
Click to collapse
Hahaha, that's funny and more towards Apple ideology.
Bluetooth was designed to be efficient. But, if its running then it consuming energy ,and that's something I don't like.
I already checked logcat/kmsg ,but nothing about this Bluetooth issue.
I didn't see anyone on JB came to complain about this, let's see what the offical JB has to offer.
hatemk said:
A restart sometimes fix the problem but not always. Today I had bluetooth turned off then after restarting by four hours my device reports that bluetooth has been on for 4 hours even though I didn't turn it on and it shows that it's off.
Click to expand...
Click to collapse
Try to disable "fastboot", and give it a try.
I am afraid nothings more can be done on stock, other option is to wait for JB and hope it already fixed.
thekillingroad said:
I'm now having a chat with HTC live support about JB update and also asked the question about BT off issue.
He said, please follow the following steps.. Waiting for what he'll say..
So he suggested booting in safe mode, going to applications? >> manage, uncheck.. ? I'm not familiar with safe mode so I cannot surely say what he is talking about.
Has anyone tried this? Did it work?
So he sad that this will solve if an application is triggering the problem, but I haven't used any applications that use BT.
So, the next suggestion is factory reset, bullsh*t. sorry guys =)
useless post may be, but confirms that HTC official support has no fixing for this.
Click to expand...
Click to collapse
Safe mode is a mode in Android, that will will disable all the 3rd party installed apps. Similar to safe mode in Windows. After your turned on your phone, just press on the volume key and it will get you there.
Beside that, I never trust customer support, and I never had a good experience with any of them.
The only good thing is about companies offering customer support, is they add job opportunities into the economy.

This problem just crept up on me. I noticed the battery was lower than normal, I checked BBS and it seems like BT never turned off. A reset would solve the problem until I turn BT back on again.
Does anyone know if this has been fixed with 4.1?

sefuwl said:
Does anyone know if this has been fixed with 4.1?
Click to expand...
Click to collapse
It seems so, at least on my One X G Sam is now reporting the correct BT on-time, whereas pre-JB it was continually on, clock ticking even after turning it off.
Sent from my HTC One X using Tapatalk 2

bluetooth
no probs here:good:

[Q] Galaxy Nexus Sleep of Death

Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
 The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
 The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
 The problem seems to be irrelevant to the Apps installed.
 The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
 I manually reboot my phone at most every two days.
Solutions tried, but don’t work
 Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
 Turning off the auto-brightness control, as suggested by some post on the Internet.

Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app

Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.

Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.

Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?

Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...

eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.

Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.

I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL

I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.

NVM
Screen still goes dead.
Anyone find an actual fix to this?

isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)

Random reboot - OP3 6.0.1 stock

Hi,
I have a OnePlus 3 which is about 7 months old now. I'm running stock 6.0.1 (OOS 3.2.7) with Xposed. ElementalX kernel and TWRP recovery (if that matters) ... I use Kernel Adiutor for a few misc tweaks (vibrator, LED, hostname) and AKT Profiles is set to Fusion Conservative - which limits GPU as well. I have been using various Xposed modules without any issue until the following happened.
I had installed Parallel Space - an app which allows dual WhatsApp capability. I started experiencing random soft reboots and shutdowns. So I uninstalled it. Then I cleared cache and ART cache. I also uninstalled a few apps that I had installed in the past month.
I am still experiencing reboots and I cannot pinpoint the cause. The reboots/shutdowns occur when the screen is off. Always when the screen is off.
I'm bad at reading logs, so can't figure out from the logcat either.
Anyone who can help me out, will be greatly appreciated! I will provide all logs as necessary.
[EDIT] Solution: Do not let any app make use of the proximity sensor to manipulate the screen. For example, apps which switch off the screen when flipped might be the culprit.

Do you use Magisk? And if, what modules?
Had random reboots, too, and found out, that Magisk+some Modules were culprit.
Just provide logs, maybe someone sees something

cl0g said:
Do you use Magisk? And if, what modules?
Had random reboots, too, and found out, that Magisk+some Modules were culprit.
Just provide logs, maybe someone sees something
Click to expand...
Click to collapse
Nope, no Magisk. Only Xposed.

Providing logs from logcat. Will provide anything else if required.

A few more logs containing fatal errors.

I thought the problem was solved by uninstalling this app called "Pixoff", but no, it still persists. Also, the LED is glowing orange, without any notification pending. During screen on as well as off.

Can you please flash stock ROM and check once if the same problem persists?

hrishikeshgramani said:
Can you please flash stock ROM and check once if the same problem persists?
Click to expand...
Click to collapse
That is what I'll have to do if changing settings or regular fixes don't work... But I don't want to jump to it right now because there's a lot of tweaks I'm running and they will be destroyed.
Also, it was running perfectly until last week. I have uninstalled all apps that I got in the last month. Cleared ART cache and normal cache. Haven't restored to factory settings yet.
I'm experimenting with disabling Xposed modules one by one, although I don't think it's a module problem - because I've had them since eternity.
What I have concluded is - I downloaded a rogue app from the Play Store which has left it's data and that is the cause of reboots... I might be wrong though.
Hence, I would really appreciate if someone would go through the logs and figure it out.

I think better logs would be ramoops/last_kmsg.
You can find it at /sys/fs/pstore/console-ramoops
post this file after having a random reboot.

cl0g said:
I think better logs would be ramoops/last_kmsg.
You can find it at /sys/fs/pstore/console-ramoops
post this file after having a random reboot.
Click to expand...
Click to collapse
Will do that next time, thanks!

Okay, so I figured this out. Proximity sensor is having issues. I had enabled "Proximity wake" in GravityBox and that was causing problems. Disabled it and Everything was fine as ever.
To verify that proximity sensor was at fault, I tried Pixoff's flip to Black screen feature - it uses the proximity sensor to figure whether device is in pocket or flipped... And yes, phone rebooted there too.
Phone is running fine as long as the sensor is used only during calls (to switch screen off)
But what I cannot understand is why this is happening in the first place! I mean, proximity sensors are supposed to be used in this manner only, right?
Nevertheless, if anyone wants to help, they are welcome. Otherwise my issue is solved.