Notion Ink

[Kevin JF]

Hi,
 I am trying to port Android-X86 to Notion Ink Cain 10'' .
After building Android-x86 with Kernel 4.0 and Mesa 10.6-devel, this is the list of items working/not working

Status
Graphics    -            Working
Touch        -            Working
Video Playback        -    Not Checked
External Keyboard    -    Working
Wifi                -    Not Working
Bluetooth            -    Not Working
Sound                -    Not Working
Power Button        -    Not Working
Suspend/Power Off    -    Not Working
Battery/Charger        -    Not Working
Accelerometer        -    Not Working
Expandable Storage[Memory Card]    -    Not Working
Mounting [Internal NAND]        -    Not Working [NTFS problem?]

Other things I've found
Wifi
Realtek 8723BS Wifi with BT Coexist in SDIO Mode
Spec Sheet[?]:http://wenku.baidu.com/view/d7bf46ff76eeaeaad1f3306b.html

Related Links
https://github.com/hadess/rtl8723bs
OR
https://github.com/lwfinger/rtl8723bs/tree/hadess

https://github.com/22ktv/rtl8723bs
https://github.com/22ktv/bluez-hcitools

Bluetooth

 - Requires h5 protocol (3-Wire) [?]
 - Support in Bluedroid with hci_h5.c required?
Example:
https://github.com/jasonyuananbei/sunniwell_bluetooth

Another place with reference to Realtek 8723BS
http://dl.linux-sunxi.org/SDK/A23-v1.0/unpacked/A23/android/device/softwinner/polaris-common/hardware/realtek/
Contains some files with support for realtek/8723BS

Battery/Charger
Seems to be a MPD - Uses XPower AXP288 chipset.
More support is there in linux-4.1. They just added the extcon support for charger detection to the kernel

Accelerometer
Seems to be Kionix KXCJ9 from the driver file in Program files.

Sound
Uses Baytail SOC RTK5640[?]



Also : I recently checked github for source compatible to my device and I came across these

https://github.com/heidiao/sfp_m2_wifi/blob/master/ww04_WLAN_WS/0001-Merge-the-patches-from-product-variant-cht_rvp-to-ch.patch
has
-# Source: device/intel/mixins/groups/wlan/rtl8723bs/BoardConfig.mk

and

https://github.com/heidiao/sfp_m2_bt/blob/master/BT_20150318_Pre-Alpha-Final-Patches/0001-LnP-BT-porting-for-product-cht_cr_rvp-20150210.patch
has
-# Source: device/intel/mixins/groups/bluetooth/rtl8723bs/BoardConfig.mk

It seems that there is support for cherrytrail devices somewhere and there is a mixin with realtek 8723bs support. But I haven't found it anywhere. Any one have any link where I can find it?

I checked android-ia sources but didn't find it anywhere. :( . Does anyone know where to get these files?


Attaching decompiled DSDT , the kernel config , and some log files.

Please help me port android-x86 to this device :)
Thanks
K

[Chih-Wei Huang]

Good work.

You may sync the latest kernel 4.0 branch.
I just added the rtl8723bs driver based on
the hadess's branch.

[Kevin JF]

Good work.

Thanks :)

 

You may sync the latest kernel 4.0 branch.
I just added the rtl8723bs driver based on
the hadess's branch.

I'm compiling it now and will test it today evening.
There is an errata in the above post

SOUND Card  is  byt-rt5640

 

[Kevin JF]

You may sync the latest kernel 4.0 branch.
I just added the rtl8723bs driver based on
the hadess's branch.

Ok. I compiled the new build and ran it.

Wifi
I can now enable the Wifi and scan networks in the Android Notification Area. But I couldn't connect to my network, which is WPA2 secured. What should I do next?

