Test build 20130725 for Android-x86 4.3 (JB-x86)

[Frans van Berckel]

On the site, there's a article about today's test build 20130725 for Android-x86 4.3 ...

http://www.android-x86.org/releases/build-20130725

Anyone know where I can find the android-x86-4.3-20130725.iso called? Wanna do USB boot demo at tonight and being prepared, so asking.

Thanks,

Frans van Berckel

[Chih-Wei Huang]

2013/7/25 Frans van Berckel <fber...@xs4all.nl>:

Wow, you're impatient.

Now it's uploaded.


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

[Pedro Ivo Gama]

How to got root with this new kernel?
yours trully,
Pedro Ivo

[Greg McGee]

Impatience has it's rewards.

_Everything_ works for me on my Lenovo X200 tablet, including BT and SLEEP.

(Fn (by itself) puts it so sleeep, but it will wake up, whcih is a huge win)

Looking forwards to trying it untethered for the first time as an Android tablet...

All I had to do manually was add in inputattach for the Wacom pen and edit init.sh to load it with the right args.

. (would a patch to add inputattach to the repo be OK?)

Profuse props to all the devs!

[Chih-Wei Huang]

2013/7/26 Greg McGee <gjm...@gmail.com>:

> Impatience has it's rewards.
>
> _Everything_ works for me on my Lenovo X200 tablet, including BT and SLEEP.
> (Fn (by itself) puts it so sleeep, but it will wake up, whcih is a huge win)
> Looking forwards to trying it untethered for the first time as an Android
> tablet...
>
> All I had to do manually was add in inputattach for the Wacom pen and edit
> init.sh to load it with the right args.
> . (would a patch to add inputattach to the repo be OK?)

You may send me a patch for it
so I can add it in next release.
Thanks!

[Greg McGee]

Here is a "simple" tarball (with binary, src and modified /etc/init.sh)
It works on early wacom pen only machines another lister made some
changes to this to get it working on pen+ touch units.

src upstream came from linux-input project latest version.
Needed minor baudrate change to work

> --
> 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/MD2nfT_tUYI/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.
> Visit this group at http://groups.google.com/group/android-x86.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Greg McGee]

Will post up git diff once repo sync starts working again.

[Frans van Berckel]

On Thursday, July 25, 2013 10:27:25 PM UTC+2, Chih-Wei Huang wrote:

Wow, you're impatient.

Now it's uploaded.

Good to know, I am not that bad :-) Thanks for supporting 4.3 ...

Frans van Berckel

[austin pinto]

are the arm libs added?

> --
> 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/groups/opt_out.
>
>
>

--
surch for me on facebook, google+, orkut..
austinpin...@gmail.com
follow me on twitter.
austinmpinto
contact me on skype.
austin.pinto3

[austin pinto]

hi all i red the artical and im glad to know that arm translater is
supported this means i can install arm apps without adding any lib
files?.

also i will be installing this to my external hard drive so are the
any changes in the way it needs to be installed?

and the last time i had tested android 4.2 build by installing it to
external hard drive the grub boot loader got installed to the internal
hard drive i think is there any way to tel the installer in which hard
drive should the grub boot loader be installed?

[Stefan Svensson]

Is there no root access?

I tried to install EXT2 and EXT3 but still no luck...

[Greg McGee]

alt+F1... and install superuser, it's not included in the build.

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

[Greg McGee]

Just realized I have been installing to an existing partition I only use for android, ext3.

You may want to install a linux distro to make managing android easy.

(makes building possible as well, use x64)

[Frans van Berckel]

> Just realized I have been installing to an existing partition I only use
> for android, ext3.
>
> You may want to install a linux distro to make managing android easy.
> (makes building possible as well, use x64)

Like they do in "How to run Debian GNU/Linux on your Android?"

http://whiteboard.ping.se/Android/Debian ...

Sure others will do it as well.

Frans van Berckel

> On Friday, July 26, 2013 6:24:24 AM UTC-5, Stefan Svensson wrote:
>>
>> Is there no root access?
>> I tried to install EXT2 and EXT3 but still no luck...
>>
>

[Pedro Ivo Gama]

Tried without sucess to root manually - using GingerBreak method in Alt + F1 in Iconia w500.
Waiting this to be patched in the final version of de iso file.
Pedro Ivo

[Stefan Svensson]

How do I make the kernel?
The command "make kernel PRODUCT_TARGET=generic_x86" don't work! Get error:
"grep: kernel/arch/arm/configs/goldfish_defconfig: file not found...."

Uh....?

[Greg McGee]

Well, actually the installer generates a new dir for each install by default.

There is no need to reformat or reinstall grub, although I had to install grub to the partition manually.

It could just as easily be installed in the root of a std linux distro or any other partition for that matter, as each release is essentially self contained.

