Rotation, camera, audio jack and wifi problem android x86 8.1

TAUSIF AMLANI

unread,

Jun 20, 2019, 1:00:55 PM6/20/19

to Android-x86

hello,

i am using android x86 8.1 R2 version and facing 5 problems other than that it is working perfectly, please help me resolve following issues

1)audio jack is not working.
2)auto rotation doesn't work.
3)camera app is not showing in app tray and when i use 3rd party app or double press power button the camera app starts but gives an error "can't connect to the camera"
4)wifi can't find any wifi connections after it come back from sleep mode.
5) when i press power button to lock device the backlight remain on.

other relevant information:
i have used phoenix os and android x86 6.0 the rotation works on both os but in reverse order (when in potrait it work as landscape and vise versa) which is most common issue. however those 2 os where not stable as much as android x86 8.1 is.

my system information:
its a 2in1 laptop with detachable keyboard

Lenovo MIXX 310 - 80sg
preinstall os: windows 10
processor: Intel(R) Atom(TM) x5-Z8350 CPU @ 1.44GHz (4 CPUs), ~1.4GHz
RAM: 2gb
System DPI Setting: 96 DPI (100 percent)

mic: Microphone (Intel SST Audio Device (WDM))
mic Driver Name: isstrtc.sys
Driver Version: 604.10135.2747.5232 (English)

i can share dxdiag information if required. please help me out. thanks in advance

Jon West

unread,

Jun 20, 2019, 10:14:44 PM6/20/19

to Android-x86

Your device likely works best on versions using Kernel 4.4. I would look into compiling on your own with that kernel version as a solution.

TAUSIF AMLANI

unread,

Jun 21, 2019, 12:38:15 AM6/21/19

to Android-x86

Could you suggest os which has kernel 4.4 so that i can try those and update you further...

Jon West

unread,

Jun 22, 2019, 10:16:19 AM6/22/19

to Android-x86

As of right now, there are no versions of Android-x86 currently in development that use that kernel version. Most of us have moved to making 64bit only builds using kernel 4.9 +

TAUSIF AMLANI

unread,

Jun 22, 2019, 11:15:09 AM6/22/19

to Android-x86

Thank you for helping. Can you please tell What about older version of android x86 5.1 and cm 13.1 does it use kernel 4.4 or any specific os which in your opinion use this version...as i am in need because i don't have windows back up drive and without that i cant revert to windows....

Chih-Wei Huang

unread,

Jun 25, 2019, 10:06:52 AM6/25/19

to Android-x86

For the rotation issue, try the method (by root):

setprop ro.iio.accel.quirks no-trig
stop; start

Please see more details in
https://groups.google.com/forum/#!msg/android-x86/UL08_7ooh6k/SbBz5vbzFQAJ

TAUSIF AMLANI <tausif...@gmail.com> 於 2019年6月22日週六下午11:15寫道：

>
> Thank you for helping. Can you please tell What about older version of android x86 5.1 and cm 13.1 does it use kernel 4.4 or any specific os which in your opinion use this version...as i am in need because i don't have windows back up drive and without that i cant revert to windows....

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

Chih-Wei Huang

unread,

Jun 25, 2019, 10:11:18 AM6/25/19

to Android-x86

Chih-Wei Huang <cwh...@android-x86.org> 於 2019年6月25日週二下午10:06寫道：

>
> For the rotation issue, try the method (by root):
>
> setprop ro.iio.accel.quirks no-trig
> stop; start
>
> Please see more details in
> https://groups.google.com/forum/#!msg/android-x86/UL08_7ooh6k/SbBz5vbzFQAJ

Sorry! Should be
https://groups.google.com/d/msg/android-x86/UL08_7ooh6k/E5imycUXFgAJ

Daniel Cheung

unread,

Jun 26, 2019, 12:48:50 AM6/26/19

to andro...@googlegroups.com

Any suggestions for those that have problem with iio with quirks no-trig and iio-old? My previous init.sh using iio-old and accel matrix no longer works in 8.1 R2. Also tried using iio and quirks no-trig but not successful.

Chih-Wei Huang

unread,

Jun 26, 2019, 1:05:52 AM6/26/19

to Android-x86

Daniel Cheung <dwt.c...@gmail.com> 於 2019年6月26日週三下午12:48寫道：

>
> Any suggestions for those that have problem with iio with quirks no-trig and iio-old? My previous init.sh using iio-old and accel matrix no longer works in 8.1 R2. Also tried using iio and quirks no-trig but not successful.

Did it work before?

There are several discussions in the forum before.
Search and read them.
If still not working, trace and debug the code.

Daniel Cheung

unread,

Jun 26, 2019, 1:14:50 AM6/26/19

to andro...@googlegroups.com

Yes, it worked before with 8.1 R1 which I reinstalled. I actually started a few of those threads regarding rotation issues with my device and you helped me resolved the issue. That's how I end up using iio-old and accel matrix to fix the problem. Even with the standard iso I downloaded, both iio and iio-old didn't do the trick. I'll boot in debug mode and take a look at the log and report back in a few days. Looks like I may need to use Kionix provided drivers and try compiling it.

Chih-Wei Huang

unread,

Jun 26, 2019, 10:14:11 PM6/26/19

to Android-x86

Daniel Cheung <dwt.c...@gmail.com> 於 2019年6月26日週三下午1:14寫道：

>
> Yes, it worked before with 8.1 R1 which I reinstalled. I actually started a few of those threads regarding rotation issues with my device and you helped me resolved the issue. That's how I end up using iio-old and accel matrix to fix the problem. Even with the standard iso I downloaded, both iio and iio-old didn't do the trick. I'll boot in debug mode and take a look at the log and report back in a few days. Looks like I may need to use Kionix provided drivers and try compiling it.

Firstly, you have to check whether if the sensors driver works.
Use the command (by root):

cat /sys/bus/iio/devices/iio:device*/in_accel_?_raw

Rotate the tablet and see if the values change.
Compare the values in 8.1-r1 and -r2 to see
if it works the same way.
If not, then the driver in 8.1-r2 is broken.
If yes, there is something wrong with the userspace
(i.e. the sensors HAL)
You need to trace it to see what happened.
However, it's unlikely since there is no change
of the sensors HAL between -r1 and -r2.

Daniel Cheung

unread,

Jun 26, 2019, 10:25:06 PM6/26/19

to andro...@googlegroups.com

Thanks for the suggestions, I'll run those tests during the weekend. In the meanwhile, I found out there was a patch in the kernel at added the following in the kxcjk-1013.c file:

{"KIOX010A", KXCJ91008}, /* KXCJ91008 inside the display of a 2-in-1 */

https://patchwork.kernel.org/patch/10690261/

Chih-Wei Huang

unread,

Jun 26, 2019, 10:57:36 PM6/26/19

to Android-x86

Daniel Cheung <dwt.c...@gmail.com> 於 2019年6月27日週四上午10:25寫道：

>
> Thanks for the suggestions, I'll run those tests during the weekend. In the meanwhile, I found out there was a patch in the kernel at added the following in the kxcjk-1013.c file:
>
> {"KIOX010A", KXCJ91008}, /* KXCJ91008 inside the display of a 2-in-1 */
>
> https://patchwork.kernel.org/patch/10690261/

After checking, the patch is in 8.1-r2 but not in 8.1-r1.

How is it related to your problem?

Daniel Cheung

unread,

Jun 26, 2019, 11:05:50 PM6/26/19

to andro...@googlegroups.com

I suspect the kernel change is affecting my tablet as the accel unit in my tablet is a KXCJ9. I can't prove this change is causing the problem until I run the test as suggested this weekend.

Daniel Cheung

unread,

Jun 29, 2019, 7:29:19 PM6/29/19

to andro...@googlegroups.com

OK here is an update on the rotation issue.

1. The changes to the kernel where KIOX010A is added to kxcjk-1013.c file has nothing to do with my problem. My device is detected as KIOX000A.

2. I'm getting values from accel_*_raw regardless of iio or iio-old being used in 8.1R1 and 8.1R2.

3. Using iio in 8.1R1 and 8.1R2 will detect the accel hardware as KIOX000A but will not rotate at all, this is the same back in 7.x. Log showing the following for both 8.1R1 and 8.1R2 using iio:

Sensors : Initializing IIO sensors HAL module
Sensors : Cannot read string from /sys/bus/iio/devices/iio:device0/in_accel_offset (No such file or directory)
Sensors : Cannot read number from /sys/bus/iio/devices/iio:device0/in_accel_offset (No such file or directory)
Sensors : Cannot read string from /sys/bus/iio/devices/iio:device0/sampling_frequency_available (No such file or directory)
Sensors : Cannot read string from /sys/bus/iio/devices/iio:device0/mounting_matrix (No such file or directory)
Sensors : Cannot read string from /sys/bus/iio/devices/iio:device0/../firmware_node/pld/panel (No such file or directory)
Sensors : Cannot read number from /sys/bus/iio/devices/iio:device0/../firmware_node/pld/panel (No such file or directory)
Sensors : Found 3 channels on iio device 0
Sensors : S0 C0 : offset 0, size 2, type le:s12/16>>4
Sensors : S0 C1 : offset 2, size 2, type le:s12/16>>4
Sensors : S0 C2 : offset 4, size 2, type le:s12/16>>4
Sensors : Detected timestamp channel on iio device 0
Sensors : Expecting 16 scan length on iio dev 0
Sensors : Discovered 1 sensors
Sensors : Cannot read string from /sys/bus/iio/devices/trigger0/name (No such file or directory)
Sensors : Sensor 0 (S0-i2c-KIOX000A:00) default trigger: i2c-KIOX000A:00-dev0
Sensors : Discovered 1 sensors
Sensors : S0: S0-i2c-KIOX000A:00

Sensors : Sensor 0 (S0-i2c-KIOX000A:00) sampling rate set to 14.9999
Sensors : Cannot write to /sys/bus/iio/devices/iio:device0/in_accel_sampling_frequency (Invalid argument)
Sensors : Enabling sensor 0 (iio device 0: S0-i2c-KIOX000A:00)
Sensors : Setting S0 (S0-i2c-KIOX000A:00) trigger to i2c-KIOX000A:00-dev0
Sensors : Cannot write to /sys/bus/iio/devices/iio:device0/buffer/enable (Invalid argument)
Sensors : Failed enabling buffer on dev0, retrying
CarrierConfigManager: Error getting config for subId -1 ICarrierConfigLoader is null
CarrierConfigManager: Error getting config for subId -1 ICarrierConfigLoader is null
TelephonyRegistry: listen oscl: hasNotifySubscriptionInfoChangedOccurred==false no callback
Sensors : Cannot write to /sys/bus/iio/devices/iio:device0/buffer/enable (Invalid argument)
Sensors : Failed enabling buffer on dev0, retrying
Sensors : Cannot write to /sys/bus/iio/devices/iio:device0/buffer/enable (Invalid argument)
Sensors : Failed enabling buffer on dev0, retrying
Sensors : Could not enable buffer
Sensors : Activation of sensor S0-i2c-KIOX000A:00 took 1 ms

I'm not sure if it's trying to read and write to the wrong location because the file it's looking for are actually under device1 not device0.

4. iio-old in 8.1R2 seem to be broken.

Here's the log snip from 8.1R1 using iio-old:

vndksupport: Loading /vendor/lib64/hw/sensors.iio-old.so from current namespace instead of sphal namespace.
iio-sensors: open_iio_sensors: id=poll
iio-sensors: found node /sys/bus/iio/devices/iio:device0: in_accel_scale
iio-sensors: found IIO Accelerometer Sensor
iio-sensors: SensorPollContext: module=0x7e631e92d0f8 sensors: 1
iio-sensors: enter sensors_get_sensors_list
iio-sensors: poll_activate: dev=0x7e632ea8cc00 handle=0 enabled=0

healthd : battery l=55 v=3572 t=0.0 h=2 st=3 c=-2048 fc=8198736 chg=

Here's the log snip from 8.1R2 using iio-old:

vndksupport: Loading /vendor/lib64/hw/sensors.iio-old.so from current namespace instead of sphal namespace.
healthd : battery l=38 v=3555 t=0.0 h=2 st=3 c=-1744 fc=8198736 chg=

It's loading iio-old.so but in 8.1R2, it didn't detect the accelerometer.

Chih-Wei Huang

unread,

Jun 30, 2019, 8:06:15 PM6/30/19

to Android-x86

Please show the result of

ls -lR /sys/bus/iio/devices/iio:device?/

from 8.1-r1 and -r2.

Daniel Cheung <dwt.c...@gmail.com> 於 2019年6月30日週日上午7:29寫道：

Daniel Cheung

unread,

Jun 30, 2019, 9:29:22 PM6/30/19

to andro...@googlegroups.com

The output of ls -lR /sys/bus/iio/devices/iio:device?/ as follow:

8.1R1

/sys/bus/iio/devices/iio:device0/:
total 0
-r--r--r-- 1 system system 4096 2019-06-30 18:16 dev
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_current3_raw
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_current4_raw
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_temp0_raw
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_temp1_raw
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_temp2_raw
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_voltage5_raw
-r--r--r-- 1 system system 4096 2019-06-30 18:16 name
drwxr-xr-x 2 system system 0 2019-06-30 18:16 power
lrwxrwxrwx 1 root root 0 2019-06-30 18:16 subsystem -> ../../../../../../../bus/iio
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 uevent

/sys/bus/iio/devices/iio:device0/power:
total 0
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 autosuspend_delay_ms
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 control
-r--r--r-- 1 system system 4096 2019-06-30 18:16 runtime_active_time
-r--r--r-- 1 system system 4096 2019-06-30 18:16 runtime_status
-r--r--r-- 1 system system 4096 2019-06-30 18:16 runtime_suspended_time

/sys/bus/iio/devices/iio:device1/:
total 0
drwxr-xr-x 2 system system 0 2019-06-30 18:16 buffer
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 current_timestamp_clock
-r--r--r-- 1 system system 4096 2019-06-30 18:16 dev
drwxr-xr-x 2 system system 0 2019-06-30 18:16 events
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_sampling_frequency
-r--r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_sampling_frequency_available
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_scale
-r--r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_scale_available
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_x_raw
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_y_raw
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_z_raw
-r--r--r-- 1 system system 4096 2019-06-30 18:16 name
drwxr-xr-x 2 system system 0 2019-06-30 18:16 power
drwxr-xr-x 2 system system 0 2019-06-30 18:16 scan_elements
lrwxrwxrwx 1 root root 0 2019-06-30 18:16 subsystem -> ../../../../../../bus/iio
drwxr-xr-x 2 system system 0 2019-06-30 18:16 trigger
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 uevent

/sys/bus/iio/devices/iio:device1/buffer:
total 0
-r--r--r-- 1 system system 4096 2019-06-30 18:16 data_available
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 enable
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 length
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 watermark

/sys/bus/iio/devices/iio:device1/events:
total 0
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_x_thresh_either_en
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_x_thresh_either_period
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_x_thresh_either_value
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_y_thresh_either_en
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_y_thresh_either_period
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_y_thresh_either_value
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_z_thresh_either_en
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_z_thresh_either_period
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_z_thresh_either_value

/sys/bus/iio/devices/iio:device1/power:
total 0
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 autosuspend_delay_ms
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 control
-r--r--r-- 1 system system 4096 2019-06-30 18:16 runtime_active_time
-r--r--r-- 1 system system 4096 2019-06-30 18:16 runtime_status
-r--r--r-- 1 system system 4096 2019-06-30 18:16 runtime_suspended_time

/sys/bus/iio/devices/iio:device1/scan_elements:
total 0
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_x_en
-r--r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_x_index
-r--r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_x_type
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_y_en
-r--r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_y_index
-r--r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_y_type
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_z_en
-r--r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_z_index
-r--r--r-- 1 system system 4096 2019-06-30 18:16 in_accel_z_type
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 in_timestamp_en
-r--r--r-- 1 system system 4096 2019-06-30 18:16 in_timestamp_index
-r--r--r-- 1 system system 4096 2019-06-30 18:16 in_timestamp_type

/sys/bus/iio/devices/iio:device1/trigger:
total 0
-rw-r--r-- 1 system system 4096 2019-06-30 18:16 current_trigger

8.1R2

/sys/bus/iio/devices/iio:device0/:
total 0
-r--r--r-- 1 system system 4096 2019-06-30 17:50 dev
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_current3_raw
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_current4_raw
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_temp0_raw
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_temp1_raw
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_temp2_raw
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_voltage5_raw
-r--r--r-- 1 system system 4096 2019-06-30 17:50 name
drwxr-xr-x 2 system system 0 2019-06-30 17:50 power
lrwxrwxrwx 1 root root 0 2019-06-30 17:50 subsystem -> ../../../../../../../bus/iio
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 uevent

/sys/bus/iio/devices/iio:device0/power:
total 0
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 autosuspend_delay_ms
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 control
-r--r--r-- 1 system system 4096 2019-06-30 17:50 runtime_active_time
-r--r--r-- 1 system system 4096 2019-06-30 17:50 runtime_status
-r--r--r-- 1 system system 4096 2019-06-30 17:50 runtime_suspended_time

/sys/bus/iio/devices/iio:device1/:
total 0
drwxr-xr-x 2 system system 0 2019-06-30 17:50 buffer
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 current_timestamp_clock
-r--r--r-- 1 system system 4096 2019-06-30 17:50 dev
drwxr-xr-x 2 system system 0 2019-06-30 17:50 events
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_sampling_frequency
-r--r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_sampling_frequency_available
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_scale
-r--r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_scale_available
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_x_raw
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_y_raw
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_z_raw
-r--r--r-- 1 system system 4096 2019-06-30 17:50 name
drwxr-xr-x 2 system system 0 2019-06-30 17:50 power
drwxr-xr-x 2 system system 0 2019-06-30 17:50 scan_elements
lrwxrwxrwx 1 root root 0 2019-06-30 17:50 subsystem -> ../../../../../../bus/iio
drwxr-xr-x 2 system system 0 2019-06-30 17:50 trigger
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 uevent

/sys/bus/iio/devices/iio:device1/buffer:
total 0
-r--r--r-- 1 system system 4096 2019-06-30 17:50 data_available
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 enable
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 length
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 watermark

/sys/bus/iio/devices/iio:device1/events:
total 0
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_x_thresh_either_en
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_x_thresh_either_period
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_x_thresh_either_value
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_y_thresh_either_en
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_y_thresh_either_period
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_y_thresh_either_value
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_z_thresh_either_en
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_z_thresh_either_period
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_z_thresh_either_value

/sys/bus/iio/devices/iio:device1/power:
total 0
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 autosuspend_delay_ms
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 control
-r--r--r-- 1 system system 4096 2019-06-30 17:50 runtime_active_time
-r--r--r-- 1 system system 4096 2019-06-30 17:50 runtime_status
-r--r--r-- 1 system system 4096 2019-06-30 17:50 runtime_suspended_time

/sys/bus/iio/devices/iio:device1/scan_elements:
total 0
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_x_en
-r--r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_x_index
-r--r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_x_type
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_y_en
-r--r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_y_index
-r--r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_y_type
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_z_en
-r--r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_z_index
-r--r--r-- 1 system system 4096 2019-06-30 17:50 in_accel_z_type
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 in_timestamp_en
-r--r--r-- 1 system system 4096 2019-06-30 17:50 in_timestamp_index
-r--r--r-- 1 system system 4096 2019-06-30 17:50 in_timestamp_type

/sys/bus/iio/devices/iio:device1/trigger:
total 0
-rw-r--r-- 1 system system 4096 2019-06-30 17:50 current_trigger

As first glance, there are no difference between 8.1R1 and 8.1R2.

Chih-Wei Huang

unread,

Jun 30, 2019, 10:22:25 PM6/30/19

to Android-x86

Daniel Cheung <dwt.c...@gmail.com> 於 2019年7月1日週一上午9:29寫道：

>
> As first glance, there are no difference between 8.1R1 and 8.1R2.

Right. I've compared them by diff, no difference.
You may need to dig further to find what happened.
If you can build the sensors HAL yourself, try to add
more debug messages.

It seems iio:device1 is the correct acceleration (rotation) sensors.
Although it may be changed every time it boots.

Another way you can try is to replace the kernel and /system/lib/modules
in 8.1-r2 with 8.1-r1. (suppose kernel & drivers of -r1 work).

Daniel Cheung

unread,

Jul 1, 2019, 1:50:10 AM7/1/19

to andro...@googlegroups.com

I prefer not to replace the kernel with R1 because R2 boots a lot faster and haven't giving me boot hang. I'm trying to compile the factory drivers but it doesn't seem to be successful as the build log doesn't show the relevant o file being included. Also, the debug log didn't detect any devices.

Chih-Wei Huang

unread,

Jul 1, 2019, 4:47:40 AM7/1/19

to Android-x86

Daniel Cheung <dwt.c...@gmail.com> 於 2019年7月1日週一下午1:50寫道：

>
> I prefer not to replace the kernel with R1 because R2 boots a lot faster and haven't giving me boot hang. I'm trying to compile the factory drivers but it doesn't seem to be successful as the build log doesn't show the relevant o file being included. Also, the debug log didn't detect any devices.

By replacing the kernel, at least you can confirm
whether if it's a kernel driver issue from -r1 to -r2.

Daniel Cheung

unread,

Jul 1, 2019, 7:01:36 PM7/1/19

to andro...@googlegroups.com

Before I try copying the kernels and modules from the 8.1R1 USB drive, wouldn't install with upgrade do the same thing? If so, I already try that method as I always use upgrade option to save my apps to avoid reinstalling them.

Daniel Cheung

unread,

Jul 1, 2019, 8:26:29 PM7/1/19

to andro...@googlegroups.com

It seems like my problem is resolved. I went back and rebuild the ISO using a new kernel configuration. Here are the things I done to make it work:

1. Under Industrial I/O Support main menu, I selected all the options except ChromeOS ES Sensors Core.

2. Removed all unnesscary options under Industrial I/O Support that doesn't relate to the KIONIX sensor.

3. IIO Rescale checked.

4. High resolution timer trigger checked.

5. Generic interrupt trigger checked.

6. SYSFS trigger checked but leave kthread trigger unchecked.

7. Intel MID GPIO checked.

After upgrading the install with the install ISO, I found the following:

1. In sys/bus/iio/device directory, there is only one device in there instead of two. All the iio files and directory are listed under device0.

2. Still will not rotate so I added quirks no trig option as suggested earlier, reboot and see the screen rotates but orientation is off.

3. Added order 102 to get the orientation correctly.

Chih-Wei Huang

unread,

Jul 2, 2019, 12:15:26 AM7/2/19

to Android-x86

Daniel Cheung <dwt.c...@gmail.com> 於 2019年7月2日週二上午8:26寫道：

>
> It seems like my problem is resolved. I went back and rebuild the ISO using a new kernel configuration. Here are the things I done to make it work:
>
> 1. Under Industrial I/O Support main menu, I selected all the options except ChromeOS ES Sensors Core.
> 2. Removed all unnesscary options under Industrial I/O Support that doesn't relate to the KIONIX sensor.
> 3. IIO Rescale checked.
> 4. High resolution timer trigger checked.
> 5. Generic interrupt trigger checked.
> 6. SYSFS trigger checked but leave kthread trigger unchecked.
> 7. Intel MID GPIO checked.

Please try to minimize your change and provide a patch (diff)
to the current kernel config.

> After upgrading the install with the install ISO, I found the following:
> 1. In sys/bus/iio/device directory, there is only one device in there instead of two. All the iio files and directory are listed under device0.

That's probably because you removed drivers of other sensors.

> 2. Still will not rotate so I added quirks no trig option as suggested earlier, reboot and see the screen rotates but orientation is off.
> 3. Added order 102 to get the orientation correctly.

Nice. Please provide a patch.
(see /etc/init.sh for how to add quirks of your device)

BrokenE39

unread,

Jul 2, 2019, 12:47:08 AM7/2/19

to Android-x86

I just noticed my changes made the battery icon to show as charging even without being plugged in to a charger. So I went back to testing an older ISO image without all these kernel configuration changes. All I added to init.sh are iio, no-trig, and order 102 and rotation worked and the battery icon is displaying correctly. I probably made a mistake a few days back when I first tried adding no-trig. I'll make another ISO without these changes and re-test. I'll not provide a patch at the moment because it looked like it did more harm than good.

Chih-Wei Huang

unread,

Jul 2, 2019, 12:55:34 AM7/2/19

to Android-x86

BrokenE39 <dwt.c...@gmail.com> 於 2019年7月2日週二下午12:47寫道：

>
> I just noticed my changes made the battery icon to show as charging even without being plugged in to a charger. So I went back to testing an older ISO image without all these kernel configuration changes. All I added to init.sh are iio, no-trig, and order 102 and rotation worked and the battery icon is displaying correctly. I probably made a mistake a few days back when I first tried adding no-trig. I'll make another ISO without these changes and re-test. I'll not provide a patch at the moment because it looked like it did more harm than good.

It won't if you add it based on your device dmi correctly.
Please see /etc/init.sh how to do it.

Daniel Cheung

unread,

Jul 2, 2019, 2:25:49 AM7/2/19

to andro...@googlegroups.com

I ran cat $DMIPATH/uevent but it return sh: cst: not found. Running cat /sys/class/dmi/id/uevent return a long string that doesn't contain anything that would identify the device model. Further look into board_name, product_family, product_name, product_serial, and chassis_vendor all came up as Default String. Looks like it's not possible to provide a patch since it's not possible to identify the device by make and model.

Reply all

Reply to author

Forward