Currently running an LG G5 RS988 on Resurrection Remix 5.8.5
I have two issues:
Big one is that WiFi is spotty. It wasn't before, but after flashing it drops out
When I try to connect, settings either says "Password may be incorrect" or underneath the SSID it just says "Saved"
It usually connects after ~30 seconds, but is a hassle.
2nd issue is that fast charging does not work.
Does anyone have any fixes for these issues?
Update: Restarted router and wifi problem seems to be fixed, can't tell though because its a negative symptom.
Any ideas for fast charging? It takes ~4 hours to charge
Update 2: Wifi still seems to be somewhat spotty, not sure what to make of this
Fast charging doesn't work in ANY CM/LOS based custom rom since late July because they broke something upstream. Use the search in the RR or any of the other rom threads for details.
WiFi is fine on my H850 with RR (and any other rom), but some users have reported issues. Again, use the search
And FYI: Post issues with a specific rom in the thread of that rom, you'll get more replies and don't clutter everything up
How is Bluetooth working for everyone? Also, when I tried RR, it forgot the devices I previously paired with the G5.
KCKitsune said:
How is Bluetooth working for everyone? Also, when I tried RR, it forgot the devices I previously paired with the G5.
Click to expand...
Click to collapse
Works fine with music + movies, doesn't work with calls. I only have 1 headset, but RR never forgot it so far
Nimueh said:
Works fine with music + movies, doesn't work with calls. I only have 1 headset, but RR never forgot it so far
Click to expand...
Click to collapse
Thanks for the heads up, Nimueh.
Damn, I was so hoping to be able to go back to a LOS Rom rather than stock, but I need that Bluetooth function.
Related
I'm going to download it tonight and test it out. Hopefully, the massive bugs were fixed and we can have OFFICIAL Cyanogenmod 12 on our devices.
I just randomly checked yesterday and noticed it was back. I'm on 03/27 right now and so far, so good.
Sent from my Sprint Galaxy S5.
Is everything working?
daniel3x said:
Is everything working?
Click to expand...
Click to collapse
It seemed to be. Calling, wifi, data (3g and LTE), SMS and MMS were all working for me. I opened Maps and the phone froze, so not sure if GPS is working. I flashed back to another rom though.
GPS works just fine.
Sent from my Sprint Galaxy S5.
Does anyone have a visual voicemail apk that works by any chance? If you do, please pm it to me or something, I'd really appreciate it, thanks!
JSarella said:
Does anyone have a visual voicemail apk that works by any chance? If you do, please pm it to me or something, I'd really appreciate it, thanks!
Click to expand...
Click to collapse
Check PM
CM12 Noob
Nor sure if anyone is still following this post but I installed cm12 a few days ago and the only issue I can reproduce it the Bluetooth cuts out. I can't complain, it's way faster than touchwiz and it does not crash any more frequently. One issue I have noticed is that it doesn't seem to download MMS automatically but I've only noticed it when receiving a group txt in hangouts. I can't seem to find any good discussion groups on cm here on XDA. If anyone has a suggestion, I have a Spring Galaxy S5 and am quite new to flashing as well as forums, but pretty proficient with computers. Any help would be appreciated, Thx
If CM 12 is broken i dont receive calls but can do it, It is best to install MOAR
Bluetooth does not work , the messages are closed every 5 minutes
Need working Sprint Visual Voicemail apk for Galaxy S5 running Fusion Rom
I apologize if I am posting this in the wrong area. I have been running the Fusion Rom on my Sprint Galaxy s5. I love it, but cannot get any voicemails! Have tried a few apks, but no luck. Any info and/or download links would be very much appreciated!!
Susan
I just tried the 8/8 build. So far, pretty stable. I did try the full device encryption and it basically borked the installation. I got it to come back by clearing cache a few times (why a few times and not just once? Who knows.) but it was increasingly unstable at that point (random crashes, random boot freezes). I wiped and reinstalled and it's back to stable, so it's definitely the encryption. Going to mess with bluetooth today to see if that's been resolved yet.
Bluetooth still completely doesn't work. I can't even get it to connect. Not quite ready for prime time I guess.
So at this point, not worth trying? no BT? How's the camera?
TN 12.1 latest build
I have been running the 9/26/15 build for three days and am experiencing the worst battery drain since the day this phone came to market.
I am wondering if this is a TN problem or the latest lollipop aosp issue as a whole?
Thanks
im using Team Nocturnal vm_kltespr-userdebug 5.1.1 lvy48f0333148f75 test keys build date 9/13/2015 and I adjusted the i/o-scheduler and have stopped charging my phone over night... it lasts all day with tons of emails and some multimedia a few dozen phone calls and 150 texts and all night and I charge it in the car between work and home... approx 45 min... good to go.... the only thing that doesnt work is the fingerprint scanner... everything else is fine... it does have trouble switching data back to mobile off of wifi, but, nice smooth and fast...
misile2012 said:
im using Team Nocturnal vm_kltespr-userdebug 5.1.1 lvy48f0333148f75 test keys build date 9/13/2015 and I adjusted the i/o-scheduler and have stopped charging my phone over night... it lasts all day with tons of emails and some multimedia a few dozen phone calls and 150 texts and all night and I charge it in the car between work and home... approx 45 min... good to go.... the only thing that doesnt work is the fingerprint scanner... everything else is fine... it does have trouble switching data back to mobile off of wifi, but, nice smooth and fast...
Click to expand...
Click to collapse
What i/o settings are you using?
Sent from my SM-G900P using XDA Free mobile app
So i've tried pretty much every ROM out and wanted to post my findings with Call reception,data issues, APNs, etc and see if anyone else on Sprint has workarounds or advice on how to fix issues. On some ROMs i can get data but can't get calls/texts. On others i can get voice and data and hear people fine while on calls, but they tell me i'm breaking up constantly.
ROMs with voice and data, but poor voice delivery while on calls:
Resurrection Remix
AOKP
Turbo ROM
Temasek(i think...been awhile since i've flashed and can't remember)
Roms with data(sometimes) but cant make calls/texts:
PureNexus
DirtyUnicorn
ROMs with working data and good call quality:
AICP
Mokee
TruPureX(yes, i know it's not a custom ROM just putting it here because there are no issues with call reception or data on Sprint)
I believe if we were able to manually set APNs for some of these ROMs we could possibly correct this issue but for some reason the majority of ROMs i've flashed say "APN settings are not available for this user". Does anyone know a workaround for this issue? Please post other ROMs that i haven't commented on or other findings/workarounds
I know this is a long shot since this is an old post, but I was curious if you ever found anything on this? I had gone through a bunch of the ROMs mentioned and had the same experience. The only ROM I have had success with and has been almost flawless is Turbo. Yet I have the calling issue where everyone says I'm choppy and cut out so I am having to switch again. Everything else except TruePure I have had data issues with. LTE seems to drop and then I have nothing, it's almost like it can't hand off to 3g. Then I have no signal at all.
I'd go with the stock ROM, but that just has some horrible lag when operating. If I could pull whatever make Turbo work over to another ROM that would be great, but I've never set anything like that up.
Can it be a problem if you are using a XT1572 or XT1575? Maybe you need to be ROM specific when it comes to your device model.
This is the most annoying problem. At this point most roms I try have everything but 4g.
So I got my S4 up and running on Ting and got CM13 running on it, was having the LTE issues and flashed the .zip for MVNO and got my lte working so that was fine. Everything was great but than I realized that when I'm at home (where I have very weak signal) that the network would drop out and it would just say no service and stay that way until I rebooted, than everything would be good again for a few minutes until it lost service again and it would not pick it back up. I flashed back to stock using odin and even though I would have very weak signal it would never fully drop the network and I could still receive calls. The phone is running on OK3, I tried the OCTOS CM13 rom and had the same problem. Haven't tried any AOSP or any other Touch wiz roms yet to see if the problem persists just because work hasn't afforded me the time to mess with it. I was curious if anyone else had these same issues though or if there was anything I could edit in the system files to get it to reconnect to the network after it drops it. I will note as well that when I'm at work where I have a strong cellular signal I don't have this problem at all, it's just when the network falls out it won't pick it back up again. I figure it has to be something simple that can be corrected but I don't have the experience or knowledge to even begin to know where to look and after almost a week of searching these forums and google I haven't been able to find an answer or a similar problem. Any help or guidance would be hugely appreciated.
Yes I feel your pain. I've been experiencing this issue also and have yet to find a fix. I did see that someone reported that they don't have the issue with the R1 build of OctOs. I have yet to test this but I hope it will fix the issue.
andyman2017 said:
Yes I feel your pain. I've been experiencing this issue also and have yet to find a fix. I did see that someone reported that they don't have the issue with the R1 build of OctOs. I have yet to test this but I hope it will fix the issue.
Click to expand...
Click to collapse
Well at least now I know I am not the only one! I'll keep searching for an answer and try a few other roms that aren't CM based and see if I can find some sort of solution that isn't running rooted stock firmware. Ideally something MM based. Also if you could link to the thread where someone else reported a similar problem that would be great. Let me know if you find a solution before I do, one has to exist I'm sure.
So I saw towards the end of the octos thread where other people have been reporting the same issue with CM13 and OCTOS, found the R1 version of octos, will give it a try and report back. Hopefully CM13 catches wind and can trace back to whatever it is that is causing this issue as well, I might try one of the newer CM13 nightlies and see if maybe the problem hasn't been remedied but I'm not holding my breath :-/ I just really want MM back.
So update, I installed the R1 version of octos and the "no network" issue has not reared its head again yet. I Flashed the buzzbeemvno fix as well afterwards and one thing I did notice, before the mvno flash I was getting 3g signal with the sprint profile, once I flashed over to the ting profile it was only pulling 1x as far as signal is concerned. I don't really mind though since I have a solid wifi signal at home and the main goal here was to just have reliable signal to receive calls and texts when I ought to.
Give this APN a shot. It's the one I'm using currently. I think I may need to make some adjustments still, but it seems to work well enough so far.
It's also usually a good idea to reboot into recovery and delete the telephony.db and telephony.db-journal files in /data/data/com.android.providers.telephony/databases/ after you have replaced the apns-conf.xml. The system will recreate those files on startup using the new data.
Blaises are you running that APN pack on the newer cm13 builds?
I'm running the APN I linked earlier rather than the MVNO fix., and I'm using it on OctOS R1 which is a CM13 build from March.
I'm using Ting on the Sprint network.
Can I get your opinion on oct-os? Is it a daily driver ROM? Did you guys stay on the ROM? Any advice for me or warnings?
Sent from my KIW-L24 using XDA-Developers mobile app
So I am on the older build of octos from the spring, it's been a great daily driver gives me almost no problems. There has been an occasional Bluetooth hiccup and camera hiccups. But maybe once a month, overall it's been a great ROM.
I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. <--- Reported fixed with light patch v1.2 experimental
Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?
I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.
ThePublisher said:
I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.
Click to expand...
Click to collapse
Yeah you're prolly right. I'll excise the last part. I tried Bad Boyz. It's great but I can't do stock based. I've come to rely on all the tweaks in custom ROMs. I should have done more research prior to buying the phone. I need a tweaker's phone like the OnePlus 5. Thank you for your response.
I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. It solved mine and others too.
---------- Post added at 07:22 AM ---------- Previous post was at 07:17 AM ----------
Doc Ames said:
I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...
ArgonautPollux said:
I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.
Click to expand...
Click to collapse
Thank you. That's very helpful.
Laleka said:
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...
Click to expand...
Click to collapse
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.
Doc Ames said:
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.
Click to expand...
Click to collapse
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.
Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
That's a really good idea to use a Tasker task. I wonder if Bluetooth will ever be fixed though. Problem is that Bluetooth connectivity issues only happen with some car head units. It seems like devs aren't looking to fix Bluetooth on custom ROMs because they don't think there's an issue.
piet8stevens said:
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.
Click to expand...
Click to collapse
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.
Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.
Doc Ames said:
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.
Click to expand...
Click to collapse
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.
piet8stevens said:
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.
Click to expand...
Click to collapse
Audio streaming with AVRCP works fine. However the head unit (Kenwood KMM-BT515HD) shows a status of "Connected (no phone)" in Android Bluetooth settings. This means that I can't use my deck to make/answer calls or use voice commands. It works as expected on stock and on Pure Nexus. Others are having this issue too. I know a couple members had issues on Nissan decks and one that I know of had a BMW deck.
Does anyone get voice echo during voice calls on custom roms?
I'm looking to buy the Axon 7 soon, but the voice echo would be a dealbreaker if it exists.
( it's currently an issue with the custom roms I've tried on my Xperia XZ - if I call anyone they complain that they can hear an echo of their voice )
Waancho said:
Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.
Click to expand...
Click to collapse
You need to install Dolby digital
Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.
rafyvitto said:
Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.
Click to expand...
Click to collapse
Whatever the issue is it only causes connection problems (i.e. "Connected (no phone)" ) with some head units. I should try connecting to my roommate's Toyota. I bet it would connect as a phone just fine. There was an issue with BT in LOS that was causing AVRCP (remote control, song info) to not work with some head units. I'm guessing the devs couldn't solve the underlying issue because the fix was to roll back the AVRCP version. It seems there are still compatibility issues with Bluetooth in LOS and AOSP ROMs (save Pure Nexus).
If I could get BT to work fully with my car I would absolutely use RR as my daily driver. Unfortunately the phone is sitting in the box right now until I lose patience and sell the phone or the BT gets fixed. Sucks because I was totally thrilled with the phone after installing and setting up AOSPExtended. Then I got into my car and noticed the issue forcing me back to the dusty, but trusty OnePlus One.
supergear said:
You need to install Dolby digital
Click to expand...
Click to collapse
Hi there,
Thanks a lot for the info (new to me) - to verify:
Are you referring to
https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342
or is there another (preferable safe/easy to install) version one would need?
Thanks again!
This has been happening for a couple months. Seems like a couple times a day I lose my data connection, and the only fix is to reboot. After that it's fine for a while, until it drops again...
Running rooted 6.0.1, radio version 3.61. Anything I can check? Or should I just flash a new image?
I have this issue, flashing different radios did nothing for me. The hardware is just going bad I think
Been having the same issue for a couple months now, going to my carrier for a new SIM and resetting APN did nothing. Thought it was my ROM at first and ended up flashing a few different ones along with kernels, it was never fixed. Data drops and comes back about 10 minutes later, every half hour or so. Seems to not effect calling or messaging, only data. Is this a confirmed hardware issue?
My wife and I both had our 6P's doing this as well. Seems like the device will get in a connection loop or something. the WiFi drops, then my 4g data signal, then both are out, then WiFi turns on, Data turns on, then repeats the process. I usually reboot, or toggle airplane mode off and on to stop it. Its periodic, but it doesn't last long on my end. I'm on T-Mobile BTW
UPDATE - REFER YOU TO THIS LINK. Looks like radio files from Android O Beta DP4 are confirmed to fix the T-Mobile Cell Signal Bug
Hopefully, this means our prayers have been answered
https://forum.xda-developers.com/nexus-6p/general/nexus-6p-radio-bootloader-recovery-t3433637/page35
mikeygeer said:
UPDATE - REFER YOU TO THIS LINK. Looks like radio files from Android O Beta DP4 are confirmed to fix the T-Mobile Cell Signal Bug
Hopefully, this means our prayers have been answered
https://forum.xda-developers.com/nexus-6p/general/nexus-6p-radio-bootloader-recovery-t3433637/page35
Click to expand...
Click to collapse
My radio didn't drop once on the way to work today, hell, it's still going right now. I actually think it's been fixed
is it ok to apply the updated radio without upgrading android (staying on 6.0.1)? i heard there have been some issues with 7.x on the Nexus?
mgoblue2005 said:
is it ok to apply the updated radio without upgrading android (staying on 6.0.1)? i heard there have been some issues with 7.x on the Nexus?
Click to expand...
Click to collapse
I do not know its comptibility with 6.0.1 - you could just make a backup and give it a try.
conversely I must say - Nougat on good ROMs is stable and gets good battery life. What are you concerns with just joining the party here on Nougat?
mikeygeer said:
I do not know its comptibility with 6.0.1 - you could just make a backup and give it a try.
conversely I must say - Nougat on good ROMs is stable and gets good battery life. What are you concerns with just joining the party here on Nougat?
Click to expand...
Click to collapse
-----------------------------------------------
I'm running rooted stock android. Haven't made the move to any custom ROMs yet. I recall when Nougat first landed people were reporting some issues with it on the 6P (battery life? instability?).
That being said I'm open to loading a Nougat ROM if it's gonna be stable. Is there any consensus on top ROM for the 6P (something close to stock android experience)?
Close to stock with aroma installable features, check superxe rom, you can choose between nougat or Android O.