Solution (temporary) to "sns_eve_sync_wakelock" - RAZR HD General

Well, I've benn having this wakelocks keeping my phone fully awake since a little more than a week when I installed AOSPA build 2.
This problem happens even in fresh installs without gapps (I tried it), so the problem is on the OS.
According to a guick google search, this problem was most likely NFC related. But I already had it disabled.
Seeing build 3 didn't fixed it and PA legacy community didn't pay attention, I switched back to CM11 but, to my surprise, the same wakelock was still there and my phone not sleeping.
Since it was a fresh install, I went to settings and disabled NFC. sns_eve_syn_wakelock was gone, but a new wakelock occupied it's place: Nfce:EemWakelock (or something like that, not sure), so I got confirmation that google was right, it was NFC.
So I proceeded to flash this http://forum.xda-developers.com/showthread.php?t=2544811.
Problem is fixed. My phone is deep sleeping again.
Of course, it's a TEMPORARY fix, until developers can find out what's wrong with android sources.

Related

[Info][WIP] LET's FIGURE OUT the sleep of Death!!!! [NOT A ROM]

Does anyone have a logcat from their dead transformer, during/around the time when it died?
Has anyone noticed any trends in when it happens? I saw something about 82% battery but I think that's just a coincidence.
Please post here so we can get to the bottom of this.
Jcarrz1
I think this is dev, unless it's a hardware issue. But hopefully we'll be able to discern that.
I have had multiple sleep of death issues after rooting. When I flashed back to the stock Blob, they stopped. Every time I root to Blob V5 (I am on the most recent firmware), they come back. I tried MoDaCo's Rom - they still occurred. Trying Prime's Rom now - so far it's working without any sleep of deaths.
I was on MoDaCo's Hr4 for a few days and never had a sleep of death. Since installing Prime 1.2 I've had 3 or 4.
Since we've had completely opposite experiences I think we can safely rule out that this issue is ROM related.
I've used both those roms and never had a sleep of death. But I also used the root method without the v5 blob, just the standard GingerbreakBB.
I've had one sleep of death incident, using unrooted stock Transformer configuration.
mine case: downgrade back to 8.2.2.6 using SD method (EP101_SDUPDATE.zip) then Gigerbreakbb then the BLOBV5 => lots of SOD issue.
May be we must update to the latest 8.2.3.9 before break using gingerbreakbb and install BLOBV5?
BR
Blob 5 is made to work with 8.2.3.9... It will most definitely have issues with the old firmware.
I am beginning to think the issue is with one of my apps and its settings. When I am rooted, I use Titanium Backup to restore my data and maybe the reason for the SOD is because something in an application isn't playing nice with Honeycomb... Obviously when I am not rooted, I cannot restore the settings and thus no SOD.
I just flashed back to root with Blob V5. Going to see if there are any SOD issues before installing apps... Will probably install one by one to try to see if I can find the problem - A PITA, but I really want the SOD to stop.
Had it with latest asus Update, no root and 40% brightness + wifi sleeps while screen is off. Lockscreen was enabled.
Sent from my Nexus One using Tapatalk
Edit:
Had another one after changing wifi sleep policy. I think it is wifi related.
The-Nazgul said:
Had it with latest asus Update, no root and 40% brightness + wifi sleeps while screen is off. Lockscreen was enabled.
Sent from my Nexus One using Tapatalk
Edit:
Had another one after changing wifi sleep policy. I think it is wifi related.
Click to expand...
Click to collapse
Other threads are pointing to the WiFi scanning be enabled. I have flashed back to MoDaCo Hr4 (because it was more stable for me than Prime 1.2) and also disabled WiFi notifications and will report back if/when I get a SOD.
Unrooted, getting about one or two of these a day depending...... seems to happen more if I've left it sleeping for an hour or more.
Putzy said:
Unrooted, getting about one or two of these a day depending...... seems to happen more if I've left it sleeping for an hour or more.
Click to expand...
Click to collapse
this could relate to wifi scanning as well. were you connected, and what are your current settings?
Thanks for participating everyone, so far there isn't a conclusive answer.
However, could someone install log collector from the market, and leave it there until the BlackSOD happens, and then upload the file? that would be super awesome. preferably someone who gets them all the time. if the last thing in the logcat is consistently wifi-related, then we're on to something.
is there any firmware version on which NOBODY has EVER had a BlackSOD? This could be worth looking in to as well.
Well, I rerooted and have installed about 80% of my apps. So far no SOD. I have a few more apps to install and I usually freeze some of the unwanted apps. Will post an update later. Also, I read on other forums that fancy widget caused issues like this on other tablets. I had been using beautiful widgets I wonder if the way that tries to access wifi causes issues.
The apps I have yet to install are:
Watchdog lite, beautiful widgets, adfree android
Sent from my Transformer TF101 using Tapatalk
Just had one while wifi was disabled! I guess that makes it less likely that wifi causes the problem.
Next time I will upload a logfile!
Sent from my Nexus One using Tapatalk
I've had 2 so far, both with Hr4 and blob v5. Battery has been at different levels, so I think thats a coincidence.
Has anyone tested on a 100% Factory reset device (either with a custom or stock ROM?) That should help rule out any apps which may cause the problem.
FWIW, never had this issue (have run Stock, HR1 -> HR4 & Prime V1.2)
so far no SOD after a clean tstart
Had a SOD this morning on Hr4 so I will run Log Collector today and hope to catch another. I'm assuming that Log Collector is continually writing to my Gmail draft so it should be there after the full reboot? Doesn't seem like it will let me mirror logcat to a file on sdcard...
sent from a device using an app
I realize this isn't the least bit helpful, but after having several SoD issues, and trying all the fixes (and then undoing them), I haven't had the issue for a week now. Mine would do it sporadically -- it would happen once in a day, and then 3 times in a day -- and the only thing I've left changed is disabling the lock screen, but I think that's just coincidence. This will be a hard one for Asus to nail down.
Hopefully someone produces a helpful log for Asus, I'm sure some non-XDA people may think they have a dead tablet rather than one they have to force power down and reboot.
had my firs SOD today.
running prime 1.2 US. battery at 96%. wifi on.
spuniun said:
Had a SOD this morning on Hr4 so I will run Log Collector today and hope to catch another. I'm assuming that Log Collector is continually writing to my Gmail draft so it should be there after the full reboot? Doesn't seem like it will let me mirror logcat to a file on sdcard
Click to expand...
Click to collapse
So it does not seem that this app will work because it only collects logs in real-time, does not store them for later analyzing. What else can I use other than leaving adb logcat running?
sent from a device using an app

