Develop Bugs

[discussion|support|F.A.Q] Porting Ubuntu Phone OS to Defy(+)

Well this thread is dedicated about the possibilities of getting a port of ubuntu phone os. Recently displayed and would be launched around MWC 2013, Ubuntu OS will be launched for galaxy nexus! .
although there are short threads present about the topic, aim of this thread would be to provide Support/Bug-Report/F.A.Q if any port of ubuntu shows up for our phone from our great developers.
This is refreshingly new OS.
HERE IS THE LINK TO THREAD--> http://forum.xda-developers.com/showthread.php?t=2174544
I am damn sure some-one will take up this great job
Latest: Ubuntu Phone OS Porting Guide https://wiki.ubuntu.com/Touch/Porting
Some of Features of ubuntu phone:(taken from wikipedia)
OS family Unix-like
Working state Current
Source model Open source
Initial release February 2013; 30 days' time
Available language(s) Multilingual
Update method Ubuntu Software Center (+ APT, …)
Package manager dpkg
Supported platforms i386, ARM
Kernel type Monolithic (Linux kernel)
Userland GNU
Default user interface Unity shell
So what may be the hindrances:
What kernel version is it based on
will it require bootloader unlock ;-(
UBUNTU PHONE OS
since it is yet to be released this is an open discussion, if any developer takes this project for defy, this thread will be a F.A.Q/support/Bugreport thread (if ever it happens )

i'm here for tests.
i'm not a developer, but you guys can count with my defy+ for tests. I really would like to have ubuntu phone on my defy+.

I'd love to see Ubuntu Phone OS on Defy. First of all it's based on Android kernel so there wouldn't be much difficulty for it. The sources should be out next month. Also we'll need to find a method to dual boot with a custom kernel because it's less likely for someone to use it as a primary OS.
Sent from my MB526 using xda premium

Will be very nice to see ubuntu working natively on ours Defy but the specification for minimal resources is beyond the possibilities of defy. So it can be ported but will be very laggy IMHO.

swapnil360 said:
I'd love to see Ubuntu Phone OS on Defy. First of all it's based on Android kernel so there wouldn't be much difficulty for it. The sources should be out next month. Also we'll need to find a method to dual boot with a custom kernel because it's less likely for someone to use it as a primary OS.
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
what is ubuntu's packaging method? i mean the OS image?

pgreed said:
Will be very nice to see ubuntu working natively on ours Defy but the specification for minimal resources is beyond the possibilities of defy. So it can be ported but will be very laggy IMHO.
Click to expand...
Click to collapse
Not that beyond. Min specs (as stated here) only ask 4-8GB internal storage for an entry-level ubuntu phone, everything else (CPU clock, minimum RAM and multitouch capability) already cover our phone. Plus, as far as I remember (though I can easily be wrong on this, since I haven't touched an Ubuntu machine for months, now), this OS (specially considering it was specifically deployed for running on phones) doesn't take more than 2GB when installed. Again, I can be wrong, BUT... What about multiboot? A class 6 8GB card (or even a class 4, like the one included with our phones) may do the job, and we will still be able to boot CM10+ and ask silly questions to Google Now.
vedhasd said:
what is ubuntu's packaging method? i mean the OS image?
Click to expand...
Click to collapse
I may be wrong, but I think I read in more than one place it'll be available as a flashable zip. Since the folks there at Canonical were able to boot this little beauty in a Galaxy Nexus, and they intend to release the GNx version (without many workarounds needed to install) before the end of january, I think it's pretty safe to bet on a recovery-flashable zip file. Last, but not least, I think an install script (like the ones devs use in current Android flashable zips) may be slightly modified to install Ubuntu from a system image, specially if you consider Aroma-based installers are doing wonders in matter of personalizing Android installations. This not considering (and in this matter I have absolutely no idea) the possibility of the disk installer of linux distributions be already running scripts very similar to those used on Android flashable zips to install desktop OSs on computers. Devs will be better suited to tell about the latter.
P.S.: if anyone there tried Android-x86, you guys can see the installable image is very similar to an Ubuntu (or any other linux) installation zip. This might lead us in the opposite direction, looking at which modifications were made for the installer to work with Android, and reversing them for a Ubuntu installer to work in a flashable zip.

K3n H1mur4 said:
Not that beyond. Min specs (as stated here) only ask 4-8GB internal storage for an entry-level ubuntu phone, everything else (CPU clock, minimum RAM and multitouch capability) already cover our phone.
...
Click to expand...
Click to collapse
Is nice that you are very optimistic with this. I wanna be so but ... the entry level processor is a Cortex9 ! which is more powerfull than ours and Ubuntu is based on 3.4x kernel and necesitate a bigger system ROM to install (ours is ~350MB). Anyhow will wait and see and ... speculate.

pgreed said:
Is nice that you are very optimistic with this. I wanna be so but ... the entry level processor is a Cortex9 ! which is more powerfull than ours and Ubuntu is based on 3.4x kernel and necesitate a bigger system ROM to install (ours is ~350MB). Anyhow will wait and see and ... speculate.
Click to expand...
Click to collapse
It may depend on how far our devs will be able to strip down the OS for our phone, I think we may not require full fledged running desktop compatibility but it still depends by what extent we can strip down the footprint!
Sent from my MB525 using xda premium

Ubuntu Phone OS Porting Guide https://wiki.ubuntu.com/Touch/Porting

red lens defy+ guinea pig
swapnil360 said:
I'd love to see Ubuntu Phone OS on Defy. First of all it's based on Android kernel so there wouldn't be much difficulty for it. The sources should be out next month. Also we'll need to find a method to dual boot with a custom kernel because it's less likely for someone to use it as a primary OS.
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
'm not developer but my red lens defy+ is available as a guinea pig.
Then I can make rather a system as primary OS alpha and p500 use my day-to-day
sorry my english

It would be nice if we had more one option rom. Live freedom!

are there some news? i've founded this video, but I can't understand if this is related to the thread in android development...
in youtube: watch?v=hglLF3dM8Zk (i'm not allowed to post link ^^ )

Kayant had released an alpha preview.. but the ubuntu project will be helpful iff we some how boot up 3.0.x kernel with RIL
Sent from my MB526 using xda premium

Android M Developer Preview for Xperia Z1 [July-04]

Introduction
Hello,
Recently Sony released their source binaries for the Android M Developer Preview, so I decided to build and share it . Keep in mind this is a Developer Preview. It's just to give an idea of how the new Android M looks like. Both the camera and modem aren't included by Sony, so you can't use those.
Click to expand...
Click to collapse
Not included
Modem
Camera
Click to expand...
Click to collapse
Installation instructions
Make a back-up and store it outside of your phone.
Connect the device to your computer in Fastboot mode, by pressing volume up while inserting the USB cable.
In the terminal on your computer type the following commands:
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata.img
Now when you disconnect your device from the computer and start it, it will be running AOSP.
Click to expand...
Click to collapse
XDA:DevDB Information
AOSP M, ROM for the Sony Xperia Z1
Contributors
aquaboy11
Source Code:
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/list-of-devices-and-resources/
https://android.googlesource.com/platform/manifest/+/android-m-preview
https://github.com/sonyxperiadev/
ROM OS Version: Android M
ROM Firmware Required: C6903
Based On: AOSP
Version Information
Status: Testing
Created 2015-06-26
Last Updated 2015-07-04

good for trying how M looks but hope some one will come with a patch to make modem work... I tried to build it too.. but reposync will take for ever

jos_031 said:
good for trying how M looks but hope some one will come with a patch to make modem work... I tried to build it too.. but reposync will take for ever
Click to expand...
Click to collapse
I don't think anyone wants to port the modem and camera to a Developer Preview. We will have to wait for Sony to do that.

Think the modem is intentionally disabled from the article i read, interesting that its using the 3.4 kernel though, i would have thought 4.x or at least a newer 3.x.. Did not spot a link to the sources(?), i really like the way Sony Ericsson has managed these projects ( the Z series), not only will it benefit us in the future when they eventually deprecate the project, but actually including the community and promoting development rather then hampering it by all means possible, reason enough for me to recommend the series, me like :>

threader said:
Think the modem is intentionally disabled from the article i read, interesting that its using the 3.4 kernel though, i would have thought 4.x or at least a newer 3.x.. Did not spot a link to the sources(?), i really like the way Sony Ericsson has managed these projects ( the Z series), not only will it benefit us in the future when they eventually deprecate the project, but actually including the community and promoting development rather then hampering it by all means possible, reason enough for me to recommend the series, me like :>
Click to expand...
Click to collapse
Oops, I forgot to include the sources . Will add them now .

I tested it, and think it's only more buggy lollipop, which sony/google called "m". Any new features like multiwidow from m preview, API 22 (from 5.1), old lockscreen, lollipop easter egg, and strange android version 5.1.51
Bluetooth sharing gives FC. When Sony give us a full working clear aosp ?
Wysłane z mojego Xperia Z1 przy użyciu Tapatalka

It's not Sony's fault. Google hasn't made the new APIs open source yet. They have just given build instructions for the aosp M preview branch.
I wouldn't recommend using this, as there's absolutely no difference from Lollipop as far as I've seen.

aquaboy11 said:
Oops, I forgot to include the sources . Will add them now .
Click to expand...
Click to collapse
Read trough the build guide.
It's supposed to use the 3.10 kernel. I'm having all sorts of problems with this kernel though, i havent gotten it booting on the device yet.. .Just says missing dtb no matter what i do .. even creating the zImage-dtb trough config or manually results in fastboot saying no dtb...
<project path="kernel/sony/msm" name="kernel" groups="device" remote="sony" revision="aosp/AU_LINUX_ANDROID_LA.BF64.1.2.1_RB1.05.00.02.019.067" />

threader said:
Read trough the build guide.
It's supposed to use the 3.10 kernel. I'm having all sorts of problems with this kernel though, i havent gotten it booting on the device yet.. .Just says missing dtb no matter what i do .. even creating the zImage-dtb trough config or manually results in fastboot saying no dtb...
<project path="kernel/sony/msm" name="kernel" groups="device" remote="sony" revision="aosp/AU_LINUX_ANDROID_LA.BF64.1.2.1_RB1.05.00.02.019.067" />
Click to expand...
Click to collapse
You can try to put the kernel sources into a build environment, i.e., any cm based rom, do build envelope, launch your device, then do mka bootimage and see what happens. But generally, this development has been nothing short of grossly pathetic. Linux now has fully working 4.x kernels. I don't necessarily blame developers primarily, as the main culprits are Sony and Google. However, oems are not more cooperative with linux developers than with android devs, yet linux is ages ahead not only in terms of kernels, os, but also in creating open source firmware...

optimumpro said:
You can try to put the kernel sources into a build environment, i.e., any cm based rom, do build envelope, launch your device, then do mka bootimage and see what happens. But generally, this development has been nothing short of grossly pathetic. Linux now has fully working 4.x kernels. I don't necessarily blame developers primarily, as the main culprits are Sony and Google. However, oems are not more cooperative with linux developers than with android devs, yet linux is ages ahead not only in terms of kernels, os, but also in creating open source firmware...
Click to expand...
Click to collapse
True, replacing the kernel directory and running a script to remake the headers from that kernel used to build android is the way to port android to a new kernel. I'm not building a rom atm though, i'm building the kernel only (bellow). I suspect the 3.10 kernel and newer require an updated bootloader.. However, in what way updating this would affect my ability to boot 4.4.4 i do not know, so im a bit weary.
Code:
ARCH=arm CROSS_COMPILE="$home"/dev/sdk/linaro-gcc-4.9-abe-gnueabihf/bin/arm-none-linux-gnueabihf- make -j8
dtbTool -o dt-0.img -s 2048 -p/scripts/dtc/ arch/arm/boot/ ( changed arch/arm/boot/ to arch/arm/boot/dtb in later kernels)
mkbootimg --cmdline "androidboot.hardware=qcom user_debug=31 maxcpus=2 msm_rtb.filter=0x37 ehci-hcd.park=3 lpj=192598 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y vmalloc=400M" --base 0x00000000 --kernel "$home"/dev/nix/xperia/xperia-c6903-z1-source-final-4.4.4-0/arch/arm/boot/zImage --ramdisk "$home"/nix/xperia/boot-xperia-c6903-z1-sony-kernel-0/157/kernel_S1-SW-LIVE-6732-PID1-0005-MMC.elf.ramdisk --ramdisk_offset 0x02000000 -o boot-0.img --dt dt-0.img --tags_offset 0x01E00000
Also spotted this (Recovery mode now available for a range of unlocked Xperia devices) http://developer.sonymobile.com/201...for-a-range-of-unlocked-xperia-devices-video/ , however, my device (thankfully) runs Customized NCB_1276-9897 ( scandinavia ), so i dont know how well it would take to a UK rom, which has been updated.
As i mentioned before elsewhere, porting to a newer kernel ought be relatively easy, 4.1 would be a natural choice, its LTS and i suspect Android M or so will probably land there..

threader said:
True, replacing the kernel directory and running a script to remake the headers from that kernel used to build android is the way to port android to a new kernel. I'm not building a rom atm though, i'm building the kernel only (bellow).
Click to expand...
Click to collapse
I know you are not building a rom, but my point is it is much better to compile a kernel in a native (to your device) environment with all the tools already there. You also have your native ramdisk, as opposed to some generic one. I have built quite a few kernels using this method and it has yet to fail once...

True, as it stands now, the way im assembling the boot.img it's incompatible with certain installers for Multibot, using the method you described would avoid that entirely.
Spotted the nexus 5 and 7 are on 4.2.2 for android m. I guess 3.10 is just a step.

no links?

OptidroidPlus said:
no links?
Click to expand...
Click to collapse
Downloads tab on XDA Website (not app)...
I see an update...any changes yet? Or is it still lollipop?

drakonizer said:
Downloads tab on XDA Website (not app)...
I see an update...any changes yet? Or is it still lollipop?
Click to expand...
Click to collapse
give me links please? i am new in xda.. thanks

drakonizer said:
Downloads tab on XDA Website (not app)...
I see an update...any changes yet? Or is it still lollipop?
Click to expand...
Click to collapse
No, it's still a buggy Lollipop version. The update just includes the latest commits and changes made to the project.

OptidroidPlus said:
give me links please? i am new in xda.. thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/devdb/project/?id=10518#downloads

Thanks!!

Android M Preview 2 is coming ? http://www.droid-life.com/2015/07/09/android-m-developer-preview-2-now-available/
Sent from my Xperia Z1 using Tapatalk

danny19901 said:
Android M Preview 2 is coming ? http://www.droid-life.com/2015/07/09/android-m-developer-preview-2-now-available/
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
I doubt Google is going to update AOSP sources...one can only hope. @aquaboy11 Could you post a changelog of any noticeable difference when you update your builds? Thanks...

[ROM][AOSP][7.1/8.1 EXP][K3.4][Repartition] Unlegacy Android Project

The Unlegacy Android Project
TF201 | TF300T/TG/TL | TF700T​
Introduction
Unlegacy Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for the Asus Transformer Series include:
- Linux kernel 3.4.y (currently 3.4.113)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data and /cache)
Installation
You must have NvFlash backup. It is MANDATORY!
You need to use modified TWRP recovery that works with updated F2FS. If you're planning to install GApps, be sure to read the second post!
Problems
Non working/Known bugs:
- GPS; - need a device owner to configure!
- Camera (both);
- Dock special keys (top row);
- Modem on TG and TL;
- GUI crashes; - occure less often
Currently, no one from Unlegacy Team, has TF300T/TG/TL device. Help in developing or device donation would be highly appreciated.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds Else is enclosed in downloads.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed (or similar) to add extra features.
As usual, feedback is appreciated
Contacts
You may join Telegram development group, where all fresh staff is published and tests are made.
XDA:DevDB Information
Unlegacy Android Project, ROM for the Asus Transformer TF300T
Contributors
Clamor, Ziyan
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Bootloader 4.2 JB
Based On: AOSP
Version Information
Status: Beta
Created 2018-02-18
Last Updated 2018-10-17

Installation gide (for those who uses F2FS)
Before installing ROM you need to update your current recovery with this TWRP, else you will get a bootloop with next format from fastboot. Install zip from your current recovery and reboot into your current system. Than boot into new recovery and install ROM (with factory reset).
Currently 3.4 kernel isn't stable enough for daily use. You may use updated 3.1 _that16 kernel, it works fine with this ROM. To make wifi work with _that16 kernel just move nvram_nh615.txt from system/etc to data/misc/wifi and rename to nvram.txt
You may use KatKiss 7.1 if you want, but you must flash a _that16 kernel every time after flashing KatKiss ROM. Else you will get a bootloop with next format from fastboot.
If you want to go back to ordinary TWRP, you need to make a format from fastboot, flash TWRP and make formats from there as well.

REPARTITION and TREBLE
I worked on this for few last weeks to make it stable and simple enough to any user to install this update. As usual NvFlash is MANDATORY! TF300TG/TL users shouldn't use this as it can harm your tablet.
So, UA_Bootloader.zip includes latest JB4.2 10.6.1.27.5 bootloader, modified TWRP [email protected] from Downloads section and my new partition table. It's main benefits are /system partition increased to 1GB and /vendor partition. This means that we may install bigger gapps packages and support of TF's may be extended plus having /vendor partition gives us at least hardware support for Project Treble, even if there is no 8.1 builds currently.
Before installation copy everything from tablet on PC, else all you data will be lost! To install this update just install it via TWPR and when flashing is finished press reboot into system. Than wait till blue line gets to the end and tablet reboots. Tablet will than stuck into ASUS screen with Device is Unlocked sign in top left corner. Than reboot manually into recovery and format /system to ext4; /cache to ext4 or f2fs; /data to ext4 or f2fs and you are good to go.
New partition table is compatible with all existing ROMs for TF's. If you flash ROM with system in .img file you need after flash into recovery do Wipe -> System -> Advanced Wipe -> Change or resize partition -> Resize filesystem. If you want to restore 4.2 state you can flash Stock or Bootloader 4.2 attached in Downloads section.

How is this project going? and why you choose android 7.1? instead of the new android 8.0? because i would definitely want to help with a android 8.0/8.1 rom

androidjel said:
How is this project going? and why you choose android 7.1? instead of the new android 8.0? because i would definitely want to help with a android 8.0/8.1 rom
Click to expand...
Click to collapse
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.

Clamor said:
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Click to expand...
Click to collapse
Ah okay thats clear, a other question i want to try this rom but there are no downloads.
I want to test for you if you want? :good:

androidjel said:
Ah okay thats clear, a other question i want to try this rom but there are no downloads.
I want to test for you if you want? :good:
Click to expand...
Click to collapse
All needed files you can find in Downloads tab on top of this thread

Clamor said:
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Click to expand...
Click to collapse
Clamor said:
All needed files you can find in Downloads tab on top of this thread
Click to expand...
Click to collapse
I see tnx, what do you want to know or what do you want to have tested to help you?
and Btw which TWRP is that? i have the last one already installed.

androidjel said:
I see tnx, what do you want to know or what do you want to have tested to help you?
and Btw which TWRP is that? i have the last one already installed.
Click to expand...
Click to collapse
Nothing, you may install Rom to see current project progress (If you have TF300T there will be no sound). For further developement test device is needed, or a developer with TF300T(better solution). Mostly all major functions are fixed, see buglist, and 3.4 works on all transformers on Tegra 3.
That is KANG TWRP with support of updated F2FS

TF300T users, if you are interested in further developement, please help me with debuging sound driver. I need a tester, with TF300T and some free time.

Clamor said:
TF300T users, if you are interested in further developement, please help me with debuging sound driver. I need a tester, with TF300T and some free time.
Click to expand...
Click to collapse
I am more than willing to be a tester if you want. Heck, I will even find a cheap TF300T to load only this on. My mornings are relatively free as my business doesn't pick up till noon or so. Just PM me specifics of what you need. Any more development for our tablets is a blessing as far as I am concerned

I would love to help debugging, testing and developing. I'm currently in possession of a tf300t with dock and an me301t. Do you think it will be possible to port this to the ME301t?

@gs-crash-24-7 please write me in PM. Actually ME301t was supported at early stages of 3.4 bringup. I fully excluded it from board since I couldn't test it and Memopad parts made transformers board really messy. I had enough problems with TF stuff at that moment.
3.4 kernel porting and repartitioning before were just a dream, but now they are real. Memopad bringup depends only on your interest in it.

Oreo 8.1
Yesterday I have quickly build 8.1 ROM for transformers. There doesn't work almost anything and I won't have excess to my TF201 for a while to fix stuff Rom can be booted with same requirements as N roms. Here is first build. Please don't post any issues/logs here from O for now. I know already about all major issues.

I have some good news. Here is mostly working Oreo build with issues from N + non working bt. I'm still working on fixing staff so this isn't last build.
P.S. Remove system/lib/hw/bluetooth.default.so to avoid constant bt crash

Any possibility of sharing the 3.4 kernel supporting the ME301t...I have that little bugger and the latest software updates from my TV provider and Netflis like programs are all KK dead for the most part. Having unlegacy on the Me301t would be a dream come true and would avoid trashing this one and getting a new one just because I want to see some shows or TV. Thank you for your work. I will assist to the best of my knowledge.

@AlphaDivxMovies nothing impossible, but first of all, I have no MemoPad and it's hardware isn't that close as my Prime is with TF300T. Second is that I put huge amount of my time and afforts in porting transformer board so I have no desire at all to do this once more time, I can help with suggestions but actual development will lie on your shoulders.
P.S. To just boot rom atm you would need only a kernel port, ROM is mostly compatible. Almost all drivers memopad uses are already included. You may contact @gs-crash-24-7 as well, he has memopad and if he agrees, than work in pair is much more simple.

@Clamor , Where is the oreo version? https://builds.unlegacy-android.org/ here i could only find the 7.1.2 version.
The other downloads in this post dont work anymore (oreo).

@androidjel sure, since there are no stable enough builds on O and even N builds aren't for everyday use with 3.4 kernel. I didn't launch O builds for a long time.

Clamor said:
@androidjel sure, since there are no stable enough builds on O and even N builds aren't for everyday use with 3.4 kernel. I didn't launch O builds for a long time.
Click to expand...
Click to collapse
@Clamor But could you launch a O build again? maybe i could try to help, I have some time to do that at the moment.

Linux Kernel 4.x ?

Thanks for checking out the thread - I'll keep this short, sweet and consise.
Is it possible to use the Linux Kernel 4.x on a Malin device? If so - has it been done before?
Any information will be appreciated,
Thanks.
- Ian.

Mr Ian said:
Thanks for checking out the thread - I'll keep this short, sweet and consise.
Is it possible to use the Linux Kernel 4.x on a Malin device? If so - has it been done before?
Any information will be appreciated,
Thanks.
- Ian.
Click to expand...
Click to collapse
Searched this thread, or read this?

I have checked the majority of Roms and Kernals available on the development section but nothing.
I just had a quick read through the other link and subsequent links from that too and have taken from it that there is a set 'requirement' from Google for the Kernal to be 4.x from 2017 (this model released in 2016!) and that Android P and Q's API level should be 4.x but apparently they didn't bother too follow their own rule as even throughout P and now on Q we are still using Kernal 3.x .
I'm not apt enough too be able to port a Kernal myself, But am questioning wether just simply Flashing say... Pixel 2's 4.x kernal for Android 10
Sounds silly then I type it out loud.
But thanks for the information and digging for me!
I appreciate the time and effort.
- Ian.
p.s. I only search for LK4.X to do with using an exploit for iOS as you can read in my recent post about arm64 checkra1n.

Mr Ian said:
I have checked the majority of Roms and Kernals available on the development section but nothing.
I just had a quick read through the other link and subsequent links from that too and have taken from it that there is a set 'requirement' from Google for the Kernal to be 4.x from 2017 (this model released in 2016!) and that Android P and Q's API level should be 4.x but apparently they didn't bother too follow their own rule as even throughout P and now on Q we are still using Kernal 3.x .
I'm not apt enough too be able to port a Kernal myself, But am questioning wether just simply Flashing say... Pixel 2's 4.x kernal for Android 10
Sounds silly then I type it out loud.
But thanks for the information and digging for me!
I appreciate the time and effort.
- Ian.
p.s. I only search for LK4.X to do with using an exploit for iOS as you can read in my recent post about arm64 checkra1n.
Click to expand...
Click to collapse
It is possible, if the out-of-tree drivers and fixes from 3.18.x are somehow ported to 4.x.
Theoretically, it's nigh-on impossible except for Google's engineers who have Qualcomm's help.
Practically, it is indeed possible. Several devices were mainlined before, including the Galaxy Note II and some variant of the Amazon Kindle/Fire tablet.

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