Develop Bugs

Android 6 32bit builld

Has anyone managed a 32bit build of the latest aosp and got it to actually boot? Am currently stuck on the android boot screen

We have a 64 bit phone. Why are you attempting to use the 32 bit build?

hopesrequiem said:
We have a 64 bit phone. Why are you attempting to use the 32 bit build?
Click to expand...
Click to collapse
I need a 32bit aosp or cm13 so I can build Sailfish on top of it.
I tried compiling a 32bit aosp and stole vendor binaries from the nexus 5 for 32bit, but I can't get surfaceflinger to do anything aside from getting stuck on boot animation.
now am trying to build cm13 with FORCE_32BIT flag in BoardConfig like I saw somewhere else.
Also since this phone is a dual cpu, it has both libs 32/64 so its not an issue there.

m4r0v3r said:
I need a 32bit aosp or cm13 so I can build Sailfish on top of it.
I tried compiling a 32bit aosp and stole vendor binaries from the nexus 5 for 32bit, but I can't get surfaceflinger to do anything aside from getting stuck on boot animation.
now am trying to build cm13 with FORCE_32BIT flag in BoardConfig like I saw somewhere else.
Also since this phone is a dual cpu, it has both libs 32/64 so its not an issue there.
Click to expand...
Click to collapse
I highly doubt that you'll ever really get this to work. Even if you did get a 32-bit system image onto the device, there won't be any drivers since they'll have been compiled for AArch64.
Correct me if I'm wrong.

davidc14 said:
I highly doubt that you'll ever really get this to work. Even if you did get a 32-bit system image onto the device, there won't be any drivers since they'll have been compiled for AArch64.
Correct me if I'm wrong.
Click to expand...
Click to collapse
I think your slightly wrong. See the Nexus 5x has 2 cpus, not both are AArch64. So the vendor partition has both 32bit and 64bit libs.
Also 64bit cpus are generally backwards compatible with 32bit

m4r0v3r said:
I think your slightly wrong. See the Nexus 5x has 2 cpus, not both are AArch64. So the vendor partition has both 32bit and 64bit libs.
Also 64bit cpus are generally backwards compatible with 32bit
Click to expand...
Click to collapse
Well, no it doesn't have two CPUs. It has six cores on one SoC. It has four Cortex A53 cores and two Cortex A57 cores. You can see this by googling: snapdragon 808. Qualcomm's page details it.
You can see from ARM's specifications that both types of core are ARMv8-a AArch64 cores, which are 64-bit (hence AArch64). You're right that they include AArch32 ARMv7-a compatibility, as they have to for backwards compatibility. But I don't think Google or Qualcomm will have written any 32-bit drivers for the various radios, and GPU, etc on the device. So I don't think you'll get a 32-bit Android rom working on the 5X.

davidc14 said:
Well, no it doesn't have two CPUs. It has six cores on one SoC. It has four Cortex A53 cores and two Cortex A57 cores. You can see this by googling: snapdragon 808. Qualcomm's page details it.
You can see from ARM's specifications that both types of core are ARMv8-a AArch64 cores, which are 64-bit (hence AArch64). You're right that they include AArch32 ARMv7-a compatibility, as they have to for backwards compatibility. But I don't think Google or Qualcomm will have written any 32-bit drivers for the various radios, and GPU, etc on the device. So I don't think you'll get a 32-bit Android rom working on the 5X.
Click to expand...
Click to collapse
Hmm you might be right here, although the vendor partition seems to include identical lib and lib64 shared libs. I'll have to do more digging. The only other solution is to build sailfish 64bit but I don't think such a thing exists :'(
edit:
after digging around the vendor partition it seems theres both 32bit and 64bit binaries.

Because 64bit is a mixed bag, its not all positive. 64bit adrees space has much bigger memory footprint (64bit pointers etc)

Nexus 5x 32-bit kernel?

