I run a custom rom (DU) and the boot process takes at least 2 minutes, it feels really slow. A clean/empty flash of a rom doesn't even need a minute to boot.
I have 89 user apps from which are 16 xposed modules.
I use this setup:
DU rom
Bensschold's kernel
Opengapps pico
xposed systemless v86.2
Is there any reason that it boots this slow? Even my S4 booted faster with the same amount of apps and xposed. Besides this, the phone operates smoothly and lagfree
2mins for that much apps doesn't seem long.
Related
Hello everybody!
I tried the V6 Supercharger the other day and since then, everytime i reboot my phone it takes a minimum of 5 minutes, does anyone know how to speed up boot time?
i am running hyperdroid 5.9.0 (magldr) with fikret Kernel
Boot has always been slow since i moved back to magldr but never that bad.
any help is appreciated, thanks in advance
+1
After I applied the SuperCharger script, my HTC Desire S takes forever to boot. After the standard script was done, I selected the 16, 22 and 32 options.
I did unsupercharge with the script, and removed all the tweaks by the supercharger. Boot time is now normal, and the random crashes & reboots I had twice per day don't happen anymore. Life seems better without the supercharger.
I have come across a very annoying bug with cm12.1 version for 550m...everytime I reboot the phone gets stuck in bootloop almost all the time...half of the time it keeps optimizing apps and then gets stuck at starting apps and other half it just gets stuck in bootloop...it has made installing xposed modules so difficult since it takes me 4-5 rebbots to get even strted with my phone after downloading a module...can anybody help please...
I have no problem with rebooting on my 550. It sometimes hangs on starting apps on first boot after flashing, but turning off and back on solves this (except with broken 0819 build). Xposed may be the cause of your problem - the devs have said countless times that it is not supported and not recommended. If you want to use xposed, you are better off staying on stock or using super zen.
Xposed causes this on CM. It's not supported.
Sent from my serial terminal
Maybe the MediaScanner is going crazy.
I was having the exact same issue as you.
Try to reboot your phone until cyanogenmod boots successfully and run this command on terminal app or adb.
It will disable media scanning on boot.
su
pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
if you want to run cm with xposed.... then run the initial (first) build of cm12.1... Xposed is well supported
Has anyone tried to flash the Xposed Module that came out earlier today/yesterday? If you don't know what I'm talking about, watch this video real quick: https://youtu.be/eADZK17N7rk
I understand it is unofficial and might be unstable with lots of bugs, & that some modules currently don't work, but would I be at (more) risk of bricking my phone if I flashed it?
I flashed it yesterday and everything went well. The bugs are the following that I've experienced:
1. In order to download a module, you must press save instead of download. After that, a toast notification will prompt you on where to go in your file manager to find the apk.
2. Some force closes such as kernel auditor and Google/services. Those were resolved later on for me.
3. I noticed the fingerprint scanner got a little sluggish after, but a reboot fixed that.
4. Sorta made the UI a little sluggish as well so be careful if you've already under clocked your processor.
There we go. I am currently on the latest version of Lineage OS. I uninstalled it today, but I plan on installing it again with a new ROM tonight.
It doesn't seem to work on AOSP or Extended AOSP, but apparently seems to work on other ROMs. Want to switch ROMs unless EAOSP fixes that because I really want Amplify again
Hello guys! I know it's a common issue, but when I reboot my phone there's roughly a 50% chance it gets stuck on the boot screen and I have to reboot. It's surely caused by Magisk, but has someone found a fix already?
The bricks got more frequent and really annoying when I began to install some modules (Xposed, Viper ecc.). Sometimes it takes even 2-3 reboots to start my phone properly, and sometimes it boots without recognizing my sim card.
Is there a fix for this, or do I have to live with it?
Happened to me too. Got rid of magisk for now so running stock un rooted until this gets sorted. Haven't ran into the issue since un rooting.
BetaPix said:
Hello guys! I know it's a common issue, but when I reboot my phone there's roughly a 50% chance it gets stuck on the boot screen and I have to reboot. It's surely caused by Magisk, but has someone found a fix already?
The bricks got more frequent and really annoying when I began to install some modules (Xposed, Viper ecc.). Sometimes it takes even 2-3 reboots to start my phone properly, and sometimes it boots without recognizing my sim card.
Is there a fix for this, or do I have to live with it?
Click to expand...
Click to collapse
Xposed is not yet stable for Oreo. So just get rid of that first. Moreover, it depends on what Magisk version did you flash. V16.0 is the latest stable version and you are recommended to flash it only. I have been using magisk for a long time on both stock and custom rom and never had an issue.
Rowdyy Ronnie said:
Xposed is not yet stable for Oreo. So just get rid of that first. Moreover, it depends on what Magisk version did you flash. V16.0 is the latest stable version and you are recommended to flash it only. I have been using magisk for a long time on both stock and custom rom and never had an issue.
Click to expand...
Click to collapse
I flashed 16.0 too, but I have to say the issue became real even before I installed Xposed. Guess it's something Magisk-related
Try older Magisk, for example 15.3.
Same to me. Just reboot and it´s fine.
BetaPix said:
Hello guys! I know it's a common issue, but when I reboot my phone there's roughly a 50% chance it gets stuck on the boot screen and I have to reboot. It's surely caused by Magisk, but has someone found a fix already?
The bricks got more frequent and really annoying when I began to install some modules (Xposed, Viper ecc.). Sometimes it takes even 2-3 reboots to start my phone properly, and sometimes it boots without recognizing my sim card.
Is there a fix for this, or do I have to live with it?
Click to expand...
Click to collapse
Same. I don't have Xposed or other mods, so I think it's a Magisk's issue.
Made over 20 reboots in order to find the"right" combination of substratum themes the last two days.only 2-3 times i had stucked in reboot. I have magisk, xposed ,gravitybox .
Huh, I get this sometimes too. So it's Magisk v16 you say?
TrueMS said:
Try older Magisk, for example 15.3.
Click to expand...
Click to collapse
Good idea, will give that a go. I don't use any modules anyway, only use it for Safetynet-friendly root.
Same problem here.
I Will follow the topic.
Double post, Sorry!
With beta magisk v16.4 my mi A1 boot normaly...with v16.0 must force reboot 3 times out of 5
laugeek57 said:
With beta magisk v16.4 my mi A1 boot normaly...with v16.0 must force reboot 3 times out of 5
Click to expand...
Click to collapse
Currently testing 16.4b and no boot issues atm!
Must have been topjohnwu's boot operations code change.
Thank you really much
Last few days I tried to use custom ROM. Volte doesn't work. I've given up on that issue now. Now problem is Miui pro.
After flashing it keeps showing boot logo ( I waited for more than 30 minutes) but the older version (7... Something) flashes without any problem.
How long should I wait to complete it's booting process( more than an hour??!!!!!)
P.s- device encryption is enabled [ but I don't think it's causing the problem cuz older version is doing fine]
http://miuiid.blogspot.in/p/rom.html?m=1
Download this and flash like normal rom.
First clear data, dv-cache, system,
Then flash this along with magisk
After flash don't clear dv-cache, not even after flashing magisk and dont change anythink in the system partition untill first boot u can also flash the magisk modules straight ahead.
This is miui id best, u get paid themes free, also volte working and it does have split screen.
Note:- don't forget to flash magisk, don't clear cache after flashing the rom and i mean anytime don't do it it will take a lot of time then.
First boot will take 15 min, dont wait for it once it gets past the boot logo and enters the bootanimation wait for 2 min then again do force reboot by long pressing the power button, do it one more time this time wait for 5 min if it opens then good or again reboot. This time it will happen.
The rom is stable and totally worth the trouble.
This process is just to reduce the first booting time.
Thanks ?
Also check this post for more information.
Link:- https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036
Thanks.
Im running Miui 9.2 global stable 9.2.2.0
Can i do dirty install? I dont wanna lose apps data
Im using stock miui global stable 9.2.2. Android 6.0
If i wanna install miui id, do i need to wipe all , as in format my handset. Or is it ok to just wipe system, cache dv? I dont wanna lose my apps data
@Trovies hi,
Just do titanium or swiftbackup search the apk in google, and u can do dirty flash but i will not recommend it.
Note :- download the premium version of the swiftbackup from the internet.
Thanks
Flash lazyflasher.zip
Sagar_zac said:
http://miuiid.blogspot.in/p/rom.html?m=1
Download this and flash like normal rom.
First clear data, dv-cache, system,
Then flash this along with magisk
After flash don't clear dv-cache, not even after flashing magisk and dont change anythink in the system partition untill first boot u can also flash the magisk modules straight ahead.
This is miui id best, u get paid themes free, also volte working and it does have split screen.
Note:- don't forget to flash magisk, don't clear cache after flashing the rom and i mean anytime don't do it it will take a lot of time then.
First boot will take 15 min, dont wait for it once it gets past the boot logo and enters the bootanimation wait for 2 min then again do force reboot by long pressing the power button, do it one more time this time wait for 5 min if it opens then good or again reboot. This time it will happen.
The rom is stable and totally worth the trouble.
This process is just to reduce the first booting time.
Thanks
Click to expand...
Click to collapse
very well explained. As per habit I was clearing both dv cache and cache and due to this rom was taking too much time to boot. But after reading your post I have made clear pretty much everything. This is the best MIUI rom I have ever used. Performance, battery life, smoothness everything is spot on. I just wish it would had double tap to wake feature and recent apps menu would had icon mode option. Audio through earphones is also low. other than that its fantastic rom.
https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036
Vinayakn73 said:
very well explained. As per habit I was clearing both dv cache and cache and due to this rom was taking too much time to boot. But after reading your post I have made clear pretty much everything. This is the best MIUI rom I have ever used. Performance, battery life, smoothness everything is spot on. I just wish it would had double tap to wake feature and recent apps menu would had icon mode option. Audio through earphones is also low. other than that its fantastic rom.
https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036
Click to expand...
Click to collapse
Well u don't get everything but the things you mentioned i don't use it. So... Good for me right. ?For the audio problem use Dolby from the magisk repo the lenovo A7000 one the others don't work. Just flash the settings zip after flashing the rom and don't clear cache
Sagar_zac said:
Well u don't get everything but the things you mentioned i don't use it. So... Good for me right. For the audio problem use Dolby from the magisk repo the lenovo A7000 one the others don't work. Just flash the settings zip after flashing the rom and don't clear cache
Click to expand...
Click to collapse
well I'm using viper4android but with it audio quality increased but volume decreased further, I think I can live up with it. After flashing settings zip I did everything as you mentioned (did not clear dvk cache or cache) but now rom is stuck on mi logo (almost 20 to 25 minutes) can I dirty flash rom again???? Or do I need to do clean install??
Vinayakn73 said:
well I'm using viper4android but with it audio quality increased but volume decreased further, I think I can live up with it. After flashing settings zip I did everything as you mentioned (did not clear dvk cache or cache) but now rom is stuck on mi logo (almost 20 to 25 minutes) can I dirty flash rom again???? Or do I need to do clean install??
Click to expand...
Click to collapse
Just do a clean flash, rom + settings zip, together like do a batch. Then no clear cache boot and do the process
Sagar_zac said:
Just do a clean flash, rom + settings zip, together like do a batch. Then no clear cache boot and do the process
Click to expand...
Click to collapse
yup I'm not noob and doing exactly as you are saying but still I'm struggling with this rom
1st attempt wipe dalvik, system, data cache - flashed rom - flashed settings zip - flashed magisk - tried to flash magisk modules (failed) - reboot without any wipe - rom didn't boot
2nd attempt - clean installed with only rom and settings zip - booted normally - went to bootloader again installed magisk - reboot system - went in bootloader again - flashed app systemizer module- rebooted successfully - went to magisk manager and added module youtube advanced - reboot stuck on mi logo
3rd attempt - reinstalled clean as described in 2nd attempt till the setup of app sytemizer on reboot - went to app systemizer module and ticked gps app- module asked to reboot boooooom stuck on mi logo
Everything I wrote above is my common practice with every miui rom but I don't know why It is not working with this rom. anyways thanks for your help I am moving to global stable as I can't live without these modules. n sorry for bad english
Vinayakn73 said:
yup I'm not noob and doing exactly as you are saying but still I'm struggling with this rom
1st attempt wipe dalvik, system, data cache - flashed rom - flashed settings zip - flashed magisk - tried to flash magisk modules (failed) - reboot without any wipe - rom didn't boot
2nd attempt - clean installed with only rom and settings zip - booted normally - went to bootloader again installed magisk - reboot system - went in bootloader again - flashed app systemizer module- rebooted successfully - went to magisk manager and added module youtube advanced - reboot stuck on mi logo
3rd attempt - reinstalled clean as described in 2nd attempt till the setup of app sytemizer on reboot - went to app systemizer module and ticked gps app- module asked to reboot boooooom stuck on mi logo
Everything I wrote above is my common practice with every miui rom but I don't know why It is not working with this rom. anyways thanks for your help I am moving to global stable as I can't live without these modules. n sorry for bad english
Click to expand...
Click to collapse
Ya i know modules can be a pain in the ass only one suggestion when ever after flashing a module if its stuck in the bootloop then just use magisk Uninstaller then again install Magisk or use magisk for recovery to remove the particular module which is causing boot loop also use root youtube valence and use universal installer it will not cause bootloop. Also use minimal module only what you need. Ok then. Also do as u discreet i am fine in this rom. And its great. ?
See my modules
I too use YouTube vanced.
Man u got to find solutions not give up and change only after a few attempts. U know how many times i got bootloop because of this rom and it's compatibility issues with the modules. After many attempts i got it. Now its the best custom miui rom ever also the dev is constant and hops to bring miui 10. Also if u have used this rom only for a few hours u can realize the difference.
Sagar_zac said:
I too use YouTube vanced.
Man u got to find solutions not give up and change only after a few attempts. U know how many times i got bootloop because of this rom and it's compatibility issues with the modules. After many attempts i got it. Now its the best custom miui rom ever also the dev is constant and hops to bring miui 10. Also if u have used this rom only for a few hours u can realize the difference.
Click to expand...
Click to collapse
yup there is no doubt this is best custom miui rom out there. But this bootloop and boot time driving me nuts. I wonder why all this problems are popping up though the rom is based on official firmware and I've never faced such problem with official roms. I will give it a try again after two days. I just hope that time it will go smooth.