Database Info

Any issues or questions regarding CyanogenMod 10 - Please ask here

If anyone has questions or concerns regarding the CyanogenMod 10 please ask here and stay away from the development section for these posts, as it has over 3000 posts.

To start off please read the CM10 faq on the first Page of the CM10 thread before asking any questions here or in the official thread. Thanks
Sent from my HTC One X(L/AT&T)

So, does (or will) the camera app in CM10 have the same burst mode that the Sense camera has? Can you take AS MANY photos AS QUICKLY? Will those photos be similar quality? Will we be able to pull stills from previously recorded video? Or take Hi Res stills while shooting HD video?
I read the last 15 pages of the development thread and didn't see any of this being discussed.
Thanks a bunch!
Billy
Sent from my Nexus 7 using Tapatalk 2

Burst mode is a sense cam feature only, because there is no sense in cm those features will not be there. Your best bet is if you want sense cam but asop feel go with clean rom or tn rom, they can desense the launcher but keep the apps but you will be on ics. But i will say the cm cam is alot faster then it used to be and is still a good camera.

**PLEASE READ IN REGARDS TO CAMERA ISSUES WITH CM10**
The rapid fire camera mode is named Zero Shutter Lag or ZSL and there are plans to implement this in the near future. You will also soon be able to take still pictures while recording video. H8 & the CM10 team are working on getting every feature of the camera to 100% and they say they are nearly there.
However, as of right now the camera, video camera, & panorama mode is still relatively broken. The camera's bare bones features are working but only in the build's that are labeled as EXPERIMENTAL. The regular CM10 nightlies do not contain the WORKAROUND that H8 has come up with because this workaround has not been merged with the offical CM10 nightlies that the One XL is now getting.
Word on the street is the camera will be 100% working very, very soon so please be patient.
If you use and rely on the camera on a daily basis...please only flash the EXPERIMENTAL builds until further notice!!!

PaKMaN787 said:
To start off if you want the video camera and/or audio fixes, please download the experimental build instead of the new nightlies. They will soon be merged.
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
by audio fixes do you mean caller volume? Im on the 8/22 build. I heard the 8/19 has good caller voice but it kills my battery.

Any idea how we can get native emoji working? It gives the option to download the add on in keyboards settings. Installs. Then refreshes and shows ready to download again. Also, any plans for Google wallet? This ROM is amazing and ridiculously fast!! Thanks for your hard work and help!!
Sent from my One X using xda app-developers app

yungskeeme said:
by audio fixes do you mean caller volume? Im on the 8/22 build. I heard the 8/19 has good caller voice but it kills my battery.
Click to expand...
Click to collapse
Sorry I meant music by audio. Honestly they aren't even fixes for music it just doesn't seem to work sometimes for nightlies... and in call is always a hit or miss
Sent from my HTC One X(L/AT&T)

PaKMaN787 said:
To start off if you want the video camera and/or. music workarounds, please download the experimental build instead of the new nightlies. They will soon be merged.
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
PaKMaN787 said:
Sorry I meant music by audio. Honestly they aren't even fixes for music it just doesn't seem to work sometimes for nightlies... and in call is always a hit or miss
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
Definetly hit or miss. Heard it was fixed in the 8/28 but no music so I guess I'll stay on 8/22 and deal with it. Heard someone say they flashed AOKP ICS rom and reflashed CM10 and it was fixed.

bstephens2u said:
Any idea how we can get native emoji working? It gives the option to download the add on in keyboards settings. Installs. Then refreshes and shows ready to download again. Also, any plans for Google wallet? This ROM is amazing and ridiculously fast!! Thanks for your hard work and help!!
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I'll do a little poking around and see if I can get this working (I probably won't) and I'll let you know if I do!

tropazr said:
**PLEASE READ IN REGARDS TO CAMERA ISSUES WITH CM10**
The rapid fire camera mode is named Zero Shutter Lag or ZSL and there are plans to implement this in the near future. You will also soon be able to take still pictures while recording video. H8 & the CM10 team are working on getting every feature of the camera to 100% and they say they are nearly there.
However, as of right now the camera, video camera, & panorama mode is still relatively broken. The camera's bare bones features are working but only in the build's that are labeled as EXPERIMENTAL. The regular CM10 nightlies do not contain the WORKAROUND that H8 has come up with because this workaround has not been merged with the offical CM10 nightlies that the One XL is now getting.
Word on the street is the camera will be 100% working very, very soon so please be patient.
If you use and rely on the camera on a daily basis...please only flash the EXPERIMENTAL builds until further notice!!!
Click to expand...
Click to collapse
This is such great news! I'd like to publicly commit to donating $30 to the team that makes this happen!
Anxiously waiting,
Billy
Sent from my Nexus 7 using Tapatalk 2