I just got my Nexus 5x in! I've never developed for Android before, so this is all a new experience for me. I managed to get a 6.0.1_r30 generic arm build compiled (forgot to `lunch` for bullhead), so I know my environment is finally sane. However, I'd like to get some clarification on the Snapdragon 808.
I know the Snapdragon 808 is based on the ARMv8-a architecture, which means that it should, in theory, be both arm and arm64 compatible. And, from the look of devices/lge/bullhead/BoardConfig.mk, it appears that the default kernel is dual-arch arm and arm64. However, the primary arch is arm64. I'd like to attempt to build a kernel that's arm (armv7-a-neon) only. You might ask, "Why would you want to do that?" Well, I would like to build Ubuntu Touch for the device. Ubuntu touch is using the KitKat dev tree, so is only 32-bit compatible. Attempts to expand the KitKat tree with an arm64 cross-compilation toolchain were fruitless after spending countless hours attempting it.
At this point, I don't even know if it's worth trying for a couple of reasons:
Hardware drivers are Lollipop, Ubuntu Touch is KitKat
I don't know if ARMv8-a will boot a 32-bit kernel out-right or it has to start in 64-bit mode and drop to 32-bit (if that's the case, would the kernel know to do that? Or does the CPU start in 32 bit mode and bump up to 64 bit mode)?
It's probably pretty unlikely that dropping in a pre-built Lollipop kernel into the Ubuntu Touch dev tree would work -- different ABI's (That's the ever-changing kernel/Android-specific API/syscalls, right?)
So, I'm looking for some help clarifying any of these issues. Is there anybody here really familiar with ARM that could answer these questions? Heck, if these are non-issues, I might even attempt a build.

How to compile the oficial OOS sourcecode?

Hi,
Since OP released the source code of the OP3 I thought I would take a shot on compiling them.
I have a lot of experience with C++ on an application level and also did some minor work with windows drivers.
But on Linux I'm still a beginner.
Since the repository OP points to (https://github.com/OnePlusOSS/android/tree/oneplus3/6.0.1) contains only a shell script I guess I can't compile it on windows, right?
So I will go for a Linux VM, what OS should I use Ubuntu 12 or 14 or may be better Debian?
Also How much power does a machine need in order to compile a android image in a reasonable time frame? My PC has a 6 core i7 @ 4GHz with 64 GB of RAM, AFAIK I can give all cores to the VM and up to 32 GB or RAM.
Giving cores is no problem, but the more RAM I give the larger all the snapshots become, so what would be a recommended amount?
Also What tools do I need? I tried to run the pull_library.sh but it threw some errors as I did not have ADB installed in the VM, so before I try and try i thought I just ask what thing I'll need to swiftly succeed with my endeavor?
Cheers
David X.

DavidXanatos said:
Hi,
Since OP released the source code of the OP3 I thought I would take a shot on compiling them.
I have a lot of experience with C++ on an application level and also did some minor work with windows drivers.
But on Linux I'm still a beginner.
Since the repository OP points to (https://github.com/OnePlusOSS/android/tree/oneplus3/6.0.1) contains only a shell script I guess I can't compile it on windows, right?
So I will go for a Linux VM, what OS should I use Ubuntu 12 or 14 or may be better Debian?
Also How much power does a machine need in order to compile a android image in a reasonable time frame? My PC has a 6 core i7 @ 4GHz with 64 GB of RAM, AFAIK I can give all cores to the VM and up to 32 GB or RAM.
Giving cores is no problem, but the more RAM I give the larger all the snapshots become, so what would be a recommended amount?
Also What tools do I need? I tried to run the pull_library.sh but it threw some errors as I did not have ADB installed in the VM, so before I try and try i thought I just ask what thing I'll need to swiftly succeed with my endeavor?
Cheers
David X.
Click to expand...
Click to collapse
Why do you not asking this in the right section?
Maybe general or Q&A
Best Regards,
Taker

What are you expecting when trying to compiling this ? It's the device tree and the kernel, not a full rom that you can install and run on your phone. Maybe you should look at how to compile a full rom like cm13. (if you want to compile something with your beast). There are plenty of tutorials.

_Man0waR_ said:
What are you expecting when trying to compiling this ? It's the device tree and the kernel, not a full rom that you can install and run on your phone. Maybe you should look at how to compile a full rom like cm13. (if you want to compile something with your beast). There are plenty of tutorials.
Click to expand...
Click to collapse
and where would I find those?

DavidXanatos said:
and where would I find those?
Click to expand...
Click to collapse
perhaps by searching? there is a whole thread about building cm13 in Guides, News and Discussion. And google should bring you many results. I know I searched when I wanted to build my first rom a couple of years ago.

DavidXanatos said:
and where would I find those?
Click to expand...
Click to collapse
Come on. There is even a thread dedicated to building cm13 for the OP3. It should help you to start. There are several useful links inside the thread too. It's almost the same for any android rom (with a few adjustments).
http://forum.xda-developers.com/oneplus-3/how-to/learning-to-build-cm13-t3406725
Feel free to ask questions there if you get stuck. It should get you busy until we have official nightlies.
Good luck ! But please don't create a new thread 'Unofficial cm13 build'. We have enough of them

DavidXanatos said:
and where would I find those?
Click to expand...
Click to collapse
You will never be able to build yourself if you ask people where to find those.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app

[DEV][WIP][HOW TO] 64-Bit ( ROMs + Kernel + TWRP )

There are several threads on Moto's support site with dozens of people asking for 64-bit on the G4 Plus.
Well we can now run 64-bit ROMs on our device.
The 64-bit architecture is much more streamlined, more energy efficient and much faster.
There's an app compatibility benefit i.e some apps are built to run pretty well or only on 64bit processors.
Well currently we have to run app_process (system server) as 32bit, mainly cause of sensors non working actually with a 64bit system server ( Thanks to @vache for pointing this out )
What will you need:
Device Tree : https://github.com/TeamButter/android_device_motorola_athene/tree/lineage-15.1-64
Kernel Tree : https://github.com/TeamButter/android_kernel_motorola_msm8952/tree/lineage-15.1-64
Vendor Tree : https://github.com/TeamButter/proprietary_vendor_motorola/tree/lineage-15.1-64
Downloads Links:
64-bit TWRP 3.1.1-0 : https://sourceforge.net/projects/twrp-athene/files/twrp-3.2.1-r2-arm64-tywinlannister7.img/download ( Thanks to @tywinlannister7 )
64-bit LineageOS-15.1 : https://drive.google.com/file/d/1NnhMle31msyk1i3_lwE2NVRdP9PYQLRa/view?usp=drivesdk
Got a query? Ask in the thread.
Regards
XDA:DevDB Information
ARM64 Development on athene, ROM for the Moto G4 Plus
Contributors
Nikit, rajatgupta1998
ROM OS Version: 8.x Oreo
Version Information
Status: Alpha
Created 2018-04-09
Last Updated 2018-11-18

Nice work. Seems like sources aren't up yet on GitHub.

Long live Athene...

Nice work. Good for athene users too now.
PS:- @vache ftw

Will the 64 bit TWRP be able to flash 32 bit ROMs?

arm64 8.1 GApps
8.1 arm64 GApps.
Download:
https://drive.google.com/file/d/13S4Oo0RpxB5ox3J-oA2J08C8wEsIbEN4/view?usp=sharing
Courtesy @Dreamstar
---------- Post added at 05:56 PM ---------- Previous post was at 05:52 PM ----------
zeomal said:
Will the 64 bit TWRP be able to flash 32 bit ROMs?
Click to expand...
Click to collapse
yes

zeomal said:
Will the 64 bit TWRP be able to flash 32 bit ROMs?
Click to expand...
Click to collapse
yes. I tested.

I'm new to this 64 bit on Android ROMs...
What differences might I notice?
Thx....
Long live athene

hacker1911 said:
What differences might I notice?
Click to expand...
Click to collapse
HDR+ on Google Camera for instance. Any app that requires ARM64, actually.

Dreamstar said:
There are several threads on Moto's support site with dozens of people asking for 64-bit on the G4 Plus.
Well we can now run 64-bit ROMs on our device.
The 64-bit architecture is much more streamlined, more energy efficient and much faster.
There's an app compatibility benefit i.e some apps are built to run pretty well or only on 64bit processors.
Well currently we have to run app_process (system server) as 32bit, mainly cause of sensors non working actually with a 64bit system server ( Thanks to @vache for pointing this out )
What will you need:
Device Tree : https://github.com/TeamButter/android_device_motorola_athene/tree/lineage-15.1-64
Kernel Tree : https://github.com/TeamButter/android_kernel_motorola_msm8952/tree/lineage-15.1-64
Vendor Tree : https://github.com/TeamButter/proprietary_vendor_motorola/tree/lineage-15.1-64
Downloads Links:
64-bit TWRP 3.1.1-0 : https://drive.google.com/file/d/1EGS-uU1QBDbrP3G4lFUSVqDSHC_ZGpMR/view?usp=sharing ( Recovery Mandatory to flash for 64bit ROM )
64-bit LineageOS-15.1 : https://drive.google.com/file/d/1mXpjp22ds_rs9noDfGZNiUrj5Vn3lRc9/view?usp=sharing
Got a query? Ask in the thread.
Regards
Click to expand...
Click to collapse
Can I flash the TWRP 64-bits in TWRP or I will need a PC?

This is awesome thanks hope to see more 64bit ROMs in future
Sent from my Moto G4 Plus using Tapatalk

Luis FSS said:
Can I flash the TWRP 64-bits in TWRP or I will need a PC?
Click to expand...
Click to collapse
U can flash via twrp or even if u have root and twrp manager theoretically.
So it may work bro
But theoretically, twrp 3.2 should be able restore backups also??

cool_sid said:
U can flash via twrp or even if u have root and twrp manager theoretically.
So it may work bro
But theoretically, twrp 3.2 should be able restore backups also
Click to expand...
Click to collapse
Thank you

Guys, what's all this for? Can someone explain?
Thanks

Didn't got the last para ... Can any one explain it
Sent from my [device_name] using XDA-Developers Legacy app

EmiAndroid said:
Guys, what's all this for? Can someone explain?
Thanks
Click to expand...
Click to collapse
Ideal thread to ask this question is the Q/A thread and not in development forum but since u have asked it here.
There are two architectures for CPU to run on, 32 bit and 64 bit.
SD617 which athene has supports 64bit also but due to some reason, moto made it run 32 bit
Now @Dreamstar has done an awesome job and made rom which is 64 bit.
Now u can u all apps which run only on 64 bit devices like the google camera with HDR+
Hope this helps. For more details, google is your friend. Its great work, try it.

Does 64 bit roms are more battery efficient and faster that 32 bit roms?

Does this ROM have the same bugs as 32 bit lineage 15? Camera, chopchop, etc. ?

webnorka said:
Does this ROM have the same bugs as 32 bit lineage 15? Camera, chopchop, etc. ?
Click to expand...
Click to collapse
Yeah those exist and you can't change RGB values using Kernel Adiutor to prevent screen burn in
Sent from my Moto G (4) using Tapatalk

harshal2234 said:
Does 64 bit roms are more battery efficient and faster that 32 bit roms?
Click to expand...
Click to collapse
Plz ask yourself.... Is this the right thread for such questions? Ask these questions in Q/A thread
And yes 64 bit is obviously theoretically better than 32 bit as it allots 64 exabytes instead of 32 for each program to run
So ur games work better on 64 bit (theoretically)

Linux OS for HP Thin Client t510, RAM 4GB, ATA Flash 4GB

Dear Linux Dev's,
Maybe this is noob question, it's so sad but true. :crying:
Well,
anybody here could share me for what best OS Linux for :
Thin Client HP t510
RAM : 4GB PC3
ATA : Flash 4GB
I need to install whatever linux OS from pendrive to ATA flash, as long as the OS less than 4GB after installed.
The reason is for my kid, connected to internet and TV, just to see youtube and no need a CPU to install.
thank you.

Fmiyar said:
Dear Linux Dev's,
Maybe this is noob question, it's so sad but true. :crying:
Well,
anybody here could share me for what best OS Linux for :
Thin Client HP t510
RAM : 4GB PC3
ATA : Flash 4GB
The reason is for my kid, connected to internet and TV, just to see youtube and no need a CPU to install.
thank you.
Click to expand...
Click to collapse
Probably Debian 9 or LMDE 2. The processor will be an issue so it's lot of trial and error.
Also you will have to boot off pendrive instead of installation on ATA flash.

karandpr said:
Probably Debian 9 or LMDE 2. The processor will be an issue so it's lot of trial and error.
Also you will have to boot off pendrive instead of installation on ATA flash.
Click to expand...
Click to collapse
Thanks for reply, will do then for download and test.
Yup, i already prepare pendrive as bootable iso file.
Wish me luck, bro..

karandpr said:
Probably Debian 9 or LMDE 2. The processor will be an issue so it's lot of trial and error.
Also you will have to boot off pendrive instead of installation on ATA flash.
Click to expand...
Click to collapse
https://blog.linuxmint.com/?p=3232
512MB RAM (1GB recommended for a comfortable usage).
9GB of disk space (20GB recommended).
Minimum for Debian 9 Stretch (desktop):
1 GHz of processor.
256 MB RAM.
10 GB disk space.
My ATA Flash is only 4GB

Fmiyar said:
Thanks for reply, will do then for download and test.
Yup, i already prepare pendrive as bootable iso file.
Wish me luck, bro..
Click to expand...
Click to collapse
Fmiyar said:
https://blog.linuxmint.com/?p=3232
512MB RAM (1GB recommended for a comfortable usage).
9GB of disk space (20GB recommended).
Minimum for Debian 9 Stretch (desktop):
1 GHz of processor.
256 MB RAM.
10 GB disk space.
My ATA Flash is only 4GB
Click to expand...
Click to collapse
Yeah, you cant install it on the ATA.
Maybe try http://puppylinux.com/ if you want small footprint. Not sure how much work is required to make it work.

I know the OP wanted a Linux distro, but I've been running the Windows Embedded 7 Standard for some time on this exact config running somewhat smoothly. Worth a try.
Yes, Puppy flavoured distros might also be considered.

I have a dell N10D that's just a little bigger than a pack of smokes and runnin MX21 w/o an issue, until the power switch physically broke. Used it with a 10-inch touch screen for entertainment and my personal amusement in my truck until the switch broke. Need to get off my butt and repair switch.