Database Info

[Q] HTC Desire, rooted, bootanimation display/size issue

Hi everyone. This is a weird thing - I haven't found anyone with a similar issue, either here or with Google-fu.
I successfully rooted my HTC Desire a while ago (S-Off) and was pretty happy with it, the LCARS bootanimation installation also went well. After trying out a lot of apps, finding the best configuration for the phone etc. I decided to format and set up the whole thing again on Monday, to have a clean installation and no more space issues.
Although I went for the CyanogenMod V7.1.0-RC1 this time 'round I somehow doubt that has something to do with it, but who knows. Okay, SD card was set up anew, custom mod got installed, everything went as smoothly as it possibly could. (cool story, bro)
However, after I moved the bootanimation.zip into the system\media folder and rebooted, the animation started, but only at half the size it usually has, in the middle of the screen. I tried another one and it was the same thing. The longer one of the two also broke off in the middle with a brief flash, as if I'd pressed the Power button, then stayed dark until I pressed the Power button twice (turn off/ back on), only then it would show me the pin number display.
Apart from that the phone works perfectly.
It's not an incredibly important issue, just something I find weird and would like to fix, if possible. Does anyone have an idea what could be the source of this?

Doesn't anyone have the slightest idea?

you try flash bootanimation over Android Flasher..

Hi majko11293 - first of all thanks for pointing me to this programm. I'd used it before (worked brilliant with my own custom splash screen), but somehow lost it again.
Anyway, even when flashing it with Android Flasher, the bootanimation stays at half size. The animation itself changes depending on which one I choose, but the size issue remains...

[Q][Xoom 2] Severe screen burn-in (I think)

