Im thinking it may be the firmware cuz installing cm13 broke my GPS. lock utility apps aren't seeing a single satellite I'm wondering what the best way to fix this would be
Wait for CM13 to be stable.
Builds are now experimental and a lot of features have to be polished before it can be a stable release.
Reli4nth said:
Wait for CM13 to be stable.
Builds are now experimental and a lot of features have to be polished before it can be a stable release.
Click to expand...
Click to collapse
firstly, why do you bother posting... nothing you said makes sense.
They fix basic functionality in nightly builds they don't save the fix for a stable release the reason they release nighties are so people can find issues and resolve them by submitting bugs and logs to cm team and/or discuss issues on forums to brainstorm solutions... i literally was only asking if someone else had already found a fix for it, sometimes there are simple fixes you can do in seconds like alot of video glitches in nightly builds can be fixed by changing video settings in dev options.
second, cm 12.1 doesn't even have a stable release yet so ur asking me to wait several months , if everyone had that ****ty attitude nothing would ever get fixed.
thirdly, i didn't say i was surprised something isn't working when the first nightly was released on the 25th there is obviously going to be issues but the people who are running it already are the ones trying to advance the releases to stable by using the report to CM team feature on the phone from the earliest nightlies to provide them with information to do the polishing you speak of, so why say something like that? it just doesn't make sense. If there are no fixes available (which is why i posted to see if anyone has one) then maybe i'll spend some of my time troubleshooting it... not that i'm a pro engineer or anything but i've found fixes to issues before, plz don't tell me to wait for stable, again if everyone had that attitude there would never be a stable release.
I'm having the same issue on my d852 with the latest CM13. In the d855 cm13 thread someone posted a flashable zip that fixes the problem for them. All it contains is a modified gps.conf so it's safe to flash on our d852. It didn't work for me but it may for you.
http://forum.xda-developers.com/showpost.php?p=64095347&postcount=221
eradicator006 said:
I'm having the same issue on my d852 with the latest CM13. In the d855 cm13 thread someone posted a flashable zip that fixes the problem for them. All it contains is a modified gps.conf so it's safe to flash on our d852. It didn't work for me but it may for you.
http://forum.xda-developers.com/showpost.php?p=64095347&postcount=221
Click to expand...
Click to collapse
appreciate the suggestion but already tried an app that makes a new gps.conf for specific areas didn't work. thanks again.
this issue has been fixed
http://forum.xda-developers.com/lg-g3/general/gps-fix-mm-roms-6-x-t3280787
Related
Hello everyone I did a quick search and couldn't find anything.I would like to know who handles the updates for the CM version of the phone. Is it Oppo or the CM team? Will there be OTA updates or do we have to manually download and install?
Thanks in advance.
Invalid_GR said:
Hello everyone I did a quick search and couldn't find anything.I would like to know who handles the updates for the CM version of the phone. Is it Oppo or the CM team? Will there be OTA updates or do we have to manually download and install?
Thanks in advance.
Click to expand...
Click to collapse
CM will handle the CM version. Oppo will supply updates to their software, but CM will handle the actual ROM itself.
Right now there's only one build released. I have a new build that I'm checking out now, but it's still on 10.2. We should see CM11 very soon, and I predict that it will come with the official Google software built in, so there won't be a need to flash gapps. I might be wrong about that, but I think that's how it will work.
I'll post the link for the update very soon in the correct section.
Invalid_GR said:
Hello everyone I did a quick search and couldn't find anything.I would like to know who handles the updates for the CM version of the phone. Is it Oppo or the CM team? Will there be OTA updates or do we have to manually download and install?
Thanks in advance.
Click to expand...
Click to collapse
Software should be coming out tomorrow, can't wait.
Cyanogenmod does have their new CM Installer software for Windows and Android. If you're not familiar with fastboot, installing recoveries, and all that....it may be the easier way to go....in fact, I'm curious to try it myself.
http://www.tomshardware.com/news/oppo-n1-cyanogenmod,25495.html
I am more interested to see how this will work not only for the N1 but for future CM phones.
Imo if they want to go official they should provide the stable versions OTA to begin with.
Harfainx said:
CM will handle the CM version. Oppo will supply updates to their software, but CM will handle the actual ROM itself.
Right now there's only one build released. I have a new build that I'm checking out now, but it's still on 10.2. We should see CM11 very soon, and I predict that it will come with the official Google software built in, so there won't be a need to flash gapps. I might be wrong about that, but I think that's how it will work.
I'll post the link for the update very soon in the correct section.
Click to expand...
Click to collapse
I'm fairly certain that CM11 won't have included gapps until an official "stable" release occurs.
Only the released version of 10.2 has been approved by Google.
Entropy512 said:
I'm fairly certain that CM11 won't have included gapps until an official "stable" release occurs.
Click to expand...
Click to collapse
I'm talking about the official build of CM11. Steve Kondik has informed me that the build is almost ready to roll. They're just waiting on a few last details... Which I assume is the inclusion of gapps.
Sent from my HTCONE using Tapatalk
All People Update CM. there is the cm-11-20140724-NIGHTLY
First update to the latest nightly in CM page, after that you can update via OTA in your phone, there is Daily updates!!
O-Click, Works, meaby a second lag (while focusing?)
O-Touch Works, not as the touchpad of your lap but works, And for some reason changing the VM to ART works better for me.
3G works
Battery last very good, and its suposed to las more in stand-by if you use ART instead of Dalvik
ART works well by the way.
Q&A for [ROM] [NIGHTLY] [4.4.4] CyanogenMod 11 for Samsung Galaxy Nexus
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
CM11-M11 stable?
Hello,
I have a short question regarding the stability of the newest snapshot M11 of CM11. Are there any bugs which may prevent using it in a productive environment? I'm giving the device away and it probably won't be updated afterwards. M11 would replace the currently installed M7, I stopped updating regularly after having endured an unstable device for two months prior to M7 (and I do not wish to give it away having a nightly installed).
Since a long time ago the native sip client has been fixed. There are other kitkat ROMs out there for other devices which still have an audio bug rendering the sip client useless. Could someone link me to this ROM's fix so other developers could apply it to their ROMs?
I've been trying to search for it myself but I can't find it. Thanks a lot! [emoji4]
Silpion said:
Hello,
I have a short question regarding the stability of the newest snapshot M11 of CM11. Are there any bugs which may prevent using it in a productive environment? I'm giving the device away and it probably won't be updated afterwards. M11 would replace the currently installed M7, I stopped updating regularly after having endured an unstable device for two months prior to M7 (and I do not wish to give it away having a nightly installed).
Click to expand...
Click to collapse
The latest M release should be pretty stable.
Hello @Ziyan
Many thanks for your amazing work.
I just want to know that when we can expect CM 12 for Galaxy Nexus ?
Any news about M12 release? Still not seeing it on the building queue page...thanks Ziyan for your effort!
ImTheDroid said:
Hello @Ziyan
Many thanks for you amazing work.
I just want to know that when we can expect CM 12 for Galaxy Nexus ?
Click to expand...
Click to collapse
By the time they start pushing nightlies (in December), maguro should be fully functional (meaning it will be built too), or I may release test builds earlier
Codename89 said:
Any news about M12 release? Still not seeing it on the building queue page...thanks Ziyan for your effort!
Click to expand...
Click to collapse
They said they'll build it on the weekend.
When Galaxy Nexus Maguro CM M12 build?
Hello Ziyan,
[Edit]: Sorry, I saw the previous post after I posted this question.
I still don't see the M12 for Galaxy Nexus Maguro. Although I see in another thread you mentioned that it will happen once you ask the CM team to build it, but nothing seems to have happened. Just wanted to have this last one of CM11 as it might be better to keep for a long time (in the light of the fact CM12 is coming but might take some time to stabilize). So, any idea, when is the build going to take place?
Thanks...
(I would like to post in the mail thread, but my post count seems to be a problem, anyway..)
After the update to cm11 m12 my phone works really smooth.
As other I noticed that generally the rom degrades its performance after some days probably because of the memory trimm.
I also evidenced performance issues in cm 11 m11 due to Google now voice detection of "Ok google" so I disabled it.
I registered in xda to thank you.
In the CM12 roadmap [1] there's:
1) Watering down of SELINUX protections or Encryption by default. These are base protections L is introducing and we should support these items as such. If your device fails to allow encrypting, it will not get a CM sanctioned release.
Click to expand...
Click to collapse
Currently CM11 kernel has SELINUX set to permissive to fix some bugs (in the dialer iirc), but enforcing should be possible. Just have to add some rules:
https://source.android.com/devices/tech/security/selinux/validate.html
Getting encryption to work without watering it down sounds impossible when it expects hardware backing, which tuna doesn't have. [2]
(Technically tuna hw has TEE support, but google disabled it for keystore already due to a power usage bug [3])
Edit:
Seems like Google left the old software encryption still in:
https://android.googlesource.com/platform/system/vold/+/69f4ebd
(use_keymaster == 0)
Didn't look at CTS yet if one still passes without hardware keymaster.
Or what's your take on it?
[1] http://www.gadgtspot.com/2014/10/31/roundtable-cyanogenmod-12-roadmap-leaked-fun-times-ahead/
[2] http://source.android.com/devices/tech/encryption/index.html#storing_the_encrypted_key
[3] http://nelenkov.blogspot.it/2012/07/jelly-bean-hardware-backed-credential.html
Same here...
Anyone else got problems with video playback in YouTube in the 20150201 nightly?
*Deleted
sorry, delete please
SELinux
Hi there Ziyan,
I don't know if it's a choice or something went wrong in the 05-10 CM11 Weekly build for the Maguro Gnex but the SELinux is disabled... Just wanted to point it out since i know that you guys usualy build with SELinux set to Permessive...
Have a good day
SELinux
Hi @Ziyan SELinux is still disabled in last weekly...
gps fix cm11 maguro
Hi Guys,
I can't get gps fix with cm11 maguro http://forum.xda-developers.com/galaxy-nexus/development/rom-cyanogenmod-11-kvt49l-samsung-t2405147
can anyone help me with this issue? I've tried 'fastergps' app without any luck
kernel left alone, I didn't changed it
Phone freezes and reboots right after wake up in CM11 20150626 Snapshot
Hi everyone,
I just updated the phone from CM11 nightly of a version maybe two months old to the latest CM11 20150626 Snapshot, and I get this problem.
Right after the phone reboots, the locking, unlocking works fine. After a while (seems every app finishes its starting up), when I lock the phone and wake it up, the phone freezes right away and reboots a while later.
Can anyone let me know how to identify or solve this problem? Thanks.
Edit:
Ok, I just did a factory reset and now it seems to be running ok.
Edit:
I finally found out it's because I forgot to flash kernel for the PGM app.. how stupid I am.
Thank for great ROM.
@Ziyan and any people who help to create the great ROM for our device, Last year we hope to use KITKAT and now we fulfill this great ROM. Thank you every one.
Guys,
Please let me know if anyone has any information about latest CM 12.1 nightly for e980. The last build was taken on 0601 and nothing after that.
-Mesh
mshimpi said:
Guys,
Please let me know if anyone has any information about latest CM 12.1 nightly for e980. The last build was taken on 0601 and nothing after that.
-Mesh
Click to expand...
Click to collapse
My only guess is the maintainer is on vacation or had an emergency of some sort.
The latest build is pretty decent IMO. We will just have to wait and see when an update comes. It will come most likely. They could be trying to iron out major bugs they overlooked or something. We just have to wait and see what happens.
rjmxtech said:
The latest build is pretty decent IMO. We will just have to wait and see when an update comes. It will come most likely. They could be trying to iron out major bugs they overlooked or something. We just have to wait and see what happens.
Click to expand...
Click to collapse
Actually, I always try to build it locally and it's is broken. It says 'touchpanel_sysfs is undefined'.
I realize that it's in these 3 files, which gets generated during compilation (I guess)
cm12.1/out/target/product/e980/obj/ETC/sepolicy_intermediates/policy.conf
cm12.1/out/target/product/e980/obj/ETC/sepolicy_intermediates/policy.conf.dontaudit
cm12.1/out/target/product/e980/obj/ETC/sepolicy.recovery_intermediates/policy_recovery.conf
After defining the variable, the compilation went smooth and I got the build. BUT my phone would not boot with it. I had to roll back to the previous working build.
So, I'm guessing it's nothing to do with any major change or update.
Anyways, if anyone could build the latest code and get it working on their phone, I'm very much interested in knowing how
Hey, I flashed SuperZen r21 on my zengone 2 but I see last update was like a month ago. Anyone have any idea if its continuing or should I maybe find a different rom..
(Please move to Q&A, made a mistake)
he is only updating the rom when ASUS releases a new version!
Binigold9 said:
Hey, I flashed SuperZen r21 on my zengone 2 but I see last update was like a month ago. Anyone have any idea if its continuing or should I maybe find a different rom..
(Please move to Q&A, made a mistake)
Click to expand...
Click to collapse
If you like to play with daily/weekly rom flashing, go with CM 12.1 (and daily opengapps too). You won't get bored !
There's no point in updating SuperZen if there's no update for the stock rom from Asus, unless there's a bug.
We try to stick with the actual releases.
If you want something specific updated, or if something is broken, feel free to drop comment in the thread.
Otherwise, you won't be seeing random updates on it.
Maybe we could update the Asus apps and such as newer versions come out, but there won't be much.
Edit: There are still some things that I would like to update/fix, but I've been swamped with life lately and haven't been able to get to them. When I get some free time, we will likely put out a few updates/fixes to take care of some nagging issues.
Harfainx said:
We try to stick with the actual releases.
If you want something specific updated, or if something is broken, feel free to drop comment in the thread.
Otherwise, you won't be seeing random updates on it.
Maybe we could update the Asus apps and such as newer versions come out, but there won't be much.
Edit: There are still some things that I would like to update/fix, but I've been swamped with life lately and haven't been able to get to them. When I get some free time, we will likely put out a few updates/fixes to take care of some nagging issues.
Click to expand...
Click to collapse
Thanks very much! I really appreciate your work. Thus is my favorite rom so thats why I asked. Was just curious.
Hope everything goes well with life
This is my fav rom too. Can't wait till Asus releases a MM update. I always like to be running the newest OS
I've searching for karthick111's cm11 folder, then i saw a folder called "cm14.1" with a zip called "cm14.1-20161220UNNOFICIAL-nevisp" and i downloaded and flashed it but it bootloops :'v
Does anybody know if it's usable or a wip?
Pd. There a bootable cm13 rom that i'm using to write this :v
I'm sorry if i had a bad engish, i'm a mexican :v
armando121504 said:
I've searching for karthick111's cm11 folder, then i saw a folder called "cm14.1" with a zip called "cm14.1-20161220UNNOFICIAL-nevisp" and i downloaded and flashed it but it bootloops :'v
Does anybody know if it's usable or a wip?
Click to expand...
Click to collapse
Yeah... I have just flashed it, but it has been in a bootloop for 20+ minutes already. Needless to say, this is probably a test/WIP CM14.1 build that @karthick mostwanted is testing for the Galaxy Fame to see if it will work at all. From what I am aware of, later CM ROMs (CM13, 14, and 14.1) will not work as well as they should on this device as it is low-end and doesn't have the RAM or processing power that is required, however, CM13 is fairly usable from what I have tried, but I still find the CM11 (KitKat 4.4.4) ROMs to be the best. Then again, it is always good to keep and eye on and test the latest builds that the developers release, as I have seen some older devices get ROMs which shouldn't work on them because of their hardware, but do, because the developer is able to configure it to make it work.
I'm disappointed
I don't know why everyone being stalkers
The work is not even done yet and u guys are posting it here without my permissions
Yes in next build I will try to brick the device badly if this persists again
If the work is done I will share it for sure
Don't irritate developers by doing this way
karthick mostwanted said:
I'm disappointed
I don't know why everyone being stalkers
The work is not even done yet and u guys are posting it here without my permissions
Yes in next build I will try to brick the device badly if this persists again
If the work is done I will share it for sure
Don't irritate developers by doing this way
Click to expand...
Click to collapse
Fair enough, but I assumed that since it was publicly available to view and download, then it should be okay to publicly discuss about the development surrounding the ROM/s, but I guess not.
Thank you for the time and effort you put into these builds and the continuation of custom ROM development for this device.