Related
This thread is for UNOFFICAL CM10.1 Builds. All are welcome to post their builds! You can find many of us in IRC, freenode #verizons3.
Other Threads of Interest
OFFICIAL CM10.1 builds - [OFFICIAL]CM10.1 Official Nightlies for D2VZW GSIII
Q&A Thread for CM10.1 - [Official] CM 10.1 Q&A Thread.
Linaro unofficial builds - [UNOFFICIAL][LINARO]CM10.1 UNOFFICIAL builds w/ Linaro for D2VZW
My 'semi'daily builds.
Here is my 7/31 build. Repo Sync @ around 11:00 AM EST
This ROM now uses a service from www.romdashboard.com that allows instant notifications and downloads of my daily updates. You will see an app in your app-drawer that enables this service called "ROMdb Dev Tool". Please don't remove this unless you don't want to use the notification service. No other mods are built in so if you block/delete/freeze that app, that should be the end of it. When an update is uploaded, you will get a notification that an update is ready. Click download and you are ready to go. The ROM gets downloaded to /sdcard/download folder.
Download - http://bit.ly/1cooKbo / MD5SUM - 88fe3b9d2b4c3988ac449f0572005894
Recommended GAPPS (20130301) - http://bit.ly/13Mcy2N
Recommended Firmware (VRBMF1) - http://bit.ly/1aIhVR3
Recommended Firmware (VRBMB1) - http://bit.ly/1b08F8h
New favorite boot animation (flash in recovery) - http://bit.ly/13Gnle3
Cherry Picks:
Mms: Add the ability to select recipients from a checkbox list - http://review.cyanogenmod.org/#/c/34094/
Show advanced reboot if using an insecure lock screen - http://review.cyanogenmod.org/#/c/45936/
Reverts:
http://review.cyanogenmod.org/45566
http://review.cyanogenmod.org/45565
Uncommited Tweaks
Tweaked MMS image attachment size (attachment size limit, dimensions, user-agent and UAProf)
re-enabled Standalone Power Collapse - was disabled by cyanogen a few months back, just testing to see if anything bad happens turning it back on
tweaked LTE signalbar display
Enjoy!
Thanks, masta! You're CM10.1 build is the best I've come across, easily a daily driver. Thanks for all that you do!
So just FYI I've got (on a CM derived ROM) audio working perfectly (and confirmed by multiple people) with no lags or stuttering. This includes bluetooth streaming, talking, etc. In call volume is working perfectly as is speakerphone. If you need any help mastamoon getting it working on your builds let me know I'll be happy to help.
termleech said:
So just FYI I've got (on a CM derived ROM) audio working perfectly (and confirmed by multiple people) with no lags or stuttering. This includes bluetooth streaming, talking, etc. In call volume is working perfectly as is speakerphone. If you need any help mastamoon getting it working on your builds let me know I'll be happy to help.
Click to expand...
Click to collapse
Well this would just be awesome. This is exactly what I'm looking for, a build with all of these things working. I was so happy when BT audio worked in the beginning, and then they borked it in the name of open source lol.
And the worst part is JB TW ROMs crackle on BT for me, but ICS roms are fine, which makes no sense whatsoever but whatever.
Sweet, I've used your build before. Now has the most recent ones fixed the weak signal issues? I have full bars where I am now on 4.1.2, but with 4.2 before I had 0-1
Recon0212 said:
Sweet, I've used your build before. Now has the most recent ones fixed the weak signal issues? I have full bars where I am now on 4.1.2, but with 4.2 before I had 0-1
Click to expand...
Click to collapse
Probobly not as the RIL is still a mess on 4.2 for the d2.
I know the CM guys are working on (invisiblek) so hopefully we'll have some stuff ironed out soon.
M Diddy said:
Probobly not as the RIL is still a mess on 4.2 for the d2.
I know the CM guys are working on (invisiblek) so hopefully we'll have some stuff ironed out soon.
Click to expand...
Click to collapse
Figured, it's a shame, I really like CM10.1
Masta,
One thing. I'm on your 1-10 build and everything is gravy, except battery life. For some reason, Maps is using a lot of battery even though I haven't even opened the app. Any idea what's causing that?
M Diddy said:
Masta,
One thing. I'm on your 1-10 build and everything is gravy, except battery life. For some reason, Maps is using a lot of battery even though I haven't even opened the app. Any idea what's causing that?
Click to expand...
Click to collapse
I hear opening and closing Maps fixes battery drain. I keep maps frozen on my phone to stop all battery drain from location services. I don't think anything I pick/reverted should cause battery issues, but one never knows.
M Diddy said:
Probobly not as the RIL is still a mess on 4.2 for the d2.
I know the CM guys are working on (invisiblek) so hopefully we'll have some stuff ironed out soon.
Click to expand...
Click to collapse
There are a couple things recently merged into CM that will help with that and a couple cherry picks you can do. My signal on my build is as good as it was on 4.1.
Masta, thanks for the builds. I've been on your stuff mostly since 12-18 official, which I downgraded to your unofficial. Only thing that really bothers me and my wife is the low volume on video recording. 12/17 everything was fine, but by 12/27 everything was soft. I've been dirty flashing (occasionally wiping cache/dalvik, but not data) since CM 10 back in August/September. Any idea on what's going on and why your original unofficial cm 10.1 builds worked but now they've stopped?
fluffman86 said:
Masta, thanks for the builds. I've been on your stuff mostly since 12-18 official, which I downgraded to your unofficial. Only thing that really bothers me and my wife is the low volume on video recording. 12/17 everything was fine, but by 12/27 everything was soft. I've been dirty flashing (occasionally wiping cache/dalvik, but not data) since CM 10 back in August/September. Any idea on what's going on and why your original unofficial cm 10.1 builds worked but now they've stopped?
Click to expand...
Click to collapse
Hey, thanks!
That was around the time that BT audio and such died.. so maybe these audio related reverts fix that also. Give my next build a try and let us know how recording is. My phone has always seems to have ok recording volume, through both clean and dirty flashing officials and unofficials.
termleech said:
So just FYI I've got (on a CM derived ROM) audio working perfectly (and confirmed by multiple people) with no lags or stuttering. This includes bluetooth streaming, talking, etc. In call volume is working perfectly as is speakerphone. If you need any help mastamoon getting it working on your builds let me know I'll be happy to help.
Click to expand...
Click to collapse
Have you released this if so where? I didn't see anything other than your Nexus 7 stuff.
Running Mastamoon's build from the 10th, I'm seeing that when I walk in to work and in to wifi coverage, it takes a while for my wifi symbol to turn blue. This is a similar issue of when I walk out of the parking garage, it takes a bit for the 3G/4G symbol to turn blue - and I'm totally blocked from doing data during this time. Is this known about? What must I provide log wise to help diagnose this?
Here is my daily unofficial build for 01/11, Repo Sync as of 3:00PM EST - http://d-h.st/vnw
Cherry Picks:
GPS - http://review.cyanogenmod.org/#/c/29349/
RIL - http://review.cyanogenmod.org/#/c/28195/
RIL - http://review.cyanogenmod.org/#/c/29653/
RIL - http://review.cyanogenmod.org/#/c/29654/
Bluetooth - http://review.cyanogenmod.org/#/c/29952/
Bluetooth - http://review.cyanogenmod.org/#/c/29951/
Bluetooth - http://review.cyanogenmod.org/#/c/29950/
Reverts:
Audio - http://review.cyanogenmod.org/#/c/29175/ - Fixes Bluetooth/A2DP Streaming
Audio - http://review.cyanogenmod.org/#/c/29174/ - Fixes Bluetooth/A2DP Streaming
Audio - http://review.cyanogenmod.org/#/c/29661/ - Fixes In Call Volume Adjustment
As always check here to see what my repo sync may have missed: CM Gerrit - Merged
Enjoy!
mastamoon said:
I hear opening and closing Maps fixes battery drain. I keep maps frozen on my phone to stop all battery drain from location services. I don't think anything I pick/reverted should cause battery issues, but one never knows.
Click to expand...
Click to collapse
I've tried that but it still drains on maps and location services. I have found that a reboot almost always fixes it. When it doesn't I just freeze it in TiB as well.
mastamoon said:
Here is my daily unofficial build for 01/11, Repo Sync as of 3:00PM EST - http://d-h.st/vnw
Cherry Picks:
GPS - http://review.cyanogenmod.org/#/c/29349/
RIL - http://review.cyanogenmod.org/#/c/28195/
RIL - http://review.cyanogenmod.org/#/c/29653/
RIL - http://review.cyanogenmod.org/#/c/29654/
Bluetooth - http://review.cyanogenmod.org/#/c/29952/
Bluetooth - http://review.cyanogenmod.org/#/c/29951/
Bluetooth - http://review.cyanogenmod.org/#/c/29950/
Reverts:
Audio - http://review.cyanogenmod.org/#/c/29175/ - Fixes Bluetooth/A2DP Streaming
Audio - http://review.cyanogenmod.org/#/c/29174/ - Fixes Bluetooth/A2DP Streaming
Audio - http://review.cyanogenmod.org/#/c/29661/ - Fixes In Call Volume Adjustment
As always check here to see what my repo sync may have missed: CM Gerrit - Merged
Enjoy!
Click to expand...
Click to collapse
Will any/all of these changes ever been implemented into the official nightlies?
Sent from my SCH-I535 using Tapatalk 2
atc3030 said:
Will any/all of these changes ever been implemented into the official nightlies?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
yes/no...the reverted items are not going to be reverted in the official.
Does this have the nav bar. I love cm but use aokp cause I can't live with out nav
Bar
Sent from my SCH-I535 using xda app-developers app
Masta.. Yesterday and today build. The phone won't work with wired headset. Works on official not on yours. Any idea?
Man I wish I were capable of cooking a ROM myself and stripping out the parts of other ROMs that work and compiling them together.
I'm on Sprint, xt897c CDMA, I've tried stock/rooted, CM10.1 stable, CM10.2 M snapshot, various CM10.x nightlies, and a couple of the latest PACman nightlies. Every single one of them has things working that others don't, and something not working that I can't live without:
Stock/rooted - need a good/easy way to wifi tether to my Nexus 7 tablet and laptop. Wifi tether app in the play store doesn't work like it does on other phones I've had. JB-style quick settings and notification widgets would be nice too, but mainly this is missing the wifi tether. I could live with it if it had that. However I really want to be running something CM-based...
CM10.1 - Everything runs great on the stable build - its fast, stable, has all the features I want, but there's a problem with the phone audio. My phone first and foremost needs a stable phone. There's a high-pitched whine/hiss in both the speaker and mic that makes phone calls annoy the far end, give me a headache, and makes speaker phone all but unusable. Its also there when recording videos and it stays with the video when its transferred off the phone.
CM10.2 - Same issue as above, plus it hangs on bootloader after the first reboot. Every version I've tried.
PACman - Phone calls sound great - no audio issues. All the features I want. But it's not stable. If I'm listening to music in Apollo and switch to Maps, Apollo just terminates (not FC, just closes like the memory manager killed it or something). Same thing with many other apps (Strava recording segments, etc.). Also the GPS lock is terrible or non-existent.
Ideally I'd like to solve the audio issue with CM10.1 or that and the reboot hang on 10.2. If anyone knows of fixes for these I'd be immensely grateful. I've seen others refer to them but no concrete confirmation or a fix mentioned...
/rant
Try Carbon, try AOKP... try Slimbean. What else... PA? I can't think of any others which have been ported to our device.
Try other ROM's, and I can assure you the ROM's will get better with time - although it's odd you have a high pitched whine in CM but not PAC. I've heard some report that whine, and I was under the impression that all the aftermarket/custom ROM's suffered from that issue.
Either way, CM11 is shaping up to be pretty solid - although I have had a few random reboots, not sure what the issue there was. Mostly when using Google Music in airplane mode/no service areas.
@cmags: As far as I was able to reproduce it, the high pitch whine/buzz was caused by MICBIAS CAPLESS Switch enabled and I've addressed this issue for CM-10.2 branch here: http://review.cyanogenmod.org/51949
I have no issues using speaker phone (I'm running cm-10.2 and cm-11.0 on my two Qs).
Regarding the noise in the high frequency range in camcorder recordings, I'm still not sure about the cause nor a solution for it. (I mean the pure noise, not the whine here).
Regarding the hang after first reboot, I'm not able to reproduce it and the logs from users I've seen so far were not very helpful.
I suspect that it may be caused by the timing of the mounting of internal partitions, but I'm not sure yet.
I'd welcome /proc/last_kmsg captured in recovery after such failed boot.
Thanks for the helpful replies fellas. @kabaldan I'll test out your latest branch and grab logs if I experience the issue.
Sent from my XT897 using Tapatalk
The latest skrilax build of CM10.2 seems to have resolved the audio issue. I was even able to restore my CM10.1 nandroid, flash 10.2 over the top (along with new gapps) and keep my data/settings. Thanks guys for the help!
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Termuellinator said:
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Click to expand...
Click to collapse
*push* nobody got any ideas? i would post it in the appropriate thread (especially since this rom is still only nightly) as a potential bug report, but as a new user i'm not able to :/
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Termuellinator said:
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Click to expand...
Click to collapse
The WiFi bug is a known issue since early August. It affects almost every Moto device (G, G 4G, X and defy?) it's reported several times to CM-s bug tracking system, but nobody cares... You can use custom kernels. Maybe they aren't affected.
I don't know anything about the BT bug.
i found some posts about people having the same kind of wifi-issue, but it is good to know, that the devs are aware and - kind of - working on it
the BT-thingy is driving me insane though...fiddled around a bit, stopping BT-Related processes etc...this somehow did something...my phone now connects and stays connected, i can make phone calls...but the contact list is incomplete - only 3 random contacts are displayed on the car system
haven't rebooted since then, i kind of fear that rebooting will bring back the issue :/
BT still working after reboot, so it seems my "fix" is permanent...must have something to do with deleting the BT-data/cache while process was killed i would think - in case someone else also encounters this problem
still can't acces all my contacts from Car-system though :/
Most nights roms have a lot of issues and it is pretty hard to stay aware all of bugs. Why don't you try something more stable like Pac Man RC or some. Sometimes a different kernel will help sometimes it's the opposite.
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Termuellinator said:
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Click to expand...
Click to collapse
All AOSP rom uses the CM device tree and kernel as a base, so the low level kernel bugs are the same.. Also the last "stable" CM for falcon is dated back to April, so you didn't lose anything with peregrine...
Just in case anyone encounters the same Issues:
with CARBON-KK-NIGHTLY-20140922-0414-peregrine the BT-Problems seem to be resolved, connection works and the contacts are accessible from the car.
WiFi still has problems with dhcp, but as stated, devs are aware of that :good:
bad news: flashed to CARBON-KK-NIGHTLY-20141103-0939-peregrine and the BT-issue is back as in the beginning - com.andoird.bluetooth stops working - but only following the first connect -.-
interestingly going back to my pre-flash-backup didn't resolve the issue (doesn't matter if i just restore or wipe prior to that...but after flashing/restoring the first connect works perfectly)...perhaps that leads to some ideas about the cause?
was just trying to get it to work like the other time by stopping/deleting data of com.andoird.bluetooth, but didn't work this time
ok, figured it out again, this time i'll post my steps in case anyone ever encounters similar issues (and for my future reference in case i encounter them again, too )
1) unpair
2)switch off bluetooth
3) stop com.android.bluetooth in "apps"
4) delete data of com.android.bluetooth
5) reboot
6) pair
7) unpair
8) delete data of com.android.bluetooth
9) pair
10) reboot
at least these are the steps i did and it seems to be working now, again
Are you experiencing the following Kernel wakelocks on your phone?
msm_serial_hs_dma
BTLowPower
It hapepns both with an LG G Watch R (5.0.2) and a regular BT headset.
If we take the second device, I do expect a Kernel wakelock while speaking or streaming music. The phone is active any way while performing this task.
What is strange is that even if there is no activity the wakelocks avoid deep sleep.
What is strange is that if I move away from the headset (and the BT icon goes the "non connected" status), the wakelocks are always there.
The effect is that my phone (both on 4.4.4 and 5.0.2) almost never ever sleeps, and sometimes get warm.
If I switch BT off, everything goes back to normal.
Any solution?
I'm rooted, so I can do further tests researches (I'm using BBS to spot the wakelock).
Is it possible that this is an hardware problem? I'm asking as it looks like I'm the only one with this issue!
Thanks.
I can imagine Android Wear as an issue but the Bluetooth headset is mind boggling.... I have a Sony SRS X7 Bluetooth speaker and that never causes this issue as far as I am aware.
abhinav.tella said:
I can imagine Android Wear as an issue but the Bluetooth headset is mind boggling.... I have a Sony SRS X7 Bluetooth speaker and that never causes this issue as far as I am aware.
Click to expand...
Click to collapse
I was pointing to Wear as well.
Then I noticed it just connecting to a BT headset.
Can you please connect to the speaker and play music for a minute or so. Then stop but keep the Z3 connected and report if you notice the wakelocks (provided you are rooted)? 10 minutes will be enough.
Could it be an hardware problem?
Thanks a lot.
Yeah, I checked again as you asked, still have not noticed any impact on battery life. Mind you I am still on KitKAt and I noticed you are on Lollipop. Have you tried restarting? Maybe it's like the old camera big on Nexus Kitkat release where camera app sometimes ran in the background till restarted.
I thought im the only one having this bluetooth issues..
If you are rooted, can you please check if you have the same wakelock as myself? Tx.
Inviato dal mio Nexus 10 utilizzando Tapatalk
abhinav.tella said:
Yeah, I checked again as you asked, still have not noticed any impact on battery life. Mind you I am still on KitKAt and I noticed you are on Lollipop. Have you tried restarting? Maybe it's like the old camera big on Nexus Kitkat release where camera app sometimes ran in the background till restarted.
Click to expand...
Click to collapse
Thanks for it.
Did you check wakelocks via Battery stats? It could be that a direct impact on battery life is not visible.
I did a test pairing my watch with a 5.1 Nexus 10. The wakelocks are there (with a slightly different name) but they are way less intrusive. They wake the phone up only when needed and the counted 4 minutes over a usage of 10 hours.
My conclusion is that the BT implementation on Z3 (regardless 4.4.4 or 5.0.2) is defective, from a wakelocks and battery perspective.
The fact that I'm one of the few noticing it, could also lead to an hw defect.
What's the expert view?
I have the same problem. Took me a while to figure out it is BT. Since turning off BT did not work (turns out it takes a restart of BT). Odd thing is it does not always happen. Over the past few days I have experimented on different apps (Beyondpod, Audible, Kugou), stopping at different situation (from app, stop from device then turn off, turn off device without first stopping), and on different BT devices (Plantronic Backbeat 903, Nissan Leaf, some no-name car kit (amazon.com/dp/B00L1VT5KS). So far I've ruled out the apps and Plantronic. But between the car and car kit I am not certain. Sometime I connects to both and it would have no problem. Some days (e.g. today) BT will keep the phone awake). Am I'm running more or less the same apps.
In all cases, reboot will fix the issue. But I don't always have luck with simply restarting BT.
I'm able to locate a few threads on the topic. looks like it is not limited to Z3. Z1/s and compact suffer from the same
community.o2.co.uk/t5/Android-Devices-Samsung-HTC-Sony/Z1-Compact-doesn-t-go-to-Deep-Sleep/td-p/648801/page/3
talk.sonymobile.com/t5/Xperia-Z1-Z1s/KitKat-757-Bluetooth-draining-the-battery/m-p/652237#U652237
Both referencing this link for the "workaround":
talk.sonymobile.com/t5/Xperia-Z1-Z1s/Z1-KitKat-687-Toyota-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
(I can't post link, so sorry about the non-linked text)
colonelheero said:
I have the same problem. Took me a while to figure out it is BT. Since turning off BT did not work (turns out it takes a restart of BT). Odd thing is it does not always happen. Over the past few days I have experimented on different apps (Beyondpod, Audible, Kugou), stopping at different situation (from app, stop from device then turn off, turn off device without first stopping), and on different BT devices (Plantronic Backbeat 903, Nissan Leaf, some no-name car kit (amazon.com/dp/B00L1VT5KS). So far I've ruled out the apps and Plantronic. But between the car and car kit I am not certain. Sometime I connects to both and it would have no problem. Some days (e.g. today) BT will keep the phone awake). Am I'm running more or less the same apps.
In all cases, reboot will fix the issue. But I don't always have luck with simply restarting BT.
I'm able to locate a few threads on the topic. looks like it is not limited to Z3. Z1/s and compact suffer from the same
community.o2.co.uk/t5/Android-Devices-Samsung-HTC-Sony/Z1-Compact-doesn-t-go-to-Deep-Sleep/td-p/648801/page/3
talk.sonymobile.com/t5/Xperia-Z1-Z1s/KitKat-757-Bluetooth-draining-the-battery/m-p/652237#U652237
Both referencing this link for the "workaround":
talk.sonymobile.com/t5/Xperia-Z1-Z1s/Z1-KitKat-687-Toyota-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
(I can't post link, so sorry about the non-linked text)
Click to expand...
Click to collapse
Thanks a lot for reporting your experience.
The main difference is that if I disconnect the BT device the drain and wakelocks continue, but if I switch BT off they stop.
Then I do not have BT listed in battery stats as a drain.
Here are your links in a click friendly form!
http://talk.sonymobile.com/t5/Xperi...tooth-draining-the-battery/m-p/652237#U652237
http://talk.sonymobile.com/t5/Xperi...-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
Unfortunately the workaround of turning off + wait + on BT is not a usable solution in a scenario where you use a smartwatch, that has to be connected the all day!!
I'm tempted to try an AOSP based rom to see if the problem is HW related or just SW.
I'll keep you posted.
Thanks.
I did a further test, in the below sequence:
- BT ON + connected to a Plantronics headset => wakelock + device always on
- BT ON + disconnected to a Plantronics headset => wakelock + device always on
- BT OFF + disconnected to a Plantronics headset => no wakelock + device sleep
- BT ON + disconnected to a Plantronics headset => wakelock + device always on
This thing is driving me crazy!!!!!
vittogn said:
Are you experiencing the following Kernel wakelocks on your phone?
msm_serial_hs_dma
BTLowPower
It hapepns both with an LG G Watch R (5.0.2) and a regular BT headset.
If we take the second device, I do expect a Kernel wakelock while speaking or streaming music. The phone is active any way while performing this task.
What is strange is that even if there is no activity the wakelocks avoid deep sleep.
What is strange is that if I move away from the headset (and the BT icon goes the "non connected" status), the wakelocks are always there.
The effect is that my phone (both on 4.4.4 and 5.0.2) almost never ever sleeps, and sometimes get warm.
If I switch BT off, everything goes back to normal.
Any solution?
I'm rooted, so I can do further tests researches (I'm using BBS to spot the wakelock).
Is it possible that this is an hardware problem? I'm asking as it looks like I'm the only one with this issue!
Thanks.
Click to expand...
Click to collapse
I've NEVER seen this happen on stock. I've only seen it happen on Sony AOSP, which currently has a broken BT LPM config.
Entropy512 said:
I've NEVER seen this happen on stock. I've only seen it happen on Sony AOSP, which currently has a broken BT LPM config.
Click to expand...
Click to collapse
Hi Andrew, that's great to have @Entropy512 input for what appears to be a very "personal" problem!!
I had some further investigation and discovered that:
In wakelock detector under kernel wakelocks I can notice that:
ipc000000ef_sensors.qcom has the highest number (7387 in 3h).
ipc0000008c_sensors.qcom (649 in 3h).
Under CPU WL I have UID [Type: System (Bluetooth) - bluedroid_timer] is the biggest WL. This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
In Sony talk forum I got a reply from a moderator: "That item you listed is known to prevent sleep from back in 2012 and to fix you need to decompile and rebuild the item with amended code - However you still could have an app hence why I mentioned the app to check."
It's strange to me to be asked, as a customer, to decompile and rebuild system stuff!!
Any chance there is an app causing my issue? Any suggestion on how I can root cause it?
Is there a chance it is an hw problem?
Thanks a lot.
vittogn said:
This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
Click to expand...
Click to collapse
By the way, I'm on Sony Store stock Kit Kat 23.0.1.A.5.77.
colonelheero said:
By the way, I'm on Sony Store stock Kit Kat 23.0.1.A.5.77.
Click to expand...
Click to collapse
Hi, my reference to Lollipop was only related to UID [Type: System (Bluetooth) - bluedroid_timer] CPU WakeLock.
All the rest of my findings where exactly the same in KK.
I got to Sony support forum and a very kind Sony guy promised to look after this issue.
I provided some system dump log taken via PC C after recreating the issue.
I'll keep you updated about the progress.
vittogn said:
Hi Andrew, that's great to have @Entropy512 input for what appears to be a very "personal" problem!!
I had some further investigation and discovered that:
In wakelock detector under kernel wakelocks I can notice that:
ipc000000ef_sensors.qcom has the highest number (7387 in 3h).
ipc0000008c_sensors.qcom (649 in 3h).
Under CPU WL I have UID [Type: System (Bluetooth) - bluedroid_timer] is the biggest WL. This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
In Sony talk forum I got a reply from a moderator: "That item you listed is known to prevent sleep from back in 2012 and to fix you need to decompile and rebuild the item with amended code - However you still could have an app hence why I mentioned the app to check."
It's strange to me to be asked, as a customer, to decompile and rebuild system stuff!!
Any chance there is an app causing my issue? Any suggestion on how I can root cause it?
Is there a chance it is an hw problem?
Thanks a lot.
Click to expand...
Click to collapse
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)
Entropy512 said:
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)
Click to expand...
Click to collapse
Thanks.
Any advice on how to discover if this a system/rom issue or caused by an app? Any system log I can take?
Entropy512 said:
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)
Click to expand...
Click to collapse
Hi Andrew, did Sony fix it in their recent AOSP 5.1?
OT ON: are u working on Omni for the Z3? OT OFF
Here a self explanatory comparison in between two very simalar days.
The first is with a BT device connected (just connected not streaming or talking).
The second (NO BT - ....) is without. The deep sleep attitude is very different!!
I was on KK yes, but the situation with 5.0.2 is exactly the same.
When I watch YouTube videos with my bluetooth speaker connected to the tablet while running Lollipop-based ROMs like KatKiss and Zombi-POP, the video would speed up and the audio is also distorted. The problem has been partly resolved after I enabled AptX codec
Code:
setprop persist.service.btui.use_aptx 1
I wonder why it's not enabled by default in these ROMs.
The problem still happens occasionally. I wonder if modifying Bitpool will help. If so, how can that be done?
@sam369
I've been having the same problem with ZOMBI-POP RC1 and RC2 and have not found a solution. This is my experience:
I currently have my tablet connected to a bluetooth speaker and play all the audio through that. Every now and then, the audio will skip/speed up/play normally/speed up. In the app, you can see time skip. For example, the song starts at 0:00 then jumps to 0:02 then plays normally for a second then jumps 2 seconds ahead. If I disconnect from the bluetooth speaker and play the song normally, everything is fine.
Are you having a similar experience?
Of note, I upgraded from ZOMBI-POP RC1 to RC2 and the problem does not occur as frequently, but is still a problem. I'm wondering if this is kernel related because I'm using Omni kernel on RC2 but used _thats' kernel on RC1 and the problem occurred a lot more on RC1.
I really hope we can figure this out.
matt11601 said:
@sam369
I've been having the same problem with ZOMBI-POP RC1 and RC2 and have not found a solution. This is my experience:
I currently have my tablet connected to a bluetooth speaker and play all the audio through that. Every now and then, the audio will skip/speed up/play normally/speed up. In the app, you can see time skip. For example, the song starts at 0:00 then jumps to 0:02 then plays normally for a second then jumps 2 seconds ahead. If I disconnect from the bluetooth speaker and play the song normally, everything is fine.
Are you having a similar experience?
Of note, I upgraded from ZOMBI-POP RC1 to RC2 and the problem does not occur as frequently, but is still a problem. I'm wondering if this is kernel related because I'm using Omni kernel on RC2 but used _thats' kernel on RC1 and the problem occurred a lot more on RC1.
I really hope we can figure this out.
Click to expand...
Click to collapse
@matt11601 Have you tried the command:
Code:
getprop persist.service.btui.use_aptx
It doesn't return anything. It means that AptX codec was not enabled. Then
Code:
setprop persist.service.btui.use_aptx 1
to enable AptX codec.
This mostly solves the problem. I have not figured out how to modify Bitpool yet.
sam369 said:
@matt11601 Have you tried the command:
Code:
getprop persist.service.btui.use_aptx
It doesn't return anything. It means that AptX codec was not enabled. Then
Code:
setprop persist.service.btui.use_aptx 1
to enable AptX codec.
This mostly solves the problem. I have not figured out how to modify Bitpool yet.
Click to expand...
Click to collapse
I did that, except in the wrong order:
1) setprop persist.service.btui.use_aptx 1
2) getprop persist.service.btui.use_aptx
After #2, it did return a value of 1, but this doesn't tell me the setting before. However, this morning the audio problems happened again and I did not restart the tablet. I'm assuming this codec is still enabled, but I'll check again.
What I notice is the problem will either be fixed or return after my tablet wakes up. A reboot always fixes it. This is the one consistent observation I've noticed. Could it be related to the kernel? Or how Bluetooth is enabled from sleep. For my setup, I have Tasker turn Bluetooth off when the tablet screen is off. And then re-enabled when the screen is on.
What has your experience been?
matt11601 said:
I did that, except in the wrong order:
1) setprop persist.service.btui.use_aptx 1
2) getprop persist.service.btui.use_aptx
After #2, it did return a value of 1, but this doesn't tell me the setting before. However, this morning the audio problems happened again and I did not restart the tablet. I'm assuming this codec is still enabled, but I'll check again.
What I notice is the problem will either be fixed or return after my tablet wakes up. A reboot always fixes it. This is the one consistent observation I've noticed. Could it be related to the kernel? Or how Bluetooth is enabled from sleep. For my setup, I have Tasker turn Bluetooth off when the tablet screen is off. And then re-enabled when the screen is on.
What has your experience been?
Click to expand...
Click to collapse
What I found is that it happens if the resources of the system is quite limited (there are resource-consuming processes) when the bluetooth speaker is connected.
If a solution cannot be easy found, maybe you can consider using other ROMs. You can install Crombi-kk to a microSD card with ROM2SD option. It is fast and doesn't have the problem, but I found that its WIFI is not as stable, though.
sam369 said:
What I found is that it happens if the resources of the system is quite limited (there are resource-consuming processes) when the bluetooth speaker is connected.
If a solution cannot be easy found, maybe you can consider using other ROMs. You can install Crombi-kk to a microSD card with ROM2SD option. It is fast and doesn't have the problem, but I found that its WIFI is not as stable, though.
Click to expand...
Click to collapse
Ahh I see. Out of curiosity, how do you know it occurs when resources are low? I would love to monitor that too and report back my findings.
I've toyed around with switching ROMS. I was specifically thinking about 5.4 Resurrected, but the stability of RC2 is fantastic. I have not had a single random reboot or battery drain. I want to work through this because this ROM is excellent.
FYI, bluetooth audio worked well this morning. Fingers crossed.
matt11601 said:
Ahh I see. Out of curiosity, how do you know it occurs when resources are low? I would love to monitor that too and report back my findings.
I've toyed around with switching ROMS. I was specifically thinking about 5.4 Resurrected, but the stability of RC2 is fantastic. I have not had a single random reboot or battery drain. I want to work through this because this ROM is excellent.
FYI, bluetooth audio worked well this morning. Fingers crossed.
Click to expand...
Click to collapse
Like I said the problem has been mostly solved after AptX codec was enabled, but it happened again yesterday when I was installing offline maps. After the task was finished, the problem was gone even without restarting the tablet.
I think you can try out omniROM. It's what ZOMBi-POP is based on but is lighter. I did not notice the problem. What you can do is to replace the contents of /system/ of ZOMBi-POP 5.1.1 RC2 20151210 with those of /system/ of omniROM, and choose omni kernel during installation. That worked well for me. No need to get separate SuperU or gapps, and you can get regular updates for omniROM.
Thanks a lot for the help. Sounds like a good idea to switch to omniROM.
matt11601 said:
Thanks a lot for the help. Sounds like a good idea to switch to omniROM.
Click to expand...
Click to collapse
@matt11601 How is your new ROM? I'd like to let you know that I have been using TechFusion+ V4 recently. It's pretty snappy and doesn't have the WIFI stability issue I noticed on CROMBi-kk. If you are interested, I can walk you through how I installed it on micro SD card.
sam369 said:
@matt11601 How is your new ROM? I'd like to let you know that I have been using TechFusion+ V4 recently. It's pretty snappy and doesn't have the WIFI stability issue I noticed on CROMBi-kk. If you are interested, I can walk you through how I installed it on micro SD card.
Click to expand...
Click to collapse
I haven't tried it yet. I've been doing everything I can to stay with this ROM because it's the first time my tablet has been stable, but the bluetooth problem persists. Even when I check the codecs status, it returns a value of 1 but I still get the bluetooth problems.
I was thinking about cromi 5.4 resurrected, but may try omniRom first. Does TechFusion use f2fs?
matt11601 said:
I haven't tried it yet. I've been doing everything I can to stay with this ROM because it's the first time my tablet has been stable, but the bluetooth problem persists. Even when I check the codecs status, it returns a value of 1 but I still get the bluetooth problems.
I was thinking about cromi 5.4 resurrected, but may try omniRom first. Does TechFusion use f2fs?
Click to expand...
Click to collapse
You don't have to give up ZOMBi-POP when you try other ROMs except cromi 5.4 resurrected. You can just get a 32 gb or even 16 gb fast class 10 TF card, and install new ROMs using rom2sd option.
I was able to install TechFusion to TF card with f2fs data. I believe you can just replace the contents of /system/ of cm-11.0-20140921-tf700t-crombi-kk-R1_signed.zip with those of /system/ of TechFusion+ V4(TF700).zip, and then you can use the Aroma installer of CROMBi-kk and choose rom2sd and f2fs /data, though I did it differently, for I have a backup of internal installation of TechFusion, so I just expanded the backup to corresponding partitions on the TF card and then copied over the /boot/ from CROMBI-kk rom2sd installation with f2fs /data.
I installed omniROM with rom2sd using the same strategy. I just downloaded the latest nightly build of omniROM and use it's contents of /system/ replaced those of ZOMBi-POP installer, and chose rom2sd and f2fs /data during installation.
I believe you can find instructions on how to do rom2sd installation in the ZOMBi-POP thread. Just format /data partition on TF card to f2fs in Linux system. It's better to use a really fast TF card for rom2sd, like Sandisk ExtremePro or Samsung Evo.
Please feel free to ask if you have any questions.
matt11601 said:
I haven't tried it yet. I've been doing everything I can to stay with this ROM because it's the first time my tablet has been stable, but the bluetooth problem persists. Even when I check the codecs status, it returns a value of 1 but I still get the bluetooth problems.
I was thinking about cromi 5.4 resurrected, but may try omniRom first. Does TechFusion use f2fs?
Click to expand...
Click to collapse
I know it's been a while, but I wanted to touch base in case anyone was wondering. I've tried the following ROMS: omniRom and Katkiss.
The bluetooth problem persisted on omniRom despite the following:
Change governor to ondemand or performance
Disable USB audio routing.
Turn off WiFi notify
Change minimum CPU to ~729mhz
Added line to build.prop: ro.bluetooth.request.master=true
Turn on aptX codec
I also tried the same in Katkiss and still have bluetooth problems, but they occur less often. For example, bluetooth would skip/garbled 3-4 times a day. On Katkiss, it's 1-2 times every few days. I'm still hoping I can figure this out, but I'm not hopeful. From reading other forums, it appears the new bluetooth stack introduced in Lollipop is a problem with our hardware.
matt11601 said:
I know it's been a while, but I wanted to touch base in case anyone was wondering. I've tried the following ROMS: omniRom and Katkiss.
The bluetooth problem persisted on omniRom despite the following:
Change governor to ondemand or performance
Disable USB audio routing.
Turn off WiFi notify
Change minimum CPU to ~729mhz
Added line to build.prop: ro.bluetooth.request.master=true
Turn on aptX codec
I also tried the same in Katkiss and still have bluetooth problems, but they occur less often. For example, bluetooth would skip/garbled 3-4 times a day. On Katkiss, it's 1-2 times every few days. I'm still hoping I can figure this out, but I'm not hopeful. From reading other forums, it appears the new bluetooth stack introduced in Lollipop is a problem with our hardware.
Click to expand...
Click to collapse
Have you tried the command with KatKiss 6?
Code:
setprop persist.service.btui.use_aptx 1
That seems to work for me. If you have not, you should try KatKiss 6. It's even smoother than many LP ROMs.
sam369 said:
Have you tried the command with KatKiss 6?
Code:
setprop persist.service.btui.use_aptx 1
That seems to work for me. If you have not, you should try KatKiss 6. It's even smoother than many LP ROMs.
Click to expand...
Click to collapse
Yep I did that on both omniROM and Katkiss 6. Out of curiosity, does the bluetooth device need to support aptX?
FYI, I've made the aforementioned changes one at at time. Then, let the tablet run for a week to see if it helped which is why it took me a while to respond to this.
After reading the TF700 threads for a few years, you notice those minority of people that have trouble with their tablets. I've always been one of them. The tablet never runs as smooth as others or I run into problems. I've always wondered if I have an earlier version of the tablet.
I'll keep trying though. For now, I went to Cromi-X Resurrected and bluetooth is working great. But we'll see what the next few weeks bring.
Thanks again for all your help and advice.
Most stable Android 4 ROMs for TF700T do not have the Bluetooth problem, and they are usually smoother than LP ROMs.
I only have one Bluetooth speaker, so I never thought about whether Apx support is a factor, but the command works in KatKiss 6 for me.
BTW, KatKiss 6 has been improved over time, so if you used an earlier version, you can try the latest one, and then just enable Apx codex to see if it works. It is almost as smooth as Android 4 ROMs now. You can do ROM2SD installation using attached files. Flash rom2sd1.zip, the ROM, rom2sd2.zip, SuperSU, and Gapps, in order. This method works for most ROMs.
If only Android 4 ROMs work for you, I think KatKiss 4 or PAC-MAN ROM have better features. Official KatKiss 4 doesn't support TF700t, but you can flash Grimlock4 kernel to make it work, or do ROM2SD installation by flashing rom2sd1.zip, KatKiss 4 for TF300T, Grimlock4 kernel, rom2sd2.zip, SuperSU, and Gapps. Let me know if you want to try but have questions.