Specific Android x86 build for my RCA Cambio W101SA23T1?

[Jordan Anderson]

I have an RCA Cambio W101SA23T1 and it uses UEFI.

Intel Atom x5 Z8350 at 1.44Ghz

x64 based processor.

According to Device manager:

Kionix KXCJ9 3-axis accelerometer

Intel SST Audio device(WDM) with a Realtek I2S Audio codec

Camera sensor OV2680

Standard bluetooth radio with Realtek Bluetooth UART Bus driver

Realtek RTL8723BS Wireless LAN 802.11n SDIO Network adapter

Intel AVStream camera

Intel HD Graphics

SanDisk DF4032 SSD

Any experts out there that would like to put together an image of Android that's fully compatible with the RCA Cambio? I tried every flavor of Android and none of them worked. I used Rufus to flash images to my flash drive, but some of them refuse to boot or get stuck at the android logo. 6.0 r2 and 7.1 work, but 4.4 and beyond won't work in fact I don't even know anything about code or editing mapfiles to get specific drivers to work with my tablet. I don't know what lsusb is, so I'm just gonna let someone else build an image for it. Let me know if anyone has info

[Jordan Anderson]

This post seems to be ignored. If a driver implementation involves mapfiles or editing the source code, please give easy to understand instructions..  While I am experienced with Android, I am not experienced in the Linux source file editing side, but I can follow instructions well.

[Jordan Anderson]

I'm not happy that the 20 people viewing this are not helping me. If you do a google search for "Android-x86 on an RCA Cambio W101SA23T1", it will come up bone dry. 

[Chih-Wei Huang]

Because you didn't explain your problem clearly.
You said "6.0 r2 and 7.1 work, but 4.4 and beyond won't work"
So what problem did you ask exactly?
You want to run 4.4 on it?
That's unrealistic since 4.4 is EOL.



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

[Jordan Anderson]

Sorry if I sounded a bit harsh on that. I had no idea 4.4 was EOL. Basically I wanted an Android build that will specifically run on RCA's line of Cambio tablets like the W101SA23T1, because almost all the device functions don't work, and if I wanted to add a device like the Goodix GDIX1002 touch driver for it to work, I had to edit a mapfile or something along the lines of coding. The problem I'm having is, there's a whole host of compatibility issues and some versions of Android simply won't boot even if I had my flash drive on GPT or MBR for UEFI which my tablet has. I simply didn't think anyone has ever tried Android-x86 on their Cambio. If there's an easier workaround I would like to hear from you

[Jordan Anderson]

Plus I used Rufus and tried Win32DiskImager and Unetbootin as well and the "stuck on android logo" problem still persists. I have a boot log file, from when I last tried 7.1, that you could get a further look at. I'll attach it later. Thanks in advance.

[Jordan Anderson]

Advice on how to easily add your own devices to the Android kernel and compile it is what I am asking. I would try to use Windows to figure it out or go around the command line. But android-x86_64-6.0-r1.iso  is not functioning enough to do anything when it does boot up on my tablet

[Chih-Wei Huang]

Adding drivers to Android kernel is nothing different than
adding drivers to a linux distribution.
However, if you don't have any experience on kernel hacking,
it's not recommended unless you really want to learn.

But the real question is, are linux drivers available
for all your peripherals? If you really search it,
I am afraid that the answer will let you down.

At a glance your peripherals,
The CPU and GPU is supported;
sensors KXCJ9 is probably supported;
audio is may be a problem;
camera is almost no hope.

[Jordan Anderson]

I think I will go with 7.1 RC1 which works flawlessly but probably most of the specs my Cambio has don't work quite well. Auto-rotate on the KXCJ9 works fine but I wonder how to get the Goodix GDIX1002 touchscreen to work, but to my experience, it probably needs a little tweaking to get the devices to function properly. 

We probably can work together to build an image and add drivers to the files in /system/lib/devices (Which I *think* is the right directory). Then we can compile the android-x86-7.1-w101sa23t1.iso, test it on my tablet, and release it to the public. 

I've already renamed the stock Iso, but it wouldn't let me attach it because of an upload error.

[Jordan Anderson]

