Build baytrail image for ASUS T100

[Chih-Wei Huang]

ASUS T100 uses 32-bit UEFI.
However, the baytrail target of android-ia 4.4.2 release
uses 64-bit UEFI by default.
To build a bootable image for T100,
one has to apply the attached patches:

* 0001-Change-baytrail_generic-to-32-bit-UEFI.patch
apply to device/intel/baytrail

* 0001-Fix-a-build-break-due-to-the-wrong-flag.patch
apply to linux/modules/debug_tools
(the patch is suggested to merge to android-ia tree
since it's definitely a bug to me)

Then build it:
. build/envsetup.sh
lunch baytrail_generic-userdebug
m -jX liveimg

I have uploaded the image I built to
http://goo.gl/VhVmWA

Then dd the image to a usb disk and boot
from it on T100.

The image can boot to Home on T100.
However, the display on the panel messed up.
But output to HDMI is good.
The benchmark shows the 3D acceleration works fine.

I hope more experts especially kernel devs
who are familiar with display driver
can join to improve it.


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

[Vaidotas]

Some guys have made T100 panel display work on Linux:
Ubuntu: http://www.jfwhome.com/2014/03/07/perfect-ubuntu-or-other-linux-on-the-asus-transformer-book-t100/
Fedora: https://www.happyassassin.net/fedlet-a-fedora-remix-for-bay-trail-tablets/
Not sure if something from their work might be useful in Android-x86.

[Václav Lipert]

No luck by me, I've got kernel panic :(

Dne čtvrtek, 29. května 2014 10:06:45 UTC+2 Chih-Wei Huang napsal(a):

[Chih-Wei Huang]

[ 34.192539] Iago: Couldn't find installation media

Where is your installation media?

[Wally]

On USB memory stick inserted in USB port in dock station. Could it be the problem?

Dne úterý, 3. června 2014 4:11:20 UTC+2 Chih-Wei Huang napsal(a):

[Wally]

Ups, sorry, now it's ok. I tried another tool for writing images and now it works as you wrote (with messed display).

Dne úterý, 3. června 2014 4:11:20 UTC+2 Chih-Wei Huang napsal(a):

[ 34.192539] Iago: Couldn't find installation media

[Petr Tomaník]

I tried on dell venue 8 pro also with messed up display, however it is useless since dell doesn't have hdmi out.

Dne úterý, 3. června 2014 16:49:32 UTC+2 Wally napsal(a):

[Christopher Price]

Try updating your BIOS to v307, the latest as of today.

Christopher Price

ConsoleOS.com

[Christopher Price]

Just saw Wally got his working. Still, BIOS 307 seems to be working for me. I heard some issues earlier but at least update to the release before 307 which greatly improves things for the device.

Also Venue 8 Pro just got BIOS A08 too yesterday.

More on-point though - has anyone else got this to build right from the patches? I still can't reproduce on my end with building from source. Huang's compiled build does work as described, but patches still no-go for me.

Christopher Price

ConsoleOS.com

[Petr Tomaník]

Updated Venue 8 Pro to A08, but still can't boot 64bit EFI and 32bit one is still messed up. 

What did Wally get working? Display on Asus?  

Dne sobota, 21. června 2014 9:51:51 UTC+2 Christopher Price napsal(a):

[Christopher Price]

No, I meant Wally got Huang's build working with HDMI.

I didn't expect BIOS A08 to Venue 8 Pro - but it's an important update as it improves charging functionality. Also if you didn't have A05 it includes the eMMC fix from that release - which likely could affect Android booting down the road.

Christopher Price

ConsoleOS.com

--
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/j-iKHx23hMg/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/d/optout.

[Beau Steward]

Are you attempting to apply the patches to android-x86 code? If so, try doing it against the android-ia code (Intel's code). From what I can tell, the image is generated from that codebase, and while I haven't yet attempted to apply the patches, the code within looks like things from that codebase.

The display corruption appears to be caused by a weird assumption on resolution. I'm suspecting it's attempting to render at the wrong orientation. It could also be a problem with incorrect or non-detection of the display information.

Additionally, there are many other things not working on the T100:

- Touchscreen (easy test is to attempt to slide down the status bar)
- Hardware buttons (power, volume, etc)

The keyboard and touchpad appears to work.

Kernel 3.15 appears to have much of the work in getting android-ia working, apparently. 3.16 is suppose to be more complete, but is currently pre-release. Might need to backport display driver from there, and figure out what is missing to make input hardware functional (buttons, touchscreen).

The BIOS update notes indicate a fix to applying BIOS updates from the BIOS itself, though I had no problem with it (maybe I did not have the condition mentioned). I didn't see any indication that anything else was changed.

[Christopher Price]

I’m attempting to apply the patch to Android-IA. Builds would complete with the two patches but I could not re-create the same result as Huang’s compiled build.

My next step (which I just started) is a completely clean repo sync in case repo status missed something, certainly not the first time if that was it.

I think “flipping” the screen resolution is a good next step, hope to try it later today.

ASUS is notorious for not including all BIOS changes in the notes - not that I’m singling ASUS out in that. While there was some concern raised on other lists about BIOS 307 - Huang’s compiled build runs fine on it (well, as fine as HDMI anyways).

Christopher Price

ConsoleOS.com

[Petr Tomaník]

Yes, you are right. 

I did try it yesterday and I was able to compile android-ia code. I set resolution 800x1280@60e for Dell and I have readable text while booting. I guess it has also wrong resolution when it starts graphics. How to set up proper resolution in ramdisk image? Where? Easy part was kernel_cmdline. 

Dne pondělí, 23. června 2014 4:25:58 UTC+2 Beau Steward napsal(a):

[Christopher Price]

I've gotten to the same point as well. Turns out my repo sync was corrupted, due to additional files that sync missed.

As to the video, I believe these are bugs in libdrm on Android-IA.

When I declare  video=VGA-1:e \ (force-enabling VGA), I get the same output as video=VGA-1:800x1280@60e \ on my Venue 8 Pro, once I got to SurfaceFlinger.

This leads me to believe that libdrm/dir components are the bug and that resolution is being detected, just detected incorrectly.

FWIW, here's my current display path (Venue 8 Pro, will try with T100TA in a bit):

BOARD_KERNEL_CMDLINE += vga=current i915.mipi_panel_id=3 i915.i915_rotation=1 \

                        i915.modeset=1 \

video=VGA-1:800x1280@60e \

                        acpi_backlight=vendor

Christopher Price

ConsoleOS.com

[rbg]

had no issue with patches:(android-ia 4.4.2_r1-ia2 sync'd jun 23,2004)

rbg@ubuntu-13:~/jun23-intel-ia-4.4.2/device/intel/baytrail$ git apply -v 0001-Change-baytrail_generic-to-32-bit-UEFI.patch
Checking patch baytrail_generic/BoardConfig.mk...
Checking patch baytrail_generic/baytrail_generic.mk...
Checking patch baytrail_generic/kernel_defconfig_overlay...
Applied patch baytrail_generic/BoardConfig.mk cleanly.
Applied patch baytrail_generic/baytrail_generic.mk cleanly.
Applied patch baytrail_generic/kernel_defconfig_overlay cleanly.

rbg@ubuntu-13:~/jun23-intel-ia-4.4.2/linux/modules/debug_tools$ git apply -v 0001-Fix-a-build-break-due-to-the-wrong-flag.patch
Checking patch vtunedk/sepdk/include/lwpmudrv_types.h...
Applied patch vtunedk/sepdk/include/lwpmudrv_types.h cleanly.
 

additional generated test image(untested) available here: (patches by Chih-Wei Huang for Android-IA baytrail image for Ausu-T100)

    https://drive.google.com/folderview?id=0B2evBKvIpdYkWEpTeXNIVEM5UGs&usp=sharing

[Christopher Price]

Yeah I think we're all stuck at the same point here. I've thrown every VGA switch I know at the issue. I'm going to touch base with some engineers and see if this is indeed a libdrm issue, which I suspect it is. I attempted to bypass the UFO driver in software mode, and got the same results.

Christopher Price

ConsoleOS.com

[Petr Tomaník]

What about some patch that would force choosen resolution and bypass driver autodetection or veryfication? 

I tried setprops in init.rc file, however without any success.  

[Christopher Price]

I suspect (it really irks my engineers when I suspect) that DRM auto detects and bypasses init.rc.

Personally I would wait until after I/O before exhausting more resources in it. I reported this bug awhile back to relevant parties as it pretty clearly is a (libdrm) bug upstream.

Christopher Price
ConsoleOS.com

On Jun 24, 2014 1:03 PM, "Petr Tomaník" <pet...@gmail.com> wrote:

What about some patch that would force choosen resolution and bypass driver autodetection or veryfication? 

I tried setprops in init.rc file, however without any success.  

--

[Ricardo Castro]

Thank you Chih-Wei Huang

On Thursday, May 29, 2014 4:06:45 AM UTC-4, Chih-Wei Huang wrote:

 Thank you Chih-Wei Huang, rbg,Christopher Price

[Petr Tomaník]

Do you have a bug id so we can sync and try it when it will be fixed?

Dne středa, 25. června 2014 4:35:59 UTC+2 Christopher Price napsal(a):

[Christopher Price]

There may be a fix in the latest build of libdrm on freedesktop. I won't be able to test until next week. No bug number on me, sorry.

Christopher Price

ConsoleOS.com

[Beau Steward]

From what I can tell it's not really drop-in. I can get it to build with the firmware, but without some of the code changes Intel threw in (perfmon and color space conversion appear to be the big items). I'm going to try massaging it a bit and see if I can get it to boot.

I tried the latest from Intel's site (newer than what's in their android build) without much luck (doesn't fully boot). It's only 2 versions behind the latest from freedesktop.

[Petr Tomaník]

Any news? Anyone succeeded? 

Dne pátek, 4. července 2014 8:48:55 UTC+2 Beau Steward napsal(a):

[Shawn Lin]

I'm having some trouble building my own copy of this.
I have an Onda V975w which is able to boot Chih-Wei's T100 image with no problems whatsoever.  Even video works perfectly, despite being the wrong density.  It works fine and seems smooth enough.
Problem is, I have tried to build my own.  I have followed the tutorial here to the letter, using Ubuntu 12.04.
https://01.org/android-ia/guides/developers/workstation-setup
I am using the source specified in the tutorial as well.  I'm building for baytrail_generic.  I have used git to apply the two patches, and it says all patches were applied successfully.  Make compiles everything successfully.  However, I have 2 problems:
1. Won't boot at all.  The UEFI BIOS of the V975w refuses to boot at all.  I can make it boot by copying the EFI folder from Chih-Wei's T100 image to mine.
2. By using the EFI folder from Chih-Wei's T100 image, it will boot and Android will come up, but it is extremely slow.  Unusably slow, as in I click something, and it takes 5-full minutes for it to respond.  Mouse pointer is also laggy.  Using mouse because touch doesn't work yet.

I'm not sure if the two problems are related.  Anyone have any idea what I did wrong?  Same thing both using baytrail_generic_eng and baytrail_generic_userdebug.

[Klim Chani]

Hi everyone.

First off I wanted to thank you guys for your energy spent on the development of android for baytrail 32 bit UEFI systems. 

Recently there was an update, about a week ago, it's the new BIOS 313 for t100 transformer. It seems to have no functionality  issues, but I wanted to know if it had any impact on our ability to get a 64 bit UEFI working?

Thanks

[Beau Steward]

jonpry posted over at xda-developers that he's gotten the 3.17 kernel working and it has some improvements.

http://forum.xda-developers.com/showpost.php?p=55936009&postcount=352
https://github.com/jonpry/t100_patches

Might be worth getting a new build up for broader testing.

[Petr Tomaník]

What about to try image from Asus MeMo Pad 8 which has BayTrail Z3735 CPU. Image with kernel source can be downloaded from asus website. http://www.asus.com/Tablets/ASUS_MeMO_Pad_8_ME181C/HelpDesk_Download/

 I'm going to try to put it on USB flash and boot on DVP8 or chinese Z3735F tablet. Next step would be resize partition and make dualboot. 

[Christopher Price]

That will be a lot easier with Lollipop as you will likely have an x86 Fastboot platform that is compatible. Nexus Player likely implies AOSP will have the x86 bootloader bits included.

Lollipop is going to be a major improvement of x86 support in Android, but it does not nullify Android-x86.org or Console OS in my view. Both open-source and closed-source PC solutions still make sense as AOSP will not likely support BIOS, UEFI, or Coreboot systems. You can count drivers in that, too. Obviously, it’s up to Google, and just my team’s speculation… but I don’t see them accepting commits there.

Christopher Price

ConsoleOS.com - iConsole.tv

On Oct 17, 2014, at 2:16 AM, Petr Tomaník <pet...@gmail.com> wrote:

What about to try image from Asus MeMo Pad 8 which has BayTrail Z3735 CPU. Image with kernel source can be downloaded from asus website. http://www.asus.com/Tablets/ASUS_MeMO_Pad_8_ME181C/HelpDesk_Download/

 I'm going to try to put it on USB flash and boot on DVP8 or chinese Z3735F tablet. Next step would be resize partition and make dualboot. 

[Dwayne]

Hello. Please excuse my commenting on this group, I do not mean to annoy anyone. I am not a dev or anything like that; I am 14 years old and desperate to get android running on my asus t100! I tried the image uploaded by Chih-Wei Huang but I get kernel panic. I have tried fresh downloads and I have used two different usb flash drives. I would really appreciate any help or advice from anyone. Thanks for taking the time to read this and I apologize if this is a stupid comment.

[Povilas Staniulis]

On 2015.04.22 19:44, Dwayne wrote:
> Hello. Please excuse my commenting on this group, I do not mean to annoy anyone. I am not a dev or anything like that; I am 14 years old and desperate to get android running on my asus t100! I tried the image uploaded by Chih-Wei Huang but I get kernel panic. I have tried fresh downloads and I have used two different usb flash drives. I would really appreciate any help or advice from anyone. Thanks for taking the time to read this and I apologize if this is a stupid comment.
>

No need to excuse, we all have to start somewhere.
Currently, there's no automated way to install Android on T100, but you
can try my latest image as a live USB.

http://raspis.ddscentral.org/pub/downloads/android-x86/Android-x86-Kitkat_Baytrail-K4.0_Apr21.rar

Just extract the downloaded archive to your USB flash drive.

[Gisa Tunbridge]

Thank you. I really appreciate your support :)

[Александр Кондратьев]

четверг, 23 апреля 2015 г., 4:50:49 UTC+3 пользователь Povilas Staniulis написал:

On my ASUS T100TAM with this image (Android-x86-Kitkat_Baytrail-K4.0_Apr21.rar) very often wifi connection dead and repair after full reboot

[Александр Кондратьев]

I run wpa_supplicant from command line
wpa_supplicant -iwlan0 -c/system/etc/wifi/wpa_supplicant.conf
and logcat wrote (see 4437)
how repair wifi from command line?

I/wpa_supplicant( 4437): Successfully initialized wpa_supplicant
I/wpa_supplicant( 4437): rfkill: Cannot open RFKILL control device
D/WifiMonitor( 2001): startMonitoring(wlan0) with mConnected = false
D/BluetoothAdapter( 4009): 560983292: getState() : mService = null. Returning STATE_OFF
D/ConnectivityService( 2001): Sampling interval elapsed, updating statistics ..
D/ConnectivityService( 2001): Done.
D/ConnectivityService( 2001): Setting timer for 720seconds
D/ConnectivityService( 2001): handleInetConditionChange: no active default network - ignore
I/EventLogService( 2910): Aggregate from 1430150125920 (log), 1430150125920 (data)
D/SurfaceFlinger( 1686): Screen released, type=0 flinger=0x404a9010
I/wpa_supplicant( 4437): CTRL_IFACE monitor[0]: 2 - No such file or directory
W/wpa_supplicant( 4437): wlan0: Failed to initiate AP scan
E/wpa_supplicant( 4437): Could not get interface hwaddr: Not a typewriter
D/WifiConfigStore( 2001): Loading config and enabling all networks
D/BluetoothAdapter( 4009): 560983292: getState() : mService = null. Returning STATE_OFF
W/Settings( 3196): Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
W/wpa_supplicant( 4437): wlan0: Failed to initiate AP scan
I/InputDispatcher( 2001): Application is not responding: AppWindowToken{21ac5974 token=Token{21a1cc3c ActivityRecord{216b5ff4 u0 com.android.settings/.Settings$WifiSettingsActivity t6}}} - Window{2184150c u0 com.android.settings/com.android.settings.Settings$WifiSettingsActivity}. It has been 5006.8ms since event, 5005.5ms since wait started. Reason: Waiting because the focused window has not finished processing the input events that were previously delivered to it.
I/WindowManager( 2001): Input event dispatching timed out sending to com.android.settings/com.android.settings.Settings$WifiSettingsActivity. Reason: Waiting because the focused window has not finished processing the input events that were previously delivered to it.
I/Process ( 2001): Sending signal. PID: 4009 SIG: 3
I/dalvikvm( 4009): threadid=3: reacting to signal 3
I/dalvikvm( 4009): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 2001): Sending signal. PID: 2001 SIG: 3
I/dalvikvm( 2001): threadid=3: reacting to signal 3
W/EventHub( 2001): poll failed (errno=1)
E/Sensors ( 2001): poll() failed (Interrupted system call)
I/dalvikvm( 2001): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 2001): Sending signal. PID: 2143 SIG: 3
I/dalvikvm( 2143): threadid=3: reacting to signal 3
I/InputDispatcher( 2001): Window 'Window{2184150c u0 com.android.settings/com.android.settings.Settings$WifiSettingsActivity}' spent 5261.9ms processing the last input event: KeyEvent(deviceId=12, source=0x00000101, action=0, flags=0x00000008, keyCode=131, scanCode=59, metaState=0x00000012, repeatCount=210), policyFlags=0x42000002
I/dalvikvm( 2143): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 2001): Sending signal. PID: 2055 SIG: 3
I/dalvikvm( 2055): threadid=3: reacting to signal 3
I/dalvikvm( 2055): Wrote stack traces to '/data/anr/traces.txt'
W/wpa_supplicant( 4437): wlan0: Failed to initiate AP scan
D/dalvikvm( 2001): GC_CONCURRENT freed 2388K, 18% free 11772K/14336K, paused 2ms+3ms, total 36ms
D/dalvikvm( 2001): WAIT_FOR_CONCURRENT_GC blocked 21ms
D/dalvikvm( 2001): WAIT_FOR_CONCURRENT_GC blocked 24ms
D/dalvikvm( 2001): GC_EXPLICIT freed 258K, 18% free 11791K/14336K, paused 1ms+2ms, total 33ms
E/ActivityManager( 2001): ANR in com.android.settings (com.android.settings/.Settings$WifiSettingsActivity)
E/ActivityManager( 2001): PID: 4009
E/ActivityManager( 2001): Reason: Input dispatching timed out (Waiting because the focused window has not finished processing the input events that were previously delivered to it.)
E/ActivityManager( 2001): Load: 0.47 / 0.21 / 0.17
E/ActivityManager( 2001): CPU usage from 14079ms to 83ms ago:
E/ActivityManager( 2001): 3.3% 2001/system_server: 1.8% user + 1.5% kernel / faults: 3 minor
E/ActivityManager( 2001): 1.2% 4009/com.android.settings: 0.8% user + 0.3% kernel / faults: 7 minor
E/ActivityManager( 2001): 1% 4433/logcat: 0% user + 1% kernel
E/ActivityManager( 2001): 0.9% 2055/com.android.systemui: 0.5% user + 0.4% kernel / faults: 1 minor
E/ActivityManager( 2001): 0.7% 3843/com.android.browser: 0.7% user + 0% kernel
E/ActivityManager( 2001): 0.5% 2126/com.android.inputmethod.latin: 0.3% user + 0.1% kernel / faults: 3 minor
E/ActivityManager( 2001): 0.2% 4437/wpa_supplicant: 0.1% user + 0.1% kernel / faults: 32 minor
E/ActivityManager( 2001): 0.1% 1138/mount.ntfs-3g: 0% user + 0% kernel
E/ActivityManager( 2001): 0% 10/rcuop/0: 0% user + 0% kernel
E/ActivityManager( 2001): 0% 1037/mmcqd/0: 0% user + 0% kernel
E/ActivityManager( 2001): 0% 1439/kworker/u9:42: 0% user + 0% kernel
E/ActivityManager( 2001): 0% 1686/surfaceflinger: 0% user + 0% kernel
E/ActivityManager( 2001): 0% 4371/kworker/u8:0: 0% user + 0% kernel
E/ActivityManager( 2001): 1.7% TOTAL: 0.8% user + 0.8% kernel + 0% iowait
E/ActivityManager( 2001): CPU usage from 1837ms to 2344ms later:
E/ActivityManager( 2001): 5.7% 2001/system_server: 1.9% user + 3.8% kernel
E/ActivityManager( 2001): 3.8% 2016/ActivityManager: 1.9% user + 1.9% kernel
E/ActivityManager( 2001): 3.8% 2020/android.ui: 1.9% user + 1.9% kernel
E/ActivityManager( 2001): 3.8% 2031/InputDispatcher: 1.9% user + 1.9% kernel
E/ActivityManager( 2001): 1.4% 1037/mmcqd/0: 0% user + 1.4% kernel
E/ActivityManager( 2001): 1.5% 2055/com.android.systemui: 1.5% user + 0% kernel
E/ActivityManager( 2001): 1.5% 2200/Binder_3: 1.5% user + 0% kernel
E/ActivityManager( 2001): 1.5% 4056/Binder_5: 1.5% user + 0% kernel
E/ActivityManager( 2001): 1.5% 4061/Binder_6: 0% user + 1.5% kernel
E/ActivityManager( 2001): 1.7% 4009/com.android.settings: 1.7% user + 0% kernel
E/ActivityManager( 2001): 3.4% 4009/ndroid.settings: 1.7% user + 1.7% kernel
E/ActivityManager( 2001): 1.9% TOTAL: 0.9% user + 0.9% kernel
D/dalvikvm( 2001): GC_FOR_ALLOC freed 616K, 19% free 11712K/14336K, paused 78ms, total 79ms
I/dalvikvm-heap( 2001): Grow heap (frag case) to 11.760MB for 281892-byte allocation
D/dalvikvm( 2001): GC_FOR_ALLOC freed 0K, 18% free 11988K/14612K, paused 37ms, total 37ms
W/wpa_supplicant( 4437): wlan0: Failed to initiate AP scan
W/wpa_supplicant( 4437): wlan0: Failed to initiate AP scan

