I bricked my phone last night, fixed it. Screwing around with TWRP I bricked it again today, fixed it. In my frustration over yapp store and Auraro store not working with anonymous log in I installed aptoide store and was doing some updates. One of them was the update for Oneplus Launcher. I did not realize Joe Anybody could upload files so I really have no idea what I installed( it did have the green ok to install check makr though). Since then the launcher has not worked.
Used Migrate to do a dirty restore ( not the smartest idea), thinking it would restore my working launcher and layout.
So far I have installed the nova launcher with xXxNoLimits and been able to navigate. I have tried uninstalling the launcher via Titanium, rebooting, and reinstalling the Android 9 version, didn't work. I did a dirty flash of oos 9.0.17 that I downloaded from Oneplus and now I have no launcher at all so I flashed xXx again and have the Nova Launcher.
My profile for xXx leaves the OP launcher installed and adds Nova.
I have tried everything I can think of.
Thought about taking the plunge and installing Android 10 but, from what I am reading, it is buggy, *****y, and not playing well with TWRP and Magisk.
I am still pretty new to this fun so be gentle!
Thank you in advance.
Related
I've always been a fan of the stock launcher since I never cared much to use settings available in custom launchers to tweak settings. However, with the new Nova Prime I really wanted to give gestures a try. After hearing great things about the launcher I decided to purchase the app and start fiddling with it. Overall the launcher is very fast, stable, and the homescreen gestures are awesome.
However, I'm noticing that immediately after unlocking the phone the screen flickers once before opening the homescreen. I've tried disabling Nova launcher to see if the stock launcher did this as well. However, as I suspected, the stock launcher fluidly fades from the lockscreen to the homescreen with no flicker at all.
Is anyone else experiencing this issue? Is there a setting I can adjust to fix this? I'd love to keep using Nova but unfortunately this flicker is annoying me.
Thanks in advance.
No issue's to report with nova launcher that's the only launcher i use:good: don't like stock I uninstall it whenever i flash a new rom. Some guys put nova into there roms. I have the prime version. Do you have your animations on? You could try disabling the animations if that helps..
yyz71 said:
No issue's to report with nova launcher that's the only launcher i use:good: don't like stock I uninstall it whenever i flash a new rom. Some guys put nova into there roms. I have the prime version. Do you have your animations on? You could try disabling the animations if that helps..
Click to expand...
Click to collapse
Thanks for the advice. I just disabled animations and it made the transition a lot faster, which I suppose I can live with. I just wish it was fluid during unlock like the stock launcher is. Aside from that it's perfect.
EDIT: I decided to follow your tactic and uninstalled the stock launcher, then wiped cache, dalvik cache, and fixed permissions. After restarting I'm happy to report that the unlock flicker has completely gone away. This is the case even with animations set back to 1x. I'm guessing the phone was trying to load the stock launcher for a split second before loading Nova Launcher, causing the slight flicker/delay. I'm a happy camper now, thank you!
sn0warmy said:
Thanks for the advice. I just disabled animations and it made the transition a lot faster, which I suppose I can live with. I just wish it was fluid during unlock like the stock launcher is. Aside from that it's perfect.
EDIT: I decided to follow your tactic and uninstalled the stock launcher, then wiped cache, dalvik cache, and fixed permissions. After restarting I'm happy to report that the unlock flicker has completely gone away. This is the case even with animations set back to 1x. I'm guessing the phone was trying to load the stock launcher for a split second before loading Nova Launcher, causing the slight flicker/delay. I'm a happy camper now, thank you!
Click to expand...
Click to collapse
Nice I'm glad it worked for you that's the best launcher:highfive:
sn0warmy said:
Thanks for the advice. I just disabled animations and it made the transition a lot faster, which I suppose I can live with. I just wish it was fluid during unlock like the stock launcher is. Aside from that it's perfect.
EDIT: I decided to follow your tactic and uninstalled the stock launcher, then wiped cache, dalvik cache, and fixed permissions. After restarting I'm happy to report that the unlock flicker has completely gone away. This is the case even with animations set back to 1x. I'm guessing the phone was trying to load the stock launcher for a split second before loading Nova Launcher, causing the slight flicker/delay. I'm a happy camper now, thank you!
Click to expand...
Click to collapse
I am experiencing the same issue now. i tried uninstall the stock launcher and then wiped everything else. but still didn't work for me. i was wondering what permission did you fix?? could you please tell me? thank you
indomi said:
I am experiencing the same issue now. i tried uninstall the stock launcher and then wiped everything else. but still didn't work for me. i was wondering what permission did you fix?? could you please tell me? thank you
Click to expand...
Click to collapse
I get this issue on all launchers, when using stock AOSP 4.3 and CM 10.1
Has anyone deduced what the problem is caused by?
patsmike said:
I get this issue on all launchers, when using stock AOSP 4.3 and CM 10.1
Has anyone deduced what the problem is caused by?
Click to expand...
Click to collapse
Ha! Forgot all about this thread. For me, every time I install a fresh ROM the first thing I do after initial setup is install Nova Launcher. After doing this I uninstall the stock launcher or the trebuchet launcher (on CM10.1 ROMs) and wipe cache/dalvik and fix permissions. After doing this I never see the initial screen flicker anymore and I've used this method with all sorts of ROMs.
However, now that I'm on the stock 4.3 JWR66V image, without root, I am getting the same screen flicker again. I'm just dealing with it until an updated SuperSU or Super User zip is available which will allow me to root, install root explorer, and uninstall the stock launcher. I'm confident that going with the same procedure I mentioned above will solve the issue once again.
Good luck!
sn0warmy said:
Ha! Forgot all about this thread. For me, every time I install a fresh ROM the first thing I do after initial setup is install Nova Launcher. After doing this I uninstall the stock launcher or the trebuchet launcher (on CM10.1 ROMs) and wipe cache/dalvik and fix permissions. After doing this I never see the initial screen flicker anymore and I've used this method with all sorts of ROMs.
However, now that I'm on the stock 4.3 JWR66V image, without root, I am getting the same screen flicker again. I'm just dealing with it until an updated SuperSU or Super User zip is available which will allow me to root, install root explorer, and uninstall the stock launcher. I'm confident that going with the same procedure I mentioned above will solve the issue once again.
Good luck!
Click to expand...
Click to collapse
You're kidding, seriously? That's it? That's so sad on Google's part (for such a terrible launcher)
But thanks for the hint, I've been searching far and wide for this answer - ill let you know if it works in 4.3 (I'm rooted). I'm surprised so little users notice this annoying stuff!
Sent from my Nexus 10 using xda app-developers app
sn0warmy said:
However, now that I'm on the stock 4.3 JWR66V image, without root, I am getting the same screen flicker again. I'm just dealing with it until an updated SuperSU or Super User zip is available which will allow me to root, install root explorer, and uninstall the stock launcher. I'm confident that going with the same procedure I mentioned above will solve the issue once again.
Good luck!
Click to expand...
Click to collapse
I followed your instructions but I still get flickering from time to time on stock rooted 4.3, though maybe less than before... Any other step that I may be missing that you didn't mention?
Sent from my Nexus 4 using xda app-developers app
Hey guys,
Pixel launcher seems to be constantly crashing after flashing the 7.1.1 ota with twrp. When I flash the 'pixel stuff v1.1' (that installs pixel launcher and navbar via twrp) I get a constant system UI error.. So I had to restore my nandroid backup. Also, installing apk files doesn't seem to work anymore. I get an error saying that there was a problem parsing the package? I tried multiple apks.. So, does anyone else has this?
The problem is the SystemUI apk... It is from 7.0 not from 7.1.1, this is the reason why it crashes.
JotaJgreen said:
The problem is the SystemUI apk... It is from 7.0 not from 7.1.1, this is the reason why it crashes.
Click to expand...
Click to collapse
Yeah I've noticed it just before reading this post, thanks anyway! Installing apk files work when I do it via root explorer, it just doesn't work when I try to installl them by going to downloads.. Oh well.
I've got the pixel launcher working now (made the app a system app using titanium backup. It kept hanging on processing, but after rebooting it seemed it worked). If anyone's able to get their hands on the new pixel launcher apk (with the weather info on the home screen), feel free to share it with us!
swa100 said:
Yeah I've noticed it just before reading this post, thanks anyway! Installing apk files work when I do it via root explorer, it just doesn't work when I try to installl them by going to downloads.. Oh well.
I've got the pixel launcher working now (made the app a system app using titanium backup. It kept hanging on processing, but after rebooting it seemed it worked). If anyone's able to get their hands on the new pixel launcher apk (with the weather info on the home screen), feel free to share it with us!
Click to expand...
Click to collapse
I was able i made my own flashable zip with the pixel_launcher, and i have the weather next to the time in homescreen.
swa100 said:
Hey guys,
Pixel launcher seems to be constantly crashing after flashing the 7.1.1 ota with twrp. When I flash the 'pixel stuff v1.1' (that installs pixel launcher and navbar via twrp) I get a constant system UI error.. So I had to restore my nandroid backup. Also, installing apk files doesn't seem to work anymore. I get an error saying that there was a problem parsing the package? I tried multiple apks.. So, does anyone else has this?
Click to expand...
Click to collapse
Are you talking about non pixel phones???
If yes flash the pixel launcher again.....
Install backup script....to survive ota...
Here's the link to latest pixel launcher and its backup script....
http://forum.xda-developers.com/android/general/addon-d-pixel-launcher-backup-script-t3486478/page1
Hello all, I have updated to OOS 9.0.16 using the twrp method with twrp 3.2.3-2, rooted with magisk 19.3. I'm converted from T-Mobile. Since the update, my recent app list has changed configuration from horizontal to vertical. It's not a big deal as everything is working fine but I prefer horizontal. Is there something in settings that I've missed or do I need to reflash? I asked in the main thread but no one replied.
The reason the recent app list configuration changed was I froze the OnePlus launcher which I had not done previously. Once I unfroze it, everything went back to how it was previously. It was a coincidence that I had updated about the same time that I froze that launcher.
Hello..
I have a One Plus 6T since 1 year and this is the first problem that I have..
I updated the phone a few weeks ago with the last update 9.0.17
Yesterday I did a Wipe data+cache to restore the phone like new..
But I have one problem.. I always disable the apps of google like Duo, Chrome, Youtube and Photos.. But once they are disabled in a few hours automatically they came enabled again.. Why!!???
I know that using adb I can delete those apps but I prefer to use the disable option of the system.. In the last versions of the OxygenOs this was working fine but not now and I know that there is more people with that problem. Anybody knows why,??
Many thanks for the help
I freeze some apps with sd maid as I noticed the same or similar issue
I believe is has to do with the OOS update. I had that problem as well before. I am rooted so I used Titanium to freeze the apps. When things update it appears the app is functional and does not reinstall it.
If you are rooted, I HIGHLY HIGHLY recommend the xXxNoLimits Magisk module. It allows you to debloat both Google and Oneplus apps.
Many thanks for the answers.. I just want to use the tools that offer the system.. I think that is the last update because in the old ones this works like a charm.
I have not rooted yet the phone because I think that OxygenOS works fine without root maybe in the future I will start with magisk modules and custom roms but for now I'm going to wait.
I'll keep waiting for new OS Updates and maybe is solved. Many thanks for the help.
Hi. I have a Xiaomi MiA1, Lineage 16.0 (I try to update it two or three times per week). It is rooted. I use openGapps.
I have a problem since yesterday: suddenly, my phone got a lot of lag that makes impossible the use. KLWP got closed (it stopped being the default background), Nova Launcher was lagging and restarting several times. Openning any app was impossible, including the settings and system, it freezes and closes, returning to the launcher home screen... I tried to stop, clean data and delete klwp, nova, but i got the same result. The minutes passed and it got worse. Finally, the phone freezed, the clock wasn't working, so the only solution was doing a manual soft reset.
So, yesterday I did a dirty flash, because I didn't have a recent backup. I used SDMaid database feature in the morning so I tought maybe it was bad executed and was the origin of the issue. I tried to rescue some information (to backup some app data) with oandbackups. I cleaned caché and did a Factory reset. It seem to work. and do a clean installation. at first, it seem like it worked. I installed the apps I had by my Google account, and went to sleep. Today, it was ready, I turned it off and charged it, and in the morning: again the crash. So I did a clean installation. Again, it seemed to work. It installed all my apps and... crash again. I fear it could be some launcher issue? any prob with lineage? Any app? How can I know whats happening?
Sorry for my bad english. Any help would be apreciated.
vainille said:
Hi. I have a Xiaomi MiA1, Lineage 16.0 (I try to update it two or three times per week). It is rooted. I use openGapps.
I have a problem since yesterday: suddenly, my phone got a lot of lag that makes impossible the use. KLWP got closed (it stopped being the default background), Nova Launcher was lagging and restarting several times. Openning any app was impossible, including the settings and system, it freezes and closes, returning to the launcher home screen... I tried to stop, clean data and delete klwp, nova, but i got the same result. The minutes passed and it got worse. Finally, the phone freezed, the clock wasn't working, so the only solution was doing a manual soft reset.
So, yesterday I did a dirty flash, because I didn't have a recent backup. I used SDMaid database feature in the morning so I tought maybe it was bad executed and was the origin of the issue. I tried to rescue some information (to backup some app data) with oandbackups. I cleaned caché and did a Factory reset. It seem to work. and do a clean installation. at first, it seem like it worked. I installed the apps I had by my Google account, and went to sleep. Today, it was ready, I turned it off and charged it, and in the morning: again the crash. So I did a clean installation. Again, it seemed to work. It installed all my apps and... crash again. I fear it could be some launcher issue? any prob with lineage? Any app? How can I know whats happening?
Sorry for my bad english. Any help would be apreciated.
Click to expand...
Click to collapse
Keeping in mind the kind of apps you mentioned, I'd go with an app+data backup of those apps you installed and uninstall them completely, check if problem is still there.
I suspect you're facing a compatibility or configuration issue, since both apps are related to home screen.
If problem is solved, first read if those apps are actually compatible with ROM and OS version, then you could try to install just one app, without data, and check if things go well (give it a day), same with the rest until you can confirm OS is working well with apps just installed, no changes made in them yet... In other words, were trying to confirm that problem comes from apps and/or their configurations, so you could somehow report those issues to apps developers. You can use Catalog or other apps to record System logs until app crashes.
On the other hand, if problem is still there, even before you started to reinstall apps, then Dirty flashing isn't a good choice in that case, since it preserves System configurations, no mention your device is rooted, were user changes are present... you are opened to different problems, worse if you use an old Magisk version, or installed modules there, or apps that force your OS to do things it doesn't do in it's original state.
So, as you were so dare to go with a dirty flash, you could better go with a clean flash instead.
Erase any system lock protection (fingerprint, pattern, etc), do a ROM Backup from TWRP, flash latest firmware and make a clean install of the latest version of the ROM of your choice, keeping in mind their own flashing procedure.
As with above reply, if a completely clean install doesnt work, consider going back to a previous lineage release. If it still doesnt work, consider a full EDL stock rom reflash using MiFlash -- then flash your custom rom.
KaaMyA said:
Keeping in mind the kind of apps you mentioned, I'd go with an app+data backup of those apps you installed and uninstall them completely, check if problem is still there.
I suspect you're facing a compatibility or configuration issue, since both apps are related to home screen.
If problem is solved, first read if those apps are actually compatible with ROM and OS version, then you could try to install just one app, without data, and check if things go well (give it a day), same with the rest until you can confirm OS is working well with apps just installed, no changes made in them yet... In other words, were trying to confirm that problem comes from apps and/or their configurations, so you could somehow report those issues to apps developers. You can use Catalog or other apps to record System logs until app crashes.
On the other hand, if problem is still there, even before you started to reinstall apps, then Dirty flashing isn't a good choice in that case, since it preserves System configurations, no mention your device is rooted, were user changes are present... you are opened to different problems, worse if you use an old Magisk version, or installed modules there, or apps that force your OS to do things it doesn't do in it's original state.
So, as you were so dare to go with a dirty flash, you could better go with a clean flash instead.
Erase any system lock protection (fingerprint, pattern, etc), do a ROM Backup from TWRP, flash latest firmware and make a clean install of the latest version of the ROM of your choice, keeping in mind their own flashing procedure.
Click to expand...
Click to collapse
I made a clean flash in the morning, with the same results, so there's when I thought it could be an app the main problem. It worked with Nova a few hours.
I just followed your instructions, I installed the last firmware (the jan one) and the last rom of lineage. I didn't installed the apps in my google backup so I can install them and check how is the behaviour. I will install CatLog so I can check the logs too! I really hope installing the firmware was enough. Thank you very much!
ayunatsume said:
As with above reply, if a completely clean install doesnt work, consider going back to a previous lineage release. If it still doesnt work, consider a full EDL stock rom reflash using MiFlash -- then flash your custom rom.
Click to expand...
Click to collapse
I was planning to reflash the custom ROM but I couln't find the latest one that's compatible with MiFlash. I really hope the clean install is enought... thank you
I was planning to reflash the custom ROM but I couln't find the latest one that's compatible with MiFlash. I really hope the clean install is enought... thank you[/QUOTE]What our partner said was flashing stock (original) ROM.
In any case, if you went with a clean flash, try to leave your system free of user installed apps for a few and check how it goes.