Am running Superior OS ROM, really like it, except it uses something like 1.2 GB RAM as baseline, reporting 500 MB of apps I did not launch, so probably GAPPS, etc.
Since I got rid of stock ROM ,can anybody tell me how much it uses after boot?
Am sure Lineage OS was using much less when I tried it, but never really checked. Also seems to me that battery life was better on Lineage with less stuff running? Anybody?
I'm using that rom for about 3 days, right now I have 1.1 gb free ram and for me it's quite the same on lineage and stock. One annoying thing is Lawnchair which i don't use cannot be killed and always remain in background doing who knows what.
If you have dark/black theme, when you open the settings do you see for a brief moment a white screen just before it opens?
anzhaki said:
I'm using that rom for about 3 days, right now I have 1.1 gb free ram and for me it's quite the same on lineage and stock. One annoying thing is Lawnchair which i don't use cannot be killed and always remain in background doing who knows what.
If you have dark/black theme, when you open the settings do you see for a brief moment a white screen just before it opens?
Click to expand...
Click to collapse
Yes, there is a nasty half a second long white flash when opening Settings in dark theme, just checked it out. Happens each time. (PS. White flash vanished after the phone sat idle a while).
I thought RAM consumption might be similar because they are all based on stock ROM., but Lineage boots much quicker, not that it's done often, but there must be fewer services running, seems faster, and I think uses less battery, which is what I was after. You think Superior uses how much battery compared to others? Because on mine it seems to drop rather fast.
If you wanna stay on Superior maybe you could kill LawnChair with something like App Quarantine app, Greenify or some hibernation app. Works on Play Services all right.
Plus , Superior didn't let me pass SetUp without connecting to network, unlike stock ROM, or others, and installed VIA browser, first I heard of it, which can only be disabled, not uninstalled. If not nasty, it's a boneheaded move. Happened to you?
I didn't notice that the white flash vanishes when the phone is in idle after a while. It's so annoying that I just put the light theme to avoid seeing the white screen on dark theme.
For me too lineage is the perfect rom, simple and without too much customization. Unfortunately, after selinux was updated to enforcing Magisk was not working anymore so I tried other roms and used resurrection remix for a while. I found out later that it was needed to use Magisk 18.1, in a few days I think I'll gonna come back to lineage since there are small things that I don't like on superioros.
About the battery life, with lineage I was not using any custom kernel but with resurrection remix and superioros I used butterfly kernel 4.4 and I have less consumption compare to lineage. I think with a custom kernel lineage will have a better battery life.
Now I'm trying the module gms doze that should improve the battery by limiting Google services wake lock. I'll see in fews day if I will have some improvement. Other modules I tried were lkt and fde but they just consume more battery without performance improvement.
About Lawnchair it is really annoying, you can't disable it nor kill it. It just relaunch itself after terminating it from settings. Even greenify can't do anything.
I always configure the phone with a sim.
Yep I found via browser too which at least can be disabled.
anzhaki said:
One annoying thing is Lawnchair which i don't use cannot be killed and always remain in background doing who knows what.
Click to expand...
Click to collapse
I don't use this ROM, but this behaviour matches stock...
The multitasking UI in pie comes from the default launcher. The launcher is also involved in "OK Google" listening, but this can at least be turned off.
Probably the ROM has lawnchair setup as the default launcher. If you are using a different launcher, you can disable or uninstall lawnchair to stop it running, but you'll have the Oreo recents screen instead of the pie recents.
I use a Magisk module (debloater) to disable system apps that prevent it. There's also an adb command you can use if you don't have root. https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
a1291762 said:
I don't use this ROM, but this behaviour matches stock...
The multitasking UI in pie comes from the default launcher. The launcher is also involved in "OK Google" listening, but this can at least be turned off.
Probably the ROM has lawnchair setup as the default launcher. If you are using a different launcher, you can disable or uninstall lawnchair to stop it running, but you'll have the Oreo recents screen instead of the pie recents.
I use a Magisk module (debloater) to disable system apps that prevent it. There's also an adb command you can use if you don't have root. https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Click to expand...
Click to collapse
Thanks. I'll gonna try the method without root. I found the module debloater but unfortunately it was not working, its commands on terminal are not recognized. I already wrote on its thread and still waiting for an answer.
I have Magisk 19.1 on ROMs installed by flashing patched boot images after full stock ROM flash, then installing custom ROM, then twrp, disabler, switch slots, reboot twrp, install gapps, the usual, then boot system, install Magisk Manager, then reboot twrp, and then install Magisk 19.1 and reboot system. It works, with messages can't mount system, then vendor, but all works.
Damn, funny because Oreo Recents is what I was after. Can anybody tell me how to get them on Lineage, for example? Install different launcher than Trebuchet, what? I just think Oreo recents were better, so I wanted a ROM with that option. But I am getting off Superior, I think. Tried Resurrection Remix, but UI started going crazy after a while, maybe Recents switching, and apps stopped launching altogether.
Magisk 19.1
Posted twice, sorry. No way to delete posts except editing? Never mind.
MarkR7 said:
Damn, funny because Oreo Recents is what I was after. Can anybody tell me how to get them on Lineage, for example?
Click to expand...
Click to collapse
The stock launcher on the system handles recents. If you hide/remove it then you'll get Oreo recents.
I use a Magisk module to remove the stock launcher. There's adb commands if you don't have root. There's also a quickswitch Magisk module, that's aimed more at enabling third party launchers to handle recents, but it can also force oreo recents.
a1291762 said:
The stock launcher on the system handles recents. If you hide/remove it then you'll get Oreo recents.
I use a Magisk module to remove the stock launcher. There's adb commands if you don't have root. There's also a quickswitch Magisk module, that's aimed more at enabling third party launchers to handle recents, but it can also force oreo recents.
Click to expand...
Click to collapse
Thanks, will try.
Related
I have heard xposed having lag and battery issues with the grace UX. Anyone have xposed working fine?
Thanks
Brava27 said:
I have heard xposed having lag and battery issues with the grace UX. Anyone have xposed working fine?
Thanks
Click to expand...
Click to collapse
Not sure if Xposed is causing my lack of deep sleep (it wasnt linked to Xposed when I had the same problem after rooting my Note 5..), but everything else seems to be perfect. Mind you, I'm using the N930W8 with Sprint's userdebug, rooted, but all is good! Just have to pin down this battery draining problem.
Does anyone have root and xposed working fine on N930F or N930FD?
EasyWorld said:
Does anyone have root and xposed working fine on N930F or N930FD?
Click to expand...
Click to collapse
Nope hardly not, I tried more than 2 days on the N930F for Xposed (FD is same firmware apparently). Wanams, Official, Systemless Magick. I think it might have to do with Samsung's new OS Grace updates or the fact of encyption. Who knows? Unless someone makes special changes to Kernel or Wanam's Xposed, it will be very hard.
I'm not telling you this for simple fact, Hydra-Rom (Not sure) might be getting closer with own kernel and no doubt that at least some development will happen when Wanam and Chainfire get a Note 7. So my advice is to wait out, backup with titanium backup now that SuperSu works.
And wait until that sweet day or month comes and behold the glory. At least, it's not a Priv in security lockdowns.
EasyWorld said:
Does anyone have root and xposed working fine on N930F or N930FD?
Click to expand...
Click to collapse
Don't take me on my word for this but booting with the latest Hydra Rom 1.15 and it's kernel, Xposed at least so far works without lag and start boot optimization. (Wanam's and N390F)
Haven't fully test Kernel or Xposed Modules (Like 3+) but seems to be going better than super lag or battery death. (New Kernel disabled encryption)
Again, might be something looking into.
EDIT 1: Was working quite well, enabled some modules like Greenify and XinternalSD. Seems like bootloop now affecting my phone, either enabling one of these modules with some settings bootlooped my phone or xposed is simply not just ready yet. Either ways, the very fact that no optimization was needed at the start (Rebooted tons of times to make sure) is progress.
EDIT 2: Don't know what I did, but just manually shut down phone and Phone booted up. I sense some lag (Might be placebo) but Xposed is working. Along with more SuperSu apps not crashing, again I reckon because Kernel disable encryption allowing mounting of /data. If you have the time, try out the new rom with kernel, seems to be getting closer.
Hey community. I would like to ask you a way to avoid the removal of Pixel Launcher after OS updates (monthly updates). Basically, I install the launcher as system app and fix the permissions as for the guides, but as soon an an update comes the launcher is removed. Any tips on how to avoid it? The annoying part is that each time I need to reinstall and set up my preferences. Thanks in advance.
No modifications to /system will persist across stock updates. However, as long as you reinstall the Pixel Launcher via recovery before you first boot back into Android, it won't lose its preferences. You can also install Magisk and then use the Pixel Launcher Magisk module, which will let you save even more effort (you still have to be careful to reinstall Magisk before letting Android boot, though).
Anyone tried Xposed on Oreo?
Yup, tried on my OP3 Oreo 8.0.
It's as awesome as before. Only a couple of complaints though -
1. Safetynet check can not be verified while xposed is active, this doesn't let few apps to work. One workaround is, to disable xposed, restart the phone and then to install and login to such apps. Afterwards, activate xposed and restart your phone again. This is tedious. However, it works. Not everytime, though - to use apps such as Zebpay, you always need your xposed to be disabled. This can be managed, but, again, tedious task.
2. OneTap download isn't working!
I was such a fan of this module. Unfortunately, it doesn't work in my OP3. I've tested the module, and just in case any of you have suggestions on how to make it work, do let me know. Till then, I'll better wait for a new release of the module.
These points are my opinions/feedback about xposed on oreo 8.0 on OP3. However, I love XPOSED and I'm totally in love with android because of the tweaks XPOSED has got to offer.
I have an unlocked redmi note 5 (whyred) and also rooted with magisk and I'd like to get of the annoying ads in the official MI apps such as theme app which didn't disappear even after using adaway .
So if there is another good way to do that please let me now :fingers-crossed:
Rarohd said:
I have an unlocked redmi note 5 (whyred) and also rooted with magisk and I'd like to get of the annoying ads in the official MI apps such as theme app which didn't disappear even after using adaway .
So if there is another good way to do that please let me now :fingers-crossed:
Click to expand...
Click to collapse
I'm able to block every Single ad in my 10.2.1.0 Stock Global Stable Rom, even though I'm not rooted and with locked Bootloader. With Blokada.
This might help,
https://www.xda-developers.com/disable-system-app-bloatware-android/
Also you could try apps like Adguard, Adclear and Blockada, where as Adaway requires root.
There is also an option to turn off system ads by turning off msa app.
https://forum.xda-developers.com/re...orial-how-to-remove-ads-redmi-note-5-t3842425
xell75 said:
I'm able to block every Single ad in my 10.2.1.0 Stock Global Stable Rom, even though I'm not rooted and with locked Bootloader. With Blokada.
Click to expand...
Click to collapse
Hey, I've installed Blokada following your advice, I have a question, does blokada autoruns on your device? After reboot I have to manually open it, if I swipe the app away from the recent screens it closes and have to rerun it manually. I've disabled the miui energy saver for blokada, I've enabled the run at boot, persistent notification, whatchdog and force wakeup (I'm translating since my app is not in english) but still I have to manually run it and I must not close it from the recent screen.
Any ideas?
AccaOC said:
Hey, I've installed Blokada following your advice, I have a question, does blokada autoruns on your device? After reboot I have to manually open it, if I swipe the app away from the recent screens it closes and have to rerun it manually. I've disabled the miui energy saver for blokada, I've enabled the run at boot, persistent notification, whatchdog and force wakeup (I'm translating since my app is not in english) but still I have to manually run it and I must not close it from the recent screen.
Any ideas?
Click to expand...
Click to collapse
Then you have to lock the app in recents menue and your not allowed swiping it away, since MIUI have a very strict energy save management even though you turn it off.
First update since installing Lineageos on Lenovo P2.
The navigation bar along the bottom disappeared. Couldn't be swiped up - had been fixed previously.
Then found other things as well. Fingerprint sensor not working. Pixel launcher failing. Had been using Nova launcher and foolishly removed it thinking I'd reinstall to see if it restored the nav bar. But now stuck with a failing launcher and can't start anything - including Play to reinstall Nova. Just says 'Pixel Launcher keeps stopping, App info, Close App.' Cleared cache from App info as that was all I could do but no difference.
I haven't read it anywhere but are updates cumulative? Ie, can I skip one if I miss it and get all updates rolled up into the next one. I hope so because that's what I did. Jumped from something like 9th August to 30th.
Any ideas?
Current update always include codes from previous builds so you can skip nightlies in between. There are few solutions for your problem. I'm telling you two:
1. Install a third party launcher apk through system settings
2. Reboot into TWRP, wipe system only and install latest update package with nano gApps and it should work.
alirazaagha said:
Current update always include codes from previous builds so you can skip nightlies in between. There are few solutions for your problem. I'm telling you two:
1. Install a third party launcher apk through system settings
2. Reboot into TWRP, wipe system only and install latest update package with nano gApps and it should work.
Click to expand...
Click to collapse
Thanks so much for your help. In fact, while trying your first suggestion I somehow got into Google Play through APK install settings from where I was able to reinstall Nova Launcher. So now I have a partly useable phone again but still with the problems that followed the update in my OP (navigation bar gone, fingerprint sensor stopped working plus the failing launcher - those are just the things I found without looking).
It's disappointing that the update failed though, not least as staying updated was a major reason for moving to Lineage. Any ideas why this might be?
Maybe I should try the second suggestion and reinstall the update by sideloading as described here. So do I use the same file that I use to install LineageOS in the first place from here https://download.lineageos.org/kuntao? It's not stated in the document. And will this wipe the phone clean again?
Finally would I have to re-sideload a GApps package at the same time and should it be Nano GApps as suggested? Originally I installed Open GApps as suggested in the upgrade instructions.
bind00 said:
Thanks so much for your help. In fact, while trying your first suggestion I somehow got into Google Play through APK install settings from where I was able to reinstall Nova Launcher. So now I have a partly useable phone again but still with the problems that followed the update in my OP (navigation bar gone, fingerprint sensor stopped working plus the failing launcher - those are just the things I found without looking).
It's disappointing that the update failed though, not least as staying updated was a major reason for moving to Lineage. Any ideas why this might be?
Maybe I should try the second suggestion and reinstall the update by sideloading as described here. So do I use the same file that I use to install LineageOS in the first place from here https://download.lineageos.org/kuntao? It's not stated in the document. And will this wipe the phone clean again?
Finally would I have to re-sideload a GApps package at the same time and should it be Nano GApps as suggested? Originally I installed Open GApps as suggested in the upgrade instructions.
Click to expand...
Click to collapse
The Pixel launcher in Android 10 force closes if it is not chosen as "Recents provider". Therefore, navigation bar also stops working. Hence, we need Quickswitch app to choose Pixel or any other launcher such as Lawnchair for giving them the mentioned right and that works without any hiccups.
You should install the latest update after wiping system only. You don't need to wipe everything, just wipe system partition.
Nano GApps are taken from Open Gapps website. I've suggested nano GApps because it doesnt include Pixel Launcher hence, stock ROM launcher will flawlessly work. However, if you want to use Pixel Launcher then install Magisk from recovery and Quickswitch module within Magisk. Then open Quickswitch app from launcher and click Pixel Launcher. Quickswitch app will process for a few moments and will restart your phone. Now, choose Pixel launcher as default from settings if it is not used as default and Done.
alirazaagha said:
The Pixel launcher in Android 10 force closes if it is not chosen as "Recents provider". Therefore, navigation bar also stops working. Hence, we need Quickswitch app to choose Pixel or any other launcher such as Lawnchair for giving them the mentioned right and that works without any hiccups.
You should install the latest update after wiping system only. You don't need to wipe everything, just wipe system partition.
Nano GApps are taken from Open Gapps website. I've suggested nano GApps because it doesnt include Pixel Launcher hence, stock ROM launcher will flawlessly work. However, if you want to use Pixel Launcher then install Magisk from recovery and Quickswitch module within Magisk. Then open Quickswitch app from launcher and click Pixel Launcher. Quickswitch app will process for a few moments and will restart your phone. Now, choose Pixel launcher as default from settings if it is not used as default and Done.
Click to expand...
Click to collapse
Many thanks again for your detailed help. Much appreciated.
Went for standard Open GApps just because that's what I had before and had hoped to get it all back as it was. (I've no particular preference for Pixel only that was all that was available to me after updating through updater. ) I've got the update loaded now, sideloaded with adb and TWRP. Unfortunately I seem to have accidentally factory reset from TWRP (thought I was just swiping to unlock and only noticed too late. Doh.)
TBH, this has been a whole lot of hassle for an update. After hours to get this far now have to set phone up from scratch yet again. And crucially, I still don't know why updater failed. Going to be very nervous about running update in future and staying updated was the main point of moving to Lineage in the first place.
But thanks for help again.
bind00 said:
Many thanks again for your detailed help. Much appreciated.
Went for standard Open GApps just because that's what I had before and had hoped to get it all back as it was. (I've no particular preference for Pixel only that was all that was available to me after updating through updater. ) I've got the update loaded now, sideloaded with adb and TWRP. Unfortunately I seem to have accidentally factory reset from TWRP (thought I was just swiping to unlock and only noticed too late. Doh.)
TBH, this has been a whole lot of hassle for an update. After hours to get this far now have to set phone up from scratch yet again. And crucially, I still don't know why updater failed. Going to be very nervous about running update in future and staying updated was the main point of moving to Lineage in the first place.
But thanks for help again.
Click to expand...
Click to collapse
No problem bro. Next time, when you update, follow these things:
1. Keep ROM, Magisk and GApps in a single folder.
2. When updating ROM, just install the ROM and restart.
alirazaagha said:
No problem bro. Next time, when you update, follow these things:
1. Keep ROM, Magisk and GApps in a single folder.
2. When updating ROM, just install the ROM and restart.
Click to expand...
Click to collapse
Thanks again. That's good information. So you recommend not using the Updater but adb sideloading instead?
OK, and I just read this at stackexchange "You normally don't need to re-flash GApps as most GApps installers will install an addon.d script which restores GApps automatically after flashing a new ROM that supports addon.d (LineageOS does so)." So if GApps is in the same folder it finds it automatically I guess.
I'd better clue myself up on Magisk now and a decent backup system.
cheers
bind00 said:
Thanks again. That's good information. So you recommend not using the Updater but adb sideloading instead?
OK, and I just read this at stackexchange "You normally don't need to re-flash GApps as most GApps installers will install an addon.d script which restores GApps automatically after flashing a new ROM that supports addon.d (LineageOS does so)." So if GApps is in the same folder it finds it automatically I guess.
I'd better clue myself up on Magisk now and a decent backup system.
cheers
Click to expand...
Click to collapse
Built in update works as required but if it messes with system partition then you better download update and install it through recovery.
GApps can be restored after update but the point is that you don't need it. System update only replaces the older system files with new ones without touching gApps files. Whereas, Magisk is automatically installed after update if it's in the same folder.