[Povilas Staniulis]

T100TAM has slightly different hardware. Wifi works fine on my T100TA and I don't have the TAM model to test on.

Could you post the dmesg log ? (would be best if you get it right after Android boots up).

[Александр Кондратьев]

dmesg after boot  in attached file

wifi   down after some time with this messages (from logcat) process 4377

I/System.out( 4264): Tapstream Error: Failed to fire event, error=java.net.UnknownHostException: Unable to resolve host "api.tapstream.com": No address associated with hostname
I/wpa_supplicant( 4347): wlan0: CTRL-EVENT-TERMINATING

W/Settings( 3196): Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.

W/Settings( 2398): Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.

D/BluetoothAdapter( 4009): 560983292: getState() :  mService = null. Returning STATE_OFF

D/SurfaceFlinger( 1686): Screen released, type=0 flinger=0x404a9010

I/wpa_supplicant( 4356): Successfully initialized wpa_supplicant
D/dalvikvm( 2126): GC_CONCURRENT freed 386K, 14% free 2951K/3420K, paused 3ms+1ms, total 18ms
I/System.out( 4264): Tapstream Error: Failed to fire event, error=java.net.UnknownHostException: Unable to resolve host "api.tapstream.com": No address associated with hostname

D/ConnectivityService( 2001): Sampling interval elapsed, updating statistics ..
D/ConnectivityService( 2001): Done.
D/ConnectivityService( 2001): Setting timer for 720seconds

D/dalvikvm( 4009): GC_CONCURRENT freed 428K, 14% free 4072K/4728K, paused 3ms+3ms, total 25ms
I/System.out( 4264): Tapstream Error: Failed to fire event, error=java.net.UnknownHostException: Unable to resolve host "api.tapstream.com": No address associated with hostname

D/ConnectivityService( 2001): handleInetConditionChange: no active default network - ignore

I/GLSUser ( 2291): [GLSUser] getTokenFromCache: [account: <ELLIDED:9040>, callingPkg: com.android.vending, service: androidmarket]
W/System  ( 3905): Ignoring header User-Agent because its value was null.
I/System.out( 4264): Tapstream Error: Failed to fire event, error=java.net.UnknownHostException: Unable to resolve host "api.tapstream.com": No address associated with hostname
I/wpa_supplicant( 4364): Successfully initialized wpa_supplicant
I/System.out( 4264): Tapstream Error: Failed to fire event, error=java.net.UnknownHostException: Unable to resolve host "api.tapstream.com": No address associated with hostname
I/wpa_supplicant( 4372): Successfully initialized wpa_supplicant
D/dalvikvm( 2126): GC_CONCURRENT freed 387K, 14% free 2950K/3408K, paused 2ms+2ms, total 17ms
I/System.out( 4264): Tapstream Error: Failed to fire event, error=java.net.UnknownHostException: Unable to resolve host "api.tapstream.com": No address associated with hostname
I/wpa_supplicant( 4374): Successfully initialized wpa_supplicant
I/wpa_supplicant( 4374): rfkill: Cannot open RFKILL control device
D/dalvikvm( 4009): GC_CONCURRENT freed 394K, 15% free 4061K/4728K, paused 2ms+3ms, total 23ms
D/SurfaceFlinger( 1686): Screen acquired, type=0 flinger=0x404a9010
D/GRALLOC-DRM( 1686): set master
E/wpa_supplicant( 4374): mkdir[ctrl_interface=wlan0]: Read-only file system
E/wpa_supplicant( 4374): Failed to initialize control interface 'wlan0'.
E/wpa_supplicant( 4374): You may have another wpa_supplicant process already running or the file was
E/wpa_supplicant( 4374): left by an unclean termination of wpa_supplicant in which case you will need
E/wpa_supplicant( 4374): to manually remove this file before starting wpa_supplicant again.
D/WifiService( 2001): setWifiEnabled: true pid=4009, uid=1000
E/WifiStateMachine( 2001): Failed to reload STA firmware java.lang.IllegalArgumentException: command '36 softap fwreload wlan0 STA' failed with '501 36 SoftAP command has failed'
D/CommandListener( 1683): Setting iface cfg
D/CommandListener( 1683): Trying to bring down wlan0

