Develop Bugs

[Q] Long boot up time

Does anyone elses DInc 2 take forever to boot up after hitting restart. I swear mine takes like 5 minutes at least. Also the boot animation doesnt last for the whole boot up time. The droid eye moves back and forth twice then just sits there and doesnt move. Seems like a oversite on HTC. Thoughts?

it does take a little bit of time, but 5 minutes?? wow.. you could always go into settings and change to quick boot.

Here's what I'm wondering. If quick boot is available, why would any of us ever use regular boot? Is there some advantage to long boot?

Same problem here. Five minutes may be an exaggeration, but it takes at least two minutes or so. And it seems to make no difference whether I have Quick Boot checked or not. Could this have something to do with running Launcher Pro instead of Sense?

yeah i'm not sure either. but the description says that some market applications/services are disabled if you use quick boot.

When I select restart it does take about 2 minuets to fully boot, but when I just turn it on with its booted in under 20 seconds, quick boot enabled.

aczm1988 said:
Does anyone elses DInc 2 take forever to boot up after hitting restart. I swear mine takes like 5 minutes at least. Also the boot animation doesnt last for the whole boot up time. The droid eye moves back and forth twice then just sits there and doesnt move. Seems like a oversite on HTC. Thoughts?
Click to expand...
Click to collapse
Mine sort of freezes on the Droid eye as well. Mainly with the eye and two black dots to the right of it. It doesn't sit there for long though, but definitely noticeable. I have quick boot on as well.
Sent from my ADR6350 using Tapatalk

[Q] clockwork mod splash screen takes too long

Hello,
Ever since I rooted my phone I've been having this issue...the first image on boot, the clock work mod splash screen takes an awfully long time...like 20-25 seconds before it goes to the boot screen animation where it takes another 20 -25 seconds, is there any way to speed things upand get the phone to boot up as fast as a non rooted device? I'm using AIO Runny 4.01
Thanks

any one knows a way to solve this??

Maybe nobody (me also) gets why this is a problem for you?

leoaamro said:
Hello,
Ever since I rooted my phone I've been having this issue...the first image on boot, the clock work mod splash screen takes an awfully long time...like 15-20 seconds before it goes to the boot screen animation where it takes another 20 -25 seconds, is there any way to speed things upand get the phone to boot up as fast as a non rooted device? I'm using AIO Runny 4.01
Thanks
Click to expand...
Click to collapse
well just my opinion buddy......I don't see the need to fix your issue...as I find it normal....I myself takes 30sec or so before I managed to get into CWM Recovery....
You just need to be patient......unless there is a "real" issue behind it.

Hey
Thanks for the replies. I guess I wasn't clear...
It stays on the first screen - the one with the Joker for 20 - 25 seconds before switching to boot animation where it takes another 20 seconds....thats like almost 45 secs of booting time.
I don't remember it taking that long before rooting? Is it normal??
Thanks

If it is under 1 minute you have got to suck it up my friend...as it is fairly typical. Mine seems to roughly to take up to 50 seconds.
However there are apps available such as rescan media root from the android market. Run the app and select the option to disable media scanner. It basically stops media scan to run on boot, therefore theoretically should save a lot of boot time and make the phone boot faster.

Thanks alot mate!

[Q] How long do Nandroid backups/restore take for you?

Hey guys,
So before I had my HTC One, I stuck around for about 2 years with my HTC Thunderbolt and that was one of the influencing factors in my choosing an HTC device. However, there is a big difference that in some way, my Thunderbolt has the upper hand on.
On my Thunderbolt, recoveries and backups only took about 5 minutes tops whereas on my HTC One, both functions take about an hour. Is this normal? It took that long when I originally made my first stock backup before root and even now while running the latest versions of both CWR and TWRP.
Is this hour duration normal? How long does it take for you guys?

none
Mine takes about 2-3 minutes usually. It would take someone with more knowledge than I to tell you why it's taking so long, but what your experiencing I wouldn't think is normal.
Sorry I can't help more

Yea, mine only takes 2-3 minutes as well...maybe 5 tops.
Sent from my HTC6500LVW using XDA Premium 4 mobile app

Depending on what I'm doing, I flashed back to my pre from back up and that took 5min. But if I need to flash one of my backups of either eclipse ge or vanir. Forget it it takes me an hour or an hour an a half ugh.