I have a couple of general questions.
1. Will the official release of HTC JB drastically and rapidly improve the project? Will lots of things need to be redone/reoptimized? Or it's simply some missing links being filled? What kind of time frame can we expect for a fully working CM10 (equal or close to the quality of CM on the other officially supported devices) following the HTC JB release?
2. Exactly how was the team able to develop this rom so far without official support? And how much farther can this realistically go if we do not get the official JB in the near future (hopefully this doesn't happen). From what I read, I'm under the impression that this rom is already in a much better shape compared to the development phase CM builds on many other non-officially supported devices (for example ICS/JB builds on older devices that received EOL after GB). Is the kernel of the phone somewhat "easier" to crack compared to those devices or is that we have some super talented developers behind this project? And the developer seems confident that even without official HTC JB, this rom can pretty much become a *fully working* one?
Thanks for the awsome work!

Is wake locks an issue with cm10 so far or just a few users isolated type instance? I was getting massive wake lock for alarmmanager that I do not get on CleanRom.

anyone else getting bad battery life with this ROM? currently running the 8/29 nightly.
Right now im at 33% battery with 11h on the battery but only 1h45min screen time. I also have GPS on and brightness around 1/2..which could possibly be the problem.

JeepFreak said:
This is such great news! I'd like to publicly commit to donating $30 to the team that makes this happen!
Anxiously waiting,
Billy
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well, its done and it should be in the next nightly (20120901)...assuming nightlies are fixed (today's nightly 404's).

toptalent said:
I have a couple of general questions.
1. Will the official release of HTC JB drastically and rapidly improve the project? Will lots of things need to be redone/reoptimized? Or it's simply some missing links being filled? What kind of time frame can we expect for a fully working CM10 (equal or close to the quality of CM on the other officially supported devices) following the HTC JB release?
2. Exactly how was the team able to develop this rom so far without official support? And how much farther can this realistically go if we do not get the official JB in the near future (hopefully this doesn't happen). From what I read, I'm under the impression that this rom is already in a much better shape compared to the development phase CM builds on many other non-officially supported devices (for example ICS/JB builds on older devices that received EOL after GB). Is the kernel of the phone somewhat "easier" to crack compared to those devices or is that we have some super talented developers behind this project? And the developer seems confident that even without official HTC JB, this rom can pretty much become a *fully working* one?
Thanks for the awsome work!
Click to expand...
Click to collapse
1. Nope, didn't help us at all. Didnt need it. As far as I'm concerned, after tonight's nightly (technically...tomorrow morning's nightly) everything is pretty much 100%. a few bugs here or there...but I think the Nexus devices are the only ones ahead of us regarding "working" status.
2. We're magical. *snicker* just kidding. We've pretty much completely beat HTC to Jellybean with CM10. The great part of the kernel work intervigil has provided is that we use the same kernel for ICS and JB. Meaning we can backport all JB stuff to ICS with minimal differences. We are very confident that this will be a fully working one. The last piece we needed was the Camera HAL which we *just* received.
Thank you for the thanks! Enjoy!

h8rift said:
Well, its done and it should be in the next nightly (20120901)...assuming nightlies are fixed (today's nightly 404's).
Click to expand...
Click to collapse
Wooooooooooot!! And would it just be TeamDouche in general that deserves the donation? Or was somebody specific working on this?
Thanks H8!
Billy
Sent from my Nexus 7 using Tapatalk 2

1. Nope, didn't help us at all. Didnt need it. As far as I'm concerned, after tonight's nightly (technically...tomorrow morning's nightly) everything is pretty much 100%. a few bugs here or there...but I think the Nexus devices are the only ones ahead of us regarding "working" status.
2. We're magical. *snicker* just kidding. We've pretty much completely beat HTC to Jellybean with CM10. The great part of the kernel work intervigil has provided is that we use the same kernel for ICS and JB. Meaning we can backport all JB stuff to ICS with minimal differences. We are very confident that this will be a fully working one. The last piece we needed was the Camera HAL which we *just* received.
Thank you for the thanks! Enjoy!
Click to expand...
Click to collapse
That sir, is very impressive. "Beating HTC to jellybean" sounds so satisfying in an ambitious way, and completely changes the way these games used to be played. Hats off to all the "magicians" who made this happen!
One more question: what about LTE? I'm currently on the 4.0.4 based CleanRom 4.5, which is my first custom rom flashed on the phone (only bought it a week ago). Do I have to flash back to a 4.0.3 based ROM (which I have trouble finding) before flashing to CM 10? If the answer is still yes, is a solution being worked out to troubleshoot and solve the problem?

toptalent said:
That sir, is very impressive. "Beating HTC to jellybean" sounds so satisfying in an ambitious way, and completely changes the way these games used to be played. Hats off to all the "magicians" who made this happen!
One more question: what about LTE? I'm currently on the 4.0.4 based CleanRom 4.5, which is my first custom rom flashed on the phone (only bought it a week ago). Do I have to flash back to a 4.0.3 based ROM (which I have trouble finding) before flashing to CM 10? If the answer is still yes, is a solution being worked out to troubleshoot and solve the problem?
Click to expand...
Click to collapse
I'm not entirely sure if something is being worked on but I think you should flash CR4.0 as it is definitely working and is 4.0.3 base which is what h8rift said to flash.
Sent from my HTC One X(L/AT&T)