D/WifiMonitor( 2001): startMonitoring(wlan0) with mConnected = false
D/BluetoothAdapter( 4009): 560983292: getState() :  mService = null. Returning STATE_OFF

I/wpa_supplicant( 4377): Successfully initialized wpa_supplicant
I/wpa_supplicant( 4377): rfkill: Cannot open RFKILL control device
I/System.out( 4264): Tapstream Error: Failed to fire event, error=java.net.UnknownHostException: Unable to resolve host "api.tapstream.com": No address associated with hostname

D/SurfaceFlinger( 1686): Screen released, type=0 flinger=0x404a9010

E/wpa_supplicant( 4377): Could not get interface  hwaddr: Not a typewriter

D/WifiConfigStore( 2001): Loading config and enabling all networks

I/ProcessStatsService( 2001): Prepared write state in 11ms

W/Settings( 3196): Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.

I/ProcessStatsService( 2001): Pruning old procstats: /data/system/procstats/state-2015-04-27-08-52-51.bin
I/wpa_supplicant( 4377): CTRL_IFACE monitor[1]: 2 - No such file or directory

D/BluetoothAdapter( 4009): 560983292: getState() :  mService = null. Returning STATE_OFF

W/wpa_supplicant( 4377): wlan0: Failed to initiate AP scan

