Acer SP111-33

326 views
Skip to first unread message

Ralph deGennaro

unread,
Oct 13, 2019, 7:28:26 PM10/13/19
to Android-x86
Hi,

I had a gift card to Staples and they had the Acer Spin 1 (SP111-33) for $200.  It had Windows 10 on it, and I replaced it with Android-X86 8.1-r2.  Awesome that it installed to built-in mmcblk device.  I read that some other Linux distros had troubles.  For the most part it works great.  And performance is incredible, it feels extremely "snappy" compared to Windows 10.

But swapping back and forth between laptop and tablet does not seem to be as seasoned as everything else.  Which I guess is as expected since the Distro seems to focus on the desktop metaphor and not the touch metaphor.  

Anyways, I noticed the following:
  • No screen auto-rotation
  • Keyboard stays on
  • Mouse stays on
  • Touch gets confused and stops.
The auto-rotation is solved by an app (swipe and tap).  For the mouse, there is the F7 button.  I can't figure out anything for the keyboard.  The touch sometimes gets confused when flipping the keyboard around, messing with the mouse, toggling the virtual keyboard setting and at other random times.  I don't mind too much, but some apps don't let me click-drag with the mouse.  A reboot brings the touch back.  

I also don't have huge amounts of time, but I can send debug/log information if it helps the greater good.  I understand if its not useful without a developer who wants to take it on.

Thanks,
Rio

Daniel Cheung

unread,
Oct 13, 2019, 9:46:30 PM10/13/19
to andro...@googlegroups.com
You can try going into init.sh and scroll down to init_hal_sensors function and after the last "fi" statement insert the following:

has_sensors=true
hal_sensors=iio
set_property ro.iio.accel.quirks no-trig

From what I understand, the init.sh script looks for the substring of the DMIPATH and try to match it then set the HAL sensor type. I had similar issue with my Teclast device as it just returns "Default String" when accessing the DMIPATH. As for the KB and Mouse, I think that's the default behavior when the system detects them. I don't think a lot of OS understands the switch between tablet mode and desktop mode via flipping the 2-in-1 screen around. I have a tablet and touch works fine. So boot into debug mode and start using the device and post some logs for the devs.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/499ed054-4a35-4021-aa1b-786cb6fb87ca%40googlegroups.com.

Ralph deGennaro

unread,
Oct 14, 2019, 12:14:00 PM10/14/19
to andro...@googlegroups.com
Excellent, thank you Daniel!  I can confirm adding the following to /system/etc/init.sh works:

has_sensors=true
hal_sensors=iio
set_property ro.iio.accel.quirks no-trig
set_property ro.iio.accel.order 102

Your guidance pointed me in the right direction to get the 4th line.  

I also saw that people posted the result of
  • cat /sys/class/dmi/id/product_name
  • cat /sys/class/dmi/id/board_name
  • cat /sys/class/dmi/id/uevent
Which are:
  • Spin SP111-33
  • Hamm_GL
  • MODALIAS=dmi:bvnInsydeCorp.:bvrV1.07:bd03/19/2019:svnAcer:pnSpinSP111-33:prvV1.07:rvnGLK:rnHamm_GL:rvrV1.07:cvnAcer:ct31:cvrChassisVersion:
Strange that there is no value after Chassis.

I will look into debug mode, maybe Wednesday or next weekend.

Thanks!

-Rio


You received this message because you are subscribed to a topic in the Google Groups "Android-x86" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-x86/MW0rE7Gkpqw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/CAFgJqCdi6vYmGAiyUbxQ2RwAzrcN4KTn-BNmY2tMeHsgZsaBQw%40mail.gmail.com.

Ralph deGennaro

unread,
Oct 14, 2019, 12:27:58 PM10/14/19
to andro...@googlegroups.com
Ha!  I should have checked the keyboard/mouse functionality.  I should have realized it may have changed.  But now the keyboard & mouse get turned off when I "spin".  It does not when I "spin" it back.  Anyways, debug mode when as soon as I can....

Chih-Wei Huang

unread,
Oct 15, 2019, 5:51:10 AM10/15/19
to Android-x86
Ralph deGennaro <rmdeg...@gmail.com> 於 2019年10月15日 週二 上午12:13寫道:
>
> Excellent, thank you Daniel! I can confirm adding the following to /system/etc/init.sh works:
>
> has_sensors=true
>
> hal_sensors=iio
>
> set_property ro.iio.accel.quirks no-trig
>
> set_property ro.iio.accel.order 102
>
>
> Your guidance pointed me in the right direction to get the 4th line.
>
> I also saw that people posted the result of
>
> cat /sys/class/dmi/id/product_name
> cat /sys/class/dmi/id/board_name
> cat /sys/class/dmi/id/uevent
>
> Which are:
>
> Spin SP111-33
> Hamm_GL
> MODALIAS=dmi:bvnInsydeCorp.:bvrV1.07:bd03/19/2019:svnAcer:pnSpinSP111-33:prvV1.07:rvnGLK:rnHamm_GL:rvrV1.07:cvnAcer:ct31:cvrChassisVersion:

I'll add your device to init.sh.
Thank you!


> Strange that there is no value after Chassis.
>
> I will look into debug mode, maybe Wednesday or next weekend.


--
Chih-Wei
Android-x86 project
http://www.android-x86.org
Reply all
Reply to author
Forward
0 new messages