android-x86 partition looks like:

/android-x86-4.2-test

/android-x86-4.3-test

/grub

/lost+found

I just keep installing to the same partition w/o reformatting, preserves /grub so that all I have to do is update the install dir name to /grub/menu.lst and I'm done.

/grub contains the std android installed contents, but moved to a partition, I call it from another instance of grub..

grub has ~no issues installing to a partition, unlike grub2.

[Greg McGee]

"grub has ~no issues installing to a partition, unlike grub2."

BUT--- the android installer will NOT do this out of the box, you must skip installing grub and do it manually.

[austin pinto]

how do i install grub manually? i dont know anything of the grub cause
ive never used any linux distros and what about apps made for arm
processers as i have red this iso supports arm translater so will the
apps work without adding any libs or so to the installation?

[Ankur Arora]

ok
the best and simplest method is ... 

1 create partition for android preferably ext3

2 install android with grub(inbuilt)

3 add entry of windows to it

4 run windows

5 install easy bcd

6 use some ext3 partition reader and get the menu list file from grub folder in your ext3/android partion

7 copy the contents of menu list of grub and then open easy bcd

8 in easy bcd , go to backup and restore and click repair

9 click "add new entry of neogrub" in easybcd and in the menu list(settings) of neogrub, paste contents you copied earlier

10 then tada, its done

PS open menu list in notepad or some other software like notepad

the problem i faced with grub(inbuilt) was that i was not able to boot windows 8 and windows 7 and android(i have triple boot) ... only windows 7 and android were available by inbulit grub

but by above method grub is not your boot loader and now the default bootloader can boot anything, linux, windows etc.. first the deafault bootloader is loaded and then neogrub is loaded   

also it helps in faster booing of my windows 8, cuz its default

[Chih-Wei Huang]

2013/7/26 Greg McGee <gjm...@gmail.com>:

> Here is a "simple" tarball (with binary, src and modified /etc/init.sh)
> It works on early wacom pen only machines another lister made some
> changes to this to get it working on pen+ touch units.

I've checked it.
It's not hard to integrate it.
The problem is in your init.sh it's hardcoded
to run inputattach. It's not good.
Please change it to be detected
by dmi id or some better ways.
You may check other init_* functions as examples.
(or show me the /sys/class/dmi/id/product_name
and /sys/class/dmi/id/uevent)

Besides, modprobe ftdi_sio is probably redundant
as you commented. It should be loaded by ueventd.
Please check if this line can be removed.

> src upstream came from linux-input project latest version.
> Needed minor baudrate change to work

Is there an upstream git repo?

[Alexey Seredkin]

When playing music or video, the sound raucous and slows. android 4.3

[Greg McGee]

The Wacom "tablets" used are meatspace serial devices, AFAIK the only way to detect them is by poking at them.

What I posted will probably only work for the pen-only and getting the pen working on the pen+ touch units.

I only have an early version, but there hopefully is an elegant way to tell which one you have and select the right baud rate.

Pen-only must run at a slower baud rate than the later ones, and the pen+touch setups require additional work beyond what I posted.

(this is done via udev rules on normal Linux distros)

I'll comment out the modprobe for ftdi_sio and see if it autoloads this evening.

[Greg McGee]

You can actually install grub manually from the install CD, but you probably want to read a few how-tos.

The problem is ... the installer will only install grub to the mbr (of sda or such) rather than the partition.

It will install a /grub dir on the partition that contains menu.lst, which is the config file for grub...

it will needed edited for each installation.