Storage
Previously I could write to the FAT partition of the USB which was used to live-boot android. But now it seems that it is mounted read-only(according to mount command) . How can I mount it in read/write mode? Is there any particular reason for mounting it in ro? Without that, I have no way of taking dmesg or logcat out of the running system. Sorry :(

Sound
It seems that now there is some files in /dev/snd [ Previously, I only found a file/folder named timer] . But my dmesg is filled with a spurious message.

sst-mfld-platform sst-mfld-platform :ASsC: can't open interface media-cpu-dai : -22
Baytrail Audio Port : ASoC: failed to start FE -22

I can't find anything else when I type dmesg | less

I saw somewhere about using alsa_ctl . So I tried

/ # alsa_ctl restore -f /android/etc/alsa/bytrt5640.state

but the error shown is
ALSA lib external/alsa-lib/src/conf.c:3311:(snd_config_hooks_call) Cannot open shared library (null)
ALSA lib external/alsa-lib/src/conf.c:3712:(snd_config_update_r) hooks failed,removing configuration
alsa_ctl: set_controls:1424: snd_ctl_open error: No such file or directory

I'm not sure if this was the command to run or if bytrt5640.state needs to be changed , since that seems to be for A100TA[?] . I ran the same command through strace and I'm attaching the output picture[The quality is bad, i know :) ]

Accelerometer
A good news is I can see the accelerometer working by reading a file in sys folder . If I get some help in mounting the USB device in rw mode, I can give more info.




All the rest of the items are still "Not Working"

Please help me.
d(._.)b
-K

[Kevin JF]

Forgot to attach file :embarassed:

[Chih-Wei Huang]

2015-05-07 12:40 GMT+08:00 Kevin JF <reach.k...@gmail.com>:
> Ok. I compiled the new build and ran it.
>
> Wifi
> I can now enable the Wifi and scan networks in the Android Notification
> Area. But I couldn't connect to my network, which is WPA2 secured. What
> should I do next?

Check the logcat and/or update the driver.

> Storage
> Previously I could write to the FAT partition of the USB which was used to
> live-boot android. But now it seems that it is mounted read-only(according
> to mount command) . How can I mount it in read/write mode? Is there any
> particular reason for mounting it in ro? Without that, I have no way of
> taking dmesg or logcat out of the running system. Sorry :(

Should not happen.
What does vold say?

For debugging, just re-mount it to be rw.

> Sound
> It seems that now there is some files in /dev/snd [ Previously, I only found
> a file/folder named timer] . But my dmesg is filled with a spurious message.
>
> sst-mfld-platform sst-mfld-platform :ASsC: can't open interface
> media-cpu-dai : -22
> Baytrail Audio Port : ASoC: failed to start FE -22
>
> I can't find anything else when I type dmesg | less
>
> I saw somewhere about using alsa_ctl . So I tried
>
> / # alsa_ctl restore -f /android/etc/alsa/bytrt5640.state

The command should be run in android env,
not before chroot to android.

> but the error shown is
> ALSA lib external/alsa-lib/src/conf.c:3311:(snd_config_hooks_call) Cannot
> open shared library (null)
> ALSA lib external/alsa-lib/src/conf.c:3712:(snd_config_update_r) hooks
> failed,removing configuration
> alsa_ctl: set_controls:1424: snd_ctl_open error: No such file or directory

What branch and target did you build exactly?
I recall it's a known issue of lollipop-x86 64-bit target.
No idea about it yet.

Try the 32-bit target first.

> I'm not sure if this was the command to run or if bytrt5640.state needs to
> be changed , since that seems to be for A100TA[?] . I ran the same command
> through strace and I'm attaching the output picture[The quality is bad, i
> know :) ]
>
> Accelerometer
> A good news is I can see the accelerometer working by reading a file in sys
> folder . If I get some help in mounting the USB device in rw mode, I can
> give more info.

What sys node is it?

[Kevin JF]

On Thursday, May 7, 2015 at 12:01:26 PM UTC+5:30, Chih-Wei Huang wrote:

2015-05-07 12:40 GMT+08:00 Kevin JF <reach.k...@gmail.com>:

> Wifi

Check the logcat and/or update the driver.

WIfi WORKS!!! It seems I may have entered a wrong password during checking. Sorry (,_,) . Anyway, it works! I was able to use the browser and visit few websites. Thanks a lot :)

Bluetooth doesn't work. When it is switched on in notification drop down menu, It seems to do something, but then returns to the off state.

