Hey,
I have a G920F and the boot animation is not working as it should. I'm on 6.0 Beta and don't think the problem is coming from the beta because if I remember correctly, the first time I booted the beta everything went smoothly. I am not rooted and the phone is completely clean.
The problem isn't a big one, but it isn't working normally. When I boot my S6, the 'Galaxy S6' screen comes, then no boot animation is shown, a black screen is shown instead, then after the small vibration, the boot animation is then shown without the sound. (an the phone is not in silent/vibrate mode)
My guess is flashing a new stock ROM fixes the problem, but I don't have enough time to sort the settings and stuff out after flashing.
Someone may be able to help?
Thank you,
I have the same problem. Check Marshmallow thread, quite many people have same problems too. That's why it's called "Beta" . Nothing to worry about.
Related
I need some people to test out an app that previews boot animations on the device. It also can set the boot animation (requires root). This is a complete rewrite of the original version that is currently on the market. This version is using OpenGL to render the animations, which allows for the larger animations to actually work.
As I said, I just want to get an indication of what devices / android versions it is working on, and which ones its not. I still have a bit to do with the OpenGL, as the frames are rendering inverted, but this is just an alpha test
Note: If you are going to test it out, you must have the AndExplorer app installed on your device as well.
If you test it out, please post your device, and if you were able to see the boot animation.
I have attached 3 boot animations, if you do not have any to test with.
Thank you for taking the time test.
question
okay i am running android 2.2 froyo and tested the app out i was able to see the star wars logo one but it didnt take up all of the screen and it was in the bottom left hand corner and was fairly small but i was not able to load the matrix or the other one it just sat there on the white screen and said loading so it seems like some may work and others don't but its a wonderful app if its able to test all boot animations it will save me loads of time cause then i can just preview them instead of having to install them to see what the look like
okay so like i said earlier i have the moto droid running android 2.2 and the matrix boot animation didnt load in it but i also tried some of the added functions in the app such as setting a boot animation from your sd card to be your default boot animation and that didnt work but if you were able to get this app to were you could preview boot animations and then set them to play when your phone boots up i would give you a big kiss lol but i love the idea
i have the samsung moment and when i tried it, the animation showe up on the bottom half of the screen for like 2-3 seconds then went blank.
On Samsung Galaxy Spica 2.1 same problem, animation is displayed normally, but only in the lower left corner.
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...
Hi there fellow robot lovers (or killers as it may be) !
Before we start, both identical phones (public mobile zte n762), both rooted, both booting normallish, meaning they get to keyguard screen, apps are starting, messages coming in, etc. Only one is activated, which would be the one with the broken screen, which boots fine, the touch membrane works, it's just the screen only displays pure white light, from total dark to overbright (meaning brighter than full brightness)
What I want from this one is an up to date backup that I might flash on the other one when its softish brick status is resolved.
Then, I can think of hacking the hardware itself, as in changing screen.
Goal for this one is to get a full backup so I can then mess around with it. Or if someone knows that the screen is not dead, since it does light up, I'm all ears on way to play with it. After a backup.
For the little history : I dropped my activated phone while trying to figure out the problem with the other one, to my great dismay and no immediate hilarity I had been running it for more than 4 months with a nasty crack on the screen, and it seems the dropping from a foot high the other night was the shock that sent it over the top.
Now it seems this can also be caused by software glitches ? aka White Screen Of Death
Now, the soft brick phone, which I got for nothing before it was thrown to the garbage (supposedly defective, it was just very barebones, and missing its sdcard)
Now, why do I say very softly bricked ? Well, it works, fully boots, and I sometimes manage to get a glimpse of the running OS "behind" the boot anim when I let if fully boot.
It's running a varianf of the Warp Cream sandwich rom for the n762, called Ice Cream Sandwich 420
It's like the boot anim is looping as an overlay over the running OS. Even managed to get Text+ in the foreground yesterday and chat with a buddy for a while.
Now, why didn't I just wipe it and reinstall ? For one, I thought [ I had no copy of the rom, just a cwm recovery backup once it started acting up.
Mostly, because the challenge in getting it (both phones if it so happens the screen on the other one can be brought back to normal operation) back to glorified PDA status without wiping it, as that's a bit like the good ole, reinstall DOS/Windows/etc. tech support level 1 answer, isn't it ?
So what options exist for soft brick to resume normal activities without wiping the whole thing ?
What could lead to the custom boot anim playing as an overlay to the OS ?
All ears and eyes on your suggestions, shouldn't be that hard for someone who knows, as I have read quite a bit of information that doesn't agree with each other...
anything in italic is edit(s)
Hi! I manually installed the Android 5.0 update by unlocking the bootloader and manually pushing the files onto my Nexus 5. Everything is working fine but since I installed it, it noticed that when I plug my cellphone and the screen goes off, the phone is acting really strangely. The screen keeps on flickering, the shutting down screen sound plays in loop, my wallpaper goes back to the factory one, and my phone is unusable. The weird part is that when I unplug it, it goes back to normal, except the wallpaper that does not go back to the one I chose.
Any ideas why it's doing this? Before that, I did not have any problem whatsoever.
Thanks a lot for your help!
The problem is exposed here: https://code.google.com/p/android-developer-preview/issues/detail?id=82
It was an issue on the preview build with French France... Google fixed it. However they didn't fix it for French Canada.
The workaround is to set the os language to US English or French France.. And wait for a fix from google
Thank you! It works now!
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.