Develop Bugs

[Q] I just want AVRCP 1.3+... Is there a 4.2.1 Rom + AVRCP 1.3 support?

I get that there is already AVRCP 1.3 support in the custom roms (CM7+ i believe). And that is great. But honestly, all i want is to be able to add the bluetooth support to my current build. Are there any builds out there that are nothing but the Stock android ROM + AVRCP 1.3 (or Bluetooth 4.0 even) ?

I know in 4.1 there was a patch a lot of ROMs were including that updated part of the system's bluetooth stack to support AVRCP 1.3. However, I'm thinking it won't work with the newly rewritten bluetooth stack in 4.2. Not a dev, so can't confirm. I looked at the patch code that was going around and it looks pretty specific to the older bluetooth stuff. Guess we'll have to wait for Cyanogen to rewrite their stuff for 4.2.

So, I'm kinda a newb, but I'm learning. If Cyanogen gets around to rewriting their stuff for 4.2, is it possible just to take various bluetooth binaries, and put them in place of the stock android binaries?!? That would affectively be the very definition of a "patch"

lordneeko said:
So, I'm kinda a newb, but I'm learning. If Cyanogen gets around to rewriting their stuff for 4.2, is it possible just to take various bluetooth binaries, and put them in place of the stock android binaries?!? That would affectively be the very definition of a "patch"
Click to expand...
Click to collapse
There's a JIRA ticket to add AVRCP 1.3 into CM 10.1. According to progress on the ticket, they're trying to get it assigned to someone. I would post the link, but of course I can't do that yet. Google is your friend for the cyanogenmod jira, and it's issue CYAN-20.

I found it I will keep an eye on this issue

Wifi Region code Connectivity problems: A Solution

Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
March 19,2014
Added new Version for newer CM11 nightlies
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
March 25 Note: Added zip for new versions of Commotio Rom
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk

arifqur said:
Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk
Click to expand...
Click to collapse
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later

atifsh said:
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later
Click to expand...
Click to collapse
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.

arifqur said:
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.
Click to expand...
Click to collapse
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.

atifsh said:
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.
Click to expand...
Click to collapse
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.

arifqur said:
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.
Click to expand...
Click to collapse
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.

atifsh said:
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.
Click to expand...
Click to collapse
Yup it is pretty simple. Glad this problem has been sorted out, kind-of

arifqur said:
Yup it is pretty simple. Glad this problem has been sorted out, kind-of
Click to expand...
Click to collapse
yeah flashing every time you update is a mess

atifsh said:
yeah flashing every time you update is a mess
Click to expand...
Click to collapse
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL

arifqur said:
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL
Click to expand...
Click to collapse
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone

atifsh said:
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone
Click to expand...
Click to collapse
Not all phones have this problem and also a lot of custom rom devs apply this patch directly in their roms.
I have an S3, S4, HTC One, Note 2, S2 Skyrocket, Nexus4 and none of them have this problem. Even on OGP this problem started from CM11 Jan 22, 2014 build. The Jan 21st build flashes without this issue.

Flashable zip added for new Commotio Rom Nightlies

Any chance to apply the patch to a stock rooted rom?
Thanks

Region Code
Hi can someone fix this file for region code?

nagi_007pk said:
Hi can someone fix this file for region code?
Click to expand...
Click to collapse
Sorry man.
Tried to patch it but seems to be way different in code from the rest of the roms that I have seen.

Can someone post the patch for latest cm nightlies?

nagi_007pk said:
Can someone post the patch for latest cm nightlies?
Click to expand...
Click to collapse
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.

arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based

nagi_007pk said:
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based
Click to expand...
Click to collapse
Here you go.
Hope it works

arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
just tried it latest nightly, still the same.

[Q] Do any KitKat ROMs support Bluetooth Low Energy?

I have a stock, unrooted Galaxy Nexus GSM purchased new from Google currently running 4.3.
I have a FitBit Flex which will only sync with phones that have Bluetooth Low Energy support.
I can not find any information on any of the KitKat ROMs out there for Galaxy Nexus to see if I install it, will Bluetooth LE work?
If it does then work, my next concern would be if the FitBit app would recognize that the Bluetooth LE works and it would then be able to sync, or if it simply would still see it as a Galaxy Nexus which they do not list as a supported device: http://www.fitbit.com/devices
If anyone can offer me some advice here, I'd greatly apprecaite it!
Thanks.
(btw, sorry if this is in the wrong froum. please move it if it is)

