Related
hi guys
For those that haven't heard of or seen an Sleep of Death (SoD) in action , it is where your phone does not respond to any user input whilst it's in sleep mode thus making the phone unusable since you are unable to wake the phone. The only way to recover is to either force reboot the phone, receive a call or call yourself from another phone.
I have encountered SoD four times til now, on KE2, KE7 and Now KF2 .
I don't think its got anything to do with the ROM, this has happened for me on Cognition, VillainRom , CF-root on stock Roms.
looking around the web it seems it might be a kernel/driver issue and remains unfixed (not sure)?
Anyone knows workarounds? Any Devs that are working on this?
Thanks
I haven't encountered this yet and I've also tried a bunch of different ROMs. Are you by chance overclocking or underclovking/UVing at all? If so, that could be the culprit. If not, then its hardto say what may be causing it other than an app the phone may not respond well with.
I had this happen once. I tried many ways to wake it up even charging, the charging sound comes up but the screen wont wake. Had to reboot.
Havent happened again though.
I haven't under/over clocked the CPU at all but from what I understand it has nothing to do with CPU frequency but more so a bug in kernel or in one of the drivers.
Its not easy to reproduce but its definitely there, I'm hoping it'll be addressed in cyanogen rom when its out given the fixed SoD somewhere in 7.0rc I think.
Sent from my GT-I9100 using XDA Premium App
ke3pup said:
I haven't under/over clocked the CPU at all but from what I understand it has nothing to do with CPU frequency but more so a bug in kernel or in one of the drivers.
Its not easy to reproduce but its definitely there, I'm hoping it'll be addressed in cyanogen rom when its out given the fixed SoD somewhere in 7.0rc I think.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
On my ace this issue occured when the wifi was on. The phone goes into "sleep mode" and needs a reboot (press the power key for 10 seconds).
I was not able to find the exact conditions but it was more promient when 3g was also switched on.
Does your issue occur only when the wifi is on?
This has happened 4-5 to me
as well. I have found that a putting the phone on charge can free it. But its a real pain if it happens out and about, I had to take the battery out to get it to work
i got it 2-3 times while using "Green Power" app.
Again this has nothing to do with an app/rom..etc. you may think a certain app you installed its causing it but in case of SoD that's highly unlikely. The source of problem is else where.
"@cyanogen: @Bradart @1000hams try a nightly build if you are on 7.0. Google fixed bugs for 2.3.4 that can cause that (7.0 is 2.3.3)."
Click to expand...
Click to collapse
The above is a quote in response to SoD question (don't know which device, but android < 2.3.4) which to me suggests another bug in 2.3.3 that has been fixed in 2.3.4.
http://forum.xda-developers.com/showthread.php?t=1238478
Here's the solution I hope it helps... it worked for me
Bug Report - SGS2 (Sleep of Death)
Please use this link to report the bug:
code.google.com/p/android/issues/detail?id=21607&thanks=21607&ts=1320690472
I think I found a way to avoid SoD (Sleep of Death)
I'm new on the forum And that SoD problem annoyed me for so long and I kept searching.... But I think I finally found why we kept getting SoD.
Ok so I'M NOT SURE, but Try following those steps and be sure of every single thing and then tell me if you guys keep getting SoDs..
1- "Do not use two governors as screen-on & screen-off govs, if they both have an upper frequency limit for screen-off state." - droidphile
2- I think some of us don't do "clean flash of our ROM", so you guys need to follow those exact steps from that link
http://forum.xda-developers.com/showpost.php?p=28395322&postcount=3
Or I will just write them again...
1- Reboot into recovery (Turn off your phone then press and hold the keys: Volume Up + Power + Home)
2- Wipe Data / Factory Reset
3- Install the Main ROM file
4- In AROMA installer select "Custom Installation"
5- Choose depending of your taste
6- When AROMA installer finish untick the "Reboot Now" option
7- When you're back on the recovery go to Advanced
8- Wipe Dalvik Cache
9- Fix Permissions
10- Wipe Cache Partition
11- Reboot
12- When you get the step for add your Google Account, if you don't have a WiFi enabled or you can' add it, skip it
13- When you boot into the system, it's probably that you don't have data enabled (3g, H+) just reboot the phone
14- When you boot again into the system, the data will be enabled and you can do the configuration of Google Account (if you don't do this step before)
This is the moment for install all the extras like themes, mods, fixes, kernels, etc.
3- ok and NOW After your "CLEAN Flash of ROM" When you use Titanium backup Root application to restore your applications, DONT restore the things with RED text color. Restore ONLY the things with green text color.
In other words, restore only apps with their data and NOT all system data.
4- Ok and Once you did that. About the Governor you use, I think we push the limits of the CPU and the phone just can't resist the tweaks we did and a SoD appears. So try these settings if you have Siyah Kernel
Minimum CPU frequency: 200 Mhz
Maximum Frequency: 1000 Mhz
Governor: luzactive
Default I/O sheduler: SIO
So try THAT and tell me if you guys keep getting SoD ...
lol I didn't get SoD since 2 days And I hope it could help. Because installing Wake My Android Pro, or WakeLock or Load Monitor just DIDN'T work for me -__-
i stumble upon this problem whenever i use too harsh UV settings(depends from kernel to kernel). also my device SoDs whenever i use 100mhz as the lowest step- again with some kernels it tolerates it. my guess is: every phone is slighty different, so you just have to experiment with yours and find the best settings for your specific hardware (you dont say xD)
screenager said:
i stumble upon this problem whenever i use too harsh UV settings(depends from kernel to kernel). also my device SoDs whenever i use 100mhz as the lowest step- again with some kernels it tolerates it. my guess is: every phone is slighty different, so you just have to experiment with yours and find the best settings for your specific hardware (you dont say xD)
Click to expand...
Click to collapse
I understand your point of view, but by the way, I read a lot of that forum, and putting minimum frequency at 100Mhz might be Bad for your phone for 4 reasons:
1) When you receive a call, the call might lag because it needs absolutely a minimum of 200Mhz, so setting your CPU minimum frequency at 100Mhz might cause probs for phone calls.. ( i read that somewhere on XDA but dont remember where...)
2) Moreover, "It seems 100 mhz uses more power than 200 mhz. According to tests, 100 mhz accounted to 1 W / GHz and 200 mhz to 0.7 W / GHz, when both the cores were online."
3) "200 mhz can finish same task faster compared 100 mhz and thus hit deep idle soon."
4) "200 mhz is the 'sweet spot' of frequency in SGS II. ie, the frequency used in the calculations based on the optimal energy to run (Ex: In Milestone it's 550 MHz). So , 'energetically efficient' frequency for our CPU is 200 mhz."
Those 3 last reasons came from droidphile I'm not the author of this, but minimum frequency should stay at 200Mhz
i want reactivate this thread, because I think there are some users who still have this problem like me.
As far as I recognized there seems to be more reasons for SoD.
All seems to have begun with Android 4.1.2 and just keeps on until now.
I have tried some kernels and runs now Dori 9.33 and see how it works.
It seems that there are some kernel issues as well as some apps and some constellations of SD-cards.
But no one has a real solution.
I read about a "indish kernel" for the i9100g models, but also some who reported SoDs with this kernel.
But I found no real solution for our i9100.
I have attached a logfile (catched with Catlog) which I recorded until my last SoD.
In my case, I can also call my phone and the caller hears it ringing, but my phone stays black without sound and unresponible.
The only thing is to hold the power button for 10 seconds and reboot it.
just to tell:
nearly 24h without a SoD with my combination
BUT: I have not used my camera so far! And I think camera & media scanning has something to do with it.
If everything is running until tonight, I will try my camera and see the result.
after nearly 2 days
:good: nearly 48h working, so I will keep my combination.
But it is interesting, that nobody has any problems although you can read a lot about this problem.
after more than 2 days:
and here we go. SoD :crying: but 48h is better than nothing
a lot of things might come from corrupt files.
There are 2 scripts which will clean your partitions and try to fix broken files
1. GS2ROMclean made by hawkerpaul
2. Fix_Partitions_v1.0.2.zip made by Computoncio
you can run out of CWM and install as a zip.
So far it is recommended to run 1. GS2ROMClean, reboot, then 2. Fix Partitions to ensure you have clean partitions
Be patient! 2. runs very long, up to 2 hours and the phone becomes very hot. So I think power connection is absolutely recommended
BUT NOT TESTED COMPLETELY BY ME
what I do not know is, how often these scripts shall be used
You could run the ROM clean as often as you want. If the other doesn't fix it after one time, no point running it again. In saying that, I'm not sure if there would be any benefit from running the first one more than once anyway.
Sent from a galaxy far, far away
lavemetoo said:
a lot of things might come from corrupt files.
There are 2 scripts which will clean your partitions and try to fix broken files
1. GS2ROMclean made by hawkerpaul
2. Fix_Partitions_v1.0.2.zip made by Computoncio
Click to expand...
Click to collapse
1. runs very fast, took round about 10 seconds. Reboot was successful afterwards. All was working.
Now I run 2. - info will follow - would be great, if there were a kind of progress bar or a kind of information. So you don not know if it hangs or not.
script 2. ended after 1h with a warning. Now run again?
Code:
/dev/block/mmcblk0p10: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p10: ********** WARNING: Filesystem still has errors **********
/dev/block/mmcblk0p10: 11854/131072 files (5.4% non-contiguous), 524288/524288 blocks
Checking preload partition:
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Create? yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p12: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p12: 544/32768 files (0.0% non-contiguous), 29992/131072 blocks
Automatic Fix Partitions finished at 30-07-2013 14:10:33
attached is the complete logfile
ATTENTION: My phone was connected to USB and lost 10% battery during this script operation!
I'm a noob so I can't ask a question in the dev forum on this thread (where it would be more appropriate):
http://forum.xda-developers.com/showthread.php?t=1362961
I've got the ROM installed and I'm not going to complain about the lag because I've read that it clears up. However, I haven't seen any comments about 2 problems I have.
1) I'm on the east coast of the US and I've got the settings to auto-update over the network, but my phone thinks it's 5hrs ahead of my actual time.
2) When I try to download anything through the market or using apps (like SMS Backup +), it just crawls at a tiny fraction of my previous speeds.
Are these more "just wait for it" issues that will clear up or is there something I can do?
I've already installed CWM's Rom Manager and used it to fix permissions and rebooted a couple of times. THANK YOU!
For the time, it's better to just select your time zone. I've never had the time be accurate when set to automatic. As for the lag, I believe it just takes time. I'm flashing it now so I'll let you know if I notice the same thing and if it seems unusual.
Edit:
After flashing and letting the phone sit, the biggest thing I noticed was it running slow and the battery dropped from 98% to 30% in the 2 hours it sat. I hadn't tweaked my settings yet and CPU Spy revealed that my system was running at 1200 MHz for the majority of the time. Here's what I've been doing with previous versions of ICS that I feel makes a huge difference. In Rom Toolbox, set CPU from 1200 MHz to 1000. Then go to settings > developer options > Don't keep activities. This seems to kill activities more efficiently than a task killer/manager. I also don't allow any other stuff in the background like google getting my location. I also keep gps off unless I need it. With these settings and v6.5 I was getting an average of 10 hours on a charge with frequent use. I'll keep updating as the rom settles.
I set it manually and that seems to stick fine. As a test, I then set it back to auto-via-network and it's still right after a couple of reboots.
The slow internet downloads are KILLING me.
Prior to following the instructions in the ICS passion v7 OP, I dd a ClockworkMod backup of my CyanogenMod7-Kang setup.
Now, I've done a CWM backup of this ICS setup. Can I use CWM to go back and forth from one backup to the other?
...well, I guess I'll find out as I'm about to give it a shot.
Edit: didn't have any problems going from the clean ICS install back to my CM7-kang backup! (whew)
On the other hand, when I tried to go forward from the CM7-kang backup to the ICS backup, it was craptacular and I had to flash the ICS rom again. Not too awful, I guess.
Also, holy crap it's faster now that I let it sit, turned on, while I slept! Yeehaw!
Even the market-downloading is blazing.
a fellow noob with a problem on ics v7
for some reason I can't see the external sd on the phone. I CAN access the external sd on my pc and write files to it. I just cant get the phone apps to SEE the external sd. Help? Should I get back to stock then go for ics v7? (I tried a few mods in-between, might not be ics v7 fault - otherwise everything great with it!) Well, I am going to go back to stock via odin now (sigh) and then to v7 to see if that's the problem.
I've had similar problems. I think the fix is to format everything, but I'd rather not so I'm must accepting things as they are for now. Just a layperson guess, though.
The time zone needs to be set manually.
The slow 3G connection is the only noticeable problem. Wifi speeds are the same as always. Toggling the wifi on/off seems to help my 3G speeds at first. I used the speedtest app in the market to test.
Good luck!
update to v8
I had the same snail download speeds on v7 and am not sure why, but now I'm up to v8 and it is back to the crazy fast downloads!
Hello everyone. I have a GSM EVO 3D, S-OFFed and running KingCobra3D 1.8.1 and Unity v3 kernel. Problem is, my phone occasionally bootloops for no apparent reason. When it happens, I need to shut the phone off (PWR+VolUp+VolDown for 5 seconds) and repower it again and it boots up fine. It happens approximately every 25-35 hours. Other than that, the phone is running perfectly fine. It can happen while I'm watching a movie, browsing through the UI or even while it's in standby state (which is the worst because it sometimes drains the whole battery at night while I'm sleeping). I used another kernel before (AnthraX 12-15) and bootloops where present too.
I already tried flashing the stock ROM through PG86IMG.zip (if I got the name right) and then applying my ROM again, but bootloops still happen. I have a feeling there is an issue with some software. Other users of this ROM (and kernel) report to bootloops.
Can anyone recommend me any ways to check what causes the problem? Are there any good loggers that can log phone activity besides logcat? I have an idea to do adb logcat on my PC and leave the phone connected hoping it will catch a bootloop this night, but are there any other methods? Maybe Android makes error logs somewhere?
Or maybe forum users know of something about those sudden bootloops?
I'm using Go Launcher EX, CPU 384-1.52Ghz Ondemand (so no OC).
Please use the Q&A Forum for questions Thanks
Moving to Q&A
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,
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?