28 апр. 2015 г. 19:56 пользователь "Povilas Staniulis" <wdmo...@gmail.com> написал:

--

[Alexandros Kritikos]

Any chance of taking a look at T100TAF as well? Most features work fine apart from wireless, dmesg availiable at https://gist.github.com/akritikos/d2f6d0842c23ba171711

Most probable cause should be this:
brcmfmac: brcmf_sdio_drivestrengthinit: No SDIO Drive strength init done for chip 43340 rev 2 pmurev 20

[Александр Кондратьев]

28 апр. 2015 г. 19:56 пользователь "Povilas Staniulis" <wdmo...@gmail.com> написал:

2015 m. balandis 27 d., pirmadienis 04:31:01 UTC+3, Александр Кондратьев rašė:

--

[rbg]

>Currently, there's no automated way to install Android on T100

have you tried hatharry's newinstaller???? 

[Povilas Staniulis]

2015 m. gegužė 2 d., šeštadienis 19:48:05 UTC+3, rbg rašė:

>Currently, there's no automated way to install Android on T100

have you tried hatharry's newinstaller????

My post was before the installer was released.

I may release builds with the new installer, but it's not a priority.

 

[Povilas Staniulis]

2015 m. gegužė 2 d., šeštadienis 18:50:56 UTC+3, Александр Кондратьев rašė:

