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.
Related
Thread Closed !!
New Google's Android 4.2.1 Features
-> Photo Sphere
-> Gesture Typing
-> Multi-User Support (Tablets Only)
-> Miracast Wireless Display Support
-> Daydream
-> Notification Power Controls
-> Google Now Improvements
For More Information on Which of the above features available in CyanogenMod, Come to My New Thread T989 Official CM10.1 4.2.1 Discussion (Coming Soon)
Enjoy !!! :good:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
theandroidrooter88 said:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
Click to expand...
Click to collapse
This is why i started this Thread, So we can discuss Bugs in the latest versions. :highfive:
I heard AOKP JB is stll having SODs and RRs. Do u find anything like these?
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
First we have to fix our flashing methods and recoveries used. I for one haven't experienced one single RR or SoD since I started flashing official nightlies. People are probably causing these issues themselves to begin with. Expecting a fix for an issue that has no identifiable cause.. I wonder if any other phones outside the t989 forums are experiencing RR and SoDs with Jelly Bean..
Sent from my SAMSUNG-SGH-T989 using xda premium
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
garth719 said:
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
Click to expand...
Click to collapse
Great to hear that your running latest 10-Oct Nightly. A Simple advice to you & all other users, is to restore app without data if your are using any backup tools such as TitaniumBackup etc., Restore Apps with data cause Problems.
srikanth.t989 said:
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
Click to expand...
Click to collapse
Sorry, I don't mean to crap on the thread but unless you can confidently say that SODs and RRs have been fixed (changelogs, yourself writing the code, etc.), going by your own experience shouldn't be the end-all-be-all to say whether something is fixed or not. Just like with call echo, some devices are worse than others.
I see that supposedly the issue with audio and docking has been addressed. However, the docking option is still grayed out for me when docked. Just looking for audio pass-through while docked...
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
eight_heads said:
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
Click to expand...
Click to collapse
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
I'm on recent CM10 Oct10 nightly and the BLN lights stay on, even with the Oct 7 nightly.
Update: fixed my own problems. This post helped: go to menu - systems - advanced settings - sensor and uncheck and check enable keys notifications and then send yourself a text or email. It actually should work out the box mine always has. Make sure you have notifications checked off in the apps like sms and gmail.
Also check display - notification light to make sure it enabled and you can add the apps you want to have the light enabled to work
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
garth719 said:
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
EDIT:
Just ran the music player for 45min on a run. no skips, nothing.. ran a 90 mb mp3 file too which usually gives my ipod trouble.. good sign
Click to expand...
Click to collapse
So is that how we're saying we don't get random reboots anymore? We just call them something else??
algorhythm said:
So is that how we're saying we don't get random reboots anymore? We just call them something else??
Click to expand...
Click to collapse
well there was a difference in this reboot because my phone didnt actually fully shut off. the "cyanogenmod" boot animation came up and the phone was ready to go in about 20 seconds. there was no usual vibration indicating that the phone has shut off and no "samsung" boot image as a regular reboot would do. call it what you will
Quote:
[email protected]: on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
Try updating it on the market
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Laazyboy said:
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Run only One ROM. Do a clean reflash. We are not experiencing any SODs or RRs. Use only one ROM because Flashing different ROMs one after the Other will Make your device weak. The data left by the AOKP causes some errors to CM10. Thats why i said that don't restore the apps with data.
So there's been a lot buzz lately about the bugs that are present in the latest build. Therefore, I'm going to maintain the thread to keep track of it all.
RULES:
-This is not a thread for feature requests. It's a thread for bugs, issues, and problems only!
-Before posting, you must swear under oath and punishable by law, that you are referring to a fresh installation and not a dirty flash (a fresh flash can alleviate a lot of the intermittent problems you may be having)
-In order to be a bug, it has to be confirmed by other users under same conditions
Please make sure to actually test bugs instead of saying yes yes yes. I will try to test each bug, but I'm relying on people's integrity as well. We don't want devs wasting time trying to fix something that isn't properly broken. So ensure that your bugs are legit and reproducible. Also, logcats where possible would be an amazing help too. I'm only adding bugs OP that are confirmed by at least a couple users. If it's not in the OP, it's not official.
Current bug list in no particular order:
Lock screen takes a while to draw
GPS works but reports 0-2 satellites only, NMEA data stream seems to be incorrect, so parsing this data may be touchy in some apps
Face unlock doesn't work
Autobrightness is choppy and slow
Pictures from camera show up in the wrong orientation from how they were taken
Bluetooth for headsets does not work, but may work connecting to GPS, etc.
Audio in skype is messed up
Gallery picture editing
Sound delay in calls
Work in progress...
FIXED (latest build)
Music skip/stutter when screen is off
Tethering is broken - M3 Build - thanks budor
No audio in video recording
Data usage/tracking does not work in the settings menu
Keyboard crashes
Current news...
Bluetooth is still broken
New build has an updated kernel with ota support
They are closing in on the audio issues
Stay tuned for a fresh build when the new monthly is released
For the record: this is on CM10.1, on the Samsung Captivate Glide, using the recent 4.2.2 update dated 2/17/2013
- Bluetooth Headset profile doent work
- Audio in video recording not working
- Photosphere unavailable
- audio stutters if screen is turned off (seems to be a CPU sleeping issue)
- Something (i am suspecting Google+, even though i am not actively using it) is filling up my SD card with gigabytes of thumbnails, which i have to delete manually
- lockscreen takes too long to appear
- from 4.2.1 to 4.2.2 the mount point of the external SD card changed again (so 'acast' cant find my downloaded podcasts). Not a bug per se, but a symlink would've been nice?
- auto-brightness is choppy and slow
- GPS usually get a lock in an okay-ish timeframe, but always reports that it's only locked to "0 / 2 satellites"
- face unlock doesnt work (hangs when opening the camera)
- orientation issues when taking photos: if i take a photo in landscape mode, it ends up in portrait mode in the gallery, and vice versa
Since i guess and hope many people will report bugs, and some of them will be not reproducable by others, we should have some mechanism to 'vote' or 'confirm' bugs, i guess?
All of the above...
Connecting to PC with USB, MTP mode does NOT work (it did work in Adam77root's last CM10.1 build ...)
Email - Any mail delivered into sub folders (Using Push MS Exchange) doesn't create a notification.... I miss a lot of email when sorting via rules on delivery. This is new in JB.
Some apps are deleted after reboot. (temporary fix is manually move to sdcard)
The phone connection will drop randomly and not come back until I reboot the phone. Note that I am using a Rogers (Canadian) model, if it has any relevance. Let me know how I can help you diagnose this bug.
mschweini said:
For the record: this is on CM10.1, on the Samsung Captivate Glide, using the recent 4.2.2 update dated 2/17/2013
- Audio in video recording not working
Click to expand...
Click to collapse
+1
- lockscreen takes too long to appear
Click to expand...
Click to collapse
+1
- from 4.2.1 to 4.2.2 the mount point of the external SD card changed again (so 'acast' cant find my downloaded podcasts). Not a bug per se, but a symlink would've been nice?
Click to expand...
Click to collapse
+1, using Directory Bind as a replacement
- auto-brightness is choppy and slow
Click to expand...
Click to collapse
+1
- GPS usually get a lock in an okay-ish timeframe, but always reports that it's only locked to "0 / 2 satellites"
Click to expand...
Click to collapse
GPS lock timeframe +1, not sure about the report
- face unlock doesnt work (hangs when opening the camera)
Click to expand...
Click to collapse
+1
- orientation issues when taking photos: if i take a photo in landscape mode, it ends up in portrait mode in the gallery, and vice versa
Click to expand...
Click to collapse
+1
yohan4ws said:
Some apps are deleted after reboot. (temporary fix is manually move to sdcard)
Click to expand...
Click to collapse
For me, some apps are weird and are missing icons: http://i.imgur.com/CNZ5Nwq.png
face unlock does not work, but it's not that important, just to mention it.
OP updated. Please make sure to actually test bugs instead of saying yes yes yes. I will try to test each bug, but I'm relying on people's integrity as well. We don't want devs wasting time trying to fix something that isn't properly broken. So ensure that your bugs are legit and reproducible. Also, logcats where possible would be an amazing help too. I'm only adding bugs OP that are confirmed by at least a couple users. If it's not in the OP, it's not official.
Sent from my SGH-I927 using Tapatalk 2
Just thought that I would mention that I've noticed that the audio stutter is even more noticeable when the phone is plugged into something using a line in instead of headphones. I'm not sure if this is a issue specific to my device, but if I use a patch cord (audio cable, but w/o the extra contact for a remote) the music sometimes stops altogether, and rarely resumes. This happens whether the screen is on or off. Bluetooth audio stream however is completely fine. No stutter even if screen is off.
Devian50 said:
Just thought that I would mention that I've noticed that the audio stutter is even more noticeable when the phone is plugged into something using a line in instead of headphones. I'm not sure if this is a issue specific to my device, but if I use a patch cord (audio cable, but w/o the extra contact for a remote) the music sometimes stops altogether, and rarely resumes. This happens whether the screen is on or off. Bluetooth audio stream however is completely fine. No stutter even if screen is off.
Click to expand...
Click to collapse
I've never had it stop on me all together.
I feel like this thread should be in the dev section, no? Flag this thread to move it if you think so
Sent from my SGH-I927 using Tapatalk 2
Please don´t throw stones, but bluetooth is or isn´t working? I´d like to try CM 10.1 but I need bluetooth working to use the phone while driving.
brunobbarcelos said:
Please don´t throw stones, but bluetooth is or isn´t working? I´d like to try CM 10.1 but I need bluetooth working to use the phone while driving.
Click to expand...
Click to collapse
2nd post ... says Bluetooth headset profile doesn't work .. this means you can stream Audio to your car's stereo, but you can NOT use your headset... I'm going to assume it's the same accross all ROMs that you can HEAR the other person talk, but the microphone via bluetooth isn't enabled.... my other assumption is that it has to do with the sound driver issues of using skype etc. where when the microphone is activated, all other sound output becomes sloooow motion. -
These are assumptions based on an under educated hypothesis .. a guess.. a shot in the dark ... based on no fact .. and hence, could be completely entirely wrong
Here's a thought, though, why don't you do a nandroid backup in CWM one evening, download the CM10.1 and install it and play with it test bluetooth and some other things, report your findings and if bluetooth deosn't work, revert back to your backup... nothing lost and everything to gain PLUS you'll be helping out the community.
gtmaster303 said:
I've never had it stop on me all together.
I feel like this thread should be in the dev section, no? Flag this thread to move it if you think so
Sent from my SGH-I927 using Tapatalk 2
Click to expand...
Click to collapse
The reason it isn't in the dev section is because it isn't actually a dev thread. The dev section is more for an actual product, whereas this is more documentation for a product, meant to answer questions people might otherwise ask in the general section.
Any of you guys use Whatsapp? It will tell you that tablets are not supported.. :/
And the main Google search app (where you can't type more than one letter from the homescreen) always closes.
Great work BTW. I just got this this afternoon. I'm loving how smooth it is
Sent from my SGH-I927 using xda app-developers app
chrisyjwai said:
Any of you guys use Whatsapp? It will tell you that tablets are not supported.. :/
And the main Google search app (where you can't type more than one letter from the homescreen) always closes.
Great work BTW. I just got this this afternoon. I'm loving how smooth it is
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Whatsapp works for me.
You can fix the google search app by disabling the hotword feature.
Snuuuuupy said:
Whatsapp works for me.
You can fix the google search app by disabling the hotword feature.
Click to expand...
Click to collapse
Yea. Sorry my bad. I had no service at that point. The app could not verify a network and assumed it was a tablet.
Thanks.
Okay. So basically I flash this firmware and before I proceed to use any of the apps I decide to update them. So while the outdated search app still had the hotwords feature on, I updated it. Thereafter, the app will close even before I could get to the setting menu. So the only way is to either use the older version or use the older version to turn off the hotwords feature and update. I know this is minor. Just thought I'd add this to a bugs thread.
And there are some speaker/microphone issues with google hangouts.
Anyone second this?
Sent from my SGH-I927 using xda app-developers app
chrisyjwai said:
Okay. So basically I flash this firmware and before I proceed to use any of the apps I decide to update them. So while the outdated search app still had the hotwords feature on, I updated it. Thereafter, the app will close even before I could get to the setting menu. So the only way is to either use the older version or use the older version to turn off the hotwords feature and update. I know this is minor. Just thought I'd add this to a bugs thread.
And there are some speaker/microphone issues with google hangouts.
Anyone second this?
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Open up the older one. Don't update, disable hotwords and that new google feature (cards?). Update, should work fine.
Tethering
Tethering is broken, I didn't see it in the list. Even FoxFi doesn't work.
Hi!
Sorry for posting here, but as newby I'm not allowed to post in development section.
I have an P936 which runs fine with PAC-ROM. I only get a reset sometimes, but no BSODs. The only problem for me is that bluetooth doesn't run well. I can connect to my car hands free, but disconnecting and reconnecting doesn't work well. Sometimes I have to reboot the phone to get it reconnected.
It worked fine with WIND-kernel 1.91 but not with 2.X nor stock kernel. With the latest PAC versions (it started in May) I get a bluescreen when I flash WIND kernel 1.91, I can only use kernel 2.X.
I have now flashed CM 10.1.0 stable and it works well with Wind kernel 1.91 besides a short blue "flashing" between LG and CM boot logo. BT works well again, no problems with dis- or reconnecting.
So, as I would like to use PAC-ROM again, how can I get WIND-kernel 1.91 run with it? Or is it possible, to get the BT functionality back to kernel 2.X?
BT problem solved?!
meister61 said:
Hi!
Sorry for posting here, but as newby I'm not allowed to post in development section.
I have an P936 which runs fine with PAC-ROM. I only get a reset sometimes, but no BSODs. The only problem for me is that bluetooth doesn't run well. I can connect to my car hands free, but disconnecting and reconnecting doesn't work well. Sometimes I have to reboot the phone to get it reconnected.
It worked fine with WIND-kernel 1.91 but not with 2.X nor stock kernel. With the latest PAC versions (it started in May) I get a bluescreen when I flash WIND kernel 1.91, I can only use kernel 2.X.
I have now flashed CM 10.1.0 stable and it works well with Wind kernel 1.91 besides a short blue "flashing" between LG and CM boot logo. BT works well again, no problems with dis- or reconnecting.
So, as I would like to use PAC-ROM again, how can I get WIND-kernel 1.91 run with it? Or is it possible, to get the BT functionality back to kernel 2.X?
Click to expand...
Click to collapse
Today I could install WIND 1.91 with latest PAC and only get the short blue flash before PAC-logo. Fine! Must be the changes in CM 10.1?
The causes of short blue screen or black/blue screen forever is due to the display driver changes in kernel AND rom.
It is always suggested to use latest cm + kernel.
Otherwise not guarantee it works well.
I dont use BT.
I think BT in wind kernel should work as same as CM.
Sent from my LG-SU640 using xda premium
lyfkevin said:
The causes of short blue screen or black/blue screen forever is due to the display driver changes in kernel AND rom.
It is always suggested to use latest cm + kernel.
Otherwise not guarantee it works well.
I dont use BT.
I think BT in wind kernel should work as same as CM.
Sent from my LG-SU640 using xda premium
Click to expand...
Click to collapse
Hi Lyfkevin!
Thanks for answering. The point is that I need BT for hands-free in my car. You changed BT from 1.91 to 2.X to CM-Mode, but 1.91 is the only version that works without problems for me. In all other kernels (CM or WIND) I have problems to disconnect and reconnect.
But since CM 10.1 (and new PAC) 1.91 works again without blue screen. I had two resets (UI) in five minutes yesterday, but after that there was no reset nor BSOD or force close apps. I changed to 432/1458Mhz and badass/sio again as I had before kernel 2.X and battery was at 53% after 12 hours with some heavy testing yesterday
meister61 said:
Hi Lyfkevin!
Thanks for answering. The point is that I need BT for hands-free in my car. You changed BT from 1.91 to 2.X to CM-Mode, but 1.91 is the only version that works without problems for me. In all other kernels (CM or WIND) I have problems to disconnect and reconnect.
But since CM 10.1 (and new PAC) 1.91 works again without blue screen. I had two resets (UI) in five minutes yesterday, but after that there was no reset nor BSOD or force close apps. I changed to 432/1458Mhz and badass/sio again as I had before kernel 2.X and battery was at 53% after 12 hours with some heavy testing yesterday
Click to expand...
Click to collapse
I will consider rolling back to 1.91 BT driver.
P.S. Badass is an awesome governor (3 phase) for non-gaming uses.
lyfkevin said:
I will consider rolling back to 1.91 BT driver.
P.S. Badass is an awesome governor (3 phase) for non-gaming uses.
Click to expand...
Click to collapse
2.X with 1.91 BT driver could be great, thanks!
Today I went on testing after installing PAC-nightly p930 20130628: booting with that short blue "flash", everything went fine. Turning device horizontically/vertically when watching video resulted in crashes and two UI-resets. Changing "debug.compositon.type" to "c2d" and "debug.mdpcomp.maxlayer" to"2" in build.prop helped, no more crashes nor resets since then. Nearly four hours with watching video (and turning!), BT, GPS, Wifi. data testing, gaming a bit, benchmarking (Antutu, about 10% less performance than before) with brightness set to 25% - battery has 60% left. I think it's okay for that heavy use?!
It looks like I have found my stable daily use ROM and kernel!
meister61 said:
2.X with 1.91 BT driver could be great, thanks!
Today I went on testing after installing PAC-nightly p930 20130628: booting with that short blue "flash", everything went fine. Turning device horizontically/vertically when watching video resulted in crashes and two UI-resets. Changing "debug.compositon.type" to "c2d" and "debug.mdpcomp.maxlayer" to"2" in build.prop helped, no more crashes nor resets since then. Nearly four hours with watching video (and turning!), BT, GPS, Wifi. data testing, gaming a bit, benchmarking (Antutu, about 10% less performance than before) with brightness set to 25% - battery has 60% left. I think it's okay for that heavy use?!
It looks like I have found my stable daily use ROM and kernel!
Click to expand...
Click to collapse
Thanks for your info, I have some problem in 2.X too, but not in BT, my systemUI always can't load on reboots after 2.X . It was find in 1.X , If 1.9 is OK for CM 10.1 stable /PAC .I think I should have a try on this
Sent from my Nexus 7 using xda app-developers app
Hi @meister61
Thanks for supporting.
Check this out. Hope it helps
http://forum.xda-developers.com/showpost.php?p=43071295&postcount=648
Hi lyfkevin!
BT works flawlessly. I tried with car hands-free an laptop, connect/disconnect/reconnect directly. Great job!
When installing 2.41 first I got stuck in PAC bootlogo. Pac ran and ran and ran for about ten minutes, then I decided to reset. Second boot the same and even booting in CWM and installing 1.91 didn't work. So I decided to restore the backup I took just before installing 2.41 (yes, I'm a good guy!) abd I could boot again. I installed 2.41 again and this time I didn't set "fix permissions" in CWM. Then everything went fine! Is it possible that this was the problem? I always used to do that before...
I left the settings badass/sio and 432/1458 and the for four hours now there was no remarkable issue! Maybe I'll test other settings when I'm sure that this works stable und look after power consumption and stability.
Thanks for your great work!
Just recived the july patch some minutes ago
no changelog
Good day.
Me too. Probably July security patches only.
I'm hoping that this time they fix the wifi problem. :fingers-crossed:
noideaforaname said:
Just recived the july patch some minutes ago
no changelog
Click to expand...
Click to collapse
Same here with Customized_DE
Battery and others
noideaforaname said:
Just recived the july patch some minutes ago
no changelog
Click to expand...
Click to collapse
Some users are saying that the battery for standby time has improved, the Camera seems to be unable to take pictures and camera distortion is back.
www[dot]xperiablog[dot]net/
BearyBeary said:
Some users are saying that the battery for standby time has improved, the Camera seems to be unable to take pictures and camera distortion is back.
Click to expand...
Click to collapse
I read one user complaining of that on the comments for the update at that site. Just one. Not sure the camera thing is a crisis. Since I'm on the US version and our updates seem to follow a few weeks later, I can't say that with personal confirmation though.
I'm in France and I haven't received the June security patch, and I haven't received this one yet :/
BearyBeary said:
Some users are saying that the battery for standby time has improved, the Camera seems to be unable to take pictures and camera distortion is back.
www[dot]xperiablog[dot]net/
Click to expand...
Click to collapse
For me the battery seems to drain much faster
_Nexus8_ said:
I'm in France and I haven't received the June security patch, and I haven't received this one yet :/
Click to expand...
Click to collapse
I am in france too. I have got the june patch, but not july.
Burn02 said:
I am in france too. I have got the june patch, but not july.
Click to expand...
Click to collapse
Weird, I'm still with May patch
with this update I can not take pictures anymore. the video works but no more photo. do not install it ..
with this update my battery drains 28% overnight. GPS,BT,WLAN turned off, stamina mode. no consuming apps. it was 4-5% after 205 update and nearly 20% 145update, 119update was fine. cant believe sony. I/m 39years old, not youngster, and phone holding 12hours with no internet browsing and few calls is joke.
elviukai said:
with this update my battery drains 28% overnight. GPS,BT,WLAN turned off, stamina mode. no consuming apps. it was 4-5% after 205 update and nearly 20% 145update, 119update was fine. cant believe sony. I/m 39years old, not youngster, and phone holding 12hours with no internet browsing and few calls is joke.
Click to expand...
Click to collapse
Sounds like a Google Play Services problem, along with RCSservice.
There are some tips in this thread
When GPS starts acting up it's usually syncronisation errors, sometimes it's down to bad reception or it's just gone and tied itself up in knots.
Try uninstalling your Google account. Then go into airplane mode. Delete the app data for
Google Backup transport
Google Play Services
Google Play store
Google Services Framework
Restart your phone
Enable the network
Log into your Google account again
Keep on the wifi for ten minutes or so to let everything sync with no errors.
This will force the phone to re syncronise with fresh data. Hopefully squashing the Play Services error that's causing your power drain.
The other thing to try is download Google Play Services Beta from APK mirror. Download it, go into airplane mode, install it, then repeat steps listed above.
I still have great battery life und still can make great Pictures
Look 13h39min standy and 3h Screen on, and WiFi on all time, surfing on internet, watching small videos etc. and still 80%.
Camera works fine for me and battery is better than on the June patch so far.
elviukai said:
with this update my battery drains 28% overnight. GPS,BT,WLAN turned off, stamina mode. no consuming apps. it was 4-5% after 205 update and nearly 20% 145update, 119update was fine. cant believe sony. I/m 39years old, not youngster, and phone holding 12hours with no internet browsing and few calls is joke.
Click to expand...
Click to collapse
I have same problem. I have been searching for months with no solution.
Customised De. I have update... 235. Have no issues.
Customized IT .235 here, updated with XperiFirm+Newflasher and then rooted through xperiafix 3.0, everything working fine.
Just a little OT question: which combination of Magisk+Xposed is working for you guys?
chichino84 said:
Customized IT .235 here, updated with XperiFirm+Newflasher and then rooted through xperiafix 3.0, everything working fine.
Just a little OT question: which combination of Magisk+Xposed is working for you guys?
Click to expand...
Click to collapse
I tried Magisk 16.6 and found that I lost DRMfix. I tried downloading the zip and flashing with Xperiafix 3, but same result. The only version that worked was 16.3.
Xposed v90.2 beta3 doesn't work on any firmware newer than April, that said there is some feedback on the XZ Permium thread that V90.2 beta2 does work on later firmware, but a number of modules fail to load afterwards.
I am on old .75 firmware, Xposed works and I can't be bothered to chase the constant upgrades trail any more.
Maybe if P ever comes to the XZ1c I might think about it, but historically, version changes of android that are different from the original released version that came with the hardware always run badly and use more battery.
Didgesteve said:
I tried Magisk 16.6 and found that I lost DRMfix. I tried downloading the zip and flashing with Xperiafix 3, but same result. The only version that worked was 16.3.
Xposed v90.2 beta3 doesn't work on any firmware newer than April, that said there is some feedback on the XZ Permium thread that V90.2 beta2 does work on later firmware, but a number of modules fail to load afterwards.
I am on old .75 firmware, Xposed works and I can't be bothered to chase the constant upgrades trail any more.
Maybe if P ever comes to the XZ1c I might think about it, but historically, version changes of android that are different from the original released version that came with the hardware always run badly and use more battery.
Click to expand...
Click to collapse
That was a silly mistake from me, just pulled the OTA update when the phone was right out of the box without checking last incompatibilities and issues.
So it seems that the only route to have full things right it's a downgrade. And I suppose it's impossible without a full wipe, am I correct?
chichino84 said:
That was a silly mistake from me, just pulled the OTA update when the phone was right out of the box without checking last incompatibilities and issues.
So it seems that the only route to have full things right it's a downgrade. And I suppose it's impossible without a full wipe, am I correct?
Click to expand...
Click to collapse
I think you can use Sonys Emma to downgrade, but as I've not used it, I don't know if you can keep your data partition. Sorry.
To recap: firmware. 75 and Xposed 16.3 works perfectly, modules work ok.
Hello, I just received MIUI 11.0.2.0 based on Android 10 Stable, so I'm wondering if it is safe to update, I'm afraid that after updating the battery will drain faster as it usually happens, do you have any info about this?
HELLO!! I update my RN8P to android 10.0.2.0 QGGEUXM and the battery is very good as the android 9 :good: don't be Afraid ?
jimkan said:
HELLO!! I update my RN8P to android 10.0.2.0 QGGEUXM and the battery is very good as the android 9 :good: don't be Afraid
Click to expand...
Click to collapse
Update just showed up, is it worth? any audio improvement?
Update and don't be afraid ...?
jimkan said:
HELLO!! I update my RN8P to android 10.0.2.0 QGGEUXM and the battery is very good as the android 9 :good: don't be Afraid
Click to expand...
Click to collapse
After the upgrade the phone cannot connect anymore with the Bluetooth of my Ford C-Max (2011, it cannot be updated and I cannot update the car yet).
Is it happening to anyone else?
jimkan said:
HELLO!! I update my RN8P to android 10.0.2.0 QGGEUXM and the battery is very good as the android 9 :good: don't be Afraid ?
Click to expand...
Click to collapse
Well I have worse battery live on Android 10.
Something keeps phone awake and drain battery.
I have about 1 or 2 hours less SOT.
Looking for solution. ?
I ended up upgrading, at first, my phone was lagging when scrolling in any app, and the battery was somehow draining a bit faster but I managed to fix it.
Try this if you have a related problem.
-Go into developer settings
-Scroll almost to the button
-Disable MIUI optimization
-Reboot
-Enable MIUI optimization
-Reboot
Also, the permission of most of my apps got lost, like access to the microphone, storage, phone... so I had to re-enable them manually because they were "blocked".
For those experiencing problems, it's probably worth doing a full wipe. I tend to find its needed after as version update of Android.
I did a wipe and haven't encountered problems as of yet. Bluetooth, apps and battery all fine for me.
Kev23 said:
For those experiencing problems, it's probably worth doing a full wipe. I tend to find its needed after as version update of Android.
I did a wipe and haven't encountered problems as of yet. Bluetooth, apps and battery all fine for me.
Click to expand...
Click to collapse
Did a full wipe after the android 10 update and for now batterylife shortened for me. Hopefully after a few charges it will be better again.
gee2012 said:
Did a full wipe after the android 10 update and for now batterylife shortened for me. Hopefully after a few charges it will be better again.
Click to expand...
Click to collapse
You can do that also for fix battery drain...
[MIUI with Tom #8] FIX battery Drain in MIUI - after OTA or after reset to factory settings! https://c.mi.com/thread-2834067-1-0.html?t=1583590560499
littleleaf said:
After the upgrade the phone cannot connect anymore with the Bluetooth of my Ford C-Max (2011, it cannot be updated and I cannot update the car yet).
Is it happening to anyone else?
Click to expand...
Click to collapse
I didn't get much feedback so I suppose it isn't a very popular issue. However, I've a solution to share for the annoying problem.
After doing a full wipe of the phone the issue was still present and I was still facing connection problems.
So I enabled the developers options menu and started to play with Bluetooth hidden settings.
At first I downgraded the AVRCP version from the default 1.4 version to 1.3 but it was not working, so I tried 1.5 (same issue) and 1.6. This version was slightly better... The car was authenticating and showing the Bluetooth audio codec in a small icon beneath the device name (Ford Audio -> SBC) but the connection was not stable and dropping. So I changed the default audio codec and I set SBC.
Everything started to work well and I was able to make several hands free call without issues anymore.
I hope it helps whoever could have similar issues.
Angelo
littleleaf said:
I didn't get much feedback so I suppose it isn't a very popular issue. However, I've a solution to share for the annoying problem.
After doing a full wipe of the phone the issue was still present and I was still facing connection problems.
So I enabled the developers options menu and started to play with Bluetooth hidden settings.
At first I downgraded the AVRCP version from the default 1.4 version to 1.3 but it was not working, so I tried 1.5 (same issue) and 1.6. This version was slightly better... The car was authenticating and showing the Bluetooth audio codec in a small icon beneath the device name (Ford Audio -> SBC) but the connection was not stable and dropping. So I changed the default audio codec and I set SBC.
Everything started to work well and I was able to make several hands free call without issues anymore.
I hope it helps whoever could have similar issues.
Angelo
Click to expand...
Click to collapse
Today I discovered that settings changed in the developer menu are not persistent and don't survive to a phone reboot. So every time I get in the car I've to repeat settings.
This is quite annoying, any solutions other than waiting for another software update?
Another alternative would be changing the car, but it's more expensive than buying another mobile phone.
Danchibald said:
You can do that also for fix battery drain...
[MIUI with Tom #8] FIX battery Drain in MIUI - after OTA or after reset to factory settings! https://c.mi.com/thread-2834067-1-0.html?t=1583590560499
Click to expand...
Click to collapse
Tried this, still seeing high Android OS drain
gee2012 said:
Did a full wipe after the android 10 update and for now batterylife shortened for me. Hopefully after a few charges it will be better again.
Click to expand...
Click to collapse
Think you are right on the battery. Mine has settled down and not as good as before
I think after few cycles of charging it will be better...
littleleaf said:
After the upgrade the phone cannot connect anymore with the Bluetooth of my Ford C-Max (2011, it cannot be updated and I cannot update the car yet).
Is it happening to anyone else?
Click to expand...
Click to collapse
Me too...
I've got a Ford Focus with Sync 1.1, and have got issues with bluetooth. First of all, my car can't recognize signal level and i've got problem making calls and closing calls...
ScanaX said:
Me too...
I've got a Ford Focus with Sync 1.1, and have got issues with bluetooth. First of all, my car can't recognize signal level and i've got problem making calls and closing calls...
Click to expand...
Click to collapse
Changing profiles in the developer menu is not helping... I was able to make a couple of calls, no more. Connection is continuously dropping.
Full wipe was not a solution. Before the upgrade I never had a disconnection.
I also tested a couple of Bluetooth profiles apps, including Android Auto, but no luck.
I think we need a fix ASAP.
Is there an official support site where to make complaints regarding this update?
Ever since I updated to 11.0.3.0PGGEUXM I've been unable to use one of my wallet apps (bbva wallet), and am afraid something else breaks if I update; has anyone from Mexico updated and been able to use it again, along with citibanamex pay?
littleleaf said:
Changing profiles in the developer menu is not helping... I was able to make a couple of calls, no more. Connection is continuously dropping.
Full wipe was not a solution. Before the upgrade I never had a disconnection.
I also tested a couple of Bluetooth profiles apps, including Android Auto, but no luck.
I think we need a fix ASAP.
Is there an official support site where to make complaints regarding this update?
Click to expand...
Click to collapse
I'm opening a ticket reporting this issue with my phone...
I hope It will work
After 20 days I decided to downgrade back to MIUI V11.0.3.0PGGEUXM based on android 9, the only thing I liked about android 10 was the dynamic MAC address but it didn't compensate the high battery drain from the Android System, with up to 9-10 hours of CPU usage and about 6-6:30 hours of Screen-on time. I will test how many hours of SOT I have now.