Re: Running Android-x86-4.0-RC2 on Dell Latitude 2100 - WiFi or Touchscreen but not both

619 views
Skip to first unread message

fgdn17

unread,
Oct 4, 2012, 12:26:52 AM10/4/12
to andro...@googlegroups.com
check builds from:

   http://www.tabletsx86.org & http://android-x86.sceners.org/en/



On Wednesday, October 3, 2012 10:43:08 PM UTC-4, Barnaby Jeans wrote:
I'm trying to get Android-x86-4.0-RC2 running on a Dell Latitude 2100 Netbook (http://www.dell.com/us/business/p/latitude-2100/pd#TechSpec) and have had varying levels of success with the asus_laptop and eeepc builds.
 
With the asus_laptop build I'm able to connect to WiFi and the sounds works however the touchscreen on the 2100 doesn't work. 
With the eeepc build the touchscreen works however the WiFi doesn't.
 
Is there a way to get a build that includes the WiFi support from the asus_laptop build and the touchscreen support from the eeepc build.
 
I'm trying to extend the life of this little netbook and give it to the kids, however, without network it is a little harder to get applications installed.
 
I'm happy to try to create my own build but could use some pointers on how to get started and the modules that I should be looking at including.
 
If there are any logs that might help let me know where to find.
 
thanks,
Barnaby

Christopher Price

unread,
Oct 4, 2012, 1:44:30 AM10/4/12
to andro...@googlegroups.com
The good news is, you have everything working between the two builds.

Probably the easiest way to isolate is to compare the two Android build .mk files between the two device targets. A simple diff will reveal what is being used in terms of drivers on each default build, which should give you a good overview of where to start tinkering.

fgdn17

unread,
Oct 4, 2012, 10:42:37 AM10/4/12
to andro...@googlegroups.com
unfortunately that won't tell you very much...

however checking the diff between the defconfig for each target will

Christopher Price

unread,
Oct 4, 2012, 10:53:25 AM10/4/12
to andro...@googlegroups.com
Right, I was referring to both config files. They'll define what drivers are called up.

Probably the best "first step" would be to compile a generic Android-x86 build. After that, it gets pretty easy to figure out how to adapt, and even make your own build targets. Hey, if Intel can do it, I think anyone can ;)

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To view this discussion on the web visit https://groups.google.com/d/msg/android-x86/-/seDbC-ICyl0J.
To post to this group, send email to andro...@googlegroups.com.
To unsubscribe from this group, send email to android-x86...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

Reply all
Reply to author
Forward
0 new messages