Related
Earlier today I was mucking about and decided to play around with the fingerprint scanner for the first time. When I went in to settings and clicked the fingerprint manager, I received an error stating that the scanner is borked, and to reset my device to fix it. Rebooting did not fix the issue.
Soon I found another person with the same issue, who said that he was able to fix it by flashing stock NJ7 via Odin. After a bit of chatter we realized that neither he nor I had set up the fingerprint scanner before flashing a ROM. We basically booted the phone and went straight to rooting it, and flashing ROMs on it.
I can confirm that re-flashing the stock ROM via odin allowed me to set up the scanner successfully, and that the functionality has not been affected by any subsequent ROM flashing.
I do not understand the mechanism behind why this happens, it is just my experience. Perhaps there is some sort of validation that is run the first time you use the scanner, making sure you are running official firmware, and then setting a flag somewhere? How then would that flag be saved for all subsequent rom flashes? Hidden partition or some ****? Hardware flag? I dunno I don't get it, but I figured out how to fix it by golly. Hopefully this helps someone else.
If any others can confirm the same issue, we may want to add this as a step in the rooting/romming how-to threads, so that others don't run into the same issue.
One good thing is that when I flashed stock via odin, it didn't wipe my data. I was able to then flash TWRP and then Dynamic Kat again, keeping all of my settings the whole way through. Ended up not being as much of a hassle as I thought it was going to be :good:
Thank you for sharing this, I have to say in my case it is not working now i did get the phone rooted and then added jovys rom then did my setup the fingerprint scanner worked for me, then i installed dynamic rom and then the later update of same rom and then the fingerprint scanner is no longer working for me there is a new update for the rom i am going to flash and see if it works now as in a previous version the bloat from samsu g had been removed and with jovys rom being stock rooted it was still there, so i am wondering if it has to do with some of the bloat from Samsung and it being removed that breaks the fingerprint scanner, i will report after i flash the new version of dynamic.
santos.moreno3 said:
Thank you for sharing this, I have to say in my case it is not working now i did get the phone rooted and then added jovys rom then did my setup the fingerprint scanner worked for me, then i installed dynamic rom and then the later update of same rom and then the fingerprint scanner is no longer working for me there is a new update for the rom i am going to flash and see if it works now as in a previous version the bloat from samsu g had been removed and with jovys rom being stock rooted it was still there, so i am wondering if it has to do with some of the bloat from Samsung and it being removed that breaks the fingerprint scanner, i will report after i flash the new version of dynamic.
Click to expand...
Click to collapse
I first noticed the problem while I was on Dynamic Kat 1.1 and thought the same thing, that it was something to do with the Sammy apps, but it still didn't work after updating to DK 1.2. I've had it both working and non-working whilst running the same ROM (1.2,) and the only thing different between the two instances was the fact that I configured it while I was in stock in one instance.
This is important information. Hopefully the devs will be able to fix this asap. Thanks!!
Wow thank you BotsOne! I'm having the same issue. I'll try this in the morning. Before I rooted, I set up the fingerprint scanner and it worked fine the I switched back to swipe, then rooted. After rooting I installed Jovys rom and lo it hasn't worked since. Does the lock screen have to be set to fingerprint scanner at the time of flashing roms or can you set it up once and move on from that point forward? Thanks again!
android242 said:
Wow thank you BotsOne! I'm having the same issue. I'll try this in the morning. Before I rooted, I set up the fingerprint scanner and it worked fine the I switched back to swipe, then rooted. After rooting I installed Jovys rom and lo it hasn't worked since. Does the lock screen have to be set to fingerprint scanner at the time of flashing roms or can you set it up once and move on from that point forward? Thanks again!
Click to expand...
Click to collapse
Honestly I'm not sure. We need a few more people with the same error to get to the bottom of what's going on here. I could be way off with my assumption. We need a bit more info.
Cool I'll try tomorrow and report back..
BotsOne said:
Earlier today I was mucking about and decided to play around with the fingerprint scanner for the first time. When I went in to settings and clicked the fingerprint manager, I received an error stating that the scanner is borked, and to reset my device to fix it. Rebooting did not fix the issue.
Soon I found another person with the same issue, who said that he was able to fix it by flashing stock NJ7 via Odin. After a bit of chatter we realized that neither he nor I had set up the fingerprint scanner before flashing a ROM. We basically booted the phone and went straight to rooting it, and flashing ROMs on it.
I can confirm that re-flashing the stock ROM via odin allowed me to set up the scanner successfully, and that the functionality has not been affected by any subsequent ROM flashing.
I do not understand the mechanism behind why this happens, it is just my experience. Perhaps there is some sort of validation that is run the first time you use the scanner, making sure you are running official firmware, and then setting a flag somewhere? How then would that flag be saved for all subsequent rom flashes? Hidden partition or some ****? Hardware flag? I dunno I don't get it, but I figured out how to fix it by golly. Hopefully this helps someone else.
If any others can confirm the same issue, we may want to add this as a step in the rooting/romming how-to threads, so that others don't run into the same issue.
One good thing is that when I flashed stock via odin, it didn't wipe my data. I was able to then flash TWRP and then Dynamic Kat again, keeping all of my settings the whole way through. Ended up not being as much of a hassle as I thought it was going to be :good:
Click to expand...
Click to collapse
Yes, I am quoting the entire op...
Give me some more evidence of this and I will edit the Root & Recovery Guide immediately... I have seen conflicting posts on this matter too... Also, is not clear if private mode does continue to work after rooting or not... Can anyone confirm... (without flashing any roms... from original unrooted to rooted) Private mode... does work or not??? (Private mode is not suppose to work after rooting... but some say it does work???)
Nice post! Come on people... help...
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
inphamous36 said:
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
Click to expand...
Click to collapse
I think this may be an additional problem for flashers, but not necessarily the same one I am addressing. The reason I say this is because I hadn't configured the scanner at all previous to when I discovered that mine didn't work, the error completely prevents me from opening the fingerprint manager. I couldn't even enable the fingerprint function to begin with. Does that make sense?
Not trying to argue just trying to make sure we are on the same page =)
Just noticed my fingerprint scanner isn't working. Wtf lol
Sent from my SM-N910T using Tapatalk
i notice this problem as soon as i flashed first rom the only way o get it working again is flashing back to stock odin but no matter what i do as soon as i flash a rom I get a error message ? here the post another member had the same problem
http://forum.xda-developers.com/note-4-tmobile/help/fingerprint-sensor-error-t2918069
inphamous36 said:
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
Click to expand...
Click to collapse
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
force70 said:
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
Click to expand...
Click to collapse
Have you tried restoring a backup and using the scanner? That's when it breaks. I can flash roms fine without having to disable it, but it didn't work after I restored a rom that had it enabled. Locked out of it
JawjaBill said:
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
Click to expand...
Click to collapse
I can tell you my history. I setup the fingerprint scanner right away before flashing anything as it is a must have feature for me. Later, I flashed a couple different ROM's and never had an issue. Just had to setup the fingerprint again. So my guess is if you set it up before flashing any ROM, you should be good. At least I was. I haven't had to disable before flashing or anything like that.
COCODRILO45 said:
i notice this problem as soon as i flashed first rom the only way o get it working again is flashing back to stock odin but no matter what i do as soon as i flash a rom I get a error message ? here the post another member had the same problem
http://forum.xda-developers.com/note-4-tmobile/help/fingerprint-sensor-error-t2918069
Click to expand...
Click to collapse
force70 said:
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
Click to expand...
Click to collapse
JawjaBill said:
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
Click to expand...
Click to collapse
inphamous36 said:
Have you tried restoring a backup and using the scanner? That's when it breaks. I can flash roms fine without having to disable it, but it didn't work after I restored a rom that had it enabled. Locked out of it
Click to expand...
Click to collapse
keitht said:
I can tell you my history. I setup the fingerprint scanner right away before flashing anything as it is a must have feature for me. Later, I flashed a couple different ROM's and never had an issue. Just had to setup the fingerprint again. So my guess is if you set it up before flashing any ROM, you should be good. At least I was. I haven't had to disable before flashing or anything like that.
Click to expand...
Click to collapse
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
TEKHD said:
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
Click to expand...
Click to collapse
I think once you root the KNOX counter gets tripped preventing private mode.
keitht said:
I think once you root the KNOX counter gets tripped preventing private mode.
Click to expand...
Click to collapse
Yeap I know... but there is this:
http://forum.xda-developers.com/galaxy-s5/development/mod-enable-private-mode-knox-0x1-t2904723
That almost nobody seems to know... It's actually possible to regain Private Mode after a tripped Knox... (Not impossible)
TEKHD said:
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
Click to expand...
Click to collapse
Well now....never tried it but just did and its working for me. Rooted, jovy23 deodexed stock, twrp.
The day i got my phone i odin'd update then installed twrp, then wiped everything but int & ext sdcard, rebooted to recovery, wiped again then flashed the deodexed stock rom.....just tested fingerprint unlock last night for the first time, no problems and just now tested private mode and again that works for me.
keitht said:
I think once you root the KNOX counter gets tripped preventing private mode.
Click to expand...
Click to collapse
Anyone tried CM12 on their Nexus 10 yet?
I installed it, and then tried to add new user (wife), wizard started, i entered gmail acount and password and then weird things started to happen.
Accessibility option was immediatelly started and I am unable to switch it off (Accessibility means the tablet starts to speak what you see, you can't click normalny on things, pretty annoying).
Tried it with different accounts too.
Any help would be appretiated how to disable this auto-accessibility starting after new user is added..
Currently Guest profile seems to be working ok, the drawback is, that after switching you have to confirm you want to continue in previous guest session..
EDIT: Forgot to mention that CM12 on my Nexus10 runs pretty fast compared to stock 5.0.1 (unfortunatelly, I installed CM12 day before Google announced 5.1 lollipop).
Settings > Users > Add New User Help
sarnowak said:
Anyone tried CM12 on their Nexus 10 yet?
Click to expand...
Click to collapse
Settings > Users > Add New User
While Creating New user it just stuck at cyanogenmod logo and light blue screen and with processing for a long long time and it never complete.
Any help in this matter please.
All things are successfully done. Rooting, Flash, Recovery, Rom, Gapps, All set and working for owner user fine and fantastic, but New user creation is nor finishing it just continuously processing and processing and processing.
Tried installing Rom many times.
CM12-maguro
Nightly built cm12 20150313 fixes this issue.
I can now create new profiles with no problem.
sarnowak said:
Nightly built cm12 20150313 fixes this issue.
I can now create new profiles with no problem.
Click to expand...
Click to collapse
Can you provide a download link!
Put in Google: cm12 manta download
Hi,
I have a S4 GT-I9505 running lineage_jfltexx Version 20190912 nightly.
After a few days, I was not able to unlock the screen with my pin.
When I entered the correct Pin, the unlock screen appeared again after a few seconds.
Entering a wrong pin gave an error message - wrong pin entered.
The current fix I'm using is:
Setting screen-lock-mode to 2 (instead of 0) in /data/system/profiles.xml
This disables the screen lock altogehter.
I found out a work around by creating a new user and a new profile with a lock-screen feature.
When I use the lock-screen feature profile, I cannot unlock as primary user (infinity loop).
Switching to the new user, I can unlock the phone, switch to a profile without lock and
switch to the primary user again.
So there has to be a problem with the user profile of the primary user.
How can I reset this profile for the system settings?
I tried clearing the system settings cache, but this did not work.
Thanks.
Hi fkno,
Same issue for me.
Do you succeed to deal with this issue in a better way?
Thanks
fkno said:
Hi,
I have a S4 GT-I9505 running lineage_jfltexx Version 20190912 nightly.
After a few days, I was not able to unlock the screen with my pin.
When I entered the correct Pin, the unlock screen appeared again after a few seconds.
Entering a wrong pin gave an error message - wrong pin entered.
The current fix I'm using is:
Setting screen-lock-mode to 2 (instead of 0) in /data/system/profiles.xml
This disables the screen lock altogehter.
I found out a work around by creating a new user and a new profile with a lock-screen feature.
When I use the lock-screen feature profile, I cannot unlock as primary user (infinity loop).
Switching to the new user, I can unlock the phone, switch to a profile without lock and
switch to the primary user again.
So there has to be a problem with the user profile of the primary user.
How can I reset this profile for the system settings?
I tried clearing the system settings cache, but this did not work.
Thanks.
Click to expand...
Click to collapse
Koputy said:
Hi fkno,
Same issue for me.
Do you succeed to deal with this issue in a better way?
Thanks
Click to expand...
Click to collapse
Not yet.
I tried to track the problem. Changing the pin / trying to unlock the phone and
see, which sections in the user profile got a new timestamp.
For me, it looks like it is in the com.google.android.gms section of the user profile.
I'm not sure, wether I can delete or overwrite this directory while the phone is running.
And if I delete this section, wether it will be recreated when rebooting the phone.
Hi,
Why don't you move to Lineage OS 17.1 ? It is awesome thanks to JDC team and LOS teams.
https://forum.xda-developers.com/ga...y-s4-i9505-t3517706/post70049958#post70049958
djibe89 said:
Hi,
Why don't you move to Lineage OS 17.1 ? It is awesome thanks to JDC team and LOS teams.
https://forum.xda-developers.com/ga...y-s4-i9505-t3517706/post70049958#post70049958
Click to expand...
Click to collapse
FYI, I have the same identical problem on LOS 17.1 but on a different device (marmite). This is an Android issue, not something related to this or that LOS version.
69.5MB in size so no major changes are to be expected...
Downloaded it just now...no major changes...no bugs encountered...
Weird noise while switching camera modes seems to have gone
Patched boot of last update ?
parkpark9999 said:
Patched boot of last update ?
Click to expand...
Click to collapse
Stock and patched (Magisk 19.3) images of /boot partition:
Note: I recommend to
- copy stock image to /downloads,
- patch it with Magisk (thus a copy of stock image will be saved in /data for further "Uninstallation of Magisk")
- copy patched image to PC (or take the one attached)
- boot patched image via fastboot
- make "Direct installation" in Magisk
This method will enable you to "Uninstall Magisk" by <Restore partitions> command when preparing to download next OTA
Darshan28 said:
Weird noise while switching camera modes seems to have gone
Click to expand...
Click to collapse
Yes i can confirm that.
Is seems THat WI-Fi Is more stable now also.
ki69 said:
Yes i can confirm that.
Is seems THat WI-Fi Is more stable now also.
Click to expand...
Click to collapse
No, the sound is still there but a lot quieter (tested with a sound meter )
WARNING: Caused my phone to get stuck in a bootloop during update.
I'm not rooted and haven't unlocked bootloader. Trying to find a solution.
Edit: after a bunch of tries and some time charging, it finally booted and displayed a "Couldn't update" error. I'm back to august patch with a working phone. I guess I'll wait for more people to report on this update.
A question: In case my phone gets stuck in a bootloop for good when updating, should leaving the "OEM Unlocking" option enabled be enough to save it and allow me to flash a fresh iso?
I mean, only leave the option enabled, but not actually unlocking the bootloader (I don't want to reset the phone unless necessary).
Wifi has indeed improved a lot! I have now connection to the WiFi with the September update where it did not even find the network with the August update. Big improvement here! It now shows the same behaviour as an Galaxy S7, which is really good with WiFi. Major thing... Thanks Xiaomi!
Edit: it looks like this was only accidentally. On other places WiFi is still far more worse than on other devices. Where other devices find multiple WiFi networks with decent speeds, the Mi A2 find no network at all. If it finds finally one, then the speeds are dramatic. I ditch the phone and I'll go for the S10.
JassyNL said:
Wifi has indeed improved a lot! I have now connection to the WiFi with the September update where it did not even find the network with the August update. Big improvement here! It now shows the same behaviour as an Galaxy S7, which is really good with WiFi. Major thing... Thanks Xiaomi!
Click to expand...
Click to collapse
I'm not sure but seems the range became reduced. Need to test again.
WiFi speeds seem to have increased, camera noise is gone for me. So far no complaints
danannnn said:
WARNING: Caused my phone to get stuck in a bootloop during update.
I'm not rooted and haven't unlocked bootloader. Trying to find a solution....
Click to expand...
Click to collapse
Used to happen with many previous OTA updates to many people. Why should this update be fully safe? That's why experienced stock MiA2 users recommend to keep bootloader and critical unlocked.
danannnn said:
Edit: after a bunch of tries and some time charging, it finally booted and displayed a "Couldn't update" error. I'm back to august patch with a working phone.
Click to expand...
Click to collapse
Good that this method worked for you.... usually works but needs great patience and dedication.
danannnn said:
A question: In case my phone gets stuck in a bootloop for good when updating, should leaving the "OEM Unlocking" option enabled be enough to save it and allow me to flash a fresh iso?
I mean, only leave the option enabled, but not actually unlocking the bootloader (I don't want to reset the phone unless necessary).
Click to expand...
Click to collapse
Yes, enough, but please consider following:
- now with working phone you can save most of your user data to PC (and to Google), then unlock and then restore data;
- when you will be forced to unlock phone in bootloop, you won't be able to save/restore user data
- after unlocking you will have ability to make TWRP backup of your /data partition
Audio is definitely louder.
Aerobatic said:
Stock and patched (Magisk 19.3) images of /boot partition:
Note: I recommend to
- copy stock image to /downloads,
- patch it with Magisk (thus a copy of stock image will be saved in /data for further "Uninstallation of Magisk")
- copy patched image to PC (or take the one attached)
- boot patched image via fastboot
- make "Direct installation" in Magisk
This method will enable you to "Uninstall Magisk" by <Restore partitions> command when preparing to download next OTA
Click to expand...
Click to collapse
Sorry for the question, i'm on 10.0.13.0, can i boot the 10.0.14.0 patched and update, because i uninstalled magisk and all of the modules and the update fails, says it couldn't update.
Anyone thinks that the screen takes quite a while to light up after the fingerprint is recognised?
tatitar said:
Sorry for the question, i'm on 10.0.13.0, can i boot the 10.0.14.0 patched and update, because i uninstalled magisk and all of the modules and the update fails, says it couldn't update.
Click to expand...
Click to collapse
To answer your question, no, you can't update by doing that.
It is highly probable that your system partition have been remounted rw (read/write). For Android to successfully update, it is important for any of the root apps to never remount system as rw.
To check if this is the cause, check Matlog (an app for logcat) after the error when performing the update. Filter "update engine" and check a message in regards to system mounting.
If this is correct, then, to be successful in updating to the September security level, you will need to flash the August's system partition from a fastboot package, and then try the update once again
---------- Post added at 04:28 AM ---------- Previous post was at 04:23 AM ----------
LeChevalierR said:
Anyone thinks that the screen takes quite a while to light up after the fingerprint is recognised?
Click to expand...
Click to collapse
I see that this have a chance to occur when a person updates to a newer patch level. This is based on the messages i have seen in this forum board though it is unknown if it really the cause.
I read that deleting your fingerprints and add them back as new "fixes" this issue. I recommend you to try it out first
Aerobatic said:
...
Click to expand...
Click to collapse
Thanks for the all the explanations.
I guess I'll just keep "OEM Unlocking" enabled for now if its enough to save me from disaster. I don't mind losing my phone data, I consider it transient anyway. I'm just too lazy to set it all up again unless I really need to.
After making sure OEM Unlocking was enabled, that I got fastboot all set up and working, etc., I went ahead and attempted to update again, this time with no issues.
New bug encountered? I was watching a video from YouTube I opened through a WhatsApp link and all of a sudden my back button was there but home and recent apps buttons disappeared and they didn't come back until I reset my phone!
My screen makes some weird noises when it register touch, like squeking or static noise behind the screen, it is hard to explain. It start to hear when touchscreen register touch and it last about 2-3 seconds, then it stop, and when i touch it again the sound is back and so on. It's very annoying
I can do confirm that the camera sound is gone, although I can still hear it if I concentrate enough. It might be what is used to sound before so I can't really tell.
WiFi is definitely improved and it now searches for available networks faster
Overall system speed is improved specially with those awkward keyboard lags in the previous update.
Also LTE Signal got better I can tell
.
.
But I do have a little doubt about the battery life cause my phone had about 14% of charge last night which I forgot to plug in the charger and it was dead in the morning which has never happened before. It usually had at least 5% when that happened before. Still am not sure if that's the real deal so I'm gonna just wait some more to see battery performance.
But the update itself seems stable and bugless enough so it's definitely recommended to install it especially if you're dealing with camera sound...
P.S. : No camera2API nor ARCore
Greetings.
Due to events beyond my control, I had to give up my Pixel 3 XL (packing it as I type this)
Until funds become available, I decided to bring the Nexus 6P - with pre-mature battery shutdown issue - back to duty. I have new battery, lens cover, etc. waiting in the wings so it may become my primary whip after all. That is "if" I can undo whatever mistake I made tonight (knocking on wood).
The 6P was unlocked already before being retired (Idon't know if it matters or not). Stock image (I think it was 8.1) with security update from December 2018 I think.
Here's what I think I did tonight that lead to the current situation:
1. installed TWRP 3.3.1
2. along the way wiped one too many partitions - my stupidity
3. thanks to TWRP for warning me that there was no OS so went back, found USB-A to USB-C adapter, copied "PixelExperience_angler-10.0-20191113-2124-OFFICIAL," and used TWRP's "Install" option
First problem is that I noticed in the text log within TWRP that the vendor image was missing
Second problem, or perhaps because of above, after restarting the 6P it never gets out of the welcome screen of Android 10
Third problem, again may be related to #2 in the things I did tonight, when I reboot into TWRP recovery, first thing it does ask is "Mount, Decrypt Data" and "Enter Password" to which I don't know the password. If I select "Cancel" I get to TWRP main menu but I can see that "Internal Storage" is now at 0MB.
I know I did wrong here but is there any way to recover? Since it doesn't boot into Android 10 (just stuck at welcome screen, I guess using ADB on laptop, if it helps, is out of question? Can I fix this through TWRP?
Thank you for any help/advice.
UPDATE: Reading some more threads on XDA & decided to try Lineage. At one point seems to have things working following the directions but the SIM card was not recognized.
Thinking of trying again with Lineage but maybe with Lineage16 instead of 17. But what is the best stable ROM that is plain Android but perhaps based with up-to-date security patching?
Thank you!
ur2punk said:
UPDATE: Reading some more threads on XDA & decided to try Lineage. At one point seems to have things working following the directions but the SIM card was not recognized.
Thinking of trying again with Lineage but maybe with Lineage16 instead of 17. But what is the best stable ROM that is plain Android but perhaps based with up-to-date security patching?
Thank you!
Click to expand...
Click to collapse
I've been running aicp for the past few months, which is 9.0 they still put out weeklies with security updates. Not sure how long they plan on supporting 9.0 though
Lawlrus said:
I've been running aicp for the past few months, which is 9.0 they still put out weeklies with security updates. Not sure how long they plan on supporting 9.0 though
Click to expand...
Click to collapse
Thank you. Because the SIM was not recognized, I was going to restore to the last Android. I may just try the aicp ROM first.
ur2punk said:
Thank you. Because the SIM was not recognized, I was going to restore to the last Android. I may just try the aicp ROM first.
Click to expand...
Click to collapse
Yeah I haven't noticed any issues with Sim with this device. You said you had it on a shelf for a while though, if it was before the last update the device got, DEC of 2018 did you DL the ota a d make sure the radio was up to date ?
ur2punk said:
Thank you. Because the SIM was not recognized, I was going to restore to the last Android. I may just try the aicp ROM first.
Click to expand...
Click to collapse
I had this SIM card issue when I was trying to flash RR, tried twice with same results. Came across a post once about a bug and it said to remove all screen locks, low and behold it worked... weird
redshirt110 said:
I had this SIM card issue when I was trying to flash RR, tried twice with same results. Came across a post once about a bug and it said to remove all screen locks, low and behold it worked... weird
Click to expand...
Click to collapse
Ah yeah, I've seen that before no idea why people have to do that. I've never had my Sim stop working because of a screen lock. I never looked onto why it happens. I always chaulked it up to a not a US problem because most of the people that posted about it seemed to be from a different country lol.
Update!
I thought it would be a good idea for me to try this routine of wipe & install the Android 8.1 again to get myself comfortable with the process. Long story short, I did exactly that:
(- Bootloader was already unlocked)
- TWRP
- flashed/installed Dec 2018 OTA images/zip
- Installed Magisk
Everything seemed to be working fine when I found out ,while on road, that Google Maps don't work after 5 seconds or so (the navigation part). Read up & they suggested safe mode so I did that. Happy to report that it works so it is not the GPS antenna as some had reported. Whew.
Is there any particular image I need to reflash to see if that was the problem? Or should I just reinstall again? At least I'm getting more comfortable with the various commands - LOL.
Thank you!