I've set up fingerprint sensor to unlock my edge (FY), but since I've updated to MM 6.01 every now and then (or after restarting the device) Android insists on entering the backup password.
EDIT:
I've noticed that it requires the password always after having been automatically restarted.
After updating to MM it worked fine for some days, but the longer I have used it the more often it freezes and reboots. Now there is no chance to navigate with maps and listen to music for longer than 20 min. and bang! freezes, reboot, password!
Anybody else having this problem? Any solution to this? Of course, I have fully wiped, reflashed the MM-firmware again and again, but still no clue.
EDIT 2: Downgraded to 5.1.1, the phone is useless with MM
EDIT 3: Seems NOT solved by the latest FW "DJ1"
Edit 4: Solved with DPK2 Firmware via Kies
I'm having the same issue as well, its also just randomly requires me to enter it sometimes too.
Does yours pop up the SD card emblem as well and tell you its for media and pictures?
Sent from my SM-N915P using XDA-Developers mobile app
I am getting the password prompt when not rebooted, the SD card issue and my night clock is broken. Reallly peeved at this.
Otherwise, I am loving Marshmallow... unfortunately for me, the above are deal breakers for me. If these issues don't get fixed, someone will be replacing my phone.
TADitto said:
I'm having the same issue as well, its also just randomly requires me to enter it sometimes too.
Does yours pop up the SD card emblem as well and tell you its for media and pictures?
Sent from my SM-N915P using XDA-Developers mobile app
Click to expand...
Click to collapse
Yap, SD-card popup also. I've sometimes serious lags (not very often) up to a complete freeze of the device, which sorts itself out by just waiting some 10 minutes or so.
I believe that it has to do with the new Google maps app voice . I deactivated it and run the test now whether it solves the prob or not. Until disabled vocal guide in maps yesterday no freeze or backup password request appeard. Keep fingers crossed.
EDIT: I can replicate the reboot, it always appears when maps is running. Makes the phone nearly unusuable.
The phone is soft-rebooting.
There's something seriously wrong with the MM builds currently out for Note Edge devices.
Hi lads
I've exact same behaviour with my SGN Edge after OTA update to MM 601 like TADitto in #2 and others;
randomly asking me for backup password instead unlock by finger also pop up on the top bar the SD card
emblem as well and tells to me its for media and pictures, and got self rebooting at least twice too since week time
so think is to early to get some solution for the moment and nothing else to do just wait for fix the issue shortly
- fingers cross
regards all XDA members
I returned to 5.11 today, way more reliable, no reboots, fingerprint working. I will wait for a bugfree release of MM.
Did you tried downgrading back to kitkat from marshmallow, because bootloader was locked in lollipop 5.1.1 and don't allow to downgrade back to kitkat from lollipop. I heard marshmallow has unlocked bootloader.
---------- Post added at 05:28 AM ---------- Previous post was at 05:25 AM ----------
charly-whiskey said:
I returned to 5.11 today, way more reliable, no reboots, fingerprint working. I will wait for a bugfree release of MM.
Click to expand...
Click to collapse
Did you tried downgrading back to kitkat from marshmallow, because bootloader was locked in lollipop 5.1.1 and don't allow to downgrade back to kitkat from lollipop. I heard marshmallow has unlocked bootloader.
charly-whiskey said:
I returned to 5.11 today, way more reliable, no reboots, fingerprint working. I will wait for a bugfree release of MM.
Click to expand...
Click to collapse
But 5.1.1 has also got a problem in which it often freezes when you are using fingerprints as your lockscreen. Have u got some solution for this issue so that I can also revert back to 5.1.1?
Raja7142 said:
But 5.1.1 has also got a problem in which it often freezes when you are using fingerprints as your lockscreen. Have u got some solution for this issue so that I can also revert back to 5.1.1?
Click to expand...
Click to collapse
vrindavan_b said:
Did you tried downgrading back to kitkat from marshmallow, because bootloader was locked in lollipop 5.1.1 and don't allow to downgrade back to kitkat from lollipop. I heard marshmallow has unlocked bootloader.
---------- Post added at 05:28 AM ---------- Previous post was at 05:25 AM ----------
Click to expand...
Click to collapse
I fully wiped my note, flashed 5.1.1 from Sammobile, and there is and was no problem at all. My fingerprint button works nice, since I have registered my fingers from every angle I could move it. No prob, works flawless.
Thanks for your reply...Samsung has released a new update for SM-N915G model in India yesterday with CSC "N915GODD1DPE1" . Has anyone tried it. If yes then please let me know if it solves this issue?
Sent from my SM-N915G using XDA-Developers mobile app
If you restore data from recovery it wont be able to copy your fingers print data. So remove finger print data and then flash mm then register your finger print again
Hi. I tried this and my phone is still asking for my password on reboot. Annoying but not a deal breaker. Would be good to solve it though
Sent from my SM-N915G using XDA-Developers mobile app
btrmpt said:
Hi. I tried this and my phone is still asking for my password on reboot. Annoying but not a deal breaker. Would be good to solve it though
Click to expand...
Click to collapse
Are you on N915GODD1DPE1? Would be interesting to know if the error still occurs in the DPE1 version.
Yes I'm on the DPE1 version.
Sent from my SM-N915G using XDA-Developers mobile app
So, yesterday I've got the OTA for DBT Germany N915FYXXU1DPC3, installed, first impression is fine.
BUT: still the pain with password request. Phone was powerd on all night, and on charger, but when my alarm rang this morning, I had to enter the backup password before I could switch off the alarm.
WTF do you think, SAMSUNG, about the pleasure I feel fighting with my phone in the dark, not finding my glasses to read what is required to switch the alarm off, and fumbling the cryptic password (which I am forced to use) into a keyboard I cannot even read at 5 am? Ah, ok, its only to my protection. Thnx.
It happen to me too. I thought my phone restarted since it did says that the password require when the phone restarted until yesterday when I'm in a middle of exploring my setting, the screen went dark for about 2 secs and then comes back asking me to enter a password instead of fingerprint. Is it MM issue?
Sent from my SM-N915F using Tapatalk
---------- Post added at 08:00 AM ---------- Previous post was at 07:55 AM ----------
Has anyone tried to factory reset? Mind to share your result on the issue?
Sent from my SM-N915F using Tapatalk
Well in the meantime there is a
N915FXXU1DPE3
and
N915FXXU1DPE4
Any news about a bugfix with this firmwares?
@Nahtiayhs : I installed MM DPE1 from scratch and the bug still occurs
Nahtiayhs said:
It happen to me too. I thought my phone restarted since it did says that the password require when the phone restarted until yesterday when I'm in a middle of exploring my setting, the screen went dark for about 2 secs and then comes back asking me to enter a password instead of fingerprint. Is it MM issue?
Sent from my SM-N915F using Tapatalk
---------- Post added at 08:00 AM ---------- Previous post was at 07:55 AM ----------
Has anyone tried to factory reset? Mind to share your result on the issue?
Click to expand...
Click to collapse
Yes, this is the bug. And it is still there with DPE3. MM reboots from time to time by itself, hangs for some minutes, then requests the pw-input. Most of the reboots happen to me when I drive using Maps, listening to Power Amp music via Bluetooth - that ends up nearly always with a silent reboot.
me too.
after install latest security pack this happen to me?
how i can unistall this patch? or how i can install clean MM without this update patch? may download rom from sammobile and flash on my phone can rescue me?
Related
Need help. I have troubles with light sensor and proximity sensor after update to lollipop. After updating in fastboot mode (without any errors) these sensors don't work until I restart my nexus. After restarting sensors are working just a few minutes (5-10) and all repeats...
I tryed to downgrde android to 4.4.2, 4.4.3, 4.4.4 - in all of them sensors are working.
Please tell me what can i do to solve this problem!
Same problem!!
I too have this same problem after the update!
dmtcher said:
Need help. I have troubles with light sensor and proximity sensor after update to lollipop. After updating in fastboot mode (without any errors) these sensors don't work until I restart my nexus. After restarting sensors are working just a few minutes (5-10) and all repeats...
I tryed to downgrde android to 4.4.2, 4.4.3, 4.4.4 - in all of them sensors are working.
Please tell me what can i do to solve this problem!
Click to expand...
Click to collapse
same here
dmtcher said:
Need help. I have troubles with light sensor and proximity sensor after update to lollipop. After updating in fastboot mode (without any errors) these sensors don't work until I restart my nexus. After restarting sensors are working just a few minutes (5-10) and all repeats...
I tryed to downgrde android to 4.4.2, 4.4.3, 4.4.4 - in all of them sensors are working.
Please tell me what can i do to solve this problem!
Click to expand...
Click to collapse
same here !!!
if i restart the phone its work for few mintues
Weird because I don't have this issue. However I had to perform a factory data reset through stock recovery because my internal storage was reading 16gb not 32gb. I mention this because maybe that'll help u. Plus I'm completely stock so far.
Have the same issue. Its so annoying. My brother and i did the updates on 2 phones. Mine has the issue, his is working fine. Any solution
I'm having the same issue, I pushed the OTA update via ADB first and has this issue. Then i tried A factory reset and still had it. Then I tried flashing the factory image using fastboot and I'm still having this problem. Everything else seems to be working great.
Do you guys think its an app related issue?
I don't think so, i booted into safe mode and still had this problem, unless the issue is being caused by a native app.
Yeh tried that too. Same thing. How come my brothers phone is fine tho
I don't know man, hopefully someone with a bit more knowledge will be able to help us out, glad I'm not alone though lol.
I fixed mine! I just needed to re-install my factory image manually. Follow the directions in this thread and use method 2.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
SlickNolte said:
I fixed mine! I just needed to re-install my factory image manually. Follow the directions in this thread and use method 2.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
I thought I do that on my phone too with no success. I used the nexus toolkit tho. Does it make a difference
*EDIT*
Never mind, it's still broke, I let the phone sit for about an hour and when I came back the sensor wasn't responding again.. I give up.
SlickNolte said:
I fixed mine! I just needed to re-install my factory image manually. Follow the directions in this thread and use method 2.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
is it working still. i just got home, about to attempt it
---------- Post added at 07:43 PM ---------- Previous post was at 07:06 PM ----------
haroyac said:
is it working still. i just got home, about to attempt it
Click to expand...
Click to collapse
what if it is an application that is causing this?
No sorry, it took about an hour but the problem came back. I didn't have any apps downloaded yet and it still happened. I would try though, can't really hurt anything. Maybe it will work for you. I'm just tired of rebuilding my whole phone every time, I'm going to ride it out maybe someone will figure something out.
Can you guys try disabling google play services. I have it disabled for 30 min now and looks like its kk
Is yours still working? I just tried this and besides making the phone generally unusable it did nothing, sensors still didn't work. I think I may flash back to 4.4.4, I'm really tired of all this tinkering just to get things working correctly.
Nope. Didn't work. Is your phone a replacement phone by any chance? I called google they acknowledged a firmware bug. They will get back to me soon
No, mine is a launch device. Did they tell you any specifics?
Sensors work fine for me.
Hi,
After updating to 7.0 nougat by official Europe update,
My fingerprint sensor stopped responding, when I'm trying to add new fingerprint it wouldn't let me even try, It shows a message (Attention: make sure that the home key is clean and dry, then try again) and then it goes back to the main lock screen settings menu.
I'm really desperate, already tried everything, plz help!
:crying:
Ronohayon10 said:
Hi,
After updating to 7.0 nougat by official Europe update,
My fingerprint sensor stopped responding, when I'm trying to add new fingerprint it wouldn't let me even try, It shows a message (Attention: make sure that the home key is clean and dry, then try again) and then it goes back to the main lock screen settings menu.
I'm really desperate, already tried everything, plz help!
:crying:
Click to expand...
Click to collapse
Have you tried to factory reset or just flash android 7.0 with Odin. I would recommend wiping after installing an update like 7.0 anyway updating always causes bugs and issues for me.
dylanneve1 said:
Have you tried to factory reset or just flash android 7.0 with Odin. I would recommend wiping after installing an update like 7.0 anyway updating always causes bugs and issues for me.
Click to expand...
Click to collapse
I also just updated my SM-G935FD via OTA to Android version 7.0.
Since then, fingerprint scanner is not working. Like for OP, all tests fail under HwModuleTest.
I tried to remove all fingerprints, but it is impossible to add new fingerprints - the error message is "Make sure that the Home key is clean and dry, then try again." Obviously, the fingerprint sensor is as dry and clean as it was before the update (when it worked perfectly).
Since then I tried, unsuccessfully:
- removing old fingerprints and adding new fingerprints (does not work, cf. above)
- formatting cache partition
- performing a hardware reset
- flashed the stock firmware G935FXXU1DQB3 with Odin
Please advice, thanks.
happiness_is_a_process said:
I also just updated my SM-G935FD via OTA to Android version 7.0.
Since then, fingerprint scanner is not working. Like for OP, all tests fail under HwModuleTest.
I tried to remove all fingerprints, but it is impossible to add new fingerprints - the error message is "Make sure that the Home key is clean and dry, then try again." Obviously, the fingerprint sensor is as dry and clean as it was before the update (when it worked perfectly).
Since then I tried, unsuccessfully:
- removing old fingerprints and adding new fingerprints (does not work, cf. above)
- formatting cache partition
- performing a hardware reset
- flashed the stock firmware G935FXXU1DQB3 with Odin
Please advice, thanks.
Click to expand...
Click to collapse
If you have tried to flash stock firmware in Odin, I'm really not sure what the issue is, if it was just a glitch in the software it should probably have been fixed by a wipe and flash with Odin. If your phone is still under warranty I would bring it back into the Samsung shop or contact them over the internet to inquire about fixing it.
The same exact problem has happened to me too . I'm tired of unlocking with patterns
What should we do ?
This cannot be a hardware issue cuz phone was fine right before the update
---------- Post added at 08:16 AM ---------- Previous post was at 08:15 AM ----------
Ronohayon10 said:
Hi,
After updating to 7.0 nougat by official Europe update,
My fingerprint sensor stopped responding, when I'm trying to add new fingerprint it wouldn't let me even try, It shows a message (Attention: make sure that the home key is clean and dry, then try again) and then it goes back to the main lock screen settings menu.
I'm really desperate, already tried everything, plz help!
:crying:
Click to expand...
Click to collapse
Do you still have the issue ?
I have the same problem ???
What the way to fix this issue
I had that problem sometimes and in the end the main reason was really sweat on my fingers and dirt on the home button.
I know this doesn't sound like a solution, but it surprised me as well. Just try drying your fingers and clean the surface of the home button.
Hi There! I encountered the same issue earlier but then suddenly my fingerprint sensor works normally. The last thing I that I made changes to my phone was to reset the password of my samsung account. Not if there was a security breach that happened but after resetting the password, works fine for me. I suggest that you back up your phone's data before and after resetting your Samsung account.
I have this problem for 1 year, tried to change the password but didnt work.
IS someone still struggling with this problem ? Yesterday i upgraded to DevBase 6.0 Oreo newest build. But after the flashing process the fingerprint sensor act in a unusual manner. Sometimes i could unlock the phone sometimes it directly jumps to the pattern unlock screen. Any news about the problem ? I wiped cache/dalvik and i resetted my password of the samsung account - nothing helps.
Any help, ideas, links are highly appreciated
Cheers
Rhonin
yesterday I got it happened again: one of my sim cards suddenly lost signal. completely. and since then it keeps happening so randomly. please help!
im currently on oreo 41.3.A.2.75, BL unlocked, kernel packed by serajr's tool using ta_poc method with my own original TA, magisk installed, systemlessly xposed. i got it all working fine. until this issue happened.
i've also tried different ways: reflash, wipe data completely including sdcard, switch to DRMfix method, remove app by app, remove xposed... even switching SIM slots.... no luck so far.
about the issue, it just happens randomly without any clue. one of my SIM card just disappears. sometimes this one, sometimes the other. until now the only way is restart and pray it won't happen again.
please help! please!
What version of magisk are you using?
snake218 said:
What version of magisk are you using?
Click to expand...
Click to collapse
it's v16 stable
boydzethuong said:
yesterday I got it happened again: one of my sim cards suddenly lost signal. completely. and since then it keeps happening so randomly. please help!
im currently on oreo 41.3.A.2.75, BL unlocked, kernel packed by serajr's tool using ta_poc method with my own original TA, magisk installed, systemlessly xposed. i got it all working fine. until this issue happened.
i've also tried different ways: reflash, wipe data completely including sdcard, switch to DRMfix method, remove app by app, remove xposed... even switching SIM slots.... no luck so far.
about the issue, it just happens randomly without any clue. one of my SIM card just disappears. sometimes this one, sometimes the other. until now the only way is restart and pray it won't happen again.
please help! please!
Click to expand...
Click to collapse
Bro I'm having the same, loosing randomly my second sim card... Thought it was caused by some apps abusing of phone permission, but no luck it's not that. I cleared cache and art yesterday, now it's has not happened, but I guess it will happen again soon
Tonio78r said:
Bro I'm having the same, loosing randomly my second sim card... Thought it was caused by some apps abusing of phone permission, but no luck it's not that. I cleared cache and art yesterday, now it's has not happened, but I guess it will happen again soon
Click to expand...
Click to collapse
it will, unfortunately. i tried almost everything except uninstall magisk, lose root and restore TA & stock image. maybe it will fix the problem but whats the point if we no longer have root right?
back to nougat it was running flawlessly so i have a doubt that it has something to do with the combination of oreo + magisk + ta_poc method but i have no idea.
in ta_poc method i see it executes something like ua_modem_switcher. does it has something to do with modem?
@serajr you mind having a look pls. sorry to bother you the master but im running out of hope...
boydzethuong said:
it will, unfortunately. i tried almost everything except uninstall magisk, lose root and restore TA & stock image. maybe it will fix the problem but whats the point if we no longer have root right?
back to nougat it was running flawlessly so i have a doubt that it has something to do with the combination of oreo + magisk + ta_poc method but i have no idea.
in ta_poc method i see it executes something like ua_modem_switcher. does it has something to do with modem?
@serajr you mind having a look pls. sorry to bother you the master but im running out of hope...
Click to expand...
Click to collapse
Yes, removing magisk will lead to loose root access. But we can keep SONY features with kernel and TA.
The idea is :
-trying running stock OREO without root
-then adding custorm kernel with or without TA (original or drm_fix)
-at least adding magisk
I guess we need to try each step for a while
Maybe Serajr will have an idea, on my side i will try these steps and report...
highly appreciate that. i will do some more testings on my side too. the point is, although i know it will happen eventually but it happens so unpredictably its not easy to reproduce.
it may sound odd but you're here so i can at least hope it is just a software problem not hardware.
I was never be able to get my xz working with magisk 15 or 16. Always get the sim not recognized problem, maybe yours is magisk related.
snake218 said:
I was never be able to get my xz working with magisk 15 or 16. Always get the sim not recognized problem, maybe yours is magisk related.
Click to expand...
Click to collapse
Hmmm how come? Try this yet? https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
Both ta_poc and drmfix working.
hmmm anyone?
boydzethuong said:
hmmm anyone?
Click to expand...
Click to collapse
My phone is working fine for some days so far. Just cleared cache and dalvik as I mentionned earlier. BTW before doing this I've updated my Magisk from 15.3 to 16 without clearing anything (maybe the problem is related). Will report soon if it's still working or not...
Tonio78r said:
My phone is working fine for some days so far. Just cleared cache and dalvik as I mentionned earlier. BTW before doing this I've updated my Magisk from 15.3 to 16 without clearing anything (maybe the problem is related). Will report soon if it's still working or not...
Click to expand...
Click to collapse
I did that, many times. clearing cache and dalvik seems do the trick. but it actually doesn't. it will work for a few days and the issue will happen again. unfortunately.
by the way I spent some times paying high attention to the screen just to wait for it to happen. It looks like the moment when it happens, SystemUI (or Home Launcher I dont know) is terminated (stopped) then I am brought back to lock screen and at that moment, one of my SIM gone. So to me it looks like a service (or an app) is terminated and isn't restarted properly?
have you tried using stock rom and see if the problem persists?
Damaged motherboard.
I had the same with my xz so buyed a new XZs and throw away my xz
Sent from my Sony Xperia XZs using XDA Labs
Pandemic said:
Damaged motherboard.
I had the same with my xz so buyed a new XZs and throw away my xz
Sent from my Sony Xperia XZs using XDA Labs
Click to expand...
Click to collapse
oh nooo!!!
Pandemic said:
Damaged motherboard.
I had the same with my xz so buyed a new XZs and throw away my xz
Sent from my Sony Xperia XZs using XDA Labs
Click to expand...
Click to collapse
@Pandemic hmmm im not saying i dont believe but how do you explain it runs just fine for days after restart? usually 2 3 days then it happens.
and like i said the moment when it happens it looks like the whole systemui and running apps get force stopped.
lets say im playing a game then it becomes a bit laggy like its running out of memory then everything just closed then im brought back to lock screen and one of the signal indicator on status bar disappears.
do you happen to know any command that can restart the modem / cell / signal service? or any services related? just wanna try to manually execute it see if it fixes it.
also wanna mention again that im using ta_poc method for the drm sh!ts and it does have something like ua_modem_switcher executed. no idea whether it could be related
Hy guys, juste a quick update, my phone was working fine until 2/3 days. I've removed magisk but problem still happening, even clearing cache and dalvik didn't fixed it. My guess is, it could it be app related or crash due to RAM to high (my ram usage average is about 2.5 Go/day)...
Hi guys,
I have the same issue on a Note 4 (sm-n910f)....
I have been flashing roms in a long time and this is the first time it happens to me.
For me, the phone shows some lag, it auto restarts and the signal is lost. I can get it back by clearing delvik and cache, but this will happen at least twice a day.
I flashed stock and the problem goes away, does not happen even once on stock. So this tells me its not a hardware issue (i was so close in thinking its a motherboard issue)...
From reading various threads on this, i get to the conclusion that it is not device specific.
I have flashed half a dozen roms and only stock eliminates the issue. I stayed on stock for 3 days no issue, then reflashed lineage 15.1 and the problem is back. The really weird part is that this happened suddenly, not after a new flash or any operation on the phone.
Anyone figured this out?
---------- Post added at 07:20 PM ---------- Previous post was at 07:14 PM ----------
vasilis_84 said:
Hi guys,
I have the same issue on a Note 4 (sm-n910f)....
I have been flashing roms in a long time and this is the first time it happens to me.
For me, the phone shows some lag, it auto restarts and the signal is lost. I can get it back by clearing delvik and cache, but this will happen at least twice a day.
I flashed stock and the problem goes away, does not happen even once on stock. So this tells me its not a hardware issue (i was so close in thinking its a motherboard issue)...
From reading various threads on this, i get to the conclusion that it is not device specific.
I have flashed half a dozen roms and only stock eliminates the issue. I stayed on stock for 3 days no issue, then reflashed lineage 15.1 and the problem is back. The really weird part is that this happened suddenly, not after a new flash or any operation on the phone.
Anyone figured this out?
Click to expand...
Click to collapse
Adding some additional info from my experience:
- Tried flashing latest BL and CP files (using odin) without any luck
- Tried various 15.1 roms as my device is not officially supported by lineage, again no luck
---------- Post added at 07:32 PM ---------- Previous post was at 07:20 PM ----------
pijes said:
have you tried using stock rom and see if the problem persists?
Click to expand...
Click to collapse
I have and the problem goes away....thing is the device is so much better on OREO
alex.do said:
yesterday I got it happened again: one of my sim cards suddenly lost signal. completely. and since then it keeps happening so randomly. please help!
im currently on oreo 41.3.A.2.75, BL unlocked, kernel packed by serajr's tool using ta_poc method with my own original TA, magisk installed, systemlessly xposed. i got it all working fine. until this issue happened.
i've also tried different ways: reflash, wipe data completely including sdcard, switch to DRMfix method, remove app by app, remove xposed... even switching SIM slots.... no luck so far.
about the issue, it just happens randomly without any clue. one of my SIM card just disappears. sometimes this one, sometimes the other. until now the only way is restart and pray it won't happen again.
please help! please!
Click to expand...
Click to collapse
similar thing i replied here
plzzz see
https://forum.xda-developers.com/showpost.php?p=77103551&postcount=190
Hello guys! First of all, sorry for my bad English.
Since this morning, my phone started crashing, and I don't know why. I didn't changed any module since yesterday and I've tried uninstalling magisk, changing kernel and so on, and nothing worked. The last thing that i wanna do is a factory reset so if somebody could figure out what is the problem based on this logcat that i did on the exact moment of the crash, it would be much appreciated!
Just go to paste ubuntu dot com and add /p/VyYQvpV72Q
itsmedigio said:
Hello guys! First of all, sorry for my bad English.
Since this morning, my phone started crashing, and I don't know why. I didn't changed any module since yesterday and I've tried uninstalling magisk, changing kernel and so on, and nothing worked. The last thing that i wanna do is a factory reset so if somebody could figure out what is the problem based on this logcat that i did on the exact moment of the crash, it would be much appreciated!
Just go to paste ubuntu dot com and add /p/VyYQvpV72Q
Click to expand...
Click to collapse
Could you provide more info? What rom and what version? Did you install an app before it started crashing?
Gionikva said:
Could you provide more info? What rom and what version? Did you install an app before it started crashing?
Click to expand...
Click to collapse
Running stock Oxygen Open Beta 9, with Blu Spark kernel and Magisk 18. At the moment, i'm reporting crashes opening facebook, gmail, SD Maid, root explorer, but it is very random, and i'm logging everything and the problem seems to be a NullPointerException at process com.android.server.am.OnePlusJankManager, but i still could not figure out what this process does. In standby mode it does not crash, tried playing brawlstars and works fine...
itsmedigio said:
Running stock Oxygen Open Beta 9, with Blu Spark kernel and Magisk 18. At the moment, i'm reporting crashes opening facebook, gmail, SD Maid, root explorer, but it is very random, and i'm logging everything and the problem seems to be a NullPointerException at process com.android.server.am.OnePlusJankManager, but i still could not figure out what this process does. In standby mode it does not crash, tried playing brawlstars and works fine...
Click to expand...
Click to collapse
What the hell, now i've tried with SD Maid a full cleanup, it removed about 3 Gb of junk and seems to be working fine!
same happens to me.
I'm on the same version (Oxygen Open Beta 9), but with stock kernel and no root at all.
I couldn't figure out a way to fix that yet
Same problem here since today.. Llast version of Oxygen OS, random crashes.
Phone goes black then ask my pin. Was about to do a factory reset but I don't know if this will be usefull. :/
I was in open beta 9 also when this problem started yesterday, I had to do factory reset and I installed the stable version 9.0.2 I had to install my applications all over again
WrathChild08 said:
Same problem here since today.. Llast version of Oxygen OS, random crashes.
Phone goes black then ask my pin. Was about to do a factory reset but I don't know if this will be usefull. :/
Click to expand...
Click to collapse
same thing for me too, since yesterday!!!! i did a factory reset, but i am also returning my OP6
lover said:
same thing for me too, since yesterday!!!! i did a factory reset, but i am also returning my OP6
Click to expand...
Click to collapse
Open Beta 9?
renatoknot said:
Open Beta 9?
Click to expand...
Click to collapse
yes
---------- Post added at 11:56 AM ---------- Previous post was at 11:53 AM ----------
same problem people have but different kernels and even on Oreo
https://amp.reddit.com/r/oneplus/comments/a2zfjt/oneplus_6_keeps_crashing_and_restarting/
https://forum.xda-developers.com/oneplus-6/help/random-crashes-5-1-8-t3811969
https://forum.xda-developers.com/oneplus-6/help/random-freeze-reboot-t3831268
https://forum.xda-developers.com/oneplus-6/help/random-soft-reboots-oos-9-0-t3847814
https://forum.xda-developers.com/oneplus-6/help/sign-9-0-3-kepp-gettin-random-reboots-t3874940
lover said:
yes
---------- Post added at 11:56 AM ---------- Previous post was at 11:53 AM ----------
same problem people have but different kernels and even on Oreo
https://amp.reddit.com/r/oneplus/comments/a2zfjt/oneplus_6_keeps_crashing_and_restarting/
https://forum.xda-developers.com/oneplus-6/help/random-crashes-5-1-8-t3811969
https://forum.xda-developers.com/oneplus-6/help/random-freeze-reboot-t3831268
https://forum.xda-developers.com/oneplus-6/help/random-soft-reboots-oos-9-0-t3847814
https://forum.xda-developers.com/oneplus-6/help/sign-9-0-3-kepp-gettin-random-reboots-t3874940
Click to expand...
Click to collapse
I went to the stable version and gave hard reset and solved ..... just try the hard reset and see what it gives
As I said, after I did a cleanup with sd maid my phone stopped crashing, but after a few days again it started to crash, and once again I did a cleanup and seems to be fixed. But I don't know why this happens
How many Rom updates did you have without factory reset?
itsmedigio said:
Hello guys! First of all, sorry for my bad English.
Since this morning, my phone started crashing, and I don't know why. I didn't changed any module since yesterday and I've tried uninstalling magisk, changing kernel and so on, and nothing worked. The last thing that i wanna do is a factory reset so if somebody could figure out what is the problem based on this logcat that i did on the exact moment of the crash, it would be much appreciated!
Just go to paste ubuntu dot com and add /p/VyYQvpV72Q
Click to expand...
Click to collapse
Sent from my ONEPLUS A6003 using Tapatalk
Only one update from beta 9 to 10 because i did a fresh installation via Fastboot after I tried to install MIUI. And anyways, I still had experienced crashes before. I also tried debloat with a script but nothing. For now it works just fine, but it's very random. I can't replicate the problem now, but maybe in a few days it will start again, and all I can see is crash at jankmanager (I see a lot of logs of that crash into /data/system/dropbox)
Hello All,
Just got a notification for the latest Android 10 build OTA.
I updated and is seems to be fine so far and hopefully it fixes all the issues
The horrible lag seems to have been fixed but I guess we'll need some more time to confirm this, will also see if battery usage has improved
Same here, updated and looks ok. No slow downs and lagging so far. let's see how it goes after some time.
Still have
- mic Volume problems while recording voice Messages in WhatsApp (Volume too Low)
Updated after factory Reset and with Xperia companion
Fingerprint is still slow when screen is off.
Why I can't update? It says could not install. Help
danidarklord said:
Why I can't update? It says could not install. Help
Click to expand...
Click to collapse
Did you try restarting your phone and try again ? Do you have enough space ?
When you tap Update, what happens ? Does it download the update then fails ?
For me so far, this update is working really well. I am not experiencing lag and overnight battery usage was very low, something that I have not experienced for months now.
I had a couple of wifi disconnects, not sure if that is related to the phone or the router itself so will monitor that
Yep, some issue of 532 version is fixed in this update 618.
Finger sensor is not good as Pie, but it quite better than 532.
danidarklord said:
Why I can't update? It says could not install. Help
Click to expand...
Click to collapse
Looking at your previus messages it looks like you are on unlocked bootloader.
If so, you can't take the Ota update.
You need to use your computer to make the update.
Skickat från min H8266 via Tapatalk
thatu said:
Did you try restarting your phone and try again ? Do you have enough space ?
When you tap Update, what happens ? Does it download the update then fails ?
Click to expand...
Click to collapse
Already tried, and I'm sure I have enough space. It does download the update and finished but failed at 1/3 of update thus the attached image.
---------- Post added at 11:49 AM ---------- Previous post was at 11:42 AM ----------
Mario.D said:
Looking at your previus messages it looks like you are on unlocked bootloader.
If so, you can't take the Ota update.
You need to use your computer to make the update.
Skickat från min H8266 via Tapatalk
Click to expand...
Click to collapse
I'm pretty sure I wasn't unlocked, can't risk missing any features yet. But I might also follow your advise to use my computer to update. Thanks
danidarklord said:
Already tried, and I'm sure I have enough space. It does download the update and finished but failed at 1/3 of update thus the attached image.
---------- Post added at 11:49 AM ---------- Previous post was at 11:42 AM ----------
I'm pretty sure I wasn't unlocked, can't risk missing any features yet. But I might also follow your advise to use my computer to update. Thanks
Click to expand...
Click to collapse
Did you use VPN or some AdBlock? If using, pls shut it down then you can download update.
Hint: connect your phone to a wifi network for stable download
trannamcloud said:
Did you use VPN or some AdBlock? If using, pls shut it down then you can download update.
Hint: connect your phone to a wifi network for stable download
Click to expand...
Click to collapse
no, I don't use any of that. I also did factory reset my phone and still it fail even with good wifi. So my only guest is that it related to region? or newflasher? I don't know. I just flash using newflasher a few days back to get android 10 update using Customize IT firmware, before the new update released.
same on my XZ3,
---------- Post added at 05:39 AM ---------- Previous post was at 05:34 AM ----------
tyrael11 said:
Still have
- mic Volume problems while recording voice Messages in WhatsApp (Volume too Low)
Updated after factory Reset and with Xperia companion
Click to expand...
Click to collapse
have the same after softwarerepair with companion on my XZ3
My experience so far has been lackluster. The fingerprint reader seems to work better but battery life is not improved and may actually be worse.
Battery life is similar to the last firmware, the performance is actually getting so much better, and the fingerprint reader is very bad (just like the last firmware with failed recognition if the screen is off).
tyrael11 said:
Still have
- mic Volume problems while recording voice Messages in WhatsApp (Volume too Low)
Updated after factory Reset and with Xperia companion
Click to expand...
Click to collapse
Same on XZ3
---------- Post added at 06:22 AM ---------- Previous post was at 06:18 AM ----------
tyrael11 said:
Still have
- mic Volume problems while recording voice Messages in WhatsApp (Volume too Low)
Updated after factory Reset and with Xperia companion
Click to expand...
Click to collapse
Same by XZ3!
trannamcloud said:
Yep, some issue of 532 version is fixed in this update 618.
Finger sensor is not good as Pie, but it quite better than 532.
Click to expand...
Click to collapse
I upgraded from pie to .618 ( I skipped 532). There is indeed a small lag on the fingerprint sensor.
For the moment I have no other problems but I will give it a few days and update this comment.
Update : with .618 when screen is off, I sometime needs to keep my finger on the fingerprint reader up to one second to unlock the phone ( but most of the time it works fine). A little bit annoying :/
i followed this guide https://forum.xda-developers.com/cr...apps/android-10-stock-enable-gesture-t4052799 for enable gesture with adb on .618 fw and i enable! but work only back and not home. can anyone help me? i have root and in the post of the guide a user said that on his xz2c with the root activated it and they work
nikkdib said:
i followed this guide https://forum.xda-developers.com/cr...apps/android-10-stock-enable-gesture-t4052799 for enable gesture with adb on .618 fw and i enable! but work only back and not home. can anyone help me? i have root and in the post of the guide a user said that on his xz2c with the root activated it and they work
Click to expand...
Click to collapse
This is specified that it doesn't work on xz2 and xz3