Depends on how many apps you have installed, call history size, text messages, everything that will write data will increase the size of your backups thus taking longer. From my personal experience using orange backup and Cwm is the fastest, takes about 10–15 minutes and I usually have a lot of apps installed.
Sent from the One and Only

For anyone who experiences long restores and backups in the future, here's what I did to bring back times back to "normal":
Factory reset via your current ROM.
Wipe data and cache in recovery.
Format SD Card in recovery.
Reflash ROM.
I probably should have done this as soon as I started experiencing these issues but it's all fixed now! Thanks everyone for letting me know that more than 15 minutes was off.

edit:
doublepost

[Q] LS980-Cloudy G3 ROM- TWRP installed&accessible- [email protected] Android is Updating screen

[Q] LS980-Cloudy G3 ROM- TWRP installed&accessible- [email protected] Android is Updating screen
Hello everyone,
I would like to say first of all to the community, thank you for SHARING KNOWLEDGE. That is the key to everyone's success.
Now down to the gritty. My, now, I guess, mess of a LS980. For starters, the phone was running I would say very well considering my abuse. Big overclocks, gaming hardcore, and pushing the storage space hard. I performed a very easy and simple rooting and recovery program installation. If I remember properly, it all started with an app/.apk that sparked my interest with making the phone mine, was Autorec? (red roundish logo?) In some time I decided to install my first aftermarket ROM. I chose and installed without any issues , Cloudys G3 ROM. I cannot however remember the version number. It is by no means recent. I think I installed it last September so maybe 1.0 or 1.2 (sorry so much bad luck with stuff recently) TWRP version 2.7.0.0 is my recovery, and its functional. Unfortunately I do NOT have my apps backed up. I have no space. (just managed to get about 7GB on this PC to try to back them up but there is not external back up option, UNLESS you are OTG cable equipped I am not )
Now, I think, (this has been the state of the phone for about 3 weeks now) this all started to go south when I saw there was a Dorimanx OTA app in the play store. I used his Kernel for as long as I have had the G3 ROM installed. With no problems. So I figure this would be easier for me than button mashing trying to get into recovery mode without popping my screen out the front. LOL Upon using the app, I was informed of an update, I read the included information, and generally knew the deal. I allowed the app to download what it needed and restart and install like a good little computer. And this is where it gets a little grey for me in terms of order and symptoms. I remember checking the status of the install and it read failed! I looked into the reason why, and I was just plain full of junk. I then uninstalled painfully a bunch of rarely if that, used apps and gained back about 2.2GB of space. I ran Dorimanxs app again and let it do its thing and reboot. And again it reported fail! I looked into it more and noticed there were newer Kernels than available on his inter-web. Alpha versions. I located them on my device and rebooted into TWRP mode and selected , then flashed his 10.4.1 Kernel. Everything went fine. Phone reboots, the LG logo is no longer animated, and takes a bit longer to actually boot into a GUI. But it was, luckily.
So now, the phone would be a usable thing for about 3 minutes tops, before a power off, to a reboot. Which at first I didnt notice to be a boot loop. My battery surprisingly went from full to about 6% in no more than 15-20 minutes. I noticed the battery was getting warm like I was running the CPUs maxed under a serious load for a good half hour. Around the range to make someone pull it out their pocket wondering wth? So after the next reboot, power cycle, I jumped back into TWRP mode, and dug around for what I thought was the culprit, Xposed. I was having the worst time with my phone after a major Xposed framework error. I picked up my phone one day and out of the blue the xda framework was telling me that there were so many errors with it and my apps that ran fine, not being installed or activated. Upon looking into it, it was removed from the phone. I belive the order was , stable, 2.5/ 2.6, then I tried the beta 2.7. and thats the version that eventually , either broke, or uninstalled, I think, during those frequent Crashes! I tried to install the previous versions, even going back to the versions that came out last year like 2.4 . But none would install. And the phone grew more unstable in terms of its cooperation with its software. My normal apps and games worked fine. The phone worked the same, the music player, but there were apps that only can work with xposed that I utilize constantly, that were kaput. So I left the phone off. For a while. I had/have no time and really no resources to research and rescue a sunken ship. I come back about two weeks to it and I take a look around in the phones storage and hunt for any kind of recovery and disabler. I found xposed's disabler and flashed it. Same luck as before. About 3 minutes on, then dump.
I dig some more and found a ccc71 back up folder with some hearty backups that I didn't know were still there (no wonder I was always loosing space) and found another xposed installer.zip . I figured well , it didn't make any sense trying to disable something that wasnt enabled in the first place. (thats why I walk away and come back . fresh mind to tackle what stumps me) So I flashed the installed zip and reboot. Same thing, but now it started to loop around one minute. I power down. Found the recovery.zip that was saved on the beater PC and adb pushed it over the the phone. Im not good enough to adb install it. So TWRP'd it and rebooted, and d'oh! Now we just have the motionless LG ball, but flashing blue and green LED. And after about 2 minutes it would black screen, but be on. Not hung or anything. I connected to the PC, it never finds the right stuff but I used adb to verify state. And it said device. It still could communicate and push. I had it dump its debug, surprise! as it flashes that crap as fast as it can up the screen. But Im a PC guy so it was a fun, pause/break over and over till I found something useful. I saw some things that I could recognize like, failed starts, and longer than normal (for a speedy experience) function or call times, but nothing that slapped me with a red flag.
And that ended that nights attempts to fix thanks to the slowest no ram having box I was using to try to learn how to have the debug save to a .txt file on my PC so I could take a good look at the results.
Upon reading forum after forum, I came to something that looked promising, telling me that, that particular boot issue was due to the wrong radio being installed. So I hunted, and hunted, and laaaaaged my arse off and finally found it. Great I thought. Powered up ten or twenty times, finally get into TWRP, tried to flash it. BBBBBAAAAAANNNNT! nope. Downloaded another copy of the file and tried it again. No luck. ( I must say not until roaming around in these forums tonight did anyone bother to mention that you dont flash that radio. You instead have to inject it via LGFlashTool, which I have used before, and its a pain in the butt.
But before I go any farther, make anymore mistakes. I need some help.. I would really LOVE to be able to flash this , slap that, curse its name then hug it and get her working, without having to ditch my 492 apps. If I would have to say goodbye to happy times, I would like to say good riddance to ugly and annoying G3 ROM. I like not flat UI. My phone was depressing me every time I had to do any navigating around inside it. So I would love to go back to KK Stock LG ROM if push came to shove. But if possible I would just like to "repair, and regain access into the phones GUI system". So I could backup my apps. And eventually labor back to OEM Kitkat.
I apologize for the length of the post. But I just dont see the point of ping ponging with partial exchanges of information. I hope I have made my situation clear, and someone knows of someway, I can get my GUI/phone working again. Thanks to all in advance.
"a non functional smartphone, is an oxymoron"

Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart

strangely enough
siggey said:
Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
strange thing,
just about 5 minutes ago, the phone, which I left on sitting at the LG screen by accident yesterday after posting the above, changed screens and presented me with the Launcher selection screen.
I immediately noticed that it looked wrong. Like if the resolution was way off. Like an old low res screen, very dull, sort of blurred looking.
I figured what the heck and tapped the screen and it of course did not immediately respond. It took its sweet time , about 30 seconds to show a change. The menu disappeared and a error message along the lines of , android system UI has crashed.
That is not the message verbatim, it was gone to fast for me to take it all in. And now its sitting at the blank powered on and repeating blue/green LED.
I havent done as you suggested yet. I kept getting results from Norway and other places and didnt understand a thing. But I found a TWRP update from Dorimanx, there was a link to it. And now I have to find my version of the OS. And to be clear, were you suggesting doing a re install, basically a file overwrite? And if so, when doing something like that, do you wipe the Dalvik cache ? Or do you just "dirty flash" it?
Thank you ,

I think that your screen is overheated. Never let the phone in bootloop for long time, it can destroy the screen.
About the cache, is better to clean it, but if I remember well the rom installer alredy do this.
_____________________________________Read more write less and be smart

Nandroid crash

Hello from sunny Spain.... well, it is raining today!
I have made 2 nandroid backups of 2 different ROMs, and I get the same problem with both: once the restore process arrives to some 20%, it jumps to 33%, the phone reboots and remains with the logo forever I have the last TWRP.
What am I doing wrong? Anyone else has gone through this?
Thanks a lot.