> Sound
> It seems that now there is some files in /dev/snd [ Previously, I only found
> a file/folder named timer] . But my dmesg is filled with a spurious message.

> ...

> / # alsa_ctl restore -f /android/etc/alsa/bytrt5640.state

The command should be run in android env,
not before chroot to android.
 

What branch and target did you build exactly?
I recall it's a known issue of lollipop-x86 64-bit target.
No idea about it yet.

Try the 32-bit target first.

I was live booting in DEBUG mode so far. But since you said to run things in android env, I booted in Normal Live mode. The same errors exist. But I'm able to get the logcat, directory listing, strace of alsactl and other miscellaneous things, which I'm attaching with this post. I tried building the 32bit build initially, but it had some errors. If you think that is the problem, I'll try building that later. Can 32bit build use make efi_img command to build?  I don't want to change my uefi to full legacy bios mode  (-_-)'

> Accelerometer

What sys node is it?

The sys node is  /sys/bus/i2c/devices/i2c-SMO8500:00/iio:device1/
and these are the files inside that node

files and corresponding values
in_accel_sampling_frequency         12.500000
in_accel_scale with the value                     0.019163
in_accel_scale_available      

                     0.009582 0.019163 0.038326
in_accel_x_raw                                         Varies according to movement
in_accel_y_raw                                         Varies according to movement
in_accel_z_raw                                         Varies according to movement
sampling_frequency_available                    0.781000 1.563000 3.125000 6.250000 12.500000 25 50 100 200 400 800 1600


Power/Battery

Also I made another discovery, there exists these files which gave different values when connected to charger
Node values and it's value during battery and power :

watch -n1 cat /sys/bus/i2c/devices/i2c-INT33F4:00/axp288_adc/iio:device0/in_current3_input
0               on battery
400           on acpower

watch -n1 cat /sys/bus/i2c/devices/i2c-INT33F4:00/axp288_adc/iio:device0/in_current4_input
1104          battery - and other values
0               on AC power

watch -n1 cat /sys/bus/i2c/devices/i2c-INT33F4:00/axp288_adc/iio:device0/in_voltage5_input
3584          on battery
3664  - settles to around that value on power

Can this be used for battery since I don't see any other place where I can get values?

Another problem that I've encountered is running apps. I tried running some apps, but it just crashes . Logcat is attached. I couldn't even run any of the live wallpapers.

procDir.txt and sysDir.txt are compressed because of their size. They are the recursive files/subfolder listing of proc and sys respectively.


-K

[Kevin JF]

Seems this new fuel_guage driver is required for power updates

http://git.infradead.org/battery-2.6.git/blob/5a5bf49088f4c92f36786a2e4c20e17f715f0827:/drivers/power/axp288_fuel_gauge.c

Lots of good news for SoC on the new 4.1 Kernel :)

[Zeeshan Ahmed P]

Can you please provide the image that you are currently running on your Cain 10 ?

--
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 post to this group, send email to andro...@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.

[Abhishek Raj]

Yes, please provide the iso you are using for your cain.

[Kevin JF]

Can I post ISO as an attachment to groups? How do people post isos here? 

Anyway, you'll have to wait because my build machine is shot to hell. Battery died and my HD started sprouting bad sectors. Thanks to the OS being installed on an LVM, I've been successful in moving it to a new HDD. Will upload a build next week...if all goes well :) 

[Antony Stone]

On Saturday 23 May 2015 at 13:11:18 (EU time), Kevin JF wrote:

> Can I post ISO as an attachment to groups?

No - something that large either won't get accepted at all, or is certainly
unpopular with all the people who then receive it in their inboxes as a
result, or find it in the archives later.

> How do people post isos here?

Upload them to any file sharing / storage service of your choice (there are
loads of free ones) and then post here a link to download it from.

> Anyway, you'll have to wait because my build machine is shot to hell.
> Battery died and my HD started sprouting bad sectors. Thanks to the OS
> being installed on an LVM, I've been successful in moving it to a new HDD.
> Will upload a build next week...if all goes well :)

Good luck :)


Antony.

--
All generalisations are inaccurate.

Please reply to the list;
please *don't* CC me.

[Kevin JF]

I came across this while browsing though dmesg

<6>[    2.601706] bytt100_rt5640 bytt100_rt5640: snd-soc-dummy-dai <-> media-cpu-dai mapping ok

<6>[    2.607669] compress asoc: snd-soc-dummy-dai <-> compress-cpu-dai mapping ok

<6>[    2.613967] bytt100_rt5640 bytt100_rt5640: rt5640-aif1 <-> ssp2-port mapping ok

<3>[    2.621527] bytt100_rt5640 bytt100_rt5640: Connecting non-supply widget to supply widget is not supported (Int Mic -> LDO2)

<4>[    2.635952] bytt100_rt5640 bytt100_rt5640: ASoC: no dapm match for Int Mic --> (null) --> LDO2

<3>[    2.643087] bytt100_rt5640 bytt100_rt5640: ASoC: Failed to add route Int Mic -> direct -> LDO2

<6>[    2.656395] intel_sst_acpi 80860F28:00: LPE base: 0x90a00000 size:0x200000

<6>[    2.664076] mmc0: MAN_BKOPS_EN bit is not set

<6>[    2.664094] intel_sst_acpi 80860F28:00: IRAM base: 0x90ac0000

<6>[    2.664144] intel_sst_acpi 80860F28:00: DRAM base: 0x90b00000

<6>[    2.664174] intel_sst_acpi 80860F28:00: SHIM base: 0x90b40000

<6>[    2.664209] intel_sst_acpi 80860F28:00: Mailbox base: 0x90b44000

<6>[    2.664234] intel_sst_acpi 80860F28:00: DDR base: 0x20000000

<6>[    2.666135] intel_sst_acpi 80860F28:00: Got drv data max stream 25

<4>[    2.666477] intel_sst_acpi 80860F28:00: Direct firmware load for intel/fw_sst_0f28.bin failed with error -2

<4>[    2.666480] intel_sst_acpi 80860F28:00: Falling back to user helper

It seems the audio HAL is not configured properly. Does anyone know a place where I can learn more about audio alsa hal in linux?

Also, interestingly the "Direct firmware load is failing"  . I checked to see if there is any difference in the firmware files between linux-firmware repository and lollipop one. It seems some of the files differ by quite a few bytes. Can it be the cause of the problem? The *bin files are the same, but the bseq files are different.

I also have a couple of more questions

What is the role of tinyalsa? How can I build it into android-x86?

What is the use of libhardware_legacy directory? Is it really necessary in lollipop? 

Is there a checklist or something on how to write libsensor HAL's? AFAIK, this contains a kionix accelerometer and nothing else. So I have to modify the sensor HAL, add the sensor to the sensor list, do something such that this gets translated to rotational sensor[?] , and cross my fingers and hope for the best :) . Can anyone point me to a tutorial or something which can help me through this? Or give a series of steps on how to move forward on this(More substantial than the above musings :D ) ..

Thanks :)

-K

[Kevin JF]

These are the logs left in my CAIN after the last test boot.

[Kevin JF]

On Saturday, May 23, 2015 at 4:53:12 PM UTC+5:30, Antony Stone wrote:

On Saturday 23 May 2015 at 13:11:18 (EU time), Kevin JF wrote:

> Can I post ISO as an attachment to groups?

No - something that large either won't get accepted at all, or is certainly
unpopular with all the people who then receive it in their inboxes as a
result, or find it in the archives later.  

> How do people post isos here?

Upload them to any file sharing / storage service of your choice (there are
loads of free ones) and then post here a link to download it from.

Ok. Will do that.

 

> Anyway, you'll have to wait because my build machine is shot to hell.
> Battery died and my HD started sprouting bad sectors. Thanks to the OS
> being installed on an LVM, I've been successful in moving it to a new HDD.
> Will upload a build next week...if all goes well :)

Good luck :)

Thanks :D 

 

                                      Please reply to the list; 

                                                         please *don't* CC me.