(on later installations, don't reformat and skip grub install)

So, you must back up your mbr and have a way to restore it.

You can actually also install grub to the partition using the proper commands in grub...

(not posting here as i don't want to be responsible for hosing your machine, Google is thy friend, and only practice makes perfect)

IMHO the easiest way to do that is to install a proper linux distro and set up a partition for android-x86 at the same time.

This gives you a place to put your backed up MBRs and such.

One can also do all the setup and management from a live CD or USB like Mageia or Knoppix, but you still have to learn how it's done.

 

I'm a fan on Mageia, KDE4. if you ~like Win7 you'd love KDE4 integrated properly.

Has nice system management tools.

If you like Debian i suggest MINT.

It's like Ubuntu with the braindamage removed.

[Andrew]

Im sorry but could someone please explain how to use the input attach tar file? Ive done android on my X41, X61 tablets and had great success. On my x200 tablet everything works but the pen. So Im assuming this is the solution for the pen. Im familiar with installing android via 'unetbootin', and have had to do a "SDCARD=/dev/MMCBLK0" on my X41T to get the SD card to work. Could someone please explain the input attach thing a little better? Greatly appreciated. *_*

[Greg McGee]

The tarfile contains the source to add to your build tree, and also the executable.

Once installed to HDD, copy the exe to somewhere in your path (xbin/) and then you need to launch it on statup, adding a line to /etc/init.sh IIRC.

add the following to /etc/init.sh:

inputattach --daemon --baud 19200 --w8001 /dev/ttyS0

On Sat, Oct 19, 2013 at 7:21 PM, Andrew <andre...@gmail.com> wrote:

Im sorry but could someone please explain how to use the input attach tar file? Ive done android on my X41, X61 tablets and had great success. On my x200 tablet everything works but the pen. So Im assuming this is the solution for the pen. Im familiar with installing android via 'unetbootin', and have had to do a "SDCARD=/dev/MMCBLK0" on my X41T to get the SD card to work. Could someone please explain the input attach thing a little better? Greatly appreciated. *_*

--

[Greg McGee]

OK, the line that needed added to init.sh got eaten by bitworm.

add the following to /etc/init.sh:(I put it in the misc section)

inputattach --daemon --baud 19200 --w8001 /dev/ttyS0

That works on my X200T, it you have a pen on a std X200 the device may be different.

There is also a slim chance you have pen+touch, some variation will be needed for that.

[Andrew Jewett]

Sorry for my ignorance and thank you for getting back to me. I honestly dont know what your saying. My experience with android and all these commands are limited. I have experience w/ putting android on my X41T, X61T, using unetbootin and booting from the usb drives for install. On my X41T i used to have to type 'a' at the android screen to then type "SDCARD=MMCBLK0" or something to get the SD card slot to work.

I used a 'universal' build last night (X200T) and everything works but screen rotation is quirky (not right) and doesnt always connect to wifi. The pen works but its slightly off (the pen does not line up with where your clicking.) I did not have this issue on my X41T or X61T. and Im assuming cause its widescreen? Not 4:3 ratio?

Android 4.2, 4.3 work good but theres no pen responce at all. Ive downloaded an 'inputattach' and 'input-wacomi686pkg.tar' file but dont know what to do with them.

So i have no idea what to do. I do not think my X200T is touch (just pen).

I was thinking being the pen does not "align-up" with where your touching the screen, then maybe cause the screens ratio difference. So I googled and found how to type VGA=ASK and it brings up a list of compatable modes but dont know what to type (ie. 8 319, ??

Do you think I would be better off using the later 4.2 or 4.3 versions and doing something later to get the pen to work or use an older 4.0 and try to calibrate the pen somehow?

Thank You. Build Tree, line added to init.sh, add the following , copy to somewhere, etc. Im not sure what all that means, but I have an idea kind of, just need more explaining. Thank You.

On Wed, Oct 23, 2013 at 5:15 PM, Greg McGee <gjm...@gmail.com> wrote:

OK, the line that needed added to init.sh got eaten by bitworm.

add the following to /etc/init.sh:(I put it in the misc section)

inputattach --daemon --baud 19200 --w8001 /dev/ttyS0

That works on my X200T, it you have a pen on a std X200 the device may be different.

There is also a slim chance you have pen+touch, some variation will be needed for that.

On Wed, Oct 23, 2013 at 3:32 PM, Greg McGee <gjm...@gmail.com> wrote:

The tar=file contains the source to add to your build tree, and also the executable.

Once installed to HDD, copy the exe to somewhere in your path (xbin/) and then you need to launch it on statup, adding a line to /etc/init.sh IIRC.

add the following to /etc/init.sh:

inputattach --daemon --baud 19200 --w8001 /dev/ttyS0

On Sat, Oct 19, 2013 at 7:21 PM, Andrew <andre...@gmail.com> wrote:

Im sorry but could someone please explain how to use the input attach tar file? Ive done android on my X41, X61 tablets and had great success. On my x200 tablet everything works but the pen. So Im assuming this is the solution for the pen. Im familiar with installing android via 'unetbootin', and have had to do a "SDCARD=/dev/MMCBLK0" on my X41T to get the SD card to work. Could someone please explain the input attach thing a little better? Greatly appreciated. *_*

--
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/MD2nfT_tUYI/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.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/groups/opt_out.

[Greg McGee]

OK, I'll try again.

The tarfile contains the exe.

Copy the inputattach exe to /system/bin or /system/xbin.

Then, add the line " inputattach --daemon --baud 19200 --w8001 /dev/ttyS0" to /etc/init.sh using vi or such.

The easiest way to deal with this stuff is if you have a real Linux distro installed alongside Android.

They can share the same partition as long as you provide room: Android has it's own directory tree that does not stomp on Linux and vice versa. (a /grub directory is nonstd on "normal" Linuxii, it typically goes in /boot/grub for example)

The source was provided so you could add inputattach to your own Android build tree, as I'm not sure it's made it into the repo... I can say it does not like 64 bit kernels for some unknown reason.