I using my Xoom earlier today and after a while I noticed that the display looked a bit strange. On closer inspection/further use, there is *massive* ghosting/burn in (I think).
If I turn the screen off/on, I can actually see through the lockscreen to the homescreen underneath. When I unlock it I can see previous apps burned in there.
If I shut it down and reboot, I can see the homescreen through the bootscreen (which should be completely black excepting the red Moto logo and the ripple effect).
I've only had it for about a month and mostly use it for browsing the web/facebook and reading comics. I could understand gradual burn-in if I was using a certain app really heavily but that isn't the case here. It seems to have gone from fine to completely f**ked in the space of about half an hour.
I guess my question is, is there any chance it's software based and a factory reset will help or do I go back to where I got it and try to get it repaired/replaced under warranty? And if I do take it back, is the fact that I rooted going to cause problems?
*************
After a factory reset (which did nothing) I used OTA RootKeeper to try and unroot before sending it to Motorola (turns out it's only a temp unroot), then used Titanium Backup to restore apps + data and the display returned to normal as suddenly as it broke 0_o
I have no idea what caused the problem and no idea what fixed it but it seems fine now 0_o

[Q] Screen stutters randomly and continuously

I have had my nexus 5 for 7 months without a single issue. I'm running a Sabermod Slimkatbuild and have been for a month with Uber kernel and just today had a issue with screen stuttering. I have had no issues to date. I was flying when this all started so phone was in airplane mode I was listening to music with Play Music from my menova usb otg and typing in quick office. My keyboard and navigation bar started stuttering in and out. I stopped all apps and rebooted and it continues in landscape and portrait on every screen from the boot animation to the app drawer. The only screen it doesn't appear on is the google initial splash screen. I have wiped cache and dalvik and restored a nandroid. Issue persists. The best way i can describe the issue is it appears that my screen size keeps changing and navigation bar rises up from the bottom of the screen overlapping the first one it also effects the widgets keyboard and pattern unlock. I am in the process of downloading the factory images to wipe the device and start fresh but am still trying to figure out what caused this.

Ok after flashing factory images the stutter still appears. It looks like it is the hardware issue I was afraid of and will be starting RMA.

[Q] How to fix an unbearably slow Nexus 5?

After installing Lollipop, everything became unbearably slow. I've tried flashing multiple ROMs, both Lollipop and Kitkat, but everything remains so slow: the actual boot-up process and the ROM itself. Does anybody have any ideas about what can be done about this? In fastboot I see hammerhead D820(H) 32GB; HW version rev_11; Bootloader version HHZ12d, Baseband M8974A-2.0.50.2.22. Lock state is unlocked. Any suggestions will be highly appreciated!

Wipe cache and see if that helps and disable Chrome's integration into the app switcher. Also get rid of Facebook and FB Messenger.
Sent from my Nexus 5 using XDA Free mobile app

Instead of Lollypop try some LSD

Thanks. But it is that slow even before any of these apps are loaded (e.g. after I do a factory reset and flash a new rom). Is it possible that Lollipop did sthg to the hardware? If so, how could I find out? Just to give you an idea about how slow exactly it is: when I am typing 5 letters at normal speed, it takes until the fifth letter before the first letter actually displays on the screen. I should also note that when the screen goes off, I can no longer get it on again without a reboot...

I'm still trying to figure out what this might be. I first thought my problems were similar to those that others have described, but I now think they be different. Here are some of the issues I'm encountering:
when I boot up the phone (whether in kitkat or lollipop), the initial android (animation sequence is already incredibly slow
there are all sorts of strange things happening with my screen. When it goes to sleep in Android, I can not wake it up anymore. When it goes to sleep in recovery, and I push the power button, the screen goes (again after some time) from pitch dark to a slightly 'lit' dark, but it never displays anything, and I have to reboot again to get the info on the screen. Also, the screen is even slow in twrp - when I swipe to do a factory reset, for instance, there is also a noticeable lag.
I have tried with various ROMs (both stock and not); with ART and Dalvik, etc. but none of these changes seem to affect the slow screen issues
Does anybody have any ideas about what the problem might be? I should also add that we had the screen replaced a few months ago - could that have something to do with it?

sdspieg said:
I'm still trying to figure out what this might be. I first thought my problems were similar to those that others have described, but I now think they be different. Here are some of the issues I'm encountering:
when I boot up the phone (whether in kitkat or lollipop), the initial android (animation sequence is already incredibly slow
there are all sorts of strange things happening with my screen. When it goes to sleep in Android, I can not wake it up anymore. When it goes to sleep in recovery, and I push the power button, the screen goes (again after some time) from pitch dark to a slightly 'lit' dark, but it never displays anything, and I have to reboot again to get the info on the screen. Also, the screen is even slow in twrp - when I swipe to do a factory reset, for instance, there is also a noticeable lag.
I have tried with various ROMs (both stock and not); with ART and Dalvik, etc. but none of these changes seem to affect the slow screen issues
Does anybody have any ideas about what the problem might be? I should also add that we had the screen replaced a few months ago - could that have something to do with it?
Click to expand...
Click to collapse
Probably the replacement screen has been reconnected poorly. There's nothing you can do on software side, for me, it's more like a hardware problem.

System Unresponsive with 5.1 Stock Rooted

Anyone having the same issue and have found a solution?
Phone suddenly stuck at some instances even with non-extensive usage.
Yesterday I was only using Facebook app. When messenger bubble pop up, my phone suddenly spiked. Moved once and then it got stuck already. You'll notice that it's not Facebook app only that's not functioning since nav. buttons are also stuck. You can't go press home and clear recent apps/hibernate apps. Power and volume buttons are also not functional.
So I assume the main system crashed. I only did a long press on power button to restart.
I installed Franco kernel r73, and thought that issue would only occur with stock kernel.
However, it occurred again today, I was viewing photos in Stock Photos app. I haven't started viewing the first 10 images yet, so memory should not be consuming that much. I turned on the auto rotate to view the image larger. When I turned the phone landscape, it reacted like it's about to rotate. And suddenly it got stuck. This time, power button is functional. It turns the screen on and off but it still turns to the same stuck screen, not the lock screen.
I've been experiencing this since 5.0.1. and almost everyday since I updated to 5.1.
I'm not sure if this is a hardware issue on my unit since mine is already about 1 year and a half old. I don't want to buy another phone yet!
Or is this a common issue nowadays due to Lollipop upgrade. If so, then could you provide temporary fix before they update this on 5.1.1.
Thanks a lot!

I had something similar . When I put forward the curtain hangs notice and then everything worked fine

Meh

I've seen this behavior on my Nexus 5 only on 5.1, and I'm pretty sure, it was introduced with that specific lollibug version. It's really annoying, that you have to reboot the phone every two or three days to avoid the freezes.
There's already in issue for that, it has got the ID 161032.