everyone who're fedup with Oxygen OS can try this new rom BlissMallow rom formerly known as Blisspop
works smooth & fine, you can use it as a daily driver
as usual LAF & FP not working as of now.
http://forum.xda-developers.com/oneplus-2/development/rom-blisspop-t3226519
Just flashed it yesterday, so far so good !
flashed it yesterday too, found it a little too buggy.. facebook app FC's, drop down menu FC's, gps was off, and alert slider doesn't work along with LAF & FP. Took crappy pic's. I'll stick with OOS with xposed modules for now. We aren't to far off from official 6.0 for OPT
Jr173 said:
flashed it yesterday too, found it a little too buggy.. facebook app FC's, drop down menu FC's, gps was off, and alert slider doesn't work along with LAF & FP. Took crappy pic's. I'll stick with OOS with xposed modules for now. We aren't to far off from official 6.0 for OPT
Click to expand...
Click to collapse
The rom is pretty stable, not a lot fc's for me and non at all at the dropdown menu.
Gps is worknig, camra is working and there is no diffrance in the pics from oos.
It's a good rom, and cloud be a daily use, even it's a bata.
I have two major issues with the latest rom :
1. rotation sensor not working.
2. proximity sensor not working.
clean flash 3 times , tried downloading the file two times to rule out bad download
also flashed it with/without Google apps , nothing helps so far
is anyone else facing those issues here or can someone please point me towards a solution?
thank you
moshikko said:
I have two major issues with the latest rom :
1. rotation sensor not working.
2. proximity sensor not working.
clean flash 3 times , tried downloading the file two times to rule out bad download
also flashed it with/without Google apps , nothing helps so far
is anyone else facing those issues here or can someone please point me towards a solution?
thank you
Click to expand...
Click to collapse
Do an advanced wipe. And wipe everything expect your SD card.
Flash Blissmallow and any gapps ( I use slim gapps) and then wipe dalvik and cache
AndroidBeginNinja said:
Do an advanced wipe. And wipe everything expect your SD card.
Flash Blissmallow and any gapps ( I use slim gapps) and then wipe dalvik and cache
Click to expand...
Click to collapse
giving it a try right now
edit: not working .
tried it twice and still no go, very weird
when trying any other cm13 based rom sensors works great, I think it has something to do with mahdi's device tree.
Just tried this today. So far:
1) Sometimes FC in settings when switching which SIM card to use for data
2) Waking up device by power button wakes the screen, but it's black and I can't input the PIN to unlock the device. Basically I have to force reset it. This happens every now and then.
3) Priority toggle: If you toggle too quick, the phone doesn't understand and misses it. I.e. you might be in "do not disturb" mode, but the phone didn't catch on so it thinks you're in "priority only", letting things through.
4) Camera seems to work OK, autofocus not an issue so far
5) No idea about battery life
6) Obviously no finger print scanner
I'm going to test it as a daily from now on, let's see how this goes. (coming from OxygenOS)
moshikko said:
giving it a try right now
edit: not working .
tried it twice and still no go, very weird
when trying any other cm13 based rom sensors works great, I think it has something to do with mahdi's device tree.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591
Mohit31 said:
Try this
http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591
Click to expand...
Click to collapse
:good: :good: :good: :good:
Will do right now , thnx
edit: THANK you very much
finally it works, tried many things but this is the only solution that works
you are my new hero!!!!
moshikko said:
I have two major issues with the latest rom :
1. rotation sensor not working.
2. proximity sensor not working.
clean flash 3 times , tried downloading the file two times to rule out bad download
also flashed it with/without Google apps , nothing helps so far
is anyone else facing those issues here or can someone please point me towards a solution?
thank you
Click to expand...
Click to collapse
I have exactly the same issue and have flashed stock using the recovery tool, and factory reset and refashed oxyslim and I still have no proximity snesor and not rotation at all.
I cant find a modem thread for the a2003 op2, some say they modem maybe wrong.
Two posts above there is a solution that works, you need to wipe persist and flash the one in the link above
Just follow the instructions and youre all set
Good luck
How can I check if LAF is working? How can it be enabled? Is a special camera app recommended?
Deacon-Frost said:
How can I check if LAF is working? How can it be enabled? Is a special camera app recommended?
Click to expand...
Click to collapse
if you're on late version that has LAF working just look at the camera and you'll see a red dot underneath it.
I use the camera that comes with the rom and its great
Great ROM
Hi All
Like this rom. This is the ONLY rom that has been stable enough to tempt me away from oos.
I did a clean flash for the initial install, then dirty flash with the updates. Current Running the 20160224-1305 build
Very few issues. Good enough for my daily driver. The only bugs I've found so far..
Lock Screen Notifications. Double Tap to launch doesn't work. Screen just shuts off again.
Bluetooth Pulldown. Pressing the "x" next to a connected device should disconnect. But actually does nothing.
Battery life seems a little poorer
TouchScreen sensitivity issues. Occasionally touchscreen goes a bit nuts and it becomes difficult to type with unintended keys being hit, and becomes difficult to access pulldown menu. Have to reboot to solve.
Minor Wifi issues. I'm getting disconnection issues when I connect to specific public wifi points which didn't occur under oos.
I had an issue with SnapChat being unable to access the camera but I solved this. If you restore from titaniumbackup the camera connect error occurs. If you then wipe cache/data for the SnapChat app and log back in it works fine.
djmarkm said:
Hi All
Like this rom. This is the ONLY rom that has been stable enough to tempt me away from oos.
I did a clean flash for the initial install, then dirty flash with the updates. Current Running the 20160224-1305 build
Very few issues. Good enough for my daily driver. The only bugs I've found so far..
Lock Screen Notifications. Double Tap to launch doesn't work. Screen just shuts off again.
Bluetooth Pulldown. Pressing the "x" next to a connected device should disconnect. But actually does nothing.
Battery life seems a little poorer
TouchScreen sensitivity issues. Occasionally touchscreen goes a bit nuts and it becomes difficult to type with unintended keys being hit, and becomes difficult to access pulldown menu. Have to reboot to solve.
Minor Wifi issues. I'm getting disconnection issues when I connect to specific public wifi points which didn't occur under oos.
I had an issue with SnapChat being unable to access the camera but I solved this. If you restore from titaniumbackup the camera connect error occurs. If you then wipe cache/data for the SnapChat app and log back in it works fine.
Click to expand...
Click to collapse
1. You have to 'disable double tap screen on lock screen to lock to sleep' on the settings/bliss settings/lock screen.
Cant help with the other issues though!
djmarkm said:
Hi All
Like this rom. This is the ONLY rom that has been stable enough to tempt me away from oos.
I did a clean flash for the initial install, then dirty flash with the updates. Current Running the 20160224-1305 build
Very few issues. Good enough for my daily driver. The only bugs I've found so far..
Lock Screen Notifications. Double Tap to launch doesn't work. Screen just shuts off again.
Bluetooth Pulldown. Pressing the "x" next to a connected device should disconnect. But actually does nothing.
Battery life seems a little poorer
TouchScreen sensitivity issues. Occasionally touchscreen goes a bit nuts and it becomes difficult to type with unintended keys being hit, and becomes difficult to access pulldown menu. Have to reboot to solve.
Minor Wifi issues. I'm getting disconnection issues when I connect to specific public wifi points which didn't occur under oos.
I had an issue with SnapChat being unable to access the camera but I solved this. If you restore from titaniumbackup the camera connect error occurs. If you then wipe cache/data for the SnapChat app and log back in it works fine.
Click to expand...
Click to collapse
1. Try not double tap that fast on the notification.
Aduck79 said:
1. Try not double tap that fast on the notification.
Click to expand...
Click to collapse
Thanks., Tofuboi01 had the right solution. It was a setting in Bliss Settings->Lockscreen
Related
1. 4g handoffs still dont work. (wiped data and reset apn)
2. after being somewhere with no signal i get 1x for a long time
3. making a phone call force closes the dsp equalizer
4. auto brightness not working
anyone else still experiencing any of these? is there a fix i dont know about. a zip, a kernel?
thanks in advance
I upgraded from 1.2 without wiping and I don't have any of those problems.
The only problems I have are some wake lock issues. The weather channel app and Android System both give me wake lock. Granted they did this on 1.2 as well, and it also seems to happen on any AOSP ROM I've tried, so it isn't just CM.
agreed. Not seeing any of these problems. Sounds like you may not have wiped when flashing so do that and try again.
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!
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?
I wanted to post this for people who want to try out MM on the LS990 and have fully working 3G and 4G/LTE data on a Sprint network. I'll explain the exact conditions that I personally went through to get it working.
I CANNOT GUARANTEE THAT THESE STEPS WILL WORK FOR YOU. YOU MAY EXPERIENCE PROBLEMS AS MENTIONED BELOW.
The flashing and setup:
What I personally did was flash BareCee v2 and then updated the PRL and Profile. Afterwards, I dirty flashed BlackSoulxxx's v30b MM port (see: http://forum.xda-developers.com/lg-g3/development/rom-lge-d855-android-marshmallow-ported-t3285025). I rooted the port with SuperSU 2.52 BETA via TWRP. Once I got to the home screen, I was greeted by a notification that stated that I need to update Google Play services. I updated it. Then I confirmed my appropriate APN settings. I'm on RingPlus, so this was important for me to even get mobile data at all.
The fix:
Once I went through all that, I edited /system/build.prop using Solid Explorer with the following lines:
ro.product.model=LGLS990
ro.build.target_country=US
ro.product.locale.language=en
ro.product.locale.region=US
ro.cdma.home.operator.alpha=Chameleon
ro.cdma.home.operator.numeric=310120
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
Click to expand...
Click to collapse
The following two lines might be disabled in your build.prop. If they are active, ensure it's set properly as listed below. It was disabled on mine, so I did NOT touch them or re-enable them:
ro.telephony.default_network=10
telephony.lteOnCdmaDevice=1
Click to expand...
Click to collapse
If you don't care for having your phone unlocked for Global/GSM use, you can edit the following lines to get the Sprint 3G/LTE, airplane mode, etc. status bar icons and branding (as well as disable the Global/GSM network option):
ro.build.target_operator=SPR
ro.carrier=Sprint
Click to expand...
Click to collapse
After you have edited the build.prop, give it a reboot and toggle data/airplane mode in the quick toggle/notification pull-down menu until you get data to finally turn on. Once it switches on, it'll work until your next reboot, I believe. You will need to fiddle with the toggle again once you reboot. This is a bug due to the ports. There's no known fix for this besides dirty flashing over BareCee v2, but I can't really say for certain if everybody will have this fixed just by dirty flashing. Dirty flashing also allows the settings switch and data settings panel to work correctly (sometimes).
From what I can tell, ro.cdma.home.operator.numeric is the key factor for getting 3G data to work properly.
Negative repercussions:
You may have issues with Messaging.app and weather.app NOT working/crashing after launch IF YOU DIRTY FLASH. I'm not sure how to fix this issue other than with a CLEAN FLASH.
Others have expressed issues with google play services not working or force crashing and causing the OS to be unstable. Clean flashing fixes this problem, usually.
Fulmics 3.1 and xpirt was the source of this fix and it was stated that this will be included in the next version of Fulmics 3.X. I personally cannot use Fulmics because it's highly unstable for me. It overheats my phone and there's heavy lag with poor battery life.
Other Notes:
I would like to see somebody clean flash BlackSoulxxx's port or Fulmics 3.1 and try this out. I'm too busy to keep flashing/testing and everything I need is working (I don't bother with the stock Messaging app and weather app works fine for me). Please report back if you do this and let us know what happens. I suspect this is the best possible outcome for avoiding force crashes, but it also may mean that the data may not work properly, even after this fix.
Hope this helps somebody. It took me weeks to resolve this issue.
Thanks to:
blacksoulxxx
xpirt
6th_hokage
jglm4u
This should get its own post: The MM port is unlocked for GSM by default, I believe. Fulmics 3.1 is the same.
No luck for me..
Whenever I make all these changes on a clean flash of fulmics 3.1, I get constant FC's of com.android.phone
spanky34 said:
No luck for me..
Whenever I make all these changes on a clean flash of fulmics 3.1, I get constant FC's of com.android.phone
Click to expand...
Click to collapse
Not sure why you're getting phone FCs, but I'm like 99% sure it may be a fulmics issue. I'm using the blacksoulxxx port right now.
Also, confirmed bug:
ro.build.target_operator=SPR
ro.carrier=Sprint
These two lines cause media services to crash for a media player stuff. Facebook messenger videos and Google hangouts voicemail audio crashed when it searches for sprint-specific players. Strange as hell.
Couldn't you just make a flashable zip to fix the build.prop?