I'm not going to bother looking up drivers because apparently from what I briefly read online, not all the Linuxes support it out of the box...

I wanted to test out Ubuntu 64-bit, but Unetbootin took forever to put it on my flash drive so I gave up :(

[Jordan Anderson]

I also have a question...Has Mauro or anyone else had any luck getting this model tablet compatible with Android in the past? Need to know how many people with the exact same tablet have the same issues as I did. 

[Povilas Staniulis]

As you are probably aware, Android x86 is an FOSS project, not a
commercial product, so do not expect commercial-grade support here.
People will respond if they have time to do so and if they have anything
to share with you.

Also, this project does not do device-specific builds. If you device
requires device specific modifications, you will probably have to do
them yourself.
All the source code is available, you are welcome to experiment and
submit patches.

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

[Povilas Staniulis]

Didn't notice that was an old post. Sorry. Do ignore this reply.

[Jordan Anderson]

I hear you, Povilas. Can you point me to the download link for the
Source code for the latest 64 bit version of 7.1?

[Povilas Staniulis]

There are instructions on the project's website on how to get and build
sources.
http://www.android-x86.org/getsourcecode

[Jordan Anderson]

No, I mean where to download the sources and all the files in a single
folder, so I can edit files and insert drivers for devices. The first
topic I see is talking about a build environment which I know nothing
about.
<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br />
<table style="border-top: 1px solid #D3D4DE;">
<tr>
<td style="width: 55px; padding-top: 13px;"><a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon"
target="_blank"><img
src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif"
alt="" width="46" height="29" style="width: 46px; height: 29px;"
/></a></td>
<td style="width: 470px; padding-top: 12px; color: #41424e;
font-size: 13px; font-family: Arial, Helvetica, sans-serif;
line-height: 18px;">Virus-free. <a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link"
target="_blank" style="color: #4453ea;">www.avast.com</a>
</td>
</tr>
</table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1"
height="1"></a></div>

> --
> 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/7eFbnVFixqA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> android-x86...@googlegroups.com.
> To post to this group, send email to andro...@googlegroups.com.

[Jordan Anderson]

You need ubuntu or other linux which I can't run on my tablet,<div

id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br />
<table style="border-top: 1px solid #D3D4DE;">
<tr>
<td style="width: 55px; padding-top: 13px;"><a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon"
target="_blank"><img
src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif"
alt="" width="46" height="29" style="width: 46px; height: 29px;"
/></a></td>
<td style="width: 470px; padding-top: 12px; color: #41424e;
font-size: 13px; font-family: Arial, Helvetica, sans-serif;
line-height: 18px;">Virus-free. <a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link"
target="_blank" style="color: #4453ea;">www.avast.com</a>
</td>
</tr>
</table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1"
height="1"></a></div>

[Mauro Rossi]

Here is how to change goodix.c driver to support GDIX1002

Thes user stavrakis in that blog said that adding entries after GDIX1001 ones should work.

http://chuwi-hi13-install-ubuntu.blogspot.it/2017/06/how-to-install-android-on-chuwi-hi13.html

Those changes are not even present in current master linux git

.../kernel$ cgrep GDIX100

./drivers/input/touchscreen/goodix.c:949: { "GDIX1001:00", 0 },

./drivers/input/touchscreen/goodix.c:956: { "GDIX1001", 0 },

In order to build nougat-x86 linux distro with at least 8 Gbytes of RAM is required.

M.

[Jon West]

I have had minimal success getting the cambrio to boot. it needs the grub flag i915.modeset=0 to even get to the bootanimation. so far my only tests have been with Oreo 8.1 versions though. I will besure to update here if I get anywhere.

[Jordan Anderson]

That sucks, at least you got it to work. It happened to me as well but
for 7.1, I didn't need to add the grub flag. It boots without a
problem.
I recommend 7.1 x64 but the only things not working are the
touchscreen, sound, and bluetooth. Other than that it works
flawlessly. I run it off a flash drive as a Live CD, as I choose to
keep Windows on it, and I clearly have no experience in dual
booting.<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br />

<table style="border-top: 1px solid #D3D4DE;">
<tr>
<td style="width: 55px; padding-top: 13px;"><a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon"
target="_blank"><img
src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif"
alt="" width="46" height="29" style="width: 46px; height: 29px;"
/></a></td>
<td style="width: 470px; padding-top: 12px; color: #41424e;
font-size: 13px; font-family: Arial, Helvetica, sans-serif;
line-height: 18px;">Virus-free. <a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link"
target="_blank" style="color: #4453ea;">www.avast.com</a>
</td>
</tr>
</table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1"
height="1"></a></div>

[Jordan Anderson]

Any help on adding a partition of Android-x86 besides windows on the same drive?
According to diskmgmt.msc my Windows drive has 3 partitions:
100MB Healthy(Efi system partition)
Windows C: 28.22GB NTFS Healthy (Boot, Page file, crash dump, Primary
partition.)
800MB Healthy (Recovery Partition)
I also have a 4GB microSD card (in the slot) that won't show up in the bios.

<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br />
<table style="border-top: 1px solid #D3D4DE;">
<tr>
<td style="width: 55px; padding-top: 13px;"><a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon"
target="_blank"><img
src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif"
alt="" width="46" height="29" style="width: 46px; height: 29px;"
/></a></td>
<td style="width: 470px; padding-top: 12px; color: #41424e;
font-size: 13px; font-family: Arial, Helvetica, sans-serif;
line-height: 18px;">Virus-free. <a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link"
target="_blank" style="color: #4453ea;">www.avast.com</a>
</td>
</tr>
</table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1"
height="1"></a></div>

[Jordan Anderson]

So I was able to dual boot android and Windows. First job was to download a root browser, specifically ES file manager from the play store, to find the files where the goodix drivers and what-not were located.

Only one I found was goodix.co.bak. Of course ES comes with a text editor. I used it to replace the 1 in GDIX1001 with a number 2, saved the file, exited, and restarted. Touchscreen still doesn't work. I went back in to add RCA W101SA23T1 after the model numbers it mentions. I saved again, restarted, and it still won't respond to touch.

I will look into the terminal emulator and see what lsusb says.

[Jon West]

I have had mostly success using my Cambrio W101SA23T1 as a Bliss OS test machine. The next release has just about everything working on it except for rotation and sound. Considering it's still a development release though, I think it's going well. https://forum.xda-developers.com/bliss-roms/bliss-roms-development/bliss-os-pie-beta-preview-t3855917

[Jordan Anderson]

That's awesome! Now we have to wait until they work on drivers and stuff.

On Tue, Nov 6, 2018, 8:44 PM Jon West <electr...@gmail.com wrote:

I have had mostly success using my Cambrio W101SA23T1 as a Bliss OS test machine. The next release has just about everything working on it except for rotation and sound. Considering it's still a development release though, I think it's going well. https://forum.xda-developers.com/bliss-roms/bliss-roms-development/bliss-os-pie-beta-preview-t3855917

--

[Jon West]

Silly, that they is me right now. 

[Kirn Gill]

I've got one of these tablets and I've got to tell you, I've never managed to get GUI (SurfaceFlinger?) to actually fully initialize. The initial text mode boot screen finds the boot drive, and then the whole screen flickers to black. 

This machine's an US$80 Walmart special (that's to say, it is basically junk), I don't expect any developer to ever specifically target it. 

Editing source code isn't something newbies can just do, it's not like tweaking settings. It involves creating the raw software commands to (in this case) send other commands to hardware. The specific "other commands" (hardware commands) may not be publicly documented, they may only be documented in Chinese, they may only be available if you pay more than the price of the tablet to the hardware manufacturer, etc. and you have to be exact in your handling of the hardware. The best case if you are not is a system crash. The worst case is you physically damage the hardware (using just software!) and ruin it. There's a reason people that write software drivers for a living rarely make less than US$100,000 per year. 

However! Do not give up hope! None of the hardware in this tablet is custom-made for this tablet; it's basically a collection of "common" components thrown together, and those components are all also found in various other computer models. As developers fix driver support for other machines using the same components, they will also simultaneously make small improvements to the software support for this machine.

While they're not particularly expensive, I also don't have $80 to spare on buying the Android-x86 developers their own unit, which would really be the best way to achieve support.