My Atrix's fingerprint sensor stopped working all of a sudden. Anybody experienced this?
Happend to me and restarting my phone seemed to be the trick
Sent from my MB860 using XDA Premium App
I have read about ppl having problems on the 83 FW thread. Are you on 57 or 83?
Same problem with mine today. Version 1.83
I've been on 1.8.3 for four days so far, and the fingerprint sensor seems to be working normally.
Perhaps you can go back and redo your fingerprint calibrations.
I'm on 4.1.57. Never rooted. I tried to re calibrate my finger prints and it the phone would not even sense it. bummer.
Same happens to me every so often. And restarting phone did fix it.
Sent from my MB860 using XDA App
Just happened to me for the first time ever. Just updated to 83 so i guess thats why.
I had the same thing happen to me today. Running .83. Rebooted the phone and it went back to normal
1.26 1.57 1.83 have the same problem.
Just config it again.
You guys tweaking your memory management?
Sent from my Motorola Olympus
If you happen to have your finger on the sensor when the phone is booting, the sensor gets confused and doesn't work.
Reboot and keep your finger off the sensor until the unlock screen and you should be fine.
fingerprint scanner going out for me once a day, reboot fixes it. for now i just shut it off. any permanent fixes or is it because of the latest 1.8 update?
Mine did the same thing after updating it to .83 and a reboot fixed it. One thing I noted was this happened whn the battery is below 20%. I initially thot it would come back after I a recharge, apparently I was wrong and had to restart. It is so annoying. Also, I am experiencing more battery drain after updating.
Sent from my MB860 using XDA App
I've had it refuse to see my finger from time to time, fewer times after each OTA update. I'm not happy about the freezes but this is the only phone with a finger reader, when it fails...pretend it is any other phone, use the passcode. I expect Moto to get this solved sooner rather than later because this is supposed to be a big feature for corporate sales and the attack on Blackberry's native security functions.
Whether it is a memory conflict (let's face it, Android apps are often ill-behaved and there's no one really doing qc testing on them) or an Atrix flaw...no choice but to wait either way.
Has anyone found a permanent fix for this? The Atrix is the first smartphone that my wife has owned and shes losing confidence in it. This is just one more thing that is on the list of problems shes had. My Atrix works fine, but her fingerprint reader stops reading once or twice per day and she has to reboot each time to get it working again.
I've had the same problem since 1.8.3--somebody suggested in another thread that it might be related to Titanium backup keeping settings from pre-update and trying to apply them?
I have to be honest that the fix suggestions were kind of over my head and I've just gone into settings and changed to a pattern instead of the fingerprint reader to avoid it.
My wifes Atrix keeps losing the fingerprint reader still. Maybe 2 times a day. Hers is not rooted. I took a closer look yesterday and looked at her running apps. She had a lot that were running and taking up a lot of memory. Could this be the problem? If she doest exit apps and just hits the home button will this cause the Atrix to use up its memory and lose the fingerprint function?
JohnnyDanger said:
My wifes Atrix keeps losing the fingerprint reader still. Maybe 2 times a day. Hers is not rooted. I took a closer look yesterday and looked at her running apps. She had a lot that were running and taking up a lot of memory. Could this be the problem? If she doest exit apps and just hits the home button will this cause the Atrix to use up its memory and lose the fingerprint function?
Click to expand...
Click to collapse
I have no idea if that could be related/the issue, but I guess it's worth a try, maybe install an app to auto-kill other apps. Something like advanced task killer, I used to use it (and it works well, no particular reason for uninstalling it) but now I just use juice defender and my battery life has increased a significant amount (I keep it on the default setting - using free version)
Every 2-3 days it happens and I have to reboot. When it fails, it doesn't scan your finger at all..
Related
My phone will randomly shut down and will not power back on unless I pull the battery, I have 2 batteries and it happens with either one. It does not shut down while on charger/dock. I have wiped the phone multiple times with odin, I've used several different roms/kernals,same results every time. Just curious if anyone else has been experiencing this issue.
I've been experiencing this after I went to eb13 with the custom kernels that are out. But my.phone will either lockup and I have yo pull the battery or it will reboot itself. Never had what happens to u yet.
Sent From My Evo Killer!
This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha
nalewis89 said:
This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha
Click to expand...
Click to collapse
I'm averaging 10 times a day myself
Permanent sleep
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.
before updating to 2.2 - I did the DK28 and now the EB13 one - with 2.1 I would have my phone randomly reboot - I would be sitting there and here the music it makes when it starts up but I never turned it off?
other times it would just be turned off, but when I turn it back on the abttery is not low enough to cause it to turn off
all this went away with DK28 2.2 and hasnet happened since I installed EB13 2.2
This happeed to me the other morning. I wasn't able to boot until I reflashed the kernel. Twilight frozen btw.
Sent from my SPH-D700 using XDA Premium App
My first epic would randomly hard power off, even running stock ROMs. If you are running a stock ROM and seeing a hard power off at random, I suggest you go swap the phone. It's just broken.
Ive never had this problem and im on my first and only epic and ive had it since it came out,
Ive been very careful with my epic as it has been great to me, it hates me probaly tho for feeding it stuff while experimenting things that make it spit up FCS,
But my phone has been always working perfect, all the way back to d118.
CLazman said:
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.
Click to expand...
Click to collapse
the buttons don't stay lit, i'm using twilight kernal right now but was happening with genocide kernal too, going back to eclair just to eliminate 2.2, ext4, etc.. to see if it's a hardware issue
First try
dk18 update.zip flash
Restored apps and data with my backup pro root
Random reboots, FC
Second try
Odin to dk18
Wipe x3
Restored apps and data with mybackup pro root
FC, music player force closing (doubletwist, stock and musicmod, poweramp worked though?), fc when trying to change ringtone or notification.
Started reading about others with the same issues and thought data backups were a reoccuring theme. Did a third try tonight and so far so good. Music players working, no force closings, keyboards working correctly, gps lock indoors. Its still early, problems might still popup, thought id share...
Latest froyotempt
Fresh backup with mybackup pro root
Wipe x3
odin eb13 prerooted (ctsy xda forum) same file from attempt 2. Did this x3 as well, read it in a thread somewhere...
backup apps only with mybackup pro root
All attempts were with genocide kernal.
So far so good, none of the previous bugs are apparent, so far... Those of you that are on the fence regarding doing the same, so far its worth the time.
Sent from my SPH-D700 using XDA App
I was thinking back-ups were part of the problem also, so I used odin and started all over from dl18 without restoring any data, same problem still occured
Still messing with my phone, everything that was broken seems to be fixed. Hopefully it stays this way...
Sent from my SPH-D700 using XDA App
That used to happened to me on eclair when I set my setcpu profiles too low when screen off. You wouldn't happen to be using setcpu would you?
actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800
I'll add to this thread. I seem to be having the same problem and I believe it started when I installed quantum rom... but I'm not sure. The symptoms i had were random reboots, where the screen would shut off and the 4 lights would stay on. Then I would have the sound of lost signal as if my phone rebooted and was starting over. Also, the most recent problem I get is my phone completely shuts off and I need to battery pull to get it to start up, and it loops on the splash screen of my rom. I have tried doing a complete odin wipe and not restoring anything and I believe it is still happening...
joedig52 said:
actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800
Click to expand...
Click to collapse
Any update?
Also, make sure the governor isn't "powersave". If you have 100-400MHz powersave governor, it still ONLY runs at the lowest speed (100MHz), even if it's 100-400MHz.
Still happening, not on powersave, doesn't matter what settings I have in set cpu. Did a hard reset back to 2.1 and it still happens, bringing it in for repair.
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
FYI for WidgetLocker lovers..........the latest update has fixed the issues where the fingerprint scanner did not work on the WidgetLocker screen. The fingerprint scanner now unlocks and takes you right to your home screen. If you use the slider bar in WidgetLocker, it no longer takes you to the normal lock screen, but brings up the code unlock screen instead as the regular lock screen does. I have checked this multiple times on my phone on 4.1.83, GladiAtrix, and Cool Blue.
WidgetLocker Market Link
You do have to swipe the scanner a wee bit slower it appears, almost like Atrix was prior to 4.1.57 update, but other than that it works fine.
+1 Yea noticed that been using it again with no problems as well ^_^
Sent from my MB860 using XDA App
It worked for me only half a day, then it was back to its old tricks. I'm bummed because I was really hoping this would fix it.
i just tried widgetlocker for the first time yesterday. It was nice and definitely modifiable (word?) but it slowed down my phone ever so slightly.
badnokia said:
It worked for me only half a day, then it was back to its old tricks. I'm bummed because I was really hoping this would fix it.
Click to expand...
Click to collapse
It happens to me also.
Sent from my Chuck Norris powered PRO RED DXblurred Atrix
badnokia said:
It worked for me only half a day, then it was back to its old tricks. I'm bummed because I was really hoping this would fix it.
Click to expand...
Click to collapse
When did you update? There was an update yesterday or the day before which did not address this particular issue. The update today wasn't there earlier because I check several times a day for Market updates out of boredom. It appeared this evening in the Market for me. Working great for me now.
Also, how fast are you swiping on the reader? You can't swipe as fast as when not using WidgetLocker.
blunted09 said:
i just tried widgetlocker for the first time yesterday. It was nice and definitely modifiable (word?) but it slowed down my phone ever so slightly.
Click to expand...
Click to collapse
When you say slowed down your phone..............in what way? I know it slows down unlocking slightly, but I notice no other slow downs once the phone is unlocked.
CaelanT said:
When did you update? There was an update yesterday or the day before which did not address this particular issue. The update today wasn't there earlier because I check several times a day for Market updates out of boredom. It appeared this evening in the Market for me. Working great for me now.
Also, how fast are you swiping on the reader? You can't swipe as fast as when not using WidgetLocker.
Click to expand...
Click to collapse
I updated this morning. I just checked the market again just now & no additional update was available; I'll check back again later. Re: swipe speed, I'd say I didn't change my speed at all. Again, that seemed to not be a problem for ~1/2 a day.
The only known issue right now is that Exchange can break things. I'm working on a method for rooted Exchange fingerprint scanning users to bypass this (the trick actually allows for some other things too so it's not as niche of a group as it sounds), but it requires manual XML changes right now and could mess up your system. When it's wrapped into an apk and ready for user testing I'll post somewhere in the Atrix section to let you guys know.
If you're not using Exchange (or a similar device admin that "Requires password") and having issues with it not working in cases that the Motorola lock screen would, then Settings > Report Bug and provide as much details as you can about when it's not working.
mine doesn't work at all anymore now. before, it would work about 50% of the time, now no response at all. i tried rebooting, clearing my lock screen settings and re-enabling fingerprinting, etc. no dice.
Sent from my MB860 using XDA App
dLo GSR said:
mine doesn't work at all anymore now. before, it would work about 50% of the time, now no response at all. i tried rebooting, clearing my lock screen settings and re-enabling fingerprinting, etc. no dice.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Same here. Mine was working, now it's completely unresponsive. Back to the stock lock screen.
I am one of the elusive Exchange users he mentioned though...
is anyone else having problems? i can't get it to work AT ALL. i've uninstalled, reinstalled, rebooted, gone through every setting in the settings menu... what gives?
dLo GSR said:
is anyone else having problems? i can't get it to work AT ALL. i've uninstalled, reinstalled, rebooted, gone through every setting in the settings menu... what gives?
Click to expand...
Click to collapse
Still not working consistently enough for me to continue using...bummer... I've been back to stock lock for awhile now & waiting for next update with fingers crossed.
ok i think i've narrowed it down.
if you set a FP profile, and use a PIN, then it will work. BUT if you are using the pattern unlock and the FP (which you can set by setting as pattern first, then FP with existing profile), it will not work.
dLo GSR said:
ok i think i've narrowed it down.
if you set a FP profile, and use a PIN, then it will work. BUT if you are using the pattern unlock and the FP (which you can set by setting as pattern first, then FP with existing profile), it will not work.
Click to expand...
Click to collapse
I use FP with pin, so maybe you have hit on something there, as I have no issues with it.
yup, confirmed it's true with the dev, and also that it's Motorola's fault.
"I did notice this in testing, however Motorola does not support the Fingerprint scanner with Pattern so I decided not to either. What you found is unintentional and may have issues on it's own (I haven't tried with the latest firmware, but I had played with that setup on the original firmware and found it unreliable. Setting a delay with the Fingerprint scanner (via sqlite) also caused weirdness).
With regard to WidgetLocker, there's some code in there to handle Motorola's pattern and some other code to handle Motorola's fingerprint scanner. I did try to get both to work, but in limited testing was unable to do so and since it's not officially supported by Motorola I decided not to pursue further. (I actually also thought they fixed the loophole you found in the later firmware so the only way of doing it was sqlite, but apparently I was wrong)"
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
Since DOK2 is new and there are several hopes from many of the new firmware, I figured it would be best to make a thread about it.
To those on DOK2 (Especially 100% stock, i.e. stock kernels), please post your feedback.
One of the main things to look for is directed at FingerPrint unlock users.
After enabling FingerPrint unlock does the phone randomly lock itself?
Does the FingerPrint crash / TouchWiz crashes?
(This should be apparent with in the first 24 hours of enabling the FingerPrint lock)
The next main thing to look for is just general issues after the phone being on for some time. This would indicate memory management issues and would show up after hours / days with out a restart.
Are you loving the new Firmware? Post about that too!
Your feedback is valuable so please take the time out to post your experiences with DOK2.
Thanks!
I'm loving the new firmware. The phone "feels" faster in switching between applications.
The fingerprint lock-screen bug is gone (for me). Memory management has improved drastically. The only thing that is the same is the battery life in power saving mode. The update is worth it for me, so I'm not as eager as I was before to get marshmallow as I was before.
Note: This phone has never been rooted
I got the update and noticed a few bugs here and there. I fully wiped twice and it resolved everything. It's smoother, faster, same battery life, keyboard and fingerprint bugs fixed. I really like it so far. It runs like it should. I'm a happy camper now.
I've never rooted, full stock.
Remember to go to options > storage and clear your cache after updating! From COG2 to DOK2 I have never had fingerprint unlock issues. If anything it seems more accurate and faster. There is more ram I fall between 1.7-1.8gb (instead of ~2gb) used when everything is cleared. There has been no random reboots since the update. There is no more weather widget re-sizing itself and black shadowed font while scrolling through home screens. My antutu score went from 52000 to 48000 though. I am 100% stock never been rooted.
I've heard tell that you can't downgrade your bootloader back to COG2 after installing DOK2 update. Any word on this? Even through Odin?
^Even if you can't, why would you want to? 5.1.1 is better in every way from 5.0.1
My computer will not recognize my phone via sub after the upgrade
chocolatet said:
My computer will not recognize my phone via sub after the upgrade
Click to expand...
Click to collapse
sub? I assume you mean usb.. Did you wipe/reset everything? Even though this is an official update dirty flashing is dirty flashing. Wiping is still a troubleshooting step.
Love it so far.
The one thing that I have noticed is that the task switching is much faster. When I used to press the button, it would take a few seconds to load, now it's pretty much instantaneous.
I tried turning on the fingerprint unlock, but I was still having too many swipes to get it to unlock, so I turned it back off.
Techngro said:
The one thing that I have noticed is that the task switching is much faster. When I used to press the button, it would take a few seconds to load, now it's pretty much instantaneous.
I tried turning on the fingerprint unlock, but I was still having too many swipes to get it to unlock, so I turned it back off.
Click to expand...
Click to collapse
When you register you finger do you swipe at different angles each pass?
That is a must. My fingerprint scanner (when not crashing) works flawlessly. I never have had a problem with swipes.
DeeXii said:
When you register you finger do you swipe at different angles each pass?
That is a must. My fingerprint scanner (when not crashing) works flawlessly. I never have had a problem with swipes.
Click to expand...
Click to collapse
Yeah, I did that. I did it one time and then I did it a second time with different angles.
Can anyone address if their GPS accuracy has improved?
Test
Sent from my SM-N910T using Tapatalk
Test 2 shy did it add a to my name
Sent from my SM-N910T using Tapatalk
Data speeds are much improved with the update. The device is snappier also. I haven't noticed a difference in GPS - seems about the same as before the update. Haven't had time to gauge battery life fully but that also seems improved.
Over all a very well put together update. I'm pleased.
I haven't rooted yet and I'm not sure I want to take this update yet. How can I turn off the auto update feature? The phone is telling me it wants to download the update and the next time I connect to wifi it will. Is there any way to prevent this?
Thanks
Rootabaga said:
I haven't rooted yet and I'm not sure I want to take this update yet. How can I turn off the auto update feature? The phone is telling me it wants to download the update and the next time I connect to wifi it will. Is there any way to prevent this?
Thanks
Click to expand...
Click to collapse
WARNING if you update your tmobile note 4 from 4.4.4 or 5.0.1 to 5.1.1 lollipop then dont do it. problems are the phone download super slow even if your on the best internet connection or using your own data. and if you like 4.4.4 or 5.0.1 then you will not be able to downgrade back to them. its no way to downgrade at all. im trying to sale mine on craigslist and get another one now
So weird, I installed it yesterday, rooted, and loaded a ported version of Kyubi's ROM. It's an awesome ROM, but too laggy on n910t. Reinstalled DOK2, and I canNOT root it again via Odin 10.7 or 10.3. It loads, and then goes into a boot loop. I've tried like, 5 times. Kinda sucks
Michael in ATL said:
So weird, I installed it yesterday, rooted, and loaded a ported version of Kyubi's ROM. It's an awesome ROM, but too laggy on n910t. Reinstalled DOK2, and I canNOT root it again via Odin 10.7 or 10.3. It loads, and then goes into a boot loop. I've tried like, 5 times. Kinda sucks
Click to expand...
Click to collapse
I just learned this recently, so I guess it's my turn to pass this information to others.
You need custom kernel to be able to root. Flash BeastMode Kernel by @freeza.