28 апр. 2015 г. 19:56 пользователь "Povilas Staniulis" <wdmo...@gmail.com> написал:

2015 m. balandis 27 d., pirmadienis 04:31:01 UTC+3, Александр Кондратьев rašė:

четверг, 23 апреля 2015 г., 4:50:49 UTC+3 пользователь Povilas Staniulis написал:
> On 2015.04.22 19:44, Dwayne wrote:
> > Hello. Please excuse my commenting on this group, I do not mean to annoy anyone. I am not a dev or anything like that; I am 14 years old and desperate to get android running on my asus t100! I tried the image uploaded by Chih-Wei Huang but I get kernel panic. I have tried fresh downloads and I have used two different usb flash drives. I would really appreciate any help or advice from anyone. Thanks for taking the time to read this and I apologize if this is a stupid comment.
> >
> No need to excuse, we all have to start somewhere.
> Currently, there's no automated way to install Android on T100, but you
> can try my latest image as a live USB.
>
> http://raspis.ddscentral.org/pub/downloads/android-x86/Android-x86-Kitkat_Baytrail-K4.0_Apr21.rar
>
> Just extract the downloaded archive to your USB flash drive.

On my ASUS T100TAM with this image (Android-x86-Kitkat_Baytrail-K4.0_Apr21.rar) very often wifi connection dead and repair after full reboot

 

