Database Users

Unknown error code during application install: "-400"

Hi I have a problem with installing cm themes from Google Play Store. Every time I want to download and install theme I'm getting this error Unknown error code during application install: "-400". Does someone have the same problem or know how to fix it. Please I really want to enjoy cm themes on my Nexus 4. ROM which I use is the last release of Purity+ ROM with hells doctor 2 r19 kernel and standard pa_gapps-stock-4.4.3-20140629-signed. Thank

Second. I have the same error on my Nexus 10 and HTC One S, but not on my Galaxy S4. All running recent CM11 nightly. Here is the relevant logcat from the install:
http://pastebin.com/pvscPk9M
Please not that this issue was present before switching to ART on both devices. I also ran "find / -iname \*tung91\* -delete" as root, but that did not help.

Thank You for your replay. So you say if I hang to ART this problem should be gone? Maybe I will try that but I prefer to not because I use the Xpose plugins and they not working well on ART . I'm also thinking to factory reset my Nexus 4 and flash some other ROM than Purity+ on my phone but the problem is that I have to many data and don't want to lose them all. I know that I can do the backup of my data but don't have space on my internal storage and my laptop is dead so can't copy them anywhere else. I still hope that somebody can help me and know how to fix this stupid issue.

krzwor said:
So you say if I hang to ART this problem should be gone?
Click to expand...
Click to collapse
No! I have this issue regardless of using ART or Dalvik. One can see in the logcat, that I currently use ART, so it would have been a fair option to test if this issue is gone under Dalvik - but I already tested that.
Regardless, a Theme-Dev replied to my mail request yesterday:
Nguyễn Tùng said:
I asked some other dev and themer, they said it's new theme engine bug, hope cm team will fix it soon. Currently we need factory reset to install, it's weird !
Will try to ask some cm dev and tell you if i can found any solution, sorry about the bug
Click to expand...
Click to collapse
I'll keep you posted, if there is anything new.

Thank You for your help I really appreciate. I hope that developers find the way to fix it maybe in another update and finally I can fully enjoy the cm themes without factory reset all my data. Thank You again and please send me a message if there something change with that issue. Cheers

400 errors are from Xposed mods blocking installation and or PA gapps using stock Google apps instead of AOSP gapps like everyone else.
Factory reset only works if it's an Xposed modules issue
Pa gapps will cause it in fresh install
Not a CM issue!
Hope that helps!
DJ

Google play services force close [temp fix]

The only fix is changing location to "DEVICE ONLY". If it still happens after that clear all data associated with "GOOGLE PLAY SERVICES"
Until google does something this is all we got as far as I'm aware. I've tried everything and this is the only reliable thing. Minus reverting versions.

billydroid said:
The only fix is changing location to "DEVICE ONLY". If it still happens after that clear all data associated with "GOOGLE PLAY SERVICES"
Until google does something this is all we got as far as I'm aware. I've tried everything and this is the only reliable thing. Minus reverting versions.
Click to expand...
Click to collapse
Lol my fix is flashing a 5/12 gapps and have no problems whatsoever for the past couple of days.

Is this a bug report for Xposed?

yellowman82 said:
Lol my fix is flashing a 5/12 gapps and have no problems whatsoever for the past couple of days.
Click to expand...
Click to collapse
Do you have a link to those gapps?

crachel said:
Is this a bug report for Xposed?
Click to expand...
Click to collapse
What does xposed have to do with this thread???

using google play services v. 7.5.66 and not a single issue here. you can try downgrading or updating your play services.

