Edit: this kernel merged a fix for newer 8 pros with different hardware, i personally tested it and works!
https://forum.xda-developers.com/on...late-1-0-0-t4096065/post83613489#post83613489
Big thanks to @tbalden for his efforts
Hi! This thread is meant to gather all the cases we can for study the following problem:
Fingerprint scanner completely dissapear from the phone.
Of course i dont mean phisically, but ROM will not recognize that there is a Fingerprint scanner on the phone.
You will not have Fingerprint options on the settings menu, and of course, no Fingerprint icons or unlock options. Just PIN and face unlock.
In my case (and some other users) this happens after flashing ANY custom kernel. After reboot ALL FP options are gone.
Another user reported this same behaiviour but flashing a custom ROM. (It is a more complex context. But same exactly thing).
Please leave the following details if you report as i do with mine:
My device Details:
Device oneplus 8 pro in2023
Rom: 10.5.13in11aa
In my case, phone was bought two weeks ago from amazon.
Behaiviour:
After flash any custom kernel, FP will just dissapear like there was no Fp scanner on the phone. No options in settings, nothing.
Reverting back to stock brings everything back to normal.
I would like to keep this thread open for devs and users for discussion about THIS specific problem. Persist corruptions has its own threads and different symptons. I am interested though to check if any user had BOTH corrupt persist (enrollment error) and no FP at all issues. Of course not at the same time, as it wouldn't be possible to have both.
I want to thank
elmarian756 said:
Hi! Decided to start this thread since i cant install any custom kernel without the FP scanner hardware fails to start. I have seen other users complain about this and some devs bringing theories to the table about new units and different FP hardware and outdated kernel sources.
Details:
Device oneplus 8 pro in2023
Rom: 10.5.13in11aa
In my case, phone was bought two weeks ago from amazon.
Behaiviour:
After flash any custom kernel, FP will just dissapear like there was no FS on the phone. No options in settings, nothing.
Reverting back to stock brings everything back to normal.
I would like to keep this thread open for devs and users for discussion about THIS specific problem. Persist corruptions has its own threads.
Click to expand...
Click to collapse
Reverting back to stock you mean also unrooted?...
And using stable magisk without any magisk module?..
cultofluna said:
Reverting back to stock you mean also unrooted?...
And using stable magisk without any magisk module?..
Click to expand...
Click to collapse
No, i mean just going back to stock kernel, keeping root. And yes, no modules, standard magisk 20.4 stable
elmarian756 said:
No, i mean just going back to stock kernel, keeping root. And yes, no modules, standard magisk 20.4 stable
Click to expand...
Click to collapse
xXx or another rom?..
Your issue is weird
cultofluna said:
Reverting back to stock you mean also unrooted?...
And using stable magisk without any magisk module?..
Click to expand...
Click to collapse
cultofluna said:
xXx or another rom?..
Your issue is weird
Click to expand...
Click to collapse
No mods, just magisk stable 20.4 and nothing else. Some other user reported the same too, maybe this thread will bring others with the same problem in the future
elmarian756 said:
No mods, just magisk stable 20.4 and nothing else. Some other user reported the same too, maybe this thread will bring others with the same problem in the future
Click to expand...
Click to collapse
Do you remember which kernel was the first one that gave you this problem?..
cultofluna said:
Do you remember which kernel was the first one that gave you this problem?..
Click to expand...
Click to collapse
weird, yes. maybe do the additional step of 'format data' as part of a reset ? ? . . . . be sure to save all your stuff to your pc first.
Yep, backup for a safety net...
elmarian756 said:
Behaiviour:
After flash any custom kernel, FP will just dissapear like there was no FS on the phone. No options in settings, nothing.
Reverting back to stock brings everything back to normal.
Click to expand...
Click to collapse
Same behaviour here on recent IN2020. Stock OxygenOS is OK. Tried lineageos and no FP sensor, or even an option to enroll fingerprint.
@DJ said:
Same behaviour here on recent IN2020. Stock OxygenOS is OK. Tried lineageos and no FP sensor, or even an option to enroll fingerprint.
Click to expand...
Click to collapse
But in stock OOS using another kernel FP works OK?
If so, we have different problems but probably due to the same cause. I dont use custom roms but custom kernel
elmarian756 said:
But in stock OOS using another kernel FP works OK?
Click to expand...
Click to collapse
No idea, never tried. Kernel in https://forum.xda-developers.com/oneplus-8-pro/development/rom-lineageos-17-1-t4122983 causes same symptoms on my IN2020. Your guess of different hardware sounds reasonable.
@DJ said:
No idea, never tried. Kernel in https://forum.xda-developers.com/oneplus-8-pro/development/rom-lineageos-17-1-t4122983 causes same symptoms on my IN2020. Your guess of different hardware sounds reasonable.
Click to expand...
Click to collapse
This is very interesting. Clearly there are not many users experiencing this. Will edit the thread to include your case as well. So anyone with no FP options or read can be included. A propper dev needs to look to the kernel sources, maybe something IS different. Especially with this device and its enrollment FP issues. Have you ever encounter enrollment or corrupt persist before?
Same thing happenes to me for all kernels. Using IN2020 new device manufactured in August.
Try this kernel for android 10 with backported fix from beta sources:
https://forum.xda-developers.com/showthread.php?p=83613489
Reportedly fixes the issue
@DJ said:
Same behaviour here on recent IN2020. Stock OxygenOS is OK. Tried lineageos and no FP sensor, or even an option to enroll fingerprint.
Click to expand...
Click to collapse
Can confirm the same stuff here on my IN2020.
elmarian756 said:
This is very interesting. Clearly there are not many users experiencing this. Will edit the thread to include your case as well. So anyone with no FP options or read can be included. A propper dev needs to look to the kernel sources, maybe something IS different. Especially with this device and its enrollment FP issues. Have you ever encounter enrollment or corrupt persist before?
Click to expand...
Click to collapse
Tried moving between different custom ROMs and stock ROMs with different kernels, tried flashing stock A10/11 with MSM, but no corruption of persist partition.
tbalden said:
Try this kernel for android 10 with backported fix from beta sources:
https://forum.xda-developers.com/showthread.php?p=83613489
Reportedly fixes the issue
Click to expand...
Click to collapse
Flashing CleanSlate kernel with FP fix didn't help too.
Related
Hey there, proud owners of Redmi Note 3 Pro. Since, there are two cm13 variants, both currently under development, so I decided to start this thread, to compare both variants and help other users to decide which to flash. And, if they mess up or want to revert back or any other problem occurs, help them and guide them through the whole process.
I want other people to participate to and list the pros and cons of both the roms with their respective version name. It will help others to decide better about which rom to flash and all.
WARNING: By flashing the new/updated firmware, you might have trouble going back to miui7 based on 5.1.1. I tried flashing fastboot stable rom, and I was having wifi, no sime, etc issues. And when flashing CM13 again, the issue were resolved. This is because of the firmware change.
For those who are also having no sim/wifi issues on miui7 after flashing fastboot or recovery rom, do not immediately come to confusion that you have lost your imei or efs partition, try going back to CM13 to check whether the issues still exist or not.
ADVICE: Make a complete backup of your miui rom using twrp alka. NOTE: Official twrp will not help you create the backup of every single patition, so please download and flash twrp alka as your recovery. Even if you don't want to make a backup, I ADVICE you to backup atleast efs partition, it may come handy later.
Nope...You can restore the splash image from your previous mm backup to get MI spalsh image. eace:
Sent from my Redmi Note 3 using Tapatalk
CM13 by Santhosh M
Build date: 17 - 06 - 2016
1. Minor bluetooth related bugs.
2. Slow gps. But it works.
3. Some force close issues.
4. LED notification settings error. Led are working, only they seems to ignore the manual settings.
5. Other small things i may have not noticed.
There may or may not be camera force close, the patch for it is uploaded right below the downloading link in his thread. Everything thing else seems to be fine. The firmware/radio is from a leaked source and thus a bit unstable and may cause some problems. If it causes problems, flash some other Android M based radio for redmi note 3 pro. Make sure not to flash radio from some other device, you may end up getting bricked or loosing your imei.
HTML:
http://forum.xda-developers.com/redmi-note-3/development/rom-cyanogenmod-13-0-xiaomi-redmi-note-3-t3350656
Build by banmeifyouwant & thestrix
Build date: 19 - 06 - 2016
Bugs:
1. Wrong bluetooth address and mac address.
2. Some bluetooth services that i may have not noticed.
3. Some force close issues that can be solved by wiping the data/cache of the app or cache from recovery.
The rest seems be good. GPS working. Voice recognition in google app working. No com.android.phone force close. No music force close. If you have some problems, then flash the radio package after flashing the rom.
HTML:
http://forum.xda-developers.com/redmi-note-3/development/cyanogenmod-13-t3398789
Another bug in cm ROMs. Music app force closes if u have more than 250+ songs listed in ur music app.
Just tested by me. I had more songs and I was getting FCS. Just to verify, I created .nomedia file in some folders and music player plays well.
Some one needs to fix it. I tested with cm13 by banmelfyouwant and mokee.
Sent from my SHIELD Tablet using XDA-Developers mobile app
srihari210 said:
Another bug in cm ROMs. Music app force closes if u have more than 250+ songs listed in ur music app.
Just tested by me. I had more songs and I was getting FCS. Just to verify, I created .nomedia file in some folders and music player plays well.
Some one needs to fix it. I tested with cm13 by banmelfyouwant and mokee.
Sent from my SHIELD Tablet using XDA-Developers mobile app
Click to expand...
Click to collapse
I have exactly 589 songs and no fc in music app. If you are having fx, clear cache and dalvik and then try again.
This thread is not in the correct section.
Polls, Guides, Tips and Tricks should reside in General category.
Please refrain from creating such threads in the development section.
I have been noticing a lot of such threads here.
Cheers.
dagger said:
This thread is not in the correct section.
Polls, Guides, Tips and Tricks should reside in General category.
Please refrain from creating such threads in the development section.
I have been noticing a lot of such threads here.
Cheers.
Click to expand...
Click to collapse
Sorry about that, i am new at XDA and thus didn't knew on which section to post this, so i just posted it under snapdragon section. I didn't know this section was reserved for just development reason only.
Even Flour_Mo rom is highly stable with everthing working
http://www.miui.com/thread-4341855-1-1.html
June 7 build
What are the bugs in Santhosh's build?
Does GPS work in his build?
jain_pranav said:
What are the bugs in Santhosh's build?
Does GPS work in his build?
Click to expand...
Click to collapse
Yes gps works, but somebody complained that it was slow in his latest built 17
I have been using banmeifyouwant build. It's very smooth but GPS is an issue for me. Will be shifting to Santhosh's build now.
archit.bajpai.ab said:
Yes gps works, but somebody complained that it was slow in his latest built 17
Click to expand...
Click to collapse
The BanMeIfYouWant build would crash/reboot when I tried to use the gps for navigation.
I switched back to Santhosh's latest and the gps was slow. It wouldn't lock at first, but after 5-10 minutes I was able to connect and haven't had an issue connecting since.
Santhosh's build is more stable in my opinion, so that's what I recommend.
Yaranaika said:
The BanMeIfYouWant build would crash/reboot when I tried to use the gps for navigation.
I switched back to Santhosh's latest and the gps was slow. It wouldn't lock at first, but after 5-10 minutes I was able to connect and haven't had an issue connecting since.
Santhosh's build is more stable in my opinion, so that's what I recommend.
Click to expand...
Click to collapse
Can you list all the pros and cons of that rom here. It would really help other to know what they will get when they flash
archit.bajpai.ab said:
both the roms use MM bootloader
Click to expand...
Click to collapse
I use the userdebug bootloader form the leaked CAF rom. :silly:
jain_pranav said:
What are the bugs in Santhosh's build?
Does GPS work in his build?
Click to expand...
Click to collapse
Yeah his build is very much stanle. The only downgrade is that you will lose 4k recording that is only available in banmeifyouwant built
archit.bajpai.ab said:
Yeah his build is very much stanle. The only downgrade is that you will lose 4k recording that is only available in banmeifyouwant built
Click to expand...
Click to collapse
No, 4K recording also working on another CM13 ROM, it's made by TheStrix and you know, he's currently working with our device for the real Official CM13.
MOVZX said:
No, 4K recording also working on another CM13 ROM, it's made by TheStrix and you know, he's currently working with our device for the real Official CM13.
Click to expand...
Click to collapse
Glad to hear. I still can't understand why banmeifyouwant a d santhosh are working seperately for the same goal. Shouldn't they be working together for the official cm13, that way the updates will be made faster.
banmeifyouwant said:
I use the userdebug bootloader form the leaked CAF rom. :silly:
Click to expand...
Click to collapse
So, you rom is technically not using the mm bootloader, instead its more like custom one.
And one more thing. Why you and santhosh are working differently on the same rom. Wouldn't it be better to merge both and hence release a more better rom. If you both can work diiferently and create such a rom in a nich of time, then if you work together, you both can create a perfectly stable rom in no time.
MOVZX said:
No, 4K recording also working on another CM13 ROM, it's made by TheStrix and you know, he's currently working with our device for the real Official CM13.
Click to expand...
Click to collapse
Where did you get this build?
Sent from my kenzo using Tapatalk
Yo i search the best rom and kernel for the G model
Not really sure man. I think its up to you to test them out and see which one gives you the best battery performance for your needs.
Yough said:
Yo i search the best rom and kernel for the G model
Click to expand...
Click to collapse
Just use Lineage with a totally black Substratum theme and Llama Sweet EAS kernel
Thanks for your advice, I had no big needs I just watch videos on Netflix ^^
Choose an username... said:
Just use Lineage with a totally black Substratum theme and Llama Sweet EAS kernel
Click to expand...
Click to collapse
Can you confirm that this is working? I've been wanting to use a black substratum theme for ages, but until now I didn't dare to, since substratum doesn't officially support LineageOS as far as I know. On top of that I read a couple of comments of people having issues
|Furō| said:
Can you confirm that this is working? I've been wanting to use a black substratum theme for ages, but until now I didn't dare to, since substratum doesn't officially support LineageOS as far as I know. On top of that I read a couple of comments of people having issues
Click to expand...
Click to collapse
You're right, but I meant LineageOS as in an LOS-based ROM more than LOS itself. Most custom ROMs run better than LOS and have a bunch of features.
You may know that Substratum uses "OMS" to do the overlay stuff, so if you want a ROM with full substratum compatibility, it's as easy as finding one with the necessary commits, like NucleaROM or RR (I prefer NucleaROM over all of the other LOS-based ROMs to be honest). Just look at the description of the ROM for 'oms support'. Or you can try, I'm sure that I used Substratum on LineageOS stock for some time and I was getting 7 hrs SOT with heavy usage
Choose an username... said:
You're right, but I meant LineageOS as in an LOS-based ROM more than LOS itself. Most custom ROMs run better than LOS and have a bunch of features.
You may know that Substratum uses "OMS" to do the overlay stuff, so if you want a ROM with full substratum compatibility, it's as easy as finding one with the necessary commits, like NucleaROM or RR (I prefer NucleaROM over all of the other LOS-based ROMs to be honest). Just look at the description of the ROM for 'oms support'. Or you can try, I'm sure that I used Substratum on LineageOS stock for some time and I was getting 7 hrs SOT with heavy usage
Click to expand...
Click to collapse
Alright, so thats how it is. But you say you had it running on LOS? Did you experience issues, or why don't you have it running anymore? To be honest I would currently prefer not flashing a new rom, since I'm kinda dependent on my phone working right now and at the moment, it works mostly fine would still love to use a totally black substratum theme though
|Furō| said:
Alright, so thats how it is. But you say you had it running on LOS? Did you experience issues, or why don't you have it running anymore? To be honest I would currently prefer not flashing a new rom, since I'm kinda dependent on my phone working right now and at the moment, it works mostly fine would still love to use a totally black substratum theme though
Click to expand...
Click to collapse
You have LOS on your phone though, right? If so, why don't you try? It's not like you have to flash anything so you can't brick your phone...
I think I used it on LOS yeah. But I prefer stock over custom ROMs by far. And now that the MiFavor 5 ROM is out (with the Android 7 QS tiles) I don't have any reason to use the buggy and laggy custom ROMs
I swear LOS was the worst of them all when I used it back in Feb/March. The worst thing was that a bunch of apps simply didn't feel like working...
Choose an username... said:
You have LOS on your phone though, right? If so, why don't you try? It's not like you have to flash anything so you can't brick your phone...
I think I used it on LOS yeah. But I prefer stock over custom ROMs by far. And now that the MiFavor 5 ROM is out (with the Android 7 QS tiles) I don't have any reason to use the buggy and laggy custom ROMs
I swear LOS was the worst of them all when I used it back in Feb/March. The worst thing was that a bunch of apps simply didn't feel like working...
Click to expand...
Click to collapse
Yes I do. Personally I don't feel like it's that bad so you think it's save to try it out?
Hmm so you feel like stock is better right now? I switched to LOS because I was kinda mad at the stock rom (at least the German one) since updates weren't coming at promised times and when they did come they were full of bugs like apps not working and more.... Which was mostly fixed afterwards, but I wasn't that happy with the situation. I also didn't like the look and feel, which now wouldn't be as much of a problem, since I'm using Nova + KLWP to change most of the visuals. Is the "Tiles-App" with more QS tiles working with stock now? It didn't when I went to LOS. How's battery life? What are your main reason to go back to stock?
And least but not last.... How would I get back to stock? Just flashing a zip from the ZTE website?
And another weird thing which didn't bother me too much until now: I bought my phone in Germany so I had the G model. Ever since going to LineageOS, which included unlocking the boot loader etc. My phone tells me /shows up as the U model.... Is that bad in any way? Other than that it seems to work alright though
|Furō| said:
Yes I do. Personally I don't feel like it's that bad so you think it's save to try it out?
Hmm so you feel like stock is better right now? I switched to LOS because I was kinda mad at the stock rom (at least the German one) since updates weren't coming at promised times and when they did come they were full of bugs like apps not working and more.... Which was mostly fixed afterwards, but I wasn't that happy with the situation. I also didn't like the look and feel, which now wouldn't be as much of a problem, since I'm using Nova + KLWP to change most of the visuals. Is the "Tiles-App" with more QS tiles working with stock now? It didn't when I went to LOS. How's battery life? What are your main reason to go back to stock?
And least but not last.... How would I get back to stock? Just flashing a zip from the ZTE website?
And another weird thing which didn't bother me too much until now: I bought my phone in Germany so I had the G model. Ever since going to LineageOS, which included unlocking the boot loader etc. My phone tells me /shows up as the U model.... Is that bad in any way? Other than that it seems to work alright though
Click to expand...
Click to collapse
-I like stock because it runs better, and even though I thought I would hate ZTE's UI, I actually like it after using it for a long time. And the 5.0 UI is awesome, nuff said. They use blur on the volume pop-up and when you pull down the status bar.
MiFavor 5.0 is not official, it's just the A2017 ROM that's been ported by the Russians. You need to install a special A2017 bootstack (it seemed really dangerous but it's not that bad really) and then the system zip, which formats /system anyways. After that you have to format /data (which will format the internal storage too, just saying) because of the encryption, and it should boot just fine.
I have an A2017G too and flipped out when they f00ked up with B02 with Google Play Store, then B03 with exfat, and went to LOS. Then i tried to go back and DFU-bricked my phone. After I fixed it I preferred to stay stock, and in B04 they fixed everything there was to fix. Tried NucleaROM, best so far but it still has that WIP feel...
Anyways, make a backup of your current system on an SD card if you want to go 5.0.
The A2017U thing is normal, it's because the universal bootloader is actually the U bootloader without the NON-HLOS.bin which you flash later via the A2017G-MODEM.zip (which is ancient lol)
Thank you again for your aid! I have another question....
I downloaded substratum now and installed some themes but somehow I can't get them to work...
For example "Flux" tells me everything went good and I need to restart, but nothing changes after the reboot...
Swift Black has some errors compiling :/
Any ideas?
|Furō| said:
Thank you again for your aid! I have another question....
I downloaded substratum now and installed some themes but somehow I can't get them to work...
For example "Flux" tells me everything went good and I need to restart, but nothing changes after the reboot...
Swift Black has some errors compiling :/
Any ideas?
Click to expand...
Click to collapse
well, it's not working with LOS then. I guess I used it on RR
Choose an username... said:
well, it's not working with LOS then. I guess I used it on RR
Click to expand...
Click to collapse
Alright thank you! How did RR compare to LOS?
|Furō| said:
Alright thank you! How did RR compare to LOS?
Click to expand...
Click to collapse
Okay but laggy. again, I prefer NucleaROM, you should check that one if you'll change ROMs
Choose an username... said:
Okay but laggy. again, I prefer NucleaROM, you should check that one if you'll change ROMs
Click to expand...
Click to collapse
I will thank you! You are awesome! So I can just flash that rom over LineageOS? Or do I have to wipe my phone first?
|Furō| said:
I will thank you! You are awesome! So I can just flash that rom over LineageOS? Or do I have to wipe my phone first?
Click to expand...
Click to collapse
The best would be wiping everything, but you can try wiping system only. after that if the phone doesn't work well just wipe data
It seems to be that all the ROMs have bugs or are laggy. Stock is best right now if my research is correct.
Stock...
Edit* with a few things added and removed...
So I am running Nuclear Ron now, everything went smoothly and I've got Magisk installed correctly for root access. So far when I'm using the rom I love everything and substratum works well as well.....
But.... Whenever I turn of the screen it almost immediately reboots... when using my phone I don't get any random reboots, but when the screen is off it restarts every time. This is a real bummer and I keep my phone off most of the time right now, to prevent the reboots every minute :/
Any ideas what the reason for this issue could be? Would love to stay with this rom, but only if I can get this fixed!
I Uninstalled substratum and the substratum themes by the way, but that didn't help either...
Any help is greatly appreciated! Thanks in advance!!
I get phenomenal battery life and speed on NucleaROM. Stability is so-so, however.
Hi all,
Looked around forum but can't find up to date recommendations...
I'm looking to take the plunge into custom, non-stock-based roms and I was wondering if anyone could recommend a good ROM that is totally bug free, preferably Nougat?
Thanks in advance :highfive:
https://forum.xda-developers.com/xperia-z2/development/7-x-x-carbonrom-cr-5-1-t3655016
Samir2298 said:
https://forum.xda-developers.com/xperia-z2/development/7-x-x-carbonrom-cr-5-1-t3655016
Click to expand...
Click to collapse
Totally bug free?
no rom in any phone is "totally bug free"
Not even stock lol
Samir2298 said:
no rom in any phone is "totally bug free"
Click to expand...
Click to collapse
I beg to differ!
What I mean is: a ROM that is as stable as and has same functionality as the stock ROM ( though I am aware that I lose DRM features with UB).
tooplanx said:
I beg to differ!
What I mean is: a ROM that is as stable as and has same functionality as the stock ROM ( though I am aware that I lose DRM features with UB).
Click to expand...
Click to collapse
Carbon rom is good for you and its the most updated
But all of nought roms almost share same bugs that some users reports
I myself didn't have a single problem using Carbon,LOS,RR
but as i said carbon is the most updated
I've just discovered that my phone has the "Bootloader unlock allowed: No" in the system configuration menu, so it looks like I can't unlock...
Is there any new way around this?
What happened to the LineageOS ROM?
https://forum.xda-developers.com/xperia-z2/orig-development/rom-lineageos-14-1-sirius-t3577518
Anyone know?
MWPau said:
What happened to the LineageOS ROM?
https://forum.xda-developers.com/xperia-z2/orig-development/rom-lineageos-14-1-sirius-t3577518
Anyone know?
Click to expand...
Click to collapse
It was discontinued , you can either switch to carbon or rr
tooplanx said:
I've just discovered that my phone has the "Bootloader unlock allowed: No" in the system configuration menu, so it looks like I can't unlock...
Is there any new way around this?
Click to expand...
Click to collapse
nope, you can still use extistienz
opendata said:
It was discontinued , you can either switch to carbon or rr
Click to expand...
Click to collapse
Well, yeah, but why?
It's rather odd it disappeared with no notice, the thread closed, and the image files removed.
Almost as if something nasty was happening behind the scenes
Im still using the latest version of it, and i really have no reason to change since it works great.
But im left wondering if i should change because they may be something nefarious in the code or something similar?
I've been pondering the same thing.
Currently I'm on the 23.5.A.1.291 version, it works but is vulnerable to some of the exploits which have surfaced since that was built by Sony.
I use the Sony SBH54 bluetooth headset with it, if I go for a custom ROM I suspect I might have some problems with it. It mostly works now but isn't bug free by any stretch of the imagination, it will lose connection and reconnect as it pleases. Most irritating.
If I go down the unlocked bootloader path I'll lose the DRM _stuff_ for the camera but I've not got a good idea of how much difference that makes.
I've not run a custom ROM on my main phone, always on tablets and experimental things and none of them are Sony with it's extra quirks, I'm thinking the TA partition here.
How many of you use non-stock on your primary devices?
What problems do you encounter?
On my tablet I've lost data a few times as I've tried something which didn't work, I don't want that to happen on my phone!
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
Hi. What's the most current pixel C rom that doesn't have any bugs or other issues? Looking to move away from stock but last I checked some of the roms had some bugs still. Is that still the case?
Lineage 17.1 is pretty smooth, camera crashes after ~30mins of video but I mean that's a lot, reboot fixes that. Sometimes on boot you have to wait ~2mins before unlock pattern will work if you want to secure it. Other than that, butter
Sent from my Pixel 4 using Tapatalk
tabormeister said:
Lineage 17.1 is pretty smooth, camera crashes after ~30mins of video but I mean that's a lot, reboot fixes that. Sometimes on boot you have to wait ~2mins before unlock pattern will work if you want to secure it. Other than that, butter
Sent from my Pixel 4 using Tapatalk
Click to expand...
Click to collapse
Thanks. Looking into it. Not an easy thing to do for a semi-beginner. Will have to do more research on how to get it done. Want to be careful not to brick the device.
Sequoia1321 said:
Thanks. Looking into it. Not an easy thing to do for a semi-beginner. Will have to do more research on how to get it done. Want to be careful not to brick the device.
Click to expand...
Click to collapse
Eh, bricking a Google device is pretty hard. Easiest thing is unlock it (enable oem unlocking) then flash twrp from fastboot (need a Linux liveboot or mac system to do that) then flash the rom+gapps. twrp should let you mount usb storage but if not you can adb 'em over, there's install instructions for all of those things in the requisite threads
Sent from my Pixel 4 using Tapatalk
Sequoia1321 said:
Hi. What's the most current pixel C rom that doesn't have any bugs or other issues? Looking to move away from stock but last I checked some of the roms had some bugs still. Is that still the case?
Click to expand...
Click to collapse
LINEAGE 18.0 is here with Android 11! Check out @followmsi 's thread for Dragon.
Alxoom33 said:
LINEAGE 18.0 is here with Android 11! Check out @followmsi 's thread for Dragon.
Click to expand...
Click to collapse
Looks like it's not fully stable yet, if that's the right term. Says encryption not tested. I tried looking into installing Lineage 17.1 as tabormeister mentioned earlier in the thread, but couldn't find an easy how to guide. It's been a while since I've installed a custom rom. Do you know where I can get easier info about how to install it?
Sequoia1321 said:
Do you know where I can get easier info about how to install it?
Click to expand...
Click to collapse
Hey, what's rom currently installed on your device?