T100TAM has slightly different hardware. Wifi works fine on my T100TA and I don't have the TAM model to test on.

Could you post the dmesg log ? (would be best if you get it right after Android boots up).

--

<3>[  237.426403] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110

<3>[  237.426414] brcmfmac: brcmf_cfg80211_get_station: Could not get rate (-52)

It looks like the Broadcom wifi suddenly stops working with timeouts (error 110).

Since other SD devices do not stop working, it looks like a problem specific to brcmfmac.

Maybe a different nvram file is needed ? (just a wild guess though, but wouldn't hurt to try).

[Coldsteel Cohen]

I really would like a step by step of this. I have the t100TAR and I am able to install. but when I reboot. It shows no "grub" and I only keep having to reinstall or live cd. am I doing something wrong? I have been reading about the 32bit ufi and making a grub, is this wat I have to do? I really appreciate it. Mr. Huang, If u are able to assist I would be more than willing to donate to ur research. I HATE Windows and would love to have android on this machine.

[IamBackX5]

Sorry for my bad english... but as i remember, this build have a problems with native install, try to use latest: https://groups.google.com/d/msg/android-x86/-gCC3wDNHj0/F5-HyCrpP2cJ

This build also have some problems, but more stable and installer must be fixed...

Also you have another way - boot android like live, but from emmc using windows partitions... before android not fully worked it more comfortable as i think, for example i make special instaleer for this: http://www.youtube.com/watch?v=jTyTtt6pQzY

понедельник, 7 сентября 2015 г., 6:31:13 UTC+5 пользователь Coldsteel Cohen написал:

[Max]

I actually got it loaded and fixed grub. Now my only issue is camera not functioning...I have tried a few suggestions and nothing has been working.

--

[IamBackX5]

Just wait, developers works on this problem... how says one of linux developers from 4PDA, to get camera worked, developers needed to integrate camera sensor and atomisp driver, and it's very difficult.

вторник, 8 сентября 2015 г., 6:46:23 UTC+5 пользователь Coldsteel Cohen написал:

[Buyuk Bang]

2 Mayıs 2015 Cumartesi 23:49:03 UTC+3 tarihinde Povilas Staniulis yazdı:

Hello,

First of all, thanks for all the great work you and Povilas and Huang did!

I'm having similar WiFi problem with the latest images by Povilas (Jul26) and Magic Stick 1.5 based on 4.4-r3 release Chih-Wei Huang.

WiFi works after a reboot, it works for some time greeat (1 min to 10 min) then it completely stop wotrking. Turning off/on Wifi in android settings does not help. Only a reboot can fix WiFi. I turned on and off WiFi sleep and battery saving settings to workaround the problem, but no change.

My tablet is 32 GB Asus T100 TA (with 3740). No such a problem in windows, only Android X86 releases have this problem.

Any idea about that?

[IamBackX5]

This problem only with 802.11n 40MHz, some people says that developers have a progress with this problem, one of them complitely builded linux kernel without this problem, and he works with Povilas Staniulis. Just wait for new Android build release from Povilas Staniulis or Chih-Wei Huang, this problem also can be fixed. But before you can make only one thing - configure channel width on your Router to 20MHz only (default is 20/40MHz)? and WiFi cannot stop... but Android also have reboots for now, my Max is 12 hours of stable working without reboots, and wifi works all this time.

If you interested in linux kernel (as i know it can be used with ubuntu, kali and others linux distribs), you can find it here (use google translate): http://4pda.ru/forum/index.php?s=&showtopic=611095&view=findpost&p=42613621

четверг, 10 сентября 2015 г., 6:17:38 UTC+5 пользователь Buyuk Bang написал:

[Buyuk Bang]

Thank you very much for the detailed answer.  I'm happy to hear that this was a known problem and there is an attempt to fix it for Android X86 images. I'll change my router router settings as you suggested.

Best regards

10 Eylül 2015 Perşembe 09:53:08 UTC+3 tarihinde IamBackX5 yazdı:

[Karol Putra]

Has anyone tried doing something with the lack of sleep state? At least I think that's what it is, but I haven't looked at the logcats yet, so not 100% sure. When power is pressed the screen just dims out, but isn't turned off competely. That makes daily usage pretty bad if you want to go mobile.

So, any solutions? Maybe there is a command to disconnect/connect specific device? Sorry I'm only starting my Android "dev" adventure, so I'm pretty far from giving solutions ony my own.

[Petr Dolak]

I think, there is no problem with a sleep itself. Problem is a backlight of the screen, which is still shining, even you put the tablet to the sleep.

[Povilas Staniulis]

Unfortunately, Baytrail PMIC support isn't complete yet, even in latest kernels.

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