michmeister said:
What does xposed have to do with this thread???
Click to expand...
Click to collapse
This looks like a problem with an Xposed module. The posts I highlighted below are all from today and they all have the same problem. If that's the case the thread doesn't belong here. That's why I ask. Troubleshooting problems and not posting your phone's configuration is completely pointless. Hence your confusion as to why I'm asking a valid question followed up immediately by another user who has no problems whatsoever with the Google Play Services in question.
torecdude said:
So iv'e updated the Google app today to 4.6.10.19.arm.
All the sudden Google keep force closing, My google now launcher was a wreck. I coudn't do anything.
I tried wiping cache did not help.
I barely managed to install nova launcher via twrp recovery.
Im using xposed ALPHA for 5.1 and xposed GEL setting.
Stupid update.
I recommend you to avoid this update, i think ill switch to nova permanently.
Click to expand...
Click to collapse
torecdude said:
After i updated google app, i get google FC all the time. I disabled Xposed from recovery and it solved it. probrably having issues with Xposed GEL Settings 2.3.4.
ill try GEL 2.3.6 and report again.
Click to expand...
Click to collapse
mattplo said:
Interesting, I'm running an HTC M8(GPE), latest Xposed, No GEL module but the latest Gravitybox and a few other mods. Latest Google App update FCs. Downgrading allows it to function properly.
Are you running any of the same mods I am? Check screenshot.
Click to expand...
Click to collapse
torecdude said:
Updated my Xposed GEL Settings from 2.3.4 to 2.3.6 Solved my problem. My modules are Ogyoutube , Gel settings, greenify and gravitybox. I had 2.3.4 Gel settings when i first updated google. I had to restore nandroid backup since things got messy for me. Then i updated google again before i had xposed sdk installed on my nexus 6. Flashed the sdk installed GEL without activating the module, everything was until i did activate it. I disabled Xposed installer through TWRP recovery, updated GEL to 2.3.6 and now everything is working perfect for me.
Click to expand...
Click to collapse

crachel said:
This looks like a problem with an Xposed module. The posts I highlighted below are all from today and they all have the same problem. If that's the case the thread doesn't belong here. That's why I ask. Troubleshooting problems and not posting your phone's configuration is completely pointless. Hence your confusion as to why I'm asking a valid question followed up immediately by another user who has no problems whatsoever with the Google Play Services in question.
Click to expand...
Click to collapse
Negative. I and several others have been experiencing this since Wednesday and do not use Xposed. There are many posts in Chroma, Bliss, Benzo with this exact issue.
http://forum.xda-developers.com/showpost.php?p=60902089&postcount=17354

derekr44 said:
Negative. I and several others have been experiencing this since Wednesday and do not use Xposed. There are many posts in Chroma, Bliss, Benzo with this exact issue.
http://forum.xda-developers.com/showpost.php?p=60902089&postcount=17354
Click to expand...
Click to collapse
Have any of the others been totally stock?

crachel said:
Have any of the others been totally stock?
Click to expand...
Click to collapse
No, it doesn't seem as if it is affecting stock.
My guess is that it's bumping up against something in AOSP.

crachel said:
Have any of the others been totally stock?
Click to expand...
Click to collapse
im using stock 5.1 and stock kernel and i had those FC issues. I recommend to anyone having those issues:
1. Disable Xposed via twrp using terminal command like it says right here : http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816
2. Update every module to lastest version.
3. Delete disable file at /data/data/de.robv.android.xposed.installer/conf/ with root explorer to able xposed to work again.
Solved my problem.

derekr44 said:
No, it doesn't seem as if it is affecting stock.
My guess is that it's bumping up against something in AOSP.
Click to expand...
Click to collapse
im using terminus rom, which was updated with the newest code yesterday from aosp, and im using play services v 7.5.65, and i dont have this issue. my guess is that its not aosp code doung it, but other code thats in those roms thats causing the issue.

simms22 said:
im using terminus rom, which was updated with the newest code yesterday from aosp, and im using play services v 7.5.65, and i dont have this issue. my guess is that its not aosp code doung it, but other code thats in those roms thats causing the issue.
Click to expand...
Click to collapse
Yeah. It's really odd. No one really wants to dig deeper into it, but it's definitely a problem with writing/reading the mobile location in memory.

derekr44 said:
Yeah. It's really odd. No one really wants to dig deeper into it, but it's definitely a problem with writing/reading the mobile location in memory.
Click to expand...
Click to collapse
well, im pretty sure its because of code that was recently added to that rom. but which code it is, im clueless.

any update on this???

ticklemepinks said:
any update on this???
Click to expand...
Click to collapse
new banks gapps, flash them

I wish this thread would gain more traction, it saddens me to see my current ROMs thread get saturated by posts about this issue when its been identified that it is not a ROM problem.

