Related
http://releases.linaro.org/11.11/android/images-ics-preview/mainline-panda/
http://www.linaro.org/downloads/
http://android.git.linaro.org/gitweb
panda is also omap4
riverzhou said:
http://releases.linaro.org/11.11/android/images-ics-preview/mainline-panda/
http://www.linaro.org/downloads/
http://android.git.linaro.org/gitweb
panda is also omap4
Click to expand...
Click to collapse
Slight bit of English might not hurt?
What is this?
What's there not to understand? Pandaboard is one of the most popular OMAP4 targets.
Sent from my SAMSUNG-SGH-I777 using xda premium
pyrostic said:
Slight bit of English might not hurt?
Click to expand...
Click to collapse
http://i16.photobucket.com/albums/b12/tehglow/manytank.jpg
that is many tank?
yes?
Linaro is an Alliance of ARM TI IBM Samsung Freescale ST-Ericsson . It's working for Open source Software for Linux on the ARM Cortex-A family of processors , Android on ARM, Unbuntu on ARM , linux/anrdoid toolchains and some libs .
They release their own source distribution Optimizated for Cortex-A8 and Cortex-A9 , and image distribution for PandaBoard(TI OMAP4430) , Origen(Samsung Exynos4210) , Snowball(ST-Ericsson's Nova A9500) , QuickStart(Freescale i.MX53) .
In one word , linaro android distribution will be better for A8 and A9 processors , much more Optimization .
This looks interesting, how do I test it out?
I just took a look at this and I don't get it sort off. It seems to be to be a version of android for like the PandaBoard.etc. However it doesn't come in the form of a zip but an img. I reckon with a bit of porting we could get it to work somehow but would it be worth it?
XperiaPlayer said:
I just took a look at this and I don't get it sort off. It seems to be to be a version of android for like the PandaBoard.etc. However it doesn't come in the form of a zip but an img. I reckon with a bit of porting we could get it to work somehow but would it be worth it?
Click to expand...
Click to collapse
They have a git repo to pull the sources from, so devs could base roms off of this instead of AOSP. I don't see the advantage, but it's another option I guess~
XperiaPlayer said:
I just took a look at this and I don't get it sort off. It seems to be to be a version of android for like the PandaBoard.etc. However it doesn't come in the form of a zip but an img. I reckon with a bit of porting we could get it to work somehow but would it be worth it?
Click to expand...
Click to collapse
You can get source as same as CM or AOSP.
repo init -u git://android.git.linaro.org/platform/manifest.git -b linaro-android-11.12-release
repo sync
Linaro Android distribution will be better for A8 and A9 processors , much more Optimization .
And , you can use gcc4.5.4(linaro version) or gcc4.6.3(linaro version) to compile this Andoid distribution but CM or AOSP only for gcc4.4.3 from google.
shobon said:
They have a git repo to pull the sources from, so devs could base roms off of this instead of AOSP. I don't see the advantage, but it's another option I guess~
Click to expand...
Click to collapse
It's a full optimization version for A8/A9 platform. It's all.
Anyway, linaro gcc is the best compiler for arm.
It can be use to compile android kernel , ever for CM or AOSP .
We have had native Linux on our Iconias for quite a while now but the builds and kernels are getting outdated, Unity is here and there is no real direction as to what needs to be accomplished.
This thread has been started principally for two kinds of people:
Kernel and Linux developers whom can offer advice or indeed actual code
Iconia enthusiasts for suggestions / ideas as well as any logic they may have
This thread does not aim to make Linux on our Iconias poof out of nowhere. It requires a huge amount of work to get going although with proper information exchange it should be much easier to get the project going.
The current ToDo list is as follows (feel free to post me more):
RootFS on /data/linux
Kernel initrd which will chroot to /data/linux
Linux Kernel will boot off mmcblk0p7
Upgrade to Ubuntu 12.04 (although RootStock is now deprecated, we can just download a pre-built bundle for the arm-eabi FS, use live-build or get a pre-made RootFS. There's lots of options for this)
Build the kernel from scratch (this is kind of obvious anyway). Building for armhf sounds like a good idea
Full graphics acceleration from the Tegra 2 for Unity
Perhaps a build of Backtrack (this shouldn't be too difficult - they offer an image for arm. If it can share the kernel then we should be okay)
A501 3G Modem
USB Huawei Modems (although initial Googling seems to imply the compatibility of usbserial.ko and hence OOTB compatibility so long as a udev rule is added)
Camera, sensors and non-patchy wifi (issue on 2.6.38 although the nvidia drivers below should fix this)
Latest Linux kernel (ie 3.1.x)
We have plenty of resources at our disposal such as:
Dual Boot Bootloader: http://forum.xda-developers.com/showthread.php?t=1619913
ICS Kernel source: http://global-download.acer.com/GDF...AB&Step3=A500&OS=a08&LC=en&BC=Acer&SC=EMEA_27
A 2.6.x chromeos-based kernel with quite a bit of functionality implemented: https://github.com/astarasikov/iconia-gnu-kernel
Linux for Tegra which provides many drivers for porting Linux to the Tegra chips: http://developer.nvidia.com/linux-tegra
Kexecboot - a bootloader on a kernel image system which could be placed on mmcblk0p2 and can give us huge flexibility in terms of launching a kernel (http://kexecboot.org)
I've looked inside the Linux for Tegra package and a HUGE amount is in there including x configurations, hardware drivers, Broadcom wifi firmware and the list goes on.......
There's also a codec package so we can have native video acceleration in loads of formats.
The bootloader will, at least initially, probably be the default Acer one. We could utilise kexecboot in the future as noted above
What we need:
A system for organising the code. CI & trac?
Perhaps a wiki.... or at least somewhere to organise ideas and reversed data
Either role assignment or a huge number of 'issues' with the code on a system such as trac and anybody can fix any issue
What works without kernel hacking:
Sound: The Wolfson WM8903 sound chip has driver provided by Wolfson which have been integrated directly into the official Linux kernel source (source: http://opensource.wolfsonmicro.com/content/linux-drivers-wolfson-devices)
Wi-Fi (almost) - the broadcom drivers are available with a simple apt-get. They are also available through Linux for Tegra
Graphics Acceleration (Hardware) - the drivers and codecs come from Linux for Tegra
armhf - Support for the hard float capabilities is built right into the Tegra2 and both Ubuntu and Linux for Tegra provide this support alongside the (seemingly legacy!) armel
The RootFS can now be built with qemu-debootstrap
Please let me know if I forgot anything else (which I undoubtedly did!)
I'm all in. I can do whatever is needed. Looking For Backtrack more than Ubuntu but i'd imagine once we get the Kernels sorted any distro will be easy to make work. Looking forward to the FUN.
First, we have 3.0.0 kernel by sp3dev (having issues), I'll take look on that one. Eventhough kernels 3.0.y and 3.2.y (not 3.1.10 - that's EOL!) are good enough.
Secondly, kernel does not chroot, a script in initrd image does chroot (this isn't any magic). As in the previous question about cmdline, it's just say "dynamic configuration" for the kernel (as where to find rootfs etc.). In the linux kernel, it's hardcoded right now (needs to be undefined).
First, it's better to get points 1) - 3) working for now.
blackthund3r said:
There is a strong focus on the preliminary uboot bootloader, however. I'm not sure if this would replace the Acer bootloader or be chainloaded? Ideally we just want a boot img on mmcblk0p7. Can somebody confirm this for me?
Click to expand...
Click to collapse
No that's not possible. U-boot will be standalone bootloader (i.e if u-boot, then no Acer BL). Right now, my patch in Acer BL gives us a "sub-bootloader" (don't want to call it second-stage bootloader, because it always returns back to Acer BL, eventhough we submit the image as a byte array (and not a partition)).
I think its a good idea to start from 3.1.10 that's on nv git and has linux variant too...
thor2002ro said:
I think its a good idea to start from 3.1.10 that's on nv git and has linux variant too...
Click to expand...
Click to collapse
I think its a good idea someone cares to share his android kernel source. I tried to rebase my cros patches on top of nvidia android branch and most stuff seems to boot, but fb is not working.
I think I'll make a new version of uboot that will be able to boot custom kernel from a file/script in data partition and stock kernel from recovery partition. I have made a good port of uboot to sgs2 and now I know how to handle boot mode detection via gpio. Sadly I'm not using my iconia at all lately.
P.S. Everything works on 2.6.38 except camera and sensors. Wifi is unstable. What else could anyone probably want
Add to todo. 3G modem for A501
While the dual-boot bootloader is nice, it's not the best solution, in my opinion. Kexecboot would offer a nice multi-boot solution with a GUI. We'll have the ability to compile kernels on the native Linux environment without flashing every time. By simply passing arguments to the kernel (the one kexecboot loads), we can have it boot off of any partition Linux can see. This would eliminate any restrictions that the dual-boot bootloader may have. This would also be beneficial to users who prefer booting from non mmcblk0p7, non boot-img systems. (I personally prefer something along the lines of mmcblk1p1, with no boot img). Kexecboot already works for the Tegra 2, and has touchscreen abilities, so porting wouldn't be too terribly difficult. See here and here.
As far as distros go, we should look at something compiled for armhf. That'll help increase speeds. The tegra2 drivers already have a hard float pre-release available to play with.
If I think of anything else, I'll edit this post.
Added all your changes
What exactly is the aim of this thread?
Is it for the improved quality of different Linux distros in general of the Tab?
Is it for the creation of a single distro which will run decently?
Is it for just for spitballing ideas about the above ideas?
Stating a single goal will help us accomplish said goal with greater ease.
apapousek said:
What exactly is the aim of this thread?
Is it for the improved quality of different Linux distros in general of the Tab?
Is it for the creation of a single distro which will run decently?
Is it for just for spitballing ideas about the above ideas?
Stating a single goal will help us accomplish said goal with greater ease.
Click to expand...
Click to collapse
Threefold:
1) to collaborate what we have
2) to port and produce a fully working Ubuntu distro (complete including all patches, drivers etc)
3) if possible, make a backtrack port too
Sent from my Iconia A500 using Tapatalk 2
blackthund3r said:
Threefold:
1) to collaborate what we have
2) to port and produce a fully working Ubuntu distro (complete including all patches, drivers etc)
3) if possible, make a backtrack port too
Sent from my Iconia A500 using Tapatalk 2
Click to expand...
Click to collapse
1. A wiki would be nice. I have server space & bandwidth available.
2. That's not too difficult, especially with Ubuntu on the AC100 being tegra2
3. I've had one working for a while. It's just not too slick.
apapousek said:
1. A wiki would be nice. I have server space & bandwidth available.
2. That's not too difficult, especially with Ubuntu on the AC100 being tegra2
3. I've had one working for a while. It's just not too slick.
Click to expand...
Click to collapse
1. I have server space too - it powers my flash tool, ICS Root etc. I can install media wiki overnight - not an issue
2. In theory. It still has to be done though and there'll be loads of bugs. We want perfection
3. That's what we aim to change
Sent from my Iconia A500 using Tapatalk 2
Im all in particularly looking forward to backtrack but Ubuntu will be awesome if we can get it running without many if any bugs....
should we be focusing on ubuntu i mean there alot more lightweight os's such as DSL, Slitaz, unity linux, and puppy linux that would be alot less of a resource hog ;-)
gears177 said:
Im all in particularly looking forward to backtrack but Ubuntu will be awesome if we can get it running without many if any bugs....
should we be focusing on ubuntu i mean there alot more lightweight os's such as DSL, Slitaz, unity linux, and puppy linux that would be alot less of a resource hog ;-)
Click to expand...
Click to collapse
The Tegra 2 + 1GB RAM puts the A500 up there as one of the most powerful dual core tabs on the market. Ubuntu will be fantastic.
Sent from my Iconia A500 using Tapatalk 2
blackthund3r said:
The Tegra 2 + 1GB RAM puts the A500 up there as one of the most powerful dual core tabs on the market. Ubuntu will be fantastic.
Sent from my Iconia A500 using Tapatalk 2
Click to expand...
Click to collapse
kk looking forward to it pm me if i can help
gears177 said:
kk looking forward to it pm me if i can help
Click to expand...
Click to collapse
Sure. What skills do you have?
Sent from my Iconia A500 using Tapatalk 2
gears177 said:
Im all in particularly looking forward to backtrack but Ubuntu will be awesome if we can get it running without many if any bugs....
should we be focusing on ubuntu i mean there alot more lightweight os's such as DSL, Slitaz, unity linux, and puppy linux that would be alot less of a resource hog ;-)
Click to expand...
Click to collapse
gears177 said:
kk looking forward to it pm me if i can help
Click to expand...
Click to collapse
Okay, so none of the distros you named could be ran on our tablet. They're all Intel/AMD only. We have an ARM device. It's a beautiful, low-power architecture, that only a few distros support. Arch Linux runs fairly smooth on it, even when running from a Class 4 external microsd card.
If you want to help, learn how to compile a kernel, the differences between x86 and ARM, and about some basic user-space tools which interact directly or almost directly with the kernel.
Honestly, I'm not trying to be an a-hole, but having a plethora of volunteers does nothing if the volunteers don't know how it works.
apapousek said:
Okay, so none of the distros you named could be ran on our tablet. They're all Intel/AMD only. We have an ARM device. It's a beautiful, low-power architecture, that only a few distros support. Arch Linux runs fairly smooth on it, even when running from a Class 4 external microsd card.
If you want to help, learn how to compile a kernel, the differences between x86 and ARM, and about some basic user-space tools which interact directly or almost directly with the kernel.
Honestly, I'm not trying to be an a-hole, but having a plethora of volunteers does nothing if the volunteers don't know how it works.
Click to expand...
Click to collapse
I suppose that's a good point.
Anyhow, now we have loads of volunteers, should we assign roles?
Sent from my Iconia A500 using Tapatalk 2
blackthund3r said:
I suppose that's a good point.
Anyhow, now we have loads of volunteers, should we assign roles?
Sent from my Iconia A500 using Tapatalk 2
Click to expand...
Click to collapse
oh sorry :'( i can build from source and compile kernels but not very good have to learn and refine more sorry alot of my scripting is sloppy :-\
gears177 said:
oh sorry :'( i can build from source and compile kernels but not very good have to learn and refine more sorry alot of my scripting is sloppy :-\
Click to expand...
Click to collapse
I meant no offense by my comment at all. You're inquisitive, which is very very necessary for this project.
I would like to work a bit of the kernel side with gears.
Kernel side question. Do we want it to be compiled for ARM HF? It would give us speed benefits, above all else.
Mozilla have launched Firefox OS based on Linux kernel ... Its open source ... I would like any of our good developers to look forward towards developing this OS for our phones
More detail here: http://www.mozilla.org/en-US/b2g/
would be hard if there's no propietary driver kernel source..
It's possible.
Here's manifest: https://github.com/mozilla-b2g/b2g-manifest
I'm too busy to port it for now. Maybe someone else can do that.
i will give it a try to port it
This isn't android based... it's not a ROM it's an other OS... i think if it's possible it will be very hard
i have knowledge of unbranded os types
It's not android. But it is linux and android is also linux, so I think drivers can be ported from android to this, no (though no api stuff and such will be the same)?
I assume it'll be hard, much harder than ics and jelly bean, but still possible.
But I also think that it won't run as good/smooth as ics and in the future jb will run.
So it might run, but if it's useful is another question...
Nevertheless it would be awesome to see it running on the gio.
Also does it need to run on it's own or is it possible to run it on top of the android kernel? If this is the case then it becomes rather easy as we have enough stable android kernels for the gio.
Marcin, is that the purpose of the link you posted?
marcin1147 said:
It's possible.
Here's manifest: https://github.com/mozilla-b2g/b2g-manifest
I'm too busy to port it for now. Maybe someone else can do that.
Click to expand...
Click to collapse
I think it's Android based, it uses AOSP repo besided Linaro repo and Mozzila repo!
Code:
<remote name="aosp"
fetch="https://android.googlesource.com/" />
bgm92 said:
I think it's Android based, it uses AOSP repo besided Linaro repo and Mozzila repo!
Code:
<remote name="aosp"
fetch="https://android.googlesource.com/" />
Click to expand...
Click to collapse
but i see no apps in the manifest
tioammar said:
but i see no apps in the manifest
Click to expand...
Click to collapse
Of course not. It's based on android, so the core shares a lot with the core of android. This doesn't make it android.
The whole os is (except for the core stuff) web based, which probably means all apps need to be written in html 5 or maybe other web standards.
So android apk apps don't work, and so it makes no sence including them.
Stannieman said:
Of course not. It's based on android, so the core shares a lot with the core of android. This doesn't make it android.
The whole os is (except for the core stuff) web based, which probably means all apps need to be written in html 5 or maybe other web standards.
So android apk apps don't work, and so it makes no sence including them.
Click to expand...
Click to collapse
simple and great explanation.. thanks
currently trying to port give me some days
warface123 said:
currently trying to port give me some days
Click to expand...
Click to collapse
https://github.com/MaclawStudios
Here are sources for android ICS on GIO. Since the manifest uses android 4.0.4 I think you may need to use some things from this (don't forget to mention Maclaw and Marcin if you do).
Soon this will be updated to JB I think, I don't know if FFOS works with JB as well or it specifically needs ICS though.
About firefox OS: http://en.wikipedia.org/wiki/Firefox_OS
So it's not entirely android based. It only uses some parts for some of the hardware.
thanks for the sourches
It's based android. Because s2 users can install it.
its dam hard but i am making progress what do you want guys odin or cwm just wanna now
warface123 said:
its dam hard but i am making progress what do you want guys odin or cwm just wanna now
Click to expand...
Click to collapse
odin
alright it will be odin then now i gonna sleep but will continu tommorow
How much android is really in it? Mozilla made it so that it can run on devices that run android. So they probably just mean ARM with a certain ammount of ram etc...
Wikipedia says it's a linux kernel, some components of android for hardware communication, mozilla's own api's for app -> hardware communication such as phone, cam, speakers etc, and last but not least the gecko engine.
So if the kernel used is the same as the one used for android then you could use maclaw (and team)'s ICS kernel + the android stuff needed, merged with the b2g sources.
I'm not really a dev so it's probably a lot harder then what I'm saying here. But I think it's easier then a fully fledged android...
Were you able to boot something already?
Hi all,
Is there any chance to run Sailfish OS on a non-Jolla phone? I would prefer a bigger screen and I'd prefer to not wait for their phone.
Assuming that the drivers from Android are compiled for the same Linux kernel version as I want to run in Sailfish, they should be loadable.
So then it's just a question of whether Sailfish is written to use the same devices (in /dev) in the same ways.
Anybody know?
Cheers.
tabstop said:
Hi all,
Is there any chance to run Sailfish OS on a non-Jolla phone? I would prefer a bigger screen and I'd prefer to not wait for their phone.
Click to expand...
Click to collapse
First of all, Sailfish is not yet released to public, and most propably wont be before Jolla phone hits markets. So you can't get it before
tabstop said:
Hi all,
Assuming that the drivers from Android are compiled for the same Linux kernel version as I want to run in Sailfish, they should be loadable.
So then it's just a question of whether Sailfish is written to use the same devices (in /dev) in the same ways.
Anybody know?
Cheers.
Click to expand...
Click to collapse
Nobody knows yet, because nobody hasn't been able to have a look at it, since it hasn't been released. But I doubt that the kernel would match, since it doesn't even match on different Android phones. There are always some minor changes.
tabstop said:
Hi all,
Is there any chance to run Sailfish OS on a non-Jolla phone? I would prefer a bigger screen and I'd prefer to not wait for their phone.
Click to expand...
Click to collapse
Yes i think it will be possible run Sailfish on non-Jolla phone, anyway you should wait because there is no image for arm cpu in public.
tabstop said:
Assuming that the drivers from Android are compiled for the same Linux kernel version as I want to run in Sailfish, they should be loadable.
So then it's just a question of whether Sailfish is written to use the same devices (in /dev) in the same ways.
Anybody know?
Cheers.
Click to expand...
Click to collapse
in android devices in /dev very often is used from binary blobs.
and this blob compiled againts another libc called bionic and it is not compatible with glibc, but Jolla phone will use android drivers via special library.
Sailfish OS for Motorola XT910 ( Droid RAZR )
tabstop said:
Hi all,
Is there any chance to run Sailfish OS on a non-Jolla phone? I would prefer a bigger screen and I'd prefer to not wait for their phone.
Assuming that the drivers from Android are compiled for the same Linux kernel version as I want to run in Sailfish, they should be loadable.
So then it's just a question of whether Sailfish is written to use the same devices (in /dev) in the same ways.
Anybody know?
Cheers.
Click to expand...
Click to collapse
Well, the Sailfish OS runs on linux kernel thats for sure and soon it will have the capability to run almost all of the android apks, which means it can not be totally different form android form 'under-the-hood' so there is always some room to try it on your android devices.
I haven't really tried to explore Sailfish OS much, but if u do, plz tell me and I would like to do it on my phone (Moto xt910).
If you come across any guide for installing Sailfish OS on non-jolla phones, plz post the links here.
sidbhatt11 said:
Well, the Sailfish OS runs on linux kernel thats for sure and soon it will have the capability to run almost all of the android apks, which means it can not be totally different form android form 'under-the-hood' so there is always some room to try it on your android devices.
Click to expand...
Click to collapse
running apk doesn`t mean anything, i can run apk on my windows 7.
internaly it is GNU Linux, not android.
sidbhatt11 said:
I haven't really tried to explore Sailfish OS much, but if u do, plz tell me and I would like to do it on my phone (Moto xt910).
If you come across any guide for installing Sailfish OS on non-jolla phones, plz post the links here.
Click to expand...
Click to collapse
you should understand that nobody care about your motorola or what ever device you own. 3.5 developers that can build nemo mobile image will not do it just because of your request.
If I remember right the first demo shown of it was on a nexus phone. so of course it will run on android phone.
tsaxda said:
If I remember right the first demo shown of it was on a nexus phone. so of course it will run on android phone.
Click to expand...
Click to collapse
can you give URL?
EnErGy[CSDX] said:
can you give URL?
Click to expand...
Click to collapse
I just remember seeing a video demo of it on youtube and the guy giving the demo said it was running on a galaxy nexus. I don't have the link but you could find it easily on youtube.
It's an open source,isn't it?
c786764052 said:
It's an open source,isn't it?
Click to expand...
Click to collapse
Silica components and that fancy home screen are not open source
I must admit I really like this OS.. even if it is similar to blackberry 10 for some aspects.. if this os will be avaiable for rooted android phones, i will certainly install it on mine!
I'd install it fast if my phone could get this (LG L5), but I think it's too weak on it. Maybe Sony Ericsson xperia neo would take this.
Sent from my LG-E610 using xda app-developers app
N9 arm port is here who starts porting?
EnErGy[CSDX] said:
Yes i think it will be possible run Sailfish on non-Jolla phone, anyway you should wait because there is no image for arm cpu in public.
in android devices in /dev very often is used from binary blobs.
and this blob compiled againts another libc called bionic and it is not compatible with glibc, but Jolla phone will use android drivers via special library.
Click to expand...
Click to collapse
since the N9 port of Sailfish OS is now available:
h**p://jollausers.com/2013/12/the-comprehensive-guide-to-port-sailfish-to-n9/
and the arm chipset in the N9 (OMAP3630) is equal to many Android devices like the Defy+ h**p://en.wikipedia.org/wiki/OMAP it would be nice to hear that someone begins with the porting to other Android devices. Hopefully also for my Droid 4 (OMAP4430).
https://github.com/KonstaT/sailfishos_kernel_jolla_msm8930
thx to Konsta @ talk.maemo.org
cvp said:
https://github.com/KonstaT/sailfishos_kernel_jolla_msm8930
thx to Konsta @ talk.maemo.org
Click to expand...
Click to collapse
Would be great if it could run on Galaxy note 2 or 3.
So I decide to step up and buy the Zenfone 2 551. WW MODEL Should have it at my door step on Wednesday. Then fun begins. Going to build a Google edition rom for you all. Be less lag in the phone. With the most power out of the kernel. It will be designed. Around all 3 versions off the 550/551. Time to share some love. Please don't ask for a time stamp. As I am working around my twin boys schedule. After all that's done. I will build a killer theme for this also. To give more colors to work with. TWRP will be tweaked to run a lot smoother for us also. I already sent some emails out to people. To help out on twrp. As that is my weak point. Hope you guys are ready..
Sent from my ASUS ZenFone 2E using XDA Free mobile app
Hell yeah...... \m/
bring it on!!!!
Oooooh exciting
Sent from my ASUS_Z00AD using XDA Free mobile app
I like Google edition ROM.
But every custom ROM comes without gapps.
Thanks in advance.
It will be fully 64-bit and have the latest PowerVR drivers? Cool
Looking forward to it. I also love GPE ROMs.
Sent from my ASUS_Z00AD using XDA Free mobile app
Send for my ASUS_Z00AD usingXDA Free mobile app
The rom is already built. Just waiting on the phone to get here. It will have all the Google apk's in it. But make it clear to you all. I will not release it until its at least 95-100% bug free. Because I don't want anyone crying.
Sent from my ASUS ZenFone 2E using XDA Free mobile app
64bit x86 Android is different from 32bit version only by kernel (and some kernel related drivers). All libraries are 32bit. Stock ZF2 Android is exactly the same as so-called 64bit AOSP in terms of bitness.
This is standard for x86 Android builds.
Both 64bit and 32bit binaries are supported seamlessly even in stock Android - thanks to x86 instructions set. So, it's up to specific application developer choice how many bits to use in native code.
Thanks so much in advance
sorg said:
64bit x86 Android is different from 32bit version only by kernel (and some kernel related drivers). All libraries are 32bit. Stock ZF2 Android is exactly the same as so-called 64bit AOSP in terms of bitness.
This is standard for x86 Android builds.
Both 64bit and 32bit binaries are supported seamlessly even in stock Android - thanks to x86 instructions set. So, it's up to specific application developer choice how many bits to use in native code.
Click to expand...
Click to collapse
I am little bit confused, do you mean x64bit os in Stock? X64bit apps support in Stock u mean?
If yes, then I don't think so..
Even Asus rep, support, care said what we have in Stock is just x64bit kernel with x32bit os, promised that 5.1 will be full x64bit os for zenfone 2.. And x64bit app of AnTuTu didn't work in zenfone 2 but works with ARM x64bit os
blazinandroid1 said:
The rom is already built. Just waiting on the phone to get here. It will have all the Google apk's in it. But make it clear to you all. I will not release it until its at least 95-100% bug free. Because I don't want anyone crying.
Sent from my ASUS ZenFone 2E using XDA Free mobile app
Click to expand...
Click to collapse
Mate, you'll ALWAYS get people crying... It is an unfortunate thing but there's alweays something someone doesn't understand, do or just plain f!cks up... And you as the dev will always be ground zero for the muck they throw...
So saying, I hope I haven't scred you off because we really need some devs for this puppy...
Has some pretty decent hardware and the software is sorta catching up but it would be nice for another dev's rom to be on the menu.
Cheers mate...
blazinandroid1 said:
So I decide to step up and buy the Zenfone 2 551. WW MODEL Should have it at my door step on Wednesday. Then fun begins. Going to build a Google edition rom for you all. Be less lag in the phone. With the most power out of the kernel. It will be designed. Around all 3 versions off the 550/551. Time to share some love. Please don't ask for a time stamp. As I am working around my twin boys schedule. After all that's done. I will build a killer theme for this also. To give more colors to work with. TWRP will be tweaked to run a lot smoother for us also. I already sent some emails out to people. To help out on twrp. As that is my weak point. Hope you guys are ready..
Sent from my ASUS ZenFone 2E using XDA Free mobile app
Click to expand...
Click to collapse
edit..
Troll? Or this is real?
https://www.reddit.com/r/galaxynote4/comments/321a8e/turns_out_that_blazinandroid1_was_a_troll/
meciu99 said:
edit..
Troll? Or this is real?
https://www.reddit.com/r/galaxynote4/comments/321a8e/turns_out_that_blazinandroid1_was_a_troll/
Click to expand...
Click to collapse
Bro. That's a whole different person.
Sent from my ASUS ZenFone 2E using XDA Free mobile app
A different person that happens to share the exact same username, state promises despite providing vague technical info, and also happens to have "twin boys".
Yeah, quite the coincidence.
What exactly is a Google Edition rom? Never heard that before.
Very excited to hear this....in for sure.
threi_ said:
A different person that happens to share the exact same username, state promises despite providing vague technical info, and also happens to have "twin boys".
Yeah, quite the coincidence.
Click to expand...
Click to collapse
Exactly, I'll believe it when I see it. No offense to the OP, but how many times on XDA do we see these things?
If he puts a GPE Rom that actually boots up for this phone, I'll eat my words..
ansebovi said:
I am little bit confused, do you mean x64bit os in Stock? X64bit apps support in Stock u mean?
If yes, then I don't think so..
Even Asus rep, support, care said what we have in Stock is just x64bit kernel with x32bit os, promised that 5.1 will be full x64bit os for zenfone 2.. And x64bit app of AnTuTu didn't work in zenfone 2 but works with ARM x64bit os
Click to expand...
Click to collapse
Linux in Stock ROM is 64bit. This is the *actual* OS.
Android is, hmmm.. how to say.. it's pseudo-OS which doesn't manage neither processes nor memory, but simply uses modified java virtual machine per process.
So, generally speaking, Stock ROM *has* 64bit OS. Only java machine i.e. Android is 32bit.
But, since real OS (Linux kernel) is 64bit, you can use 64bit applications. I mean Linux binaries and libraries.
I compile binaries on my Ubuntu x64 and can freely use them without any modifications on Zenfone 2.
There is NO Android exist which is fully compiled in 64bits on x86 architecture. You can check AOSP configs - all them are using 32bits. Only Kernel (i.e. Linux OS) is 64bits. And Android 5.1.1 has no changes in this subject.
It's like Windows x64 where you can use 32bit applications. So, Stock ROM is 64 bit OS with 32bit Android applications (including 32bit Android framework).