Database Info

Need Alpha Testers

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.

Boot evo in text mode ....

I am running the latest build of CyanogenMod-6 (V6.0.0-RC1) with the snapv3 kernel, and my Evo is running at amazing speeds and performance has been way better than my other custom ROMS.
But I wish I was able to have a boot screen that shows the boot up process in text mode, like something that looks similar to booting into "Safe Mode" in windows or verbose mode under macs. Like what logcat live wallpaper does.
http://www.androlib.com/android.screenshot.app.nxDz-tBDD.u.aspx
If this could be done, that would be great to have on the Evo and would serve to lessen the boot time.
Thank you all for all the wonderful work. Cheers!

[Q]Porting CWM 6.0 to legacy LCDs

I'm in the middle of porting CWM 6.0.0.x to dell devices, and I've gotten all but one.
Background:
CWM 6.0 prefers displays of type:
24/32bpp color Edit: after fiddling around with it, this isnt actually true.
Right side up
Double buffered(?)
My last device I'm having trouble with (Dell Streak 5):
16bpp
Upside down
Single buffered(?)
I've re-added screen flipping (for point 2) and fixed the pixels for point 1, but I have no idea how to fix point 3.
My exact issue: I can get CWM 6.0 to boot with correct colors on my S5, but every other buffer(?) is blank.
So blank -> correct screen -> blank -> correct screen -> etc.
It's just a graphics issue as it still works fine while black.
CWM 5.5 preferred single buffers but had board config switches to enable RGBX_8888 and double buffering.
But the move to 6.0 broke RGB_565 and single buffering.
I have no idea where in the code to force it to single buffer, I've already fiddled around in <CWM>\minui\graphics.c and besides the color-space changes, there's nothing changed regarding single/double buffering in it.
Here's my device tree if it helps:
DellInc._Streak_120718.rar

Warning for kernel porters - apparent brick-like symptoms!

JUST AN INFORMATION if u ppl are building CM 10.1 kernel and facing same issue >
adfad666 (RD) said -
I have been modifying the Sony kernel sources, and porting our 4.1 kernel to a 4.2 CAF branch to be used with CyanogenMod 10.1 and above. We will eventually receive Android 4.3 direct from Sony, and therefore suitable kernel sources, but if we can beat them to it, why not?
However our Xperia SP has a very temperamental screen, it really needs a perfect frame buffer or it will crap out on you with no apparent way back.
If you flash a kernel with a broken frame buffer (a kernel that does not send the correct signals to the display), you will see nothing on the screen, sometimes random vertical lines, then your device will get into a low level bootloop, (ADB will not be available) and even if you flash a working kernel from a factory image this will not recover the device. Basically, the screen gets stuck in a non-functional state, the device is able to detect this and immediately hard resets, so your device seems hard bricked.
Well... almost.
Fortunately, Sony build into their factory images a special lock that, on first boot, nothing can cause the device to shut down or reboot. Therefore to break this hard brick, you need to do a full wipe with flashtool.
On reboot the screen will still be broken, but it will do a full boot (you will eventually hear touch sounds when pressing the screen). You can now hit the power button to switch off the display, hit it again and your screen should, finally, come back to life.
* * * * * * * * * *
Why does this happen? My guess is that a specific set of commands must be used to control the display. Any deviation from that set and the screen gets stuck in a non-functional state, and the only way to recover is to eventually send the correct off/on sequence to it.
However this can only happen from a working rom, but due to the auto detect of the broken screen and hard reset (forcing the hardware to switch off without sending an off command to the screen), this can only happen after a full wipe to recreate the first boot sequence.
Therefore if you are experimenting with the kernel you need to be aware of this... 'feature' and that luckily there is a way to recover from it.
I have needed to recover my device three times now with this method and I haven't even owned it for a week yet. I have never seen such behaviour on any of the other devices I have worked on, so this is going to make kernel porting a tricky and tedious affair. The fact that the screen 'remembers' your bad kernel even after you flash a good one is pretty disturbing. (I even left my Xperia SP powered off for over an hour to see if the lack of power would reset the screen, but no change)
official thread > http://forum.xda-developers.com/showthread.php?t=2457353
is this happen to our mobile also ? because both mobile are released at same period
Thanks

the are relased in simillar time,but both have different screens,sp have hd and we have FWVGA screen,we have also different lcd density,so i think this will be only on sp not on L.

Well, we've booted cm10.1 to homescreen. I had already adjusted frame buffer ( same as we do in recovery ) and it works fine.
A quick comparison between msm_fb.c ( video driver) in our stock kernel sources and MSM8930 CAF sources will tell you that sony team uses special CCI drivers to control the LCD... For eg brightness etc.
Without them, I doubt screen will work functionally.
Thankfully, the stock kernel booted cm10.1 without any major changes ( except frame buffers fix ) .

[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.