jb-x86 source is ready

2,182 views
Skip to first unread message

Chih-Wei Huang

unread,
Jan 16, 2013, 6:02:54 AM1/16/13
to Android-x86
Hi,
I've pushed all jb-x86 branches to our main git server.
As usual, you can get it by

repo init -u http://git.android-x86.org/manifest -b jb-x86
repo sync

You will note there is only one target, android_x86.
This is the first step of the plan to create a universal image.
Though it's still far from complete.
I'll describe more details later.

SourceForge mirror is not synced yet.
Will try to do it when I have time.

--
Chih-Wei
Android-x86 project
http://www.android-x86.org
Message has been deleted

dscm

unread,
Jan 16, 2013, 2:33:02 PM1/16/13
to Android-x86
thanks Chih-Wei.....

a test build is available here:

http://www.tabletsx86.org/

select android-x86.org builds

On Jan 16, 6:02 am, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> Hi,
> I've pushed all jb-x86 branches to our main git server.
> As usual, you can get it by
>
> repo init -uhttp://git.android-x86.org/manifest-b jb-x86
Message has been deleted

Greg McGee

unread,
Jan 17, 2013, 4:31:30 AM1/17/13
to andro...@googlegroups.com
Looking forward to the sourceforge sync, I've had no luck syncing with the other server.

JPT

unread,
Jan 17, 2013, 12:10:44 PM1/17/13
to andro...@googlegroups.com
hi,
your Iso hasn't got a partition table. dd to USB thumb drive doesn't work.
Could you please have a look?

Is this a change in the jb build? Is it a problem of your builds? Strange...

thanks,

JPT
Message has been deleted

dscm

unread,
Jan 17, 2013, 12:56:41 PM1/17/13
to Android-x86
you can check your process here:

http://www.android-x86.org/getsourcecode in the testing and
advanced section

we simple check using newer tools available to do the job...ie:
unetbootin and that works...
on both windows and linux systems...there are others I'm sure...

your free to contribute other methods that work and/or are not
supported...

not speaking for android-x86.org just my own opinion

Gerhard Smith

unread,
Jan 17, 2013, 2:18:15 PM1/17/13
to andro...@googlegroups.com
I am trying to build a different device, but I am having problems when compiling:
wakelock.h is not in the tree but is required by gpio_matrix.c
I cannot work out what requires gpio_matrix, but it seems like it is a problem in any event.
Any advice appreciated.

Note: I can compile android_x86 without a problem

Nahkju Jeong

unread,
Jan 17, 2013, 7:42:12 PM1/17/13
to andro...@googlegroups.com
I'm installed your iso on Virtual Box.
Angry birds, Chrome is not working on virtualbox.
Display is not shown.
Because hardware opengl does not working, this programs do not working.
Any solution?

2013년 1월 17일 목요일 오전 4시 33분 2초 UTC+9, dscm 님의 말:

Gerhard Smith

unread,
Jan 18, 2013, 6:03:58 AM1/18/13
to andro...@googlegroups.com
@Igor:
I have managed to get the compile to work - thanks for your response in any event
HOWEVER
wakelock is very much part of Android ( There are several complaints on the internet about bad use of it draining batteries on jellybean), so it would seem that wakelock.h should very much be part of the build.
Also by getting rid of the error by disabling GPIO will make several device drivers not work if they use GPIO.

Gerhard Smith

unread,
Jan 18, 2013, 6:08:44 AM1/18/13
to andro...@googlegroups.com
@Nahkju Jeong

This thread is not for testing jb, it is the source release and report build errors here - please find correct thread



Message has been deleted

dscm

unread,
Jan 18, 2013, 7:47:07 PM1/18/13
to Android-x86
jb-x86 branch has successfully been built on newer versions of Ubuntu,
versions 12.04.1 / 12.10 / 13.04

install build instructions available @

http://www.tabletsx86.org/

Fai Wong

unread,
Jan 19, 2013, 1:54:32 AM1/19/13
to andro...@googlegroups.com
After building with lunch and make, some image files are in
out/target/product/generic_x86/, including ramdisk.img, system.img and
userdata.img, how to build a bootable USB image or ISO?


