Related
I've tried a few different custom ROMs on here, and recently most seem to be sufferring from the same issue. It's been happening to me for a couple of months now, I'm not sure if it's a 6.5 bug, or some other software package or whatever. I will say I just recently got a replacement phone for another problem, and it's doing the same thing as my old phone. At my work, we require a 4-digit password and for the phone to lock within an hour for our Exchange server sync.
For whatever reason, when I put custom ROM's on there and sync, within about 3 days at most my device will totally wipe. It wipes the storage card, everything. And it's a real pain in the ass to try to keep my settings for very long. I'm just curious if anyone else is seeing the same issue? I just figure, probably not a lot of people require a password so it doesn't happen to a lot of people. It seems to only affect 6.5 ROMs for whatever reason.
Shameless bump. Sorry, just want to make sure, someone has to have seen this, maybe not though.
I can really only confirm this happens on two ROMs. I don't want to call anyone out because it might be a WM6.5 bug and not a chef's fault.
sheps rom works for me, it is the only rom I have used so i cannot confirm your question about other roms not working. good luck and if i were you try Sheps rom, very fast and stable rom, and it looks good to.
http://forum.xda-developers.com/showthread.php?t=497699
I use exchange at work and have only seen this once, and the problem for me was the security code was input incorrectly more than 7 times and all data was erased even the microsd card. I was quite pissed but thats the only time I've seen it.
dapirate said:
I use exchange at work and have only seen this once, and the problem for me was the security code was input incorrectly more than 7 times and all data was erased even the microsd card. I was quite pissed but thats the only time I've seen it.
Click to expand...
Click to collapse
It's similar to that, it used to be where I would leave the phone sitting there for a while and come back to it and it would say "if you input your password incorrectly one more time...blah blah". And no matter what i do, it would wipe my device. Now usually i just turn the screen on and the skinned keys don't show up, it's just the old one. Pressing the keys does nothing at all, i usually reset the device, then it wipes on the next reboot.
at one time i thought it was related to either plugging it into the charger or a computer because it would usually do it right after that. I see it happen no matter what now though, i could just have it sitting there and it will do it.
stickynugz said:
sheps rom works for me, it is the only rom I have used so i cannot confirm your question about other roms not working. good luck and if i were you try Sheps rom, very fast and stable rom, and it looks good to.
http://forum.xda-developers.com/showthread.php?t=497699
Click to expand...
Click to collapse
Well obviously one of them is NRG's ROM, I have also seen this in TPC's ROM. Hard to say what's similar between the two...I can't confirm too many others though as I don't usually switch that often, just when the one's I like to use update.
Yep. I've had the very same 'feature' happen to me too. Cannot properly identify what's causing it either.
Cheers
Have you checked with your Exchange Admin... I believe there is a feature that allows them to remote wipe (or at least setup the parameters) devices attached to the server... They may be wiping your device because it shows up as a foreign device... Just stabbing in the dark, it may not be a rom based issue, but an exchange issue... It happens with custom roms, did it happen with the stock rom...?
debonairone said:
Have you checked with your Exchange Admin... I believe there is a feature that allows them to remote wipe (or at least setup the parameters) devices attached to the server... They may be wiping your device because it shows up as a foreign device... Just stabbing in the dark, it may not be a rom based issue, but an exchange issue... It happens with custom roms, did it happen with the stock rom...?
Click to expand...
Click to collapse
Good suggestion, although I am the Exchange admin, so no, I'm not wiping my own device.
I have never seen it happen on a stock ROM, although I usually don't have one on for very long. I've never seen it in 6.1 either, just 6.5 ROMs from about late June thru now.
OK, 3 ROM's now, RRE just did it to me. It must be a 6.5 bug or an Exchange server bug.
schwags said:
OK, 3 ROM's now, RRE just did it to me. It must be a 6.5 bug or an Exchange server bug.
Click to expand...
Click to collapse
well i run 6.5 and use exchange 2007 for my business, havent seen this happen at all on any rom. I dont have any pin required for my devices, but i can turn that on just to test for you.
fallingup said:
well i run 6.5 and use exchange 2007 for my business, havent seen this happen at all on any rom. I dont have any pin required for my devices, but i can turn that on just to test for you.
Click to expand...
Click to collapse
That would be cool if you could. I have a feeling since it happened on two phones and multiple ROMs that it will happen to anyone. I just feel that no one really requires a password. Just make sure you set a maximum number of attempts before wipe, I have the default of 8 set. Use one of the ROMs I mentioned if you don't already.
im not using exchange and it has happened to me with one of the roms.
the chef didn't really know what do with it or what's causing it, all i know is that it has never happened to me before, and after changing to shep's rom it hadn't happen since.
give shep's rom a try.
I'd think your Exchange server is having issues. There should be logs to see if a remote wipe was ever performed on your device. Are you sure your kids or annoying friends didn't try to unlock your phone a few times which may have caused the remote wipe?
This just happened to me on Sunday, running my own-cooked 23033 ROM (and about a week earlier as well)
I hadn't even tried inputting a password - my phone had been locked, and when I looked at it, I got the message about having one more chance to enter the password (which it wouldn't let me do - the phone was completely locked up). Since this had happened to me before (I had JUST finished putting most of the stuff back on my 16GB microSDHC card), I quickly removed the card, put in the correct password, and watched my phone hard reset.
So no, you're not crazy. It may be related to Exchange, but I doubt it. I think it's more related to Pin Lock, because after 5 unsuccessful attempts to unlock a device (whether it's synched with Exchange or not I believe), the phone is supposed to hard reset to protect your personal data. There must be a glitch with Pin Lock in some of the 6.5 builds that causes this on occasion. I'm not sure what it is, though.
Did a bit of research ...
Apparently, a trusted application can initiate an erase-and-format operation by calling a LoadLibrary function in Fatutil.dll. There a registry key that controls full device erasure is:
Code:
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\<MyProfileName>\FATFS]
"SecureWipe"=dword:1
Also, there is this key which controls LocalWipe and RemoteWipe based on the Password Required Policy (4131) setting.
Code:
[HKEY_LOCAL_MACHINE\Comm\Security\Policy\LASSD\DeviceWipeThreshold]
"4146"=1 through 4294967295 (0xFFFFFFFF)
4146 = SECPOLICY_LASS_DESKTOP_QUICK_CONNECT
Apparently, setting "4146" to zero (0) or 4294967295 (0xFFFFFFFF) disables the feature.
This is really going to suck if it turns out that some ROM packages now include LocalWipe/RemoteWipe as some form of anti cross-porting device protection.
HTH,
Captain_Throwback said:
This just happened to me on Sunday, running my own-cooked 23033 ROM (and about a week earlier as well)
I hadn't even tried inputting a password - my phone had been locked, and when I looked at it, I got the message about having one more chance to enter the password (which it wouldn't let me do - the phone was completely locked up). Since this had happened to me before (I had JUST finished putting most of the stuff back on my 16GB microSDHC card), I quickly removed the card, put in the correct password, and watched my phone hard reset.
So no, you're not crazy. It may be related to Exchange, but I doubt it. I think it's more related to Pin Lock, because after 5 unsuccessful attempts to unlock a device (whether it's synched with Exchange or not I believe), the phone is supposed to hard reset to protect your personal data. There must be a glitch with Pin Lock in some of the 6.5 builds that causes this on occasion. I'm not sure what it is, though.
Click to expand...
Click to collapse
Well that's good, i was starting to feel crazy. Exact same symptoms though, phone is just sitting there, locked, and when i turn the screen off I get that message. Most of the time the screen appears to be locked at this point, i'll try a reset and it boots, wipes instantly, reboots and runs through hard reset. I am preparing to install a few Exchange updates, so we'll see if that corrects it. I did check and our last major update was in April, and this started happening in late June, so I don't think it's Exchange either.
hilaireg said:
Did a bit of research ...
Apparently, a trusted application can initiate an erase-and-format operation by calling a LoadLibrary function in Fatutil.dll. There a registry key that controls full device erasure is:
Code:
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\<MyProfileName>\FATFS]
"SecureWipe"=dword:1
Also, there is this key which controls LocalWipe and RemoteWipe based on the Password Required Policy (4131) setting.
Code:
[HKEY_LOCAL_MACHINE\Comm\Security\Policy\LASSD\DeviceWipeThreshold]
"4146"=1 through 4294967295 (0xFFFFFFFF)
4146 = SECPOLICY_LASS_DESKTOP_QUICK_CONNECT
Apparently, setting "4146" to zero (0) or 4294967295 (0xFFFFFFFF) disables the feature.
This is really going to suck if it turns out that some ROM packages now include LocalWipe/RemoteWipe as some form of anti cross-porting device protection.
HTH,
Click to expand...
Click to collapse
Thanks for that! If someone could be so kind as to whip that into a cab file, that would be great. Might at least give a temporary fix for this until it's figured out. I keep re-flashing new ROM's and hoping it'll go away one of these times.
I would bet that the suggestion of remote wiping is the best track to follow. Perhaps the "Managed Programs" feature is somehow automatically set in your exchange environment and creating the problem? Although I do not know what I am talking about, just guessing. Seems like a security issue with your exchange/phone set-up. Try replicating the issue with the radio off. At least then you will know if it is an Over The Air Issue or something set on the phone itself.
Sounds like a real pain. Good luck sorting it out.
Doug M.
Before putting together any form of .CAB, it would be worthwhile for those experiencing the problem to provide the following feedback:
Is it only occurring on devices receiving policies from an Exchange Server
Are the registry entries I noted above present and what are their values
Is the issue specific to certain ROM builds
Is there perhaps a common set of packages in use
Cheers,
hilaireg said:
Before putting together any form of .CAB, it would be worthwhile for those experiencing the problem to provide the following feedback:
Is it only occurring on devices receiving policies from an Exchange Server
Are the registry entries I noted above present and what are their values
Is the issue specific to certain ROM builds
Is there perhaps a common set of packages in use
Cheers,
Click to expand...
Click to collapse
This issue was reported with my 23034 ROM by a user who syncs with Exchange. I do not sync with Exchange, and my unmodified ROM does not contain the DeviceWipeThreshold key.
There's a thread started by a poster named zimo in the General forum that describes the same issue-I'd link to it except I'm on my fuze. It's several months old, and was just bumped.
Are there any ROMS out there that have working MMS ? I have tried a number of them and no luck. I know these are labors of love but it's such a vital part of the phone itself to be left on the back burner. The only ones it works for me are 2.1 v's 1,2 & 3 every other ROM i tried it's always the same thing, no soft button lights, no trackball lights, no MMS. I've tried every fix offered under the sun & it just doesn't work, OR it might work, 18 hours later.
From what i have read it looks like half the people have no problems & have are in the same boat as me.
any suggestions?
thanks
I use sense-able and have no issues sending or recieving mms msgs
the MMS fix is quite simple. What ROM are you using? I know that in the EE thread there is a link to ivans-apns and instructions on removing your current APNs and installing the APNs from ivans rom.
I have working MMS on every rom I have tried except for one .....
Thanks for the 411 and I must say that name gave me the first laugh for the day "Cornbreadfarts"
Fn Funny dude.
well last night i loaded ZenEXP-Eris_Rev6-fixed_mak, i hadn't seen that one before and it looked very stylish. The overclocking isn't so important but i like the apps2sd. Followed all the instructions including flashing the mms fix also cited in the thread. I should have tried it our right away but i began to get comfy with the rom then when i remembered, bingo, same thing. Attaching even a very small photo gets a generic network error, it'll try 4 times to send it then stop. With other roms, sometimes 18 hours later it'll suddenly go through.
before this I'd tried evil eris, lightning, Dvanilla2fast, vanilladroidv1, fresh 2.1 & aloysius, all with the same result.
every rom has their own little quirks, evileris would seem to stall for a while then suddenly go through all the motions of your frantic thumb presses while u thought there was something wrong. I tried all the solutions offered also with the apn's in the evileris thread but still the same thing
the zenexp seems to restart itself at random times and does not come out of landscape mode after taking a pic. I have to press settings, then back & it resets itself
I like the variety in the various roms and the little extra bells & whistles that the developers add it's just this 1 issue really for me. I don't make a lot of calls and i mostly text back & forth to my daughter in NYC. Recently a loved pet of 13years died but beforehand i couldn't send her any pics of the cat in the days previous.
I guess i'll look for this sense-able and try that. I just don't get it though, we are all using an eris, it should either work or be broken for everyone right ?
heywoood said:
well last night i loaded ZenEXP-Eris_Rev6-fixed_mak, i hadn't seen that one before and it looked very stylish. The overclocking isn't so important but i like the apps2sd. Followed all the instructions including flashing the mms fix also cited in the thread. I should have tried it our right away but i began to get comfy with the rom then when i remembered, bingo, same thing. Attaching even a very small photo gets a generic network error, it'll try 4 times to send it then stop. With other roms, sometimes 18 hours later it'll suddenly go through.
before this I'd tried evil eris, lightning, Dvanilla2fast, vanilladroidv1, fresh 2.1 & aloysius, all with the same result.
every rom has their own little quirks, evileris would seem to stall for a while then suddenly go through all the motions of your frantic thumb presses while u thought there was something wrong. I tried all the solutions offered also with the apn's in the evileris thread but still the same thing
the zenexp seems to restart itself at random times and does not come out of landscape mode after taking a pic. I have to press settings, then back & it resets itself
I like the variety in the various roms and the little extra bells & whistles that the developers add it's just this 1 issue really for me. I don't make a lot of calls and i mostly text back & forth to my daughter in NYC. Recently a loved pet of 13years died but beforehand i couldn't send her any pics of the cat in the days previous.
I guess i'll look for this sense-able and try that. I just don't get it though, we are all using an eris, it should either work or be broken for everyone right ?
Click to expand...
Click to collapse
ZenEXP-Eris doesn't restart itself at random times out-of-the-box, you must have installed or modified something that's causing that error. My releases go through a somewhat rigorous beta testing before they see the light of day - at least since Rev5 - and we've only seen minor issues upon release of them.
As for the accelerometer (the "not coming out of landscape" issue you refer to), that's a known bug in Rev6 that was found after releasing it. It is fixed in Rev7.
At the begining of my ZenEXP-Eris thread, I state that you should read the entire thread twice before flashing. This is so you know what you're doing, what to expect, how to make things work properly and what bugs are present in the ROM. Obviously you didn't read my entire thread, or you would have found the MMS-Fix, which is located about 6 lines below the ROM download
On a side note, Rev7 includes the MMS Fix built right into the ROM, no need to flash the MMS-Fix through Recovery like you do now for Rev5 and Rev6. You'll be able to enjoy Rev7 (hopefully) tomorrow (if not the next day).
-mak
Sorry, I thought I had been clear, I did read the whole thread and did dl & flash the mms fix zip u attached. I'm only reporting on the problems I'm having. This isn't a personal attack on you.
As I said, I understand these are labors of love and I wouldn't report something if it didn't happen. I have had 3 occasions where it restarted itself and all 3 times all I had installed was vignette, meebo, Google translate, shopper & barcode scanner.
Thank you for your reply
-------------------------------------
Sent via the XDA Tapatalk App
heywoood said:
Sorry, I thought I had been clear, I did read the whole thread and did dl & flash the mms fix zip u attached. I'm only reporting on the problems I'm having. This isn't a personal attack on you.
As I said, I understand these are labors of love and I wouldn't report something if it didn't happen. I have had 3 occasions where it restarted itself and all 3 times all I had installed was vignette, meebo, Google translate, shopper & barcode scanner.
Thank you for your reply
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I'm sure it wasn't a personal attack, but I'm not sure why you're telling me that?
Anyway, if you installed the MMS fix, you should have working MMS. The MMS fix hasn't failed anyone that I know of and I used it myself on Rev5 and Rev6. Did you boot into the phone and set it up after flashing the ROM, but before install the MMS fix? The file the MMS fix installs gets overwritten during the first boot, which is why you need to reboot before installing it.
I don't use any of the apps you've installed, so I can't attest to their compatibility with ZenEXP-Eris. What I recommend you do is backup your data, go into Recovery and wipe data/cache/dalvik/ext, then re-install the latest release of Rev6, boot into ZenEXP-Eris and set your phone up, reboot into Recovery and install the MMS fix. Before installing any applications test it all out for a few hours, the proceed to install them one-by-one, leaving an hour or so in between installs until you (possibly) find what is causing the issue.
I'm really sorry to hear this issue persists for you but, as I mentioned earlier, you're the first to report such issues, thus the reason I suspect something else as the culprit
Feel free to PM me for one on one support if you need it.
-mak
edit: Also, regarding your softkey lights, they only turn on in dark areas. Hold your finger over the light sensor to the left of the earpiece speaker to see them light up. In ZenEXP-Eris the jogball LED doesn't function, but I have mapped notifications to the charging/power LED in the upper-right-hand corner of the Eris as an alternative, for now.
heywoood said:
Are there any ROMS out there that have working MMS ? I have tried a number of them and no luck. I know these are labors of love but it's such a vital part of the phone itself to be left on the back burner. The only ones it works for me are 2.1 v's 1,2 & 3 every other ROM i tried it's always the same thing, no soft button lights, no trackball lights, no MMS. I've tried every fix offered under the sun & it just doesn't work, OR it might work, 18 hours later.
From what i have read it looks like half the people have no problems & have are in the same boat as me.
any suggestions?
thanks
Click to expand...
Click to collapse
Hey,
There are several out there that work. Ivans are typically good to go out of the box and most if not all the Sprint based roms will be good to go by using the apn fix. Its a trial and error thing just find a rom that you like and give the thread a good read.
Most all the posted roms now have an mms "fix" or are good out of the box. I know it gets a bit disheartening flashing, setting up, wiping, flashing etc...lol...but thats the joy of a rooted handset...trial and error till you find a rom and dev you like well enough to stick with.
.mak said:
I'm sure it wasn't a personal attack, but I'm not sure why you're telling me that?
Anyway, if you installed the MMS fix, you should have working MMS. The MMS fix hasn't failed anyone that I know of and I used it myself on Rev5 and Rev6. Did you boot into the phone and set it up after flashing the ROM, but before install the MMS fix? The file the MMS fix installs gets overwritten during the first boot, which is why you need to reboot before installing it.
edit: Also, regarding your softkey lights, they only turn on in dark areas. Hold your finger over the light sensor to the left of the earpiece speaker to see them light up. In ZenEXP-Eris the jogball LED doesn't function, but I have mapped notifications to the charging/power LED in the upper-right-hand corner of the Eris as an alternative, for now.
Click to expand...
Click to collapse
I actually did exactly what you said. I downloaded all the files first then i formatted the sd card, toggled, loaded the rom & the mms fix, wiped the handset (reset & dalvik), flashed the rom. When it loaded I set up the phone, power cycled & booted to recovery, flashed the mms fix and restarted the phone.
I wanted to make sure that apps2sd was working to i went to the market & installed vignette (excellent photo app) and the usual google made apps like translate, shopper etc
it was after all this I remembered the mms, so i tried it & nada.
I'm about to reformat & wipe now so i'll see what happens
I've tried EVERYTHING under the sun to get this working.
Here's the deal, my current custom rom, Tesla coil GB is the only thing that lets me add a google account AND connect to Market. Actually, Vicious' MIUI rom works too, but that isn't useable for a phone.
I really want to use BAMF Forever or Cyanogen mod, but every custom rom I throw at my thunderbolt will not connect to the server.
I tried pulling the sim card out and using wifi to connect, I've tried turning on airplane mode and trying to connect, I've tried a factory reset... nothing works.
Getting an account added to the phone isn't the problem here, I can actually do that with the youtube workaround very easily, but even after I do that, every time I try and open the market app, I get an error that flashes up that says "server error" and nothing else, and then crashes when you hit "OK".
I've been sticking with my current rom for a long while because of this infuriating problem. I could really use any help possible. I'm starting to think my phone is defective.
So the problem only occurs with the market? Do other Google products work?
Sent from my HTC ThunderBolt powered by KillaSense 3.0
Yup, only market. Everything else works just fine.
After a quick google, i'm seeing some people saying they didn't have background data enables and it worked once enabled. If it is enabled, disable it, then re-enable it. Others said that worked. Good luck.
I'll give it a shot, as it's nothing I've came across on google for this problem yet.
http://bit.ly/tiTlTf
Sometimes its just different search terms. Thats where i found a ton of them for this. Good luck.
Hello there, I currently encounter a very annoying problem with Google Play, of which solution is nowhere to be found:
1. Using stock ROM, Google Play becomes extremely slow and most of the time not working at all (Network error), while other applications still work well.
2. Everytime I factory reset, it works for about 5 minutes at reasonable speed, then the same problem occurs again.
3. Tried to reverse back to 4.1.1 but nothing changes.
4. Same problem with different WIFI networks and 3G.
5. Jelly Bam (haven't tried other ROMs yet but I believe they would) fixed the problem completely, but its lack of Samsung Apps and other amazing features (like Smart Stay, S Voice, S Note, ...) quickly made me reverse to stock ROM.
After trying every trick found on the internet (reinstall Google Play, clear the cache,...) with no success, and after two days struggling I am now completely exhausted defeated. My only hope is you guys who have had this problem before could help me fix it.
Thanks a trillion.
I recently had a lot of problem signing in, it turned out for some reason my WiFi and phone didn't want to play game with wpa2 but after changing router to just wpa and resetting all working again, I've seen intermittent reports along similar lines sporadically ever since s3 release
Did you try using proxies?
Mr.W0lf said:
Did you try using proxies?
Click to expand...
Click to collapse
No, because I haven't got the faintest idea about that kind of gobbledegook as you well know
Mr.W0lf said:
Did you try using proxies?
Click to expand...
Click to collapse
Yes, I did, soneone suggested 0.0.0.0:8080 but that blocks internet connection to all other applications.
I've discovered that uninstalling Google Play updates will help, but only for 5 minutes or so. After which time the problem persists again.
Now my only solution is to uninstall Google Play updates, (then the app will ask for updating at first run), install some apps as quickly as possible before the connection goes down again. Basically I have to repeat that process every second app downloaded, and that drives me insane!!!
slaphead20 said:
I recently had a lot of problem signing in, it turned out for some reason my WiFi and phone didn't want to play game with wpa2 but after changing router to just wpa and resetting all working again, I've seen intermittent reports along similar lines sporadically ever since s3 release
Click to expand...
Click to collapse
That's interesting but in my case even 3G won't work, and the madness is that Google Play works crazily well in custom ROMs like Jelly Bam and like sh*t in stock ROMs.
crazyfffan said:
That's interesting but in my case even 3G won't work, and the madness is that Google Play works crazily well in custom ROMs like Jelly Bam and like sh*t in stock ROMs.
Click to expand...
Click to collapse
I feel the pain, took me 10 days to finally get mine working, I did everything you did multiple times, exact same scenario, uninstall updates, get a connection, next time I go back to it,bam, no connection, tried different Roms, flashed to stock, everything!
I had something similar.
What I did was adding a second Google account, deleting the first one, log in, adding the first account back, then deleting the second account, and log in again.
Works for me hoops it's working for you.
Verzonden door mijn GT-I9300 met xda premium
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?