adamwsh said:
I have a stock, unrooted Galaxy Nexus GSM purchased new from Google currently running 4.3.
I have a FitBit Flex which will only sync with phones that have Bluetooth Low Energy support.
I can not find any information on any of the KitKat ROMs out there for Galaxy Nexus to see if I install it, will Bluetooth LE work?
If it does then work, my next concern would be if the FitBit app would recognize that the Bluetooth LE works and it would then be able to sync, or if it simply would still see it as a Galaxy Nexus which they do not list as a supported device: http://www.fitbit.com/devices
If anyone can offer me some advice here, I'd greatly apprecaite it!
Thanks.
(btw, sorry if this is in the wrong froum. please move it if it is)
Click to expand...
Click to collapse
See here.
http://forum.xda-developers.com/showthread.php?t=2492436
With any kitkat rom I install only the modified apk from that thread and everything is ok!
Il you wanna stay with 4.3 you must install btle libraries as mentioned in the thread.

Gnex supports BLE with almost every KK rom.
(try BLE Checker on play store: on my Vanir says Supported!)

yes, and wrong place to ask this

caluz78 said:
See here.
http://forum.xda-developers.com/showthread.php?t=2492436
With any kitkat rom I install only the modified apk from that thread and everything is ok!
Il you wanna stay with 4.3 you must install btle libraries as mentioned in the thread.
Click to expand...
Click to collapse
THANK YOU, THANK YOU, THANK YOU!
I used The Nexus Root Toolkit (by WugFresh) to Unolock and Root my GNex. Then I used the link you gave me to get the BTLE files and the FitBit apk. I installed everything and it freakin' works!!! I'm so happy!
I'm so annoyed at Google for letting support of this device go after only 18 months. I bought it because they praised it as being thee flagship, unaltered, always up-to-date phone to have. I figured I'd be on the latest version of Android with this phone for many years. I wanted to keep it stock, but they've forced me to now go rooted. I suppose I could now flash a KK ROM, but I'm not sure what that would benefit me at this point.
Thank you again SO much for your help and fast reply! (Even if I did post this in the wrong place!)
Love XDA!

Ok, so I have to update what happened. Everything seemed to be working fine until I got into my car. My GPS has a bluetooth connection. It would connected, but then almost immediately the Bluetooth service would crash on my phone. Happened over and over again. Even after a reboot. Then when I got home, I tried it with my bluetooth speaker. Same exact thing. I figure the bluetooth binaries that I installed screwed up my connections that used to work. I even tried re-pairing them. Didn't help.
I gave up and decided to wipe everything and flash KK. I used CM11 nightly. Now everything, so far, is working as expected. GPS, speaker & fitbit. CM KK takes some getting used to over stock JB. I don't know what changes are KK and which are CM.

Android 4.4.2 Omnirom

I read about an omnirom available for our captivate glides running 4.4.2
Anyone tried running this yet? How stable is it?
I found the link here: http://true-android.blogspot.ca/2014/03/update-samsung-captivate-glide-sgh-i927.html
I also dont know, for any rom that has separate gapps, when would you flash those? After or before the new rom? at the same time? Like, if after a ROM flash it automatically reboots, it will boot up with no gapps and likely not run - correct?
Was just curious about how buggy it is. Even if down the road when things are smoother, im excited to see if i can get this one running!

Pawprints1986 said:
I read about an omnirom available for our captivate glides running 4.4.2
Anyone tried running this yet? How stable is it?
I found the link here: http://true-android.blogspot.ca/2014/03/update-samsung-captivate-glide-sgh-i927.html
I also dont know, for any rom that has separate gapps, when would you flash those? After or before the new rom? at the same time? Like, if after a ROM flash it automatically reboots, it will boot up with no gapps and likely not run - correct?
Was just curious about how buggy it is. Even if down the road when things are smoother, im excited to see if i can get this one running!
Click to expand...
Click to collapse
you can find more information here: http://forum.xda-developers.com/showthread.php?t=2541182
Gapps is included. You must install rom zip first, because it formats system partition.
Official gapps doesnt compatible with our phone, I think its better not installing.

