• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Mouse cursor beeing replaced with bootloader logo on Amlogic based ROMs

Status
Not open for further replies.
Hi,

I had this situation and for long time I couldn't reproduce the problem... but eventually I did :)

Ok, if you have set_display_mode.sh script inside /system/bin folder which is not clearing fb1 (frame buffer 1) and your users are using freescale function available trough display settings, you will eventually get mouse pointer replaced with bootloader logo image :)

At the end of script should be something like this:

Code:
...
echo 1 > /sys/class/graphics/fb1/blank
fbset -fb /dev/graphics/fb1 -g 18 18 18 18 $osd_bits
echo 1 > /sys/class/graphics/fb1/blank
 
Would you be kind enough to further explain what is going on/...

I'm in a position where I can't get the original Rom..
and I don't know if it is possible to connect my device to my PC
Thanks

In early ICS amlogic sources bug persists which replaces aml_logo partition content and copies it to osd2 layer which is used to display mouse pointer. It is amlogic bug (they do have their own implementation of showing mouse pointer that persists on top of main framebuffer).

I didn't investigate further how to fix the issue. Might be good to know default and current environment variables. You can get that only on rooted device connected via adb or direct ttl connection to device.
 
Upvote 0
So..is this a choke position?!!
if I don't have the original ROM I get to stay with that freaken mouse pointer...
c'mon there must be something I can do to fix this without flashing.
a little extra help please?..

Which device do you have? Can you go to recovery clean cache partition? Can you connect to your device via tll?
 
Upvote 0
Well..... as I can find nobody to work me through this problem
I started trubleshooting on my own
I think I did not get this problem untill I rooted the device using this file...
CWM-SuperSU-v0.96AML - Download - 4shared - Chad Kitching
If you can shed any light on this, your help is very much appreciated..

I still don't have solution for this, but have you also updated busybox? That's one of things that causes this...
 
Upvote 0
I shouldn't have updated busybox..
the problem is the fbset command I guess...
I think the original ROM contained a version of busybox that had fbset in it..
while the updated busybox doesn't..
I think the rom uses that command to "set_display_mode"..

what do you think about this stane?!

Edit:
got a busybox binary with fbset..
from THIS post by Stericson [BusyBox installer author]
installed it..
but now when I run fbset from terminal I get :
Code:
fbset: can't open '/dev/fb0': No such file or directory

edit2:is this related?!
 
Upvote 0
I shouldn't have updated busybox..
the problem is the fbset command I guess...
I think the original ROM contained a version of busybox that had fbset in it..
while the updated busybox doesn't..
I think the rom uses that command to "set_display_mode"..

what do you think about this stane?!

Edit:
got a busybox binary with fbset..
from THIS post by Stericson [BusyBox installer author]
installed it..
but now when I run fbset from terminal I get :
Code:
fbset: can't open '/dev/fb0': No such file or directory
edit2:is this related?!

Android does not use /dev/fb0 but /dev/graphics/fb0. You sure you have right busybox?
 
Upvote 0
Android does not use /dev/fb0 but /dev/graphics/fb0. You sure you have right busybox?

So you think I should do what..??
Ask Stericson to compile another busybox...
as I said.. he made this one with fbset included(obviously for android)

is there a way to use the fbset command and point to the correct path??

or is this a mistake he made, ie..I need to find another busybox binary..??
 
Upvote 0
So you think I should do what..??
Ask Stericson to compile another busybox...
as I said.. he made this one with fbset included(obviously for android)

is there a way to use the fbset command and point to the correct path??

or is this a mistake he made, ie..I need to find another busybox binary..??

My first try would be to find any stock amlogic firmware which is for your platform and your android version (doesn't have to be for your device) and install it as you did it with busybox you mentioned. If it was in some kind of update.zip, replace it in there and resign update package. Busybox is static executable so replacing it would not cause any problems, just be careful to create correct symlinks :)
 
Upvote 0
Status
Not open for further replies.

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones