CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Download Links
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=m8&type=nightly
Google apps addon:
Download: http://wiki.cyanogenmod.org/w/Google_Apps
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] CyanogenMod 12.1 Nightlies for the HTC One m8, ROM for the HTC One (M8)
Contributors
invisiblek
Source Code: http://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
Version Information
Status: Nightly
Created 2015-04-20
Last Updated 2015-04-19
CM 12.1 Nightly 4/19 is solid so far
Agreed. Easily, daily driver stuff. I really haven't found a hiccup yet.
bluetooth disconnect is still present in 04/19.
Small issue--just tried to unlink my Notification volume from the Ringtone volume--the slider moves---no change. Can someone else check that & see if the same happens...if so it looks like a minor bug.
Just flashed cm12.1 4/20 from CM12.0 4/15. Flash went fine, booted-up and got to the "optimizing apps" screen. I walked away for a few minutes, and now, the screen is completely black and unresponsive. :crying:
on 19/4 build anf can not update to 20/4 using OTA :crying:
I'm stilling getting an issue where I lose LTE/data connection and it requires a reboot to resolve. Is anyone else seeing this? I'm still able to text and receive voice calls, but nothing but a reboot will reconnect data. Even toggling airplane mode has no effect. Just see the signal strength bars with an "!" character indicating data is disconnected. I had the same issue with CM 12.
does the voice messages of Whatsapp are working?
JustMyUserName said:
I'm stilling getting an issue where I lose LTE/data connection and it requires a reboot to resolve. Is anyone else seeing this? I'm still able to text and receive voice calls, but nothing but a reboot will reconnect data. Even toggling airplane mode has no effect. Just see the signal strength bars with an "!" character indicating data is disconnected. I had the same issue with CM 12.
Click to expand...
Click to collapse
I had the same problem w/ 4/19. had to revert to cm12. I'm assuming its because of the firmware. I'll have to update mine and retry. I dunno if that would help you.
Update: upgraded firmware and now im good on 4/20.
Edit 2: getting fc on gapps, used both official and minimal, what's everyone using?
Everything seems to be running pretty smoothly. The on problem that I do have is that the system seems to be having a hard time automatically connecting to wifi. It's fine as long as I stay in range of the wifi, but when I leave and then come back, it takes a while to connect. Sometimes I even have to disable and reenable wifi before I can get it to connect.
Running 0420 build on AT&T full wipe:
I'm having an issue with connecting bluetooth with my car. Seems that it connects but once it tries to enable reading the text messages it crashes. I turned off reading text messages for now and it works. Any ideas?
Does bluetooth still disconnect on screen lock?
paul4762 said:
Running 0420 build on AT&T full wipe:
I'm having an issue with connecting bluetooth with my car. Seems that it connects but once it tries to enable reading the text messages it crashes. I turned off reading text messages for now and it works. Any ideas?
Click to expand...
Click to collapse
If you're S-OFF flash the dev edition 4.4.4 firmware and reinstall. i had the same problem with my sony headunit. havent had a problem since downgrading.
On-body detection didn't work for me on 04/19 build. I set my phone down for a few mins and it didnt lock like it was supposed to.
shadowster said:
Everything seems to be running pretty smoothly. The on problem that I do have is that the system seems to be having a hard time automatically connecting to wifi. It's fine as long as I stay in range of the wifi, but when I leave and then come back, it takes a while to connect. Sometimes I even have to disable and reenable wifi before I can get it to connect.
Click to expand...
Click to collapse
I can second that. For me connection to WiFi sometimes must be forced manually.
Not encountered any bugs yet but have to say this is easily the smoothest experience I've had in ages on a a ROM (20/4)
I'm pretty darn picky when it comes to fluidity of a ROM and this is right up there with Sense/GPE.
Nezorflame said:
I can second that. For me connection to WiFi sometimes must be forced manually.
Click to expand...
Click to collapse
Wifi is, I think, the biggest regression from AOSP (with battery life)
I dont know how to report such a bug efficiently, but I hope this can be fixed!
bluetooth is also an issue. actually it's bt/wifi issue - tthey are linked to each other.
Is ota update work thanks
Related
[SIZE=+2]Questions and Troubleshooting specific to
CyanogenMod 10.1 and 10.2[/SIZE]
This is the place to share issues, ask questions and offer help.
Be sure to specify the exact filename of the build about which you are asking questions.
For fixes to common problems, see Post 3 of either development thread listed below.
Remember to use the thanks button in lieu of simply posting "Thank you".
Keep discussion focussed on CyanogenMod and not derivative ROMs or modifications.
Development threads:
[ROM][AOSP 4.2.2] CyanogenMod 10.1 Official
[ROM][AOSP 4.3] CyanogenMod 10.2 Official
Read here for the rationale behind creating a separate Q&A thread for ROMs: Q&A Threads for ROMS / Kernels / Projects
FAQ
Q: Why create a special Questions and Troubleshooting thread for a specific ROM?
A: Much of the discussion in ROM development threads is not related to development, but rather problems with flashing, installation, bugs, or other things not working. While this is understandable, it is not in accordance with XDA guidelines for development sections. A dedicated Questions and Troubleshooting thread helps avoid clutter in the development thread and gives the community more opportunities to work together to resolve issues, rather than assuming the developer is responsible for all questions.
Q: How do I move my post to the Questions and Troubleshooting thread?
A: Copy the text of your post in the development thread and paste it here. Then, edit your post in the development thread to read: post moved to Q&T thread, preferably accompanied by a link to your new post.
Q: Where are the download links for this ROM?
Q: What are the known issues with this ROM?
AA: See post 1 of either development thread: [ROM][AOSP 4.2.2] CyanogenMod 10.1 Official or [ROM][AOSP 4.3] CyanogenMod 10.2 Official. There, you will also find the installation instructions and solutions to common problems.
I've had this issue since moving to CM 10.2, originally on the unofficial nightly 20130901, just flashed the unofficial 20131014 yesterday. My phone will not make sounds after previously set to vibrate, after turning up the volume with the volume key from the home screen the indicator shows volume, but will not make a sound to verify the sound level, and my alarm is silent too. Rebooting seems to fix the sound until I silence it again, but I have to yank the battery as it freezes on a reboot initiated from the power key. I have updated my recovery to TWRP 2.6.3.
I very much appreciate the screen flickering fix on the 10/14 nightly, it is completely gone today.
biodiesel.ufo said:
I've had this issue since moving to CM 10.2, originally on the unofficial nightly 20130901, just flashed the unofficial 20131014 yesterday. My phone will not make sounds after previously set to vibrate, after turning up the volume with the volume key from the home screen the indicator shows volume, but will not make a sound to verify the sound level, and my alarm is silent too. Rebooting seems to fix the sound until I silence it again, but I have to yank the battery as it freezes on a reboot initiated from the power key. I have updated my recovery to TWRP 2.6.3.
I very much appreciate the screen flickering fix on the 10/14 nightly, it is completely gone today.
Click to expand...
Click to collapse
There's a new official nightly you can flash now. 20131016. As for the sound thing, if you go into Settings--->Sound you can check off "Volume Adjustment Sound" and it should make a tone showing what the volume level is. I'm not sure if it's related or the same thing you're experiencing, but in the past I've had issues flashing between builds (not nightlies, but flashing from like 4.2.2 to 4.3) where the default ringtone, notifcation tone and/or alarm tone would get some issue and it would say "Unknown" if you went to check what they were set to. Setting them to a new tone fixed the issue. This usually occured when I would flash a very different build version, or when I would restore a TWRP backup. But once I set a new tone it would be fine from that point on.
I am running 10.2-20131016-NIGHTLY-fireball. Our office has two wireless routers that share the same SSID, but different channels to eliminate interference. Not unique to this build, it seems that my handset's wifi is either slow to, or just doesn't, hand off to the best router when I move about. It seems like in the past i could walk from one end of the office to the other, watch my wifi signal go down, then suddenly jump up as I near the closer router. Is this a CM issue, or is this an android issue, or is there no mechanism to adjust automatically? Thanks for any help.
spectre559 said:
I am running 10.2-20131016-NIGHTLY-fireball. Our office has two wireless routers that share the same SSID, but different channels to eliminate interference. Not unique to this build, it seems that my handset's wifi is either slow to, or just doesn't, hand off to the best router when I move about. It seems like in the past i could walk from one end of the office to the other, watch my wifi signal go down, then suddenly jump up as I near the closer router. Is this a CM issue, or is this an android issue, or is there no mechanism to adjust automatically? Thanks for any help.
Click to expand...
Click to collapse
I'm not qualified to answer on this issue but I'll point out that I've noticed this behavior since I've been on cm. I work in a large building with multiple access points and it doesn't hand off between routers well at all.
Sent from my Incredible 4G LTE using Tapatalk now Free
Maybe if you check off "Avoid poor connections" in the WiFi advanced settings it will hand off easier when the current signal gets weak. Also note that you can select the priority levels for the WiFi networks in those advanced settings. Maybe you're closer to one of them but the priority of the other one is set higher so its constantly trying to connect to that one first?
somerandomname1 said:
Maybe if you check off "Avoid poor connections" in the WiFi advanced settings it will hand off easier when the current signal gets weak. Also note that you can select the priority levels for the WiFi networks in those advanced settings. Maybe you're closer to one of them but the priority of the other one is set higher so its constantly trying to connect to that one first?
Click to expand...
Click to collapse
Not sure if this will help as the routers have the SSID, so there is only one wireless network entry in the wifi list.
spectre559 said:
Not sure if this will help as the routers have the SSID, so there is only one wireless network entry in the wifi list.
Click to expand...
Click to collapse
Ahh, I've never seen where two routers have the same ssid. I just assumed that since they were technically two different connections it would list the same name twice. Well maybe the "avoid poor connections" will help? I've never had that checked either so I don't know how well it works, but it makes sense that it would drop a low signal more easily for a higher one.
somerandomname1 said:
Ahh, I've never seen where two routers have the same ssid. I just assumed that since they were technically two different connections it would list the same name twice. Well maybe the "avoid poor connections" will help? I've never had that checked either so I don't know how well it works, but it makes sense that it would drop a low signal more easily for a higher one.
Click to expand...
Click to collapse
You'd think that would work better but it doesn't. It keeps that signal until it's low enough to drop it then actually drops it and you're without a signal for a second or few before it connects to the stronger signal. This is the behavior I notice with mine regardless if avoid poor connections is checked or not
Sent from my Incredible 4G LTE using Tapatalk now Free
somerandomname1 said:
Ahh, I've never seen where two routers have the same ssid. I just assumed that since they were technically two different connections it would list the same name twice. Well maybe the "avoid poor connections" will help? I've never had that checked either so I don't know how well it works, but it makes sense that it would drop a low signal more easily for a higher one.
Click to expand...
Click to collapse
Just checked...apparently I already "avoid poor connections" checked. I'm wondering if there is any built-in software function that actually checks for better signals on different channels when connected to the same SSID.
I flashed the unofficial 10/15 build with no problems at all for about 5 hours. Went to sleep and now I can't send txt or make phone calls. My phone shows that I have full service so I'm thinking its a borked radio. Well my comp with adb crapped out on me this morning, so I have a laptop with windows 7 and no ADB. Flashed back to a different ROM and no luck. Still no txts can be sent out or phone calls but I can receive them. Can someone point me in the right direction to install adb on windows 7? I used google but a lot of the articles were out of date. Thanks in advance!
TheGOAT232412 said:
I flashed the unofficial 10/15 build with no problems at all for about 5 hours. Went to sleep and now I can't send txt or make phone calls. My phone shows that I have full service so I'm thinking its a borked radio. Well my comp with adb crapped out on me this morning, so I have a laptop with windows 7 and no ADB. Flashed back to a different ROM and no luck. Still no txts can be sent out or phone calls but I can receive them. Can someone point me in the right direction to install adb on windows 7? I used google but a lot of the articles were out of date. Thanks in advance!
Click to expand...
Click to collapse
Did you do a full wipe and clean install? Or are you flashin' dirty?...
TheGOAT232412 said:
I flashed the unofficial 10/15 build with no problems at all for about 5 hours. Went to sleep and now I can't send txt or make phone calls. My phone shows that I have full service so I'm thinking its a borked radio. Well my comp with adb crapped out on me this morning, so I have a laptop with windows 7 and no ADB. Flashed back to a different ROM and no luck. Still no txts can be sent out or phone calls but I can receive them. Can someone point me in the right direction to install adb on windows 7? I used google but a lot of the articles were out of date. Thanks in advance!
Click to expand...
Click to collapse
Check that you have RUIM/SIM selected under Settings > (Wireless & Networks) More... > Mobile networks > CDMA subscription. Barring that, restore a known working backup and check the phone. If it does not work, follow the borked radio instructions - after which if you install CM again, set that RUIM/SIM connection type on first boot and restart.
mdmower said:
Check that you have RUIM/SIM selected under Settings > (Wireless & Networks) More... > Mobile networks > CDMA subscription. Barring that, restore a known working backup and check the phone. If it does not work, follow the borked radio instructions - after which if you install CM again, set that RUIM/SIM connection type on first boot and restart.
Click to expand...
Click to collapse
I am currently on a restored ROM that I was using prior to the CM ROM. I am currently still having the same issue, I can't send out calls and texts but I can receive text. In my previous post, I stated the PC that I had ADB installed on crapped out on me this morning. I have a laptop running Windows 7 without ADB installed. My PC is running Windows XP, as of to where my laptop is running Windows 7. So I was just looking for a guide to help me install ADB on Windows 7 and just go from there. Appreciate the quick responses, it's the only phone I have and as of right now its useless.
Speakerphone patch
@scottyb96: with reference to this post, try this sound file update (install through recovery) and see if it helps your garbled speakerphone mic. Several device definitions were missing the dual-mic feature of this phone.
Also, let me know of any regressions. I updated quite a bit more than just mic.
TheGOAT232412 said:
I am currently on a restored ROM that I was using prior to the CM ROM. I am currently still having the same issue, can't send out calls and txt but I can receive txt and no phone calls. In my previous post, I stated that I the PC that I had ADB installed on crapped out on me this morning. I have a laptop running Windows 7 without ADB installed. My PC is running Windows XP, as of to where my laptop is running Windows 7. So I was just looking for a guide to help me install ADB on Windows 7 and just go from there. Appreciate the quick responses, it's the only phone I have and of right now its just worthless
Click to expand...
Click to collapse
Drivers, ADB/Fastboot, Post 2
Is there any way to subvert the text message limit where it splits? Using third-party sms apps it's possible. Just wondering if there's any hidden way or something I can edit to disable the splitting in the stock sms app.
mdmower said:
@scottyb96: with reference to this post, try this sound file update (install through recovery) and see if it helps your garbled speakerphone mic. Several device definitions were missing the dual-mic feature of this phone.
Also, let me know of any regressions. I updated quite a bit more than just mic.
Click to expand...
Click to collapse
First test sounds good. I will report back after a few days of operation. Thanks for the update.
scottyb96 said:
First test sounds good. I will report back after a few days of operation. Thanks for the update.
Click to expand...
Click to collapse
I'd like to merge this by Thursday evening at the latest. If others can apply the sound file fix and make sure I didn't introduce any regressions I'd appreciate it. I'd also like to ensure garbled mic when on speakerphone is indeed fixed.
Hi
I prepared short review for SlimKat 3.4 unofficial build for XT910 UMTS.
I use it for a last few days and my general impression is positive.
But lets start from beginning...
1. Instalation
I use SafeStrap, so installation process is very easy: create slot, install software and gapps, clean cache and Dalvik cache. That's all.
After booting of phone there is sort setup and phone is ready to work. ALMOST...
After next restart phone stops connecting to network and to fix that problem it is necessary manually delete CellBroadcastReceiver.apk what is very easy because SlimKat is delivered with SlimCenter containing SlimSizer when user can delete any app.
So, delete it, reboot and forget about network connection problems. Why this app is delivered with most of KitKat ROMs for XT910 UMTS I do no understand. All of them have the same problem after rebooting.
2. Daily usage
I use it as my daily driver last days and it worked really good. I noticed just one crash when I used Any.do app but I cannot reproduce it so far.
Battery life is good for me - see BatteryLife.jpg attached. On the other hand I was totally surprised when I charged battery to 102% - see Battery102.jpg - really strange.
I turned system to use ART instead of Dalvik and I haven't noticed any problem so far. Every app I used worked properly. Of course app installation time is a bit longer now, but good information is that apps starts faster.
Call/receive calls - not problem. Sound is clean.
WiFi - I haven't noticed any problem with connection/disconnecting WiFi networks. Everything worked good.
GPS gets position really fat, I was very surprised with that.
SMS sending works properly but I still cannot send any MMS message. Nevermind data transmission is enabled. I does not work. To receive MMS data transmission must be enabled. This is the biggest bug I noticed.
Flip actions to dismiss call or alarm also don't work what confuses me. It worked perfectly in CARBON 4.2.2 version I used for long time.
It looks very strange in action: flip down - no action performed, flip up - phone seems to be blocked for some time and after a few seconds you can finally dismiss alarm or call.
Memory usage is much better than in 4.2.2 ROMs. After boot there is used 434MB and free 405MB of RAM with all of my services and widgets started. Great result.
Bleutooth I didn't test. I use it very seldom and it is not much important to me.
What was new for me - used apps display. It is changed in SlimKat - nice right side panel is displayed with list of used application.
Generally I must say that I like SlimKat. It has all options I really need to use it every day. I'm happy with Real dark option which turns system and most important apps into black theme, performance good enough without replacing kernel, ART support without problems and smoothness of GUI.
I hope that strange battery behavior and MMS sending problems will be fixed in next releases
And maybe XT910 will be officially supported by SlimKat team?
98236896 45
rys1908 said:
Hi
I prepared short review for SlimKat 3.4 unofficial build for XT910 UMTS.
I use it for a last few days and my general impression is positive.
But lets start from beginning...
1. Instalation
I use SafeStrap, so installation process is very easy: create slot, install software and gapps, clean cache and Dalvik cache. That's all.
After booting of phone there is sort setup and phone is ready to work. ALMOST...
After next restart phone stops connecting to network and to fix that problem it is necessary manually delete CellBroadcastReceiver.apk what is very easy because SlimKat is delivered with SlimCenter containing SlimSizer when user can delete any app.
So, delete it, reboot and forget about network connection problems. Why this app is delivered with most of KitKat ROMs for XT910 UMTS I do no understand. All of them have the same problem after rebooting.
2. Daily usage
I use it as my daily driver last days and it worked really good. I noticed just one crash when I used Any.do app but I cannot reproduce it so far.
Battery life is good for me - see BatteryLife.jpg attached. On the other hand I was totally surprised when I charged battery to 102% - see Battery102.jpg - really strange.
I turned system to use ART instead of Dalvik and I haven't noticed any problem so far. Every app I used worked properly. Of course app installation time is a bit longer now, but good information is that apps starts faster.
Call/receive calls - not problem. Sound is clean.
WiFi - I haven't noticed any problem with connection/disconnecting WiFi networks. Everything worked good.
GPS gets position really fat, I was very surprised with that.
SMS sending works properly but I still cannot send any MMS message. Nevermind data transmission is enabled. I does not work. To receive MMS data transmission must be enabled. This is the biggest bug I noticed.
Flip actions to dismiss call or alarm also don't work what confuses me. It worked perfectly in CARBON 4.2.2 version I used for long time.
It looks very strange in action: flip down - no action performed, flip up - phone seems to be blocked for some time and after a few seconds you can finally dismiss alarm or call.
Memory usage is much better than in 4.2.2 ROMs. After boot there is used 434MB and free 405MB of RAM with all of my services and widgets started. Great result.
Bleutooth I didn't test. I use it very seldom and it is not much important to me.
What was new for me - used apps display. It is changed in SlimKat - nice right side panel is displayed with list of used application.
Generally I must say that I like SlimKat. It has all options I really need to use it every day. I'm happy with Real dark option which turns system and most important apps into black theme, performance good enough without replacing kernel, ART support without problems and smoothness of GUI.
I hope that strange battery behavior and MMS sending problems will be fixed in next releases
And maybe XT910 will be officially supported by SlimKat team?
Click to expand...
Click to collapse
Small update:
MMS issue: installing 8sms application solves problem. Probably Messaging app does not resize image and whole MMS message is declined by network as too big.
SlimKat umts_spyder build 3.6 2014-03-09
I performed dirty flash of SlimKat 3.6 over SlimKat 3.4 - no problems.
Everything works as it worked before. I haven't noticed any new problems.
I'm still not happy with bad flip actions support but that this problem exists in every of tested KK ROMs - looks it is general malfunction.
Waiting for new version...
bluetooth
Hi I would be curious to know if the bluetooth works, in particular in the car. also if the bluetooth has any problems pairing and keeping the pair when you change from flight mode to normal, if you have to pair again or not . thanks for the review
Hi
I have tested bluetooth with other phone and headset and haven't noticed any problems. You do not have to pair devices again after going off flight mode.
SlimKat 3.8 upgrade
Hi
I performed dirty flash to SlimKat 3.8 without problems. CellBroadcastReceiver.apk is still delivered so you have to delete it manually to get rid of cell connection problems
After that device works good. Still great memory management
I noticed that problems with flip actions seems to be almost resolved and now I can dismiss call and alarm flipping down my phone.
For calls it works immediately but for alarms I need to perform flip down - flip up - flip down and after some delay alarm is dismissed.
What I'd like to see in SlimKat are Performance options in settings. Of course I can install some app to manipulate processor settings and governors but I think this should be part of system delivery.
And, of course, XT910 is still not supported officially, so forget OTA.
How about slim 4,any surprised？
I used SlimKat for a while and I found it REALLY FAST AND SMOOTH! I reccommend it!
Now I'm installing the 4.0 build and we'll see how it works
the only problem I experienced: when discharging completely to "0%"...my phone resets itself, quite strange/frustrating...
I'm still on 3.8. Yesterday I dischrged battery to 0% and phone shot down correctly , not restarted automatically.
Abou 4.0 - I'm a bit confused. SlimRoms.net does not mention that so far but in changelog we can find 3.10 version: http://slimroms.net/index.php/changelog.
I'll wait a bit
hello
I installed 4.4.2 build 4 and I got the network problem and after i deleted the cellbroadcast.. it worked!! but now i have a problem with the hotspot ;( my brother tried to connect but he couldn't ;( do you know what to do to solve this little problem?
I havent tried wifi tethering before (no need) but it looks problem exists. I also cannot connect to established hotspot (I still on 3.8). I remember that there was tethering problem on beginning of work on kitkat custom roms for Razr device but it was fixed long time ago.
rys1908 said:
I havent tried wifi tethering before (no need) but it looks problem exists. I also cannot connect to established hotspot (I still on 3.8). I remember that there was tethering problem on beginning of work on kitkat custom roms for Razr device but it was fixed long time ago.
Click to expand...
Click to collapse
Hello, 1st post here I LOVE Slimkat for our Razr, I've been running the latest updates in slot 1 for months and for the last few days I've run the latest build in the stock slot and love it even more.
But I have to agree that AP / hotspot / wifi tether is not working anymore. It was working fine for a while there -- here are notes in the update log:
29DEC2013 - CM's netd code "hopefully fixes wifi tether" [I think it started working around here for the 1st time]
09FEB2014 - "mobile hotspot fixed" [might have broke again along the line ? ]
In the last 2 builds (20MAR2014 first then tried 27MAR2014 both as dirty flash and then fresh in slot 1), I can create a hotspot but nothing can join. Too bad because I really make use of it, hope it gets fixed again soon
And thx to original poster for posting a quality review of what is one of the best ROMs for our classic spyder.
After a week on SlimKat 4.0 i have to say that it is really solid and stable. Wifi tethering is known problem (reported to dev forum). I also noticed that my favourite governor "hotplug" is no longer supported and battery usage over night is now 4% instead of 2% I used to. I'm not sure hotplugging is supported by interactive or ondemand governors. I think I'll try to use JBX kernel with SlimKat and see how good it is. If you have any experiences, plz share with me.
Whew this guy figured out that the CM11 WiFi AP fix still also works for us:
http://forum.xda-developers.com/showpost.php?p=51713472&postcount=1592
just installed and it's working.
Finally I tested SlimKat with JBX kernel (only battery saver enabled) and I havent noticed any better bsttery life. There was even worse than without it: 5-6% over night consumption when phone did nothing. I also played with governors enabled in JBX what almost every time caused system hanging.
So, finally I resign of JBX and made decision to give another chsnce to Carbon Rom that was my daily driver for months (release 4.2.2).
I must say I'm surprised how good is Carbon now - I remember first 4.4 releases. Everything seems to work properly including tethering. What is quite important for UMTS razor users we can disable CellBroadcastReceiver in settings - no need to delete it and restart phone.
There is one feature I love especially: lockscreen notifications. This is killer feature for me.
What is also important for me, Hotplug governor is enabled in kernel and again I have overnight usage 2-3%.
I must say I'm currently very satisfied with Carbon Rom. Looks it became my daily driver again.
rys1908 said:
Hi
I prepared short review for SlimKat 3.4 unofficial build for XT910 UMTS.
I use it for a last few days and my general impression is positive.
But lets start from beginning...
1. Instalation
I use SafeStrap, so installation process is very easy: create slot, install software and gapps, clean cache and Dalvik cache. That's all.
After booting of phone there is sort setup and phone is ready to work. ALMOST...
After next restart phone stops connecting to network and to fix that problem it is necessary manually delete CellBroadcastReceiver.apk what is very easy because SlimKat is delivered with SlimCenter containing SlimSizer when user can delete any app.
So, delete it, reboot and forget about network connection problems. Why this app is delivered with most of KitKat ROMs for XT910 UMTS I do no understand. All of them have the same problem after rebooting.
2. Daily usage
I use it as my daily driver last days and it worked really good. I noticed just one crash when I used Any.do app but I cannot reproduce it so far.
Battery life is good for me - see BatteryLife.jpg attached. On the other hand I was totally surprised when I charged battery to 102% - see Battery102.jpg - really strange.
I turned system to use ART instead of Dalvik and I haven't noticed any problem so far. Every app I used worked properly. Of course app installation time is a bit longer now, but good information is that apps starts faster.
Call/receive calls - not problem. Sound is clean.
WiFi - I haven't noticed any problem with connection/disconnecting WiFi networks. Everything worked good.
GPS gets position really fat, I was very surprised with that.
SMS sending works properly but I still cannot send any MMS message. Nevermind data transmission is enabled. I does not work. To receive MMS data transmission must be enabled. This is the biggest bug I noticed.
Flip actions to dismiss call or alarm also don't work what confuses me. It worked perfectly in CARBON 4.2.2 version I used for long time.
It looks very strange in action: flip down - no action performed, flip up - phone seems to be blocked for some time and after a few seconds you can finally dismiss alarm or call.
Memory usage is much better than in 4.2.2 ROMs. After boot there is used 434MB and free 405MB of RAM with all of my services and widgets started. Great result.
Bleutooth I didn't test. I use it very seldom and it is not much important to me.
What was new for me - used apps display. It is changed in SlimKat - nice right side panel is displayed with list of used application.
Generally I must say that I like SlimKat. It has all options I really need to use it every day. I'm happy with Real dark option which turns system and most important apps into black theme, performance good enough without replacing kernel, ART support without problems and smoothness of GUI.
I hope that strange battery behavior and MMS sending problems will be fixed in next releases
And maybe XT910 will be officially supported by SlimKat team?
Click to expand...
Click to collapse
Hi!
I installed Slimkat version 7.0 stable and my cell phone (S3 I9300) lost network connection randomly. Duration of connection is 1 - 2 seconds max. If I delete CellBroadcastReceiver.apk as you say, network connection will be stable, without disconnect randomly?
Thanks!
Hi. I built CyanogenMod 12 for LG P760/P765. It has some critical bugs like GPS problems.
What's not working/has bugs:
GPS isn't working
Wifi MAC adress is random (RIL issue)
WiFi Direct
Camera completly broken
Graphics glitch when locking screen
Kernel and rom features:
Ramhack 818Mb
Better battery life
OC to 1350 Mhz
GPU OC to 384 Mhz
Many tweaks
Sound boost on headphones
Updated screen driver
Power saving mode (in battery settings)
Internal sd disabled
Added BLN support (L9 BacklightMod app in Play Store)
Support for 5Ghz wifi
Bluetooth Low Energy support
Less battery drain by screen (lower screen refresh rate)
Better multicore managing
What you need:
LG P760/P765
Unlocked bootloader
Flashing:
Flash my recovery
Boot to TWRP
Make sure you have enabled EXT4 (if you haven't flashed CM11 before you can skip this step)
Flash ROM
Flash fix (if any)
Flash Gapps (if you want)
Reboot system now!
Download: http://artas182x.you2.pl/android-projects/cyanogenmod-12-lg-optimus-l9-ext4/
XDA:DevDB Information
CyanogenMod 12 for LG Optimus L9, ROM for the LG Optimus L9 P760, P765, P768
Contributors
artas182x
Source Code: http://github.com/artas182x
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2014-11-27
Last Updated 2014-11-26
Thanks for your work.
Is echo on call fixed or it's there like on aosp 5.0?
Doesn't camera work also for third party apps?
thanks for your work!
the truth that promises much change made.
Patch works for P768 PuntoAzul created by this device.
Thanks You Artas182x!!!
Bugs i found :
* Cannot connect to computer "USB computer connection" is not working..
* Battery usage data isn't available in battery settings
I can't say anything...
what about you @JulianJenner
Funny...
Redmi Note 1W Enhanched / MIUI 37.0.0 Stable Multilanguage / Tapatalk Pro 4.6.2
artas182x said:
Hi. I built CyanogenMod 11 for LG P760/P765. It has some critical bugs like GPS problems. [...]
Click to expand...
Click to collapse
I think u mean 12.
Thanks for ur work
Thank you for this!
Are you abandoning AOSP rom and only focusing on this now? Why did you prefer CM12 rather than AOSP?
Nice, can't wait for the major bugs to be fixed so I can try it out!
gps on cm12
Gps working for me (very very fast locking)
This rom is smoother than aosp 5.0.
Camera doesn't work with any app, also teslaled doesn't work.
Graphical glitches are also when rotate screen, not only when turn it off.
Gps works good after download lto with gps fixer. I think a little better than in cm11. I tried it on aosp and it doesn't work even with gps fixer.
I miss aosp task manager in notifications.
I didn't try calls yet to know if there is echo.
On aosp I have poor phone signal (half full) but on this rom it's full.
Is it just me or it is not possibile to get root privileges?
MirkoCe said:
Is it just me or it is not possibile to get robot privileges?
Click to expand...
Click to collapse
¿robot or root?
I'm rooted flashing supersu 2.30 beta (now updated to 2.35)
Ooops, i meant root of course! I thought there was no need for SuperSu (like in CM11).
My bad!
I can confirm, gps works well after downloading lto data im gps fixer. Unfortunately mobile data dont work for me. Artas good work!
So I tried the rom and it seems fairly smooth.
A part from the bugs already written in the first post
- mobile internet does not work, only wifi
-Privacy guard force closes if I try to open apps settings
-when I close a call dialer force closes
-if I try to delete call history in dialer it force closes too
-alarm doesn't work, clock application crashes
Haven't tried GPS but camera doesn't work anywhere, as state before. AOSP ROM seems more stable to me.
Great new CM version and artas fixing gonna give us soon a stable 5.0.
We have to thank to artas for his gift to us.
MirkoCe said:
So I tried the rom and it seems fairly smooth.
A part from the bugs already written in the first post
- mobile internet does not work, only wifi => for me both works
-Privacy guard force closes if I try to open apps settings
-when I close a call dialer force closes => it doesn't happen to me
-if I try to delete call history in dialer it force closes too => I can confirm this
-alarm doesn't work, clock application crashes => for me it works
Haven't tried GPS but camera doesn't work anywhere, as state before. AOSP ROM seems more stable to me.
Click to expand...
Click to collapse
More bugs I experienced:
Bluetooth fc's when trying to send a file.
Echo in calls seem fixed but sometimes caller can't hear me and I have to hang up and call again.
Uhm i guess I should have reinstalled. Maybe some configurations of mine were the problem. I'm gonna wait for a camera fix mainly, at least if I can use third party app.
Inviato dal mio Optimus L9 utilizzando Tapatalk
- Mobile internet does not work, only wifi
- ALARM - OK
- GPS - OK
- Something breaks the sound. How bad it will wake the phone or audio can not be that someone is calling, sms or even to activate the alarm.
- Off the phone and connected to the charger - lit display
- Camera doesn't work with any app.
- Echo in calls seem fixed but sometimes caller can't hear me and I have to hang up and call again.
- Stock ... Most visible when rotating an image.
- Lack of access to the phone when connected to a computer.
Q&A for vs985 [Official] Resurrection Remix 5.0.1 Lollipop v5.2.0 Alpha [14/12/08]
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 vs985 [Official] Resurrection Remix 5.0.1 Lollipop v5.2.0 Alpha [14/12/08]. 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!
resurrection vs985 build
It's a wonderful build but i am have troubles with my moto 360 and android wear connecting whatsoever. Any tips on this?
Skandinavia said:
It's a wonderful build but i am have troubles with my moto 360 and android wear connecting whatsoever. Any tips on this?
Click to expand...
Click to collapse
I have the lg g watch and the only way I have found to connect it after switching ROMs is to reset the watch
FC on changing screen DPI
Having trouble after updating from v5.2.0 -> 5.2.1: I had my screen DPI set to 480 before, when it first booted up after the update, it was defaulted back to the stock DPI. Went in to Resurrection Tools -> Misc -> CD Density and tried to set it back to 480, and as soon as you click on any res in the menu it Force Closes.
When I upgraded, i ran a nandroid backup, flashed the new ROM, GApps (PA_gapps_modular-micro-5.0.1-beta1-20141209 141209), wipe cache, dalvik, boot to ROM.
EDIT: I just tried doing a factory reset to see if that would resolve it, but it still F/C's when trying to set the DPI.
Any ideas on this?
no GPS lock
It seems I do not get any GPS data at all. Tried a couple apps that read your GPS data, sat locations, lock, etc, and it never does get any GPS data. Tried toggling Location settings as well. So, this sounds to me that when I was driving around the other day and getting whacky location data, it was probably just getting wifi based location, which is no good.
Anyone else having trouble with GPS on their vs985? Is there another radio .zip i should flash (and would that matter?)
[/COLOR]
oadam11 said:
I have the lg g watch and the only way I have found to connect it after switching ROMs is to reset the watch
Click to expand...
Click to collapse
I can confirm this as well: I have a Moto360, and when you re-pair it after flashing a new ROM, you just need to go in to the menu on the watch and "reset". Since all the software comes from the phone its' paired to, this is what needs to happen.
oadam11 said:
I have the lg g watch and the only way I have found to connect it after switching ROMs is to reset the watch
Click to expand...
Click to collapse
I can confirm this is needed for Android Wear devices. I also have a Moto 360, and when you flash a new ROM, as far as your Wear device is concerned, it's a new phone. go in to the settings on your watch and Reset it, and you'll be able to pair it to your phone again.
---------- Post added at 03:40 PM ---------- Previous post was at 02:53 PM ----------
joeinbend said:
Having trouble after updating from v5.2.0 -> 5.2.1: I had my screen DPI set to 480 before, when it first booted up after the update, it was defaulted back to the stock DPI. Went in to Resurrection Tools -> Misc -> CD Density and tried to set it back to 480, and as soon as you click on any res in the menu it Force Closes.
When I upgraded, i ran a nandroid backup, flashed the new ROM, GApps (PA_gapps_modular-micro-5.0.1-beta1-20141209 141209), wipe cache, dalvik, boot to ROM.
EDIT: I just tried doing a factory reset to see if that would resolve it, but it still F/C's when trying to set the DPI.
Any ideas on this?
Click to expand...
Click to collapse
Okay I figured this out, it was SuperUser. Apparently it was not installed correctly, because i went in to SuperUser and tried to open it, and it gave the warning about it being installed in the OS but needs to be installed by your Recovery Manager. I let it install in TWRP and reboot, then I was able to set the DPI as I expected.
Note to self: When in doubt, check SuperUser.
SD card
Is there something I have to do to get the ROM to recognize the SD card
Thanks in advance rob
Is anybody experiencing miscellaneous battery drain? I thought that this was addressed in 5.0.1 if I'm not mistaken.
My battery drain could get as high as 71 percent from miscellaneous battery drain
Duskmustache said:
Is anybody experiencing miscellaneous battery drain? I thought that this was addressed in 5.0.1 if I'm not mistaken.
My battery drain could get as high as 71 percent from miscellaneous battery drain
Click to expand...
Click to collapse
I have intermittent battery drain issues too, and the bulk of the drain in the Battery status is "Misc" as well. Dev's, @oadam11, let us know if there's any data/logs we can provide to help identify if this is happening in the OS/ROM layer, or by a rogue app/configuration. I have a ton of stuff on my phone, from complex Tasker profiles for custom overlays on my AppRadio interface in my car, to my own Android apps.
I know an easy comparison would be to back up my device, factory reset, and run for a few days with just essential apps, but being my daily driver phone, I'm not sure I could do that for more than 24 hrs :\
Any data I can gather I'll be happy to do.
joeinbend said:
I have intermittent battery drain issues too, and the bulk of the drain in the Battery status is "Misc" as well. Dev's, @oadam11, let us know if there's any data/logs we can provide to help identify if this is happening in the OS/ROM layer, or by a rogue app/configuration. I have a ton of stuff on my phone, from complex Tasker profiles for custom overlays on my AppRadio interface in my car, to my own Android apps.
I know an easy comparison would be to back up my device, factory reset, and run for a few days with just essential apps, but being my daily driver phone, I'm not sure I could do that for more than 24 hrs :\
Any data I can gather I'll be happy to do.
Click to expand...
Click to collapse
Did you clean flash?
oadam11 said:
Did you clean flash?
Click to expand...
Click to collapse
I haven't recently, for the incremental ROMs. I have just been backing up, install ROM, Gapps, wipe cache, reboot.
I still suspect it has something to do with my AppRadio config, as (if memory serves), it seems to really start draining batt hard when i come back from lunch, and have therefore had it connected to my car. Anyway, I dont want to hijack the OP's question, I'll let them chime back in if there's any parallels to their experiences vs mine.
com.android.phone
I'm having an issue that effectively makes this rom unusable. I constantly get a crash message saying "Unfortunately, the process com.android.phone has stopped". When I say constantly I mean that clicking "ok" just reopens the little crash window. Other than that this rom seems amazing, so does anyone have a fix? I'm running the latest version as of this post
EDIT:
My Kernel just crashed. I think ill be switching to another rom, but if there is a fix i will be monitoring this and would like to be able to stay on resurrection
Ev_da_bacon said:
I'm having an issue that effectively makes this rom unusable. I constantly get a crash message saying "Unfortunately, the process com.android.phone has stopped". When I say constantly I mean that clicking "ok" just reopens the little crash window. Other than that this rom seems amazing, so does anyone have a fix? I'm running the latest version as of this post
EDIT:
My Kernel just crashed. I think ill be switching to another rom, but if there is a fix i will be monitoring this and would like to be able to stay on resurrection
Click to expand...
Click to collapse
Nevermind, I think I found the issue. I accidentally backed up the LG phone app's data and then restored it onto the google phone app. They obviously didn't play well together, but Im back on resurrection and loving it.
wifi 5.0 not working on Verizon LG G3 Resurrection remix
first time rooting and ROMing. loaded stock 10 image on ohone then rooted and rom'd Ressurection remix. GPS wouldnt work so i went through whole process again back to stock then made a GPS lock then rooted and rom'd again.
issue is i cant make a 5.0 connection to my router. my 2.4 signal connects. is this a known issue? another stock note 3 connects just fine to my 5.0.
also is there a way to have an icon for tethering on/off on home screen?
I've actually been having some difficulty with Bluetooth. I've managed to connect with a couple devices, however: one device doesn't show up, another doesn't display the name(just the address) and can't connect, and my home theater system connects and plays, but I notice the pitch is a fair amount flat. All of which worked fine on 4.4. Could this be a kernel thing? I don't really know how radios work, just looking for some insight I suppose.
overheating issues?
Flashed the latest build and was wondering if anyone else has issues with overheating. Antutu gives me a warning before running it after running just one time prior, and my battery is sitting on 42°C and has been for a long time while just browsing. Other than that, amazing rom. Beats the socks off of stock and brings this phone to life.
So I've been running this ROM but I keep getting com.android.phone force close. Is there any fix to this?
I have MMS issue
Unable to download MMS for me anyone have a fix tried Google messenger still no luck
A few observations with resurrection remix 5.4.3
I'm seeing an occasional freeze/screen lockup while using adaptive screen. When I turn it off far fewer problems. Besides the screen locking often, when I wake the phone the screen is very dark and slowly gets brighter or the screen stays dark when the phone rings. I also see some weird bugs after a phone call or notification on the lockscreen typically can't unlock or the status bar won't drop down.
Overall I love it. Very smooth and fast and nice battery life. Thanks!
Hi,
as some people may not be sure before switching to the beta version released by nubia, it may be a good idea to list the issues that we found with this rom
here are mine (I only use one sim card)
1: UI is slow and even more slow with full brightness (installing another launcher could help)
2: the notification switchs (data) will be ON whereas data is off . Plain mode also turn off data but the switch stay on
3: bluetooth audio is crappy... there are like sound hole every 5 seconds... can't use it correcly in my car
beside that, it did not tell the car what music is playing (there was no issue on CM12 and Mokee 5)
4: once the new system is installed, you can't reinstall directly install your previous backups as the partition is now different..
new CM12/mokee will be released soon to fix this. In the worst case you can still reinstall kitkat with the nubia update tool
alain57 said:
Hi,
as some people may not be sure before switching to the beta version released by nubia, it may be a good idea to list the issues that we found with this rom
here are mine (I only use one sim card)
1: UI is slow and even more slow with full brightness (installing another launcher could help)
2: the notification switchs (data) will be ON whereas data is off . Plain mode also turn off data but the switch stay on
3: bluetooth audio is crappy... there are like sound hole every 5 seconds... can't use it correcly in my car
beside that, it did not tell the car what music is playing (there was no issue on CM12 and Mokee 5)
4: once the new system is installed, you can't reinstall directly install your previous backups as the partition is now different..
new CM12/mokee will be released soon to fix this. In the worst case you can still reinstall kitkat with the nubia update tool
Click to expand...
Click to collapse
I've tried to duplicate the problem in number 1, but have not had problems. I've also read (don't remember where now) on a couple of the Chinese bbs that this seems common. Some people really think the new UI is slow and others do not have problems. I actually think it runs pretty smoothly.
I agree with number 2. Additionally, even though I have vibrate turned off, the phone always vibrates. Unless I have the phone on silent, then there is no vibrating and no sound. I've tried to have vibrate for silent only and it does not work.
I don't use bluetooth, so I cannot confirm number 3.
I partially disagree with point 4 because you can get much of what you had back previously if you used something like Titanium Backup. As I stated in one of my previous posts, I used Titanium backup to backup all apps and data. After that, I copied the folder to my computer. After installing the Nubia beta update, I transferred the folder back to the phone and restored everything without any problems. On the other hand, number 4 is correct. You cannot go back and reinstall a previous TWRP or CWM backup because of the unified storage. In my opinion, this has nothing to do with Nubia as this applies to any phone that upgrades from 4.4 to 5.0/5.1. If a rom says that it is Android L, but does not use unified storage, it is still technically a modified version of 4.4.
A couple of additional points that I don't like:
Cannot modify the actions of the buttons
No theme engine for further UI modifications
No clock widget (I know it's minor, but many people are complaining about this on the Chinese bbs too.)
One thing that is nice is that I had issues with my battery overheating frequently and since I have updated this has not happened at all. Maybe it's just me, but I'm kind of an app junkie. I'm always trying new apps; installing them, uninstalling them and so on. This process seems to be much quicker now. Additionally, I think that the signal has improved. I now have mobile reception in several areas where it was a dead zone previously.
thank you for your long feedback
in fact i prefer using cwm or twrp backups as i change the entire rom, it may be that some settings are not located at the same place so using a tool like titanium that run on the rom itself may not find all settings (but maybe they improved it since i first tried)
Concerning the UI slownes, I used Mokee and Cm12 on this phone and the feeling was a lot smoother
other people confirmed this. Try sliding from one desktop to an other with brightness level at minimum and retry it with maximum brightness you'll notice a visible difference
concerning the existing CM12/Mokee 5 roms, these are indeed Android5. But maybe they didn't change the storage to be 100% compatible with existing nubia partition
oh i also forgot, like in previous nubia rom, the UI has no notification access menu... I don't understand why
this is particulary useful if another device needs to read the notifications like a watch or a band... (but you can access it by installing 3rd party tools)
i'm on Cuocu92's modified Android 5 (he added some stuff like multilang, removed some useless apps and added google apps)
but I will switch back to Mokee or Cm12 as soon as they release a working version... the bluetooth and notification switch issue are two point that force me to switch
I do agree that Mokee and CM12 were a bit smoother. However, even when I change brightness from minimum to maximum I don't seem to notice any drastic change in smoothness. Maybe it's the launcher that you use like we talked about in the other thread. I agree with you on the notification access menu, that's a pain in the a$$. Interesting about the CM12/Mokee; I've read several places that state otherwise, so I'm not sure what to believe. I also agree, I too will switch back to Mokee or CM12. The FIUI rom has also been having some really nice improvements and I may try that if they switch to 5.0. For me the notification, the button customization, and the themes make me want to switch back.
Have to agree that the UI on 5.0 is pretty laggy even when using Nova launcher which is usually butter smooth their is major frame drops. And it especially gets laggy when brightness adjusts its self if set on auto.
Also at some point the home button stopped working for some unknown reason. I had to use the back button to exit apps. I don't know why some guys say that they don't have a theme engine. I have one on my ROM.
All in all I would not recommend someone using this ROM as a daily driver. Stick to 4.4 or any of the CM12, CM12.1 or Mokee versions.
I happen to have 2 Z7 minis with me and they both had the exact same bugs. I had to revert back to CM12.
i went to new CM12.1
but for people who need GPS => CM12.1 has a broken GPS, no signal, not even one satelite got detecte. Even outside with a clear view. Whereas official nubia can fix whitin 10 seconds inside ...
chalimoja said:
Have to agree that the UI on 5.0 is pretty laggy even when using Nova launcher which is usually butter smooth their is major frame drops. And it especially gets laggy when brightness adjusts its self if set on auto.
Also at some point the home button stopped working for some unknown reason. I had to use the back button to exit apps. I don't know why some guys say that they don't have a theme engine. I have one on my ROM.
All in all I would not recommend someone using this ROM as a daily driver. Stick to 4.4 or any of the CM12, CM12.1 or Mokee versions.
I happen to have 2 Z7 minis with me and they both had the exact same bugs. I had to revert back to CM12.
Click to expand...
Click to collapse
I agree now and finally see what people are talking about. Certain apps have really slowed down. It's apps that I don't use very often, but it's getting to be annoying. Going to give the new CM12 a try.
alain57 said:
i went to new CM12.1
but for people who need GPS => CM12.1 has a broken GPS, no signal, not even one satelite got detecte. Even outside with a clear view. Whereas official nubia can fix whitin 10 seconds inside ...
Click to expand...
Click to collapse
Can anyone help me? I was trying to flash the new CM12.1 using TWRP and in the middle of it the phone went black. Now I can't turn it back on, can't do anything. Ideas anyone? This sucks. Fortunately, I just did a backup of everything, but now the phone won't even power up. I'd appreciate any suggestions. Yes, I had already upgraded to the official nubia beta.
Edit: The phone still won't turn on, whether it's plugged in or not. However, when I plug it into the computer I can see 5 different partitions of various odd sizes with different aspects of the phone software visible.
Edit 2: So I did a hard reset and was able to get back to TWRP. Next I tried wipe data, cache, dalvik and it did the usual trying to format partitions and it kept failing, saying it couldn't access data. I tried flashing CM12.1 and it gave me the same error, although it said it installed successfully. I also flashed gapps. Now I'm waiting for it to boot up.
alain57 said:
i went to new CM12.1
but for people who need GPS => CM12.1 has a broken GPS, no signal, not even one satelite got detecte. Even outside with a clear view. Whereas official nubia can fix whitin 10 seconds inside ...
Click to expand...
Click to collapse
I've been on CM12.1 for almost 24 hours now and have not had this problem. GPS was off by default when I installed it and I had to enable it. I've used G-maps and a couple of other apps that need GPS and all of them locked on within a few seconds.
pedrud said:
I've been on CM12.1 for almost 24 hours now and have not had this problem. GPS was off by default when I installed it and I had to enable it. I've used G-maps and a couple of other apps that need GPS and all of them locked on within a few seconds.
Click to expand...
Click to collapse
did you tried with gps device only settings ?
because maps use wifi and network localisation to have a position even when gps is not turned on
this really makes me crazy...
I installed gps test and it stay a "no fix"
whereas when i restore my nubia 5.0 OS and tried gps test it fix directly
restoring back the CM12.1 got again no fix :/
alain57 said:
did you tried with gps device only settings ?
because maps use wifi and network localisation to have a position even when gps is not turned on
this really makes me crazy...
I installed gps test and it stay a "no fix"
whereas when i restore my nubia 5.0 OS and tried gps test it fix directly
restoring back the CM12.1 got again no fix :/
Click to expand...
Click to collapse
You are correct. I had not tried device only - it does not work. This is frustrating. Off to the Chinese forums to see what they say....
Hey guys I'm using the official v3.01 and I have so many bugs and crashes. Worst of all it crashes when I have an incoming call and sometimes the screen goes dark when I get a call and I can't swipe and answer the phone. Is there anyway to go back to KitKat 4.4.4? Can anyone explain the steps?