Related
How is that possible?
I did read I am not the only one, though in his case it might be a hardware issue.... which I would hope it is not.
What I did with a brand new 3T:
1. Installed TWRP 3.0.3, wiped phone (format system, format data)
2. uploaded and restored an image from my so far daily driver OnePlus3 (Sultan's CM 13) - (TWRP was complaining about the backup image being ext4, while the 3T is on F2FS) - I know not the clean way... but it seemed fine
3. I meant to install a fresh CM13 over it and SuperSU (I thought if there are difference, it would be recognized by the installer) but I forgot, bootet and..... Oops, it works
4. I encountered a problem with the Fingerprint Sensor.... on this CM13 install *crapshoot*
5. Thought it might have restored the Firmware of the 3 as well (it didn't) and crapped my pants.
6. Installed the current OnePlus 3T OxygenOS 3.5.4 (2016-12-19) via ADB sideload to get the original Firmware and everything back (which seemed not necessary but hey, I tried)
7. I even tried the OOS 4.0.1 Beta 9 (or 10) via sideload in the hope it would give me the correct firmware that is able to talk to the Fingerprint sensor. It is a newer firmware though... no luck though.
8. Neither a) OOS 3.5.4, b) OOS 4.0.1 or c) CM 13 gave me a working sensor. CM 13 just cancels the fingerprint enrollment, OOS gives me at least a message (see picture) "Fingerprint Hardware not available".
9. The rest was working well... very well...
Internal Tests of *#808# let me test the Fingerprint sensor and it say it works well (aside from the 'quality test' in chinese I can't read)... see attached pictures
I am frustrated... did I kill it, is it broken, is something wrong? Any ideas?
Edit:
Physical buttons (left, center, right) work with haptic feedback. The moment I get to the point of the first pic (Recording Fingerprint) the whole button bar stops working. Not haptic feedback, not even getting back or the Task manager. I have to push the power button, and again, get to inset PIN to unlock and are back in the phone, one step back in the Fingerpring enrollment process and the HW button bar works again. I klick 'Next' to get to the step it was unresponsive before... and they stop working again.
In my opinion that shows the sensor itself is not broken...
Update:
Desperately doing every step again... this happend:
After sideloading 3.5.4 and 4.0.1 images from OnePlus again.... tadaaaa... a wipe/fresh install of 4.0.1 (OnePlus3TOxygen_28_OTA_037_all_1701041831_a2ba632ce9) got me a working Fingerprint Sensor.
Now I am in the process of sideloading the latest stable 3.5.4 with the aim of getting the proper firmware in the device to run Sultan's CM13 - he did implement a firmware check in hist install script. I assume this was to force people with an outdated FW to update... unfortunately it also denies installation with a newer Firmware.
Let's see if we are going somewhere...
Try the unbrick tool
You could always try the unbrick tool by Haris K, this is the link --> https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
ayush2901 said:
You could always try the unbrick tool by Haris K, this is the link --> https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
How can you brick a device these days? Not as long as you get somehow a bootloader running and that is damn hard to kill - if not impossible.
So thank you for the tip. I just do not see what a tool can do that you can't do with a fastboot / adb command line. And I prefer to understand what is happening. A magic 'black box' is not really helping to improve your understanding of your device. That is just my thought.
Conclusion time
As is turned out, the fingerprint sensor is NOT broken. It did work in the sideloaded 4.0.1 OOS. This gave me fresh energy to examine more circumstances... and why it did not work before, when I did the same thing. It took hours to repeatedly install various image, siedloading 1.5 GB + install procedure takes forever. But knowing that the sensor itself works, it would be just a matter of time and correct installation (which I seemed to **** up in the first place).
1. siedload OOS 4.0.1 worked
2. after that 3.5.4 was in order... and Yes! it also worked
(I have no clue what kept it before from working, as I did all these steps before already)
3. with Firmware of 3.5.4 -> Format System & Data -> Switch Data to ext4 (i was highly annoyed the up to 10 mins delay of TWRP)
4. Install Sultan's CM13 + nano GApps + SuperSU 2.79 -> boot -> FP sensor works!
YEAH - happy
I can't say for sure but it seems very likely that it was indeed the firmware that caused the trouble.
But it seems initially the FW was somehow botched up... and later when the Firmware was corrected it still didn't work due to my wrongful OS recovery (CM13 which I assume still run drivers for OnePlus3 and not 3T) that was the cause.
Lesson learned: Don't be greedy when it comes to installing a new phone and do the hard work of reinstalling, copying and setting up every single ****. Not really a surprise but I guess it needs to be learned over and over. It ****ing bugs me, since I can't not Titanium restore crucial setting / apps like my Exchange account and Line to a new phone. That means I loose months of transactions (contacts, chats, pics in LINE, which is the predominant App here in Asia).
I would welcome any hint how to streamline copying apps that are not willing to work on a new device as a 1:1 copy - particular LINE that does refuse to work even with adjusted device ID.
I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL
MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.
Hi,
Since I've been requested by other forumers; I will list down on how I managed to flash Pixel Experience ROM from Honor View 10 to our Note 10.
Disclaimer: I am not dev, and I don't own or developed the steps; just compiling as steps by steps to other forumers so that they can enjoy their note 10 in Pixel Experience alike
I've tested the Pixel Experience, a part from having some launcher draw slight lag - So far everything has been good and notifications come on time + the battery life is almost identical to EMUI itself.
Here is how I start:
1:UNLOCK Bootloader (Steps 1 & 2 are essentials so you can't skip it) - https://forum.xda-developers.com/note-10/how-to/bootloader-unlock-root-tutorial-huawei-t3855643
You have to unlock bootloader and the only way as mentioned, will be by paying the service. I've got my code there and so far it's been pretty legit.
Skip step 3 as you are changing the ROM. Once flash new ROM, root will disappear so you may skip it.
2. Download Pixel Experience ROM: https://forum.xda-developers.com/honor-view-10/development/rom-pixel-experience-t3867008
Direct Link: https://download.pixelexperience.org/berkeley/
It is important to you to download this TWRP as well: https://storage.codebucket.de/public...0-berkeley.img (DO NOT FLASH IT YET)
2. Boot into the default EMUI after you have done unlocked. You should notice all your data is missing and EMUI requesting you to resetup your phone. I skipped it and so far all's been good. Restart the phone. Hold Volume Up + Power Button until you boot into TWRP recovery screen.
3. Format your data using advanced wipe - Cache, Dalvik/Cache, Data and System.
4. Once done, navigate back to Install and select Pixel Experience and flash it. I do not encounter any trouble so far, no errors and etc. (You should still have it under your download folder as you do not flash your internal storage).
5. Wipe Cache
6. Reboot into your phone and viola you get Pixel Experience.
7. This may be skipped if you do not wish to root your phone as your phone is working correctly. If you are using previous TWRP, you will stuck at the splash screen and it will not boot into the TWRP.
Follow this step if you want to flash Magisk.
Enable back USB debugging > adb fastboot bootloader
8. Flash the TWRP again by using fastboot flash recovery_ramdisk twrp-3.2.2-0-berkeley.img. Reboot and hold Volume Up + Power button again. Viola, you have a working TWRP now.
Please be advised that your internal storage, might be like mine in which you will not able to flash any ZIP due to encrypted folder. Your folder will appear as some random characters/letters and you can't see your zip files. My workaround is to add-in a MicroSD and flash Magisk.zip through the MicroSD.
If you have questions, feel free to ask. I will try my best to help out. As said, I am not a developer - I am just compiling the guide for other forumers. Credit goes back to the thread owners: 7gismo, Codebucket and other developers whom involved with the projects. Kudos and peace out.
I had little more complex problem.
I was rooted with magisk in default emui ROM 8.2.0.132.
So 1st Step: Download 8.2.0.132_Full_OTA.zip & using Huawei Extractor, extract recovery & ramdisk
2nd Step: Unroot via Magisk Manager
3rd Step: Overwrite TWRP with official recovery & overwrite boot/ramdisk with extracted ramdisk
4th Step: reboot to recovery & factory reset. then reboot to system
5th Step: again TWRP
Rest are the same as you.
---------- Post added at 05:48 PM ---------- Previous post was at 05:35 PM ----------
There was a problem in TWRP. Usb device is not recognized in windows 10 in recovery mode. I had to change from my new pc (windows 10) to old pc(windows 7). Don't know what's the problem?
how many antutu score pixel rom
thx
SmartPhonesFan said:
Guyz a few pictures of the ROM would be great if you show us.. mainly settings .. what apps are present ,if google pay fully works , NFC , f-print face ID..
Thnx
Click to expand...
Click to collapse
Hi. I have not tested Google pay due to my country lack of it. So far fingerprint works, facr unlock does work but it is unlike original emui where it'll auto unlock the phone - you still need to slide to unlock after it recognise your face. So far apart from volte in which the developer has mentioned. I have not received any error or tested something which not work.
Will update if I encounter any bug or issues.
My previous phone was Nexus 6P. I always felt, there are lacking of some tiny features in barebone Android which maybe not so important to others. But to enable these features I have to use Xposed+Magisk+modules
1. network speed at status bar
2. When a call connected, short vibration alert
3. Applock with fingerprint natively
4. Battery Percentage within battery icon
5. Always on display automatically off within pocket
6. Themes
All are present in EMUI 8.2
That's why, I have returned from Pixel Experience ROM to EMUI in my Honor Note 10.
But the aggressive battery & ram management leads to unusable notification feature. Real time notification is totally absent if the app is not running in multitasking bar. Google location history is not working due to China EMUI ROM. But this notification failure is totally unacceptable, again I am planning to change to other custom ROM
Your TWRP link leads to a passworded login page. Do you have a direct link?
Right now I have TWRP 3.2.1 and am stuck with the AOSP rom bug. Hoping your 3.2.2 can fix it and I don't need to go through full erecoveery just to re-root and install roms.
SmartPhonesFan said:
Still no pictures?
Click to expand...
Click to collapse
I am not sure what pictures do you want as the ROM is exactly same as the one shown on Honor View 10:
https://forum.xda-developers.com/honor-view-10/development/rom-pixel-experience-t3867008
Or you just want a confirmation that this ROM works on RVL-AL09?
If that's the case I can provide that. Else the entire ROM experience is the exact same as Pixel Experience for Honor View 10
SmartPhonesFan said:
I meant desktop, icons, settings.. Overall the look of this ROM.. But checked.. Now
So can I install it now? All 100% works? G pay Google history works? All functions works?
Click to expand...
Click to collapse
I am not sure Gpay works or not cause I am not using GooglePay as said. All functions so far work so well except for LTE which will not. I haven't get any error and etc, and yet to encounter an app that doesn't work.
Sorry cause Android pay isn't too popular here in my country, we usually use wechat pay, alipay and other medium
SmartPhonesFan said:
What about camera functions? Can still huawei stock camera app be used? Otherwise all its features are gone...
Click to expand...
Click to collapse
Hi, good thing about this ROM is the camera app included is Huawei Stock Camera. Not Gcam. Gcam doesn't work very well with Kirin yet; even the one I've tried still give some error and no HDR+
Hi, I successfully flashed based on your instructions. Everything works perfectly except Netflix is not working properly. First I don't see it in play store, then I downloaded the all and installed. Now when I play videos there is only sound with black screen. Are you experiencing this issue?
Thanks.
zhumingvictor said:
Hi, I successfully flashed based on your instructions. Everything works perfectly except Netflix is not working properly. First I don't see it in play store, then I downloaded the all and installed. Now when I play videos there is only sound with black screen. Are you experiencing this issue?
Thanks.
Click to expand...
Click to collapse
Have you tried to flash the latest version? There's an update which fixed my Always Listen to Song as well.
SmartPhonesFan said:
Any fotos would be great? Setting menu interface..
Why u guys not uploading fotos?
Don't be lazy...
Google pay working?
Google maps history works?
Google assistance works?
Stock huawei camera works?
Is it based on pie 9?
Click to expand...
Click to collapse
I can only answer you based on this what I experience - I am not sure why photos are required though if you really want Pixel Experience because it is exactly same as the one in Honor View 10. Even the update for the newest Pixel Experience works and now my Always listen to Song works.
Google pay working? Answered
Google maps history works? It works for me. And so far no crash and etc when I am using Google Map/Waze. So all good
Google assistance works? Yes, but if the screen is locked, then it is not working. Not sure if there's changes cause my Pixel XL also doesn't work nowadays if I locked my phone.
Stock huawei camera works? Yes. The camera is based on Huawei default camera app as Gcam is not working and hence not installed in the Pixel Experience ROM
Is it based on pie 9? It is. The Pixel Experience forum has this note.
BTW, those questions have been answered in this thread and another forum (Honor View 10 Pixel Experience). If you are really into Pixel Experience, go ahead and flash it. You can revert back afterall; but I do notice that the lag of the Pixel Launcher still persists hence I have to use Lawnchair launcher (Which fixed the issue; no idea why).
lavenderyew said:
Have you tried to flash the latest version? There's an update which fixed my Always Listen to Song as well.
Click to expand...
Click to collapse
Hi, thanks for you instructions. I did flash the latest version. Everything works fine except netflix showing a black screen with only audio when play movies. I did some google and seems like it is related to root/unlocked bootloader and I am not rooted. Do you use netflix? If so does it work for you?
zhumingvictor said:
Hi, thanks for you instructions. I did flash the latest version. Everything works fine except netflix showing a black screen with only audio when play movies. I did some google and seems like it is related to root/unlocked bootloader and I am not rooted. Do you use netflix? If so does it work for you?
Click to expand...
Click to collapse
Sorry but unfortunately I don't use Netflix on my phone. But I've seen a lot of different complaint where they fixed the issue by resetting the certificate. Google Netflix black screen Google pixel and there are tons of same complaint.
SmartPhonesFan said:
Chexck this out guyyz \ : https://forum.xda-developers.com/note-10/how-to/android-p-9-0-beta-t3886194
gonna do it tonight
Click to expand...
Click to collapse
Yes I do follow the China forum but then again the reasons why I moved away from emui:
- notification issue (super aggressive killed all apps even I locked it and set full manual permission)
- the default launcher has been removed and only by removing the default launcher through adb then only it is able to change.
- ok Google unable to be used and still hivoice as default
- cause it is not global room, Google feed is not able to be swiped
- prefer stock Android as minimalist
- Samsung health not working
I kinda miss Huawei functions though, some of them are really useful in comparison to pixel experience
Don't think so as you have to remember that this isn't a global rom, but China only. If you notice and compare, the global rom has slight different and Google integration.
But I've tested the notifications issue on my emui 9. Same thing happened cause of the aggressive battery saver
Hi, does desktop mode still works with pixel experience and is the aspect ratio correct too, cause Note 10 has 1080 x 2220 and View 10- 1080 x 2160 resolution? Thanks!
Dombrr said:
Hi, does desktop mode still works with pixel experience and is the aspect ratio correct too, cause Note 10 has 1080 x 2220 and View 10- 1080 x 2160 resolution? Thanks!
Click to expand...
Click to collapse
Haven't try desktop mode yet, but my assumption that it will not work as the integration is done by EMUI.
How is the battery life after using this rom?
Gunbit said:
How is the battery life after using this rom?
Click to expand...
Click to collapse
It's less long lasting than original ROM, but this is to be expected because the notifications work well and it doesn't aggressively kills the background apps as in the orignal ROM.
Overall, I still able to:
Uncharge at 1.30 am and use it up to 8.30 pm with 20 - 30% battery life. It's quite a moderate use - like day to day routine - whatsapp, facebook, some reading, youtube, and etc
lavenderyew said:
It's less long lasting than original ROM, but this is to be expected because the notifications work well and it doesn't aggressively kills the background apps as in the orignal ROM.
Overall, I still able to:
Uncharge at 1.30 am and use it up to 8.30 pm with 20 - 30% battery life. It's quite a moderate use - like day to day routine - whatsapp, facebook, some reading, youtube, and etc
Click to expand...
Click to collapse
I see I see, so whats your average SOT? Can it last two days of moderate use?
Gunbit said:
I see I see, so whats your average SOT? Can it last two days of moderate use?
Click to expand...
Click to collapse
About 4 - 5 hours. Don't think it can last as long as the original ROM.
Hi guys,
I'm a bit concerned about my mi8. Since several weeks now the phone is getting so slow to boot, even into recovery mode !
For exemple, today before starting to see the havoc logo spinning I count more than 20 spins. Months ago it took only 5 or 6, 2 weeks ago : more than 8... Etc.
When phone is started first apps tha usualy open really fast (Viper4fx, gsam battery monitor, magisk notifications) are so slow to open. Some other apps same thing the moment I open them.
What do you think about that ? At first I thought my battery is dead. It charges as fast as usual. Discharging is like before I'd way. Not worst for sure So I hope Its nor that.
I'm using battery charge limit (the app, nor from havoc sertings) to stop at 81% and charge it always when the minimum reaches 40%. So for battery life I think I'm doing things well.
I'm still on pie. Please, see the attached picture to look at my version.
I'm wondering what could cause this big issue.
I'm used my make lot of backups with twrp 3.3.1-1. Sometimes 2 per days, sometimes none in 2 or 3 days and so from the day I unlocked the phone and installed my first and only rom : havoc. Sure I installed several updates but no other ROM and I stopped updating it cause it worked really as I expect it should. So...
Also, making twrp backups are Soooo slow. Generaly it tooks depending of the size, between 90 sec and 140. Now it takes more than 6 min !!
So before doing a last backup and do anything I wanted to ask what you all think about that before doing a clean install update/upgrade.
Do you think it worth the try ?
I tried to clear caches (both) in twrp. Nothing :/
I'm afraid I killed my phone memory or battery. Don't really know.
Last thing, maybe an important one but don't know why it would... I installed notify & fitness and sleep as Android for my mi band 4 and I noticed my phone getting slow during this period. About N&F it was on 12.27.2019.
The firmware was updated way after that issue... And of course I cleaned all app caches manualy, not using some weird app to do the job.
Sorry me for this long SOS, and please forgive my bad english. I'm starting to being crazy. OK, the phone works but oooh boy, Its slow.
Cheers
Your rom software is out of date. if you truly want the best experience on a daily basis. There is no doubt in my mind that Xiaomi.EU is still the absolute best experience overall.
It is light years better than the Global stock Rom, all of the bloat has been removed and it has some of the Pixel AOSP features integrated into the Rom. but yes it's still miui. For me that is a good thing because I am a fan. It sounds like you have never tried Xiaomi.EU so give it a shot. I guarantee, that if you keep it installed for a few days, you will not want anything else unless you are just bored. Wait until the new update comes out, it should be late today or tomorrow. by the way, you will average about 7.5 -8.5 hours SOT.
On the other hand, if you are content with Havoc, then migrate to the latest, Its pretty great but the battery SOT time is bad right at 4 hours. This can be improved by changing the kernel. I tested the LawRun_x5.0-60hz kernel and it improves SOT to 5.5 hours, and the OS gennnerally runs better. Other Roms are also good, but lack the abundance of features that Havoc has. A comparable heavily feature rich rom is CRDroid.
If you want to stay on your current rom, then clean your caches, and at least upgrade the kernel. That alone may be enough to improve your recent performance. i dont think you phone is going bad. You likely just have some corruption, or too many processes running in the background.
@tsongming Hi and cheers for replying.
To start, I forget to mention that I'm using a global version.
That being said, I did clean all caches including from all my apps. Manualy of course.
I did use Xiaomi MIUI for very long time. Since I got my first Redmi Note 4. As you well said, I did switch to custom ROMs for what you said.
Regarding SOT... And the reason why I didn't update anything on my Mi8 its because with this version of havoc and this kernel. Gsam bat monitor tells me now : 9h41 (5h58 Max) and before my issue it was 11h !
So, to answer you : before asking here I also trying to update the Rev kernel but lot of things didn't work anymore. Like unlock the phone with my fingers and I think its pretty much normal as Havoc as evolved so kernel did the same and is not compatible with older version I think. At least, mine...
Honestly I tried lot of things to make my havoc super speed, smooth with a great battery and I was happy with that
I do hope I answered to all your questions.
I don't know what to do cause I'm not 100% sure that starting from clean MIUI or custom rom will fix it. What if not ? I'll "forced" to reinstall "everything" (I'm aware of backup apps but dont wanna use them) even if I saved all important stuffs
And if I badly revert to the last MIUI (I never reinstalled MIUI after a custom ROM. I know there is good tuto, but...) I could break it and I'll loose everything. For now it works, slowly OK ^^' but I rather that than taking a risk and found what is the cause of my problem.
Erpe7 said:
@tsongming Hi and cheers for replying.
To start, I forget to mention that I'm using a global version.
That being said, I did clean all caches including from all my apps. Manualy of course.
I did use Xiaomi MIUI for very long time. Since I got my first Redmi Note 4. As you well said, I did switch to custom ROMs for what you said.
Regarding SOT... And the reason why I didn't update anything on my Mi8 its because with this version of havoc and this kernel. Gsam bat monitor tells me now : 9h41 (5h58 Max) and before my issue it was 11h !
So, to answer you : before asking here I also trying to update the Rev kernel but lot of things didn't work anymore. Like unlock the phone with my fingers and I think its pretty much normal as Havoc as evolved so kernel did the same and is not compatible with older version I think. At least, mine...
Honestly I tried lot of things to make my havoc super speed, smooth with a great battery and I was happy with that
I do hope I answered to all your questions.
I don't know what to do cause I'm not 100% sure that starting from clean MIUI or custom rom will fix it. What if not ? I'll "forced" to reinstall "everything" (I'm aware of backup apps but dont wanna use them) even if I saved all important stuffs
And if I badly revert to the last MIUI (I never reinstalled MIUI after a custom ROM. I know there is good tuto, but...) I could break it and I'll loose everything. For now it works, slowly OK ^^' but I rather that than taking a risk and found what is the cause of my problem.
Click to expand...
Click to collapse
The current version of Havoc already uses the Revolution kernel, and its part of the current problem so use something else. The Law kernel that I mentioned is extremely good. but so are the others latest release such as Mipa and Twisted. and no fingerprint issues with these kernels.
As a longtime user you do know that anytime you switch the kernel that you should remove all passkeys, screenlocks, face unlock etc.? This could explain the slowness, you have encryption issues.
Android 10 is much improved over pie, except for the battery 11 hours SOT is unheard of on Android 10. Except for 1 guy claiming 11 hours on the ION rom. I tried the rom and it is good. but I am only getting 7 hours Sot, and the Rom is like Lineage, just the basics. No fingerprint issues.
You truly need a full clean install, including formatting storage. just backup your files first.
Xiaomi Miui? Did you mean Xiaomi.EU? if not Xiaomi.EU , then you really should try it, you wouldn't know from a past experience. This is Miui 11 on Android 10 and its flawless.
thx again @tsongming
Yep, I note all what you said to me. But to be honest last year anytime I switched from kernels to kernels I never had to reset screenlock etc. Last year cause as I said once I found the kernel which suits me I stuck with it.
So I can state its note related to that cause I didn't change it since month trust me, just tried the last kernel one or week ago to be sure if it was the cause or not. Just installed and uninstalled apps since.
look at this screenshot you'll see what I meant about SOT which was better month ago. :/ Maybe I didn't explain well...
I'm not against trying any roms including xiaomi.eu perhaps (I do have links for this I think but any link is appreciated just in case. I just download the lastest stable 11 from xiaomi.eu if its what you have in mind) but I want to be sure if it'll fix what I'm facing. You know ?
I'm afraid that doing a clean install with any rom won't fix my beautiful Mi8 ^^
Erpe7 said:
thx again @tsongming
Yep, I note all what you said to me. But to be honest last year anytime I switched from kernels to kernels I never had to reset screenlock etc. Last year cause as I said once I found the kernel which suits me I stuck with it.
So I can state its note related to that cause I didn't change it since month trust me, just tried the last kernel one or week ago to be sure if it was the cause or not. Just installed and uninstalled apps since.
look at this screenshot you'll see what I meant about SOT which was better month ago. :/ Maybe I didn't explain well...
I'm not against trying any roms including xiaomi.eu perhaps (I do have links for this I think but any link is appreciated just in case. I just download the latest stable 11 from xiaomi.eu if its what you have in mind) but I want to be sure if it'll fix what I'm facing. You know ?
I'm afraid that doing a clean install with any rom won't fix my beautiful Mi8 ^^
Click to expand...
Click to collapse
You posted a question asking for help, but then you dont want to try anything because you tried things before. Yes, its true that Magisk is sometimes persistent, but it depends on the release. it is safer to remove the passkeys.
But if you really think about it, what would cause the phone to cool down, ignore the battery stats especially from Gsam it's often very wrong, I use it too, for years and in your case you are getting good SOT because you have a zero % for the phone. It's almost like a Sim card isn't installed? Every rom will provide extremely fantastic SOT when a sim card isn't being used. If you have an active sim card then something is wrong with the monitoring because Gsam is showing 0%, it should show something even if you havent made a phone call for days.
Do whatever you want it's your phone:
I still think that you have encryption or corruption issues and its bad enough for your to make a post about it. FYI : The battery dying doesnt slow down the phone. Yes, some stock roms, notably Apple intentionally by choice changed the kernel core settings automatically on aging batteries. Hence the huge controversy a couple of years ago, that isn't happening to you.
A dying battery doesn't slow down the phone, evn cold solder joints do not slow down the phone, they keep a phone from booting to system and to recovery. The only thing left is corruption or thermals, which on this phone good luck editing thermals because they are mostly encrypted. The remaining possibility is corruption, post your log files and lets see what's actually going on.
Again, what would slow down your phone even in recovery?
It's always thermals, or corruption. Slow to start up, even in recovery.: We can rule out thermals unless your battery temp or cores temps are extremely high. This leaves corruption. if its slow while booted into the system, then you may have apps or processes crashing and you are not aware of it. If that is true, then eventually the phone may stop booting up altogether. If its thermals causing overheating you should truly resolve this issue immediately before actual heat damage occurs. Did you ever flash display refresh rate mods? If so your DTBO partition could be the issue....corruption.
Use this program to provide an app list : https://play.google.com/store/apps/details?id=de.onyxbits.listmyapps ( Weed out any unknown programs that you may not realise are installed. Post the list along with complete logs. Once you see these crashes, that I am sure the logs will show: Do as I suggested earlier: wipe and "format" your phone. Then later use best practices and remove passwords before changing kernels
Cheers. I'll try what you suggest.
I might have some questions in the future regarding format and some other things.
Never flashes display refresh rate and never noticed any overheat issue on my phone.
Sure, I'll do something like you said as soon as possible.
PS : you said "before remove passwords". You mean in the parameters of the phone like schema/diagram, pin, etc ?
Cheers
Erpe7 said:
Cheers. I'll try what you suggest.
I might have some questions in the future regarding format and some other things.
Never flashes display refresh rate and never noticed any overheat issue on my phone.
Sure, I'll do something like you said as soon as possible.
PS : you said "before remove passwords". You mean in the parameters of the phone like schema/diagram, pin, etc ?
Cheers
Click to expand...
Click to collapse
You could remove password under data/system/locksettings.bin But it's better to just go the settings//security/ *.* < remove whatever you have setup : prints and face unlock first before, pattern or pin.
Another good practice for Android 10, should you go there is :
Extract the boot image from the rom
Place it inside the downloads folder.
When ready to flash root, patch to the boot image first, ( this links the existing system binary credentials into the boot image)
Boot to recovery flash boot to boot
Then flash magisk > then boot to system and you will have no issues whatsoever with root.
Afterwards, if you decide to flash different kernel, Magisk is more likely to stay stay persistent.
I hope everything is good from this point forward take care.
@tsongming Thanks for reminding me the locksettings.bin thing because I used it once on my old phone and I forgot that.
Never installed 10 yet. But I take carefuly your advice.
Hello!
Did you fix it? Because it's happening to my Mi 8 too. It's exactly the same issue, the phone takes a long time to boot up, to open apps and even to boot into TWRP
I have that issues on my mi8
I had this problem with me before and I solved it by flashing the last official ROM, Now the problem happened to me again and I do not know what is the reason behind it @tsongming
Sent from my MI 8 using Tapatalk
ahmadbasher011 said:
I have that issues on my mi8
I had this problem with me before and I solved it by flashing the last official ROM, Now the problem happened to me again and I do not know what is the reason behind it @tsongming
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
I recently had some issues with my phone as well. I was able to get my phone back to normal functioning by flashing the latest stable fastboot rom using the flashall.bat method. (dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global)
I kept everything stock for a few days even recovery, to ensure once that everything was back to normal.
Next I flashed the latest OrangeFox beta recovery, and I highly recommend the latest beta build over any other version of Recovery, it will decrypt when official Twrp will not. It is now more up to date than the LR Team version, and all of the bugs have been solved by DarthJabba. In fact, he even added a script to work around poorly designed startup scripts, which are suprisening not consistent between the wide range of custom roms for the Mi8.
Today, I am still using Orange Fox, ( OrangeFox-R10.1_002-Beta-dipper) and the latest stable Magisk. I no longer have freezing, unexpected shutdowns, slow starts, or poor battery life. My issue was without a doubt corruption, and bugs with the mid february version of Xiaomi.EU. The last 2 releases have been solid.
Since this weekend I face the same problem. Every action seems to bit slower than before. And I don't know what I did that resulted in this problem. The last thing I remember I installed was the new Miui12 live backgrounds. But I deleted them again.
I'm on stock since some weeks.
But I don't want to install everything from the beginning again.
Do you know how to solve the problem without wiping everything?
Edit: As I think about it, it seems as if the caching of the apps doesn't work as good as before and the killing of apps is too aggressiv.
But what did affect it?
Edit: I found the solution for my problem.
With Android Battery Historian was able to find the process that made the trouble.
It was the Miui wallpaper carousel app. After deleting it the problems were gone.
Erpe7 said:
Hi guys,
I'm a bit concerned about my mi8. Since several weeks now the phone is getting so slow to boot, even into recovery mode !
For exemple, today before starting to see the havoc logo spinning I count more than 20 spins. Months ago it took only 5 or 6, 2 weeks ago : more than 8... Etc.
When phone is started first apps tha usualy open really fast (Viper4fx, gsam battery monitor, magisk notifications) are so slow to open. Some other apps same thing the moment I open them.
Click to expand...
Click to collapse
it's a hardware issue and it's going to keep coming back, i spent the last two months trying to resolve it but i gave up.
it seems that UFS chip malfunctions on a lot of F1 and mi8 phones.
danielnavarrowo said:
Hello!
Did you fix it? Because it's happening to my Mi 8 too. It's exactly the same issue, the phone takes a long time to boot up, to open apps and even to boot into TWRP
Click to expand...
Click to collapse
Sorry for repling only now guys...
Thx to all who proposed to solve my issue, I will tell you what I did to fix my mi 8.
I did a crystal clean flash :
- downloaded & installed last miui image using miflash
- used "clean all" at the bottom right (be careful to not choose something else like "lock boot loader ")
- then you'll need to flash recovery (twrp), then format data by typing yes. Then copy from where you want your custom rom, flash it flash magisk and boot.
I did this several months from now and my phone is like just new!
No issue at all since.
I guess installing lot of different kernels like I did before must have broken something and hopefully this could help if you dont have more serious issues.
Ps: battery is more than ok and there is no hardware problem.
Thx again to Dexer125 for his help!
Sent from my dipper using XDA Labs
Erpe7 said:
Sorry for repling only now guys...
Thx to all who proposed to solve my issue, I will tell you what I did to fix my mi 8.
I did a crystal clean flash :
- downloaded & installed last miui image using miflash
- used "clean all" at the bottom right (be careful to not choose something else like "lock boot loader ")
- then you'll need to flash recovery (twrp), then format data by typing yes. Then copy from where you want your custom rom, flash it flash magisk and boot.
I did this several months from now and my phone is like just new!
No issue at all since.
I guess installing lot of different kernels like I did before must have broken something and hopefully this could help if you dont have more serious issues.
Ps: battery is more than ok and there is no hardware problem.
Thx again to Dexer125 for his help!
Sent from my dipper using XDA Labs
Click to expand...
Click to collapse
I can confirm this.
I have been unrooted on stock for a few months now and have had no problems since then.
Hello, I have the slow issue (Androbench app with poor performances) after several dates when I have rooted my phone: Mi8 Chinese version with stock global ROM.
After unroot the phone, several days after, the phone works fine with Androbench app with good performances.
I need root my phone to use Magisk hide for Google Pay in order to avoid the Google block for contactless payment.
Can anybody help me about the understanding of this behaviour?
I do not know the reason why the phone is slow after root and why the phone works fine after several days after rooting.
Thanks in advance. Regards
roberbas said:
Hello, I have the slow issue (Androbench app with poor performances) after several dates when I have rooted my phone: Mi8 Chinese version with stock global ROM.
After unroot the phone, several days after, the phone works fine with Androbench app with good performances.
I need root my phone to use Magisk hide for Google Pay in order to avoid the Google block for contactless payment.
Can anybody help me about the understanding of this behaviour?
I do not know the reason why the phone is slow after root and why the phone works fine after several days after rooting.
Thanks in advance. Regards
Click to expand...
Click to collapse
Hi,
Mine has hardware issue (rooted).
Didn't try to unroot it if there is a difference like you describe.
Can't help you with magisk hide. I don't use it.
I have this issue with my mi 8 guys, just happened yesterday
So flashing the latest official rom via miflash is the way to fix it?
Irish_Dude said:
I have this issue with my mi 8 guys, just happened yesterday
So flashing the latest official rom via miflash is the way to fix it?
Click to expand...
Click to collapse
Hello, yes in my case. Sometimes, with wipe all, internal storage included, the problem it solved.
Recently I have the issue again without root: only with custom rom flashed. Several times the issue was reproduced out of my habitual site during vacances.
Thanks
Hey,
I got my Pixel 7 last week and installed Graphene OS on it, however after some days I noticed it behaved very strange.
No buttons on the phone worked anymore, neither the power nor the volume buttons. After I did a full reboot the buttons worked again, but then the fingerprint scanner is not available anymore?!
As i very much like to have both, the buttons and the finger print, working I did a factory reset and installed LineageOS. But now I have the same beavior again after 2 days with the new ROM.
Did anyone experiences something similar already? Do you think this is a hardware issue? Can I still get a replacement if I already unlocked the bootloader and tinkered around with the OS on the phone?
Sounds like a hardware issue. Although its a bit strange that it would affect either the fingerprint sensor or the buttons. Could you describe what goes on with the fingerprint sensor in more detail?
Well the fingerprint hardware is simply not available, conpletely gone from the settings, doesn't show up on the lockscreen, like it doesn't even exist on the device.
If I then reboot the hardware is available again but the whole OS is super buggy, the buttons don't work and the phone will soft reboot after a few minutes.
Before you call it a hardware issue why not flash back to stock and verify. Most likely a rom issue and I'm sure the other rom pulls from the lineage source, most do. Would also explain the issue persisting on two different roms.
Yeah I will try it but the Android flash tool failed on me on 2 seperate machines. So now I habe to do it manually with adb it seems.
But even if the Stock ROM works, it's still weird, as nobody else reporting on this.
elba96 said:
Yeah I will try it but the Android flash tool failed on me on 2 seperate machines. So now I habe to do it manually with adb it seems.
But even if the Stock ROM works, it's still weird, as nobody else reporting on this.
Click to expand...
Click to collapse
I seem to recall a problem with fingerprint disappearing from screen and settings like you described. I think it was in the Pixel 6 forums months ago. I don't remember any details.
It's not unusual to lose certain functions with a custom ROM but the button problem is definitely unusual. Whether it's software or hardware, if you can reproduce at least one of these problems with stock Android then I think you have your answer. And as long as factory firmware is installed, bootloader is locked and you factory reset it, you should be ok returning the phone for repair or replacement.
Thanks for the answer!
Today I finally had the time to flash a factory image. After rooting and restoring all my apps the issue reappeared after about 20 min. on the stock rom it was even more severe. Now I uninstalled magisk and flashed the stock init_boot.img file and until now it seems fine.
Can the patched boot image cause the problems described above, or even an unlocked bootloader?
elba96 said:
Can the patched boot image cause the problems described above, or even an unlocked bootloader?
Click to expand...
Click to collapse
If these problems are caused by bootloader unlocking or rooting stock Android I think the same would've happened to other people by now and it would have been mentioned.
Regarding the bootloader, was GrapheneOS fully erased? In particular its verified boot key.
GrapheneOS CLI install guide
Command-line installation instructions for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
grapheneos.org
If that's not it, or something similar leftover from Lineage, I think you should forget any modifications long enough to reproduce your problems in the phone's factory state. Just run flash-all.bat (or bash equivalent) and let it wipe, lock the bootloader, install updates and use the phone. Time consuming, I know. But if there are hardware issues one or both problems may show up again and it's less of a mystery.
manjaroid said:
Regarding the bootloader, was GrapheneOS fully erased? In particular its verified boot key.
Click to expand...
Click to collapse
Thanks for the notice, I forgot about this!
So far the stock rom without root performs ok, no problems. It just sucks to not have all the customizations I'm used to for the last 10 years...
Maybe try not restoring any apps and see if it still persists.
manjaroid said:
If these problems are caused by bootloader unlocking or rooting stock Android I think the same would've happened to other people by now and it would have been mentioned.
Click to expand...
Click to collapse
@elba96
Maybe it's too soon to dismiss Magisk patching as the problem. You might try Magisk stable 25.2 or canary 25206 if you've been patching with one of the newer 26.x releases.
I'm starting to suspect my patched boot image may be the cause of a new problem on a Pixel 5. Either that or it's a new Android bug.
My problem is similar to one of yours: a lost function combined with a disappearing setting. SmartLock hasn't worked right since the April update a couple days ago. When I check its settings all three SmartLock options are gone. Rebooting brings them back and I'm able to get SmartLock working again. The problem seems to repeat when the phone goes idle and locks down.
By now I'm pretty sure it was the patched boot image. Until now (2 days) the stock ROM doesn't show any bugs.
And now that you say it. I used Magisk 26 for the patching as it rolled out right when I was setting up my phone. Should have stayed with v25.x it seems.
I'll give it 1 or 2 days more just to be sure and then I'll try it with Magisk v25.x again.