I am having an issue with my Nexus 6's silent mode disabling itself on LineageOS 14.1. I first experienced this issue with the January 5, 2018 build, and was hoping that it would be fixed in the January 12, 2018 build, but it wasn't. I posted about it on the LOS subreddit twice, and nobody else was complaining about the issue. I also submitted a bug report detailing the issue here, but so far, I have not heard back from anyone. That's not to say that I was expecting it to be fixed quickly, but I was hoping that I would at least see someone make an "I'm having this issue too" post.
After seeing that the issue was not resolved in the January 12 build, I thought perhaps it was an issue related to something I had unwittingly done to cause it to happen, so I tried to fix the problem by restoring a Nandroid backup I had taken with TWRP. I then reinstalled the January 12 image, but the issue remained. The backup was of the December 29, 2017 ROM, which was the last ROM that I was using before this issue started occurring. Since I haven't heard anything from the LOS community about what's going on, I thought perhaps now would be the time to ask on XDA about it.
I am still having this issue with the February 9 build if anyone would like to assist.
Couple of questions.
Have you clean flashed the newest release?
Can you replicate well enough that you could pull a log covering when it happens? Connecting to a PC and doing a logcat through ADB would probably be easiest.
Have you search/posted in the N6 LineageOS thread?
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Related
i changed to omnirom kitkat on my s3 a few weeks ago, and i just want to know if i should be downloading the latest versions?
thanks in advance, glenn.
gdaley1 said:
i changed to omnirom kitkat on my s3 a few weeks ago, and i just want to know if i should be downloading the latest versions?
thanks in advance, glenn.
Click to expand...
Click to collapse
It would be interesting to know other people's views on this too.
Well things usually get an update to be better ^^. So i'd say always. If you look around the forum you'll see there are still some (minor?) issues left which might or might not be important for you. If you stop updating you'll also miss out on potential new features and you can't contribute by filing bug reports ect.
Sent from my Find 5 using XDA Premium 4 mobile app
I usually go on omnirom's changelog to find any patches that pertain to me. Just the other week active display was not working. I updated immediately when next active display patch came out. I also update when there is a new feature I want.
Since even minor updates often have big impact (on battery life for example) I update on every nightly. But I keep a backup in case a weird bug entered the image.
I hope the build-in flash in my S2 is not the cheapest one since Samsung itself only updated once half a year or so - so I am (at least a little, little bit) worried that it someday will be worn out. Does anybody know if this is really an issue?
I update when I'm bored and happen to remember. Maybe twice or three a week. I usually check g+, device thread, or here for any update problems, though.
there's been a handful of times where I thought "ok I'm done fooling around with my phone... I'm pleased enough," but I'll update afterwards.
I've been updating on every nightly and then there was the data/wifi issue with the s3 i9305 and since then my phone just has not worked as it should at all safe to say the next nightly I find that seems to have no data/wifi issues I'll be sitting tight on. I know my friend has a system where he updates to the second newest nightly only, never the newest that way you're always up to date eventually but you get to see the feedback about the nightly first from everyone else having used it before you flash it, thus saving the issue of flashing a nightly that stuffs up pretty bad.
Also does anyone know when flashing a nightly it's OTA, if you want to go back to the previous nightly can you just flash it and it should work? Before I was having wifi/data issues I had the nightly on my SD card, then I flashed the new nightly, got data issues so I flashed the previous nightly that worked and still had the data/wifi issues...
In my opinion, you're rolling the dice with any upgrade. A nightly is just that, whatever was up that night. It might be better, it might be worse. Thankfully the OmniROM maintainers are generally pretty good about things and I haven't yet gotten a broken build. But it will happen. Invariably the night before you really, really need your phone to be working.
A cautious approach would be to maintain recent backups and only flash when you see something come up that you know you want. I like to flash on days when there hasn't been a change for a day or two -- let someone else find out that the "latest and greatest" isn't as great as they had hoped.
Yes, flash memory has a finite lifespan. If you look at the physical device layer, you'll see it. A good physical-to-logical block management layer ("wear leveling") keeps the cells reasonably evenly used and hides the failed cells from you. It might be in the device itself (microSD cards, for example), or in the driver/filesystem. You probably don't have to worry too much about flashing on a daily basis (as far as "wear" goes) as long as your device devs have made reasonable choices on how to put files onto the hardware of your device.
Being in the time zone that I am, the nightlies usually post when I am sleeping. Each morning, I check the change logs and newest comments. If there are a lot of early problem reports I pass on the build. If things look reasonably clear I download and flash.
Usually I update once or twice a week.
Now my device (SGS2) is with nightly 06/03/2014. This nightly working so well and is so battery friendly that I will keep it for a while longer.
And now the camera already has the option to choose where to save photos and videos (internal memory or external SD card).
Hi guys,
my OP3T is increasingly getting on my nerves and I'd love some input on what I should do next. I've been running rooted OxygenOS with TWRP and SuperSU - as far as I can tell, this is old technology. Every time Oneplus released an update, I'd download the full zip file, flash it in TWRP and flash SuperSU over it. Reboot and I'm up and running again right away.
Now with the OOS 9.x.x release issues, things are getting a bit more complicated - I think this might be the right point in time to do a full wipe, back up everything via Titanium Backup and start fresh with a new custom ROM that will (maybe) provide updates for the next year or two.
In general the OP3T is starting to get a little slow. Google Assistant is flakey (Sometimes doesn't activate properly on "OK Google", sometimes plays the beep and then doesn't record any commands, sometimes pops up behind the home screen icons so you can't read any of the text, sometimes just ignores the "OK Google") and the battery life is going downhill a little bit. I'm hoping a fresh wipe and maybe a new ROM will help here. I also need to take care of the earpiece issues - mine is clogged with dust, as are many Oneplus phones if Google results are anything to go by...
So I have a few options:
1. Sell the OP3T cheap (can't give it to my girlfriend because of the earpiece), buy a Pixel or some other phone
2. Upgrade the OP3T to OxygenOS 9.x.x and keep my data with this method (https://forum.xda-developers.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164)
3. Upgrade the OP3T to OOS 9.x.x, wipe everything and move to Magisk or something like that - what are my options here? Is Magisk the go-to method to get root these days?
4. Pick a custom ROM, wipe everything and just move to that. Anyone have a recommendation that's pretty much stock Android, stable and will likely receive regular security updates for the next one or two years? Easy updates with root would be a definite plus!
Any suggestions? Half of me is about ready to trash the OP3T and just get a Pixel now that I can't hear callers when I answer the phone
bemymonkey said:
...
Any suggestions? Half of me is about ready to trash the OP3T and just get a Pixel now that I can't hear callers when I answer the phone
Click to expand...
Click to collapse
You could get the ear piece and microphone ports cleaned.
You could do a clean install.
You could install custom ROMs
You could upgrade.
These are all choice you make.
My personal choice: I'm keeping my phone for at least 4 years. I'd be happy very with just OOS (I think it's the best rom I've ever used), but I want security updates. And for that reason I use LineageOS (I've been using it and CM since 2012).
You make your choice based on what matters too you.
Sent from my OnePlus 3T using XDA Labs
Hi Bill,
thanks for your answer.
Of course it's a personal choice that I'll have to make - I'm just looking to get some more info and pros/cons for each choice before wasting my time. Cleaning my earpiece is something that'll take an hour or so of careful fiddling (Is there a permanent fix to get it dustproof? Maybe an aftermarket dust gasket of some kind?), and backup/wipe/flash/restore is something that'll certainly take a chunk out of one of my weekends. All in all that's probably 12 hours of my life I'm not getting back.
Mainly what I want to know is: Is wiping the phone flashing a custom ROM like LineageOS viable for reliable day to day use on the OP3T? How has your experience been compared to OxygenOS in regards to:
-Updates (both security and Android version) - Is the update process seamless now or is it still done purely by a flash from recovery?
-Stability (I'm seeing only nightly builds on the LineageOS page [https://download.lineageos.org/oneplus3] - are there stable or even milestone builds?)
-Feature completeness compared to OxygenOS... do things like double-tap-to-wake work?
-Root... as I asked in my OP, what method is standard these days? Lineage suggests its "AddonSU" package but everyone else seems to say Magisk ist the way to go...?
-Is anything broken?
?
Does anyone else have alternative suggestions in regards to ROMs that may be exactly what I'm looking for? Something that looks and feels exactly like OxygenOS?
bemymonkey said:
...
Mainly what I want to know is: Is wiping the phone flashing a custom ROM like LineageOS viable for reliable day to day use on the OP3T? How has your experience been compared to OxygenOS in regards to:
-Updates (both security and Android version) - Is the update process seamless now or is it still done purely by a flash from recovery?
-Stability (I'm seeing only nightly builds on the LineageOS page [https://download.lineageos.org/oneplus3] - are there stable or even milestone builds?)
-Feature completeness compared to OxygenOS... do things like double-tap-to-wake work?
-Root... as I asked in my OP, what method is standard these days? Lineage suggests its "AddonSU" package but everyone else seems to say Magisk ist the way to go...?
-Is anything broken?
...
Click to expand...
Click to collapse
Updates: I dirty flash them in recovery once a month.
Security updates: Los gets them every month. OOS may get one more update, but that will be the last.
Completeness: I find Los as good as OOS. And Nlos (https://forum.xda-developers.com/on...elopment/rom-nlos-16-0-t3879405/post78433980) even has scrolling screenshots. Note: I don't care much about the camera as I rarely use it.
Root: I've been using Magisk since SuperSU became unsupported. I like it better than SuperSU. I have absolutely to problems with it.
Broken: nothing's broken for me.
But you would have known all of this if you read through the various threads. And there's no "best" rom as it's a subjective decision.
So jump in and try things for yourself.
Sent from my OnePlus 3T using XDA Labs
As the title says....
Still only Android 9, as expected (PKQ1.190321.001).
I have just received it too Trying and trying for the update for hours and finally it popped up on my phone a few moments ago!
Security patch is a shocker, I'm not seeing anything else different though but hopefully they don't introduce any bugs or problems
notification for update also displayed on our handset. it doesn't seem to come with much changes.,
marcelo
I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Matzeus said:
I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Click to expand...
Click to collapse
Probably a hardware issue. Find one of the many sensor testing apps and run it several times to identify a weak or defective sensor. There is not going to be a cleaning or software solution. If you do find a sensor not working 100%, do another clean wipe and test again before looking into replacement. Normally the FR on the P4 is extremely fast and accurate.
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Matzeus said:
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Click to expand...
Click to collapse
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
v12xke said:
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
Click to expand...
Click to collapse
How can you say google forums are a joke when literally hundreds of people are having the same issue? I dont want to believe that we all have hardware issues. Otherwise the hardware would be some hot garbage.
I removed and readded the face multiple times already.
I booted into safe mode. It works there. But like I said, it also works after a normal reboot for some hours/days before it needs a reboot again.
I also did test the sensors, no errors there. However my next step is to run the test when the error is present.
Any specific suggestion on which app I should use for testing?
Thanks again.
@Matzeus
No specific sensor app. Facial data is stored on the Titan M chip, and the only way I know to wipe that facial data and potentially fix it is by doing a factory reset from the stock recovery. Fastboot flashing will not wipe the Titan data and even from recovery is only a partial wipe. If you've ever had TWRP installed, there is a looong thread on broken face lock there. FDR from both recovery and setup would be my next suggestion.
@v12xke
In the past i ran the factory default from the system settings, didnt help. After that I used Googles "Android Flash Tool", which didnt help either.
Additional information: the device has never been rooted or anything. Always been on stock firmware.
Anyways, small update on the whole thing:
The issue occured again, I ran the app "Soli Sandbox" and it simply didnt do anything. So far so good.
After closing Soli Sandbox and clicking on the face unlock option in the system settings, magically everything worked properly again. Even without a reboot.
I am not sure what solved the error now..
I guess its safe to say, that all motion gestures stop working once the problem occurs.
Will keep this thread updated as I find out more.
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
The march update claims to have brought some improvements to Pixel 4s face unlock feature. At least thats what they say in the official changelog.
Biometrics
General improvements for face unlock stability & performance *[4]
Lets see if the problem is gone now. Will keep this thread updated.
sufy1000 said:
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
Click to expand...
Click to collapse
It's uncannily good. I keep the phone upright in a cradle by my PC so I can monitor it, and all I have to do is turn my head to peek, and it unlocks every time. It's pretty amazing. I've never had a problem with it.
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Matzeus said:
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Click to expand...
Click to collapse
Still going strong? And did you notice this issue on Android 10?
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Matzeus said:
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Click to expand...
Click to collapse
Thanks. I've got a new 4 XL that definitely has this issue but I didn't spend much time with it before updating to 12 from 10. It's a real PITA. I've never installed a custom ROM, but thinking I may need to do what you've done as this is irritating af.
@puzzlefighter
Just go for it man.
I was so upset about face unlock and i regret that i didnt install a custom ROM earlier.
Share your results afterwards please if you installed a custom ROM
this is not a hardware problem, but a software one, it started with the release of android 12, the problem is not in the face unlock sensor, but in the proximity sensor, it sticks, as if it was closed with a finger, I use Pixel experience + 12, this firmware does not have this problem, I'm disappointed with google developers(
Hello,
My M21 says it is up-to-date, but it isn't and I can't figure out why. I've even gone so far as to do a full factory reset, and still it won't update. The factory reset was the last option I knew.
Alot of google-searches resulted in the feeling that this is an isolated case.
Samsung Switch on PC also says the phone is up to date.
All my colleagues (it is a company phone) have the same model, and they have all received the updates long ago.
I've added screenshots of the software-information it is showing.
If anyone knows a solution to this, please let me know.
Thanks for any replies or clues anybody might give.
Lol, if I was you I would disable OTA updates!
If the OS is fast, stable and fulfilling its mission... let it be! Upgrades can and do break things.
No rollback from 11 as it upgrades the bootloader version too. Let that soak in; it's a one way ticket once punched Mr Wick... consequences.
Android 9/10 best, Android 11* so-so, Android 12* is a mess... in my opinion.
With Pie and higher you are protected from the worst rootkits. Unless you do something stupid security and malware won't be an issue.
*do you really want cpu cycle sucking scoped storage fully active? Some apps like the old free version of WPS Office will most likely not load.
I was actually hoping that the update would fix some of the inconveniences I've noticed since I started using it.
Things like:
Random restarts while the phone is doing nothing, needing me to enter the PIN for both SIM's. Like in the middle of the night. The alarm still goes off in the morning, however it goes of at max volume... Or in the middle of a run (i use the phone for sports tracking), causing me to lose the workout data.
Random disconnects from bluetooth devices
Sometimes slowdowns for no apparant reason
Incredibly slow camera
This is a company phone, and before this I had a personal Nokia 8.1. Transitioning to the M21 just feels like a step back. It's slower and has more buggy behavior. I was hoping the updates would fix it, because rooting is against company policy.
And this is apart from the security updates that haven't come through since october 2020, while all colleagues with the same phone did get those updates.
And I'm also just curious why this one says it has the most recent updates, while it clearly doesn't. Whether I choose to install those updates is another matter. It just doesn't give me the choise.
NCC369 said:
I was actually hoping that the update would fix some of the inconveniences I've noticed since I started using it.
Things like:
Random restarts while the phone is doing nothing, needing me to enter the PIN for both SIM's. Like in the middle of the night. The alarm still goes off in the morning, however it goes of at max volume... Or in the middle of a run (i use the phone for sports tracking), causing me to lose the workout data.
Random disconnects from bluetooth devices
Sometimes slowdowns for no apparant reason
Incredibly slow camera
This is a company phone, and before this I had a personal Nokia 8.1. Transitioning to the M21 just feels like a step back. It's slower and has more buggy behavior. I was hoping the updates would fix it, because rooting is against company policy.
And this is apart from the security updates that haven't come through since october 2020, while all colleagues with the same phone did get those updates.
And I'm also just curious why this one says it has the most recent updates, while it clearly doesn't. Whether I choose to install those updates is another matter. It just doesn't give me the choise.
Click to expand...
Click to collapse
That's not a stable load. I don't blame you for wanting to ditch it if that's the best it can do.
I never get random reboots or the rare crashes I see seldom require a reboot.
Make sure global power management is disable and that a 3rd party app isn't the cause.
It's possible that the firmware is corrupted; a reflash to the same rom might be a safer option.
Or you could try flashing the next OS version up... avoid 12 though. Lots of reported issues across the board with it, and lots of people doing rollbacks to ditch it.
This will probably get time intensive.