May I ask what is the right procedure to flash CM10? In the zip there is a boot.img. Do we need to manually extract and flash it with fastboot?
I ask this because some people (including me) can't make LTE to work in CM9/10. Some say by flashing CleanROM 4.0, full reset then flash CM10, LTE will be the default. This trick does not work for me. What is the mechanism of this trick? What stays after full reset? All I can think is the boot image. But even manually flashing CleanROM's boot.img then flash CM10 does not work for me. Changing build.prop (ro.ril.def.preferred.network and ro.telephony.default_network as suggested at code.google.com/p/cyanogenmod/issues/detail?id=1623 , sorry can't link external) of course does not work either.
I know #*#*info*#*# can change the preferred network type, but it does not stick after reboot, which renders this approach useless.
Thanks.

[Q] Stability of CM10?

I was running CM10 back in the day when it was not yet officially hosted by the CM team and I I went back to stock since there were a couple issues with the video recorder and other things. I see now that CM10 is officially being hosted by the CM team but they are still nightly, but I still would like to give it another go around. I was just wondering if there what are the major issues with the ROM right now (if any)?
The first posts don't really tell much except "it's a major work in progress" and the official change log might as well be gibberish to me, and I'm definitely not about to go through all 500+ pages, so if someone would give me a brief summary of what is/isn't working it would be much appreciated!

brob925 said:
I was running CM10 back in the day when it was not yet officially hosted by the CM team and I I went back to stock since there were a couple issues with the video recorder and other things. I see now that CM10 is officially being hosted by the CM team but they are still nightly, but I still would like to give it another go around. I was just wondering if there what are the major issues with the ROM right now (if any)?
The first posts don't really tell much except "it's a major work in progress" and the official change log might as well be gibberish to me, and I'm definitely not about to go through all 500+ pages, so if someone would give me a brief summary of what is/isn't working it would be much appreciated!
Click to expand...
Click to collapse
Its definitely daily driver ready. Just some wake locks making it not have as good battery life as sense. But everything else works great. The build bot has been broken since 10/12 so when the next official nightly comes out, it should have a bunch of new things... Maybe new kernel?
Sent from my HTC One X using xda app-developers app

ethantarheels123 said:
Its definitely daily driver ready. Just some wake locks making it not have as good battery life as sense. But everything else works great. The build bot has been broken since 10/12 so when the next official nightly comes out, it should have a bunch of new things... Maybe new kernel?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Sweet, I might just have to flash it again since I usually have a charger handy with me so battery life isn't a huge a concern. I'm sort of confused by what you mean about the next official nightly... I thought nightlys were released every... well night?

brob925 said:
Sweet, I might just have to flash it again since I usually have a charger handy with me so battery life isn't a huge a concern. I'm sort of confused by what you mean about the next official nightly... I thought nightlys were released every... well night?
Click to expand...
Click to collapse
The night lies have been down because some changes were made to the code upstream that causes the Evita build to fail. They're working on the kernel fixes to get the night lies to compile again but apparently its very involved.
Sent from my One X using Tapatalk 2

There was an experimental one posted today

my wifi doesn't crap out on the experimental nightly which was my only issue with 10/12

One should always read at min the last 10 pages of a thread of a Rom you might flash, an really it's expected of anyone.
WR
Sent from my HTC One X

Just a heads up dont know if anyone else is having this problem.
I rooted my 2.2 with the new 2.2 root instructions and downloaded the latest (10/25:experimental[cm-10-20121025-EXPERIMENTAL-evita.zip ]) cm10 build, everything works great, even wifi, except MOBILE data. I'm on straight talk, and man im getting slow speeds, nothing changed to APN, i think its a radio problem. anyone got any suggestions? I attached the radio link, which radio should i flash?
http://forum.xda-developers.com/showthread.php?t=1694012&page=99

[Q] Stability of roms for the g2x

Hi, I have a wind mobile lg-p999dw (T-Mobile G2x)
I wanted to know that since official updates never came out for the g2x cyanogenmod and other roms were created.
Since it was an abandoned phone, developers put this phone in their priority list.
CM7 was very successful and it went all the way to a fully stable version of CM 7.2.
Ever since CM9 came out these teams lost hope.
Cyanogenmod, Eaglesblood, Hellfire, Paranoid Android, ...
When jellybean came out CM 9 for the G2x was abandoned at an early stage and development of CM 10 started.
My question is why, WHY WHY WHY hasn't a perfectly stable version of a jellybean rom for g2x not come out that is perfectly as stable like CM 7.2 while other phones like htc one x and samsung galaxy s iii that already get official updates and get the stable version of the rom?

Different reasons for different ROMs.
For some older ones there wasn't HWA, but a hacked together version that still wasn't perfect and things like the camera had issues.
For newer ones the only major problem seems to be that the radio just isn't working.
It came down to LG not releasing drivers/code. People could hack together some things, but that could only get us so far. LG did a lot of weird things with their code, I believe.
At least, in my lurking and search, that's how I understand it. I'd love to see a fully working jellybean rom for the G2x since my girlfriend got it from me as a hand me down.
Take a look through adampk's CM10.1 thread in the development section and it's User Thread here in the general section. You'll get a good view at what's not working and what everyone has tried. Maybe you can even help out.

Shamoy said:
Hi, I have a wind mobile lg-p999dw (T-Mobile G2x)
I wanted to know that since official updates never came out for the g2x cyanogenmod and other roms were created.
Since it was an abandoned phone, developers put this phone in their priority list.
CM7 was very successful and it went all the way to a fully stable version of CM 7.2.
Ever since CM9 came out these teams lost hope.
Cyanogenmod, Eaglesblood, Hellfire, Paranoid Android, ...
When jellybean came out CM 9 for the G2x was abandoned at an early stage and development of CM 10 started.
My question is why, WHY WHY WHY hasn't a perfectly stable version of a jellybean rom for g2x not come out that is perfectly as stable like CM 7.2 while other phones like htc one x and samsung galaxy s iii that already get official updates and get the stable version of the rom?
Click to expand...
Click to collapse
You have to understand that most of CM9 and CM10 builds right now are based on a deprecated kernel and a modified android framework, known as "hackfest", which lacks many functions needed in the newer OSes. If you try Adampk's build 6 with, optionally, my kernel, you will see that it is really stable and works well, but not the radio. This is being worked on actively.
Most of the teams you specified simply switched to a newer model, not because of a compatibility issue. Cyanogen left us because our phone maintainer, RC, couldn't fix the radio. If he did release it anyways he would've received a lot of complains, which he didn't want.

Why why why... Wah wah wah..
Sent from my LG-P999 using xda app-developers app

Mazout360 said:
You have to understand that most of CM9 and CM10 builds right now are based on a deprecated kernel and a modified android framework, known as "hackfest", which lacks many functions needed in the newer OSes. If you try Adampk's build 6 with, optionally, my kernel, you will see that it is really stable and works well, but not the radio. This is being worked on actively.
Most of the teams you specified simply switched to a newer model, not because of a compatibility issue. Cyanogen left us because our phone maintainer, RC, couldn't fix the radio. If he did release it anyways he would've received a lot of complains, which he didn't want.
Click to expand...
Click to collapse
Thanks for someone whose actively working on it and replying. Glad to have someone with the knowledge xP
Sent from my Nexus 4 using xda premium

How do I install google apps with CyanogenMod 10
Which Gapps do you recommend for the TMobile LG G2X P999?
Currently running:
gapps-jb-20120726-signed
cm-9.9.9-JB-p999-2(OS)
Issue I am having is major feedback when making a any calls on...

Mordephi said:
Which Gapps do you recommend for the TMobile LG G2X P999?
Currently running:
gapps-jb-20120726-signed
cm-9.9.9-JB-p999-2(OS)
Issue I am having is major feedback when making a any calls on...
Click to expand...
Click to collapse
Do a search for baseband.zip, or look in these topics, there should be links in them.
Sent from my LG-P999 using xda app-developers app

redmonke255 said:
Do a search for baseband.zip, or look in these topics, there should be links in them.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
WOW that worked great! Thank you very much. Do you know if there is a solutions for the bluetooth not connecting or no audio on bluetooth?

Downgrading your baseband to 2.3.3 is only known way to get working audio for Bluetooth calling at the moment
Sent from my LG-P999 using xda premium

Pain-N-Panic said:
Downgrading your baseband to 2.3.3 is only known way to get working audio for Bluetooth calling at the moment
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Or stock 2.3.4/based ROMs. It's not too bad you know : angel:
-- The noob says:
From first-hand experience, a smartphone is incapable of making you smarter!

mansa_noob said:
Or stock 2.3.4/based ROMs. It's not too bad you know : angel:
-- The noob says:
From first-hand experience, a smartphone is incapable of making you smarter!
Click to expand...
Click to collapse
LOL yeah I guess you could do that too. I'm just way too much of a tweaker/modder/flashcrazy to keep a stock phone!

Pain-N-Panic said:
LOL yeah I guess you could do that too. I'm just way too much of a tweaker/modder/flashcrazy to keep a stock phone!
Click to expand...
Click to collapse
Lol my wife won't let me mess with her nexus 4 but it drives me nuts that she can't change her battery icon to percentage and change lockscreen background and...omg I could go all day.

TwitchyEye said:
Lol my wife won't let me mess with her nexus 4 but it drives me nuts that she can't change her battery icon to percentage and change lockscreen background and...omg I could go all day.
Click to expand...
Click to collapse
Based on experience, it is generally not a good idea to mess with your wife's phone . LOL.
-- The noob says:
From first-hand experience, a smartphone is incapable of making you smarter!

mansa_noob said:
Based on experience, it is generally not a good idea to mess with your wife's phone . LOL.
-- The noob says:
From first-hand experience, a smartphone is incapable of making you smarter!
Click to expand...
Click to collapse
Lol so true! I'm just glad she's done with this one. The first day she got her new phone she goes how do you pull the battery? I go you won't need to. She goes
If only they had a head exploding emoji

KitKat?

When should we expect the release of KitKat for the Relay?

When TeamApexQ deems fit to release it.
Sent from my Amazon Kindle Fire2 using Tapatalk 4

Nardholio said:
When TeamApexQ deems fit to release it.
Sent from my Amazon Kindle Fire2 using Tapatalk 4
Click to expand...
Click to collapse
Nardholio, do you expect any major innovations, and most importantly, any major sources of bugs or instabilities with KitKat?
Thanks!!

Guiyoforward said:
Nardholio, do you expect any major innovations, and most importantly, any major sources of bugs or instabilities with KitKat?
Thanks!!
Click to expand...
Click to collapse
That's a question we won't really be able to answer until there is more solid information on KitKat generally available.

Looks like CM is setting up the KitKat AOSP code for there builds Check out @CyanogenMod's Tweet: https://twitter.com/CyanogenMod/status/396000889011326976
Sent from my SGH-T699 using Tapatalk
---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------
Cyanogenmod Google+ post " Android 4.4 Source
Source is now being pushed to the AOSP trees. Of course, when it is all there we will begin the process of figuring out what changed, needs work, and/or is no longer feasible or needed.*
We are not in a rush to get 4.4 builds out. We are going to continue the process of working on CM 10.2 M1 - getting that out the door and onto your devices. Further, we will 'finish' the 10.2 code base, similar to what we did with 10.1.*
As a friendly reminder, please don't flood us with requests for 4.4 - we all want new and shiny things, but we will not do so at the expense of abandoning the hard work our contributors have put into 10.2.*
Final note, a lot of folks are reading into the "512mb" item on the release notes. No, this does not mean a sudden resurrection of older hardware, there are dependencies beyond the RAM (and CM has enforced that minimum since ICS)."
Sent from my SGH-T699 using Tapatalk

pst @Magamo this thread was best ended with a simple "when I say so" response and nothing more
Sent from my SGH-T699 using Tapatalk

Nardholio said:
pst @Magamo this thread was best ended with a simple "when I say so" response and nothing more
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
I actually was referring to an official KitKat OTA update from T-mobile.
How long did it take them to release a JB update after it was first introduced?
I have no interest in a CM ROM full of bugs and things that don't work.

andrewsfm said:
I actually was referring to an official KitKat OTA update from T-mobile.
How long did it take them to release a JB update after it was first introduced?
I have no interest in a CM ROM full of bugs and things that don't work.
Click to expand...
Click to collapse
Given that we never got upgraded to 4.2 or 4.3 by T-mobile/Samsung, I kinda doubt we'll be getting an official 4.4. And our CM rom, which has been built for us by a couple of people working for free, currently has fewer bugs than the official ROMs.

Jax184 said:
Given that we never got upgraded to 4.2 or 4.3 by T-mobile/Samsung, I kinda doubt we'll be getting an official 4.4. And our CM rom, which has been built for us by a couple of people working for free, currently has fewer bugs than the official ROMs.
Click to expand...
Click to collapse
4.2 and 4.3 were minor updates with no name change. JB was a major update and they did update to it.
4.4 KitKat being a major update, I've got my fingers crossed considering the wide range of devices that it's being planned for.
Was just hoping to see if there was any news on a KK update for this model.
CM is fun to play with and all, but it's not something I would trust on an everyday phone.

I use CM as a daily driver every day, and have been doing so since 10.2 became CyanogenMod official - everything just works. Now I'm not one of those people who demands a LOT of my phone, but I use it in the course of doing my job daily and it performs better, and more efficiently (with regards to battery consumption) than it did on the debloated stock rom, so much so that I deleted my Nandroid of that setup.
Sent from my SGH-T699 using the XDA-Developers app.

onebornoflight said:
I use CM as a daily driver every day, and have been doing so since 10.2 became CyanogenMod official - everything just works. Now I'm not one of those people who demands a LOT of my phone, but I use it in the course of doing my job daily and it performs better, and more efficiently (with regards to battery consumption) than it did on the debloated stock rom, so much so that I deleted my Nandroid of that setup.
Sent from my SGH-T699 using the XDA-Developers app.
Click to expand...
Click to collapse
I'm not sure if I fall into the category of demanding alot from my phone, but if there are issues like, Wifi and BT can't be on at the same time, that's not good enough. That's a serious issue. So if I forget to turn one of them off, stuff stops working? That's not okay...
I want my camera to work, for videos and photos. I want the phone to do everything the hardware is supposed to do.

andrewsfm said:
I'm not sure if I fall into the category of demanding alot from my phone, but if there are issues like, Wifi and BT can't be on at the same time, that's not good enough. That's a serious issue. So if I forget to turn one of them off, stuff stops working? That's not okay...
I want my camera to work, for videos and photos. I want the phone to do everything the hardware is supposed to do.
Click to expand...
Click to collapse
Awesome! And you want that for free? You don't seem to appreciate a lot the effort that other people are putting into this...

The wifi/bluetooth issue isn't that bad. It only falls apart when WiFi is on and connected to a 2.4GHz access point, and bluetooth is on and connected to a bluetooth device. If you have an N wifi access point that operates at 5Ghz, you can just connect to that instead of the 2.4Ghz node and then the two play nice. It's what I do.

Jax184 said:
The wifi/bluetooth issue isn't that bad. It only falls apart when WiFi is on and connected to a 2.4GHz access point, and bluetooth is on and connected to a bluetooth device. If you have an N wifi access point that operates at 5Ghz, you can just connect to that instead of the 2.4Ghz node and then the two play nice. It's what I do.
Click to expand...
Click to collapse
I would do this if I had a 5GHz AP, but what I'm saying is that I don't want to have to worry about stuff like that.
Guiyoforward said:
Awesome! And you want that for free? You don't seem to appreciate a lot the effort that other people are putting into this...
Click to expand...
Click to collapse
I don't want anything for free, except a stock KitKat update from T-Mobile/Samsung for the hardware I paid for... At no point did I say I was interested in CM. I've been explaining why I'm not, the whole time.
I started this thread to find out how long historically after the release of a new OS, does it usually take Samsung/T-Mobile to release an OTA?

andrewsfm said:
I would do this if I had a 5GHz AP, but what I'm saying is that I don't want to have to worry about stuff like that.
I don't want anything for free, except a stock KitKat update from T-Mobile/Samsung for the hardware I paid for... At no point did I say I was interested in CM. I've been explaining why I'm not, the whole time.
I started this thread to find out how long historically after the release of a new OS, does it usually take Samsung/T-Mobile to release an OTA?
Click to expand...
Click to collapse
Normally only after the Samsung high-end phones get the update and they are just barely getting Android 4.3. It also depends if they decide to update this phone at all. I have been asking t-mobile and Samsung that and they keep blaming each other or referring me to the forum for the phone on there websites.
Sent from my SGH-T699 using Tapatalk

chris122380 said:
Normally only after the Samsung high-end phones get the update and they are just barely getting Android 4.3. It also depends if they decide to update this phone at all. I have been asking t-mobile and Samsung that and they keep blaming each other or referring me to the forum for the phone on there websites.
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
I guess Windows has spoiled me, because I don't understand how it's so hard to port Android to each device.
AMD or Intel, they both use the same instruction set, so they work on any x86/x64 processor, and then you install drivers for your hardware peripherals.
Shouldn't Android run on any ARM processor, and then just have drivers that need to be plugged into it for each component of the phone to work?
Apparently it's a lot more complicated than that, but why...

andrewsfm said:
I guess Windows has spoiled me, because I don't understand how it's so hard to port Android to each device.
AMD or Intel, they both use the same instruction set, so they work on any x86/x64 processor, and then you install drivers for your hardware peripherals.
Shouldn't Android run on any ARM processor, and then just have drivers that need to be plugged into it for each component of the phone to work?
Apparently it's a lot more complicated than that, but why...
Click to expand...
Click to collapse
A lot of the complexity comes from the manufacturers of the SoCs not opening up the workings of their drivers to the wider world that makes porting to new devices, and to new versions of Android so difficult. Things work on one kernel, or one interface, and that's it, and we have no way of tweaking it to work in other ways. Back to the subject at hand. I personally suspect that the Relay will get no official update to KitKat. The Relay is over a year old, T-Mobile has been trying to dump it since 2013 began, and they are the only retailer. The 4.1.2 Jelly Bean updates were rolling out to the then mainline Samsung phones within a week of the Relay's release in September 2012, and we didn't get our update (which frankly is a broken PoS, ESPECIALLY when held up against any CM build for the Relay) until March or April of '13, so expect another 6 months before we MIGHT (and likely won't) get an official 4.3 update.

Looks like coding for CM 11 has started. Check out @CyanogenMod's Tweet: https://twitter.com/CyanogenMod/status/397817644650205185
Sent from my SGH-T699 using Tapatalk

Magamo said:
A lot of the complexity comes from the manufacturers of the SoCs not opening up the workings of their drivers to the wider world that makes porting to new devices, and to new versions of Android so difficult. Things work on one kernel, or one interface, and that's it, and we have no way of tweaking it to work in other ways. Back to the subject at hand. I personally suspect that the Relay will get no official update to KitKat. The Relay is over a year old, T-Mobile has been trying to dump it since 2013 began, and they are the only retailer. The 4.1.2 Jelly Bean updates were rolling out to the then mainline Samsung phones within a week of the Relay's release in September 2012, and we didn't get our update (which frankly is a broken PoS, ESPECIALLY when held up against any CM build for the Relay) until March or April of '13, so expect another 6 months before we MIGHT (and likely won't) get an official 4.3 update.
Click to expand...
Click to collapse
Ah k I see. The hardware vendors are mostly to blame it seems.
I may try a stable CM11 if that ever sees the light of day, but I won't hold my breath.
I've heard about the official JB ROM being problematic, so I plan to stay on ICS the phone originally shipped with.
I'm just glad to be getting rid of my Droid3 and Gingerbread.

andrewsfm said:
Ah k I see. The hardware vendors are mostly to blame it seems.
I may try a stable CM11 if that ever sees the light of day, but I won't hold my breath.
I've heard about the official JB ROM being problematic, so I plan to stay on ICS the phone originally shipped with.
I'm just glad to be getting rid of my Droid3 and Gingerbread.
Click to expand...
Click to collapse
True, there have been some bugs. However, I use the official nightly of cm10.2 as a daily driver. I'd rather put up with the MINOR issues that are left (hardware is stable for the most part) than have a manufacturer ROM. IMHO, the stock ROM that comes with the phone is usually full of crap bloat ware that I don't use and takes up space, and a UI that is SEVERELY limited in customization.
Also, the more people participate and report problems, the faster it takes TeamApex to fix and push out. At least team apex RESPONDS to their users. As mentioned before, it can take as long as 6-8 months after an android release for the manufacturer to roll out an update...still full of crap ware that's NOT used and cannot be uninstalled without root privileges or botching up the UI further.
These people who work tirelessly to provide to us, the end user, an updated version of Android, do so out of their own free will, and don't get a penny. These devs are here to proudly share what they have created, and I applaud and give my utmost respect to them.
You don't wanna install aftermarket firmware? Don't want to aid in bug reporting? Fine, put up with the crap that the manufacturer pushes onto you. Plus, Samsung & T-Mobile don't get any more of your hard earn dollars rolling out an Android update for our year-old device. They'd rather you dump it and buy the latest phone. THAT'S THEIR BUSINESS MODEL! So they have no interest in rushing an update to something as "old" as the Relay.
If you want JB or KK and are unwilling to wait for & install after-market firmware, I suggest you pony up the dough and buy a nexus 5. Better still, learn how to dev and make your own version of JB or KK for the Relay. That's the beauty of open source.
Your rant and *****ing about when "they are going to develop Kit Kat" makes you come across as arrogant, snobbish, and child-like.
Sorry for MY ranting, but it's unappreciative asshats like andre that just piss me off.
Sent from my SGH-T699 using XDA Premium 4 mobile app

Cyanogenmod 13 for ATT D850 UNOFFICIAL

I am building this for my general use and thought it would be nice to share. Just to be clear I am not developing anything just making the builds. I dirty flashed over CM12.1 and flashed the latest GAPPS with no problems. Please do not report problems as this is a nightly build and unofficial.
Official builds are out and can be found here...
https://download.cyanogenmod.org/?device=d850
I used the 6.0 micro build gapps from here
http://opengapps.org/

SupaAvenger79 said:
I am building this for my general use and thought it would be nice to share. Just to be clear I am not developing anything just making the builds. I dirty flashed over CM12.1 and flashed the latest GAPPS with no problems. Please do not report problems as this is a nightly build and unofficial.
I used the 6.0 micro build gapps from here
http://opengapps.org/
Nightly Build available here..
https://drive.google.com/folderview?id=0B4rZYkaJF5V0Z3RlR08yclZiVUE&usp=sharing
Click to expand...
Click to collapse
Thanks for sharing!
What is your experience so far with GPS locking & using Google Maps navigation?

crash4fun said:
Thanks for sharing!
What is your experience so far with GPS locking & using Google Maps navigation?
Click to expand...
Click to collapse
It's broke on my end. It can get a position lock but does not seem to track for driving directions. Another bug I discovered was trying to take a picture in a text message and the camera only showing 1 to 2 frames per second, but the regular camera works fine so I assume it has something to do with the text message app. I still use it as a daily driver don't use the driving directions often. I will keep posting the builds as I make them and let you know when that bug is fixed.

[Thanks! Will definitely follow this until CM puts out an official build. Couple other guys that were building unofficial seem to have stopped for the time.

SupaAvenger79 said:
It's broke on my end. It can get a position lock but does not seem to track for driving directions. Another bug I discovered was trying to take a picture in a text message and the camera only showing 1 to 2 frames per second, but the regular camera works fine so I assume it has something to do with the text message app. I still use it as a daily driver don't use the driving directions often. I will keep posting the builds as I make them and let you know when that bug is fixed.
Click to expand...
Click to collapse
Ah, yes it appears to get a lock for me as well, but then won't navigate. I've tried messing with gps.conf in several different manners but no luck.

I'm about to abandon the G3 because there is no official CM support. This is where Cyanogenmod is getting bad press - they claim to offer an alternative OS with the latest updates, but some phones are just left in the dust because no one wants to be the maintainer. Best Buy has started selling the 6P - may head over and pick this up!

Please post a link to the kernel source of the kernel included in your build as per GPLv2 and XDA requirements.
Thanks! And thanks for your contributions.

KennyG123 said:
Please post a link to the kernel source of the kernel included in your build as per GPLv2 and XDA requirements.
Thanks! And thanks for your contributions.
Click to expand...
Click to collapse
Sure thing
https://github.com/CyanogenMod/android_kernel_lge_g3

Still using this everyday but, as I'm sure you noticed, charging has been majorly borked since 12/23. Hope you keep this up and I'll be watching CM changelogs for a fix. GPS would be nice too!

scsgoal31 said:
Still using this everyday but, as I'm sure you noticed, charging has been majorly borked since 12/23. Hope you keep this up and I'll be watching CM changelogs for a fix. GPS would be nice too!
Click to expand...
Click to collapse
Yeah I am hoping the problems are not D850 specific or we will never see a fix. I will keep posting builds semi nightly until CyanogenMod starts posting an official build or until I get a new phone in August. I really think this is still a good phone and wonder why the community went to hell on this one.
Have a Happy New Year everyone.

I've been using CM13 for almost a month and its been great. However I only just got an SD card for Christmas. Now, I'm assuming moving apps to the SD card has changed since it let's you format as internal storage now. However that doesn't work for me. Does anyone know how to move apps to the SD card without formatting it as internal storage?

How did you build this? I've managed to build CM13 for the D850 too, but the result was the phone freezing at the LG bootup logo. Your build seems to work perfectly fine.

slabity said:
How did you build this? I've managed to build CM13 for the D850 too, but the result was the phone freezing at the LG bootup logo. Your build seems to work perfectly fine.
Click to expand...
Click to collapse
Ummm well I don't know what you did wrong, but here are the resources I used...
Dependencies for the build were grabbed from this site
https://source.android.com/source/initializing.html
Then I made a local manifest to include proprietary drivers from https://github.com/TheMuppets along with the branch for the D850 out of cyanogenmod github. Hope that gives you some clues on what went wrong.

SupaAvenger79 said:
Ummm well I don't know what you did wrong, but here are the resources I used...
Dependencies for the build were grabbed from this site
Then I made a local manifest to include proprietary drivers from TheMuppets along with the branch for the D850 out of cyanogenmod github. Hope that gives you some clues on what went wrong.
Click to expand...
Click to collapse
Strange. That's exactly what I did too.
I'll give it another shot and see what's going on. I'd like to take a crack at fixing some of the bugs.

Looks like tonight's build will fix the power charging issues. Yay!

Just posted the the 12/29 build and GPS is fixed we can now find our nearest Hardee's with ease. Thanks @invisiblek

is anyone else experiencing data loss constantly? I have to disable/re-enable data to get it to connect, otherwise I get (!) instead of (LTE). I haven't seen anyone else complain about this and yet it still hasn't been fixed on the 12/31/15 build. D850 stock CM kernel on T-Mobile, only one APN on my list. it happens on any CM13-based ROM.
also this new kernel makes my phone near flawless. it feels much more like a nexus. however it is still shutting down the phone when it overheats, hence when you first install the rom and it creates the cache, it will power off once the setup starts.
Sent from my LG-D850 using Tapatalk

xVermicide said:
is anyone else experiencing data loss constantly? I have to disable/re-enable data to get it to connect, otherwise I get (!) instead of (LTE). I haven't seen anyone else complain about this and yet it still hasn't been fixed on the 12/31/15 build. D850 stock CM kernel on T-Mobile, only one APN on my list. it happens on any CM13-based ROM.
also this new kernel makes my phone near flawless. it feels much more like a nexus. however it is still shutting down the phone when it overheats, hence when you first install the rom and it creates the cache, it will power off once the setup starts.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
I had data problems too on Tmo, a quick APN adjustment fixed it:
https://support.t-mobile.com/thread/95900?start=0&tstart=0

thanks, I applied the changes so I'll see if I have anymore problems. if not then this 13 is my new daily driver.
Sent from my LG-D850 using Tapatalk

Just flashed, great so far! Thanks OP!
Sent from my LG-D850 using Tapatalk