morbid_bean said:
I wish this thread would gain more traction, it saddens me to see my current ROMs thread get saturated by posts about this issue when its been identified that it is not a ROM problem.
Click to expand...
Click to collapse
The worst part about this is the new play services work perfectly fine on the stock rom. The only roms that seem to have problems are AOSP based roms. The developers of all of the AOSP roms have said over and over that it's not the rom and that it's the new play services causing the issue. But if play services works fine on the stock rom and not on AOSP roms then how is it play services that's the problem? So that, to me, tells me that it's something that needs either fixed in AOSP source code or something needs changed in the rom config to work with the new play services, right?
I have flashed back and forth like 20 times between stock and AOSP based roms all weekend to test this and I never get the problem on stock. It's always just the AOSP based roms. For now I've managed to stay on chroma with play services 7.3 without it auto-updating, but I'm betting that will be short lived.

sabbotage said:
The worst part about this is the new play services work perfectly fine on the stock rom. The only roms that seem to have problems are AOSP based roms. The developers of all of the AOSP roms have said over and over that it's not the rom and that it's the new play services causing the issue. But if play services works fine on the stock rom and not on AOSP roms then how is it play services that's the problem? So that, to me, tells me that it's something that needs either fixed in AOSP source code or something needs changed in the rom config to work with the new play services, right?
I have flashed back and forth like 20 times between stock and AOSP based roms all weekend to test this and I never get the problem on stock. It's always just the AOSP based roms. For now I've managed to stay on chroma with play services 7.3 without it auto-updating, but I'm betting that will be short lived.
Click to expand...
Click to collapse
again, it was banks gapps, which are fixed now. im on a custom rom as well, terminus, and this issue was never an issue for people using it. but i use an older banks gapps, as do many other users.

simms22 said:
again, it was banks gapps, which are fixed now. im on a custom rom as well, terminus, and this issue was never an issue for people using it. but i use an older banks gapps, as do many other users.
Click to expand...
Click to collapse
can i just flash updated gapps over current gapps or must we wipe?
im on a banks gapps from about a month ago and gps closing just started 2 days ago

Our Device doesn't work with Android keystore?

I tried running the "bitwarden" app without success on omnirom, AICP and paranoid. I was able to get it to work once on AICP but then never able to recreate the scenario or know what was different. When I provided logcats to the developers they came back asking why our device doesn't work with the android keystore. Specifically:
01-23 23:01:06.816 11841 11841 E AndroidRuntime: android.runtime.JavaProxyThrowable: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: The configuration is invalid. Creating the instance for type ISecureStorageService failed. Key not yet valid ---> SimpleInjector.ActivationException: Key not yet valid ---> Java.Security.InvalidKeyException: Key not yet valid
Namely
Java.Security.InvalidKeyException: Key not yet valid
This is the error. For some reason that device doesn't work with the Android Keystore. Any idea why?

I was going to say something about Chinese phones and not having good encryption due to the Chinese government's need to snoop on literally everything, but I don't think that's the case. Have you tried it on other ROMs, namely, stock/official LeEco ROMs? Or eUI? If bitwarden still doesn't work, you ought to contact a veteran dev like codeworkx.

sk8223 said:
I was going to say something about Chinese phones and not having good encryption due to the Chinese government's need to snoop on literally everything, but I don't think that's the case. Have you tried it on other ROMs, namely, stock/official LeEco ROMs? Or eUI? If bitwarden still doesn't work, you ought to contact a veteran dev like codeworkx.
Click to expand...
Click to collapse
In the bug report I opened at bitwarden a second user has reported the same issue with AICP 13.1. I personally tried AICP 12.1, Paranoid Android 7.3.1 and Omnirom 7.x. Oddly I did manage to get it working on AICP 12.1 one time but then was unable to identify what was different or recreate the situation. I did leave a PM for codeworkx identifying the issue since it appears to be a problem on both nougat and oreo. If it's an issue with any app that tries to use encryption in ANY form it could be a big problem. I don't see how that could be the case though since they have android pay working on some roms and it certainly uses encryption in it's processes (or at least I'd think it would).
Bitwarden bug report: https://github.com/bitwarden/mobile/issues/264

That app seems to be working for me, what exactly i should do to reproduce the crash?