Noticed a checkbox with "Cc" for the first time and unchecked it (y)  :D 

-K

[Kevin JF]

I've uploaded my last build to

https://drive.google.com/file/d/0Bwo5WHuXECLbZ1FfMGlHZzhnaDA/view?usp=sharing

[Zeeshan Ahmed P]

Thanks a lot..

On Fri, May 29, 2015, 10:08 Kevin JF <reach.k...@gmail.com> wrote:

I've uploaded my last build to

https://drive.google.com/file/d/0Bwo5WHuXECLbZ1FfMGlHZzhnaDA/view?usp=sharing

[Omar Zapata Valdez]

How do I install your builds on my Hp Stream 7???

[Kevin JF]

Sorry, I don't know about the items inside HP Stream 7 . So I can't recommend installing this build inside it. May work/May not work/May burn out things, etc....

[Kevin JF]

I tried building the 32bit version. But it restarts the tablet when the "ANDROID" boot screen should have shown. Don't know how to get the log to analyze the problem. It seemed to me that all the major services were crashing healthd,mediaserver etc.

On Thursday, May 7, 2015 at 12:01:26 PM UTC+5:30, Chih-Wei Huang wrote:

[Zeeshan Ahmed P]

the build you provided works great.. its smooth.. no lag at all.. wifi works perfectly but i wish touch worked.. do you have a build with gapps and touch working ?? It'd be great if you uploaded that for us.. thanks a ton in advance..

[Kevin JF]

Touch doesn't work? It works in mine!
 I recently heard that there were differences in different batches of the Notion Ink - viz. older models had micro usb cable charging, newer models doesn't, Older had a different atom processor etc. Anyway, I can't do anything about touch in your model if I can't have access to it, or get the logs and all. Sorry.
I'm currently focusing on making more peripherels - audio, accelerometer, battery work before moving into Gapps. Anyway, I'll put it online once that happens, hopefully, the new kernel supports your model out of the box ;)

-K

[Zeeshan Ahmed P]

Looking forward to ur next build... I hope touch screen starts working for me on your next build...
And is there anyway that I can get you logs on my touch screen problem...
And also I was thinking of downloading the x86 sources.. Have you uploaded your device tree for Cain 10 on github.. Would really appreciate the help... Thank you in advance...

--

[Abhishek Raj]