Random Reboots / 4.2.1?

Hey guys... I'm still seeing some random reboots even after the 4.2.1 patch. Anyone else? Just curious if the patch is releieving this issue for some or if I'm unique. (It's disappointing to say the least... I hope it gets sorted out soon). My GN phone is having 4.2.1 reboot issues even with a custom ROM as well (though less than what I see with the tablet). Luckily, my wife's N7 has been pretty good (I suspect its rebooting on her while she's not around though, as both my other devices have done this as well).
My N10 randomly shut off (not rebooted) once so far after 4.2.1, but I only had 2 cases of random reboots back on 4.2
Yeah it's happened to me to.
Things that minimize reboots are removing apps and widgets that use Location Services. Disable location services as well.
I haven't had a reboot since I did a clean sweep. Thing like Maps will require you to go in and manually disable it. I found Facebook was one of the biggest offenders.
My old tablet (Transformer TF101) was plaqued with RR/SODs after the update to ICS. Really it still is but with a few tweaks and a custom kernel, I finally got it stablized. Why are you posting this here you say?
Because in that debacle, we found out a few things:
1, Asus will push out updates to help with the issue, but being that this is a Google "Experience" device, you should have a better chance of getting this fixed than we did.
2, I have heard repeatedly on almost every device that got 4.2 pushed that this is a problem. If you can stand it, hold out for a bit, I bet Google will get it sorted out (and not Asus).
3, we found that even though you think you are not having RRs, they may be occurring w/o your knowledge. There is an app in the market called Reboot Logger (can't remember off hand if it is a Root app or not) but it will show even the soft reboots that occur in the wee hours while you are asleep.
4, This is moved to Q&A
Good luck and I hope this gets worked out.
+1
Sent from my Nexus 10 using XDA Premium HD app
Ok... I'll stay patient. Really I was looking to make sure it wasn't something I did software wise in my setup. (I had to re-lock, to a clean reset of data/cache, finally get the .1 update, then unlocked again). (Still havn't rooted).
Someone mentioned google voice as having issues (which I suppose could go along with the location settings). I do have location off as far as GPS, but have been leaving it on for the other two checkboxes.
Thanks for the responses (and thanks for moving this thread to Q&A, sorry I posted in general!).

Google Services Wakelock

Hello everyone,
I seem to be having a very annoying Google Services Wakelock on my Nexus 4 Device.
It is using more battery power than the screen, and keeps teh phone alive 100% of the time.
I'm on PA 3.97 - 4.2.2 Android.
Better Battery Stats tells me under Partial Wakelocks that SystemUpdateService Is keeping the phone alive, as well as under Kernel Wakelock PowerManagerService.
I'm wondering what I can do about this. Because it is really eating my battery life. Google tried to update to 4.3 over and over again, which wasn't possible because I was on a custom rom. So it kept redownloading it and I was forced to disable the update system (I don't exactly remember how I did it, but since I have root I disabled UpdateReciever under updates somehow).
I hope we can find a way to fix this.
Bump! Still need a solution
Artego said:
Hello everyone,
I seem to be having a very annoying Google Services Wakelock on my Nexus 4 Device.
It is using more battery power than the screen, and keeps teh phone alive 100% of the time.
I'm on PA 3.97 - 4.2.2 Android.
Better Battery Stats tells me under Partial Wakelocks that SystemUpdateService Is keeping the phone alive, as well as under Kernel Wakelock PowerManagerService.
I'm wondering what I can do about this. Because it is really eating my battery life. Google tried to update to 4.3 over and over again, which wasn't possible because I was on a custom rom. So it kept redownloading it and I was forced to disable the update system (I don't exactly remember how I did it, but since I have root I disabled UpdateReciever under updates somehow).
I hope we can find a way to fix this.
Click to expand...
Click to collapse
You're getting the wakelock because you disabled the update service.
The only solution is to either enable it , and lose data, or update to 4.3
Artego said:
Hello everyone,
I seem to be having a very annoying Google Services Wakelock on my Nexus 4 Device.
It is using more battery power than the screen, and keeps teh phone alive 100% of the time.
I'm on PA 3.97 - 4.2.2 Android.
Better Battery Stats tells me under Partial Wakelocks that SystemUpdateService Is keeping the phone alive, as well as under Kernel Wakelock PowerManagerService.
I'm wondering what I can do about this. Because it is really eating my battery life. Google tried to update to 4.3 over and over again, which wasn't possible because I was on a custom rom. So it kept redownloading it and I was forced to disable the update system (I don't exactly remember how I did it, but since I have root I disabled UpdateReciever under updates somehow).
I hope we can find a way to fix this.
Click to expand...
Click to collapse
Maybe this:
http://forum.xda-developers.com/showthread.php?t=2385843
bringonblink said:
You're getting the wakelock because you disabled the update service.
The only solution is to either enable it , and lose data, or update to 4.3
Click to expand...
Click to collapse
We are literally talking about 20 000$ + of Data usage if I were to leave it on for a month.
Unless google wants to pay me that money every month I'd rather not have the update service on. Not to mentionhow much constant Data streams to download a file over and over again would drain teh battery.
Also, doesn't everyone with PA (3.97) who hasn't updated to 4.3 have this. I'm on a custom ROM so I shouldn't be forced to update to 4.3 anyways!
How come the battery is a wakelock when I entirely Disabled the service?
What other google services should I disable to make it stop entirely from even trying to update?
bringonblink said:
You're getting the wakelock because you disabled the update service.
The only solution is to either enable it , and lose data, or update to 4.3
Click to expand...
Click to collapse
Galaxo60 said:
Maybe this:
http://forum.xda-developers.com/showthread.php?t=2385843
Click to expand...
Click to collapse
That thread is about another Google Services Wakelock that has to do with the GPS. I never had that location setting on.
Mine has to do with it trying to update, thus keepiçng the device on, although the update service is actually disabled(since it doesn't actually download data).
Does anyone know how to completely disable the google update service in every way possible since that is what keeps my wakelock on.
I have absolutely no issue like you, i`am on 4.3 stock with stock kernel and no continious syncing going on bro and the cpu going into deep sleep without issues. Try reflashing to stock to see if the issue still excists.
gee2012 said:
I have absolutely no issue like you, i`am on 4.3 stock with stock kernel and no continious syncing going on bro and the cpu going into deep sleep without issues. Try reflashing to stock to see if the issue still excists.
Click to expand...
Click to collapse
That's because the issue has to do with ParanoidAndroid having a bug that it picks up the Stock 4.3 updates, downloads them and then fails to install them. I am on a 4.2.2 ROM, 4.3 of course won't have that issue since that is what it is trying to download. Also I really just want to keep this version of Paranoid Android.
So what I tried doing was disable the Google update service entirely a few weeks ago. And it has stopped trying to download any updates.
However, the past few days that same Google Update (which should be completely disabled) is still keeping my phone a alive, although not downloading anything anymore. I just wnat a way to completely just permanently kill the Update Process.
Artego said:
Hello everyone,
I seem to be having a very annoying Google Services Wakelock on my Nexus 4 Device.
It is using more battery power than the screen, and keeps teh phone alive 100% of the time.
I'm on PA 3.97 - 4.2.2 Android.
Better Battery Stats tells me under Partial Wakelocks that SystemUpdateService Is keeping the phone alive, as well as under Kernel Wakelock PowerManagerService.
I'm wondering what I can do about this. Because it is really eating my battery life. Google tried to update to 4.3 over and over again, which wasn't possible because I was on a custom rom. So it kept redownloading it and I was forced to disable the update system (I don't exactly remember how I did it, but since I have root I disabled UpdateReciever under updates somehow).
I hope we can find a way to fix this.
Click to expand...
Click to collapse
Hi
To avoid this bug: don't pull out the charger or usb cable whit out to wake up the phone, be sure the screen is on when you pull out. If you pull out with screen off powermanagerservice.wakelock will keep your phone to never enter deep sleep.
A reboot also solves the problem
Think this bug is related to the wireless charger bug.
Sent from my Nexus 4 using Tapatalk 2
RobertSand said:
Hi
To avoid this bug: don't pull out the charger or usb cable whit out to wake up the phone, be sure the screen is on when you pull out. If you pull out with screen off powermanagerservice.wakelock will keep your phone to never enter deep sleep.
A reboot also solves the problem
Think this bug is related to the wireless charger bug.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Ok, I guess that will already stop 1/2 wakelocks.
The other one has to do with the update service still keeping my device awake although it was disabled with disable service.
I think I was finally able to fix the issue!
I downloaded AutoRun Manager and disabled
com.android.gsf.update.SystemUpdateService$Reciever, which can be found under Google Services Framework,
I already had updates disabled using "Disable Service" app from Google Play Store, which did the job for stopping Data Usage, but there was still an idle process keeping the phone awake, which was the SystemUpdateServiceReciever.
I am on Paranoid Android and might want to Update to 4.3 due to them making continious new cool features which will only work for 4.3.
First off, I would like to ask if the update to 4.3 was worth the effort for you. It doesn't really seem to be a significant update on the side on the google dev team. Secondly, how would I go about doing it?
I am now on PA 3.69 - 4.22 which is one of the latest versions before the 4.3 update.
What do I need to do before I am able to flash 3.99 PA - 4.3? How do I avoid losing my appdata, my pictures and all that?
I paid for Titamiumbackup a few months ago but I don't really know how to use it and I'm a little scared to update to a different version number as I have never done that before, and I don't want to brick my phone.
What radios do I need to flash before being able to update to 4.3 based custom roms?
Artego said:
I think I was finally able to fix the issue!
I downloaded AutoRun Manager and disabled
com.android.gsf.update.SystemUpdateService$Reciever, which can be found under Google Services Framework,
I already had updates disabled using "Disable Service" app from Google Play Store, which did the job for stopping Data Usage, but there was still an idle process keeping the phone awake, which was the SystemUpdateServiceReciever.
I am on Paranoid Android and might want to Update to 4.3 due to them making continious new cool features which will only work for 4.3.
First off, I would like to ask if the update to 4.3 was worth the effort for you. It doesn't really seem to be a significant update on the side on the google dev team. Secondly, how would I go about doing it?
I am now on PA 3.69 - 4.22 which is one of the latest versions before the 4.3 update.
What do I need to do before I am able to flash 3.99 PA - 4.3? How do I avoid losing my appdata, my pictures and all that?
I paid for Titamiumbackup a few months ago but I don't really know how to use it and I'm a little scared to update to a different version number as I have never done that before, and I don't want to brick my phone.
What radios do I need to flash before being able to update to 4.3 based custom roms?
Click to expand...
Click to collapse
I'm on PA 3.99 with BaNkS GAPPS, which I highly recommend because of the size and stripped way they are. I think TitaniumBackup had some problems with PA and root, but I'm not sure if they already fixed those.
You need latest radio and bootloader to update, I think the easiest way to do this is to make a factory reset, full clean and wipe all data and then back to 4.2.2 stock ROM. Then update through OTA and you would have latest radio and bootloader. Install custom recovery and then flash latest PA.
I did it this way and I don't have any kind of problems.
:good:
Artego said:
I think I was finally able to fix the issue!
I downloaded AutoRun Manager and disabled
com.android.gsf.update.SystemUpdateService$Reciever, which can be found under Google Services Framework,
I already had updates disabled using "Disable Service" app from Google Play Store, which did the job for stopping Data Usage, but there was still an idle process keeping the phone awake, which was the SystemUpdateServiceReciever.
I am on Paranoid Android and might want to Update to 4.3 due to them making continious new cool features which will only work for 4.3.
First off, I would like to ask if the update to 4.3 was worth the effort for you. It doesn't really seem to be a significant update on the side on the google dev team. Secondly, how would I go about doing it?
I am now on PA 3.69 - 4.22 which is one of the latest versions before the 4.3 update.
What do I need to do before I am able to flash 3.99 PA - 4.3? How do I avoid losing my appdata, my pictures and all that?
I paid for Titamiumbackup a few months ago but I don't really know how to use it and I'm a little scared to update to a different version number as I have never done that before, and I don't want to brick my phone.
What radios do I need to flash before being able to update to 4.3 based custom roms?
Click to expand...
Click to collapse
i am facing the same problem too. Running 4.2.2 (sentinel rom 4.75). google services is draining a good 30% of my battery.
so disabling using AutoRun Manager managed to solve the wakelock problem due to SystemUpdateService? i used Disable Service app to stop the data usage, but wakelock remains.
chainer22 said:
i am facing the same problem too. Running 4.2.2 (sentinel rom 4.75). google services is draining a good 30% of my battery.
so disabling using AutoRun Manager managed to solve the wakelock problem due to SystemUpdateService? i used Disable Service app to stop the data usage, but wakelock remains.
Click to expand...
Click to collapse
Yes, exactly that. Disable service disabled. That stopped My data usage (luckily before the cap of My data plan, if I would have phone higher it would probably have costed me a few hundred dollars.).
The Google services drain remained and after about 10 hours of research I found I found out the receiver was still trying to download it, but didn't get access which caused a wake lock. In auto run manager search Google services framework and disable the googleupdatereciever and nothing else, keep everything disabled that is already disabled
Sent from my Nexus 4 using xda app-developers app
Thanks for sharing the solution! helped me on 4.1.2 after disabling only some of google's receivers/services with "Google Services Framework" in Rom toolbox
Better battery FTW!
Artego said:
Yes, exactly that. Disable service disabled. That stopped My data usage (luckily before the cap of My data plan, if I would have phone higher it would probably have costed me a few hundred dollars.).
The Google services drain remained and after about 10 hours of research I found I found out the receiver was still trying to download it, but didn't get access which caused a wake lock. In auto run manager search Google services framework and disable the googleupdatereciever and nothing else, keep everything disabled that is already disabled
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the tip! but im not gonna purchase the full version of rom toolbox just for that. google should do something about it on their side!
chainer22 said:
Thanks for the tip! but im not gonna purchase the full version of rom toolbox just for that. google should do something about it on their side!
Click to expand...
Click to collapse
Sorry if this is a grave dig, but I never recall paying for anything to be quite honest.
All apps were free.

Freeze on charge

I recently rooted and unlocked the bootloader on my Razr M and installed a nightly build of CyanogenMod (I like to live on the edge, I guess.) The first week or so with it was going great, no issues as far as I could tell.
Then I installed a social application that requires GPS location. I noticed that the first time after enabling this the phone would freeze when plugged in to charge. It would freeze to the point where hitting the wake up button wouldn't even activate the screen. Not always, but it has happened on several occasions. So now whenever I charge it (daily), I have to force reboot (hold down Up, Down, Power in that order.) Sometimes it'll even go through the process of "Optimizing Apps" as if they were all just installed.
Firstly, has anyone else experienced this? And if so, is there an "easy" workaround? I can't quite pinpoint how to reproduce the bug, though I've got 3 different Cleaning applications installed that are used daily. That in mind, it's unlikely this is a memory leak bug.
Second, if there's no "easy" workaround, when can one expect the next Stable build of CyanogenMod, if ever? Is it still in development? I see that the last Stable release for this phone was in 2013. It seems like I'll have to downgrade to an earlier build, but just want some input before I do it.
Thanks much in advance
Sounds like an issue with the app, not the ROM. You said yourself that the issues started AFTER installing that app. So, delete that app and report back. Also, a lot of those cleaner apps out there will just bork your phone if you're not careful.
Sent from my Nexus 5

OOS 10.3.x - Constant random crash to black screen then spinning dot

I am at wits end. Here's how my situation has unfolded:
- Was running OOS 10.3.2 international, bootloader locked stock on a T-Mobile 6T (been running solid since 9.0.11 MSM hack early last year, updated progressively as the "System Updates" have appeared)
- No customization or tweaks
- Starting late last week, phone has been (seemingly) randomly crashing to black screen, then to spinning dots, like its booting
- I have to Vol up + power to turn off, then reboot
- I captured a logcat of the crash, which may be useful to someone, I just see the system handling a notification, then a system level ANR happens, taking out the core system processes?
I have tried:
- Google/OP backup -> factory reset -> restore account, apps, calls, sms and settings -->> still crashing
- OP backup -> factory reset -> add as fresh account, restore OP bu apps, calls, sms and settings -->> still crashing
- OP backup -> MSM downgrade to 9.0.11 -> unlock bootloader -> install TWRP, Magisk, TWRP install 10.3.2 international -> fresh account, restore SMS messages, etc
After the last attempt, ran all morning without crashing (yay!), proceeded to utter the words to my son ,"hey, fixed my phone, no crashes!", phone crashes 5 minutes later
Then I thought, "well I just signed in to Firefox sync, maybe that's it??", uninstall Firefox. Hour later, crashes during a phone call.
Okay, then thought maybe its something goofy with stock kernel? Install Omega kernel. Crashes 2 hours later on another phone call.
It also seems to crash fairly consistently in my pocket, and I have noticed "Pocket Mode" does not work (overlay doesn't appear when covering proximity sense; sensor works, tested with an app)
Am I experiencing a flaking mobo or some other hardware issue? Please tell me no, I am at 16 months with this phone, so factory warranty is out (and 6 months to go on my payment plan/offer).
Before I try LOS 17.1 (and probably still get crashes :silly, thought I'd try asking for insight here. I have tried googling for similar issues and searching forum threads, but no dice. Thanks!
Well, I have an update here. I turned off "Pocket Mode" last night for giggles, and lo and behold, I have 20 hours up time with no crashes. Proximity sensor works, took several calls today and screen turns off when covering it. Also put phone in pocket regularly to test, no crashing.
Hopefully this helps anyone else with this strange issue. Kind of sucks that I am going to potentially butt call people, but, less pocket time these days while we're all stuck at home (COVID-19 "stay at home", for those reading this post years from now wondering what the heck I'm talking about).
Sad news, random reboots persist. Going to try LOS to rule out OOS (which I can't see it being since others would be complaining too). Hopefully its not hardware, but maybe I jacked my phone up by dropping it one too many times. We'll see.
hondoslack said:
Sad news, random reboots persist. Going to try LOS to rule out OOS (which I can't see it being since others would be complaining too). Hopefully its not hardware, but maybe I jacked my phone up by dropping it one too many times. We'll see.
Click to expand...
Click to collapse
LOS 17.1, random reboots persist . Thinking my phone is toast...
hondoslack said:
LOS 17.1, random reboots persist . Thinking my phone is toast...
Click to expand...
Click to collapse
Try this port rom from op7..
Working great ..easy to install and super stable
https://forum.xda-developers.com/oneplus-6t/development/rom-oneplus7-beta-2-t3971383
have the same exact proble mwith my sons onepus 6t tmobil version, it was ported over to oneplus 6t international version, so we could use it one att.. I done system hardware test and it shows no problem.. I too was thinking of installing lineage os, but I'm lost.. anyone chime in on good tutorial...
sderaps said:
have the same exact proble mwith my sons onepus 6t tmobil version, it was ported over to oneplus 6t international version, so we could use it one att.. I done system hardware test and it shows no problem.. I too was thinking of installing lineage os, but I'm lost.. anyone chime in on good tutorial...
Click to expand...
Click to collapse
Unfortunately I've pretty much confirmed mine was a bad motherboard. I bought a used one off eBay, and installed it yesterday. Phone is running so much better, no more crashes, and proximity sensor is working properly again.
If you want to give LOS 17.1 a shot, here's a good place to start: https://forum.xda-developers.com/oneplus-6t/how-to/guide-installing-lineage-t4075955
I found it mostly a frustrating ROM, as fingerprint and face unlock don't work. Call me lame, but I absolutely love picking my phone up, looking at it, and having access immediately. Then there's all the apps that hook into the fingerprint for quickly unlocking that you can no longer leverage (the unlock part, not the app). Anyway, up to you.
Since I upgraded my op to 10.3.2, my proximity sensor IS not working.

Categories

Resources