hmm..
Pawprints1986 said:
I read about an omnirom available for our captivate glides running 4.4.2
Anyone tried running this yet?
Was just curious about how buggy it is. Even if down the road when things are smoother, im excited to see if i can get this one running!
Click to expand...
Click to collapse
I am using omni ROM . . somehow I find it less buggy than cm 11
Nevertheless I would wanna give my thanks and even though I am pointing out bugs . . I really do appreciate his work .. A lot
Omnirom is very very stable has all if not most of the theming features except for trebuchet launcher
//It is a bit more battery consuming but I like it cause I am able to run my processor at 1.4ghz which is sweeeet!!!
//It has issues with OK Google functionality the audio is lagged and irritating
//The Google experience launcher is not built for it
//It has issues with Google maps 7 but there is a fix to have 6th version to back you up when needed
//it has issues with Skype and the fix is work in progress I guess..
//GPs is a bit slow but works
//WiFi direct crashes for me
Once in a blue moon the phone might rebot itself cause of a crash..
Though considering WiFi tethering , 3g switching, link2sd ,memory swapping
Ksm everything is working really try it . . its an amazing experience from an amazing phone

Can someone tell me the difference between wifi direct, wifi sharing, and wifi sharing manager??
Wifi itself is working in 4.4.2 right?
Also, were your keyboard backlights working automatically or did you ened qwerty led?
is qwerty led something that needs to be running all the time. or "ongoing" in the top drawer?

Wi-fi direct is a type of communication between two devices, similar to Bluetooth, so you can send files. I never used this, even when transfering big files from one phone to another, it's better to use an USB OTG cable - the connection speed is lightning fast!
Don't know what you mean about wi-fi sharing. Maybe wi-fi tethering (hotspot) - it's when you share your phone 2G/3G internet connection via wi-fi. This thing is working fine. Wi-fi itself is working, of course.
As for keyboard light: when tested OmniROM, I used liblight solution, but the qwertyled using is simple too: just launch it and you're done. While the service is running, keyboard light will work.
Now I'm on CM 11, and I have 11 days of uptime already, I recommend this ROM (but that's just my taste). In CM 11 keyboard backlights are working from the box, no need for qwertyled.
Also, I looked at the link you posted, to the true-android blog. Please, don't use the guide one can found there, it's awful. You can't install 4.4.2 ROM with recommended 2.6.3.0 TWRP, the correct one is 2.6.3.1 from bubor here, and you don't need any gapps beside included in the ROM.
Better use this guide from stormdude124: [UPDATED][2014][How-to]Everything you need to know and do to your Captivate Glide, it's updated, it's verified and there's no ads!

Makshow said:
Now I'm on CM 11, and I have 11 days of uptime already, I recommend this ROM (but that's just my taste). In CM 11 keyboard backlights are working from the box, no need for qwertyled.
Also, I looked at the link you posted, to the true-android blog. Please, don't use the guide one can found there, it's awful. You can't install 4.4.2 ROM with recommended 2.6.3.0 TWRP, the correct one is 2.6.3.1 from bubor here, and you don't need any gapps beside included in the ROM.
Better use this guide from stormdude124: [UPDATED][2014][How-to]Everything you need to know and do to your Captivate Glide, it's updated, it's verified and there's no ads!
Click to expand...
Click to collapse
Can you use a cyanogen mod rom with clockworkmod recovery installed? i remember trying cyanogenmod with my phone and couldnt get it to work.

Just flash TWRP 2.6.3.1 from link above, it's superior to clockworkmod recovery (CWM) in all ways: touch interface, working backups with compression, charging support and it allows to install KitKat roms. With CWM you can install ROMs up to android 4.3, so, you still can install CM 10.1.3 or CM 10.2 with CWM, but not CM 11.

about wifi direct and sharing...
Pawprints1986 said:
Can someone tell me the difference between wifi direct, wifi sharing, and wifi sharing manager??
Wifi itself is working in 4.4.2 right?
Also, were your keyboard backlights working automatically or did you ened qwerty led?
is qwerty led something that needs to be running all the time. or "ongoing" in the top drawer?
Click to expand...
Click to collapse
Hey yeah the difference btw wifi direct and sharing is that in wifi direct you connect two devices directly to transfer files...
in wifi sharing you need to host a web adress to share your files
as a result in wifi sharing you host a list of your stuff on a web adress(local) which gets downloaded by other devices on your wifi connection
and a wifi sharing manager can either do this (host ur files using an ip) or my personal favorite is astro which can acess my pc's sharing folder over wifi which is preety awesome>..unlimited storage
also note that in a wifi sharing manager you cannot recieve files easily . . maybe airdroid but it can only run on a pc
wifi sharing apps are airdroid and other file managers like root browser
wifi direct requires specific drivers and libs... i guess.. hence not all devices can do it ..
anyway you should go for cm 11 or omni both are incredibly stable with an occasional hiccup.. which is occasional heh
also would suggest that if you do proceed to install please follow from the developer sources on xda rather than some blog etc

Android 6.0 Marshmallow for jflte(Unofficial cm13)