voron00 said:
That app seems to be working for me, what exactly i should do to reproduce the crash?
Click to expand...
Click to collapse
Which ROM? Which version of Android? At least provide that information too...

sk8223 said:
Which ROM? Which version of Android? At least provide that information too...
Click to expand...
Click to collapse
Personal build of paranoid, 7.1.2. I don't think i've changed anything related to fscrypt/keystore.

voron00 said:
That app seems to be working for me, what exactly i should do to reproduce the crash?
Click to expand...
Click to collapse
I personally tested the app on Omnirom 7.x, AICP 7.x, and Paranoid Android 7.x.
A 2nd user in the bitwarden bug report stated it crashed for them as well under AICP 13.1 (Android 8.x).
https://github.com/bitwarden/mobile/issues/264
So if you have it working please state Rom, and kernel used .
*update*
Are you using the "stock" kernel in your personal build or one of the available ones like darkobas's or blackscreen?

famewolf said:
I personally tested the app on Omnirom 7.x, AICP 7.x, and Paranoid Android 7.x.
A 2nd user in the bitwarden bug report stated it crashed for them as well under AICP 13.1 (Android 8.x).
https://github.com/bitwarden/mobile/issues/264
So if you have it working please state Rom, and kernel used .
*update*
Are you using the "stock" kernel in your personal build or one of the available ones like darkobas's or blackscreen?
Click to expand...
Click to collapse
I have no idea if it works or not, i never used that app before, but i've created an account, adding passwords, cards, notes works fine, no crashes. Maybe you should clearify what exactly makes an app crash. Is it when you open the app? Or is it when you add something?
The rom is here, you can try and see if it works for you: https://forum.xda-developers.com/showpost.php?p=75333479&postcount=797

voron00 said:
I have no idea if it works or not, i never used that app before, but i've created an account, adding passwords, cards, notes works fine, no crashes. Maybe you should clearify what exactly makes an app crash. Is it when you open the app? Or is it when you add something?
The rom is here, you can try and see if it works for you: https://forum.xda-developers.com/showpost.php?p=75333479&postcount=797
Click to expand...
Click to collapse
I'll give it a try. For me and others the bitwarden app crashes immediately when you try to open it...you never get to actually use it for anything.
I'm currently on the "official" paranoid android 7.3.1 with it crashing like that so will try yours. Hopefully just a drop in replacement.

voron00 said:
I have no idea if it works or not, i never used that app before, but i've created an account, adding passwords, cards, notes works fine, no crashes. Maybe you should clearify what exactly makes an app crash. Is it when you open the app? Or is it when you add something?
The rom is here, you can try and see if it works for you: https://forum.xda-developers.com/showpost.php?p=75333479&postcount=797
Click to expand...
Click to collapse
I just flashed your rom, open gapps 20180123 mini and finally magisk 15.3...booted up and had it start restoring apps from backup...installed bitwarden as one of my first apps and tried to open it...it promptly closed....so tell me what you are doing different please.

famewolf said:
I just flashed your rom, open gapps 20180123 mini and finally magisk 15.3...booted up and had it start restoring apps from backup...installed bitwarden as one of my first apps and tried to open it...it promptly closed....so tell me what you are doing different please.
Click to expand...
Click to collapse
Magisk could be your problem or backups, maybe try without them first. I did nothing unusual really, just downloaded that app from play store and it works, but i don't have root.

voron00 said:
Magisk could be your problem or backups, maybe try without them first. I did nothing unusual really, just downloaded that app from play store and it works, but i don't have root.
Click to expand...
Click to collapse
Are you using open gapps as well? Are you using mini or another version? I'll try it without magisk and without any type of restore.

famewolf said:
Are you using open gapps as well? Are you using mini or another version? I'll try it without magisk and without any type of restore.
Click to expand...
Click to collapse
Im using opengapps stock but i dont think gapps is an issue, most likely root.

voron00 said:
Im using opengapps stock but i dont think gapps is an issue, most likely root.
Click to expand...
Click to collapse
I tried your rom and open gapps..no magisk...no data....did the bare minimum to get to the desktop and installed bitwarden via playstore. It crashed the same as always.
Will download opengapps stock and give it a try.

*deleted*

