I have a problema with fingerprint, when I boot works perfectly, but in a variable lapse of time the sensor stops working, it’s as if it never existed.
Any ideas?
yeah i have same problem once a day, since 5 days.
a reboot makes it work again, but it's not a solution.
i'm reading about it now, seems lots of people have this issue
Antho02 said:
yeah i have same problem once a day, since 5 days.
a reboot makes it work again, but it's not a solution.
i'm reading about it now, seems lots of people have this issue
Click to expand...
Click to collapse
Yup, 6.0.1 broke this for a lot of phones.
Not for me. Still working. Uptime is 14 days and 21 hours with the latest FW.
Sent from my E5823 using XDA Free mobile app
Pepecillo said:
I have a problema with fingerprint, when I boot works perfectly, but in a variable lapse of time the sensor stops working, it’s as if it never existed.
Any ideas?
Click to expand...
Click to collapse
Try removing everything related to the fingerpring sensor from the battery optimization
---------- Post added at 23:57 ---------- Previous post was at 23:56 ----------
civicsr2cool said:
Yup, 6.0.1 broke this for a lot of phones.
Click to expand...
Click to collapse
Not 6.0.1, doze did
Pyramid Head said:
Try removing everything related to the fingerpring sensor from the battery optimization
---------- Post added at 23:57 ---------- Previous post was at 23:56 ----------
Not 6.0.1, doze did
Click to expand...
Click to collapse
I've never once used doze tho
Pyramid Head said:
Try removing everything related to the fingerpring sensor from the battery optimization
---------- Post added at 23:57 ---------- Previous post was at 23:56 ----------
Not 6.0.1, doze did
Click to expand...
Click to collapse
Me neither
..... and I have 6.0 not 6.0.1, and haven't no battery optimization
Pyramid Head said:
Try removing everything related to the fingerpring sensor from the battery optimization
Click to expand...
Click to collapse
i did that yet but the problem appeared again
I had this problem as well. I used Andro Plus Kernel v33 and some custom settings through Kernel Adiutor (different IO scheduler and CPU scheduler). After a factory reset of my Xpower 3.0 ROM and removing Kernel Adiutor (therefore using the standard settings) it works flawless. I assume the problems are caused by some energy or RAM saving settings.
HibikiTaisuna said:
I had this problem as well. I used Andro Plus Kernel v33 and some custom settings through Kernel Adiutor (different IO scheduler and CPU scheduler). After a factory reset of my Xpower 3.0 ROM and removing Kernel Adiutor (therefore using the standard settings) it works flawless. I assume the problems are caused by some energy or RAM saving settings.
Click to expand...
Click to collapse
I have the same issue since approx. 5 days. Fingerprint sensor does not work. AT lock screen message appears "Fingerabdrucksensor hardware nicht gefunden". After restart the sensors works again for some hours. I am on android 6.0.
Antho02 said:
i did that yet but the problem appeared again
Click to expand...
Click to collapse
Are you sure? There is one starting with com.fingerprint
Check out this thread: http://forum.xda-developers.com/xperia-z5/help/fingerprint-hardware-available-t3354800/page9
No general solution to it yet.
Pyramid Head said:
Are you sure? There is one starting with com.fingerprint
Click to expand...
Click to collapse
yes
i tried so many things...
- erase cach and dalvick
- remove battery optimisation for com.fingerprints and 2 other related app
- change google app to none as default app
- uninstall and desactivate google app
- uninstall xposed
but it still come once a day
reboot is the only way
Antho02 said:
yes
i tried so many things...
- erase cach and dalvick
- remove battery optimisation for com.fingerprints and 2 other related app
- change google app to none as default app
- uninstall and desactivate google app
- uninstall xposed
but it still come once a day
reboot is the only way
Click to expand...
Click to collapse
Try factory reset from inside the recovery, it wont delete your storage only apps,accounts,etc
Pyramid Head said:
Try factory reset from inside the recovery, it wont delete your storage only apps,accounts,etc
Click to expand...
Click to collapse
yeah looks like the only way, but some people did it and it came back after some days. so for now i ll still reboot once a day, too lazy for a reset :/
I upgraded to 32.2.A.0.253 and used rootkernel to get root and recovery from here: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Flashed xposed and everything works peachy. No issues with fingerprint hardware missing anymore.
So far this has fixed it for me but I had to use rootkernel 5.0 rc4. When I used 4.51 the scanner would stop working after about a day. I have a US E5803 and flashed the Nordic E5823 firmware. The idle battery drain seems better too.
quack3d said:
I upgraded to 32.2.A.0.253 and used rootkernel to get root and recovery from here: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Flashed xposed and everything works peachy. No issues with fingerprint hardware missing anymore.
Click to expand...
Click to collapse
So. I tested various combinations:
1. Stock .224 + root/no root + stock kernel/rooted stock kernel/androplus kernel + xposed/without xposed + greenify/without greenify + another mods/without these mods
2. Stock .253 + root/no root + stock kernel/rooted stock kernel/androplus kernel + xposed/without xposed + greenify/without greenify + another mods/without these mods
Yup, that's crazy, but I wanted to find out what is the cause...
1. On full stock .224 i had no problems with root +stock kernel/rooted stock kernel/androplus kernel + greenify/without greenify etc... a few days everything worked normally and usually fingerprint scanner stopped working after one day so I decided to change the combination, adding xposed. After that, everything went wrong. After a few hours I immediately noticed the error. But I did not let it go, because it could be so, that this bug appeared just at the moment and xposed just fooled me.
2. The same combination, then after 5 days without issues I have added xposed, 2 days without issues with xposed and then.... same situation, then I have just uninstalled xposed, until now no problems.
So... In my opinion, Xposed is guilty.
I haven't had this problem one time since doing the YouTube playback fix. Maybe coincidence idk but it's been two weeks no issues.
civicsr2cool said:
I haven't had this problem one time since doing the YouTube playback fix. Maybe coincidence idk but it's been two weeks no issues.
Click to expand...
Click to collapse
what is the "YouTube playback fix" ?
Related
Ok, so here's the deal.
After I updated my s3 to Jelly Bean, the following problem started to appear:
Sometimes when WiFi turns off either manually or automatically (I have Tasker which turns off WiFi when screen goes off), WiFi gets stuck at "Turning off..." and doesn't react on any actions.
The switcher gets greyed out and I can do nothing about it. The only way to troubleshot it is to restart the device. Once restarted, everything works fine, but, as you already guessed, it works not for too long. =)
It all depends how lucky I'm. Sometimes the phone can work the whole day without causing the glitch, when I'm not that lucky I have to restart the phone a couple of times during the day. <- really annoying.
The phone is rooted with Galaxy S3 Toolkit by flashing an insecure boot image.
I tried to do factory reset but problem still remained.
I have attached a few screenshots as a proof as well as a screenshot showcasing my phone's firmware specs.
Any ideas or help will be appreciated.
I would blame Tasker try uninstalling and test .
jje
JJEgan said:
I would blame Tasker try uninstalling and test .
jje
Click to expand...
Click to collapse
Thanks for the reply. But it seems like this is not the problem with Tasker. As I stated in my previous post, I did factory reset my phone and the problem still remained, though no third-party apps were installed other than those that came stock.
I can reproduce the bug very easily: all I need to do is to turn my WiFi on using the icon under notifications bar and then, once it gets turned on, quickly tap the icon again to turn WiFi off. At that point WiFi gets stuck.
JJEgan said:
I would blame Tasker try uninstalling and test .
jje
Click to expand...
Click to collapse
What date is your kernel - August ? If you have a late build of JB the stock JB on my S3 had a kernel build from 19th October.
You may need to just flash back a later stock boot image you will retain root.
Fixed things for me - just extract the boot.image from a full stock rom and use the toolkit to create a flashable tar should fix your problem and improve the battery life
starfish_001 said:
What date is your kernel - August ? If you have a late build of JB the stock JB on my S3 had a kernel build from 19th October.
You may need to just flash back a later stock boot image you will retain root.
Fixed things for me - just extract the boot.image from a full stock rom and use the toolkit to create a flashable tar should fix your problem and improve the battery life
Click to expand...
Click to collapse
Did as you suggested, tested it a bit and everything works like a charm. The problem is gone, plus I now see more RAM in the Task Manager (this was another issue I was thinking about), and the whole phone seems a bit smoother (maybe this is a placebo effect, dunno).
So thank you very much and you have my appreciation.
Domovik said:
Did as you suggested, tested it a bit and everything works like a charm. The problem is gone, plus I now see more RAM in the Task Manager (this was another issue I was thinking about), and the whole phone seems a bit smoother (maybe this is a placebo effect, dunno).
So thank you very much and you have my appreciation.
Click to expand...
Click to collapse
excellent - pleasure to help
starfish_001 said:
excellent - pleasure to help
Click to expand...
Click to collapse
What rom are you using, i want also to fix this. Thank you
Could this perhaps be brought to attention again please?
How exactly did you fix it and did it involve losing any data?
NVM: Just download and flash Siyah. Probably the easiest fix.
3dawg said:
Could this perhaps be brought to attention again please?
How exactly did you fix it and did it involve losing any data?
Click to expand...
Click to collapse
Nope, flashing kernel will no impact your data.
3dawg said:
NVM: Just download and flash Siyah. Probably the easiest fix.
Click to expand...
Click to collapse
I don't know about Siyah - I simply took a stock kernel, prepared it with the toolkit and flashed it with Odin. This was pretty easy and it worked.
Hope this post helps.
I noticed about a week ago that my GPS was not locking my location. I‛m on RootBox 4.0, and I've read that others had this issue with the ROM. I tried all the solutions listed in the thread, but nothing solved the problem. My phone shows no satellites in view or in use, even if I leave it for 20mins. Occasionally I get 1 satellite in view but my phone doesn't use it.
I would appreciate any help.
I had the same problem also on rootbox 4.0. I had success with the third fix in the rootbox thread. What isn't listed there, is that after extracting, pasting/replacing and fixing permissions of the gps driver is that a reboot is needed directly after this. Maybe try fix #3 again from the beginning, but reboot after? I get gps lock within 10 seconds if I do that.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Hopper8 said:
I had the same problem also on rootbox 4.0. I had success with the third fix in the rootbox thread. What isn't listed there, is that after extracting, pasting/replacing and fixing permissions of the gps driver is that a reboot is needed directly after this. Maybe try fix #3 again from the beginning, but reboot after? I get gps lock within 10 seconds if I do that.
Click to expand...
Click to collapse
I reboot every time I apply a GPS 'fix'. I'll try again though.
Tried again, still no joy.
vSTATERv said:
Tried again, still no joy.
Click to expand...
Click to collapse
Alright, so the obvious which may not be so obvious. It took me a while to figure out what was going on but now each flash I can get GPS lock after a few minutes fiddling and 10 seconds waiting for a lock. So we're on the same page, this is what you're doing:
Download and extract attachment. Using Root explorer, backup the gps.exynos.so in system/lib/hw to sdcard, then remove it from the system/lib/hw folder. Also using Root explorer, copy the gps.exynos4.so that you extracted or whatever its called to system/lib/hw. Fix permissions to rw-r--r--. Reboot. Open Google maps, grant it the permission to access location. Wait for GPS fix.
Using those steps I get GPS working first go every time on RootBox 4.0. If I miss anything, or do anything different, it won't work. Are those the exact steps you're using?
Hopper8 said:
Fix permissions to rw-r--r--.
Click to expand...
Click to collapse
What do you mean by this? The read write execute permissions? Or something else?
vSTATERv said:
What do you mean by this? The read write execute permissions? Or something else?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1857648
Yes, the file permissions. Stickied at the top of the GSII 'General' Section.
Permissions set properly - still not working.
vSTATERv said:
Permissions set properly - still not working.
Click to expand...
Click to collapse
Another captain obvious comment, you are searching for GPS while you're outside? I would assume so. Have you tried re-downloading the file for the fix from the RB thread? If you haven't, try that. If you have, reflash the ROM after a factory reset, cache & dalvik wipe. Try to fix the GPS before restoring all your data etc.
---------- Post added at 10:25 PM ---------- Previous post was at 10:11 PM ----------
FD1999 said:
Sorry but what attachment?
Gesendet von meinem LG-P880 mit Tapatalk 4
Click to expand...
Click to collapse
The one from the third post of this thread: http://forum.xda-developers.com/showthread.php?t=2117444. In the 3rd post, the third option for the GPS fix.
Does this mean anything? One satellite keeps popping up in the centre of the radar.
vSTATERv said:
Does this mean anything? One satellite keeps popping up in the centre of the radar.
Click to expand...
Click to collapse
Couldn't tell you sorry. Not sure what app that is/what it's meant to do. To test my GPS I use Google maps.
Edit: did you reflash the rom?
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Hopper8 said:
Couldn't tell you sorry. Not sure what app that is/what it's meant to do. To test my GPS I use Google maps.
Edit: did you reflash the rom?
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Click to expand...
Click to collapse
I did a full wipe, still persists. I might try and flash another rom.
vSTATERv said:
I did a full wipe, still persists. I might try and flash another rom.
Click to expand...
Click to collapse
Omega AOKP has written in the OP 'instantaneous GPS lock'. I've used it and had no issues with GPS at all, give it a shot.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
I've restored an old backup of resurrection remix, and I still have the problem.
Is it possible that some system files regarding the GPS were corrupted?
So when you had resurrection remix previously, did you have working GPS? And did you try omega? Next step is to flash stock after a full wipe. Stay away from 4.0.4, but pick yourself an ICS/JB ROM and try it. If the problem still persists, then it's possibly hardware. Either that or something is messing up with each flash, which is doubtful.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Hopper8 said:
So when you had resurrection remix previously, did you have working GPS? And did you try omega? Next step is to flash stock after a full wipe. Stay away from 4.0.4, but pick yourself an ICS/JB ROM and try it. If the problem still persists, then it's possibly hardware. Either that or something is messing up with each flash, which is doubtful.
Click to expand...
Click to collapse
I doubt that this is a hardware issue. A week ago I was able to get a GPS lock if I waited for 10 mins or so. I started applying all these patches and fixes in an effort to get a decent lock time. After messing around with all these fixes, I have now ended up with no satellites in view and no lock, no matter how long I wait. Therefore, I believe that I've messed up some sort of file whilst trying to reduce the GPS lock time which has now stopped it from working completely. Oh yeah and btw, I was able to use gps back when I had RR ROM.
vSTATERv said:
I doubt that this is a hardware issue. A week ago I was able to get a GPS lock if I waited for 10 mins or so. I started applying all these patches and fixes in an effort to get a decent lock time. After messing around with all these fixes, I have now ended up with no satellites in view and no lock, no matter how long I wait. Therefore, I believe that I've messed up some sort of file whilst trying to reduce the GPS lock time which has now stopped it from working completely. Oh yeah and btw, I was able to use gps back when I had RR ROM.
Click to expand...
Click to collapse
Two words: Flash Stock.
Flashed stock - problem still persists.
UPDATE - finally got it working. Flashed latest stock firmware; it didn't work at first, however after persistent testing I finally get a lock after 26 seconds or so.
Thanks very much for all the help.
Hardware problem. Service centre (Unless you want to try all the usual fixes you'd try if you were still running a custom rom, which I very much recommend you do first).
My screen broke and I got it replaced by a third party.
I changed the rom today and my touch wasn't working in the new rom. It worked fine in twrp but as soon as i booted into the system it stopped working. I booted back to twrp and it was still working there but not in the rom.
Is there any file or zip that can fix this issue? I know about Agni kernel and it fixes the issue but i suspect that it is also causing lag. I want to test the rom without flashing agni kernel and only using the touch fix zip.
Any help is appreciated.
i love agni kernel (performance and audio boost).
but if not like you this kernel... i dont know if exists a patch.
Probably your new remplace is FOCALTECH.
if you clean install a new rom try with agni kernel again... remember install all kernel over original one and not mod kernel over other mod kernel.
here: https://forum.xda-developers.com/redmi-note-3/development/devs-kenzo-hardware-variations-t3458389
the people talk about hardware variations on RN3Pro (i dont read all the post)
I have replaced screen too, my touch is working fine but my screen color is broken, it will fine after reboot from long press power button but will broke again after screen off, are anyone facing this too? I'm on xtended oreo
strawjerry said:
I have replaced screen too, my touch is working fine but my screen color is broken, it will fine after reboot from long press power button but will broke again after screen off, are anyone facing this too? I'm on xtended oreo
Click to expand...
Click to collapse
Use aida or other soft to see what screen hardware use.
Chrisis25 said:
Use aida or other soft to see what screen hardware use.
Click to expand...
Click to collapse
Mine is boe
Boe nt35532?
Do you use kernel adiutor? Or other app with colour profiles?
Chrisis25 said:
Boe nt35532?
Do you use kernel adiutor? Or other app with colour profiles?
Click to expand...
Click to collapse
Yes, I use kernel adiutor
strawjerry said:
Yes, I use kernel adiutor
Click to expand...
Click to collapse
go to:
Screen>Screen Hue> and select 0 (no more), try with it.
Chrisis25 said:
go to:
Screen>Screen Hue> and select 0 (no more), try with it.
Click to expand...
Click to collapse
Already have it
Hi, I have been testing this on this device, and finally I was able to make AOSP 10 (GSI) run on our device.
Our device needs overlay to fix this issues. I will try to work into that
How to flash
WARNING: Your device must have unlocked bootloader
1. Download the latest TWRP Recovery: https://forum.xda-developers.com/mi...overy-unofficial-twrp-xiaomi-mi-note-t4015805
2. Download the latest AOSP 10 GSI (ab with gapps): https://github.com/phhusson/treble_experimentations/releases/
3. Download vbmeta.img: https://github.com/TadiT7/xiaomi_ce...9.3.1-release-keys/firmware-update/vbmeta.img
4. Disable vbmeta partition by flashing vbeta.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5. Flash TWRP
Code:
fastboot flash recovery <twrp_file_name.img>
6. Boot TWRP, make wipe (Format Data only!)
7. Flash the AOSP system.img file to System partition
NOTE: Trying to flash system.img using fastboot causes bootloop.
Aditionally here you can flash GAPPS and Magisk
- Flash GAPPS: https://opengapps.org/
- Flash Magisk: https://github.com/topjohnwu/Magisk/releases
10. Reboot system & enjoy!
Bugs
- Fingerprint
- Auto-brightness
- NFC
-Weird notification audio: can be fixed flashing this -> https://github.com/hmuny99/GsiSystemAudioFix/raw/master/fixaudiogsi.zip
-Video recording: can be fixed by flashing this -> https://forum.xda-developers.com/attachment.php?attachmentid=4374464&d=1514638461
-Flashing Magisk causes bootloop
- GCAM Camera starts to lag when the device has been on for a long time
Since we have a complete kernel sources/device tree, we can have this as a daily diver :good:
For now, I'd need the framework-res.apk from Stock rom, if someone could provide it, that would be really helpful
iFlashed said:
For now, I'd need the framework-res.apk from Stock rom, if someone could provide it, that would be really helpful
Click to expand...
Click to collapse
I saw this on another topic.
https://forum.xda-developers.com/showpost.php?p=81824837&postcount=50
Hi, what do you think, this flashing method will work with phhussons GSI too?
https://github.com/phhusson/treble_experimentations/releases
---------- Post added at 08:00 AM ---------- Previous post was at 07:43 AM ----------
If you need it still, I can copy it now, if you tell me the full path of this file.
technoboi1 said:
Hi, what do you think, this flashing method will work with phhussons GSI too?
https://github.com/phhusson/treble_experimentations/releases
---------- Post added at 08:00 AM ---------- Previous post was at 07:43 AM ----------
If you need it still, I can copy it now, if you tell me the full path of this file.
Click to expand...
Click to collapse
Same steps, Boots up, I recommend the system-quack-arm64-ab-gapps from your link, as it includes Gapps.
However, With that both I couldn't flash Magisk or I would get a bootloop. With LoS It would also not install gapps. But would boot just fine without Gapps or Magisk.
Currently Phhussons is working with Gapps. LOS Is not, atleast for me, but neither is working with Magisk 20.4.
thank for your reply, it has same bugs like LOS?
deathhall said:
Same steps, Boots up, I recommend the system-quack-arm64-ab-gapps from your link, as it includes Gapps.
However, With that both I couldn't flash Magisk or I would get a bootloop. With LoS It would also not install gapps. But would boot just fine without Gapps or Magisk.
Currently Phhussons is working with Gapps. LOS Is not, atleast for me, but neither is working with Magisk 20.4.
Click to expand...
Click to collapse
technoboi1 said:
thank for your reply, it has same bugs like LOS?
Click to expand...
Click to collapse
Yup, Same bugs
Sent from my Mi Note 10 using Tapatalk
I remember when Android P GSI comes, we have distorted audio bugs, maybe its same bug again.
Deleting folder vendor/lib64/soundfx fixed bug in Android P.
Bugs
- Fingerprint
- Auto-brightness
- NFC
-Weird notification audio
I have been working on an overlay, but seems like I couldn't fix any bug.
Fingerprint works, but for any reason the Google API/Fingerprint config app is not recognizing it, but I can see in logcat that sensor recognizes when I use the fingerprint with any problem, so maybe problem from the GSI?
For the rest of the bugs, nothing for now
Is there an improvement?
UtkuAblak said:
Is there an improvement?
Click to expand...
Click to collapse
I'm trying to contact with phhusson. Audio can be fixed flashing a .zip
This rom use stock camera or? And what about current photo quality?
Good work and thank you guys!
Hudinited said:
This rom use stock camera or? And what about current photo quality?
Good work and thank you guys!
Click to expand...
Click to collapse
I recommend using a Gcam in order to get better quality, for example: https://www.celsoazevedo.com/files/android/google-camera/dev-urnyx05/ (tell me if you find something better!)
how did you fix the fingerprint?
iSonik said:
how did you fix the fingerprint?
Click to expand...
Click to collapse
It's not fixed yet, What I just said is that 'works' in terms that if you touch the fingerprint it will be recognized in logcat, but nothing will happend on the fingerprint setup app. Currently I'm talking with phhusson about this and thinks that this could be a GSI related issue because he told me he will make a test image
technoboi1 said:
Hi, what do you think, this flashing method will work with phhussons GSI too?
https://github.com/phhusson/treble_experimentations/releases
---------- Post added at 08:00 AM ---------- Previous post was at 07:43 AM ----------
If you need it still, I can copy it now, if you tell me the full path of this file.
Click to expand...
Click to collapse
iFlashed said:
It's not fixed yet, What I just said is that 'works' in terms that if you touch the fingerprint it will be recognized in logcat, but nothing will happend on the fingerprint setup app. Currently I'm talking with phhusson about this and thinks that this could be a GSI related issue because he told me he will make a test image
Click to expand...
Click to collapse
My fingerprint is recognized in logcat as well as the button lighting up, but it doesn't work even in stock rom funny enough.
deathhall said:
My fingerprint is recognized in logcat as well as the button lighting up, but it doesn't work even in stock rom funny enough.
Click to expand...
Click to collapse
What do you mean when you say It doesn't work in stock rom funny enough?
iFlashed said:
What do you mean when you say It doesn't work in stock rom funny enough?
Click to expand...
Click to collapse
When I flashed this GSI for Lineage 17 when the other thread first started, even after Miflashing back to Global Stock my fingerprint doesn't work anymore, If i use the testing options, it'll activate the fingerprint and register me using my finger on it, but wont activate fingerprint settings as a password, it goes to the input screen then kicks back out immediately
deathhall said:
When I flashed this GSI for Lineage 17 when the other thread first started, even after Miflashing back to Global Stock my fingerprint doesn't work anymore, If i use the testing options, it'll activate the fingerprint and register me using my finger on it, but wont activate fingerprint settings as a password, it goes to the input screen then kicks back out immediately
Click to expand...
Click to collapse
This could be something related to unlocked bootloader? u tried to relock the bootloader?
iFlashed said:
This could be something related to unlocked bootloader? u tried to relock the bootloader?
Click to expand...
Click to collapse
Are you asking if i did, or i should? Also, I don't wanna hijack the thread, maybe chat in PM or Discord or whatever you prefer?
i use magisk without recovery n latest build of global 23..
no problem so far .. but am facing weird restart ..it happend two times now after some days..the phn suddenly shutdown then , flashes screen like 3/5 times ! then the phn boots :/
whats the problem of it?
Seems to be the stock kernel. Using a different kernel I had no reboot issues at all. Any kernel of your preference
garylawwd said:
Seems to be the stock kernel. Using a different kernel I had no reboot issues at all. Any kernel of your preference
Click to expand...
Click to collapse
yes am using perf+ kernel by stock rom... how can i solve it...i need battery backup main priority
Sapper Morton said:
You can replicate this issue by forcing close system_server process, it forces a soft reboot, and the flickering issue. I'm using a upstreamed kernel build (4.14.212), the OP issue still happens, so I'm not sure about the real cause here; but it definitely is related to Android 10, since I'm yet to find a similar issue on stock state in Android Pie.
Click to expand...
Click to collapse
We have it fixed in android 11??