I tested your build on Notion Ink Cain 8, same hardware as the cain 10 but i always get a blank screen after loading androidx86. This happens with every other build(as a matter of fact with other linux too). When i do the nomodeset it goes to the flickering screen. I was able to boot into android home twice by mistake, using the generic 4.4r2 build but that is not repeating :((it was really fast so i am assuming hardware acceleration). How can i help and give logs to you?

[Greg Haerman]

I want to help as well because appearently you're build is stable on our HP Stream 7. Wifi works and possibly eveyrthing else like audio. I kinda wanna try out Android on a windows laptop, it would be cool for me. Only the touch isnt fully working and the accelometer. I can provide you dsmeg. Here are the drivers it uses

Kionix G-Sensor Enabling Driver

Goodix Touch Driver

[The Ecki]

W dniu piątek, 12 czerwca 2015 02:37:50 UTC+1 użytkownik Greg Haerman napisał:

I want to help as well because appearently you're build is stable on our HP Stream 7. Wifi works and possibly eveyrthing else like audio. I kinda wanna try out Android on a windows laptop, it would be cool for me. Only the touch isnt fully working and the accelometer. I can provide you dsmeg. Here are the drivers it uses

Kionix G-Sensor Enabling Driver

Goodix Touch Driver

For me, there are problems with the commissioning of the stick. Even though I have no way to check if everything is working. On all versions, there was a problem with the touch specifically in terms of scrolling. 

[Rolandas Gedgaudas]

have you found a way to boot?

[The Ecki]

W dniu poniedziałek, 15 czerwca 2015 16:16:06 UTC+1 użytkownik Rolandas Gedgaudas napisał:

have you found a way to boot?

Read yourself about me, it is best to have someone to help me because I do not know much about complicating the drivers on Android. The touch works very well. We need only WiFi, sound, volume keys. It's probably all. Anyone can add drivers to the build?

Link: https://drive.google.com/uc?id=0B2evBKvIpdYkZU02blF3ZFpuX1U&export=download

 

[Abhishek Raj]

Yes I can boot using the grubia32 version, just paste the bootia32.efi in efi/boot folder with grub.conf and press the power and volume up button during start up and select usb from there. You can go to setting->update and recovery->restart advanced in windows. I am only beable to boot windows i.e. 8 32bit pro and 10 32bit insider preview but almost all linux hang after i start X.

[Abhishek Raj]

Okay android_x86-5.1.0_r3-MESA-10.4-20150420 is the only build that boots everytime with nomodeset on Cain 8. There is no hw acceleration so its damn slow but this atleast goes to homescreen. All other latest builds have a 'untraced pid xxxx closed' whenever i try to start zygote and other surfaceflinger crashed errors. Iwill submit dmesg and logcat once i figure out how to mount my pendrive.

On Monday, 15 June 2015 20:46:06 UTC+5:30, Rolandas Gedgaudas wrote:

[Greg Haerman]

Any updates ont the thread? This is the only one i got working on my tablet for some reason

[Kevin JF]

Sorry..Not many changes have occured in the build..I'm waiting for new kernel release.

I've also uploaded bug report to the kernel. Hopefully power/battery and sound will get fixed from that end.

https://bugzilla.kernel.org/show_bug.cgi?id=100361
https://bugzilla.kernel.org/show_bug.cgi?id=100411

Also, it seems like some firmware changes are being made in the sound drivers.
https://kernel.googlesource.com/pub/scm/linux/kernel/git/vkoul/firmware/+/byt

I'll make a new build only after that.


Which device is yours? What is working in this device as opposed to rgb's build?AFAIK, mine is just normal kernel with a few kernel config's . If you can find out which, you can request rgb for a new build. He releases new builds in a regular basis.

[Greg Haerman]

i have the hp strram 7. Your build touch works but really buggy and wifi works but accelometer wont work. rgbs lates build of 4.4 touch works wifi dosent and the accelometer is messed up. 

[Kevin JF]

Try the latest builds from

http://www.android-x86.net/index.php?action=downloads;cat=12

Also, if you are using android-x86 while connected to the power, there might be problem with the touchscreen... I've noticed that things get weird when using items connected to power. Try it while running in battery.

[rbg]

or here:

   https://drive.google.com/folderview?id=0B2evBKvIpdYkfm1EdmFtUUc1QjA5dmlLMXlEaEJyQ29wc1VtbDRQa2YyOXlJdjZFUWRFckk&usp=sharing#list

[Zeeshan Ahmed P]

The last build that you provided works great for me on my Cain 10.. I thought the touchscreen didn't work.. but after installation it works fine works.. the build is super smooth and WiFi works too.. and the power button long press works, but short press doesn't.. it restarts when I press it..

I tried the baytrail version for t100 on my Cain.. In that build orientation worked but was oriented the wrong way, anyway that's a great start :) and the power button press puts the tablet to sleep too which is awesome, however obviously on those builds touch n WiFi don't work..

Anyhow Thank you very much for your build I'd use the last build as my secondary driver but the problem is superuser isn't working on that build which makes gapps installation impossible..

It'd be awesome if you uploaded another build with gapps or with SU.. looking forward to that.. and again thanks a lot for the previous build.. great work keep it up :)

[Kevin JF]

 

I tried the baytrail version for t100 on my Cain.. In that build orientation worked but was oriented the wrong way, anyway that's a great start :) and the power button press puts the tablet to sleep too which is awesome, however obviously on those builds touch n WiFi don't work..

Can you post the link to the version for which you could use the power button for sleep? I'll try to integrate it to the current one...as soon as I find out what made it work :) ...
 

Anyhow Thank you very much for your build I'd use the last build as my secondary driver but the problem is superuser isn't working on that build which makes gapps installation impossible..

It'd be awesome if you uploaded another build with gapps or with SU.. looking forward to that.. and again thanks a lot for the previous build.. great work keep it up :)

If the sleep button works, I'll post another build soon :) .. I'll try to integrate gapps or su...but it seems it'll need loads of work  (-_-)''  ... Let me see :)  


Kevin

[Chih-Wei Huang]

Instead of focusing your customized build, please submit
patches of fixes for your device so they could be integrated
into the future release of android-x86.

Please note I am not against customized build.
You are free to make your own build since
this is an open source project.
However, I hope the fixes of kernel, hal or firmware
for a particular device could be put into
the main trunk of android-x86 source tree.
It's fine to create your own build to customize
ui, apps or anything you like.
(submitting this kind of patches is also welcome
if you think it benefits the whole community)

> --
> 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 post to this group, send email to andro...@googlegroups.com.
> Visit this group at http://groups.google.com/group/android-x86.
> For more options, visit https://groups.google.com/d/optout.

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

[Kevin JF]

The only customization these builds have is in the kernel configuration and the packages used. I used the latest kernel with every configuration item related to baytrail, intel, designware and X-Power enabled and the latest mesa. Other than these, I haven't found anything else to change in android-x86 code, or know what to change.

I started this topic to see if there is something I could do.So far, I've found out about the wifi drivers (which was added to the android-x86 kernel) , and that the kernel does not support baytrail/intel fully and so I've submitted bug reports to the kernel. As soon something comes up, I'll update/submit patch/do something useful. :)

I've posted my changed configs in this thread, but I'm not sure that those changes could be applied to the generic android-x86. If there is an example how to create device specific folders in the current android-x86 (using kernel-config overlays, and other device specific overrides), I'll try to submit patches with those changes. I tried doing that once, but the current method was too convoluted for me to understand.Sorry.

[Chih-Wei Huang]

2015-07-21 17:47 GMT+08:00 Kevin JF <reach.k...@gmail.com>:
> The only customization these builds have is in the kernel configuration and
> the packages used. I used the latest kernel with every configuration item
> related to baytrail, intel, designware and X-Power enabled and the latest
> mesa. Other than these, I haven't found anything else to change in
> android-x86 code, or know what to change.

What latest kernel did you mean?
The latest vanilla kernel?
Or the latest android-x86 kernel?

> I started this topic to see if there is something I could do.So far, I've
> found out about the wifi drivers (which was added to the android-x86 kernel)
> , and that the kernel does not support baytrail/intel fully and so I've
> submitted bug reports to the kernel. As soon something comes up, I'll
> update/submit patch/do something useful. :)