2013/1/19 dscm <rbg.hp...@gmail.com>:
> --
> You received this message because you are subscribed to the Google Groups "Android-x86" group.
> 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.
>

Gerhard Smith

unread,
Jan 19, 2013, 8:33:08 AM1/19/13
to andro...@googlegroups.com
It looks like your TARGET_PRODUCT is incorrect:
make -jx TARGET_PRODUCT=android_x86  (Note the underscore rather than a dash) where x=number of CPUs

Gerhard Smith

unread,
Jan 19, 2013, 11:04:07 AM1/19/13
to andro...@googlegroups.com
The source tree does not support x86-atom even though there is support for all the ARM CPUs (which is not relevant here).
The first manifestation of this is compiling the Dalvik VM.

Fai Wong

unread,
Jan 19, 2013, 9:09:56 PM1/19/13
to andro...@googlegroups.com
I got this when use make.


including device/asus/grouper/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/moto/wingray/vendorsetup.sh
including device/samsung/crespo/vendorsetup.sh
including device/samsung/maguro/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including sdk/bash_completion/adb.bash
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.1
TARGET_PRODUCT=full_x86
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=x86
TARGET_ARCH_VARIANT=x86-atom
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.2.0-36-generic-x86_64-with-Ubuntu-12.04-precise
HOST_BUILD_TYPE=release
BUILD_ID=JRO03C
OUT_DIR=out
============================================

build/core/product_config.mk:205: *** No matches for product
"android_x86". Stop.


2013/1/19 Gerhard Smith <ger...@android-x86.org>:
> TARGET_PRODUCT=android_x86

dscm

unread,
Jan 19, 2013, 11:15:41 PM1/19/13
to Android-x86
PLATFORM_VERSION=4.1.1

???? your obviously not trying to get the correct product...

repo init -u http://git.android-x86.org/manifest -b jb-x86
repo sync

Lunch menu... pick a combo:
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. full_mips-eng
5. android_x86-eng
6. android_x86-userdebug
7. android_x86-user

and

PLATFORM_VERSION=4.2.1

when building
> 2013/1/19 Gerhard Smith <gerh...@android-x86.org>:
>
>
>
>
>
>
>
> > TARGET_PRODUCT=android_x86

JPT

unread,
Jan 20, 2013, 4:00:45 PM1/20/13
to andro...@googlegroups.com
Hi,

I tried to compile 4.2, but it fails.
I updated my old 4.0 repo to 4.2 by deleting everything except .repo, then repo init and sync.

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.2.1 
TARGET_PRODUCT=android_x86
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=x86
TARGET_ARCH_VARIANT=x86
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.0.0-30-generic-x86_64-with-Ubuntu-11.10-oneiric
HOST_BUILD_TYPE=release
BUILD_ID=JOP40D
OUT_DIR=out
============================================
(a lot of lines like this:)
find: "opengl/java": File not found

(a lot of lines like this:)
PRODUCT_COPY_FILES frameworks/base/data/sounds/effects/ogg/Effect_Tick.ogg:system/media/audio/ui/Effect_Tick.ogg ignored.

make: *** Keine Regel vorhanden, um das Target »out/host/linux-x86/bin/aapt«,
  benötigt von »out/target/common/obj/APPS/AndroidTerm_intermediates/src/R.stamp«, zu erstellen.  Schluss.


Igor V

