I remember a month or so ago I installed a Google Play Edition Lollipop ROM (completely stock but rooted) onto my M919.
Everything was fine until after 2 weeks of use I started to notice tons of lag. Apparently this is a normal problem with Lollipop on all phones.
Has this issue been resolved yet? I've since downgraded to 4.4.4 (KitKat) and I'm just waiting around until Lollipop gets figured out.
Wait until after 5.1 because it was fixed after the release of 5.1
The official version released to phones that got carrier updated like my wife's note 3 is running smoothly with no apparent lag and all aspects of phone and features work perfectly, NFC, wifi calling, camera, messaging and so forth.
As for what's available for the S4, unofficial, experimental and half baked setups, you would have to wait for "official" lollipop ota before the bugs get worked out of it.
I'm sitting patiently on my stock /rooted kitkat waiting for ota.
Pp.
Related
Hello all. I have my Note rooted with a custom recovery, but I have not flashed a rom. Well, I have flashed a few, but I've since gone back to stock and re-rooted because the bluetooth issues are a dealbreaker for me.
Here is the actual question. I've been getting a lot of updates from samsung. I came from an HTC Evo - and HTC rarely did updates. Has Samsung really released 3-4 updates in the last 2 weeks? Or is my phone just not properly installing them? The android version is 4.1.1, also not sure if this is all the way current. I just checked on the update your phone page in the system settings and it says I am current...
I'm running the same thing as you (stock, rooted with custom recovery) and I have not had an update recently. Mine is currently 4.1.1 as well, with the L900VPALJC build. I agree that it's the BT streaming that's keeping me from custom roms right now
bl4ckllama said:
I'm running the same thing as you (stock, rooted with custom recovery) and I have not had an update recently. Mine is currently 4.1.1 as well, with the L900VPALJC build. I agree that it's the BT streaming that's keeping me from custom roms right now
Click to expand...
Click to collapse
I've had issues not only with A2DP, but also with call quality on BT as well. It sounds choppy and has TERRIBLE range on at least 3 different roms...Paranoid Android is awesome on our 5.5" screen, but I cant talk on the phone or use Slacker radio Hopefullt someone does a better job with the BT drivers sometime soon.
I imagine once the CM blue tooth problems are fixed the roms using it will get stepped up. I downloaded Macksrom today to run a trial to see how the improvements are. Though now that I know ADW isn't messing up my phone anymore I may just stick with stock for now. I have a current backup and I'm feeling bored, so I'll most likely **** around with it this weekend
Hello all...
Has anyone else been having buffering issues at the beginning of Google Play Music streaming songs? The music will go for a second, stop, go for another couple of seconds, stop, and then play fully. This is on Normal quality and is in places where I can do a speedtest at over 10mbit/sec. Often it's 20mbit or more. It seems like this started happening when the new 3.x firmware was released. I never had buffering before.
I've tried everything from uninstalling/clearing data to clean flashing ROMs. Same thing, and it shouldn't be happening with the bandwidth I have available.
Thanks.
A
Ive noticed this as well. Have not noticed any difference in quality of music but i have noticed it start, buffer, play, buffer, play..
I also am in a strong cellular spot with LTE and often 15+mb down. So i am convinced its not a thru put issue. I have not noticed it on WiFi so ill keep a look out for that.
Alpione said:
Hello all...
Has anyone else been having buffering issues at the beginning of Google Play Music streaming songs? The music will go for a second, stop, go for another couple of seconds, stop, and then play fully. This is on Normal quality and is in places where I can do a speedtest at over 10mbit/sec. Often it's 20mbit or more. It seems like this started happening when the new 3.x firmware was released. I never had buffering before.
I've tried everything from uninstalling/clearing data to clean flashing ROMs. Same thing, and it shouldn't be happening with the bandwidth I have available.
Thanks.
A
Click to expand...
Click to collapse
I've had GPM problems as well. Sometimes what you describe, sometimes the song starts, plays a few seconds then stops completely. All on good data connections, sometimes happens on WiFi. I also have the latest FW but I flashed right after I got the phone so I have nothing to compare it to.
While we're on the subject of music, does anyone experience crackling when moving the 3.5mm jack during playback? Sometimes the crackling really bothers me when I'm walking.
No crackling that im aware of on my unit.
From past experience that crackling can be from dirty connectors or a bad connection. What your hearing is the arching or electrical components momentarily loosing then regaining contact with each other. OR if it is securely connected in its possible the connector is being stressed to much and possibly coming loose from the board.
The last alternative is your headphones were not made very well and the crackling is coming from damaged or poorly soldered connection inside the male plug.
To test this out try a different cable or different wired headphones with a different cable. IF the crackling stops its your cable and not your phone connector.
I have had these start/stop issues at the beginning of tracks using both my cellular network and Wi-Fi...very strange.
I'm also experiencing this issue. It's very distracting. ARHD 21.0 on latest firmware.
Good to hear that I'm not the only one. I did a support chat with Google Play's support techs and they couldn't figure it out. Frustrating.
I've had the issue on ARHD and Venom. I was using the default modem/radio in the new international firmware and tried changing it to the latest AT&T radio. I got significantly better speeds on the AT&T radio but the skipping problem was still there.
Weird.
A
Ok, so I finally solved this after trying a ton of things.
I've got the AT&T variant and, like many of us, had been using the international firmware and ROMs (ARHD, Venom, etc.) This Google Play buffering problem seemed to start when I upgraded to the latest 3.x firmwares. I decided to test out that theory by going back to AT&T-specific firmwares and used this thread: http://forum.xda-developers.com/att...-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
I first tried wiping everything and flashing the 3.28.1540.5 firmware and ROM, which is 4.4.4 not officially released by AT&T but apparently for the identical Dev edition. Didn't work. Buffering problem was still there.
I decided to go back to total stock and flashed the officially released AT&T 4.4.3 version - 2.22.1540.4. Eureka! Everything works great now, and LTE speeds have jumped from 10-20mbit down to 30-40. That's especially interesting because I had already tried swapping out the international modem/radio with AT&T's 1.16 version. That only got me to 20. Flashing the whole firmware and stock ROM got me to 40.
So this is a good lesson - even though the phone hardware is identical and we complain about the carriers taking forever for updates, there obviously is value in what they do to optimize these ROMs for their own network.
A
I decided to go back to total stock and flashed the officially released AT&T 4.4.3 version - 2.22.1540.4.This is still us developer build:silly:. If using the build in my thread it has been modified for ATT specifically. All firmwares in my thread are for the US Developer device, but are modified for ATT as thats my carrier.
Alpione said:
Ok, so I finally solved this after trying a ton of things.
I've got the AT&T variant and, like many of us, had been using the international firmware and ROMs (ARHD, Venom, etc.) This Google Play buffering problem seemed to start when I upgraded to the latest 3.x firmwares. I decided to test out that theory by going back to AT&T-specific firmwares and used this thread: http://forum.xda-developers.com/att...-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
I first tried wiping everything and flashing the 3.28.1540.5 firmware and ROM, which is 4.4.4 not officially released by AT&T but apparently for the identical Dev edition. Didn't work. Buffering problem was still there.
I decided to go back to total stock and flashed the officially released AT&T 4.4.3 version - 2.22.1540.4. Eureka! Everything works great now, and LTE speeds have jumped from 10-20mbit down to 30-40. That's especially interesting because I had already tried swapping out the international modem/radio with AT&T's 1.16 version. That only got me to 20. Flashing the whole firmware and stock ROM got me to 40.
So this is a good lesson - even though the phone hardware is identical and we complain about the carriers taking forever for updates, there obviously is value in what they do to optimize these ROMs for their own network.
A
Click to expand...
Click to collapse
Wonders_Never_Cease said:
I decided to go back to total stock and flashed the officially released AT&T 4.4.3 version - 2.22.1540.4.This is still us developer build:silly:. If using the build in my thread it has been modified for ATT specifically. All firmwares in my thread are for the US Developer device, but are modified for ATT as thats my carrier.
Click to expand...
Click to collapse
Ha! Too damned many versions.
Regardless, I'm good to go for now.
A
So I finally received my N7 from Asus after being held hostage by Asus for 2 months for what I thought was a simple RMA exchange. When I got it back it was on Kit Kat 4.4.4 got the OTA and installed it. When LP was installed I could not log into GPS no matter what I tried to to. I factory reset, flashed custom ROM, tried the "host file trick" when I flashed KK everything ran super smooth. Log into Google and basically have a Google experience with no BS. Flashed LP and problem persisted. Finally flashed KK again set up Google and was able to enjoy N7 and all it's Googleness glory. When I got OTA I installed them and I was partially able to use google services. I could install and update apps from the play store. However, apps would often fail when trying to install/update I was also not able to watch YouTube videos or use Chromecast. Dead trigger felt like I was playing it on a gs2 than N7. So I factory reset hoping to fix this problem believing possibly KK junk the reason. With some hesitation I factory reset and now at set up I can not login into Google.
It should be noted WiFi does in fact work, I can browse what ever I want on Chrome and can download straight from chrome browser. I imagine apps like Pandora could play, and I could watch YouTube videos on the chrome browser.
What gives I know N7 is far from cutting edge but its capable enough and with no carrier bloat and the fact it has official LP 5.0.2 it should perform like a champ. I hate to say it my backup GS2 runs better on LP with far less bugs. Anyone having same issues and better yet have a solution?
Could this be hardware? If so why does KK work flawless? Before I sent it in I had LP and had no issues what so ever setting everything up. Then I get it back and lollipop is trash.
All in all I am extremely disappointed in Asus without going into it let's just say their warranty program is Anything but world class.
As right now there is a transition to Nougat on many phones (AOSP 7.1 and CM 14.1 are released, many custom ROMs are released on Nougat platform...) be aware that there is confirmed bug in Nougat BT stack: no connection / disconnections even if HU is paired with your phone.
While it is not only MTC* specific (http://bgr.com/2016/09/29/iphone-7-bluetooth-problem-bmw-ford-kia/) I can confirm it is present (I installed CM 14.1 e.g. Nougat based ROM and BT connection is not working - it pairs, it connects and disconnects in a second saying "no phone").
Existing fixes and workarounds posted here on this forum (like changing init.qcom.bt.sh file etc.) are useless.
Google confirmed bug and it is expected that fix be with next AOSP release (expected in early December) but until we see it we cannot be sure it will fix connection issues with our HUs.
Anyhow, if anyone whish to try and experiment (I dont, I wait for fix by Google first) you may try what was used to fix very similar issues on MM a year ago: changing setprop ro.bluetooth.hfp.ver 1.7 to ver 1.6 (pay attention that Nougat does not have that proprerty set at all, so the file init.qcom.bt.sh is not at same location nor the same content in N as it was on MM - but you may try with build.prop if you like to experiment).
Search the net by keywords I hinted above for links and post your results if you experiment. It may be helpful for others.
EDIT: Issue is fixed in 7.1.1 build (and CM 14.1 nightly also)!
I am suffering from the same annoying bug.
Hope that bug will be solved ASAP in the next AOSP.
Same boat.
Sent from my A0001 using XDA-Developers mobile app
me too
for me last cm14.1 version (01/12/16) from cyanogenmod site is fixed and BT is works perfect (oneplus 3)
Fixed
Latest 7.1.1 fixed bug (work also with latest CM 14.1 nightly build)
Yestarday i updated my Nexus 6p to Android 7.1.1 OTA.
After that i am having problem with my Bluetooth Car stereo Connectivity, it's connect for a second and then disconnect, It's seems to be only with my android 4.4 RK3188 car head unit, i tried a several other Bluetooth devices and i success to connect, don't know why only with my car it's not working although it works until yesterday before the 7.1.1 OTA update...
fectivi said:
Yestarday i updated my Nexus 6p to Android 7.1.1 OTA.
After that i am having problem with my Bluetooth Car stereo Connectivity, it's connect for a second and then disconnect, It's seems to be only with my android 4.4 RK3188 car head unit, i tried a several other Bluetooth devices and i success to connect, don't know why only with my car it's not working although it works until yesterday before the 7.1.1 OTA update...
Click to expand...
Click to collapse
It looks like Nexus specific issue. It may be problem with release of 7.1.1 they used for OTA.
For instance, CyanogenMod nightly fixed exactky that issue for me. Still now WiFi Hotspot is not working, but CM just fixed that bug and I hope it will be fine with next nightly. That is why I like CM! they listen, they recognise and they fix a bug in a single day. Google is on opposite side. Exactly why I don't use Nexus and I install CM based ROM first day I get new phone
Title is a little mis-leading MR P.K..
Hate to rain on your parade, but as you have been so quick to jump into other peoples threads and hand out the B.S..
You start a thread then tell people to go and do thier own research and attempt a fix you yourself have not verified will work.. tut, tut.. is this not the mark of a good software developer..
Anyway.. on the new Huawei P9 and have stayed on A.6 as for now everything is working fine for me on the big M's Rom..
Love the way you bag Google development.. of course CM is going to Cherry pick the fixs as they are a small nimble team focused on fixing and pulling apart what has been released..
They haven't released Forward versions of Android under thier own steam as yet as they just follow what has been put out..
You still got to take your hat off to Google for going toe to toe with Apple and windows to bring to the massss what we take for granted.. and might I add.. putting up billions to grab the Motorola patients so that Android continues to be free..
Looking forward to your Bluetooth stack fix's P.K so I can upgrade to A.7 ?
Sent from my EVA-L09 using Tapatalk
PK..
Light Reading off topic.
​Cyanogen to shut down services by year's end
https://www.cnet.com/news/cyanogen-to-shut-down-services-by-years-end/
Sent from my EVA-L09 using Tapatalk
Issue fixed for Nexus 6P
Hey guys,
Just a note for the ones that have Nexus 6P (no rooted) and guess Pixels phones that the BT issues are fixed when you upgrade to Nougat 7.1.2
If you have a Nexus phone (like me) just enroll to the Beta program and upgrade to 7.1.2 Just tested and BT issues with my HU is fixed.
Cheers!!!!
how do you enroll to the Beta program? Never mind. Figured it out (https://www.google.com/android/beta) and up grading my Nexus non-rooted 6P to 7.1.2 (beta program enrolled pushed OTA 7.1.2) fixed the bluetooth issue with my phone (media worked voice calls would keep dropping the bluetooth connection) to my headunit (pumpkin RK3066 MTCB-JY-v2.86 running Malaysk ROM RK3066 800X480 version 44)
I noticed a couple days ago I was getting really slow hotspot speeds. So for the last day or so, I've been testing ROMs and flashing ROMs.
Roms I have tested are:
Omni ROM 8.1 Oreo - hotspot does not even work
Nitrogen run 8.1 Oreo - hotspot does not even work
Freedom os 8.0 Oreo - very slow speed 1-3Mbps
Freedom os last nougat version - very slow speed 1-3Mbps
Stock oxygen os 8.0 Oreo stable - very slow speed 1-3Mbps
Beta 30 oxygen os Oreo - very slow speed 1-3Mbps
Beta 24 nougat oxygen os - hotspot works normal and speeds are normal
Given all these roms and flashing I've done it boils down to this in short...... If I use the beta 24 nougat, it works fine, of I use last stable nougat or above it either doesn't work or works very very very slow.
Everything phone side works fine, speeds are great. Any of the os above, be it nougat, 8.0, or 8.1 works fine without issues, no app closes nothing, but hotspot is just utterly painfully slow.
Carrier is T-Mobile. This isn't a carrier issue or hardware issue otherwise it would do the same on all roms and it does work on the one nougat oxygen os.
So my question is, what changed from the one nougat, to the other nougat and above? APN? Modem? Both?
I'm at a loss as to what is going on.
Any ideas I can try?
easyrider77 said:
I noticed a couple days ago I was getting really slow hotspot speeds. So for the last day or so, I've been testing ROMs and flashing ROMs.
Roms I have tested are:
Omni ROM 8.1 Oreo - hotspot does not even work
Nitrogen run 8.1 Oreo - hotspot does not even work
Freedom os 8.0 Oreo - very slow speed 1-3Mbps
Freedom os last nougat version - very slow speed 1-3Mbps
Stock oxygen os 8.0 Oreo stable - very slow speed 1-3Mbps
Beta 30 oxygen os Oreo - very slow speed 1-3Mbps
Beta 24 nougat oxygen os - hotspot works normal and speeds are normal
Given all these roms and flashing I've done it boils down to this in short...... If I use the beta 24 nougat, it works fine, of I use last stable nougat or above it either doesn't work or works very very very slow.
Everything phone side works fine, speeds are great. Any of the os above, be it nougat, 8.0, or 8.1 works fine without issues, no app closes nothing, but hotspot is just utterly painfully slow.
Carrier is T-Mobile. This isn't a carrier issue or hardware issue otherwise it would do the same on all roms and it does work on the one nougat oxygen os.
So my question is, what changed from the one nougat, to the other nougat and above? APN? Modem? Both?
I'm at a loss as to what is going on.
Any ideas I can try?
Click to expand...
Click to collapse
Idk mate, but I'm from the UK and I have the exact fkin problem for the past year. I haven't found any explanation or fix for this. I'm on Three UK. My only theory was that maybe my carrier is intentionally slowly down my speed, indirectly telling me that I have to buy hotspot allowance.
Nope I just did a test. I reverted back to a beta of nougat, beta 24. When I test that I get around 24Mbps, when I jump to the last nougat update, or anything Oreo, and this is with any rom even stock, I get crap speeds. I am SO pissed right now, because this same issue in 2016 plagued the 3t, and now it plagues the 3 as well as the 5, don't believe me go check 1+ forums it's littered with the same exact issue. So.... This issue was back in 2016, and they still can't fix it???!!!??? WTH.
Attached are pics..... Anything you see with high speeds is that nougat stock room. Anything slow speeds is Oreo or the last stock nougat. Any rom be it stock or custom that is like nougat 7.1.2 and above on up to anything Oreo, results in the same exact thing
I've tested this for almost 2 days with the exact same result so considering I have a strong signal and it works on that stock 7.1.1 nougat oxygen os, tells me they either screwed something up, forgot something, or changed something which results in slow speeds and hotspot speeds.
Un freeking belivable they still have not fixed this after 2 damn years.
I might also add that the screens of the laptop are hotspot of corse, and the ones that show different are from the speedtest app on my phone and screenshots of that (the ones that show a dial)