Related
Hello, I'm glad to bring you this new, the Android-x86.org Team was released a NEW build 4.0RC2 (based in the source code 4.0.4r2.1) with gapps included, lot of fixes, and the best part, a patch included, a patch to be able to use houdini the intel binary translator which allow run ARM apps in the x86 architecture (this hack comes from Buildroid.org you can read about this here), I wanna paste here the RelaseNote4.0RC2
ReleaseNote 4.0-RC2
Android-x86 4.0-RC2 (Ics-x86).
The Android-x86 project is glad to announce 4.0-RC2 release to public. This is a second release candidate for Android-x86 4.0 stable release. Live CD ISOs are available from our sites, as usual
http://www.android-x86.org/download
http://code.google.com/p/android-x86/downloads/list
Key Features
The 4.0-RC2 release is based on the Android 4.0.4 (Ice Cream Sandwich branch). We have fixed and added x86 specified code to let the system runs smoothly on x86 platforms, especially for tablets and netbooks. Except the features in 4.0-RC1, the additional features in this release are
Kernel 3.0.36 with more drivers and bug fixes.
Enable Dalvik JIT compiler support.
Support some 3G modem.
Ready to run arm translator. (You still need to install Intel's libraries from BuilDroid.)
Physical keyboard layout selection.
Support two cameras.
Fake SD card is replaced by internal storage support.
We create targets optimized for different x86 platforms. Choose a suitable image for your platform.
android-x86-4.0-RC2-amd_brazos.iso for AMD Brazos platform
sha1sum: 41685b2fd9a0fcd101fc21aeb84882015a6fd976
android-x86-4.0-RC2-eeepc.iso for ASUS Eee PC family
sha1sum: 1953717ac1d606d57fc7d7293b367f8025c51b65
android-x86-4.0-RC2-asus_laptop.iso for some ASUS Laptops/Tablets
sha1sum: fa4a38fcb3e0191523b1673114d9fa076c461671
android-x86-4.0-RC2-tegav2.iso for Tegav2
sha1sum: 106b07aee820511077980275cc744c4327352394
android-x86-4.0-RC2-s103t.iso for Lenovo S10-3t tablet
sha1sum: 3ca23c78183da7b23f516f9c507d60d82b11ab5e
android-x86-4.0-RC2-thinkpad.iso for IBM thinkpad tablet
sha1sum: bc99ec3ace54c0c15c92e4e8eca87385c130ec1d
android-x86-4.0-RC2-tx2500.iso for HP tx2500
sha1sum: 303765d6da5fdb7d8d3979575f0728185e6fb120
The iso files are hybrid format. That means you can dump the iso into a usb drive and get a bootable usb stick, like
$ dd if=android-x86-4.0-RC2-xxx.iso of=/dev/sdX
where /dev/sdX is the device name of your usb drive.
Known issues
Suspend and resume doesn't work on some targets.
Not support Ethernet.
Source code
The source code is available in the main git server,
$ repo init -u http://git.android-x86.org/manifest -b ics-x86
$ repo sync
as well as the SourceForge mirror:
$ repo init -u git://android-x86.git.sf.net/gitroot/android-x86/x86/platform/manifest.git -b ics-x86
Click to expand...
Click to collapse
At the same time, I wanna share with you, my personal and custom Unofficial builds one for Asus EeePC T101MT (Exclusive for my device ) and another one for EeePC Generic, with all included, you can find more info and some captures, a full description of my changes and a video demo of my build in action here.
Also, I did a little howto add houdini libs in our devices (the tutorial from BuilDroid is to apply in your source code and now part of this method isnt necesary, now you just need to copy some libs) you can fin more info here
COOKING TIME WITH ARNDROID-X86!
Enjoy!, Cheers.
installed the thinkpad version on my dell inspiron 1300. I can load the broadcom b43xx via debug mode but it does not scan or show or connect to any wifi networks. that is the only issue I have so far.
http://www.webupd8.org/2012/07/android-x86-404-ics-rc2-released-with.html
dorfd1 said:
installed the thinkpad version on my dell inspiron 1300. I can load the broadcom b43xx via debug mode but it does not scan or show or connect to any wifi networks. that is the only issue I have so far.
Click to expand...
Click to collapse
Same with Broadcom BCM4310 USB Controller on HP Compaq 6830s NN328ES
The solution that has helped me: disable WPA2 encryption, leave only WPA
Vaka++ (C)
Strange, but the authors of the assembly did not put the firmware for the devices, but the modules were collected, respectively, because this device does not work, such as my wi-fi card.
Added many different firmware for devices wi-fi (especially for my zd1211rw) and touchscreens and different chipsets.
archive with firmware
Unpack the archive to the /system/lib/
Click to expand...
Click to collapse
hello! I need an android iso where they can run the appps arm, and use it with virtual box and have an Internet connection
can you help me?
hi everyone
ı' am new in here.
ı want to ask does INTEL BAY TRAIL (z3XXX) support to install linux installing? or not why ? (because bootloader or another thing etc..)
There is some variant of windows tablets on market but can ı install ubuntu, arch linux etc? does it support?
sorry my bad englısh
1a) UEFI/BIOS support. looks like for the Asus T100, Asus only gave a 32-bit UEFI bootloader, so there are hacks to go around it. not sure about other devices like Dell Venue 8 Pro (I don't have that much money to buy so many devices)
1b) Secure Boot option to be disabled. If you can't disable Secure Boot, there are ways to get around it (some distros provide a signed UEFI shim that preloads before grub2, but you'll have to get that shim working with 32-bit bootloaders if you hit the problem above in 1a)
2) SoC support. Intel has submitted the Bay Trail SoC to the linux kernel. However, there are still some parts missing (eg open source video driver xf86-video-intel has it somewhat supported with bugs)
here is my WIP on getting ubuntu working on my Asus T100.... only major thing missing is graphics driver, everything else (besides sound) is working
http://forum.xda-developers.com/showthread.php?t=2500078
Baytrail T100 grub won't boot kernel
paperWastage said:
1a) UEFI/BIOS support. looks like for the Asus T100, Asus only gave a 32-bit UEFI bootloader, so there are hacks to go around it. not sure about other devices like Dell Venue 8 Pro (I don't have that much money to buy so many devices)
1b) Secure Boot option to be disabled. If you can't disable Secure Boot, there are ways to get around it (some distros provide a signed UEFI shim that preloads before grub2, but you'll have to get that shim working with 32-bit bootloaders if you hit the problem above in 1a)
2) SoC support. Intel has submitted the Bay Trail SoC to the linux kernel. However, there are still some parts missing (eg open source video driver xf86-video-intel has it somewhat supported with bugs)
here is my WIP on getting ubuntu working on my Asus T100.... only major thing missing is graphics driver, everything else (besides sound) is working
http://forum.xda-developers.com/showthread.php?t=2500078
Click to expand...
Click to collapse
Having a hell of a time getting ubuntu to get past grub.
Tried both Asus T100, and Dell Venue 8 Pro
Rufus (GPT for UEFI + FAT + 64 kb+ bootable disk using ISO Image)
Tried x86_64: ubuntu 13.04, 13.10, Fedora 20
All 6 Combinations, Boot into Grub, but grub throws the following error message every time, when booting the kernel:
"Can't Terminate EFI Services", and go back to grub.
Tried both boot loader binaries: - bootia32.ubuntu_13.04_x64.zip, and bootia32_normal_configfile.zip
From main thread: http://forum.xda-developers.com/showthread.php?p=46861952#post46861952
After that grub error, USB devices are all disabled.
Not sure how to debug further, seems like a grub EFI issue, but can't confirm.
Tried grub debug, using "set debug=all", and the error occurs right after the EFI map is displayed.
Please advise on how to proceed - how can this happen on both T100 and V8P?
M$ ruined baytrail by requiring 32 bit EFI, on a 64 bit system!
I could be wrong, but I thought I remembered seeing a 32 efi folder in Ubuntu GNOME 14.04. I'm not positive because I used the 64 bit installation on my HP Pavilion x2 2-in-1. It has the bay trail graphics. I stumbled upon this thread because I was looking for improved driver support. Right now the only thing not working on my installation (besides bluetooth) is display brightness control.
BayTrailSucks said:
"Can't Terminate EFI Services", and go back to grub.
Click to expand...
Click to collapse
I saw this log from time to time when I've used binaries you've mentioned.
So I've recompiled grub myself from sources taken from: ftp.gnu.org/gnu/grub
I've used version 2.00
To compile grub I've used commands:
./configure \
--with-platform=efi --target=i386 --disable-nls \
--disable-grub-emu-usb --disable-grub-emu-sdl --disable-grub-emu-pci --disable-grub-mkfont \
--disable-device-mapper --disable-libzfs --disable-werror
sed -i -e '/gets is a/d' grub-core/gnulib/stdio.in.h
make -j 2 MAKEINFO=true
make -j 2 install MAKEINFO=true
and then to prepare bootloader binary I've executed:
i386-grub-mkimage -o bootia32.efi -O i386-efi -p /boot/grub ntfs boot cat efi_gop efi_uga elf fat linux keylayouts \
memdisk minicmd ext2 extcmd part_bsd part_gpt search search_fs_file chain \
loadbios loadenv memrw mmap msdospart scsi loopback
For kernel tests I've used kernel 3.12 from kernel.org and 3.13.0-rc8 from repository: git://people.freedesktop.org/~danvet/drm-intel
Kernel 3.12 booted fine when I've added 'video' parameter as was mentioned in paperWastage thread.
For kernel 3.13.0-rc8 I've to revert one commit, see more info in bug 71977 at bugs.freedesktop.org
After I've updated xf86-video-intel to 2.99.907 and libdrm to 2.4.52 I was able to run X server with acceleration:
# glxinfo | grep ren
direct rendering: Yes
GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control,
GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read,
GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control,
GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read,
OpenGL renderer string: Mesa DRI Intel(R) Bay Trail x86/MMX/SSE2
GL_NV_conditional_render, GL_AMD_draw_buffers_blend,
What about hardware accelerated video playback
What about hardware accelerated video playback?
vshalimo said:
What about hardware accelerated video playback?
Click to expand...
Click to collapse
It works. I can use GPU accelerated decoding in vlc compiled with libva support.
-bash-4.2# vainfo
libva info: VA-API version 0.34.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /kanapi_packages/libva-master/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_34
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.34 (libva 1.2.2.pre1)
vainfo: Driver version: Intel i965 driver - 1.2.3.pre1
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Simple : VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
Battery status
Patch for kernel for battery status has been just added to bug 69011 in kernel bugzilla (I can't put link here)
and it works on ASUS T100TA:
cat /sys/class/power_supply/BATC/uevent
POWER_SUPPLY_NAME=BATC
POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_TECHNOLOGY=Li-ion
POWER_SUPPLY_CYCLE_COUNT=8
POWER_SUPPLY_VOLTAGE_MIN_DESIGN=3750000
POWER_SUPPLY_VOLTAGE_NOW=4174000
POWER_SUPPLY_CURRENT_NOW=1172000
POWER_SUPPLY_CHARGE_FULL_DESIGN=8180000
POWER_SUPPLY_CHARGE_FULL=9595000
POWER_SUPPLY_CHARGE_NOW=9316000
POWER_SUPPLY_CAPACITY=97
POWER_SUPPLY_MODEL_NAME=SR Real Battery
POWER_SUPPLY_MANUFACTURER=Intel SR 1
POWER_SUPPLY_SERIAL_NUMBER=123456789
Hello. I just wanted to play Trivia Royale on my phone but it says " device isn't compatible with this version " on play store. I have installed apk manuelly and could open game . But it has so many lags . I have tried game on Samsung Note 4 it works really good. I think it is about my phone's 32 bit processor . Because Note 4 has 64 bit one. Is there a way to play that game on my galaxy a10 without laggy ? ( i guess my phone could run 64 bit supported games. I'm very dissapointed )
To find out whether phone's CPU architecture is 64-bit or not download, install and run
Droid Hardware Info
From there you can collect information about your phone's CPU. The common nomenclature for ARM, ARM64, and x86 processors are as follows:
ARM: ARMv7 or armeabi
ARM64: AArch64 or arm64
x86: x86 or x86abi
jwoegerbauer said:
To find out whether phone's CPU architecture is 64-bit or not download, install and run
Droid Hardware Info
From there you can collect information about your phone's CPU. The common nomenclature for ARM, ARM64, and x86 processors are as follows:
ARM: ARMv7 or armeabi
ARM64: AArch64 or arm64
x86: x86 or x86abi
Click to expand...
Click to collapse
It says ARMv7-A . What does this mean ?
jwoegerbauer said:
To find out whether phone's CPU architecture is 64-bit or not download, install and run
Droid Hardware Info
From there you can collect information about your phone's CPU. The common nomenclature for ARM, ARM64, and x86 processors are as follows:
ARM: ARMv7 or armeabi
ARM64: AArch64 or arm64
x86: x86 or x86abi
Click to expand...
Click to collapse
Aida64 shows 64bit ArmV8-A (32bit Mode).
Both reports show your phone runs 32-bit Android kernel and userspace. Hence you can't flawlessly run apps compiled to be used in 64-bit Android kernel and userspce.
Hello forum guys, I've registered now to see if any enlightened souls could help me.
So straight to the problem...As stated in the title I have a Galaxy A02s and I am having problems with its Android.
I did a lot of research but I'm just getting more doubts, I read things like custom mod, kernel 64, treble info, and so on.
I will specify my device with the Aida64 information for better understanding:
Chipset: Qualcomm Snapdragon 450
Core Architecture: 8x ARM CORTEX-A53 @ 1804MHz
Manufacturing Process: 14nm
Instruction Set: 64-bit ARMv8-A (32-bit Mode)
And Treble Info says:
In the Architecture part: "Your device is ARM32 but uses a 64-bit binder. This usually indicates that the hardware supports 64-bits but the software does not. In this case, a 'binder64' or 'a64' image should be used. "
And in the Image Requested part: "Your device needs an image file called 'system-arm32_binder64-ab.img.xz.'"
I don't know if this Treble has anything to do with leaving Android in 64-bit, but I was researching and researching and that's what I got, however, I have little knowledge about these things and I didn't find any tutorial teaching how to install/update to 64-bit
That's it, I hope you can help me, thank you in advance
What's your real problem?
Any 64-bit SoC flawlessly runs 32-bit Android OS and 32-bit apps
jwoegerbauer said:
What's your real problem?
Click to expand...
Click to collapse
sorry, stopping to read again what i wrote i realized i didn't specify what i needed help lol
So I just don't want this 32-bit mode, I googled to see if my processor had architecture to run in 64-bit, and apparently yes, so I wanted to put android in 64-bit, but I have no idea of how to do this
thanks again
Replace this thread's title by your real problem: How to reflash Galaxy A20s with 64bit Android
Certainly, you flashed a 32bits system.
Just flash a 64bits system.
VD171 said:
Certainly, you flashed a 32bits system.
Just flash a 64bits system.
Click to expand...
Click to collapse
I bought the phone and it came like this, but how do I do it ? To a 64bits system
I'm also with the same problem, I would need some ROM for the 64-bit system, but I realized that there is none so far, is there any other way to change it to 64-bit without changing the ROM?
Short answer: NO
Short answer: NEVER
I'd like to ask how is the 32bit system with the 64bit system?
Releases · EnesSastim/Downloads
Contribute to EnesSastim/Downloads development by creating an account on GitHub.
github.com
Bump thread
Bumped thread, again.
i picked up on a s5 neo because of the 64bit cpu over the snapdragon 801, cost only 60$ and is supported by lineage-os to my surprise the latest official version of it runs on 32bit even though the cpu can run 64bit, i did look at phone info [samsung] on the stock rom and it ran in 32 bit as well, the most i know about it is that it was android 6.0.1, so my questions is will lineage-os put this phone on 64bit since it can run it and did it ever have 64bit support at all from android, because i didn't try android 7 at all, i did try the Cosmic-Kernel that appears to run in 64bit but truth be told i haven't got a clue what im doing as to install it so i didn't try to hard to install it, heres a link to the github for it
https://github.com/Cosmic-Kernel/android_kernel_samsung_s5neolte
You have to distinguish between a device's Linux kernel and device's Android OS. Both are different to each device.
A kernel for Android OS basically is a mainstream Linux kernel, with additional drivers for the specific device, and other additional functionality, such as enhanced power management or faster graphics support.
If I'm not mistaken the kernel determines if the OS is 32bit, not necessarily the OS am I right or can the OS and kernel be 32bit
Actually any 64-bit ARM SoC can run 32-bit software ( Linux kernel -> modules, Android OS -> libraries & executables ) due to its 32-bit compatibilty mode.
This will change: ARM has announced that from 2023, all of its new smartphone CPU cores will be 64-bit only, with no 32-bit compatibility mode.
BTW:
Have never heard that Linux kernel determines whether Android OS has to run in 32-bit mode or 64-bit mode.
jwoegerbauer said:
Actually any 64-bit ARM SoC can run 32-bit software ( Linux kernel -> modules, Android OS -> libraries & executables ) due to its 32-bit compatibilty mode.
This will change: ARM has announced that from 2023, all of its new smartphone CPU cores will be 64-bit only, with no 32-bit compatibility mode.
BTW:
Have never heard that Linux kernel determines whether Android OS has to run in 32-bit mode or 64-bit mode.
Click to expand...
Click to collapse
jwoegerbauer said:
Actually any 64-bit ARM SoC can run 32-bit software ( Linux kernel -> modules, Android OS -> libraries & executables ) due to its 32-bit compatibilty mode.
This will change: ARM has announced that from 2023, all of its new smartphone CPU cores will be 64-bit only, with no 32-bit compatibility mode.
BTW:
Have never heard that Linux kernel determines whether Android OS has to run in 32-bit mode or 64-bit mode.
Click to expand...
Click to collapse
I know of running 32bit software on a 64 bit processor works on the same way with typical desktops and laptops, I'm trying to figure out how to make it run in 64bit mode, and determine the easiest way to do it