First, my apologies if this has been covered elsewhere but I don't read every post and XDA gets so much traffic that searching cold usually doesn't work well (and hasn't) for issues like these.
A bit of background.
I've used CM10.2, and loads of CM 11 nightlies and snapshots and have had the following issues on my One S
1) CM 10.2 crash happy. yes, I did do a factory reset and clean install. A couple of times just to make sure the problem wasn't me.
2) Went to CM11 and have the following issues consistently
1) Bluetooth crackle. usually after a fresh install things sound fine. After a few hours or a day the audio will start to crackle, almost like all the highs are clipping.
2) Bluetooth range. Much like the last one things start off ok but when the crackle appears, the range also drops to nothing. I can have the phone in my front pocket while I'm walking and experience regular signal drops and loss.
3) Audio playback through the ear speaker doesn't work except for phone calls. Everything else only works through a headset or on the back speaker.
Most everything else works well but these items are a deal-breaker. I've tried several CM11 based ROMs and Carbon and had the same problems.
Am I doomed to go back to stock? In the end I need something that works but also can get the latest security updates and Tmo has dropped this phone like a hot potato.
Try Viper.
Well, my initial attempt resulted in a phone that only boots to recovery.
Going to try to temporarily go back to CM since I need a working phone this afternoon
Related
So far I've tried both TnT Lite and the VEGAn roms and by far I prefer the VEGAn rom. My only issue is every once in a while, usually when something uses audio (movie, music or even a typing sound) I get a static/hissing/sounds like your TV is on a channel that doesn't have anything on it sound.it goes away after a couple seconds, but it's at full volume, doesn't matter of the audio is turned all the way down and will do it again if I do anything. I've tried the add and remove headphones, but it doesn't work. I've wiped and reinstalled the ROM, but it always comes back. The hissing/static sound happens on either the headphones or the speakers. Audio will work again when I reboot the unit but only for a little while. Any solutions?
There's another thread about a similar issue. 5 or 6 people responded that they get a crackle or pop every now and again. I get it also. One guy had it with the stock ROM. Another guy gets it through headphones when jogging.
No solution posted that I can find.
Thanks for the info. I guess it's either a hardware issue or an incompatibility between android and the driver.
I'm getting constant speaker hiss through the headphone jack, even when nothing is playing and when the display is off. Only exception is if the tablet is fully powered off. I'm flashed to VEGAn right now, but was getting the same hiss with TnT Lite. Didn't leave the stock ROM on long enough to know if it's happening there, too.
I get the same problem with some low volume hiss via headphone jack. Only happens when devices is in "sleep" -- not when powered off...
Sounds like this ROM (Vegan 5.1) leaves the the jack powered when in sleep...
My phone had the same problem until the ROM it was based on got fixed (it's running a CyanogenMod derivative)
It may be fixed in the CM7 builds -- so given that the next Vegan will incorporate some CM code as well, I'm hoping it will be fixed soon...
It has to be draining the battery if it is true that the jack is powered when in sleep...
So I rooted my Skyrocket last week and I screwed something up and since than I've had problems with the audio on the phone part. So I'm running Odin and even after double and triple checking I managed to screw it up by not having Auto Reboot checked. In a panic (and after waiting a long time) I unplugged the phone and powered it down. I booted into Recovery and did a wipe and installed CM 10.1.2 and I swear it worked fine for a week but all of a sudden I started having this weird issue with the phone audio. I'll call a number up and I won't be able to hear anything but I can put it on Speaker and it comes through fine or if I use my Bluetooth Headset it works fine.
I reloaded CM 10.1.2 and still nothing. I tried a nightly, I tried 10.1, I tried Beanstalk, and I now I'm back to stock and no luck on the phone audio. I have no idea what to do. I've tried Google searching and I'm coming up with a bunch of things but not what I'm looking for. I've even found some people having similar problems but they got no answer as well and I'm waiting to hear back from them (I found at least three people reporting the problem over on Cyanogenmod's Skyrocket Forum). I found some reference to it possibly being a Kernel problem. Thoughts?? I'll do some reading up on that tonight.
As a last resort I'm looking into buying a used Skyrocket to replace this one because I'm still 6 or 7 months till I'm eligible for an upgrade. HELP!
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?
jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Oh and yes I've tried back to stock with no luck.
dfwjose said:
Oh and yes I've tried back to stock with no luck.
Click to expand...
Click to collapse
Seems like you have your answer then. If the problem persists regardless of which ROM or kernel you're using then logically it would seem that it can't really be software related, right?
Brought to you but time and relative dimensions in space.
dfwjose said:
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?
Click to expand...
Click to collapse
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4
And just like that I'm up and running again and my phone works. I had given up and was having problems with a CM nightly so I did another wipe and loaded a stockish AT&T ROM that I've installed before and no my phone is working fine. I'm going to leave this thing alone until I pick up a spare phone!!
xcrazydx said:
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I'm sure it is and that's why I took the phone apart to see if I could get to it. I tried all kinds of things to get that tip out before tearing the phone down and I had no luck. I should have taken some pictures but I've tried tweezers (everything I had was to big or to weak to pull it out) and even glue before resorting to taking the phone apart. Unfortunately with the design it's enclosed all the way around with no way to really get to it. I even thought about replacing it but that piece looks to be soldered on.
In the end, I might just send it back to Samsung and see if they will fix it. Not sure if it's worth it but I never got serious about it because I didn't have a spare smart phone other than my work iPhone.
I shouldn't have spoken so soon. Rebooted the phone and it's locking up now. I give up. I can't find anything that will work. I either have sound with a phone that locks up or have to live with Speakerphone/Bluetooth and be able to reboot.
I've got this really annoying issue that I keep somehow getting rid of, but it comes back on it's own.
Any sound that plays from the phone e.g. Ringtones, YouTube, Poweramp, etc...
The audio levels get clipped, like something is trying to adjust the gain of the sound, parts that should be loud are not loud, but instead clipped to a really low level.
I've disabled AudioFX, cleared the data for it, and disabled the audio settings within Poweramp.
I've tried to get an example of it with my camera, but of course it's not doing it when I pull out the camera, next time Poweramp does it, I'll record it.
If I receive a call it clips the ringtone sometimes, but I tried calling the phone a second time and it didn't clip.
Really don't know what's going on, just want the audio to work properly.
I'm on 33R, Unlocked Bootloader Rooted.
If anyone knows how to fix this, I'd be really happy.
Could anyone also recommend an app that's like Poweramp, but free? I like it, but it's not quite right.
Removed Poweramp and the problem appears to be gone.
Even though I had all the audio settings disabled in Poweramp?
Still having the issue...
I have no idea what to look for now.
I seem to be having the same issue occasionally. It doesn't bother me overly much though. I just don't think the internal speakers of of the highest quality but everything else on this device is superb
I do however believe at least some of the issue is caused by the fact the the speaker grill holes are quite small so when the volume is high a lot of air pressure is created in the speaker cavity which may attribute to the the problem.
It's purely software.
Happens with the volume at 50% as well.
I have this issue too. Thought it was my headphones so tried all my pairs and it happens on all of them. Its an issue the Nexus 5 has as well and it has to do with how the phone handles the signal from the towers from you're carrier. As to my knowledge there is no fix for it yet.
https://github.com/anarkia1976/AK-OnePone/commit/8babaa621600e5b9e4614537aa75dd64988c9288
I switched to SlimKat ROM, haven't had the issue since my last post in this thread.
ak said:
https://github.com/anarkia1976/AK-OnePone/commit/8babaa621600e5b9e4614537aa75dd64988c9288
Click to expand...
Click to collapse
So are the working on a fix or how do we fix it? Because its annoying af.
Just wanted to report in again.
Still haven't had the audio clipping issue since switching to SlimKat.
The audio issue was really the only reason I had to even bother trying a ROM other than CM11S.
My experience with SlimKat on I9300 was a no-brainer to be the first ROM to try on my One.
Borgschulze said:
Just wanted to report in again.
Still haven't had the audio clipping issue since switching to SlimKat.
The audio issue was really the only reason I had to even bother trying a ROM other than CM11S.
My experience with SlimKat on I9300 was a no-brainer to be the first ROM to try on my One.
Click to expand...
Click to collapse
Running PA 4.6 Beta and its horrible. I can't stream one song on Spotify with out it clipping through. May be downloading SlimKat tonight to give it a go.
I still get the clipping on Slimkat, battery life is great tho.
Which build? I'm on Stable 7.0
When I call someone, the ringing sounds kind of funny, but other than that, every other sound works perfect so far.
Okay so I was on the M8 for about a year being a crack flasher and never having my phone set up quite the way I like it. I then switched to this phone and am loving it except the bluetooth. When I got it, I updated to 05Q before trying to connect to my car's bluetooth. I then had a lot of problems with bluetooth connecting, It would take forever to auto connect, music would skip and my phone would randomly disconnect. I did some reading and discovered it may be an issue with the update so I used the tool kit to downgrade to 44S. While less often, the issues are still very much present. I've been tempted to try CM12 but need something relatively stable. That being said, the 11s doesn't seem to be very stable itself, and I'm curious is bluetooth is better in the cm12 nightlies. I've done some research and I see references here to issues and then fixes and I'm not sure where things have landed at this point. Looking for some input on whether things would improve if I switched to the nightlies. Forgot to mention on my M8 bluetooth in my car worked flawlessly.
Hi, I am thinking to flash lineage OS to my oppo R7 plus and I was wondering how good is the battery line in lineage OS as consider to color OS. Battery life is the most imp thing for me in my cell phone. Any body using lineage OS work oppo R7 plus - can your answer me with some figures. I wil like to know some numbers. Like if I am getting 24 hours in color OS, how many hours I will get in lineage OS?
Thanks for any answers.
Hey there i'm on the latest LineageOS build , your mileage may vary but from 100% to 0% in my experience is in 1 day and multiple hours , Screen on time around 7-8 hours. Good luck !
Hi, thanks for the reply. That sounds good. One more question, VOOC charging is supported by Lineage OS?
Thanks
aiglesh said:
Hi, thanks for the reply. That sounds good. One more question, VOOC charging is supported by Lineage OS?
Thanks
Click to expand...
Click to collapse
Of course. you'll see charging rapidly on your lock screen.
Thanks a lot.
Two last questions before I can go for it.
1. If I don't like lineage OS and want to go back to stock color OS, is there any tutorial for that ( I searched but found nothing and even the official international oppo forms are closed recently).
2. Any major drawback of lineage OS as compared to Color OS? Any major features that is not working on lineage OS?
Thanks again.
how did you managed to flash lineage os ? please help me
There is tutorial here on the forums. I have not yet flashed it though.
aiglesh said:
Thanks a lot.
Two last questions before I can go for it.
1. If I don't like lineage OS and want to go back to stock color OS, is there any tutorial for that ( I searched but found nothing and even the official international oppo forms are closed recently).
2. Any major drawback of lineage OS as compared to Color OS? Any major features that is not working on lineage OS?
Thanks again.
Click to expand...
Click to collapse
If I were you, I wouldn't touch LOS with a barge pole on this phone.
I've been running the nightlies (which are really weeklies) for months and they just seem to get less and less usable.
Firstly, forget Bluetooth if you use LOS. Using any BT headset or speaker usually results in an extremely sluggish and/or resetting phone if a call then happens. I can be quite happily walking along listening to TuneIn on a BT headset but, if a call then comes in, I have about a 20% chance of taking it without the phone dying. Same if I place a call. Which basically makes BT useless unless you never want to talk to anyone., which is kinda what they're for.
I also sometimes experience frequent random slowdowns just by activating the phone (maybe once per 2-3 days). It was working fine when I put it down. Then I pick it up and press the on switch. It then takes over a minute for the screen to come on, and further interaction with it is glacially slow until you reboot it.
Other times, it doesn't become unusably slow but is still noticeably sluggish (after activating) for no apparent reason.
Various apps crash that didn't crash before. Not always, but often enough to be annoying. In particular, Titanium Backup crashed on startup for months. It doesn't now. I don't know what changed.
Double tapping the screen to wake it up sometimes works and sometimes (maybe every 10 days) doesn't.
Battery life is noticeably less than stock.
GPS (Google Maps) doesn't always work. A few days ago I had to visit somewhere I'd never been to before. I tried to follow myself, on the bus. My position didn't update after leaving the bus station.
And don't get me started on TWRP as the recovery. It claims to support USB OTG but it doesn't, which is a major problem if you want to back up the phone to a USB flash stick. You can't. And the developer completely ignores bug reports about it.
I have two of the phones, both of the r7plusf model, so I'm sure these aren't problems with a specific phone.
And the nature of most of these problems is that you can't capture logs to file a bug.
All in all, if you have this phone just stick with what OPPO gives you, warts and all, unless you *really* want an ulcer. Or, if you really want to use LOS, get another phone.
Sorry for the late reply.
PS - if a dev happens to be listening, contact me. I'd love to help fix this stuff in any way I can.
NeBlackCat said:
If I were you, I wouldn't touch LOS with a barge pole on this phone.
I've been running the nightlies (which are really weeklies) for months and they just seem to get less and less usable.
Firstly, forget Bluetooth if you use LOS. Using any BT headset or speaker usually results in an extremely sluggish and/or resetting phone if a call then happens. I can be quite happily walking along listening to TuneIn on a BT headset but, if a call then comes in, I have about a 20% chance of taking it without the phone dying. Same if I place a call. Which basically makes BT useless unless you never want to talk to anyone., which is kinda what they're for.
I also sometimes experience frequent random slowdowns just by activating the phone (maybe once per 2-3 days). It was working fine when I put it down. Then I pick it up and press the on switch. It then takes over a minute for the screen to come on, and further interaction with it is glacially slow until you reboot it.
Other times, it doesn't become unusably slow but is still noticeably sluggish (after activating) for no apparent reason.
Various apps crash that didn't crash before. Not always, but often enough to be annoying. In particular, Titanium Backup crashed on startup for months. It doesn't now. I don't know what changed.
Double tapping the screen to wake it up sometimes works and sometimes (maybe every 10 days) doesn't.
Battery life is noticeably less than stock.
GPS (Google Maps) doesn't always work. A few days ago I had to visit somewhere I'd never been to before. I tried to follow myself, on the bus. My position didn't update after leaving the bus station.
And don't get me started on TWRP as the recovery. It claims to support USB OTG but it doesn't, which is a major problem if you want to back up the phone to a USB flash stick. You can't. And the developer completely ignores bug reports about it.
I have two of the phones, both of the r7plusf model, so I'm sure these aren't problems with a specific phone.
And the nature of most of these problems is that you can't capture logs to file a bug.
All in all, if you have this phone just stick with what OPPO gives you, warts and all, unless you *really* want an ulcer. Or, if you really want to use LOS, get another phone.
Sorry for the late reply.
PS - if a dev happens to be listening, contact me. I'd love to help fix this stuff in any way I can.
Click to expand...
Click to collapse
I'm on the same nightlies , i don't have any issues you mentioned (yes even bluetooth works perfectly) ! the only bug i have started with last month's nightlies which makes headphones audio stutter at low volume.
rch.aj34 said:
I'm on the same nightlies , i don't have any issues you mentioned (yes even bluetooth works perfectly) ! the only bug i have started with last month's nightlies which makes headphones audio stutter at low volume.
Click to expand...
Click to collapse
This blows my mind. What didn't I do right? Didn't I sacrifice enough chickens?
TBH the Bluetooth problem (at least) is well documented, as well as being a massive dealbreaker.
Funnily enough though I don't have an audio stutter problem. But I don't use physically attached headphones.
Are you open to a crash-off, in which we both install the same LOS version and (if necessary) start adding apps until we either see my problems or we don't?
rch.aj34 said:
Of course. you'll see charging rapidly on your lock screen.
Click to expand...
Click to collapse
This helped me too, thanks. I put an inline meter and it was only drawing 1.x amps but without the meter I can see "rapidly charging" on the lockscreen. Pity there is no battery icon change for Oppo's in LineageOS (14.1).
One more thing, if you're still active... which country are you in? I first put 15.1 on my R7Plusf and right off the bat WiFi didn't work.. even after reboot etc.
I flashed 14.1 and every single thing works perfectly so far!