Related
Hi Friends,
I am currently using Sebastian's Runnymede_AIO_V6.0.4.1_Special_Edition ROM on my HTC Desire.
Sometimes without any reason suddenly my phone does not respond.
When i click on power button, it will not respond, it gets completely frozen.
The only solution is to remove the battery and restart it again.
This is happening since quite sometime and very annoying I wont even realize it got frozen until i check it manually.
Any one faced this problem?
Any ideas how to fix this?
Pls help
Desire acting strange
hi
I'm having the same problems with the same rom. somtimes it works fine for days then it have a fit maby 3 ore 4 times on the same day.
if anyone have any help to offer i would be very greatfull.
I haven't used AIO but I've been here long enough to know that most users of that ROM have that issue and I don't think there is any other workaround than to use another rom.
reds971 said:
Hi Friends,
I am currently using Sebastian's Runnymede_AIO_V6.0.4.1_Special_Edition ROM on my HTC Desire.
Sometimes without any reason suddenly my phone does not respond.
When i click on power button, it will not respond, it gets completely frozen.
The only solution is to remove the battery and restart it again.
This is happening since quite sometime and very annoying I wont even realize it got frozen until i check it manually.
Any one faced this problem?
Any ideas how to fix this?
Pls help
Click to expand...
Click to collapse
Your hboot version? ROM version? Which data script have you installed? There might be a problem with that.
Sent from my HTC Desire using Tapatalk
Blank Unresponsive Screen after Bluetooth
Hi
I'm using CM7.1.0-Desire and the latest Radio 5.17.05.23
I've found if I use the phone as a Bluetooth music player via my car's Stereo, the phone just goes blank after a time.
The music still plays through the car stereo though, (for at least a song) - I don't know how the streaming works, if the whole song is copied in advance or what.
I have to take the battery out to get the phone to respond to any button presses.
I had this problem on the older Radio 5.11.05.27, so upgraded and still have the issue.
Are there some logs I can look for?
reds971 said:
Hi Friends,
I am currently using Sebastian's Runnymede_AIO_V6.0.4.1_Special_Edition ROM on my HTC Desire.
Sometimes without any reason suddenly my phone does not respond.
When i click on power button, it will not respond, it gets completely frozen.
The only solution is to remove the battery and restart it again.
This is happening since quite sometime and very annoying I wont even realize it got frozen until i check it manually.
Any one faced this problem?
Any ideas how to fix this?
Pls help
Click to expand...
Click to collapse
It looks a lot like this. No solution has been found yet, but for me installing another sense 3.5 ROM (RSK Team (now known as Runny Rom)) has helped.
Coempi said:
Your hboot version? ROM version? Which data script have you installed? There might be a problem with that.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Hi, here are my stats
Rom is Runnymede AIO V 6.0.4.1
Hboot is 0.93.0001
Radio 32.56.00.32u_5.17.05.23
Kernel version is 2.6.35.10
Build is 1.27.1400.4 CL248020
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:
Hey my bluetooth and wifi both are not working. I go to wifi in settings click to turn it and it says turning on wifi for a while then the toggle sets back to off and if i try again same thing happens again and again. Exact same thing happens with bluetooth, not to sure when it started because i recently started using mobile data so have not been using wifi alot. Im currently using MIUI.us 2.10.19 v4 | 4.1.2 (JB) | 10/20/12 and was on codefire when it started, have flashed numerous other roms, jelly bean or ICS roms with the exact same thing happening each time for bluetooth and wifi. I tried restoring to a previous back up when it was all working but same thing happens there as well. how can i fix this ? anyone else have this problem ?
Your wiping you data before installation of any ROM right?
hukel56 said:
Your wiping you data before installation of any ROM right?
Click to expand...
Click to collapse
yes definitely every time i flash roms. The only reason that comes to mind that might have caused this i dropped this about 4 times last weekend. On the SAME night could it be that i damaged something inside ?
Maybe the two cables that are WiFi and Bluetooth came unplugged or are making contact with each other.
hukel56 said:
Maybe the two cables that are WiFi and Bluetooth came unplugged or are making contact with each other.
Click to expand...
Click to collapse
Do you know how i can fix ? which cables would it be ? what are the chances of my phone still working if i open it and try to fix it ? I also noticed the volume buttons don't work. They do sometimes, but rarely so if I am looking at fixing it, might aswell try to fix that up aswell. But that is not major, i just want the wifi and bluetooth to work so im looking at opening it up ?
I don't know how to fix it.
I've found a possible "fix" for the bluetooth problem... (very frequent disconnects from Android Wear and other devices, "Bluetooth Share" crashes, etc) but I need testers.
Attached is a zip you can flash from recovery.
After trying a bunch of stuff to get bluetooth to work properly with no luck, I decided to just rip the "/system/etc/bluetooth" folder off of an official LG 5.0.2 ROM and overwrite the existing bluetooth files in CM12.1. It seems to have worked. My bluetooth hasn't crashed once since, and Android Wear has been happy and synced all day. I'm running it on my E980 with the June 1 nightly build of CM12.1 (which also supposedly has some bt fixes... but bt still crashed on it until I flashed this).
New version July 6, 2015: btpatchv5.zip
v5 is based on bt from the latest (0704) CM12.1 nightly and works very well for me;
v4 is based on the official LG 5.0 ROM and IS tested.
Changes:
>> Bundled in the Ao-Shi app (not my work, all credit to Daniel Baucom for this nifty little tool)
>> Added 3 bluetooth binary files to /system/xbin in an attempt to quell the "bluesleep" wakelock and get some deep sleep.
Let me know how it works for you... grab the download below...
*Regarding the Ao-Shi app that I've included...
If you get an occasional BT crash, fire up the Ao-shi app. Tap "Kill Bluetooth" two or three times (not just once; once doesn't work). Then, click "Revive Bluetooth". For me this usually gets BT working again without a reboot. Again, thank you to Daniel Baucom for this little gem. It even has widgets you can add to your homescreen for faster action.
Thx for sharing this information.I've got another question, aren't you having problems using 'oké googe' on your wear?. I've seems to keeping having problems on my phone,using 'oké google'
stipvroegop said:
Thx for sharing this information.I've got another question, aren't you having problems using 'oké googe' on your wear?. I've seems to keeping having problems on my phone,using 'oké google'
Click to expand...
Click to collapse
Yes... when BT partially craps out, "OK Google" gets wonky. Usually I get a total BT crash shortly after.
I have been heavily experimenting, and I might be on the trail of a true fix, but I need to test more before posting it. Keep your fingers crossed.
stipvroegop said:
Thx for sharing this information.I've got another question, aren't you having problems using 'oké googe' on your wear?. I've seems to keeping having problems on my phone,using 'oké google'
Click to expand...
Click to collapse
I've uploaded a small patch, give it a shot and see if it helps you. It has worked great for me. See the OP for the file.
Mpsantiago, where can I find the patch, and how does it work? Tnx for sharing your solution
stipvroegop said:
Mpsantiago, where can I find the patch, and how does it work? Tnx for sharing your solution
Click to expand...
Click to collapse
It's up above attached to the first post- btpatchv2.zip
All it does is transplant the bluetooth files from the official LG 5.0.2 E9XX ROM into CM12.1.
Flash it from recovery and enjoy. You'll likely have to re-flash it after any nightly upgrade (until the problem gets fixed upstream).
Ok, I've tested the patch with both my Moto360 and my BT speakers- everything seems good.
mpsantiago said:
Ok, I've tested the patch with both my Moto360 and my BT speakers- everything seems good.
Click to expand...
Click to collapse
Still good with BT, do you still have screen flickering?
dpalmer76 said:
Still good with BT, do you still have screen flickering?
Click to expand...
Click to collapse
No, screen flickering is a pretty easy fix compared to BT:
Option #1: Turn off Hardware Overlays every time you boot your device
Option #2: Install the xposed module "NoMoreOverlay"
Option #3: Modify build.prop file, change the line "persist.hwc.mdpcomp.enable" from true to false
Do I only have to flash the zip for BT to stay synced? No need to change anything else?
DanC7766 said:
Do I only have to flash the zip for BT to stay synced? No need to change anything else?
Click to expand...
Click to collapse
Just flash, that's it.
So far, BT has only crashed twice since I first started testing it, and it happened when I was goofing with it pairing different stuff- not during normal use. Both times I was able to revive it without rebooting using this app: https://play.google.com/store/apps/details?id=co.loudbit.ao_shi
I've noticed very little deep sleep while using this solution, possibly related to "bluesleep" wakelock- I'm investigating this to see if I can fix it.
EDIT: I've added a new download to the OP above; not sure if it will fix bluesleep wakelocks but I'm hopeful... I'll be testing it tomorrow... off to bed now for me!
Update
mpsantiago said:
I've noticed very little deep sleep while using this solution, possibly related to "bluesleep" wakelock- I'm investigating this to see if I can fix it.
EDIT: I've added a new download to the OP above; not sure if it will fix bluesleep wakelocks but I'm hopeful... I'll be testing it tomorrow... off to bed now for me!
Click to expand...
Click to collapse
How is this fix working to date?
dpalmer76 said:
How is this fix working to date?
Click to expand...
Click to collapse
So far, so good.
I still get an occasional BT crash, but it's maybe one or two a day instead of one every 15 minutes. I'm actually testing yet another revision to the patch with an additional tweak and another LG BT library file moved over... if it is stable I'll post it next.
Tested the latest (june 4th) version and works so far. I did notice a decrease in battery life afterwards tho, significant vs the non-working bluetooth.
This patch may no longer be needed. I flashed 20150625-NIGHTLY this morning (without patching afterwards) and so far bluetooth has been flawless.
mpsantiago said:
This patch may no longer be needed. I flashed 20150625-NIGHTLY this morning (without patching afterwards) and so far bluetooth has been flawless.
Click to expand...
Click to collapse
sim card ok?
That day I was in a rush... I basically flashed the nightly and threw the phone in my pocket. My watch got all my notification alerts no problem all morning- it wasn't until lunch time that I looked at my phone and noticed the SIM problem.
Hopefully they'll have it sorted soon, though it's still not with the latest build. If it's not fixed by the end of the week I'll probably look into ripping the BT stuff out of the latest nightly and updating this patch with it.
mpsantiago said:
That day I was in a rush... I basically flashed the nightly and threw the phone in my pocket. My watch got all my notification alerts no problem all morning- it wasn't until lunch time that I looked at my phone and noticed the SIM problem.
Hopefully they'll have it sorted soon, though it's still not with the latest build. If it's not fixed by the end of the week I'll probably look into ripping the BT stuff out of the latest nightly and updating this patch with it.
Click to expand...
Click to collapse
Are you using this with blisspop? Wakelocks still?
Sent from my LG-E980 using Tapatalk
UPDATE:
Since the CM12.1 nightly builds still have a borked SIM card (but seemingly working BT), I replaced the bluetooth guts in V5 of this patch with the ones from the latest 12.1 build instead of what I was using before (the official LG 5.0 build). I have only tested it for a few hours, but it seems solid. Have NOT checked for wakelocks or battery drain. Flash at own risk.
I've omitted the Ao-Shi app; you can install it from Play Store if you want. Alternatively, if BT ever crashes you can manually revive it without rebooting:
Settings > Apps > All > Bluetooth Share > FORCE CLOSE then CLEAR DATA; turn Bluetooth back on and it should be fine.
dpalmer76 said:
Are you using this with blisspop? Wakelocks still?
Sent from my LG-E980 using Tapatalk
Click to expand...
Click to collapse
Haven't tried with Blisspop, only with cm12.1 nightlies. It should work on any CM12.1 based ROM though. I get decent deep sleep with it. YMMV.
Hey guys, I have updated to Android 10 from quite a sometime now(was a beta tester) and was noticing that device practically become usable after a few days of usage. Keyboard stops popping up, apps get killed in background and so on..
This issue gets fixed by a restart though. Has anyone else noticed something similar?
I am also facing issues after Android 10 update. Please let me know if you find permanent fix or solution.
Yes, same here. I reverted back to Pie. I thought I was the only one!
Sent from my SM-G960F using Tapatalk
Nope, you are not alone :crying:
i can confirm the exact same issue since OTA update to Android 10 on S9 (DBT). currently with second minor Update to DTAD build problem still there. Tried different things to work around but yet nothing helped. i assume it has something to do with memory leak on swap partition. memoryinfo & swapcheck app always show 0 byte free swap memory which cannot be freed again when this occurs. As stated before, only reset phone helps, but after 24h its the same. struggling with this since the first Q Update Version. Any suggestions highly appreciated.
Olioaglio
Auto-restart every morning
I didn't find any issue, and I didn't factory reset my device after installing the update. My phone runs quite smoothly, no issues whatsoever.
The only minor bug is that the transition animation of the clock from the lock screen to the always on display is laggy, and sometimes the instructions like "hold your phone more upright" get stuck on the always on display. I hope this will get fixed in the next update.
@icoolguy1995
any news on this issue? Perhaps it's any app or launcher or tool some of us use in common, since it seems not everyone is affected. i have to admit, that i have really a ton of apps on my device and freqently use it. But I already had the same conditions on Pie and there never run in this lag problem,so....
Cheers, Olioaglio
Olioaglio said:
@icoolguy1995
any news on this issue? Perhaps it's any app or launcher or tool some of us use in common, since it seems not everyone is affected. i have to admit, that i have really a ton of apps on my device and freqently use it. But I already had the same conditions on Pie and there never run in this lag problem,so....
Cheers, Olioaglio
Click to expand...
Click to collapse
Well I am still researching about this issue. I reported this issue couple of times to Samsung during beta testing; they said, they are unable to reproduce this issue neither they are able to see it on logs which I have sent. For me, the issue starts to appear after 91 hours of usage without a restart. Weirdly, using any keyboard other than Samsung Keyboard seems to help somewhat. I tried using Gboard and the issue somewhat mitigated but still annoying enough.
Did you guys tried reflashing the firmware using Odin?
icoolguy1995 said:
Did you guys tried reflashing the firmware using Odin?
Click to expand...
Click to collapse
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Olioaglio said:
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Click to expand...
Click to collapse
I have reflash the firmware because it was getting unbearable. It's been 3 days, no issues yet. Will keep you guys updated.
I just cleared the System Chache and my phone is working fine now.
Same issue here. After android 10 update it's laggy as hell. Android auto crashes randomly. Spotify stops working..
Olioaglio said:
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Click to expand...
Click to collapse
No effect of reflashing. Same issue popup up after 4-5 days. I wonder if this is more like a hardware related issue then software?
No, i don't think so.
Got a new update, it made issue worse. Now, instead of 90 hours free of system killing spree I am getting 70 around-ish hours with good ram management. So my workaround for this is now to set auto restart in 3 days interval.
Olioaglio said:
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Click to expand...
Click to collapse
Did you change your default keyboard?
icoolguy1995 said:
Did you change your default keyboard?
Click to expand...
Click to collapse
yeah, i use SwiftKey since ages.
Two updates passed (currently on G960FXXS9DTD7), so far so good (despite no mention in the changelog).