I am troubleshooting the SOD issue, and was wondering if anyone is / has been experiencing this problem when NOT using bluetooth (you get SOD when your bluetooth is turned off)?
In the meantime I am checking to see if auto updates set to "on" in Facebook / Twitter / or Weather could be the culprits.
mmicha said:
I am troubleshooting the SOD issue, and was wondering if anyone is / has been experiencing this problem when NOT using bluetooth (you get SOD when your bluetooth is turned off)?
In the meantime I am checking to see if auto updates set to "on" in Facebook / Twitter / or Weather could be the culprits.
Click to expand...
Click to collapse
sorry mmicha - when I was getting the sod I changed roms until I found a version without a problem. recently I've used roms with sys builds 23541 and 28232 running bluetooth as well as auto updates without any problems.
I once had the SOD with using bluetooth a while back (when paired with a rental car's BT stereo), but yesterday started getting it every time phone goes to standby (without using BT) - only soft reset/removing battery helps. I have made no changes to registry or even installed apps in the last couple of weeks so have no idea why it is happening. Continuing to search forums at the mo...
BTW: Stock 6.5 WWE ROM
SOLVED: Turns out it was SRS WOW HD causing the SOD as no had it once since uninstalling. It was strange as I had installed it days/week prior and the SOD just happened suddenly when I hadn't even used SRS or my music player at all that day!?
Related
Some of you guys might know di.fm, I really like listening to their streams and I recently discovered that there's an app for streaming to an android phone.
However I'm having problems with the streaming on my Desire. The app itself runs fine, but as soon as my device locks due to the 1 minute display timeout or I lock it manually, the streaming will just stop randomly after 30-60 seconds.
As soon I unlock my device and use it, the music returns instantly.
I was hoping one of you guys might help or have been experiencing similar problems.
Here's a link to the app: di.fm/apps/android/
I'm running the following official HTC ROM on my phone:
RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed.exe
Is it happening on data, or wifi? Have you got juicedefender installed?
It sounds like it's dropping the connection once your phone goes to sleep. If it's only on wifi try this.. Press Menu, then tap settings>wireless and networks>wifi settings>press menu>tap advanced>wifi sleep policy, and set to Never.
WiFi sleep policy is set to never. However this is only happening on WiFi. It works fine when I'm on mobile internet.
Thanks for pointing out there are advanced WiFi settings though, I wasn't aware of that.
Problem solved, please close this thread.
Sent from my HTC Desire using XDA App
Finally the SOD issue is fixed.
My 4 trials:
1. with no facebook auto update active, TP2 gets no SOD
2. with facebook auto update active, TP2 gets loads of SOD every day
3. download people application update from HTC and trial with no facebook update - no SOD's at all
4. switch on facebook update - since people application update installed - no SOD's at all!!!! and this has been running for quite a few weeks
NOT a single SOD at all. Fixed. Looks like SOD was related to memory issue consumption with facebook. Try it out.
Apart from a few speaker issues with Sense 2.5, my TP2 is pretty good for a slow phone compared to todays standard!
Too bad I don't use the facebook update.
I'm using the standard WM6.5 WWE Rom from HTC.
That has no update feature for facebook, but does have the SOD problems... a lot
Strange, only ever had sods with sense 2.5. And now they are completely gone. Memory usage is normal with the occasional crashes that comes with the underpowered tp2 but no black screen of deaths
I've never used facebooke, I disabled it in settings and still get SODs. In fact, much less after systemboard replacement...
Tried it all and still having the issue.
The problem for my device seems to be backlight related. I have noticed that I can not adjust the backlight settings at all...It always seems to be at 100 % no matter what I do. Tried Lumos and other backlight adjustment apps to no available solution. Tried even downgrading from wm6.5 go 6.1 stock rom and nadda. I wish there was a sound fix for everyone posted somewhere!! Any help would be greatly appreciated. When I boot into android...the sleep button will turn the screen on and off fine so the hardware button is working but I also notice in Android that the backlight is still lit even with the screen off. Backlight sensor works as when I answer a call it turns off but this dam SOD will never allow it to come back on unless a reset is done.
Telus CDMA TP2 with Sharkie Rom wm6.5 running.... Android Froyo 2.2 build as my work around but battery drains like crazy because the backlight never turns off! PLS HELP!
Thank you in advance, Kind Regards,
orangestrawberry said:
Finally the SOD issue is fixed.
My 4 trials:
1. with no facebook auto update active, TP2 gets no SOD
2. with facebook auto update active, TP2 gets loads of SOD every day
3. download people application update from HTC and trial with no facebook update - no SOD's at all
4. switch on facebook update - since people application update installed - no SOD's at all!!!! and this has been running for quite a few weeks
NOT a single SOD at all. Fixed. Looks like SOD was related to memory issue consumption with facebook. Try it out.
Apart from a few speaker issues with Sense 2.5, my TP2 is pretty good for a slow phone compared to todays standard!
Click to expand...
Click to collapse
Hi.
Which ROM are u using?
I have the same problem and i'm 100% sure too that it's the facebook update. When is turned off don't get any SOD. But if i try to update manually and the phone goes to standby it won't wake up.
Today i installed the people application update but no luck. Its getting SOD's every time i try to update. Dammmm
It's this www[.]htc[.]com/pt/SupportDownload.aspx?p_id=250&cat=0&dl_id=1061 the update that you say, wright?
I'm using the ROM 2.07.410.1 (80303) PTG.
Can we see anywuere in the phone that the update is installed?
Thanks
Nuno Viegas
Get SOD's without Facebook installed!
I am using ROM 2.07.401.1 with Manila version 2.5.20121225.0 (the standard WinMo 6.5 WWE ROM and get a lot of SOD's (about 3 per week) . And I don't even have this Facebook update installed, since I don't have a Facebook account.
If anyone has a solution I would be extremely glad!
HTC is no help....
guys,
I've issued this before in the rom specific thread, and searched for it, but no answer... (well, partially, but sure don't hope this is the answer; http://forum.xda-developers.com/showthread.php?t=835547)
When connected to bluetooth (streaming to my audio installation) and wifi on, when the signal drops, rosie freezes... only given time it unfreezes (after pressing the trackpad to wake and unlock and a loooot of time)...
It's quite an annoying error, and I seem to experience it with all gb roms...
It becomes more strange... when wifi on, and checking bluetooth on in wireless settings, wifi drops out... and gets on again...
Anyone any idea? It's kinda driving me nuts... now running the 3d version of acesmod007, but also experienced it on other roms...
- could it be gb related?
- could it be rosie related (somehow?)?
- could it be the radio (see signature)
- could it be kernel related?
- could it have anything to do with the build of the rom?
- could it have something to do....?
many thanks in advance...
To start-
I am running the latest version of Pure Nexus. My 5x had been working perfectly til the update to Android 7.1.1
My Nexus is appx. 1 year old. I am currently on Google Fi.
This is my problem. The bluetooth and wifi will randomly shut off. It seems to happen when I wake the phone from doze- I can be listening to music on bluetooth headphones, then I wake the screen to do something and the bluetooth and wifi will shut off. I have also noticed that the cellular network may be resetting- not always, but sometimes. I've tried adjusting battery settings to no avail.
My question- what should I check? Is there a log that may be helpful? Is anyone else having this problem?
Thanks for the help!
Just an update. Moved to latest update. Problem is still there. Has anyone got any idea if the problem is with the ROM, the settings, or the phone?
Hi guys,
I'm having a weird problem that I am unable to resolve. It drives me crazy since I have a very long drive daily and rely on bluetooth audio.
When playing music over bluetooth, there will be stuttering after 20-30mins of playback. The stutter will occur sporadically every x seconds. Sometimes it goes away sometimes it doesn't.
A quick fix I found is disabling/enabling bluetooth, which resets everything and gives another ~20-30 mins without stuttering.
Since I use the phone as a work device, I bought another one so that I could run some tests. Both phones are unlocked.
I tried Pi Experience (Pi) and Lineage 15.1 (Oreo). Both were ran without any apps other than the built-in ones and Play Music.
A few troubleshooting steps I did:
- Since this is occurring on 2+ devices, I strongly doubt it's a hardware issue
- My previous LG V20 (Android 6-7) and friends Iphone have zero issues (so the car isn't the problem)
- This stutter occurs on any BT device the phone connects to
- Disabling/enabling bluetooth resets the issue
- Pi and oreo are affected
- Disabling BT/Wifi scanning in location does not resolve the issue.
- Stopping every service related to BT besides a2dp while the problem occurs does not resolve the issue.
- Restarting Play Music or stopping Play store does not resolve the issue.
- Disabling battery Manager on Pi does not resolve the problem
What I think the problem could be:
- Memory leak in the A2dp service? (I have no idea how to check for that)
- Power saving features that are applied to the BT service after being active for so long (since resetting the service works)?
I'm running out of ideas. Does anyone have any suggestions/tips/story on what the culprit could be and how to fix it?
I can provide a logcat of when the problem occurs if that can be of help
Thanks
Phil
Bumping this up in case someone can chime in!
I have tried all the firmwares as they become available and still face this issue! I know for a fact I am not alone with this problem since I have 2 Redmi Note 5 pros with this problem, and had the exact same issue with a Samsung Galaxy S9+ (snapdragon) that was returned!
If someone can answer these questions, that would be greatly appreciated:
- Do the Firmwares available contain the actual android drivers for bluetooth? Or it's the literal firmware for the SOC (the driver would then be a different file inside the /system partition)?
- When you disable/enable bluetooth, what happens in android? Is the driver unloaded/loaded? or maybe disabled/enabled? Since this step resets the the problem, i'd be interested to know!
Thanks
Maybe Doze-related, but I use audio over Bluetooth for like 2hs almost every single day in my main device (Is not whyred) without problems, so I'm not sure about that.
1- No, the Bluetooth blobs are located in /vendor partition.
1- The operation of bluetooth is complex, many things happen when it's switched on/off, but simplifying: some processes and services are started/stopped.
Anyways, the best way to find the problem is taking logs and send it to the rom developer.
onliner said:
Maybe Doze-related, but I use audio over Bluetooth for like 2hs almost every single day in my main device (Is not whyred) without problems, so I'm not sure about that.
1- No, the Bluetooth blobs are located in /vendor partition.
1- The operation of bluetooth is complex, many things happen when it's switched on/off, but simplifying: some processes and services are started/stopped.
Anyways, the best way to find the problem is taking logs and send it to the rom developer.
Click to expand...
Click to collapse
Thanks for the reply.
This occurs on every rom that is loaded on the devices. I have a strong feeling it's related to the drivers.
I tried looking at the logcat while it glitches, and no errors seem to be shown. I will attach one within the next few days.