[DEV][WIP][HOW TO] 64-Bit ( ROMs + Kernel + TWRP ) - Moto G4 Plus ROMs, Kernels, Recoveries, & Other De

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)

Related

Idol 3 source code available!

http://downloads.sourceforge.net/pr...xz?r=&ts=1439784880&use_mirror=skylineservers
SHA1: 463f818fc8b57525981a46e31ea5ee63f2987742
MD5: 88d8db5d4c9637daeb339eb79878c93a
Mirror: https://mega.nz/#!j4s1WYLK!DpK2bMfznrt_ih3-UtE6xvUgFSAujw9LBu4qgSCSzkU
Thanks to @neilownz for notifying us in the system image thread! Let the rom development begin!
Oh and xposed framework also works for the idol 3 as of yesterday.
Click on mirrors. I already finished downloading it in case it disappears.
Yay. Let the development begin
Yes, thx alcatel !
thanks for noticing
damn you've been faster than me
Only source code for 4.7 ? Just decompressing it and seeing only idol347.... ?
Is source code for 5.5 also included ?
frankee207 said:
Only source code for 4.7 ? Just decompressing it and seeing only idol347.... ?
Is source code for 5.5 also included ?
Click to expand...
Click to collapse
Yes it is. Plus 1.8 GB external tools.
Game of Roms.
Roms are coming...
My favourite season of game of ROMs xD
hellow everyone,
sorry if is it the wrong place...our chip is the same as the one plus one? we can hack same system camera app and libs?
yazzabo said:
hellow everyone,
sorry if is it the wrong place...our chip is the same as the one plus one? we can hack same system camera app and libs?
Click to expand...
Click to collapse
No, the 6045 has a 64bit Snapdragon 615. The OnePlus One has a 32-bit Snapdragon 801.
someone could compile a kernel?
cpu -snap615-msm8939
board msm8916
32bits-arm.......64 bits -Aarch64 for gcc? or armv8?
arm64-defconfig
gcc version for compiling?
Woohoo cyanogenmod (or another ROM) here i come!!!
Successful compilation
I can confirm that there are no problems with the compilation of the kernel from the source (for my device of course, which probably most of you already know is 6039y). But that's all for now. There is much more work to be done.
petrov.0 said:
I can confirm that there are no problems with the compilation of the kernel from the source (for my device of course, which probably most of you already know is 6039y). But that's all for now. There is much more work to be done.
Click to expand...
Click to collapse
Does the source released allow for cross development ie if someone does put together a rom they can generate it for both the 6039 and the 6045 series? I'm waiting for the day someone generates a kernel with some of the newer governors like intellidemand or interactiveX...perhaps would solve any of the remaining lag and heat issues. I honestly thought they would have made factory rom downloads available first before source but certainly won't complain.
petrov.0 said:
I can confirm that there are no problems with the compilation of the kernel from the source (for my device of course, which probably most of you already know is 6039y). But that's all for now. There is much more work to be done.
Click to expand...
Click to collapse
Why I can not compile the kernel from arm64 none idol3 or idol347 defconfigs works, all the same mistake of the image with different gcc 4.8.2,4.9.3,4.9 .... you may need to install a tool in ubuntu 32bits to compile kernel 64bit?
on the contrary if you compile perfectly from arm (idol347) but not 64bit?
rarely anything but to extract the zip is idol347_fsr_20150717 while away the zip is OT_6039X_6045X_20150717.tar.xz but not impossible since idol347 is snap is 401 ... idol3 6045x 615
another rare idol347 has defconfig in arm and arm64 ... while idol3 only arm64
franq36 said:
Why I can not compile the kernel from arm64 none idol3 or idol347 defconfigs works, all the same mistake of the image with different gcc 4.8.2,4.9.3,4.9 .... you may need to install a tool in ubuntu 32bits to compile kernel 64bit?
Click to expand...
Click to collapse
I use the prebuilts from the Cyanogen repo. Also the recommended architecture of the host machine for compilation of Android is x86_64 from long time.
@franq36 ... In case that you are curious. This is the list with the installed gcc packages on the host machine.
Code:
gcc install
gcc-4.7 install
gcc-4.7-base:amd64 install
gcc-4.7-multilib install
gcc-4.8 install
gcc-4.8-base:amd64 install
gcc-4.8-multilib install
gcc-4.9-base:amd64 install
gcc-multilib install
franq36 said:
on the contrary if you compile perfectly from arm (idol347) but not 64bit?
Click to expand...
Click to collapse
Here are two logs from my virtual machine. The first build is for 32 bit architecture while the second is for 64 bit. The TARGET_KERNEL_ARCH in both cases however is arm. arm64 cannot be compiled successfully, as returns the following error:
Code:
make[2]: *** No rule to make target `zImage'. Stop.
make[1]: *** [sub-make] Error 2
franq36 said:
rarely anything but to extract the zip is idol347_fsr_20150717 while away the zip is OT_6039X_6045X_20150717.tar.xz but not impossible since idol347 is snap is 401 ... idol3 6045x 615
Click to expand...
Click to collapse
I don't understand what you mean here. The idol347 however is with Snapdragon 410 not 401.
franq36 said:
another rare idol347 has defconfig in arm and arm64 ... while idol3 only arm64
Click to expand...
Click to collapse
This is strange indeed.
---------- Post added at 19:52 ---------- Previous post was at 19:10 ----------
famewolf said:
Does the source released allow for cross development ie if someone does put together a rom they can generate it for both the 6039 and the 6045 series?
Click to expand...
Click to collapse
I'm not sure about this. The devices are different, the boards are different, the kernel configuration and respectively the kernel is different, the display resolution of the devices is different. These are too much differences I think.
How do we get someone from xda staff to post this in portal news so people will see they can now use the sources?
keyra74 said:
How do we get someone from xda staff to post this in portal news so people will see they can now use the sources?
Click to expand...
Click to collapse
i think you can contact the guy named mario tomas serrafero hes the one that writes the main page articles
keyra74 said:
How do we get someone from xda staff to post this in portal news so people will see they can now use the sources?
Click to expand...
Click to collapse
for now it is early, still are not completely operational ... I think for 6045
and I managed to fix compilation errors through installed ubuntu 14.04.3 64 bits and all the tools ...
idol3_defconfig is only arm64 and gives -mgeneral-regs-only error.
I could cheat and load it from arm but having to fix several compilation errors and dependencies bad in defconfig.
I am having many compilation errors which explains that the GCC is not quite right. NDK official gcc 4.9. arm-linux-androideabi have to look any more current or Linaro to check
I think there is a gcc 4.9.3
I'm half compilation with many problems ... I hope it's not the fault of sources and it is time lost
has any one started on porting CM12/12.1 ? you could count on me for testing

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

Unlocking the 32GB Mi5 frequency

Hi guys, I have been looking at / working on allowing the 32GB variant Mi5 to run at the full speeds (2.15/1.6/624) on the msm8996 SOC as its 64/128GB brothers.
I was able to patch the kernel frequency table to run my 64GB at the reduced frequency of the 32GB but cannot test this in reverse as I don't have a 32GB device
I am hoping a 32GB user can test a boot.img for me. Can fastboot boot/flash it, or flash via TWRP (install -> install image -> select img) and just backup your existing img.
I do suspect it will not boot or work (it does boot/otherwise work on my 64GB though, but there's a few more code differences I haven't changed), but it'd be nice to know
boot_rev1.img this revision does not work, yet
boot_rev2.img a few users report that this one works.
What I would like to know is overall stability for 32GB users, if they could test their phone in games etc as voltage tables may need more adjustment
Edit: please note this kernel is for CM13/AOSP based ROM. please don't flash it over MIUI8
Project moved to http://forum.xda-developers.com/mi-...d-32gb-mi5-t3482455/post69177557#post69177557
Source here: https://github.com/harrynowl/falconkernel-gemini
awesome. did you post in the miui forum?
rochee94 said:
awesome. did you post in the miui forum?
Click to expand...
Click to collapse
Not yet, hoping to find feedback here first
As you are using CM kernel as base, you must inform that this will only work on devices running MIUI 7.x firmware and a CM based ROM.
On top of that, don't forget to publish the link to the kernel source in order to follow XDA's GPL regulations. I know you have the source in Github.
Could you build a kernel to overclock the 64 &128GB versions too? That would be great.
Sorry out of topic but, does snapdragon 820 have mpdecision or not? (by default)
razibrizal said:
Sorry out of topic but, does snapdragon 820 have mpdecision or not? (by default)
Click to expand...
Click to collapse
No: https://source.codeaurora.org/quic/...init.qcom.post_boot.sh?h=LA.HB.1.3.1.c1#n1729.
GalaxyS4_Lollipop said:
Could you build a kernel to overclock the 64 &128GB versions too? That would be great.
Click to expand...
Click to collapse
First focus is on giving 32GB users the full power of the hardware they paid for
I've tried it and it fails to boot
It goes into the bootanimation but after like one second it freeze and reboot
And when it happen, it kinda overheat
Edit
Using AOKP and Cm13 same result
sys01 said:
I've tried it and it fails to boot
It goes into the bootanimation but after like one second it freeze and reboot
And when it happen, it kinda overheat
Click to expand...
Click to collapse
Thanks for info, I think I know why this is..
Harrynowl said:
First focus is on giving 32GB users the full power of the hardware they paid for
Click to expand...
Click to collapse
That's cool.
Anyway, if it is any method to power up the beast to the SnapDragon821 power, I wait for it. (on 64gb)
Good luck and thanks for your support.
4 days ago bought a 32gb Mi5 -> upgraded to latest MIUI 8.0.12
Unlocked bootloader -> Flashed Ressurection Remix's latest ROM via TWRP
Looking forward in testing this !
Alex4455 said:
4 days ago bought a 32gb Mi5 -> upgraded to latest MIUI 8.0.12
Unlocked bootloader -> Flashed Ressurection Remix's latest ROM via TWRP
Looking forward in testing this !
Click to expand...
Click to collapse
Well, please don't use the one I posted originally as it won't work. But I'm looking at a fix now :good:
Looking forward towards the fix.
Many people will be happy if this comes out with no issues !
Harrynowl said:
Well, please don't use the one I posted originally as it won't work. But I'm looking at a fix now :good:
Click to expand...
Click to collapse
thank u for the initiative will wait for the next build :good:
pls after making it work, build one for MIUI 8 if it's possible.
catalizgar said:
pls after making it work, build one for MIUI 8 if it's possible.
Click to expand...
Click to collapse
Miui8 firmware blobs are not currently compatible with the kernel sources we have.
A member got a kernel booting on miui8 but stability was a big problem.
First of all, thank you. I think all 32GB users will thank you for that.
Obviously when it's done, it will consume more power, and would have less SoT.
Can you make predictions of what it will take when optimized and fully working?
After changing my ROM to AOSP based I will use this. thanks for your hard working. really appreciated
I added a new boot.img to the OP with some updates to the source. Hopefully this one has more luck. Specifically changes to the voltage table(s).
Please test 32GB users

Port for Kali.Nethunter kernel

Thread closed.
For new thread , go to this link.
https://forum.xda-developers.com/le...t/kernel-kali-nethunter-t3813746/post77016833
I request out developers to pls port the kali nethunter kernel for our device z2 plus. U can use mostly oreo roms as base for kernel since its much optimized and this device is best for pen testing pls pls developers spare ur lil time and make history!
Atharva Ambre[AT said:
;76155798]I request out developers to pls port the kali nethunter kernel for our device z2 plus. U can use mostly oreo roms as base for kernel since its much optimized and this device is best for pen testing pls pls developers spare ur lil time and make history!
Click to expand...
Click to collapse
Update I have created the changes for the kernel but I'm getting this error while compiling ...pls do suggest me the fix den the nethunter kernel is ready
Atharva Ambre[AT] said:
Update I have created the changes for the kernel but I'm getting this error while compiling ...pls do suggest me the fix den the nethunter kernel is ready
Click to expand...
Click to collapse
Wrong architecture maybe? Z2 is arm64.
JashanjotSidhu said:
Wrong architecture maybe? Z2 is arm64.
Click to expand...
Click to collapse
Thanks for the reply but nope I have ported rightly for z2 plus 64 bit defconfig file so I don't think its an arch issue since Kali nethunter kernel is for both arch 32 and 64 bit its something else.....thanks for ur try
Atharva Ambre[AT] said:
Thanks for the reply but nope I have ported rightly for z2 plus 64 bit defconfig file so I don't think its an arch issue since Kali nethunter kernel is for both arch 32 and 64 bit its something else.....thanks for ur try
Click to expand...
Click to collapse
Yeah my bad that was Linux x86....
Can you share include/linux/cpufreq.h file?
JashanjotSidhu said:
Yeah my bad that was Linux x86....
Can you share include/linux/cpufreq.h file?
Click to expand...
Click to collapse
Ya sure
Note the major errors are in proc.c
Atharva Ambre[AT] said:
Ya sure
Note the major errors are in proc.c
Click to expand...
Click to collapse
You uploaded cpu.h bro... I asked for the cpufreq.h...
Proc.c errors point to the above file as per your screenshot.
JashanjotSidhu said:
You uploaded cpu.h bro... I asked for the cpufreq.h...
Proc.c errors point to the above file as per your screenshot.
Click to expand...
Click to collapse
Oh I'm sorry my bad here's the right file
Atharva Ambre[AT said:
;76282414]Oh I'm sorry my bad here's the right file
Click to expand...
Click to collapse
Sorry again same wait take this
Atharva Ambre[AT] said:
Sorry again same wait take this
Click to expand...
Click to collapse
Try deleting the 657th and 658th line of cpufreq.h and then make again....
From where did you get the kernel sources? I couldn't find any 820chipset kernel sources with those lines.
Here's Z2 plus's file.
JashanjotSidhu said:
Try deleting the 657th and 658th line of cpufreq.h and then make again....
From where did you get the kernel sources? I couldn't find any 820chipset kernel sources with those lines.
Here's Z2 plus's file.
Click to expand...
Click to collapse
Will try and I got it from github its the open sources kernel , its available on most of the ROM first page , I got it from aex intro page on XDA
U won't find it bcoz the CPU freq file is inside Linux/include/CPU so its not android based file it's the main working of Linux so u won't find any specific chip based also it won't mention sd820 bcoz its open source u can port it as long as u are able to get it right without bugs its an open source so its open for many devices and many chipsets.
Update :
I tried again from start I think its the problem with the compiler of ndk will download older version and try out tomorrow...still getting many other errors while compiling from the source kernel
Pls provide me the link of latest stable ROM with it sources updated!thank you!
Update:
I'm gonna switch to Ubuntu distro it maybe can be distro problem.....have been trying to compile on Kali Linux..but failed despite many tries ,also re downloaded latest sources of kernel
Atharva Ambre[AT] said:
Update:
I'm gonna switch to Ubuntu distro it maybe can be distro problem.....have been trying to compile on Kali Linux..but failed despite many tries ,also re downloaded latest sources of kernel
Click to expand...
Click to collapse
I don't think linux distro could be a problem... maybe kernel version isn't compatible? Try using a different source.
JashanjotSidhu said:
I don't think linux distro could be a problem... maybe kernel version isn't compatible? Try using a different source.
Click to expand...
Click to collapse
Idk I have just right now running Ubuntu on VM I m downloading the files I don't think so that the problem is associated with kernel version bcos the thing is many new Android devices like one plus 3 and other many update android version devices like nexus have official nethunter support so latest android means the kernel will be upgraded to more newer version such as 3.18.xx and all so is our z2 plus to the same version ....anyways gonna give a try in Ubuntu or else have to wait till I get a proper source for kernel.
Can u suggest any good source for this project ?
I'm currently using the Oreo ROM and the source of the kernel is DDrb0h kernel which is the branch of lineage 15.1.
Also I have identified the major error which is in CROSS COMPILE step for android ndk idk why but in Kali Linux I'm not able to get CROSS COMPILE so kinda in lil problem...
JashanjotSidhu said:
I don't think linux distro could be a problem... maybe kernel version isn't compatible? Try using a different source.
Click to expand...
Click to collapse
I think the problem is associated with the kernel sources same error on ubuntu
Update
Tried my best to compile yet ran into another error
Changed the sources to latest treble one
I got new error with arm-linux-androideabi- gcc error some command is invalid ....I require a little guidance here . So kernel developers pls show me which version of ndk shld I use and sources shld I refer and what extra commands shld I run?
@Ayush Rathore.. Could you help this guy in solving his problem.. I think it's a interesting project..
SteelBodyX said:
@Ayush Rathore.. Could you help this guy in solving his problem.. I think it's a interesting project..
Click to expand...
Click to collapse
Thank you for ur suggestion. Ya I haved pm him already but didn't receive any update from him and also the work is done.I have made the changes for the project just one step I'm lagging is compiling it......then its free for distribution here.

Android 9/10/11 32bit ROM

Guys I'm tired of my camera going nuts. Can someone just create a 32 bit ROM for the Moto G5, I'll be willing to help in testing the ROM
MultiMan15 said:
Guys I'm tired of my camera going nuts. Can someone just create a 32 bit ROM for the Moto G5, I'll be willing to help in testing the ROM
Click to expand...
Click to collapse
Trees for this device are 64bit so no. Motorola haven't updated their source code for 32bit so it's not going to happen.
Also Google are ending support for all 32bit devices so it would be pointless.
There's also nothing wrong with camera on the latest android 11 build.
Make sure are on the latest retail orero stock firmware.
There's nothing wrong with the camera in my Sakura rom builds.
The battery life however on android 11 is a lot less than stock android 8 though and the boot time is a lot longer.
MultiMan15 said:
Guys I'm tired of my camera going nuts. Can someone just create a 32 bit ROM for the Moto G5, I'll be willing to help in testing the ROM
Click to expand...
Click to collapse
He never talks about 32-bit rom because it is not that it cannot be done, it is that the developers do not want to return the device tree to 32-bit, the 64-bit one has no advantage, the GCam will never work as it should, the camera stock took 4 years of bug fixes 32-bit support won't die because even Android ships at 32-bit in devices new
rtd4 said:
the 64-bit one has no advantage
Click to expand...
Click to collapse
that's plain wrong.
rtd4 said:
He never talks about 32-bit rom because it is not that it cannot be done, it is that the developers do not want to return the device tree to 32-bit,
Click to expand...
Click to collapse
1. you would also have to return the kernel to 32-bit
2. the camera problems in the end were just using the wrong blobs and not related to bitness at all
3. I am waiting for you to do it yourself instead of just complaining because that doesn't help at all
nift4 said:
that's plain wrong.
1. you would also have to return the kernel to 32-bit
2. the camera problems in the end were just using the wrong blobs and not related to bitness at all
3. I am waiting for you to do it yourself instead of just complaining because that doesn't help at all
Click to expand...
Click to collapse
Until today the rom nougat are the best in performance because they are in 32bits despite having MTP problems and Ugly Colors I do not complain much they were solid when going to 64bits in android 8.1 they killed the device completely until the beginning of this year that fixed device tree both lineageos 17.1 and mint-os are the most stable roms for cedric, it hurts that the current changes of the device tree are only sent to lineageos 18.1
nift4 said:
that's plain wrong.
1. you would also have to return the kernel to 32-bit
2. the camera problems in the end were just using the wrong blobs and not related to bitness at all
3. I am waiting for you to do it yourself instead of just complaining because that doesn't help at all
Click to expand...
Click to collapse
forget it no one is going to return the device tree of the g5 to 32-bit most users will return the device to android 7 / 8.1 because it still works so well that the only valid path is lineageos 17.1

Categories

Resources