famewolf said:
I tried your rom and open gapps..no magisk...no data....did the bare minimum to get to the desktop and installed bitwarden via playstore. It crashed the same as always.
Will download opengapps stock and give it a try.
Click to expand...
Click to collapse
@voron00
Tried the unofficial version of paranoid + opengapps stock...nothing else.......connected to my google account...installed bitwarden via play store...it crashes.
Until I can find a 2nd person that says it works for them I have to consider you the lucky one

@voron00
After alot of testing it looks like a clean install of AICP 12.1 is the ONLY rom I personally could use that will let bitwarden work. Titanium Backup can be used to restore user apps and the data for those apps but that's it. Thanks for the information that it was possible to get it to work although I'm still unsure how you got it working on Paranoid Android unless perhaps you restored data from AICP 12.1 that had whatever bitwarden is looking for. Here's hoping android pay works on AICP 12.1. The low volume in calls on AICP is very bad or I'm going deaf..will work on that next.

I got works on AOKP 7.2.1 everything works on this great ROM.
Sent from my LEX727 using xda premium

mchlbenner said:
I got works on AOKP 7.2.1 everything works on this great ROM.
Click to expand...
Click to collapse
How is in call volume and speakerphone? So far the only ones that I found with good in call sound were pixel experience and omnirom.

famewolf said:
How is in call volume and speakerphone? So far the only ones that I found with good in call sound were pixel experience and omnirom.
Click to expand...
Click to collapse
In call is good.
Sent from my LEX727 using xda premium

Gapps Have To Be Included In Custom Roms?

I've been looking at buying the phone since there's a sale going on Amazon for $249USD, but after reading a bit through the forum, seems like custom roms will have gapps preinstalled?
This would be a real deal breaker for me, as I'd like to go microG, Xposed FakeGapps, FakeStore, Fdroid route, Google Free, as much as possible...
But if gapps have to be presinstalled, anyone used Terminal Debloater and uninstalled gapps with it?
Hmm

I dunno about using the rom without gapps, but CarbonRom doesn't come with gapps.
I use it with gapps and its pretty smooth, so I'm assuming it should be the same without it.
CarbonRom also has signature spoofing included.

foueddyf said:
I dunno about using the rom without gapps, but CarbonRom doesn't come with gapps.
I use it with gapps and its pretty smooth, so I'm assuming it should be the same without it.
CarbonRom also has signature spoofing included.
Click to expand...
Click to collapse
I was reading something on XDA over this, not sure now, sounded like because of some issues custom roms had to come with Gapps preinstalled for Essential.
But now you mentioning Carbon without, well, guess that throws that out the window, I hope... LOL
Every custom rom I've installed didn't have any Gapps installed, expect for just a few of the the basics, phone, messenger, calendar...
I never install Gapps, I use microG, Xposed, F-Droid here on my phones, I like to be as Google Free as possible.
Thanks

A lot of the essential (mata) roms have gapps included because it's actually a pain to install it post-install because of the 2 partitions.
So many users get confused and end up flooding the Rom threads with the same questions on how to install gapps.

I thought if they want the Gapps, then people would just pick and choose between the various OpenGapps and flash one in twrp?
hmm

DoR3M3 said:
I thought if they want the Gapps, then people would just pick and choose between the various OpenGapps and flash one in twrp?
hmm
Click to expand...
Click to collapse
Typically, you would do that, but for whatever reason Essential Phone is a lot harder to install gapps on; apparently it's not as easy as flashing in TWRP, I'm not daring enough to mess up the rom install by installing it on my own
My guess is, the partitions really throw a wrench into the equation.
Thanks!

beard805 said:
Typically, you would do that, but for whatever reason Essential Phone is a lot harder to install gapps on; apparently it's not as easy as flashing in TWRP, I'm not daring enough to mess up the rom install by installing it on my own
My guess is, the partitions really throw a wrench into the equation.
Thanks!
Click to expand...
Click to collapse
Is the A/B partitions, that have just come out, pretty much the same on all Android devices?
Because I see on some phones with A/B it seems to all be working easier then then Essential... hmm
Anyone?

DoR3M3 said:
I use an Mi A1 which has A/B partitions, I wonder what is so different about the Essential then?
Anyone?
Click to expand...
Click to collapse
Flash carbon then..it doesn't include them

Can't we all just get along? Lol, @DoR3M3 did you get your phone yet?

I just got one and installed resurrection remix no pre installed gaps

ipatrick123 said:
I just got one and installed resurrection remix no pre installed gaps
Click to expand...
Click to collapse
Nice to hear, carbonrom was mentioned with no gapps...
Are you going to try microG and Xposed on it, if so, let us know how that works out...

DoR3M3 said:
Nice to hear, carbonrom was mentioned with no gapps...
Are you going to try microG and Xposed on it, if so, let us know how that works out...
Click to expand...
Click to collapse
Actually just made a post about a huge issue I am having with Xposed that caused me to need to Uninstall it, but I really need to have it installed so I was asking for suggestions on what to do. As far as microG probably sometime soon I've been customizing the hell out of this phone.
https://forum.xda-developers.com/essential-phone/help/essential-phone-fingerprint-scanner-t3820388

I've had a cleanup in here and I don't want to be returning for more of the same!
If you've got nothing constructive to add to the thread, do not even bother posting here.
If you see that one or more of your posts have been deleted, I'm referring to you!

[Share] OFFICIAL Mokee 9.0 (android pie) nightly non treble for Zte Nubia Z11 nx531j

Until Few Days back i was almost certain that My Z11 will be on android Nougat till its last charge but thanks to our great Devs i was wrong(gladly)
Behold... official Mokee 10.0 for our beloved mighty Nubia Z11
I am sharing this link so that more users can experience it. Make sure you are on twrp given below before installing the rom else it wont boot.
Rom is almost bug free and could be used as daily driver.
Clean install is suggested.
Gapps are not included, please download required pack from: https://opengapps.org/
Rom Download: https://download.mokeedev.com/?device=nx531j
Twrp: https://drive.google.com/open?id=1vZ8_FOGjuYRPHrVIHpYbGKfWZbjhjSYf
Flash audio fix last from twrp
Again none of above ia my work i am just sharing the fabulous work of Great Devs
How to install
1. Download all files mentioned above
2. Put everything in sd card/ otg pendrive
3. Flash the TWRP given above
4. Reboot in TWRP and format data
5. Wipe System, Data, Dalvik & cache
6. Flash Rom then Gapps
7. Reboot and enjoy your Z11
Edit: Audio is fixed now, some users suggested that battery performance is slightyy better now.

Vi7eta said:
Few Days back i was almost certain that My Z11 will be on android Nougat till its last charge but thanks to our great Devs i was wrong.
Behold... official Mokee 9.0 for our beloved mighty Nubia Z11
I am sharing this link so that more users can feast upon it. Make sure you are on twrp given below before installing the rom else it wont boot.
Rom is released Recently and its a nightly build still.. Other then Audio bug (fix will be found below) and broken IR (no fix yet) haven't found any issue in last 24 hours Rom is almost bug free and could be used as daily driver.
Clean install would be suggested.
Gapps are not included, please download required pack from: https://opengapps.org/
Rom Download: https://download.mokeedev.com/?device=nx531j
Audio Fix: https://androidfilehost.com/?fid=1395089523397917582
Twrp: https://drive.google.com/open?id=1vZ8_FOGjuYRPHrVIHpYbGKfWZbjhjSYf
Flash audio fix last from twrp
Again none of above ia my work i am just sharing the fabulous work of Great Devs
How to install
1. Download all files mentioned above
2. Put everything in sd card/ otg pendrive
3. Flash the TWRP given above
4. Reboot in TWRP and format data
5. Wipe System, Data, Dalvik & cache
6. Flash Rom then Gapps and lastly audio fix
7. Reboot and enjoy your Z11
Click to expand...
Click to collapse
Thank you for sharing , would you mind to give a quick Guide
on how to flash Trwp , i have never flashed anythink but Stock
Roms on that Device .
Thanks in advanced !

fares70 said:
Thank you for sharing , would you mind to give a quick Guide
on how to flash Trwp , i have never flashed anythink but Stock
Roms on that Device .
Thanks in advanced !
Click to expand...
Click to collapse
Go through this page, you will find everything you are looking for.
https://4pda.ru/forum/index.php?s=&showtopic=782022&view=findpost&p=60483845

