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.
Related
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 guys I have been using CM 11 on my Galaxy Note 8.0 for some time, since I prefer the stock UI to TouchWiz. It is also convenient to be able to mount an NTFS formatted external drive w/o any third party solution. However, I noticed that BT audio skips quite a bit to the point where it would make listening to music through my BT adapter or headphones annoying or unbearable. The issue appears only when the screen is locked (no skipping occurs when the screen is on) Has anyone else encountered this issue?
I believe I found a way to fix this issue. I basically enabled development settings by tapping build number a couple times, then I went into performance and changed the governor from pegasusq to ondemand. This appears to have resolved the BT audio skipping. If anyone else has experienced this problem, I would like for them to try this quick fix and let me know if it works!
EDIT - the performance governor also seems to resolve the BT issue while at the same time improving game performance.
The thread was moved to an incorrect device forum. This only refers to the GT-N5110 - Galaxy Note 8.0 WiFi. I let a forum administrator know.
There are 3 CM11 ROMs for the 3 variants of the Note 8.0. Which one are you referring to?
CafeKampuchia said:
There are 3 CM11 ROMs for the 3 variants of the Note 8.0. Which one are you referring to?
Click to expand...
Click to collapse
My bad for not specifying. I was referring to the N5110
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
Q&A for Lollipop 5.0 runs on our msm8960s on kkbl
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Lollipop 5.0 runs on our msm8960s on kkbl. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Battery Life
derpyherp said:
I think its odd how there is no deep sleep state i put a screen shot of the cpu times at each cpu speed... Its odd but somehow battery life is amazing
Click to expand...
Click to collapse
I switch back to cm11 because i have 6%/hr of battery drain, (7hr/41min Screen on time, 65% left), that is for me horrible battery life.
I did not look the cpu states, but, if there is no deep sleep, it sould explain mi experience about battery.
I have the same mensage when I was in f2fs. I have to go back to ext4 to work.
Does anyone know if the AOSP Camera will be made available? I don't like the Google one since it doesn't allow me to choose the external SD card as a storage option.
The system itself boots, and runs quite smoothly from what I've tried so far. Very exciting!
But I've found that Lastpass crashes immediately when I try to launch it. I did a clean install with CM12 11/17. Has anyone else seen this behaviour with this app? I'm assuming for the moment it just hasn't yet caught up to Android 5, and I'll have to sit patiently on 4.4 until then.
Cubkyle said:
The system itself boots, and runs quite smoothly from what I've tried so far. Very exciting!
But I've found that Lastpass crashes immediately when I try to launch it. I did a clean install with CM12 11/17. Has anyone else seen this behaviour with this app? I'm assuming for the moment it just hasn't yet caught up to Android 5, and I'll have to sit patiently on 4.4 until then.
Click to expand...
Click to collapse
I don't use that app, but it's probably either one of two things (or both):
This ROM was just release back on 11/14, so it's fairly new (the 11/14 was the first release), so there could be some issues that are causing the app to fail.
The app needs to be updated to run correctly under LP. There were some major changes to the API for LP that could cause other apps to fail that are now using these deprecated API calls. The developer needs to take there app and compile it under the latest LP compiler and libs to see if it compiles.
So, you'll probably have to wait and see. So far, I've been lucky. The apps that I need to work (CoPilot USA, etc) all work. Just waiting for dhacker to figure out the correct set of libs for DRM so that Google Play Movies and Netflix start working again. They work fine under my Nexus 7 running LP, but that was an official release by Google.
iBolski said:
I don't use that app, but it's probably either one of two things (or both):
This ROM was just release back on 11/14, so it's fairly new (the 11/14 was the first release), so there could be some issues that are causing the app to fail.
The app needs to be updated to run correctly under LP. There were some major changes to the API for LP that could cause other apps to fail that are now using these deprecated API calls. The developer needs to take there app and compile it under the latest LP compiler and libs to see if it compiles.
So, you'll probably have to wait and see. So far, I've been lucky. The apps that I need to work (CoPilot USA, etc) all work. Just waiting for dhacker to figure out the correct set of libs for DRM so that Google Play Movies and Netflix start working again. They work fine under my Nexus 7 running LP, but that was an official release by Google.
Click to expand...
Click to collapse
It turns out it was simply a matter of PEBCAK. I uninstalled Android System Webview, because it has the same icon as the stock Browser, while I was removing unwanted processes.
The first time , I flashed 11/15 version, everything seems to work fine ,then I flashed gapps, then I got no signal anymore,but everything else seems to work, so I did a factory reset, the gsm signal came back again, today when I trying to flash 11/18 version, the signal gone again, this time I don't want loose my data , what should I do to get a gsm signal? *#*#4636#*#* seems not working on 11/18, sorry for my poor english
Cubkyle said:
It turns out it was simply a matter of PEBCAK. I uninstalled Android System Webview, because it has the same icon as the stock Browser, while I was removing unwanted processes.
Click to expand...
Click to collapse
Ah, I'm familiar with those errors as well as the ID10T error as well.
Works just fine, very smooth. Had no troubles with the signal at all.
However, I can't receive a call, the dialer just stops. It is possible though to make a call. Anyone had this problem?
yes had that error many times "dialer has stopped", this is work in progress man. I hope that dhacker checks this and the other thread and try to remedy some of the prob.
For that dialer has stopped error, a reboot can cure it. But again i cant rely on a phone that is going to quit when you need to make or receive a call.
So the fix for no service is still reboot and hope?
I'm on Verizon CDMA, XT926, 11/23 build, 11/22 gapps, SuperSU 2.27
Thanks.
Doug B.
I had an odd issue on 11/22 build:
When I connect my car via bluetooth, when a call comes in, pressing the answer button does nothing and the call keeps ringing forever.
Also,
Is Anyone having issues with restoring on TWRP 2.8.1.0? I tried restoring a backup I made and my phone won't boot. It just gets stuck at the cyanogen mod screen.
Edit: I restored a previous backup, installed TWRP 2.8.2.0 and then restored the backup I was trying to. It worked.
dvgb173 said:
So the fix for no service is still reboot and hope?
I'm on Verizon CDMA, XT926, 11/23 build, 11/22 gapps, SuperSU 2.27
Thanks.
Doug B.
Click to expand...
Click to collapse
On my 11/25 build data wasn't working at first, I just turned it on and off from settings and it started working.
11/25 build is working for me as far as being able to receive phone calls. I was previously getting FCs on it when an incoming call was coming, but I was also running f2fs. I've gone back to ext4 and things seem to have stabilized at this point.
This build is the dhacker? I found nothing in his link. Many changes over the previous build?
When open 3g ,call comein can not.
How to fix it?
Thank.
soowijux said:
When open 3g ,call comein can not.
How to fix it?
Thank.
Click to expand...
Click to collapse
Now, I install 30/11 it OK.
Thanks.
SMS issue
Is the sms issue (can't receive sms, although the phone I'm sending from receives the delivery report) still present in this new build (12-02)? I've tried the 11-25 build and BlissPop and none of them allowed me to receive sms... It's the one real issue that's keeping me from jumping into Lollipop
Razr HD (XT925, KK bootloader)
My device does not come out of the boot with this version.
So I wiped the phone completely, installed the latest CM12 nightly, franco kernel, gapps. The usual. Everything went buttery smooth, connected to wifi, got all my apps installed, settings set, and set my phone down.
Come back to it a few hours later and there was an exclamation mark over the wifi icon, which took several seconds to go away. Now the wifi is INCREDIBLY slow and/or won't work. Facebook won't load, webpages won't, the play store will let me search around it I can download an app but it takes maybe a minute of just sitting there before it starts to download (and then it will download at a slow speed but not this excruciatingly slow speed).
I've used this same setup for a long time and never had this problem, nor have I ever had this problem with any combination of phone/rom/kernel/settings. It wasn't even happening earlier, it just started within the past hour. Has this happened to you guys? What's going on, and how do I fix it?
There's no problem with lag as far as I can tell. Everything works great except the wifi, and everything WAS working perfectly until the wifi started acting up an hour ago.
LTE works fine. Things that didn't help the problem:
Rebooting
Wiping cache, dalvik, and internal storage then rebooting
Forgetting network and reconnecting
I'm sure I could reset the entire phone and things would work again because this must be some bug, but I'd rather not have to do that.
.Psd
I have this issue and having more time than brains I hammer at it until my desire is met!
I first thought it was from dirty flashing but it isn't.
I found that opening my wifi connection and getting to advanced settings and the setting DHCP to static and giving it any IP address in your range. Mine said it was 192.168.1.192 so I went with 192.168.1.19(4) and bam it worked!
I have done this with iphones by giving them the DNS of google 8.8.8.8
Good luck
Rick
dentman said:
.Psd
I have this issue and having more time than brains I hammer at it until my desire is met!
I first thought it was from dirty flashing but it isn't.
I found that opening my wifi connection and getting to advanced settings and the setting DHCP to static and giving it any IP address in your range. Mine said it was 192.168.1.192 so I went with 192.168.1.19(4) and bam it worked!
I have done this with iphones by giving them the DNS of google 8.8.8.8
Good luck
Rick
Click to expand...
Click to collapse
I'll try it, but then how come it was working fine earlier and now it's being problematic? Also, I don't see any setting to change the DHCP...
(I've never had to do this before, even with this exact setup... :/)
dineshjumani said:
I did not face this issue till now but it seems opo have many issue I have issue with lag in games and did you try factory reset or try installing again and please also help me by telling do you have lag in games in opo in small games like subway surfers or dumb ways to die 2
Click to expand...
Click to collapse
You're already discussing this here:
http://forum.xda-developers.com/showthread.php?t=3066492
Transmitted via Bacon
---------- Post added at 15:56 ---------- Previous post was at 15:53 ----------
.psd said:
I'll try it, but then how come it was working fine earlier and now it's being problematic? Also, I don't see any setting to change the DHCP...
(I've never had to do this before, even with this exact setup... :/)
Click to expand...
Click to collapse
Are you running the same build of Franco as when it was working perfectly? Something could have changed within the kernel perhaps, try using the stock kernel with a ROM before creating bug reports.
Transmitted via Bacon
This isn't a bug report, and it's explicitly regarding a setup (perhaps the most popular setup) involving a custom rom and kernel.
The kernel version is the same. As I stated, everything worked fine, as it ALWAYS does with this very stable setup (OPO + CM12 + Franco kernel), then when I came back to my phone the wifi was having problems and has been since.
I just wiped the phone completely and reinstalled the rom and kernel, and it's still having the problem. The only difference is now I can't reinstall any apps because the Internet is effectively nonexistent...
.psd said:
This isn't a bug report, and it's explicitly regarding a setup (perhaps the most popular setup) involving a custom rom and kernel.
The kernel version is the same. As I stated, everything worked fine, as it ALWAYS does with this very stable setup (OPO + CM12 + Franco kernel), then when I came back to my phone the wifi was having problems and has been since.
I just wiped the phone completely and reinstalled the rom and kernel, and it's still having the problem. The only difference is now I can't reinstall any apps because the Internet is effectively nonexistent...
Click to expand...
Click to collapse
Ok, but you didn't mention which build of Franco you're on. Franco evolves, like any other kernel, to keep up with how the ROMs evolve. And vice versa.
I had assumed that seeing as it was after a flash, that the chances of either the ROM build version or the kernel build version changing were pretty high. Or don't you update your ROM or your kernel? If you're on the latest CM12 nightly but still using whatever build of Franco you're on then it isn't the same setup you've been using, because part of that config has changed (different ROM build).
Anyway, you came here looking for help. And one of the first things anyone who's even slightly capable in the world of ROM/kernel flashing will tell you is to test without the custom kernel. That's basic troubleshooting, it's a process of elimination. If the problem stops, there's a high chance the kernel was causing it (or there's a mismatch between the kernel build and the new ROM build), if the problem persists you've pretty much ruled out the kernel as the problem, move on to next possible cause. It'll take you less than a minute to dirty flash the ROM zip so you're on the stock kernel, not hard at all.
Transmitted via Bacon
---------- Post added at 16:25 ---------- Previous post was at 16:20 ----------
PS. The q&a and troubleshooting section is here:
http://forum.xda-developers.com/oneplus-one/help
Transmitted via Bacon
Perhaps we misunderstood rah other. What I meant was that earlier today I wiped my device and installed cm12 and Franco kernel. Everything was working fine, I downloaded all my apps (over wifi, which was working fine), set my settings, then left the device alone for several hours. When I picked it up later on, there was an exclamation mark on the wifi icon, which took awhile to go away. Even after it went away, the Wifi has remained dysfunctional.
A wipe and reflash doesn't restore proper wifi functionality. At worst, I would expect it to restore wifi and then give me trouble some hours later, but in fact the wifi is botched from the get go, suggesting that something in my phone has changed.
But my main point was to see if this is a problem others have experienced, because I never have before. And if people had experienced if, I'm curious what they did to resolve the issue.
.psd said:
Perhaps we misunderstood rah other. What I meant was that earlier today I wiped my device and installed cm12 and Franco kernel. Everything was working fine, I downloaded all my apps (over wifi, which was working fine), set my settings, then left the device alone for several hours. When I picked it up later on, there was an exclamation mark on the wifi icon, which took awhile to go away. Even after it went away, the Wifi has remained dysfunctional.
A wipe and reflash doesn't restore proper wifi functionality. At worst, I would expect it to restore wifi and then give me trouble some hours later, but in fact the wifi is botched from the get go, suggesting that something in my phone has changed.
But my main point was to see if this is a problem others have experienced, because I never have before. And if people had experienced if, I'm curious what they did to resolve the issue.
Click to expand...
Click to collapse
Ok, fair enough. But like I said, the first thing you need to do is get rid of the custom kernel in order to test properly. The fact that it was working fine earlier doesn't mean it can't be the kernel, at the same time I'm not saying that it is the kernel, what I'm saying is testing on stock is the first step in working this out, you need to remove any variables.
Transmitted via Bacon
I think it's my modem/router (net gear c3000). Will look more into the situation later.
EDIT: bingo. Factory reset the modem and problem fixed immediately.
Great, glad to see you got it worked out.
Transmitted via Bacon
Have the same problem connecting to wifi after I installed CM12 Nightly.
Doing a factory reset now and checking.
Hope this should solve the wifi issue
---------- Post added at 10:35 AM ---------- Previous post was at 10:24 AM ----------
Did factory reset but still the same issue.
The wifi status is still connecting from a long time........doesn't get connected
Did turn on and turn off the flight mode too (read in few posts that it solved the issue). But it did not solve the issue...
Any help or suggestion?