3 issues in the latest 9.0 r1
1,759 views
Skip to first unread message
XiaoTao Liu
Feb 28, 2020, 7:35:31 PM2/28/20
to Android-x86
Quite exited to see the newly released stable version. I found 3 issues when test it on my teclast x98 air 3G . The first 2 issues work fine in 9.0 rc2.
1. native bridge can't be enable in settings. Every time I turned it on and exit, it will be automatically turn off the next time I enter into the settings.
2. I understand that the command of enable_nativebridge should be excuted as superuser in order to run arm app. When I run the command in 9.0r1 terminal, it just show no such file and won't connect online to download the required file. I tried to mannually download houdini.sfs and copy it to /syste/etc/ and /system/lib/arm/, and it still doesn't work.
3. bluetooth can't detect any device
Chih-Wei Huang
Feb 29, 2020, 10:44:19 PM2/29/20
to Android-x86
XiaoTao Liu <kevin....@gmail.com> 於 2020年2月29日 週六 上午8:35寫道：
the native bridge libraries.
Since 9.0-r1 the downloading will be carried out by
DownloadManager.
You can check the notification from the systemui
to see if the downloading is ongoing or complete.
Once it's completed, the native bridge function
will be enabled.
> 2. I understand that the command of enable_nativebridge should be excuted as superuser in order to run arm app. When I run the command in 9.0r1 terminal, it just show no such file and won't connect online to download the required file. I tried to mannually download houdini.sfs and copy it to /syste/etc/ and /system/lib/arm/, and it still doesn't work.
Don't run the script manually.
> 3. bluetooth can't detect any device
Then provide the debug messages.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
>
> Quite exited to see the newly released stable version. I found 3 issues when test it on my teclast x98 air 3G . The first 2 issues work fine in 9.0 rc2.
>
> 1. native bridge can't be enable in settings. Every time I turned it on and exit, it will be automatically turn off the next time I enter into the settings.
You must have a working network to download
> Quite exited to see the newly released stable version. I found 3 issues when test it on my teclast x98 air 3G . The first 2 issues work fine in 9.0 rc2.
>
> 1. native bridge can't be enable in settings. Every time I turned it on and exit, it will be automatically turn off the next time I enter into the settings.
the native bridge libraries.
Since 9.0-r1 the downloading will be carried out by
DownloadManager.
You can check the notification from the systemui
to see if the downloading is ongoing or complete.
Once it's completed, the native bridge function
will be enabled.
> 2. I understand that the command of enable_nativebridge should be excuted as superuser in order to run arm app. When I run the command in 9.0r1 terminal, it just show no such file and won't connect online to download the required file. I tried to mannually download houdini.sfs and copy it to /syste/etc/ and /system/lib/arm/, and it still doesn't work.
> 3. bluetooth can't detect any device
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
XiaoTao Liu
Mar 1, 2020, 12:46:20 AM3/1/20
to Android-x86
Thanks Chih-Wei.
For issue 1, I guess I figured out why the download manager didn't start, because I am behind the Great China firewall. Even I get connected to wifi, as Google.com is banned in China, the system think that I have no internet. I tried use some vpn app, and the downloading of native bridge 9_y starts. However the vpn is not stable, I still can't download the file successfully. So is there any mannual way to install the file, as I have alreay download this file from some chinese website.
For issue 3, could provide more information about how to provide debug information? I can boot into debug in boot menu. But what next?
On Sunday, March 1, 2020 at 11:44:19 AM UTC+8, Chih-Wei Huang wrote:
On Sunday, March 1, 2020 at 11:44:19 AM UTC+8, Chih-Wei Huang wrote:
XiaoTao Liu <kevin...@gmail.com> 於 2020年2月29日 週六 上午8:35寫道：
Message has been deleted
XiaoTao Liu
Mar 2, 2020, 8:30:52 AM3/2/20
to Android-x86
Does this help， i don't know how to get log file.
On Sunday, March 1, 2020 at 11:44:19 AM UTC+8, Chih-Wei Huang wrote:
XiaoTao Liu <kevin...@gmail.com> 於 2020年2月29日 週六 上午8:35寫道：
Chih-Wei Huang
Mar 2, 2020, 7:05:22 PM3/2/20
to Android-x86
XiaoTao Liu <kevin....@gmail.com> 於 2020年3月1日 週日 下午1:46寫道：
mkdir /sdcard/arm
cp houdini9_y.sfs /sdcard/arm
setprop persist.sys.nativebridge 1
Then check if /system/lib/arm contains the libraries.
> For issue 3, could provide more information about how to provide debug information? I can boot into debug in boot menu. But what next?
This has been explained many times. Please search the forum.
>
> Thanks Chih-Wei.
> For issue 1, I guess I figured out why the download manager didn't start, because I am behind the Great China firewall. Even I get connected to wifi, as Google.com is banned in China, the system think that I have no internet. I tried use some vpn app, and the downloading of native bridge 9_y starts. However the vpn is not stable, I still can't download the file successfully. So is there any mannual way to install the file, as I have alreay download this file from some chinese website.
You can do this by root:
> Thanks Chih-Wei.
> For issue 1, I guess I figured out why the download manager didn't start, because I am behind the Great China firewall. Even I get connected to wifi, as Google.com is banned in China, the system think that I have no internet. I tried use some vpn app, and the downloading of native bridge 9_y starts. However the vpn is not stable, I still can't download the file successfully. So is there any mannual way to install the file, as I have alreay download this file from some chinese website.
mkdir /sdcard/arm
cp houdini9_y.sfs /sdcard/arm
setprop persist.sys.nativebridge 1
Then check if /system/lib/arm contains the libraries.
> For issue 3, could provide more information about how to provide debug information? I can boot into debug in boot menu. But what next?
kevin.Liu
Mar 2, 2020, 7:53:36 PM3/2/20
to android-x86
thanks for the guide. I have attached a photo of debug info in previous email. Could you take a look
------------------ Original ------------------
From: Chih-Wei Huang <cwh...@android-x86.org>
Date: Tue,Mar 3,2020 8:04 AM
To: Android-x86 <andro...@googlegroups.com>
Subject: Re: 3 issues in the latest 9.0 r1
XiaoTao Liu <kevin....@gmail.com> 於 2020年3月1日 週日 下午1:46寫道： > > Thanks Chih-Wei. > For issue 1, I guess I figured out why the download manager didn't start, because I am behind the Great China firewall. Even I get connected to wifi, as Google.com is banned in China, the system think that I have no internet. I tried use some vpn app, and the downloading of native bridge 9_y starts. However the vpn is not stable, I still can't download the file successfully. So is there any mannual way to install the file, as I have alreay download this file from some chinese website. You can do this by root: mkdir /sdcard/arm cp houdini9_y.sfs /sdcard/arm setprop persist.sys.nativebridge 1 Then check if /system/lib/arm contains the libraries. > For issue 3, could provide more information about how to provide debug information? I can boot into debug in boot menu. But what next? This has been explained many times. Please search the forum. -- 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/CAKc24n1otTnVL3D3K8K%3Dgc4_jabb4%3DLRvGZaxKD3KwivDgZ5FA%40mail.gmail.com.
Chih-Wei Huang
Mar 2, 2020, 9:20:41 PM3/2/20
to Android-x86
kevin.Liu <kevin....@gmail.com> 於 2020年3月3日 週二 上午8:53寫道：
Full log is required.
In particular, check if the service is started:
getprop | grep rtk_hciattach
>
> thanks for the guide. I have attached a photo of debug info in previous email. Could you take a look
It only shows you have a RTL8723BS BT chip.
> thanks for the guide. I have attached a photo of debug info in previous email. Could you take a look
Full log is required.
In particular, check if the service is started:
getprop | grep rtk_hciattach
XiaoTao Liu
Mar 3, 2020, 5:24:15 PM3/3/20
to Android-x86
I boot into grub and choose debug. Type exit twice and boot into system. copy the log.txt from /data/log.txt.
I have attahced the log file in this email. Is this the full log?
On Tuesday, March 3, 2020 at 10:20:41 AM UTC+8, Chih-Wei Huang wrote:
On Tuesday, March 3, 2020 at 10:20:41 AM UTC+8, Chih-Wei Huang wrote:
kevin.Liu <kevin...@gmail.com> 於 2020年3月3日 週二 上午8:53寫道：
Chih-Wei Huang
Mar 3, 2020, 11:08:20 PM3/3/20
to Android-x86
XiaoTao Liu <kevin....@gmail.com> 於 2020年3月4日 週三 上午6:24寫道：
I didn't see any related messages from BT HAL.
I notice your device seems have to serial ports:
03-03 12:16:42.373 0 0 I 80860F0A: 00: ttyS1 at MMIO
0x9093b000 (irq = 16, base_baud = 2764800) is a 16550A
03-03 12:16:42.383 0 0 E serial0-0: controller busy
03-03 12:16:42.390 0 0 E serial0-0: failure adding device. status -16
03-03 12:16:42.396 0 0 I serial0 : tty port ttyS1 registered
03-03 12:16:42.416 0 0 I 80860F0A: 01: ttyS2 at MMIO
0x90941000 (irq = 17, base_baud = 2764800) is a 16550A
03-03 12:16:42.425 0 0 E serial1-0: controller busy
03-03 12:16:42.434 0 0 E serial1-0: failure adding device. status -16
03-03 12:16:42.441 0 0 I serial1 : tty port ttyS2 registered
Currently the init.sh will only attach the first port (ttyS1).
Maybe your device should use ttyS2.
You may try these commands (by root):
ln -sf ttyS2 /dev/rtk_h5
stop rtk_hciattach; start rtk_hciattach
Then test BT again.
BTW, please avoid sending such a big file
to the mailing list. The list has thousands of people.
Not everyone wants to receive such emails.
Just upload it to somewhere and provide the link.
>
> I boot into grub and choose debug. Type exit twice and boot into system. copy the log.txt from /data/log.txt.
> I have attahced the log file in this email. Is this the full log?
Right. But have you tried to operate Bluetooth?
> I boot into grub and choose debug. Type exit twice and boot into system. copy the log.txt from /data/log.txt.
> I have attahced the log file in this email. Is this the full log?
I didn't see any related messages from BT HAL.
I notice your device seems have to serial ports:
03-03 12:16:42.373 0 0 I 80860F0A: 00: ttyS1 at MMIO
0x9093b000 (irq = 16, base_baud = 2764800) is a 16550A
03-03 12:16:42.383 0 0 E serial0-0: controller busy
03-03 12:16:42.390 0 0 E serial0-0: failure adding device. status -16
03-03 12:16:42.396 0 0 I serial0 : tty port ttyS1 registered
03-03 12:16:42.416 0 0 I 80860F0A: 01: ttyS2 at MMIO
0x90941000 (irq = 17, base_baud = 2764800) is a 16550A
03-03 12:16:42.425 0 0 E serial1-0: controller busy
03-03 12:16:42.434 0 0 E serial1-0: failure adding device. status -16
03-03 12:16:42.441 0 0 I serial1 : tty port ttyS2 registered
Currently the init.sh will only attach the first port (ttyS1).
Maybe your device should use ttyS2.
You may try these commands (by root):
ln -sf ttyS2 /dev/rtk_h5
stop rtk_hciattach; start rtk_hciattach
Then test BT again.
BTW, please avoid sending such a big file
to the mailing list. The list has thousands of people.
Not everyone wants to receive such emails.
Just upload it to somewhere and provide the link.
youling 257
Mar 4, 2020, 12:33:49 AM3/4/20
to Android-x86
"rtk_hciattach -n -s 115200 /dev/rtk_h5 rtk_h5" only work if patch rfkill_gpio, http://git.osdn.net/view?p=android-x86/kernel.git;a=commit;h=81fad47aeb1c767a4ded1b579ed2b7be5f1724b1
rtl8723bs Bluetooth work with CONFIG_BT_HCIUART_RTL=y since kernel-4.19, "start rtk_hciattach" service never work on kernel-4.19 Androidx86, and never need this service.
brcm Bluetooth work with upstream kernel may be since begin kernel-4.17, "start btattach" service never work and never need on kernel-4.19 Androidx86.
but rtl8723bs and brcm bluetooth has same not detect any device problem if use upstream firmware.
they work well use my Android-ia vendor rtl8723bs bluetooth firmware and windows brcm bluetooth firmware BCM4343A0.hcd.
Daniel Cheung
Mar 4, 2020, 1:02:36 AM3/4/20
to andro...@googlegroups.com
I'm confused. If RTL8723BS BT works with just setting CONFIG_BT_HCIUART_RTL=y in kernel config, then it should be detecting devices right? Or do you mean it works only because you are using the Android-IA firmware? Then, can you upload a copy of the Android-IA firmware for RTL8723BS BT?
--
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/55cb98dc-b695-4233-a015-562d827d290d%40googlegroups.com.
youling 257
Mar 4, 2020, 3:27:26 AM3/4/20
to Android-x86
在 2020年3月4日星期三 UTC+8下午2:02:36，BrokenE39写道：
I'm confused. If RTL8723BS BT works with just setting CONFIG_BT_HCIUART_RTL=y in kernel config, then it should be detecting devices right? Or do you mean it works only because you are using the Android-IA firmware? Then, can you upload a copy of the Android-IA firmware for RTL8723BS BT?
On Tue, Mar 3, 2020 at 9:33 PM youling 257 <youli...@gmail.com> wrote:
"rtk_hciattach -n -s 115200 /dev/rtk_h5 rtk_h5" only work if patch rfkill_gpio, http://git.osdn.net/view?p=android-x86/kernel.git;a=commit;h=81fad47aeb1c767a4ded1b579ed2b7be5f1724b1--rtl8723bs Bluetooth work with CONFIG_BT_HCIUART_RTL=y since kernel-4.19, "start rtk_hciattach" service never work on kernel-4.19 Androidx86, and never need this service.brcm Bluetooth work with upstream kernel may be since begin kernel-4.17, "start btattach" service never work and never need on kernel-4.19 Androidx86.but rtl8723bs and brcm bluetooth has same not detect any device problem if use upstream firmware.they work well use my Android-ia vendor rtl8723bs bluetooth firmware and windows brcm bluetooth firmware BCM4343A0.hcd.
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 andro...@googlegroups.com.
Chih-Wei Huang
Mar 4, 2020, 5:02:40 AM3/4/20
to Android-x86
OK. Could you provide all necessary patches
to support rtl8723bs_bt?
Thank you!
youling 257 <youli...@gmail.com> 於 2020年3月4日 週三 下午1:33寫道：
to support rtl8723bs_bt?
Thank you!
youling 257 <youli...@gmail.com> 於 2020年3月4日 週三 下午1:33寫道：
youling 257
Mar 4, 2020, 6:15:03 AM3/4/20
to Android-x86
no patch. bluetooth work but can't scan any device is firmware problem.
but if rtk_hciattach method better than linux kernel upstream support, external rtl8723bs wifi driver better than linux kernel upstream support, why not "CONFIG_BT_HCIUART_RTL is not set""CONFIG_RTL8723BS is not set".
external rtl8723bs driver, https://github.com/youling257/rockchip_wlan/commits/443ce25ea0bb8e0b116e31541e534ac550be5dc8
在 2020年3月4日星期三 UTC+8下午6:02:40，Chih-Wei Huang写道：
在 2020年3月4日星期三 UTC+8下午6:02:40，Chih-Wei Huang写道：
Chih-Wei Huang
Mar 4, 2020, 9:35:12 AM3/4/20
to Android-x86
youling 257 <youli...@gmail.com> 於 2020年3月4日 週三 下午7:15寫道：
OK. Let me ask clearer.
CONFIG_BT_HCIUART_RTL=y is the current setting.
What else we need to do are:
* Put the firmware you provided to device/generic/firmware/
* Remove rtk_hciattach related code in init.sh
Is that it?
> but if rtk_hciattach method better than linux kernel upstream support, external rtl8723bs wifi driver better than linux kernel upstream support, why not "CONFIG_BT_HCIUART_RTL is not set""CONFIG_RTL8723BS is not set".
> external rtl8723bs driver, https://github.com/youling257/rockchip_wlan/commits/443ce25ea0bb8e0b116e31541e534ac550be5dc8
I don't know which one is better. I don't have a chance to test.
So does the driver in vanilla kernel work or not?
>
> no patch. bluetooth work but can't scan any device is firmware problem.
Sounds you know what to do. Then why can't you make the patches?
> no patch. bluetooth work but can't scan any device is firmware problem.
OK. Let me ask clearer.
CONFIG_BT_HCIUART_RTL=y is the current setting.
What else we need to do are:
* Put the firmware you provided to device/generic/firmware/
* Remove rtk_hciattach related code in init.sh
Is that it?
> but if rtk_hciattach method better than linux kernel upstream support, external rtl8723bs wifi driver better than linux kernel upstream support, why not "CONFIG_BT_HCIUART_RTL is not set""CONFIG_RTL8723BS is not set".
> external rtl8723bs driver, https://github.com/youling257/rockchip_wlan/commits/443ce25ea0bb8e0b116e31541e534ac550be5dc8
So does the driver in vanilla kernel work or not?
youling 257
Mar 4, 2020, 10:40:23 AM3/4/20
to Android-x86
在 2020年3月4日星期三 UTC+8下午10:35:12，Chih-Wei Huang写道：
youling 257 <youli...@gmail.com> 於 2020年3月4日 週三 下午7:15寫道：
>
> no patch. bluetooth work but can't scan any device is firmware problem.
Sounds you know what to do. Then why can't you make the patches?
OK. Let me ask clearer.
CONFIG_BT_HCIUART_RTL=y is the current setting.
What else we need to do are:
* Put the firmware you provided to device/generic/firmware/
need a few people test the Android-ia vendor 8723bs_bt firmware.
* Remove rtk_hciattach related code in init.sh
Is that it?
kernel-4.9 need rtk_hciattach, @XiaoTao Liu to test 9.0-r1-k49 bluetooth scan device.
> but if rtk_hciattach method better than linux kernel upstream support, external rtl8723bs wifi driver better than linux kernel upstream support, why not "CONFIG_BT_HCIUART_RTL is not set""CONFIG_RTL8723BS is not set".
> external rtl8723bs driver, https://github.com/youling257/rockchip_wlan/commits/443ce25ea0bb8e0b116e31541e534ac550be5dc8
@ BrokenE39 to test rtl8723bs v5.2.17.1_26955.20180307_COEX20180201-6f52
XiaoTao Liu
Mar 4, 2020, 5:53:02 PM3/4/20
to Android-x86
just want to make sure what I should do because I am not a expert in this.
Do you mean that I go to download the 9 r1 4.9kernel version and install it. Go to debug mode, try to scan blue tooth device, and then copy the log.txt to somewhere to upload. Send the download link in this email?
Chih-Wei Huang
Mar 4, 2020, 10:32:39 PM3/4/20
to Android-x86
XiaoTao Liu <kevin....@gmail.com> 於 2020年3月5日 週四 上午6:53寫道：
You may also try the firmware youling provided on kernel 4.19 version.
Just unzip it to /system/lib/firmware/, reboot and try again.
(your system must be installed as read-write)
>
> just want to make sure what I should do because I am not a expert in this.
> Do you mean that I go to download the 9 r1 4.9kernel version and install it. Go to debug mode, try to scan blue tooth device, and then copy the log.txt to somewhere to upload. Send the download link in this email?
Surely you can do that.
> just want to make sure what I should do because I am not a expert in this.
> Do you mean that I go to download the 9 r1 4.9kernel version and install it. Go to debug mode, try to scan blue tooth device, and then copy the log.txt to somewhere to upload. Send the download link in this email?
You may also try the firmware youling provided on kernel 4.19 version.
Just unzip it to /system/lib/firmware/, reboot and try again.
(your system must be installed as read-write)
kevin.Liu
Mar 5, 2020, 7:08:41 AM3/5/20
to android-x86
Awesome! I replaced those two files provided by youling and bluetooth works fine in 4.19 now.
------------------ Original ------------------
From: Chih-Wei Huang <cwh...@android-x86.org>
Date: Thu,Mar 5,2020 11:32 AM
To: Android-x86 <andro...@googlegroups.com>
Subject: Re: 3 issues in the latest 9.0 r1
-- 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/CAKc24n2U4JyHBZj_FTv4pfDpPxutprYc%3DWpmPybMpD4PPHPP1A%40mail.gmail.com.
Chih-Wei Huang
Mar 5, 2020, 10:57:34 PM3/5/20
to Android-x86
kevin.Liu <kevin....@gmail.com> 於 2020年3月5日 週四 下午8:08寫道：
So just replacing the firmware is enough. Right?
I'll submit the patch.
>
> Awesome! I replaced those two files provided by youling and bluetooth works fine in 4.19 now.
Cool!
> Awesome! I replaced those two files provided by youling and bluetooth works fine in 4.19 now.
So just replacing the firmware is enough. Right?
I'll submit the patch.
kevin.Liu
Mar 5, 2020, 11:15:41 PM3/5/20
to android-x86
yes,only replacing firmware is enough.
BTW, I noticed there are some customized code in init.sh for different tablet models started by "case". I am wondering if you could add some code for teclast x98 in your next release, especially for the gravity and rotation problem.
------------------ Original ------------------
From: Chih-Wei Huang <cwh...@android-x86.org>
Date: Fri,Mar 6,2020 11:57 AM
To: Android-x86 <andro...@googlegroups.com>
Subject: Re: 3 issues in the latest 9.0 r1
-- 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/CAKc24n16YFQrPBQ0GaO8v1pJb1bDGDH8F5%2Bt4vP3s3u9qEuNPA%40mail.gmail.com.
Jeff M.
Mar 6, 2020, 9:35:09 AM3/6/20
to Android-x86
I tried applying the firmware patch from youling mar4 on yhis thread now BT does not scan.
Chih-Wei Huang
Mar 6, 2020, 8:22:07 PM3/6/20
to Android-x86
kevin.Liu <kevin....@gmail.com> 於 2020年3月6日 週五 下午12:15寫道：
>
> yes,only replacing firmware is enough.
> BTW, I noticed there are some customized code in init.sh for different tablet models started by "case". I am wondering if you could add some code for teclast x98 in your next release, especially for the gravity and rotation problem.
Sure. But only if you tell me what to be added.
> yes,only replacing firmware is enough.
> BTW, I noticed there are some customized code in init.sh for different tablet models started by "case". I am wondering if you could add some code for teclast x98 in your next release, especially for the gravity and rotation problem.
XiaoTao Liu
Mar 6, 2020, 11:45:56 PM3/6/20
to Android-x86
Thank you in advance for your help. Only 4 lines, they are
has_sensors=true
hal_sensors=iio
set_property ro.iio.accel.quirks no-trig
set_property ro.iio.accel.y.opt_scale -1
I guess in order to make the "case" command effective, I need to provide model name of my tablet. But I don't know how to get model name in android. could you teach me how to do that?
On Saturday, March 7, 2020 at 9:22:07 AM UTC+8, Chih-Wei Huang wrote:
On Saturday, March 7, 2020 at 9:22:07 AM UTC+8, Chih-Wei Huang wrote:
kevin.Liu <kevin...@gmail.com> 於 2020年3月6日 週五 下午12:15寫道：
Daniel Cheung
Mar 6, 2020, 11:50:00 PM3/6/20
to andro...@googlegroups.com
No Chih-Wei Huang meant is how is the device identified. Look at the command at the top of the CASE code block and try to run it on the Teclast device and see what comes back. I tried it with my Teclast X98 Plus (A5C6 model) and it returns a lot of "default". That's not good enough to build a CASE to set those 4 command lines. Those lines are just commands to tell the system what to do, he can't just add it in there since he need to support multiple devices.
--
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/315daf19-d187-4d3d-96fb-b8010396474d%40googlegroups.com.
XiaoTao Liu
Mar 7, 2020, 12:01:55 AM3/7/20
to Android-x86
Thank you, I was think about the same thing. I mistaken it as model name.
So could you tell me which command to run to get the device identification info?
By typing the command "getprop ro.hardware" or "cat $DMIPATH/uevent" after executing "su"?
On Saturday, March 7, 2020 at 12:50:00 PM UTC+8, BrokenE39 wrote:
No Chih-Wei Huang meant is how is the device identified. Look at the command at the top of the CASE code block and try to run it on the Teclast device and see what comes back. I tried it with my Teclast X98 Plus (A5C6 model) and it returns a lot of "default". That's not good enough to build a CASE to set those 4 command lines. Those lines are just commands to tell the system what to do, he can't just add it in there since he need to support multiple devices.
On Fri, Mar 6, 2020 at 8:45 PM XiaoTao Liu <kevin...@gmail.com> wrote:
Thank you in advance for your help. Only 4 lines, they are--has_sensors=truehal_sensors=iioset_property ro.iio.accel.quirks no-trigset_property ro.iio.accel.y.opt_scale -1I guess in order to make the "case" command effective, I need to provide model name of my tablet. But I don't know how to get model name in android. could you teach me how to do that?
On Saturday, March 7, 2020 at 9:22:07 AM UTC+8, Chih-Wei Huang wrote:kevin.Liu <kevin...@gmail.com> 於 2020年3月6日 週五 下午12:15寫道：
>
> yes,only replacing firmware is enough.
> BTW, I noticed there are some customized code in init.sh for different tablet models started by "case". I am wondering if you could add some code for teclast x98 in your next release, especially for the gravity and rotation problem.
Sure. But only if you tell me what to be added.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
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 andro...@googlegroups.com.
Daniel Cheung
Mar 7, 2020, 12:11:35 AM3/7/20
to andro...@googlegroups.com
It's the DMIPATH. Can't remember the exact command but you can try as it is first and see what comes back.
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/cee240b6-60ca-4b31-89f1-4768ec229147%40googlegroups.com.
XiaoTao Liu
Mar 7, 2020, 7:11:56 AM3/7/20
to Android-x86
I entered "cat /sys/class/dmi/id/uevent" in terminal, and the output is as follows,
MODALIAS=dmi:bvnAmericanMegatrendsInc.:brv5.6.5:bd04/21/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M:rvnTECLAST:rntPAD:rvrTobefilledbyO.E.M.:cvnToBeFilledbyO.E.M.:ct3:cvrToBeFilledByO.E.M.:
.jpg?part=0.1&view=1)
On Saturday, March 7, 2020 at 1:11:35 PM UTC+8, BrokenE39 wrote:
It's the DMIPATH. Can't remember the exact command but you can try as it is first and see what comes back.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/cee240b6-60ca-4b31-89f1-4768ec229147%40googlegroups.com.
Jeff M.
Mar 7, 2020, 7:33:56 AM3/7/20
to Android-x86
In my Bios it gives the option for Wifi select either RTL8723BS or AP6255 but when I run ifconfig the driver appears as r8169 is there a way to blacklist this driver?
My system is a Z83-f
Why is it that when I plug usb touch screens and keyboards in that Bluetooth fails iver and over does it have to do with serial load order?
Jeff M.
Mar 7, 2020, 11:39:34 AM3/7/20
to Android-x86
When I mod probe it say module not found in modules.dep
Chih-Wei Huang
Mar 9, 2020, 1:12:23 AM3/9/20
to Android-x86
XiaoTao Liu <kevin....@gmail.com> 於 2020年3月7日 週六 下午8:12寫道：
http://git.osdn.net/view?p=android-x86/device-generic-common.git;a=commitdiff;h=3ad4607a3b786df3ab487e8a40852ade71684f48
> I entered "cat /sys/class/dmi/id/uevent" in terminal, and the output is as follows,
> MODALIAS=dmi:bvnAmericanMegatrendsInc.:brv5.6.5:bd04/21/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M:rvnTECLAST:rntPAD:rvrTobefilledbyO.E.M.:cvnToBeFilledbyO.E.M.:ct3:cvrToBeFilledByO.E.M.:
OK. I added this:
> MODALIAS=dmi:bvnAmericanMegatrendsInc.:brv5.6.5:bd04/21/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M:rvnTECLAST:rntPAD:rvrTobefilledbyO.E.M.:cvnToBeFilledbyO.E.M.:ct3:cvrToBeFilledByO.E.M.:
http://git.osdn.net/view?p=android-x86/device-generic-common.git;a=commitdiff;h=3ad4607a3b786df3ab487e8a40852ade71684f48
kevin.Liu
Mar 9, 2020, 5:49:48 AM3/9/20
to android-x86
I can only see 1 line of code being added, however there should be actually 4 lines, they are
has_sensors=true
hal_sensors=iio
set_property ro.iio.accel.quirks no-trig
set_property ro.iio.accel.y.opt_scale -1
------------------ Original ------------------
From: Chih-Wei Huang <cwh...@android-x86.org>
Date: Mon,Mar 9,2020 1:11 PM
To: Android-x86 <andro...@googlegroups.com>
Subject: Re: 3 issues in the latest 9.0 r1
-- 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/CAKc24n11LWPC%2B8zjTs0w6vhqQP7E7Z2v-1%2BeSiJVafxEq%3Dc2oQ%40mail.gmail.com.
Chih-Wei Huang
Mar 9, 2020, 5:55:35 AM3/9/20
to Android-x86
kevin.Liu <kevin....@gmail.com> 於 2020年3月9日 週一 下午5:49寫道：
>
> I can only see 1 line of code being added, however there should be actually 4 lines, they are
> has_sensors=true
> hal_sensors=iio
> set_property ro.iio.accel.quirks no-trig
> set_property ro.iio.accel.y.opt_scale -1
Just try it.
> I can only see 1 line of code being added, however there should be actually 4 lines, they are
> has_sensors=true
> hal_sensors=iio
> set_property ro.iio.accel.quirks no-trig
> set_property ro.iio.accel.y.opt_scale -1
Jeff M.
Mar 9, 2020, 9:56:48 AM3/9/20
to Android-x86
So I got my wifi to scan and connect but now several apps wont install anymore from the play store and on reboot were uninstalled does enabling rw mode normally cause this? This is my first time attempting to add firmware files to an Android root directory. Still after hardware is detected Mac address appears empty is there something in brcm that needs to be appended?
XiaoTao Liu
Mar 9, 2020, 6:46:19 PM3/9/20
to Android-x86
You are right. It works. Could you also add this model to init_tscal? Because when I newly install android, I will have to manually creat pointercal to do calibration.
I guess what init_tscal does is to check if there is pointercal in the corresponding location first, and creat it if there is not. Right?
I guess what init_tscal does is to check if there is pointercal in the corresponding location first, and creat it if there is not. Right?
Chih-Wei Huang
Mar 9, 2020, 11:11:48 PM3/9/20
to Android-x86
XiaoTao Liu <kevin....@gmail.com> 於 2020年3月10日 週二 上午6:46寫道：
What's the output of 'cat /sys/class/dmi/id/product_name'?
Anything else?
> I guess what init_tscal does is to check if there is pointercal in the corresponding location first, and creat it if there is not. Right?
Yes, if it's a known model which needs pointercal.
>
> You are right. It works. Could you also add this model to init_tscal? Because when I newly install android, I will have to manually creat pointercal to do calibration.
OK. But due to some reasons, init_tscal checks a different string.
> You are right. It works. Could you also add this model to init_tscal? Because when I newly install android, I will have to manually creat pointercal to do calibration.
What's the output of 'cat /sys/class/dmi/id/product_name'?
Anything else?
> I guess what init_tscal does is to check if there is pointercal in the corresponding location first, and creat it if there is not. Right?
XiaoTao Liu
Mar 10, 2020, 8:03:33 AM3/10/20
to Android-x86
The output is "To be filled by O.E.M."
I have asked a lot, thank you so much.
On Tuesday, March 10, 2020 at 11:11:48 AM UTC+8, Chih-Wei Huang wrote:
.jpg?part=0.1&view=1)
On Tuesday, March 10, 2020 at 11:11:48 AM UTC+8, Chih-Wei Huang wrote:
XiaoTao Liu <kevin...@gmail.com> 於 2020年3月10日 週二 上午6:46寫道：
Jeff M.
Mar 12, 2020, 8:23:57 AM3/12/20
to Android-x86
I found ts_cal to not work on my device and pointecal was in a different directory than expected.
Reply all
Reply to author
Forward
0 new messages