Fine. If there are patches, please back-port them
to the android-x86 kernel (android-4.0 branch) if possible.

I'll also keep tracking the upstream kernel as possible.

> I've posted my changed configs in this thread, but I'm not sure that those
> changes could be applied to the generic android-x86. If there is an example
> how to create device specific folders in the current android-x86 (using
> kernel-config overlays, and other device specific overrides), I'll try to
> submit patches with those changes. I tried doing that once, but the current
> method was too convoluted for me to understand.Sorry.

I do not encourage creating device specific folders.
Like a normal linux distro, currently we use a generic kernel
that should works for any device.
Device drivers should be set to modules and loaded on demand.

So please base on the current android-x86 defconfig
to create your configs and provide a patch.

[Zeeshan Ahmed P]

Have managed to install the previous build that you provided on to a partition along with windows 10 on my cain10
Since there is no root or gapps.. The use has been limited.. Any build that u already have with gapps or su will be very useful.. Would be great if u uploaded it somewhere.. Thank you

[Prasanna T.R.]

Hey, I hope there are notion ink Cain users here.. I had installed nougat rc1 earlier, but the power button wouldn't work properly. One press would turn the screen off, but after some time, pressing the power button wouldn't wake the screen.
However, quickly pressing power button after making it sleep wakes the screen.
Is there some default behaviour that I have to change? If so, how do I do it?

[Tomasz Witke]

Same on VirtualBox and VMware player for me.

--
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+unsubscribe@googlegroups.com.

To post to this group, send email to andro...@googlegroups.com.

Visit this group at https://groups.google.com/group/android-x86.