Mouse cursor beeing replaced with bootloader logo on Amlogic based ROMs

[stane1983]

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:

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

 

[grindinonyourm]

im so glad you found it! i was starting to feel a little like a crazy person.

 

[hosamn]

Sorry to bring this up again
but it IS driving me mad..

I don't see how I can fix the issue with the info from your post stane..

the end of my set_display_mode.sh looks like this:

echo 1 > /sys/class/graphics/fb1/blank
fbset -fb /dev/graphics/fb1 -g 48 48 48 48 $osd_bits
echo 1 > /sys/class/graphics/fb1/blank

 

[hosamn]

changed 48 > 18
no difference..

 

[stane1983]

changed 48 > 18
no difference..

Hi,

You should apply change before error occures if I remember correctly. Reinstalling ROM will fix mouse pointer issue, then apply change mentioned here to script file.

Regards

 

[hosamn]

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

 

[stane1983]

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.

 

[hosamn]

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

 

[stane1983]

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?

 

[hosamn]

I have the Amlogic MBX f16ref
I did clean the Cache partition...nothing different..
tll??....... I do not know what that is...you lost me there....
but if it is relevant I could not connect the device to my PC...
thanks for your time..

 

[hosamn]

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

 

[stane1983]

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

 

[hosamn]

Well..
I HAVE updated busybox..
and I think that is the reason
do you have any Idea how to roll back to the old BUSYBOX?!!
thanks..!

 

[hosamn]

And how is the busybox problem exactly connected to the set_display_mode.sh script file...???

 

[__Rob__]

I had same here with HD16T DVBT (f16ref ?). And lovely busybox After few hours of searching I loaded firmware from G-Box and everything works fine except dvb function. Any suggetion ? I have dumped original firmware (but with f...ed up cursor) if needed.

 

[hosamn]

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 :

fbset: can't open '/dev/fb0': No such file or directory

edit2:is this related?!

 

[stane1983]

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 :

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?

 

[hosamn]

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

 

[stane1983]

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

 

[__Rob__]

Or try to install earlier version of busybox, the cursor will back. I made that too because of problem with DVBplayer on g-box firmware.

 

[hosamn]

Or try to install earlier version of busybox, the cursor will back. I made that too because of problem with DVBplayer on g-box firmware.

How old ..?!

 

[hosamn]

Or try to install earlier version of busybox, the cursor will back. I made that too because of problem with DVBplayer on g-box firmware.

How old exactly..?!

 

[__Rob__]

I installed BusyBox v6.8.

 

[ardennext99]

Ola, I've got the same problem and i'm going crasy to fix it. please can you send me a busybox 6.8 version, because I cannot found? I'v tryed with a 5.5 but not work. thanks a lot. ardennext99@gmail.com

P.S. please zip it because gmail block suspected attachment.

 

[ardennext99]

I had same here with HD16T DVBT (f16ref ?). And lovely busybox After few hours of searching I loaded firmware from G-Box and everything works fine except dvb function. Any suggetion ? I have dumped original firmware (but with f...ed up cursor) if needed.

I need it please. i'm one minute to a brick, and i've no idea how to save my device.

Thanks