Hello!
Hello! I’ve been using this launcher for years, and loving it! I am putting this in the bug report, b/c I have isolated my phone not booting up to Lightning Launcher and can reproduce the problem. I am using ResurrectionRemix ROM on my OnePlusOne. The latest Marshmallow nightly. It is buttery smooth, no issues at all. After the latest update, phone kept getting stuck at boot logo. I spent 3 days going crazy trying to figure what could be wrong. I had completely wiped phone, and reinstalled a hundred times. Every single time, the phone would work just fine, until I restored my apps and settings and then I could not reboot back into phone. After many many process of elimination, I restored everything EXCEPT LL. Phone rebooted fine and worked smoothly, no issues at all. The ONLY thing I did after that is install LL and made it my default launcher. That’s it. I have not even restored my backup and when I tried to reboot the phone, I could not. I repeated this few more times, and always and only did I run into this issue after LL was installed. What could be wrong??? At the moment, I cannot use LL at all. Please advise. Thank you!
]]>
D5 Creation
< ![CDATA[
A normal app isn’t capable of stopping the phone booting up if it was it would be a serious security issue.
]]>
< ![CDATA[
Well, what can I tell you? That’s exactly what its doing. As long as I do not have LL installed, everything is perfectly fine. Only with LL installed do I have booting up issues. It is not a “normal” app in the sense that it is the launcher and is replacing the default google launcher.
]]>
< ![CDATA[
But its not a system app and it’s not a root app either, so it is a normal app. You said you restored your apps and settings my guess would be something to do with that.
]]>
< ![CDATA[
Actually what I said was that after restoring all my apps and settings I had no problems at all. I am currently using the phone without LL and everything is buttery smooth! Reboots no problem. As soon as I install LL and make it my default launcher, that’s when it gets stuck on boot. THanks for trying to think it through though!
]]>
< ![CDATA[
I just tested something else. I can install LL and as long as I do not make it the default launcher (meaning when it ask “just once” vs “always” and I chose “just once”) i have no problems, phone will boot up. However, when I chose “always” and make it the default launcher, phone will NOT boot up. So its 1000000% the cause.
]]>
< ![CDATA[
My bad I cant read lol, it beats the hell outta me :/ only other thing I can think of is if your using Xposed try disabling it. Its caused issues with Tasker and other apps before never stopped them from booting though.
]]>
< ![CDATA[
No exposed…. i know its really weird. Help Pierre Hébert !!!!
]]>
< ![CDATA[
Zsolt Golenya if I were you, I would report this as a bug report for the Rom you’re using.
]]>
< ![CDATA[
Also try installing a different 3rd party launcher as default, just for shits and giggles.
]]>
< ![CDATA[
Oh, yeah, I could have said “help Chris Chastain ” too LOL
So you think this is a ROM bug as opposed to LL bug?
]]>
< ![CDATA[
I have exactly the same since the last update of RR.
So I think something wrong between RR ROM and LL.
Sent a ton of FC reports to Pierre Hébert, hope there is something helpfull in.
hibin maheendran how can we check ?
]]>
< ![CDATA[
I don’t know where those reports are sent because I see none of them in the developer console 🙁 I hope to release a beta soon, in which the builtin crash reporter is enabled (not enabled in stable builds). if you can live with the app not being the preferred launcher for a week or so (if you don’t reboot too frequently) then maybe you can try the beta.
Yes, a launcher is a normal app, and a third party one. As it does nothing of the “preferred app” status, I would say the issue is in the system, although that doesn’t mean it cannot be fixed with a workaround in the launcher.
]]>
< ![CDATA[
I’m on the beta
]]>
< ![CDATA[
Zsolt Golenya don’t know, but if it has same failure with a different 3rd party launcher… That might be a hint?
🙂
]]>
< ![CDATA[
Chris Chastain I’ll check the same , need to do a nandroid backup with “Once” (flashed 10 times during the week end just for that issue)
]]>
< ![CDATA[
Pierre Hébert I confirm the issue
set Google Launcher as always : no issue
set trebuchet as always : no issue
set Smart Launcher as Always : no issue
Set LLx as Always : bootloop , I think it’s because LLx is force closing and during the startup there is no message.
hopefully I’ve done a nandroid backup with LLx and Once , restoring now 🙂
]]>
< ![CDATA[
Nova, Trebuchet, Next, Google launchers no issues.
]]>
< ![CDATA[
Zsolt Golenya yes only LLx. So really it’s an issue on Lightning Launcher.
]]>
< ![CDATA[
Bruno-Isa LAMOUR-ARNOULD weird, there is no beta at the moment?! Could you check the version number in the main settings screen please?
Crash of a launcher is not an issue on Android since 2.3 (or maybe 2.2?), this is detected and gracefully handled by the system which then asks the user to select again the preferred launcher. And believe me I tested this feature a lot, lol 🙂
]]>
< ![CDATA[
Pierre Hébert I’m on V12.8.1 (r2521)
]]>
< ![CDATA[
Fine, this is the stable version then (at least it’s labeled as is).
]]>
< ![CDATA[
I’ll check if I could produce an adb logcat
]]>
< ![CDATA[
Pierre Hébert thanks for looking into this. Crash of the launcher is not the issue, it’s nastier than that. Can’t reboot, or to be exact, it gets stuck on booting up. I tried dirty flashing rom, gapps, but the only solution is to do a full wipe and reflash everything, or to do a nandroid restore. Either way is a 30 min ordeal each time. 🙁
]]>
< ![CDATA[
yes a restore from a nandroid backup where you set as Once
]]>
< ![CDATA[
So nothing to be done about this? We just can’t use LLX anymore? Any clue what could be causing this?
]]>
< ![CDATA[
Zsolt Golenya we’ll fix it. I’ll take a logcat.
Use “Once” for the moment , not a big deal for me currently.
]]>
< ![CDATA[
Tested couple more launchers and they are all fine. What is once Bruno-Isa LAMOUR-ARNOULD?
]]>
< ![CDATA[
Zsolt Golenya set Run once and not Always
]]>
< ![CDATA[
Oh you mean not set it as a default launcher .. got you. I think that would drive me insane after about a day or so LOL
]]>
< ![CDATA[
Zsolt Golenya yes
Waiting logcat and analysis
I’ll try to produce a logcat tomorrow
]]>
< ![CDATA[
Bruno-Isa LAMOUR-ARNOULD good news! I just updated to latest RR nightly and the problem seems to be gone! I installed and made LLX the default launcher and it rebooted fine! What do you know! I still don’t get why only LLX had incompatibilities with the rom, but the update made it go away.
]]>
< ![CDATA[
Wow very good news
]]>
< ![CDATA[
Great. This isn’t so unexpected. In French : “Il est urgent d’attendre”…
]]>
< ![CDATA[
Pierre Hébert lol
I confirm : working fine wirh last ROM upgrade
]]>
< ![CDATA[
I once used lots of custom roms.
When having a strange issue such as this, ALWAYS suspect the rom build first!
]]>
< ![CDATA[
Chris Chastain so strange as all other launchers had no issue.
]]>
< ![CDATA[
all other tested launchers, that makes a difference 😉
]]>
< ![CDATA[
Pierre Hébert lol
I tried a lot of launchers.
(Nova,Apex,SL, Lucid Launcher,Google Now Launcher,Trébuchet, LauncherX,Total Launcher,SweeterHome2)
Probably as yours is the most “techie” it was more “sensible”
I don’t have all FC I had before 🙂 only had 1.
Could you work on securing the lockscreen in LL ?
Loading first the lock desktop when phone is starting ?
]]>
< ![CDATA[
Is one of these launchers a paid app ? I mean not with a separate key or in-app purchase. It wouldn’t surprise me if the issue was linked to secure storage. Also if the problem went away in the ROM upgrade, chances are that the reason can be found in the changelog.
]]>
< ![CDATA[
Pierre Hébert I have
Nova Pro
SL 3 pro
Lucid Launcher Pro
Yes I’ve checked and bought some launchers before finding yours 🙂
And very happy with LLx.
]]>
< ![CDATA[
Nova Prime is just a key for the free launcher. Don’t know about those other two.
]]>
< ![CDATA[
No issue,it’s fine now.
]]>