unread,
Jan 20, 2013, 4:46:21 PM1/20/13
to andro...@googlegroups.com
Did you change the target from ics-x86 to jb-x86? (repo init -u http://git.android-x86.org/manifest -b jb-x86)
Also try to upgrade linux version. I successfully compiled it using Ubuntu 12.10 (gcc 4.7)

Fai Wong

unread,
Jan 20, 2013, 10:06:40 PM1/20/13
to andro...@googlegroups.com
Reinit the repo and building.
But "system/extras/ext4_utils/mkuserimg.sh" has a small problem, it
can't determine the correct size of userdata.img, it tries to create
1M userdata.img, and lead to not enough space and got error, I fixed
the SIZE to say 100M and it seems to be working now.

++ du -sm out/target/product/x86/data
++ cut -f1
+ SIZE=1M
+ '[' -n '' ']'
+ MAKE_EXT4FS_CMD='make_ext4fs -l 1M -a data
out/target/product/x86/userdata.img out/target/product/x86/data'
+ echo make_ext4fs -l 1M -a data out/target/product/x86/userdata.img
out/target/product/x86/data
make_ext4fs -l 1M -a data out/target/product/x86/userdata.img
out/target/product/x86/data
+ make_ext4fs -l 1M -a data out/target/product/x86/userdata.img
out/target/product/x86/data
error: do_inode_allocate_extents: Failed to allocate 1025 blocks



2013/1/19 Gerhard Smith <ger...@android-x86.org>:
> To view this discussion on the web visit
> https://groups.google.com/d/msg/android-x86/-/qd0L7868Mu0J.

Chih-Wei Huang

unread,
Jan 20, 2013, 10:51:17 PM1/20/13
to andro...@googlegroups.com
2013/1/21 Fai Wong <laz...@gmail.com>:
> Reinit the repo and building.
> But "system/extras/ext4_utils/mkuserimg.sh" has a small problem, it
> can't determine the correct size of userdata.img, it tries to create
> 1M userdata.img, and lead to not enough space and got error, I fixed
> the SIZE to say 100M and it seems to be working now.
>
> ++ du -sm out/target/product/x86/data
> ++ cut -f1
> + SIZE=1M
> + '[' -n '' ']'
> + MAKE_EXT4FS_CMD='make_ext4fs -l 1M -a data
> out/target/product/x86/userdata.img out/target/product/x86/data'
> + echo make_ext4fs -l 1M -a data out/target/product/x86/userdata.img
> out/target/product/x86/data
> make_ext4fs -l 1M -a data out/target/product/x86/userdata.img
> out/target/product/x86/data
> + make_ext4fs -l 1M -a data out/target/product/x86/userdata.img
> out/target/product/x86/data
> error: do_inode_allocate_extents: Failed to allocate 1025 blocks

I sometimes encountered a similar problem.
Usually just re-make again can fix it.

Chih-Wei Huang

unread,
Jan 20, 2013, 10:53:20 PM1/20/13
to andro...@googlegroups.com
BTW, make sure you are making the iso_img goal.
It won't need to build userdata.img

m -jX iso_img


2013/1/21 Chih-Wei Huang <cwh...@android-x86.org>:
> 2013/1/21 Fai Wong <laz...@gmail.com>:
>> Reinit the repo and building.
>> But "system/extras/ext4_utils/mkuserimg.sh" has a small problem, it
>> can't determine the correct size of userdata.img, it tries to create
>> 1M userdata.img, and lead to not enough space and got error, I fixed
>> the SIZE to say 100M and it seems to be working now.
>>
>> ++ du -sm out/target/product/x86/data
>> ++ cut -f1
>> + SIZE=1M
>> + '[' -n '' ']'
>> + MAKE_EXT4FS_CMD='make_ext4fs -l 1M -a data
>> out/target/product/x86/userdata.img out/target/product/x86/data'
>> + echo make_ext4fs -l 1M -a data out/target/product/x86/userdata.img
>> out/target/product/x86/data
>> make_ext4fs -l 1M -a data out/target/product/x86/userdata.img
>> out/target/product/x86/data
>> + make_ext4fs -l 1M -a data out/target/product/x86/userdata.img
>> out/target/product/x86/data
>> error: do_inode_allocate_extents: Failed to allocate 1025 blocks

Fai Wong

unread,
Jan 20, 2013, 11:29:41 PM1/20/13
to andro...@googlegroups.com
When using m -j2 iso_img, it complains about missing
"out/target/product/generic_x86"
/bin/sh: 1: cd: can't cd to
/workspace/jenkins/android-x86/out/target/product/generic_x86/obj/kernel
but it works when I use make TARGET_PRODUCT=android_x86 as suggested
by someone before, it will use "out/target/product/x86" instead, which
has the required directories like kernel there.

What is the correct steps for configure and build JB-x86?
1) . build/envsetup.sh
2) lunch full_x86-eng
3a) make -j2 TARGET_PRODUCT=android_x86 <-- no ISO built, only
system.img data.img kernel
3b) m -j2 iso_img <-- cannot find generic_x86 in out/target/product,
failed to build