After impatiently waiting for that day to arrive, here it is: Android 6.0 for our dear s4 is there thanks to our great dev @AntaresOne.
He brought us an unofficial cm13 for the unified s4 variants (jflte) which is stable enough to be used as a daily driver. All credits go to him.
Almost all the basic functions work.
FYI, it's a goodbye gift.
Download link: http://forum.xda-developers.com/showpost.php?p=63729768&postcount=312
Please, used the gapps suggested by the dev. Otherwise, you may face bootloop.
Enjoy but remember to thank @AntaresOne for this awesome work!

Reserved

Reserved...

I'm downloading it right now and going to give it a shot. Hopefully everything works out, including using streaming services like Netflix or Hulu Plus. Will report findings soon.

I have read that cm13 will support tmobile wifi calling will it work with the s4 builds? Is it implemented in this build?

madcow007 said:
I have read that cm13 will support tmobile wifi calling will it work with the s4 builds? Is it implemented in this build?
Click to expand...
Click to collapse
It's not implemented yet

Flash failed... Hmmm. Maybe corrupt data?

bbroad4455 said:
Flash failed... Hmmm. Maybe corrupt data?
Click to expand...
Click to collapse
It should work if the signature verification is skipped.
Also be sure that the downloaded file is correct; some of the mirrors do not yield the correct file andd have a different checksum.
The checksums should be:
Code:
cm-13.0-20151108-UNOFFICIAL-jflte.zip
Size: 297,677,777 bytes
CRC32: 919fb9b9
MD5: cfc714dda4be22afabdaa95e98f72bed
SHA-1: 97d993fccce699fdeb15bb1d39ad074220ce4a75
SHA-256: a3eff70e51b3c32f94808f9ade592d9cb9e1da07113773f2aa30d62503429295

Successfully flashed here. However internal and external mic don't work as well as auto time zones. Other than that, I haven't noticed an issue. I guess at first glance it also does not appear to be rooted.

Trying this on my Metro PCS S4 (jfltetmo) since it's not my daily driver and not connected to their network. So far it seems to be stable, but the battery usage is not good at the moment. The top of the list shows "Uncounted" using the battery the most. Not sure what that means. I am willing to help with testing this rom for this model jfltetmo, so if you want any info from this phone, let me know what and how to get it, and I will gladly share.

This thing did not work for me, leaving the phone stuck at the Galaxy S4 screen at boot. Restored using Odin and stock image, my device is the M919V.

CM 13flashed
Everything works fine but microphone. It does not work at all; call, skype, hangout, voice recorder, etc.

pointdotslash said:
Everything works fine but microphone. It does not work at all; call, skype, hangout, voice recorder, etc.
Click to expand...
Click to collapse
It's a known issues in all cm13 built. No fix for it yet.

Is this ROM dead? or will it be updated to work with microphone fix?

madcow007 said:
I have read that cm13 will support tmobile wifi calling will it work with the s4 builds? Is it implemented in this build?
Click to expand...
Click to collapse
It cannot. Since ICS, T-Mobile's WiFi Calling has depended on TouchWiz to work. Sadly, for the S4, TouchWiz is stuck on 4.4.4 KitKat and likely won't be moving up to Lollipop. As of now, I keep a working KK TW Rom backup up as a Nandroid in case I need it but I've since resigned myself to moving on.

Need something to fix 6.0
I downloaded the Android 6.0 marshmallow for tmobile and the 6.0 gapps i flash them with TWRP recovery on my galaxy s4 I cannot create an APN because it says my device model is unknown and sims card is not inserted what do I need to do to fix this or is it just a CM bug.

Same^ any help

i used these micro gapps http://opengapps.org/

madcow007 said:
I have read that cm13 will support tmobile wifi calling will it work with the s4 builds? Is it implemented in this build?
Click to expand...
Click to collapse
I think that a work around would be to call with hangouts... That's what I use to call over Wi-Fi
Sent from my SGH-M919 using Tapatalk

jfltetmo
vasolini said:
Trying this on my Metro PCS S4 (jfltetmo) since it's not my daily driver and not connected to their network. So far it seems to be stable, but the battery usage is not good at the moment. The top of the list shows "Uncounted" using the battery the most. Not sure what that means. I am willing to help with testing this rom for this model jfltetmo, so if you want any info from this phone, let me know what and how to get it, and I will gladly share.[/QUOTEiwould definatly interested in this that i have s4 with 5.1.1 rooted aicp rom w/twrp.
]
Click to expand...
Click to collapse