Be cautious if you flash Mk90.1 2019318, an user got bootloop.

I flashed the latest Mokee (19/03) with Micro Gapps for Android 9.0 and it seems to work fine.
The only problem I have is that the power button launches the camera and there's no way to disable this annoying feature.

valorien said:
I flashed the latest Mokee (19/03) with Micro Gapps for Android 9.0 and it seems to work fine.
The only problem I have is that the power button launches the camera and there's no way to disable this annoying feature.
Click to expand...
Click to collapse
Settings>system>gesture>jump to camera>off
Lemme know if the annoyong feature still persists.

Vi7eta said:
Settings>system>gesture>jump to camera>off
Lemme know if the annoyong feature still persists.
Click to expand...
Click to collapse
That solved it! thank you so much! It was driving me crazy all day.
Have you encountered any other issues with the ROM? I'm seeing random shutdowns/black screen every now and then.
Guess it's still unstable.

valorien said:
That solved it! thank you so much! It was driving me crazy all day.
Have you encountered any other issues with the ROM? I'm seeing random shutdowns/black screen every now and then.
Guess it's still unstable.
Click to expand...
Click to collapse
After every manual reboot it shuts itself off once but after force power on it stays on, if you use pin/password then do this..
after reboot give 1 second pause between entering each digit and let it settle for a minut.
Yes its still in beta but its the best thing till date Z11 got.
Even Nubia coudnt/woudnt offer 2 major update but our devs give it a new lease of life.

Vi7eta said:
After every manual reboot it shuts itself off once but after force power on it stays on, if you use pin/password then do this..
after reboot give 1 second pause between entering each digit and let it settle for a minut.
Yes its still in beta but its the best thing till date Z11 got.
Even Nubia coudnt/woudnt offer 2 major update but our devs give it a new lease of life.
Click to expand...
Click to collapse
Unfortunately, it still randomly shuts down or resets.
I'm appreciative of the fact that someone put time and effort to develop this ROM, but it's just too buggy at the moment to serve as a real alternative.
Users at the 4PDA forum (where this ROM originates from) report similar issues.
In the meantime, I'm going back to 3.06.

valorien said:
Unfortunately, it still randomly shuts down or resets.
I'm appreciative of the fact that someone put time and effort to develop this ROM, but it's just too buggy at the moment to serve as a real alternative.
Users at the 4PDA forum (where this ROM originates from) report similar issues.
In the meantime, I'm going back to 3.06.
Click to expand...
Click to collapse
As i mentioned its in beta i too am using it as my secondary driver.
Though i havent faced random shut downs but i apreciate you tried the rom and reported the issues.
Please share exact steps you took while flashing mokee.

Thank you, I am using it now, very good rom

洛父110 said:
Thank you, I am using it now, very good rom
Click to expand...
Click to collapse
Good to hear that you having a great ride with mokee.

im getting error:7 in twrp mine is 128+6gb signature gold edition and i really dont know what to do
i need help

Basically there is no restart now, it can be used daily, very good work.

SolidSnake140 said:
im getting error:7 in twrp mine is 128+6gb signature gold edition and i really dont know what to do
i need help
Click to expand...
Click to collapse
Did you flash mentioned twrp first?
If yes then re-download the rom file and try again, it should work.

Vi7eta said:
Did you flash mentioned twrp first?
If yes then re-download the rom file and try again, it should work.
Click to expand...
Click to collapse
actually i did not, i have a twrp 3.0.2.0 i will update it but idk it should have the same functionality after all its a recovery , what will change if i didnt update ?

SolidSnake140 said:
actually i did not, i have a twrp 3.0.2.0 i will update it but idk it should have the same functionality after all its a recovery , what will change if i didnt update ?
Click to expand...
Click to collapse
twrp 3.0.2.0. dosent support pie.

battery performance?
洛父110 said:
Thank you, I am using it now, very good rom
Click to expand...
Click to collapse
how is the battery performance, compared to the official ROM?

Good rom no hanging but it's over heating in gaming and getting shut down when gaming under 40 battery

jdigra said:
how is the battery performance, compared to the official ROM?
Click to expand...
Click to collapse
Almost same. Although depends on usage.. You might want to try it for yourself to get exact results.