2013/1/21 Chih-Wei Huang <cwh...@android-x86.org>:

Chih-Wei Huang

unread,
Jan 20, 2013, 11:35:30 PM1/20/13
to andro...@googlegroups.com
2013/1/21 Fai Wong <laz...@gmail.com>:
> When using m -j2 iso_img, it complains about missing
> "out/target/product/generic_x86"
> /bin/sh: 1: cd: can't cd to
> /workspace/jenkins/android-x86/out/target/product/generic_x86/obj/kernel
> but it works when I use make TARGET_PRODUCT=android_x86 as suggested
> by someone before, it will use "out/target/product/x86" instead, which
> has the required directories like kernel there.
>
> What is the correct steps for configure and build JB-x86?
> 1) . build/envsetup.sh
> 2) lunch full_x86-eng

lunch android_x8-eng (or userdebug, user)

full_x86 is the original AOSP target.
It maybe not workable or buildable.
Probably I should remove it later.

> 3a) make -j2 TARGET_PRODUCT=android_x86 <-- no ISO built, only
> system.img data.img kernel

m -j2 iso_img TARGET_PRODUCT=android_x86

(with this command you can skip the lunch step)

> 3b) m -j2 iso_img <-- cannot find generic_x86 in out/target/product,
> failed to build

This is ok. The problem is you lunch the wrong target.

Fai Wong

unread,
Jan 21, 2013, 1:32:56 AM1/21/13
to andro...@googlegroups.com
Thanks, I got my ISO built sucessfully now! I also setup my jenkins
server to regular build it from git. :-)

2013/1/21 Chih-Wei Huang <cwh...@android-x86.org>:

JPT

unread,
Jan 21, 2013, 4:43:59 AM1/21/13
to andro...@googlegroups.com
I found a typo in device/generic/x86/overlay/frameworks/base/core/res/res/values/config.xml

    <string-array translatable="false" name="networkAttributes">
...
        <item>"ethernet,9,9,1,-1,ture"</item>
should be true instead of ture


Chih-Wei Huang

unread,
Jan 21, 2013, 5:07:19 AM1/21/13
to andro...@googlegroups.com
2013/1/21 JPT <jpt.n...@gmail.com>:
OOPS! Good catching.
Now corrected. Thanks a lot!

Gerhard Smith

unread,
Jan 21, 2013, 6:15:19 AM1/21/13
to andro...@googlegroups.com
Where can I get the INTERP files for ATOM for jellybean (required by DALVIK VM)?
Can I just copy the files from ICS -  I had a look but it seems like that part of jb has been reworked.

aLexzkter

unread,
Jan 21, 2013, 10:26:46 AM1/21/13
to andro...@googlegroups.com
Tried the latest jb iso on my Samsung NC10, and it's working really nice.
Except for...the fact the Play Store is not installed by default, and once installed when I try to open it closes by itself instantantly.
I guess something was disabled.

As for the brightness control, it doesn't work either, as in the ICS releases.







tsukishiro yamazaki

unread,
Jan 21, 2013, 9:40:45 PM1/21/13
to andro...@googlegroups.com
JB-x86! As always, Chih-Wei, you're the best!

Btw, I just tried building and I got a few warnings and 1 error.
As a short background, here is the initial output from my make command ("make -j16 iso_img")
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.2.1
TARGET_PRODUCT=android_x86
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=x86
TARGET_ARCH_VARIANT=x86
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.2.0-29-generic-x86_64-with-Ubuntu-12.04-precise
HOST_BUILD_TYPE=release
BUILD_ID=JOP40D
OUT_DIR=out
============================================

Below are 6 warnings and 1 error that I got just when the build was about to finish
Install: out/target/product/x86/system/app/VisualizationWallpapers.odex
Install: out/target/product/x86/system/app/VisualizationWallpapers.apk
 'out/target/common/obj/APPS/Mms_intermediates/classes.dex' as 'classes.dex'...
  adding: lib/ (stored 0%)
  adding: lib/x86/ (stored 0%)
  adding: lib/x86/libWnnJpnDic.so (deflated 37%)
  adding: lib/x86/libWnnEngDic.soout/target/common/obj/JAVA_LIBRARIES/android_stubs_current_intermediates/src/android/telephony/gsm/SmsManager.java:3: modifier static not allowed here
public static class SmsManager
              ^
 (deflated 40%)
  adding: lib/x86/libwnndict.so (deflated 52%)
Warning: AndroidManifest.xml already defines versionCode (in http://schemas.android.com/apk/res/android); using existing value in manifest.
Warning: AndroidManifest.xml already defines versionName (in http://schemas.android.com/apk/res/android); using existing value in manifest.
Warning: AndroidManifest.xml already defines minSdkVersion (in http://schemas.android.com/apk/res/android); using existing value in manifest.
 'out/target/common/obj/APPS/OpenWnn_intermediates/classes.dex' as 'classes.dex'...
Processing target/product/x86/obj/APPS/Mms_intermediates/package.apk
 'out/target/common/obj/APPS/VideoEditor_intermediates/classes.dex' as 'classes.dex'...
Done!
Install: out/target/product/x86/system/app/Mms.odex
Install: out/target/product/x86/system/app/Mms.apk
target Symbolic: libwebcore (out/target/product/x86/symbols/system/lib/libwebcore.so)
Processing target/product/x86/obj/APPS/VideoEditor_intermediates/package.apk
Processing target/product/x86/obj/APPS/OpenWnn_intermediates/package.apk
out/target/common/obj/JAVA_LIBRARIES/android_stubs_current_intermediates/src/java/util/concurrent/ScheduledThreadPoolExecutor.java:6: warning: [unchecked] unchecked conversion
found   : java.util.concurrent.BlockingQueue
required: java.util.concurrent.BlockingQueue<java.lang.Runnable>
public  ScheduledThreadPoolExecutor(int corePoolSize) { super(0,0,0,(java.util.concurrent.TimeUnit)null,(java.util.concurrent.BlockingQueue)null,(java.util.concurrent.ThreadFactory)null,(java.util.concurrent.RejectedExecutionHandler)null); throw new RuntimeException("Stub!"); }
                                                                                                        ^
out/target/common/obj/JAVA_LIBRARIES/android_stubs_current_intermediates/src/java/util/concurrent/ScheduledThreadPoolExecutor.java:7: warning: [unchecked] unchecked conversion
found   : java.util.concurrent.BlockingQueue
required: java.util.concurrent.BlockingQueue<java.lang.Runnable>
public  ScheduledThreadPoolExecutor(int corePoolSize, java.util.concurrent.ThreadFactory threadFactory) { super(0,0,0,(java.util.concurrent.TimeUnit)null,(java.util.concurrent.BlockingQueue)null,(java.util.concurrent.ThreadFactory)null,(java.util.concurrent.RejectedExecutionHandler)null); throw new RuntimeException("Stub!"); }
                                                                                                                                                          ^
out/target/common/obj/JAVA_LIBRARIES/android_stubs_current_intermediates/src/java/util/concurrent/ScheduledThreadPoolExecutor.java:8: warning: [unchecked] unchecked conversion
found   : java.util.concurrent.BlockingQueue
required: java.util.concurrent.BlockingQueue<java.lang.Runnable>
public  ScheduledThreadPoolExecutor(int corePoolSize, java.util.concurrent.RejectedExecutionHandler handler) { super(0,0,0,(java.util.concurrent.TimeUnit)null,(java.util.concurrent.BlockingQueue)null,(java.util.concurrent.ThreadFactory)null,(java.util.concurrent.RejectedExecutionHandler)null); throw new RuntimeException("Stub!"); }
                                                                                                                                                               ^
out/target/common/obj/JAVA_LIBRARIES/android_stubs_current_intermediates/src/java/util/concurrent/ScheduledThreadPoolExecutor.java:9: warning: [unchecked] unchecked conversion
found   : java.util.concurrent.BlockingQueue
required: java.util.concurrent.BlockingQueue<java.lang.Runnable>
public  ScheduledThreadPoolExecutor(int corePoolSize, java.util.concurrent.ThreadFactory threadFactory, java.util.concurrent.RejectedExecutionHandler handler) { super(0,0,0,(java.util.concurrent.TimeUnit)null,(java.util.concurrent.BlockingQueue)null,(java.util.concurrent.ThreadFactory)null,(java.util.concurrent.RejectedExecutionHandler)null); throw new RuntimeException("Stub!"); }
                                                                                                                                                                                                                 ^
out/target/common/obj/JAVA_LIBRARIES/android_stubs_current_intermediates/src/java/security/cert/PKIXBuilderParameters.java:5: warning: [unchecked] unchecked conversion
found   : java.util.Set
required: java.util.Set<java.security.cert.TrustAnchor>
public  PKIXBuilderParameters(java.util.Set<java.security.cert.TrustAnchor> trustAnchors, java.security.cert.CertSelector targetConstraints) throws java.security.InvalidAlgorithmParameterException { super((java.util.Set)null); throw new RuntimeException("Stub!"); }
                                                                                                                                                                                                             ^
out/target/common/obj/JAVA_LIBRARIES/android_stubs_current_intermediates/src/org/apache/http/impl/conn/tsccm/BasicPoolEntryRef.java:5: warning: [unchecked] unchecked conversion
found   : java.lang.ref.ReferenceQueue
required: java.lang.ref.ReferenceQueue<? super org.apache.http.impl.conn.tsccm.BasicPoolEntry>
public  BasicPoolEntryRef(org.apache.http.impl.conn.tsccm.BasicPoolEntry entry, java.lang.ref.ReferenceQueue<java.lang.Object> queue) { super(null,(java.lang.ref.ReferenceQueue)null); throw new RuntimeException("Stub!"); }
                                                                                                                                                   ^
target Strip: libwebcore (out/target/product/x86/obj/lib/libwebcore.so)
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
1 error
6 warnings
 'out/target/common/obj/APPS/Phone_intermediates/classes.dex' as 'classes.dex'...
make: *** [out/target/common/obj/JAVA_LIBRARIES/android_stubs_current_intermediates/classes.jar] Error 41
make: *** Waiting for unfinished jobs....

How do I resolve the error?

On Wednesday, January 16, 2013 8:02:54 PM UTC+9, Chih-Wei Huang wrote:
Hi,
I've pushed all jb-x86 branches to our main git server.
As usual, you can get it by

repo init -u http://git.android-x86.org/manifest -b jb-x86
repo sync

You will note there is only one target, android_x86.
This is the first step of the plan to create a universal image.
Though it's still far from complete.
I'll describe more details later.

SourceForge mirror is not synced yet.
Will try to do it when I have time.

Gerhard Smith

unread,
Jan 22, 2013, 5:31:02 AM1/22/13
to andro...@googlegroups.com
Read and follow instructions properly:

Either use the lunch command
or
make -j4 iso_img TARGET_PRODUCT=android_x86
Message has been deleted

dscm

unread,
Feb 10, 2013, 10:34:51 PM2/10/13
to Android-x86
updated jb-x86 preview builds here:

http://www.tabletsx86.org/android-x86-builds.htm

On Jan 16, 2:33 pm, dscm <rbg.hptou...@gmail.com> wrote:
> thanks Chih-Wei.....
>
> a test build is available here:
>
>      http://www.tabletsx86.org/
>
> select android-x86.org builds
>

walter79

unread,
Feb 11, 2013, 7:24:34 AM2/11/13
to andro...@googlegroups.com
Is it possible to add support for Wetab?

I managed to build a working ICS with lateste 3.0.36 kernel.

I used some source from StefenS and rabraken.

But still need to use modded ril from rabraken.

link to source:  https://github.com/walter79/android-wetab   ;  https://github.com/walter79/android_device_wetab ;  and RIL from https://github.com/rbraken/wetab-ICS-device-tree

Here is a 4.2.1 RIL for huawei generic: https://github.com/DerArtem/huaweigeneric-ril

McSurly

unread,
Feb 11, 2013, 12:37:32 PM2/11/13
to andro...@googlegroups.com
Hi,
I would be happy to help in any way I can to get a working, fairly-recent build going for Wetab.
I have an ExoPC, and I've been stuck on Corvusmod's "update4" release of 4.0.3 for a very long time.
It's great, but I would really like to put together something that either provides libhoudini, or allows the  user to do an install-time drop-in of libhoudini.
StephanS? Other prominent wetab folk?
What can I do to help? Is there a fairly recent build (I am fine with 4.0.3-based) I can/should try?
Thanks!

walter79

unread,
Feb 11, 2013, 1:22:08 PM2/11/13
to andro...@googlegroups.com

Troy Volin

unread,
Feb 11, 2013, 8:51:22 PM2/11/13
to andro...@googlegroups.com
I will try it tomorrow for sure.
One thing which was fixed between Update4 and Update5 (I think) of corvusmod was the SLEEP function.
I have a non-3G unit so I am not worried about RIL stuff, but I would like to know if the above will have SLEEP problems.
Thanks in advance!

Regards,
Troy


--
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.

Anil S

unread,
Jul 13, 2013, 3:39:33 PM7/13/13
to andro...@googlegroups.com
Hi Chih-Wei,

Great work... you are the best!

I could build android_x86 target successfully and the ISO file worked great on Virtual Box.

Just wondering how to run this image on an Android SDK Emulator. I tried it without success.

This is what I did:

1. Copied system.img, userdata.img, and ramdisk.img from "out/target/product/x86"   to  "<adt-install-dir>/sdk/system-images/android-17"
2. Also copied "kernel" from "out/target/product/x86"   to  "<adt-install-dir>/sdk/system-images/android-17" (and renamed kernel to kernel-qemu)
3. Started AVD manager and created a new AVD using the following settings:

    Device: Nexus S (4.0", 480 x 800 hdpi)
    Target: Android 4.2.2 - API Level 17
    CPU/ABI: Intel Atom (x86)

4. Started the AVD

The emulator screen comes up but it sits there on the black screen. Android never comes up.
Is it because of the wrong "kernel" version? Please help if you can or just point me to the right direction.

My big question is that: IS IT POSSIBLE TO RUN THE IMAGE ON GOOGLE SDK EMULATOR or IT WORKS ONLY ON VIRTUAL BOX?

Your time and efforts are appreciated.

Thanks in advance
Anil

On Wednesday, January 16, 2013 6:02:54 AM UTC-5, Chih-Wei Huang wrote:
Hi,
I've pushed all jb-x86 branches to our main git server.
As usual, you can get it by

repo init -u http://git.android-x86.org/manifest -b jb-x86

Chih-Wei Huang

unread,
Jul 13, 2013, 9:45:48 PM7/13/13
to Android-x86
2013/7/14 Anil S <cpuki...@gmail.com>:
> Hi Chih-Wei,
>
> Great work... you are the best!
>
> I could build android_x86 target successfully and the ISO file worked great
> on Virtual Box.
>
> Just wondering how to run this image on an Android SDK Emulator. I tried it
> without success.
>
> This is what I did:
>
> 1. Copied system.img, userdata.img, and ramdisk.img from
> "out/target/product/x86" to
> "<adt-install-dir>/sdk/system-images/android-17"
> 2. Also copied "kernel" from "out/target/product/x86" to
> "<adt-install-dir>/sdk/system-images/android-17" (and renamed kernel to
> kernel-qemu)
> 3. Started AVD manager and created a new AVD using the following settings:
>
> Device: Nexus S (4.0", 480 x 800 hdpi)
> Target: Android 4.2.2 - API Level 17
> CPU/ABI: Intel Atom (x86)
>
> 4. Started the AVD
>
> The emulator screen comes up but it sits there on the black screen. Android
> never comes up.
> Is it because of the wrong "kernel" version? Please help if you can or just
> point me to the right direction.
>
> My big question is that: IS IT POSSIBLE TO RUN THE IMAGE ON GOOGLE SDK
> EMULATOR or IT WORKS ONLY ON VIRTUAL BOX?

Don't know it works or not.
Emulator is not our target.
At least, you should not replace the kernel.

The SDK has x86 image.
Why bother to do it?

Zachary Sun

unread,
Aug 1, 2013, 6:03:50 AM8/1/13
to andro...@googlegroups.com
Hi Chih-Wei,
     I was download android source code x86-jb and following the below step(https://googledrive.com/host/0BwGIrsQjBkyQai1mZXQ0U1JaV0U/ubuntu-builds.htm) to build image.
     Owing build error about xgettext, Gettext was installed.
     Owing build error about https://groups.google.com/forum/#!topic/android-x86/egYoE9yMjoU, I modified the definitions.mk line 1970 from " onepct=$$((((($(2) / 100) - 1) + img_img_blocksize + 1* img_blocksize)); \" to "onepct=$$(((($(2) / 100) - 1) + img_img_blocksize )); \"
     And then android_x86.iso was created under "/out" folder include initrd.img, install.img, ramdisk.img and system.img.
     android_x86.iso size:413,696KB
     system.img size:406,528KB
     When I installed the iso file to virtualBox, it can't work.
     The suitation :
     1. System can enter the desktop first page(Make yourself at home You can put your favorite apps here.). But I can use touch or mouse to un-lock the system.
     2. type "enter" key, system will echo "root@x86:/" and can type any key.
     I try your iso. It can work and can select language during installation.
     My environment info is Ubunutu desktop 12.04.1 on VM.
     Build info as following:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.3

TARGET_PRODUCT=android_x86
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=x86
TARGET_ARCH_VARIANT=x86
TARGET_CPU_VARIANT=
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.2.0-51-generic-x86_64-with-Ubuntu-12.04-precise
HOST_BUILD_TYPE=release
BUILD_ID=JSS15J
OUT_DIR=out
============================================
     Could you help me check it? Thanks!!!!
best regards
Zachary

Zachary Sun

unread,
Aug 1, 2013, 6:34:41 AM8/1/13
to andro...@googlegroups.com
Message has been deleted

Greg McGee

unread,
Aug 3, 2013, 12:33:24 AM8/3/13
to andro...@googlegroups.com

Getting random GUI restarts after getting to desktop
(shows android-x86 logo again etc) still trying to find culprit.

Avast complains about ~everything it scans being in the wrong context.

On Aug 2, 2013 8:27 PM, "tabletsx86" <rbg.tab...@gmail.com> wrote:
quick and untested build of android-x86 4.3 from git source available here:



On Thursday, August 1, 2013 6:03:50 AM UTC-4, Zachary Sun wrote:
Hi Chih-Wei,
     I was download android source code x86-jb and following the below step(https://googledrive.com/host/0BwGIrsQjBkyQai1mZXQ0U1JaV0U/ubuntu-builds.htm) to build image.
     Owing build error about xgettext, Gettext was installed.
     Owing build error about https://groups.google.com/forum/#!topic/android-x86/egYoE9yMjoU, I modified the definitions.mk line 1970 from " onepct=$$((((($(2) / 100) - 1) + img_img_blocksize + 1* img_blocksize)); \" to "onepct=$$(((($(2) / 100) - 1) + img_img_blocksize )); \"
     And then android_x86.iso was created under "/out" folder include initrd.img, install.img, ramdisk.img and system.img.
     android_x86.iso size:413,696KB
     system.img size:406,528KB
     When I installed the iso file to virtualBox, it can't work.
     The suitation :
     1. System can enter the desktop first page(Make yourself at home You can put your favorite apps here.). But I can use touch or mouse to un-lock the system.
     2. type "enter" key, system will echo "ro...@x86:/" and can type any key.

--
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/zW2jAgmU4ww/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.
Reply all
Reply to author
Forward
0 new messages