I see many tutorials talking about how to compile a rom from source (with an already existing device tree, vendor tree etc), but how do you go about making a custom ROM (and TWRP) from scratch? I already have programming experience with quite some programming languages (including Java, which I heard is important for custom ROM dev), but I can't figure out looking at device trees why people do certain commits.
Oh and by the way, would the process be much different on a treble device? The device I want to build for (huawei P Smart) supports project Treble.
ahmed.al said:
Oh and by the way, would the process be much different on a treble device? The device I want to build for (huawei P Smart) supports project Treble.
Click to expand...
Click to collapse
Hi! If your phone supports "Treble", you can directly boot a GSI (Generic System Image) build of any custom ROM. Check "Phh-Treble". Treble means having /vendor partition outside of the traditional /system partition. Before /vendor used to be mounted by using /system/vendor. Good Luck!
What's the phone's kernel version currently? If the SoC is released before 2017 it would most probably be 3.18 or if it released after 2017 it must be 4.4+.
pvineeth97 said:
Hi! If your phone supports "Treble", you can directly boot a GSI (Generic System Image) build of any custom ROM. Check "Phh-Treble". Treble means having /vendor partition outside of the traditional /system partition. Before /vendor used to be mounted by using /system/vendor. Good Luck!
What's the phone's kernel version currently? If the SoC is released before 2017 it would most probably be 3.18 or if it released after 2017 it must be 4.4+.
Click to expand...
Click to collapse
I changed my mind. I think a Moto G6 (plus) would be a better buy. It's going to be released in 3 days (don't know if you can buy it right away). Anyway since it's so new it should be 4.4+
pvineeth97 said:
Hi! If your phone supports "Treble", you can directly boot a GSI (Generic System Image) build of any custom ROM. Check "Phh-Treble". Treble means having /vendor partition outside of the traditional /system partition. Before /vendor used to be mounted by using /system/vendor. Good Luck!
What's the phone's kernel version currently? If the SoC is released before 2017 it would most probably be 3.18 or if it released after 2017 it must be 4.4+.
Click to expand...
Click to collapse
This is not the case. The only reason those boot on those devices is because it was made to. There are things the users are not being told to get them behind this. Even though it will not do a lot for updates or anything else.
ahmed.al said:
I changed my mind. I think a Moto G6 (plus) would be a better buy. It's going to be released in 3 days (don't know if you can buy it right away). Anyway since it's so new it should be 4.4+
Click to expand...
Click to collapse
Check if the SoC is released in 2017. If SoC is released in 2017 or later then it should have Linux kernel 4.4+.
---------- Post added at 09:04 PM ---------- Previous post was at 08:59 PM ----------
zelendel said:
This is not the case. The only reason those boot on those devices is because it was made to. There are things the users are not being told to get them behind this. Even though it will not do a lot for updates or anything else.
Click to expand...
Click to collapse
Treble can guarantee at least 4 - 5 major updates for phones having it. Even if you don't get updates you can flash a GSI build of any custom ROM.
Problems come when implementing treble because it is not that easy to implement it. Even very old phones having msm8916 are getting treble support now unofficially using Phh-Treble.
pvineeth97 said:
Check if the SoC is released in 2017. If SoC is released in 2017 or later then it should have Linux kernel 4.4+.
---------- Post added at 09:04 PM ---------- Previous post was at 08:59 PM ----------
Treble can guarantee at least 4 - 5 major updates for phones having it. Even if you don't get updates you can flash a GSI build of any custom ROM.
Problems come when implementing treble because it is not that easy to implement it. Even very old phones having msm8916 are getting treble support now unofficially using Phh-Treble.
Click to expand...
Click to collapse
Is that what you think? You do know the only reason it is working right is is because of the available kernels out. Just because aosp has to load for the oem on say 9.0 that doesn't mean the oem has to release the kernel that allows aosp to boot.
I along with many of the devs have been following this closely. Notice how not many are really working on it outside of remote devices. Things like honor and Xiaomi.
Only time will tell how useful it is. To be honest I have not seen anything major. It is pretty much the same as last year. Sure there is one image for some devices but that means nothing. Custom rom devs all will have to make their own anyway. So not a big deal.
zelendel said:
Is that what you think? You do know the only reason it is working right is is because of the available kernels out. Just because aosp has to load for the oem on say 9.0 that doesn't mean the oem has to release the kernel that allows aosp to boot.
Click to expand...
Click to collapse
Correct me if I'm wrong, but aren't OEMs forced to release their kernel source? Since Android is licensed under the GPL.
ahmed.al said:
Correct me if I'm wrong, but aren't OEMs forced to release their kernel source? Since Android is licensed under the GPL.
Click to expand...
Click to collapse
Only for OS they ship out. If they, never release a build say aosp then they are not required to post it. There are many internal kernel builds that never see the light of day to users.
Again. Android is not licensed under the gpl. Only the kernel is. Android is under the apache license. Meaning they own all code. They use. The reason for no source for this gs like TouchWiz, sense or any of the other oem distros.
So in theory. The oem could easily pass by getting it to boot aosp in, house and never release the kernel they used.
zelendel said:
Only for OS they ship out. If they, never release a build say aosp then they are not required to post it. There are many internal kernel builds that never see the light of day to users.
Again. Android is not licensed under the gpl. Only the kernel is. Android is under the apache license. Meaning they own all code. They use. The reason for no source for this gs like TouchWiz, sense or any of the other oem distros.
So in theory. The oem could easily pass by getting it to boot aosp in, house and never release the kernel they used.
Click to expand...
Click to collapse
I see, thank you.
Anyway, I saw somewhere mentioned that little changes should be made to the GSI (if issues are present). Since this is much different from traditional porting (with a device, vendor and kernel tree), where should the changes be made? There are no docs or anything inside this repo.
ahmed.al said:
I see, thank you.
Anyway, I saw somewhere mentioned that little changes should be made to the GSI (if issues are present). Since this is much different from traditional porting (with a device, vendor and kernel tree), where should the changes be made? There are no docs or anything inside this repo.
Click to expand...
Click to collapse
I am not using his work so I am not sure. There are some that are doing it on our own.
zelendel said:
Only for OS they ship out. If they, never release a build say aosp then they are not required to post it. There are many internal kernel builds that never see the light of day to users.
Again. Android is not licensed under the gpl. Only the kernel is. Android is under the apache license. Meaning they own all code. They use. The reason for no source for this gs like TouchWiz, sense or any of the other oem distros.
So in theory. The oem could easily pass by getting it to boot aosp in, house and never release the kernel they used.
Click to expand...
Click to collapse
True that. Most of the Chinese companies don't release their kernel sources and it seems like FSF doesn't care much about it.
---------- Post added at 01:08 PM ---------- Previous post was at 01:04 PM ----------
ahmed.al said:
I see, thank you.
Anyway, I saw somewhere mentioned that little changes should be made to the GSI (if issues are present). Since this is much different from traditional porting (with a device, vendor and kernel tree), where should the changes be made? There are no docs or anything inside this repo.
Click to expand...
Click to collapse
There will never be a guide on it since it is not easy to write completely about porting Android in a guide and also it depends on hardware, OEM specific changes and upstreaming the kernel for newer Android version (OMG, I did this once yet I ended up having kernel build errors but afterwards I applied specific commits on top of Nougat kernel for OREO and it worked!).
Just 2 days back I built new Android 8.1 ROM for LG G4c and I will trebelize it in future,
https://forum.xda-developers.com/g4/development/rom-lineageos-15-1-t3768654
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pvineeth97 said:
There will never be a guide on it since it is not easy to write completely about porting Android in a guide and also it depends on hardware, OEM specific changes and upstreaming the kernel for newer Android version (OMG, I did this once yet I ended up having kernel build errors but afterwards I applied specific commits on top of Nougat kernel for OREO and it worked!).
Just 2 days back I built new Android 8.1 ROM for LG G4c and I will trebelize it in future
Click to expand...
Click to collapse
I stopped following your g4c custom ROMs, because I have replaced my phone with an iPhone 6s (temporary, cause IOS is gross). Anyway how in the world are you going to trebelize it? Trebilizing it would require changing partitions, which is a pretty dangerous thing to do.
ahmed.al said:
I stopped following your g4c custom ROMs, because I have replaced my phone with an iPhone 6s (temporary, cause IOS is gross). Anyway how in the world are you going to trebelize it? Trebilizing it would require changing partitions, which is a pretty dangerous thing to do.
Click to expand...
Click to collapse
@Anghirrim told me long back that you replaced your phone.
So I didn't bother about it much. I was just showing you that I could boot Oreo and next I will port P without treble on a msm8916 device.
I need not create any new partition. There are some patches that I need to apply for the kernel and use Oreo blobs of a known msm8916 device then I will proceed with other things I need to do. If I need to create one there is cust/ partition which is handy for storing vendor blobs. I am not planning on it yet. I will just merge newer patches for P and modify the device trees for newer Android versions.
pvineeth97 said:
@Anghirrim told me long back that you replaced your phone.
So I didn't bother about it much. I was just showing you that I could boot Oreo and next I will port P without treble on a msm8916 device.
I need not create any new partition. There are some patches that I need to apply for the kernel and use Oreo blobs of a known msm8916 device then I will proceed with other things I need to do. If I need to create one there is cust/ partition which is handy for storing vendor blobs. I am not planning on it yet. I will just merge newer patches for P and modify the device trees for newer Android versions.
Click to expand...
Click to collapse
Sounds nice and all, but shouldn't you rather focus more on make your ROMs actually usable? Last time I checked your g4c ROMs, they were full of bugs and there were very few things working.
ahmed.al said:
Sounds nice and all, but shouldn't you rather focus more on make your ROMs actually usable? Last time I checked your g4c ROMs, they were full of bugs and there were very few things working.
Click to expand...
Click to collapse
Ohh when did you check? You must be dreaming... Please check my threads before you speak... I already fixed everything in Nougat for G4c this March itself even the sound and camera. Now will complete LOS 15.1 before I go to USA in 3 months.
My latest LOS 14.1 builds for March/April which are very stable (already tested by Paul, DonOleq and Anighirrim). Even Anghirrim flashed my AEX ROM on his wife's G4c phone because he liked it a lot and it is very stable with SELinux Enforced. It's their daily driver now. It's your loss if you didnt check my latest builds.
On heavy usage of Nougat ROM on G4c some lags are encountered because of limited RAM - 1 GB and slower flash memory.
https://forum.xda-developers.com/g4/development/rom-lineageos-14-1-t3668489
pvineeth97 said:
Ohh when did you check? You must be dreaming... Please check my threads before you speak... I already fixed everything in Nougat for G4c this March itself even the sound and camera. Now will complete LOS 15.1 before I go to USA in 3 months.
You keep telling me right - "Check before you speak". Don't be a hypocrite.
https://forum.xda-developers.com/g4/development/rom-lineageos-14-1-t3668489
Click to expand...
Click to collapse
No need to be so mad lol. A simple "I've already fixed the bugs" would've been enough.
ahmed.al said:
No need to be so mad lol. A simple "I've already fixed the bugs" would've been enough.
Click to expand...
Click to collapse
Again check my post xD. I am not at all mad/angry lol.
Related
EDIT: We got it! It boots. But some things like RIL and audio are not working, but we'll get this sorted out soon.
Official thread here: http://forum.xda-developers.com/opt...opment/rom-cyanogenmod-12-1-lg-l3-ii-t3297897Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
Shared L1/L3/L7 II files for CM12.1: https://github.com/TeamVee/android_device_lge_vee-common/tree/cm-12.1
We also have a build of CM12.1 recovery for E430 by me. Nevermind, broken.
L5's device tree for CM12.1: https://github.com/aidasaidas75/android_device_lge_e610
L5's vendor propretiary files for CM12.1: https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
What do we probably need?
A device tree for CM12.1 for L3 IINot needed.
Vendor files for CM12.1 for L3 IINot needed.
Lollipop kernel.Not needed.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
EDIT: I managed to build CM12.1 for LG L3 II, but I don't know if it's working or not - download here and tell me: https://www.androidfilehost.com/?fid=24345424848488130
Everyone, if you can help us create CM12.1, PM me your Telegram username (a great IM), I'll add you to a group chat. @aidasaidas75 @IGGYVIP and other devs are welcome.
dadziokPL said:
Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
We also have a build of CM12.1 recovery for E430 by me. It's the only thing we can build with the local manifest. Download here: https://mega.nz/#!Io0xxBrR!gCin0V8pDZ_-PqAGTC05PfUEWTbdLhgqdBBMjnBrhdI (I would put it in the attachments, but it's 0.43 MB too big... Dammit :/
What do we probably need?
A device tree for CM12.1
Vendor files for CM12.1
Lollipop kernel.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
Click to expand...
Click to collapse
First you forgeted https://github.com/TeamVee/android_device_lge_vee-common and second i will still here if anyone need, i builded CM12.1 but, without any reason, the ROM not boot, but i not tried again.
Possible, maybe, i try to build this again after update of MK.
And my last TWRP is from CM12.1
Caio99BR said:
First you forgeted https://github.com/TeamVee/android_device_lge_vee-common and second i will still here if anyone need, i builded CM12.1 but, without any reason, the ROM not boot, but i not tried again.
Possible, maybe, i try to build this again after update of MK.
And my last TWRP is from CM12.1
Click to expand...
Click to collapse
Yeah, it's that recovery I built Also, I can't test ROMs for L3 II anymore, I changed to Windows Phone But I think my cousin still has my old L3 II. I'll see. BTW I got a new PC, with a quad-core Intel Core i5-4460, and I set up a VM on it, so can build and build and build BTW You don't have to build, it's not building...
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
IGGYVIP said:
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
Click to expand...
Click to collapse
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Need more info and need a dev
dadziokPL said:
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Click to expand...
Click to collapse
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
IGGYVIP said:
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
Click to expand...
Click to collapse
Ohh, secure boot, alright. I see.
I heard that Lollipop actually runs better than KitKat, and it was optimized for devices with 512 MB of RAM.
At least we can try and get it to build. We can build a recovery, which is a first step according to the porting wiki
So, I was right, we need device files, vendor files, and a kernel for Lollipop?
If Caio could tell us where he got the files for KitKat, we could do something....
IGGYVIP said:
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
Click to expand...
Click to collapse
First only the Adreno is not updated, because of vsync is broken and new Adreno Blobs use hwcomposer and this is broken because vsync. When i tried to test in KK with new Adreno Blobs this happened:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Second from L5, and yes but @aidasaidas75 confused all commits, and not said the recipe to anyone.
And last i have thought this but no way to change this, the display driver of bootloader is hard edited by LG, yes i tried.
Note: No one build can make a brick of device, only if fstab is edited
dadziokPL said:
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Click to expand...
Click to collapse
And not say drivers, say vendor blobs or kernel drivers, this not is windows
IGGYVIP said:
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
Click to expand...
Click to collapse
I think you wanted to say the kernel and ramdisk.
Use "@" i will see this in seconds
I used L5/L7/MSM7x27a-Common/and some others msm7x27a devices
I think this cant be able to daily usage, but with DualBootPatcher, all will be possible.
I have through this too, but the Android Wear saved us , and if this work is a good progess, btw the last.
dadziokPL said:
Ohh, secure boot, alright. I see.
I heard that Lollipop actually runs better than KitKat, and it was optimized for devices with 512 MB of RAM.
At least we can try and get it to build. We can build a recovery, which is a first step according to the porting wiki
So, I was right, we need device files, vendor files, and a kernel for Lollipop?
If Caio could tell us where he got the files for KitKat, we could do something....
Click to expand...
Click to collapse
Device tree, vendor files and kernel need someone with experience to this, like @aidasaidas75, but him left L5 CM12 support.
My english is bad and my keyboard too
Sorry for mistypes and long post.
Topic subscript agan of right way now!
---------- Post added at 10:54 PM ---------- Previous post was at 10:52 PM ----------
See DualBoot Custom ROMs on the LG L3 II (via PC) in TOP FORUM DISCUSSIONS -------------------->
Just for case
Caio99BR said:
First only the Adreno is not updated, because of vsync is broken and new Adreno Blobs use hwcomposer and this is broken because vsync. When i tried to test in KK with new Adreno Blobs this happened:
Second from L5, and yes but @aidasaidas75 confused all commits, and not said the recipe to anyone.
And last i have thought this but no way to change this, the display driver of bootloader is hard edited by LG, yes i tried.
Note: No one build can make a brick of device, only if fstab is edited
And not say drivers, say vendor blobs or kernel drivers, this not is windows
I think you wanted to say the kernel and ramdisk.
Use "@" i will see this in seconds
I used L5/L7/MSM7x27a-Common/and some others msm7x27a devices
I think this cant be able to daily usage, but with DualBootPatcher, all will be possible.
I have through this too, but the Android Wear saved us , and if this work is a good progess, btw the last.
Device tree, vendor files and kernel need someone with experience to this, like @aidasaidas75, but him left L5 CM12 support.
My english is bad and my keyboard too
Sorry for mistypes and long post.
Topic subscript agan of right way now!
---------- Post added at 10:54 PM ---------- Previous post was at 10:52 PM ----------
See DualBoot Custom ROMs on the LG L3 II (via PC) in TOP FORUM DISCUSSIONS -------------------->
Just for case
Click to expand...
Click to collapse
Thanks for clearing up some stuff Caio!
Ok, so here are propertiary files for L5(for CM12.1): https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
And here are device blobs for L5(also for CM12.1): https://github.com/aidasaidas75/android_device_lge_e610
Let's see what we can do, we got @IGGYVIP, he knows a lot, and he pretty much started everything with modding L3 II, we can bring CM12.1 for our L3 II together!
I am the orders! e-e
Wow! Let's see what we can do, I can help them in some respects too, and I can test whatever they want. I'm not afraid to have a paperweight, and I know it will be worth it. If they need a Tester, I am the orders!
It's great idea to build CM12 on LG L3 II, and if we need testers, I have working E430 phone, and I can test unstable versions of this ROM.
MinusThousand said:
It's great idea to build CM12 on LG L3 II, and if we need testers, I have working E430 phone, and I can test unstable versions of this ROM.
Click to expand...
Click to collapse
Okay, but we need to get it to build first. It won't build, there are errors, we need a proper device tree and proprietary blobs for CM12.1.
dadziokPL said:
Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
Shared L1/L3/L7 II files for CM12.1: https://github.com/TeamVee/android_device_lge_vee-common/tree/cm-12.1
We also have a build of CM12.1 recovery for E430 by me. It's the only thing we can build with the local manifest. Download here: https://mega.nz/#!Io0xxBrR!gCin0V8pDZ_-PqAGTC05PfUEWTbdLhgqdBBMjnBrhdI (I would put it in the attachments, but it's 0.43 MB too big... Dammit :/
L5's device tree for CM12.1: https://github.com/aidasaidas75/android_device_lge_e610
L5's vendor propretiary files for CM12.1: https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
What do we probably need?
A device tree for CM12.1 for L3 II
Vendor files for CM12.1 for L3 II
Lollipop kernel.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
Click to expand...
Click to collapse
Actually device l5 is not set correctly in your tread tbh almost all l5 dependencies set wrong in op even display caf
aidasaidas75 said:
Actually device l5 is not set correctly in your tread tbh almost all l5 dependencies set wrong in op even display caf
Click to expand...
Click to collapse
Yo dude long time no see
Any chance you could make git group with correct base set of whats there that can be used to build for vee3 ? (I'm aware there will be a lot to do and missing stuffs but nice set from you would be a great start )
IGGYVIP said:
Yo dude long time no see
Any chance you could make git group with correct base set of whats there that can be used to build for vee3 ? (I'm aware there will be a lot to do and missing stuffs but nice set from you would be a great start )
Click to expand...
Click to collapse
I started building again so it might be lucky day for e430
@aidasaidas75 happy days pure cm or else ?
@freeusername
Yo santy
Would you be interested in the challenge of kernel ?
We could really use your experience with custom building this
MERRY CHRISTMAS ALL
IGGYVIP said:
@aidasaidas75 happy days pure cm or else ?
@freeusername
Yo santy
Would you be interested in the challenge of kernel ?
We could really use your experience with custom building this
MERRY CHRISTMAS ALL
Click to expand...
Click to collapse
Kernel is easy peazy lemon squizy. I was hooked on csgo but now synched cm12.1 and and started messing around it . I have new git and started everything from scratch for e610 and e430
aidasaidas75 said:
Kernel is easy peazy lemon squizy. I was hooked on csgo but now synched cm12.1 and and started messing around it . I have new git and started everything from scratch for e610 and e430
Click to expand...
Click to collapse
Cool, seems like the Optimus L series won't die so quick! Thanks to people like you, IGGYVIP or Caio the L3 II is usable. My Lumia 535 was sent to repair a MONTH ago, and they are still waiting for parts to arrive. I got a substitute device from my carrier, and surprise surprise, it's the L3 II. I know it's not my device, and that I'll have to pay if they figure out that I installed a custom ROM, but I couldn't resist. I installed CM11. The stock ROM is complete ****, it's laggy and unusable. I don't know for how much longer, but I can test. And when I'll have to return the L3 II, my cousin that got my old L3 II from me said that he'll test for me
I created this thread to encourage people to keep making ROMs for this phone, and it seems like we got our best developers back! I'll help you as much as I can, but I'm not as advanced as you guys! Although I learned how to build Cyanogenmod from source, and I got a great PC, building CM11(with cache enabled)on a VM took not even an hour! If you want me to do something, just tell me, I got lots of free time, and I'll do what I can to help!
Good luck to y'all, let's see what we can make together!
dadziokPL said:
Cool, seems like the Optimus L series won't die so quick! Thanks to people like you, IGGYVIP or Caio the L3 II is usable. My Lumia 535 was sent to repair a MONTH ago, and they are still waiting for parts to arrive. I got a substitute device from my carrier, and surprise surprise, it's the L3 II. I know it's not my device, and that I'll have to pay if they figure out that I installed a custom ROM, but I couldn't resist. I installed CM11. The stock ROM is complete ****, it's laggy and unusable. I don't know for how much longer, but I can test. And when I'll have to return the L3 II, my cousin that got my old L3 II from me said that he'll test for me
I created this thread to encourage people to keep making ROMs for this phone, and it seems like we got our best developers back! I'll help you as much as I can, but I'm not as advanced as you guys! Although I learned how to build Cyanogenmod from source, and I got a great PC, building CM11(with cache enabled)on a VM took not even an hour! If you want me to do something, just tell me, I got lots of free time, and I'll do what I can to help!
Good luck to y'all, let's see what we can make together!
Click to expand...
Click to collapse
Wow, you will gonna have a bad time if something goes wrong with you substitute device , just for case not test the CM12 builds, and i updated device tree (vee-common) and local manifests, these are the Display and Media repos used in CM12.1 by @aidasaidas75:
https://github.com/SlimLP-Y300/android_hardware_qcom_display-caf
https://github.com/SlimLP-Y300/hardware_qcom_media
Just for case (i like this phrase ), my inspiration is people like you and these awesome devs who cares for keep this device alive (but sometimes get crazy and disappear sometimes because they are also people ).
Note: i will be still here, just for case :silly::victory:
Caio99BR said:
Wow, you will gonna have a bad time if something goes wrong with you substitute device , just for case not test the CM12 builds, and i updated device tree (vee-common) and local manifests, these are the Display and Media repos used in CM12.1 by @aidasaidas75:
https://github.com/SlimLP-Y300/android_hardware_qcom_display-caf
https://github.com/SlimLP-Y300/hardware_qcom_media
Just for case (i like this phrase ), my inspiration is people like you and these awesome devs who cares for keep this device alive (but sometimes get crazy and disappear sometimes because they are also people ).
Note: i will be still here, just for case :silly::victory:
Click to expand...
Click to collapse
These are for Huawei Y300/G510. Are you sure these are gonna work?
Also, my carrier valued the phone at around 25 euro, If they figure out, I'll just have to pay it, but I can keep the phone forever, no big deal
NEED HELP
Hello guys, I'm working on a generic tree for our beloved device Honor 7, but not getting enough success, so each and every of you are invited to help me create a new device tree for AOSP 5.1 ROM or CM 12.1, so that we can taste the Stock Android too.
The benefits of these ROMs are that the device will get more fast and stable as there will be minimum apps and bloatwares installed.
So, it is a humble request, that whosoever have any knowledge about creating a tree from scratch please help me.
I have created a skeleton of the tree but it is not a success too as there are many things we still have to consider.
@sminki and @kenshiwara, we will setup an organization on GitHub so everyone can contribute there only.
Hi,
It will be wonderfull to have CM on our honor7.
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
sminki said:
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
Click to expand...
Click to collapse
Thanks, this will help enough and I was not aware of your troubles
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Is there any whatsapp group of honor 7.I want to join it.
udayraj99 said:
Is there any whatsapp group of honor 7.I want to join it.
Click to expand...
Click to collapse
Stop spamming
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Mee too
omkarpranavxxx said:
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Click to expand...
Click to collapse
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
asiekierka said:
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Click to expand...
Click to collapse
Hello, did any of the CM compiled fully to be a flashable zip? if yes, then have you flashed it and took logcat?
Nishadan said:
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
Click to expand...
Click to collapse
Yup lesson learnt snapdragon or nothing frm now on
maybe you know
I post link - http://download-c.huawei.com/downlo...oadId=62086&version=204465&siteCode=worldwide
Honor 7 Open Source（PLK-L01_Android5_0_2_EMUI3_1_kernel_EN)
Any progress?
I hope I can do something,it is nice to see cm for honor 7.
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
cycovision said:
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
Click to expand...
Click to collapse
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
DigiGoon said:
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
Click to expand...
Click to collapse
good luck with your exams
Until then you can use this
New ROM for Honor 7 PLK-L01.
DigiGoon said:
Until then you can use this
New ROM for Honor 7 PLK-L01.
Click to expand...
Click to collapse
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
muhammad Shohayeb said:
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
Click to expand...
Click to collapse
I will be developing AOSP 6.0, if others can give it a try then maybe we can get it.
Hi all,
Now that CM is dead (RIP) and official Lineage OS for the Wileyfox Swift 2 has not yet happened, i've been looking into other alternative OS's that are compatible with the Wileyfox Swift 2 [marmite].
However i'm not seeing any that are compatible for this device (Resurrection Remix, Dirty Unicorn, LineageOS (yet) and wondered if anyone has had any experience with any other custom OS's that they know are compatible?
Thanks
There are none because there is no source code for this device. You must be patient and wait until Wileyfox releases (Before the end of this month?!) the promised Android 7.1 update, and hope they also release the source code with it.
I did several modifications to stock CyanogenOS 13.1 version for myself, but I found not worth it sharing that, since we're going to receive the new update really really soon. If the update is a disaster, or they do a OnePlus (release the update on the 31st, late in the night before the end of the month, and full of bugs), I'll consider sharing it. But until then, just wait for it.
Thanks for the update. :good::good:
linuxct said:
since we're going to receive the new update really really soon.
Click to expand...
Click to collapse
I live in hope. :fingers-crossed:
linuxct said:
There are none because there is no source code for this device. You must be patient and wait until Wileyfox releases (Before the end of this month?!) the promised Android 7.1 update, and hope they also release the source code with it.
I did several modifications to stock CyanogenOS 13.1 version for myself, but I found not worth it sharing that, since we're going to receive the new update really really soon. If the update is a disaster, or they do a OnePlus (release the update on the 31st, late in the night before the end of the month, and full of bugs), I'll consider sharing it. But until then, just wait for it.
Click to expand...
Click to collapse
Thats not true there is maybe not a source code but the chips inside the device (and drivers) are also used in other devices wich are so you can make roms for this device.
There are no roms because this phone isn't used by many peaple yet or the community isnt big at the moment for this device but we can port roms from the xiaomi redmi 3s for instance
draakwars said:
Thats not true there is maybe not a source code but the chips inside the device (and drivers) are also used in other devices wich are so you can make roms for this device.
There are no roms because this phone isn't used by many peaple yet or the community isnt big at the moment for this device but we can port roms from the xiaomi redmi 3s for instance
Click to expand...
Click to collapse
WTF? Do you think that by having same CPU means we should have the very same source code? I know there's source code for the SD430 in codeaurora, and that Xiaomi released sources for land, but that doesn't mean anything. It'd require a lot of dirty and unnecessary stuff to get it working here (it's not only about the CPU, right?), and since Wileyfox is REQUIRED to release the source code (all OEMs are) we can avoid it by just waiting patiently. From there, building Lineage will be easier, but hey, if anyone wants to do the hard job, use land-m source code and try to port it, is free to do so! :laugh:
linuxct said:
Wileyfox is REQUIRED to release the source code
Click to expand...
Click to collapse
Manufacturers need to release kernel source as it's under a GPL license, but Android itself is under the Apache License 2.0 and manufacturers are not required to release any source code. In fact the vast majority of manufacturers do not release any of their internal Android code.
And having kernel source does not magically allow you to make custom ROMs. In fact you shouldn't even need the manufacturers kernel source unless they are using some obscure hardware.
flibblesan said:
Manufacturers need to release kernel source as it's under a GPL license, but Android itself is under the Apache License 2.0 and manufacturers are not required to release any source code. In fact the vast majority of manufacturers do not release any of their internal Android code.
And having kernel source does not magically allow you to make custom ROMs. In fact you shouldn't even need the manufacturers kernel source unless they are using some obscure hardware.
Click to expand...
Click to collapse
I know, but it's better having and working with it, isn't it? I know we will need to bring up a device tree, and that it's not that easy, but starting out of a good base is better than mixing sources from other phones, at least that's my opinion.
The kernel sources are already available for a long time (slowpokes?): https://bitbucket.org/wileyfox/kernel-wileyfox-msm8937
BeYkeRYkt said:
The kernel sources are already available for a long time (slowpokes?): https://bitbucket.org/wileyfox/kernel-wileyfox-msm8937
Click to expand...
Click to collapse
Oops. You made my day man. I swear I wasn't able to find that, I had no idea they published it already, they didn't mention it on social media, and whenever I asked them on the support chat they were like "Sorry, we don't have that".
linuxct said:
Oops. You made my day man. I swear I wasn't able to find that, I had no idea they published it already, they didn't mention it on social media, and whenever I asked them on the support chat they were like "Sorry, we don't have that".
Click to expand...
Click to collapse
Because I do not think that the public (where most users are not geeks, probably) will be interested in the post that the developers have released the source code of the kernel. Or someone beforehand, before closing Cyanogen Inc, released the source code for the kernel. And support is usually not answered to such questions, because they do not have such information.
But in any case you need the information you need to find in all available ways.
This is unofficial lineageos 16 for Motorola Clark. It is only compatible with nougat firmware - you must have the nougat bootloader and modem flashed on your device.
Tons of thanks to hashbang for all of his work
Kernel Source-
https://github.com/randomblame/android_kernel_motorola_msm8992
Device tree-
https://github.com/randomblame/android_device_motorola_clark
Current status of rom-
Daily Driver
Broken-
Camera post processing- rotation is not accounted for in hal with latest round of hacks credit to AgathosAnthropos for fixing image capture by disabling the calls to pp, hold device in landscape for photos
Tethering - it works but device will soft reboot when tethering stops
Dual sim variants are NOT supported! I do not have the hardware to test and fix at this time - bugreports appreciated
Working - everything else?
Try it yourself (Requires Nougat Firmware and as always wipe data+cache)
Latest Releases:
1/12/2020 https://www.androidfilehost.com/?fid=4349826312261700035
8/1/2019 https://www.androidfilehost.com/?fid=6006931924117928331
Don't forget to grab a compatible version of gapps for 9.0
https://opengapps.org
Once again this rom REQUIRES that the stock nougat firmware was properly flashed to work correctly... It will check before installation that you have the correct modem version installed.
*If your radio does not work you may have the wrong modem
*If you can not switch lockscreen to pin or pattern you may have the wrong modem.
*Modem flashes fail quietly sometimes please make sure you have properly flashed it before reporting issues.
Great! [emoji6]
Enviado desde mi Nexus 5X mediante Tapatalk
I'll be happy to test once there is a working rom
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Can't wait to see more from this
We wait impatiently.
Spent a couple more hours going through init narrowing it down failure happens just before zygote startsI currently have my pure propped up in charging position so I can work more on it it's had a hard life
Thank You so much
randomblame said:
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Click to expand...
Click to collapse
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Moto X Pure XT1575 said:
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Click to expand...
Click to collapse
Hi, I have the Lineague 14.2 installed. What I did to eliminate the bootloader check was to edit the uptader-script
Fixing error caused by missing taskstats kernel feature
Hi randomblame,
A quick review please, could you tell us the intended purpose of your project.
Meaning like I'm thinking it's for a "Moto X Pure 2015 (clark)" device isn't it?
Would that be for everyone on this XT1575 device which has upgraded to a stock Nougat kernel and modem?
Or could/would others benefit from it as well with your research here - other moto's?
Any and all answers - thoughts are welcome in understanding the project...
Thanks for the lady power on XDA,
RIF
This device can have a new future. Think about it !
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
randomblame said:
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
Click to expand...
Click to collapse
I'm trying to follow along with your posts best as is possible for me - but, so sorry I and as well many others are lame to understand the under-the-hood workings of Android.
Are you saying in such a way that the Moto Pure XT1575, will maybe and with your research efforts move forward to a true PIE OS possibly?
Maybe I'm reading to much into your words.
But, as I follow your posts, you'll advance us Pure device owners beyond the Nougat kernel - or at least try too?
Or yet with your efforts will this yield something like HashBang did for the XT1575 device when a Nougat OS wasn't even a thought of possibility from Motorola for us.
Back then, HashBang had worked the Nougat OS on the Marshmallow kernel and modem - I'm very green to all of this - but that's what I understood.
Still that's good none the less if that will come here from you with PIE on Nougat internals...
Beings Motorola support is dead for our device for anything future of an OS update - not to mention security patches.
If you would spell it out better as any interested XT1575 owners now could grasp the concept here in your efforts - create a buzz for a greater community following. More MXP owners to jump on board as gained support from well wishers.
Is it to early yet for that? Is there a fear that someone could steal it out from under you? Unexpected negativity, or is it just the way you wish to present this to us for the present.
I'm still going to watch and support this project with high hopes no matter what may come in the end...
Could you benefit knowledge from a LineageOS 16 for Moto Z. download?
https://www.cyanogenmods.org/forums/topic/download-moto-z-lineage-os-16-android-9/
For people like me,
Device Tree = https://source.android.com/devices/architecture/dto
and on XDA
https://forum.xda-developers.com/android/software/guide-how-to-make-device-tree-phone-t3698419
As for any active developers still left for the XT1575 a big thank you to you all, seems to me like a daunting task to crawl inside of android moreless understand things once your there...
Kernels are only loosly linked to Android versions, Google maintains the Android-common kernel repos which are usually quite far behind mainline Linux, and caf who maintains Qualcomm specific kernels are further behind in general. Literallyany feature required by Android can be backported to an old kernel I'm sure 2.6.27 could run pie but it would need so many patches it would be an unrecognizable mess. It will become progressively more of a nuisance as time goes on to keep patching up 3.10 Pie "requires" 4.4 for new devices but only needs kernel features from 3.18 which I've backported to 3.10. with each new version of Android more assumptions are made about how modern the devices kernel is and what features it has so moving to a newer kernel would be nice and like I said 3.18 seems doable but it will still be quite a bit of work.
Thank you @randomblame I was able to grasp most of that...
Maybe it's too early but, how does Googles Android security patches figure into this - if they are possible to bring us forth from Oct 2017?
Remembering I'm a laymen to the nuts and bolts of android.
I understand your post #16 - Super !
Security patch version is irrelevant when you are building from the latest source
Obnoxiously after a few builds the dedicated 250gb SSD is full and I have to make clean which takes ages, I nooped every thing but the basics didn't include telephony or wifi, ril, audio, Bluetooth GPS nfc etc and left it to build overnight will test after work trying to narrow down the problem
Surface flinger is the culprit
I have the device laying around and getting no use. Will sure donate some $$$. Seeing a los16 with all working hardware would be great.
Only got a couple hours to work on it this weekend, there is an issue where /system/vendor is not symlinked to /vendor early enough and calls for things in /vendor fail thus the issue, since we don't have a physical /vendor partition it can not be mounted immediately via the kernel. Tis annoying. I can change the calls to /system/vendor or maybe make it symlinked earlier when I get a chance
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction:
UnicornHorn kernel is a v4.14 Linux stable based, trying to be upstreamed with AOSP Kernel Common , aiming to give a balance of performance to battery life.
Code:
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Supports:
- Any custom non CFW AOSP custom ROMs on Android 11 for AOSP
- Android 10 MIUI 11/12 for MIUI
Reporting bugs:
- If you want to report any bugs, please post a logcat and kernel log - I recommend syslog to give all the logs I need.
If this information is not provided, I cannot - and will not - help.
Features:
- CPU Masks and bi-cluster API support
- Disable and fix a lot of MTK debug spam
- Module for get current display framerate
- MTK modules builded
- O3 for clang and vDSO
- Overall improvement
- vDSO32 support
- Upstream to the latest Linux kernel 4.14 version available
Downloads:
Latest Release
All releases go under this format: UnicornHorn-[revision]_[codename]_[date]
Telegram Chat:
UnicornHorn kernel chat
Flashing Instructions:
- Be sure to be rooted before flashing this kernel
- Reboot to latest non CFW recovery, flash this kernel and reboot
Credits and thanks:
@m_vaisakh for cleaning MTK debugging
@Agent_fabulous for his kernel base
And everyone else that helped me and worked with me on the kernel! PM me if I missed anyone
Contributors:
TheMalachite
Source Code:
UnicornHorn Kernel github
Version Information:
Kernel version Linux 4.14.236
UnicornHorn Version R9
Kernel Compiler Google Clang 9.0.3
Based On AOSP Kernel Common
ROM Firmware Required: Any non CFW AOSP rom based on MIUI 12 for AOSP build and Android 10 MIUI 11/12 for MIUI build
Status: Stable
Created 2020-04-08
Last Updated 2021-06-11
Reserved #1
Reserved #2
Done flashing it.
Any bugs?
work normally miui?
[email protected] said:
work normally miui?
Click to expand...
Click to collapse
No, currently it only supports custom AOSPs, read the thread carefully
What the hell???
I just followed the instructions for this kernel an now my cell is hard bricked.
I just got havoc gsi working on it.
This kernel instantly hard bricked my RN8P?
What the hell is the point of making a kernel that does that??
Seriously dude??
---------- Post added at 10:25 AM ---------- Previous post was at 10:15 AM ----------
There is no working android 10 for this phone? I flashed android 9 HavocOS 2.9.
Why would you release a kernel for a rom that is not yet working properly.
Are you trying to hard brick peoples RN8P's.
Please let everyone know who trys it that if they are running any form of android 9 an try this Kernel they will get an instant hard brick.
PLEASE.
I should be able to unbrick it with SPflash tools once I figure out how to use them.
This Kernel is very dangerous an needs to used with extreme care.
Bryceicle1971 said:
I just followed the instructions for this kernel an now my cell is hard bricked.
I just got havoc gsi working on it.
This kernel instantly hard bricked my RN8P?
What the hell is the point of making a kernel that does that??
Seriously dude??
---------- Post added at 10:25 AM ---------- Previous post was at 10:15 AM ----------
There is no working android 10 for this phone? I flashed android 9 HavocOS 2.9.
Why would you release a kernel for a rom that is not yet working properly.
Are you trying to hard brick peoples RN8P's.
Please let everyone know who trys it that if they are running any form of android 9 an try this Kernel they will get an instant hard brick.
PLEASE.
I should be able to unbrick it with SPflash tools once I figure out how to use them.
This Kernel is very dangerous an needs to used with extreme care.
Click to expand...
Click to collapse
Did you follow the instruction?
---------- Post added at 12:43 PM ---------- Previous post was at 12:42 PM ----------
Bryceicle1971 said:
I just followed the instructions for this kernel an now my cell is hard bricked.
I just got havoc gsi working on it.
This kernel instantly hard bricked my RN8P?
What the hell is the point of making a kernel that does that??
Seriously dude??
---------- Post added at 10:25 AM ---------- Previous post was at 10:15 AM ----------
There is no working android 10 for this phone? I flashed android 9 HavocOS 2.9.
Why would you release a kernel for a rom that is not yet working properly.
Are you trying to hard brick peoples RN8P's.
Please let everyone know who trys it that if they are running any form of android 9 an try this Kernel they will get an instant hard brick.
PLEASE.
I should be able to unbrick it with SPflash tools once I figure out how to use them.
This Kernel is very dangerous an needs to used with extreme care.[/QUO
SUPPORT ONLY AOSP CUSTOM ROM.
Click to expand...
Click to collapse
Yes Havoc is AOSP. However even though this cellphone (RN8P) has miui 11. its android 9. There is no working android 10 for RN8P.
So why did you write this kernel for an android version that does not yet work/exist with this cellphone?
I am unable to unbrick my unit with miflashpro or SP flash tools?
Bryceicle1971 said:
Yes Havoc is AOSP. However even though this cellphone (RN8P) has miui 11. its android 9. There is no working android 10 for RN8P.
So why did you write this kernel for an android version that does not yet work/exist with this cellphone?
I am unable to unbrick my unit with miflashpro or SP flash tools?
Click to expand...
Click to collapse
-Non-compatible ROMs with icecream kernel:
Stock Android 9 miui 10
Stock Android 9 miui 11
Stock Android 10 miui 11
-Compatible ROMs with icecream kernel:
AOSP based Android 10 custom ROMs (Los, posp, etc.)
All the aforementioned ROMs exist. This kernel was written though only for AOSP based Android 10 custom roms, as of today.
polfrank said:
-Non-compatible ROMs with icecream kernel:
Stock Android 9 miui 10
Stock Android 9 miui 11
Stock Android 10 miui 11
-Compatible ROMs with icecream kernel:
AOSP based Android 10 custom ROMs (Los, posp, etc.)
All the aforementioned ROMs exist. This kernel was written though only for AOSP based Android 10 custom roms, as of today.
Click to expand...
Click to collapse
Android 10 is virtually impossible to flash on RN8P. So I dissagree, Whenever I flash supposedly android 10 roms on it they turn out to be android 9.
all miui 11 for this cellphone is android 9.
The point is.
Anyone using yout kernel on a RN8P has a 99% chance of a hard brick like I now have as almost every rom version MIUI or AOSP is android 9.
That is not made very clear in your instructions which I misread
Bryceicle1971 said:
Android 10 is virtually impossible to flash on RN8P. So I dissagree, Whenever I flash supposedly android 10 roms on it they turn out to be android 9.
all miui 11 for this cellphone is android 9.
The point is.
Anyone using yout kernel on a RN8P has a 99% chance of a hard brick like I now have as almost every rom version MIUI or AOSP is android 9.
That is not made very clear in your instructions which I misread
Click to expand...
Click to collapse
I personally have been using Android 10 MIUI 11 a long time now. Without problems or bricks.
Right now I am using the Android 10 based LOS17.1.
I think you should reconsider regarding Android 10 on RN8P. Anyway, we're getting off topic. If you need help flashing Android 10, you can gladly pm me.
Bryceicle1971 said:
I just followed the instructions for this kernel an now my cell is hard bricked.
I just got havoc gsi working on it.
This kernel instantly hard bricked my RN8P?
What the hell is the point of making a kernel that does that??
Seriously dude??
---------- Post added at 10:25 AM ---------- Previous post was at 10:15 AM ----------
There is no working android 10 for this phone? I flashed android 9 HavocOS 2.9.
Why would you release a kernel for a rom that is not yet working properly.
Are you trying to hard brick peoples RN8P's.
Please let everyone know who trys it that if they are running any form of android 9 an try this Kernel they will get an instant hard brick.
PLEASE.
I should be able to unbrick it with SPflash tools once I figure out how to use them.
This Kernel is very dangerous an needs to used with extreme care.
Click to expand...
Click to collapse
First, their Android 10 aosp roms for this phone and read op also, this kernel is only compatible with AOSP Android 10 roms so before say it's my fault you should read op first ;__;
And did I say this kernel is compatible with GSI ? I think no ;__;
So don't try to boycott my work because YOU didn't read carefully op ;__;
Bryceicle1971 said:
Yes Havoc is AOSP. However even though this cellphone (RN8P) has miui 11. its android 9. There is no working android 10 for RN8P.
So why did you write this kernel for an android version that does not yet work/exist with this cellphone?
I am unable to unbrick my unit with miflashpro or SP flash tools?
Click to expand...
Click to collapse
A GSI will not work with a custom kernel, unless you install a compatible dtbo image. This is because a GSI has not modified your boot and dtbo partition. All AOSP based ROMs (again, not GSIs) have the same kernel dtb and dtbo image at this point. If you try to run the compiled kernel against newer MIUI dtbo images, you will hard brick.
The only MIUI dtbo images I've found working with the compiled kernel are from the initial MIUI 10 Android 9 builds. Consider using the factory preloader, and reading the thread properly.
MTK not for me
polfrank said:
I personally have been using Android 10 MIUI 11 a long time now. Without problems or bricks.
Right now I am using the Android 10 based LOS17.1.
I think you should reconsider regarding Android 10 on RN8P. Anyway, we're getting off topic. If you need help flashing Android 10, you can gladly pm me.
Click to expand...
Click to collapse
Thanks I might do that. But Im pretty sure the cell is unfixable now without either a service center or ERP surgery. Its not following any of the rules for hard bricks.
The only way the computer seems to respond to it is if I hold all 3 buttons down. Then I get an error an a chain of numbers an letters an an 'error' message.
Ill apologise to the developer. I misread the instructions an it was late at night. I kind of went off at him lol.
I definitely think if I can fix it Ill give it away or sell it. The MTK processor is a funny beast. Ive never had a processor that needs an authorised account to fix?
I'm going back to snapdragon I think. Its more predictable an more forgiving when you make errors
---------- Post added at 11:24 PM ---------- Previous post was at 11:19 PM ----------
Agent_fabulous said:
A GSI will not work with a custom kernel, unless you install a compatible dtbo image. This is because a GSI has not modified your boot and dtbo partition. All AOSP based ROMs (again, not GSIs) have the same kernel dtb and dtbo image at this point. If you try to run the compiled kernel against newer MIUI dtbo images, you will hard brick.
The only MIUI dtbo images I've found working with the compiled kernel are from the initial MIUI 10 Android 9 builds. Consider using the factory preloader, and reading the thread properly.
Click to expand...
Click to collapse
Hey just wanted to apologise for losing my temper at you. It was late at night an was the last thing I expeted would happen.
I think ill give it away if I can get it fixed.
MTK is not for me. Too unforgiving an wierd behaviour when it bricks if you make a simple mistake.
I still doubt the existence of android 10 for RN8P mate every time I think I installed it turned out to be android 9.
There are tons of youtubers seeking click bate over it. Promising android 10 wen it says in version 11.0.6.0 global that its android 9 in the version info.
This was my %$#@ up not yours ok.
Just frustrating :-|
Bryceicle1971 said:
Hey just wanted to apologise for losing my temper at you. It was late at night an was the last thing I expeted would happen.
I think ill give it away if I can get it fixed.
MTK is not for me. Too unforgiving an wierd behaviour when it bricks if you make a simple mistake.
I still doubt the existence of android 10 for RN8P mate every time I think I installed it turned out to be android 9.
There are tons of youtubers seeking click bate over it. Promising android 10 wen it says in version 11.0.6.0 global that its android 9 in the version info.
This was my %$#@ up not yours ok.
Just frustrating :-|
Click to expand...
Click to collapse
No worries and, yes there is Android 10 MIUI 11 for the device. Here are the archives we're using as reference for development:
Global
Indonesian
Indian
EEA (EU)
Russian
For more information and support of flashing these, you might wanna join the Telegram groups, or ask in relevant threads Let's not bloat this thread any further regarding A10 firmware.
Bryceicle1971 said:
Yes Havoc is AOSP. However even though this cellphone (RN8P) has miui 11. its android 9. There is no working android 10 for RN8P.
So why did you write this kernel for an android version that does not yet work/exist with this cellphone?
I am unable to unbrick my unit with miflashpro or SP flash tools?
Click to expand...
Click to collapse
Not going to lie, but all this sounds like you've been living under a rock for at least 3 months.
All jokes aside, please see the ROM section of this forum. There's five working Android 10 AOSP ROMs out for this device since about 2 months. Which is why this Kernel was released. You DID NOT have to flash GSI at all.
I've tried this kernel on the previous build of EvolutionX and LineageOS. The current version of EvoX also comes with IceCream Kernel by default.
Good luck on unbricking your phone. And hopefully you flash a REAL ROM on it next time ?
Helhound0 said:
Not going to lie, but all this sounds like you've been living under a rock for at least 3 months.
All jokes aside, please see the ROM section of this forum. There's five working Android 10 AOSP ROMs out for this device since about 2 months. Which is why this Kernel was released. You DID NOT have to flash GSI at all.
I've tried this kernel on the previous build of EvolutionX and LineageOS. The current version of EvoX also comes with IceCream Kernel by default.
Good luck on unbricking your phone. And hopefully you flash a REAL ROM on it next time ?
Click to expand...
Click to collapse
Hard brick was unresolvable. EDL reset points had no success. Its in the rubbish bin now. I dont get MTk mediatek has different rules an I'm used to snapdragon. I am thinking of stepping down to Redmi note 8 as it is snapdragon an has a number of roms that are bugless an work very well. Even finger print unlock an faceunlock.
I made mistakes yes. But am not used to mediatek.
And yes I failed once again to understand that Miui releases numbers are not sequential.
11.0.6.0 = android 9
11.0.2.0 = android 10
Miui releases are not released sequentially. Fools me every time. That was the rock I was under 3 months lol.
I have never to my knowlwdge tried a mediatek cellphone before. Too hard for me.
polfrank said:
I personally have been using Android 10 MIUI 11 a long time now. Without problems or bricks.
Right now I am using the Android 10 based LOS17.1.
I think you should reconsider regarding Android 10 on RN8P. Anyway, we're getting off topic. If you need help flashing Android 10, you can gladly pm me.
Click to expand...
Click to collapse
can i get your help?
i want to flash twrp on my begonia, currently unlocked bootloader, Android 10 Indonesia.
please help. :highfive: