Related
Guys,
Naturally, as the title states, its a general discussion thread for huashan LBL users. I want to discuss some things with like-minded people and hopefully once the momentum builds, we can try to achieve something.
Android L official release is just around the corner and our official fate is sealed by Sony @ 4.3.
But i plan on trying to port L using existing 4.3 kernel and make it at least boot so we know later on its a possibility for Locked Bootloader to have Android L.
Unlocked Bootloader guys are advised to stay away, as sooner or later, they will get proper AOSP 5.0.
Some points i want to make important.
1. This is NOT a cheer thread. Dont just post to show your excitement. It blocks the purpose of healthy discussion.
2. This is not for people who want new android. Have some sense, it isnt going to come anytime soon.
3. This is strictly for Locked Bootloader guys. So any other person coming and commenting might just be wasting his time.
Although, if you really have some positive thing to contribute, than whatever you have, LBL or UBL, please do share with all.
This is a good starting place to study.
https://github.com/Android-L-Porting-Team/Android-L-Mako/commits/master?page=3
Lets begin !
Im not sure how much id be able to contribute but ill be willing to help any way I can do. Do we even have a vague idea of what kernel modules would be needed for L? Im assuming thats what we'd need as I remember Bagyusz saying thats what he had to do for KK.
Has any of the freexperia team looked at L yet to your knowledge? Perhaps they may be able to give some small insight into drivers etc for LBL/UBL.
Will PA still be updated while this is being looked at? I'm assuming PAC wont need anything now unless problems occur as its all automated. Until L is working PA is a good thing for those wanting L due to them implementing features from L in KK such as recents and tinted bars (if they ever release them to legacy!!).
Oblox said:
Im not sure how much id be able to contribute but ill be willing to help any way I can do. Do we even have a vague idea of what kernel modules would be needed for L? Im assuming thats what we'd need as I remember Bagyusz saying thats what he had to do for KK.
Has any of the freexperia team looked at L yet to your knowledge? Perhaps they may be able to give some small insight into drivers etc for LBL/UBL.
Will PA still be updated while this is being looked at? I'm assuming PAC wont need anything now unless problems occur as its all automated. Until L is working PA is a good thing for those wanting L due to them implementing features from L in KK such as recents and tinted bars (if they ever release them to legacy!!).
Click to expand...
Click to collapse
Dont worry so much. PA is at a stage that if u have linux, u can just compile it right away and all is on Auto.
I will release milestone builds... No point pushing weekly updates if there arent any major changes.
For PAC, i have even taken that burden off and compiling and uploading is not my headache now.
And apart from above, i dont use PA personally. PAC suits me best.
As you stated the main concern is how well "the sealed by Sony @ 4.3. bootloader" will be able to cope with android L?
I really appreciate your enthusiasm. And yes there is only one way to find out. And that is to actually try porting it.
mmfh said:
As you stated the main concern is how well "the sealed by Sony @ 4.3. bootloader" will be able to cope with android L?
I really appreciate your enthusiasm. And yes there is only one way to find out. And that is to actually try porting it.
Click to expand...
Click to collapse
Porting is not an issue. We need a team. Not a band, but maybe 3 people. One compiler, One to tinker with trees and files, One tester. Just my suggestion.
One person cannot do it alone, unless he is an expert dev.
And about coping with L, all current devices having L port are using 4.4 kernel. And our 4.3 copes with 4.4. Technically there are not much issues compatibility wise. Just ramdisk and correct blobs.
I may be wrong, but thats why this discussion is goign on, if someone wants to correct me, please do.
I think this is an interesting project, XDA needs ppl like U
you think is easy port L with 4.3 kernel? I mean I'm just talking w/o reference, but Sony is just (until now) ignoring ART which is the biggest change for L (since 4.4 but well, now is not optional), and I think that could be a barrier to port new android for older phones (like SP)... what do you think about?
I hope this thread came with great news in the near future, :good:
This can be either hard or easy, hell or heaven, depending on the changes in L official release. Up until now, the changes are lying in ramdisk, but some features aren't available in the beta release.
But here are a few things that I noticed right now, before the official release:
1. UBL and LBL are stuck with 4.3 blobs. We are already using patched libraries, I guess it will get worse later, even on UBL.
2. I think we should wait until the CM12(?) will be working on UBL, while helping with bringing it up. If it works on UBL, then we should tinker with the LBL version. Actually, we have the hijack part, and we have the patches needed. I think it will be easy to get it to boot.
3. I think when @delewer finishes his kexec modules, some people that are experienced with kernel development could port it to SP, and then we could use it on forever locked phones. It will take some time, but will be the best for our phones.
So overall, if we have some luck, we would only have to kang CM trees, add the patches for hwcomposer, etc., add hijack and maybe some kernel modules. But we can be extremely unlucky and... I don't even want to imagine the worst case scenario.
Dont worry, the ground work is there. bagyusz gave us a great gift. I am sure Final release wont have boot-related changes. Maybe framework and libs, but not more.
The best thing is, 4.3 SONY rom DID NOT support ART. Bagyusz made it work even on LBL. and as Android L only supports ART, so thats the most important point i think.
Hmm, is ART even kernel-dependent?
I think that's not the case, and it's just great for us. So, bagyusz did a great work(it's just amazing), but I don't think he made any change to support ART.
And yeah, maybe there are just changes in frameworks and libs, but I'm still paranoid about this.
Anyway, I think that we are going to make it. That's what I feel, and I hope it comes true
neXus PRIME said:
Porting is not an issue. We need a team. Not a band, but maybe 3 people. One compiler, One to tinker with trees and files, One tester. Just my suggestion.
One person cannot do it alone, unless he is an expert dev.
And about coping with L, all current devices having L port are using 4.4 kernel. And our 4.3 copes with 4.4. Technically there are not much issues compatibility wise. Just ramdisk and correct blobs.
I may be wrong, but thats why this discussion is goign on, if someone wants to correct me, please do.
Click to expand...
Click to collapse
As I'm far from developer, I'm afraid cannot be of big help to you.
But I'm willing to contribute by testing builds and discovering bugs.
MrSteve555 said:
Hmm, is ART even kernel-dependent?
I think that's not the case, and it's just great for us. So, bagyusz did a great work(it's just amazing), but I don't think he made any change to support ART.
And yeah, maybe there are just changes in frameworks and libs, but I'm still paranoid about this.
Anyway, I think that we are going to make it. That's what I feel, and I hope it comes true
Click to expand...
Click to collapse
Not kernel dependant, i know, but you know what, booting a new android version using old kernel with just hijack n scripts is one HELL of a job.
And ART even didnt work for a long time on AOSP CM for huashan on UBL.
My point was, what we have here is a 4.3 kernel and blobs which might or might not be enough for android L. But before official release, we can try to port L from mako, by replacing blobs and ramdisk and boot, so that we have at least a proof of concept that LBL CAN boot L. Just boot. Nothing else.
neXus PRIME said:
Not kernel dependant, i know, but you know what, booting a new android version using old kernel with just hijack n scripts is one HELL of a job.
And ART even didnt work for a long time on AOSP CM for huashan on UBL.
My point was, what we have here is a 4.3 kernel and blobs which might or might not be enough for android L. But before official release, we can try to port L from mako, by replacing blobs and ramdisk and boot, so that we have at least a proof of concept that LBL CAN boot L. Just boot. Nothing else.
Click to expand...
Click to collapse
"Just" hijack? Bagyusz gave us an excellent base(hijack), and I bet we can boot FFOS or Ubuntu on that.
I didn't even know that ART didn't work on huashan before. Wasn't it a Gapps problem?
And yeah, these maybe aren't enough, as we are already patching some libs.
Ans one thing - I don't think we could port that from mako. It uses a little different base, and it isn't a CAF base. I think we should just wait
MrSteve555 said:
"Just" hijack? Bagyusz gave us an excellent base(hijack), and I bet we can boot FFOS or Ubuntu on that.
I didn't even know that ART didn't work on huashan before. Wasn't it a Gapps problem?
And yeah, these maybe aren't enough, as we are already patching some libs.
Ans one thing - I don't think we could port that from mako. It uses a little different base, and it isn't a CAF base. I think we should just wait
Click to expand...
Click to collapse
Just hijack meant different in a positive sense. But maybe it came out wrong.
And I'm talking about porting. Framework. Not building from source. They are actually doing same thing. I'll have to give it some time though.
neXus PRIME said:
Just hijack meant different in a positive sense. But maybe it came out wrong.
And I'm talking about porting. Framework. Not building from source. They are actually doing same thing. I'll have to give it some time though.
Click to expand...
Click to collapse
Yes, I know what you are trying to say with porting L. Actually, there would be a few things that would break:
1. The YUV color palette support (fixable with our hwcomposer, gralloc etc)
2. GPU drivers - this is the "best" part. L is precompiled, and I think it uses the libRS override, which doesn't work on our huashan because of a kernel difference (if we could build from source, we could just not enable it). There are a few other things that aren't compatible. So even if we got it to boot, it would just show black screen, and I assume by "just booting" you mean actually seeing the effort
3. The whole "thing" is built off AOSP repos, not CAF ones. Idk if SP's stock kernel would play nicely with the whole different stuff.
These are just my assumptions, in the end everything could work just fine. If you have the sufficient time, it's nice to try. Just deleting the mako proprietary stuff, and adding the needed huashan blobs + adding correct ramdisk would get it to the bootable/half working state (or there is a chance that the "build" wouldn't even boot.). I guess it's not done yet for a reason.
Anyway, I have to squash one last bug in my CM builds. If it will work, I could also try porting the magical "L".
As the question says, I want one or the other, on lollipop. I want it to be stable. Most of the features in gravity box are also in cm12 so it has peaked my interest. What do yall think?
NickM_27 said:
As the question says, I want one or the other, on lollipop. I want it to be stable. Most of the features in gravity box are also in cm12 so it has peaked my interest. What do yall think?
Click to expand...
Click to collapse
go with stock xposed if you want stable. i am using it and for the few days i have gravity box/xposed everything works like a charm. cm has a higher chance of random reboots, without saying it is not stable (i didn't try it)
Why not just grab a well-crafted ROM instead of those half-assed attempts such as gravitybox and CM?
I'm running Euphoria and it's been pretty much flawless, with a couple xposed modules running as well. A custom ROM installation doesn't necessarily preclude a bit of xposed micromanagement.
Im a quite few day on CM its stable for me atm
Flipz77 said:
Why not just grab a well-crafted ROM instead of those half-assed attempts such as gravitybox and CM?
I'm running Euphoria and it's been pretty much flawless, with a couple xposed modules running as well. A custom ROM installation doesn't necessarily preclude a bit of xposed micromanagement.
Click to expand...
Click to collapse
there's no such thing as a "well-crafted ROM",it's still AOSP when you rid of all the facelifting and the fancy features. i've no special education for android devices,but i've used well over 20 different ROMs with the same kernel for different devices and all of them looked and felt the same. i never understood why people empathize that only ROMs make the difference.
I see your point and I agree, in fact I was just suggesting to stay away from CM and GravityBox. I wasn't looking for differences between AOSP ROMs as I've tried my fair share as well and even if they're not that different they're always more reliable than a CM eternal-nightly or an ugly xposed patchwork.
I recommend CyanogenMod - more features .
You have custom recovery, no? Make a nandroid, then try both and decide for yourself.
I'd like to use CM12.1 (marshmallow) but I realize there still are no stable release? Why? Is it not good enough yet?
I've had a pretty bad experience with CM on my old Galaxy S4 so I'm a little afraid to remove the stock recovery and ROM from my Moto X Play. I want to make sure that it's bug free (or as buggy as stock) and suitable for day use. In other words I want to flash it and know it's fully reliable. Given the fact that there are only nightly releases, are they reliable enough for this?
Thanks
Prosis said:
I'd like to use CM12.1 (marshmallow) but I realize there still are no stable release? Why? Is it not good enough yet?
I've had a pretty bad experience with CM on my old Galaxy S4 so I'm a little afraid to remove the stock recovery and ROM from my Moto X Play. I want to make sure that it's bug free (or as buggy as stock) and suitable for day use. In other words I want to flash it and know it's fully reliable. Given the fact that there are only nightly releases, are they reliable enough for this?
Thanks
Click to expand...
Click to collapse
I can't vouch for the latest releases, as my xplay has been broken for like 3 months now, but being a nightly doesn't inherently make it unstable. Stable builds are usually relabeled nightlies. I say give it a shot. You can always go back to stock if you don't like it, unless you're speaking about voiding warranty
dictionary said:
I can't vouch for the latest releases, as my xplay has been broken for like 3 months now, but being a nightly doesn't inherently make it unstable. Stable builds are usually relabeled nightlies. I say give it a shot. You can always go back to stock if you don't like it, unless you're speaking about voiding warranty
Click to expand...
Click to collapse
Oh! I thought nightlies were unstable releases. So before yours broke, you had a good experience? No problem with camera or other stuff?
It's not really a question of warranty but rather just not having any issues when I need it to work. For instance, with my Galaxy S4, the camera kept crashing while I was out with my kids so I lost time trying to make it work when I wanted to take a picture. That's the kind of thing I wouldn't want happening just because I got another ROM.
Indeed I did (have a good experience). If you're every unsure of a nightly, head to the thread. You'll usually find one or several people commenting if it's no good.
dictionary said:
Indeed I did. If you're every unsure of a nightly, head to the thread. You'll usually find one or several people commenting if it's no good.
Click to expand...
Click to collapse
Yeah I had a look (I just realized I was talking about CM13 not 12.1) but given there are now 205 pages I thought I'd ask about the nightly situation in a different thread.
I think I may try it and restore it from the ROM available in the forum.
Oh and I keep wondering, given Motorola never actually released the ROM, how can someone make it available?
I m using nightly for like 3 months ......and I can say nightly is far better than stock if you are looking for customization and speed. I recently tried to go back to stock 6.0.1 but that experience is so "LAGGY" that I again return back to CM.I can say that CM nightly build working best for me with my requirements(like gaming and also photography and editing and HEAVY Customization and many more ) . and about custom recovery,it's a must have tool I suggest as with that I can return back to my previous builds. SO i recommend to go for NEW CM build,but in the end it's upto you.
and if u r still fearing about NIGHTLIES then flash the custom recovery(twrp) and then make backup of whole stock system and then do whatever U want to.
Btw this is the wrong forum to discuss things
Sent from my XT1562 using XDA-Developers mobile app
anks095 said:
I m using nightly for like 3 months ......and I can say nightly is far better than stock if you are looking for customization and speed. I recently tried to go back to stock 6.0.1 but that experience is so "LAGGY" that I again return back to CM.I can say that CM nightly build working best for me with my requirements(like gaming and also photography and editing and HEAVY Customization and many more ) . and about custom recovery,it's a must have tool I suggest as with that I can return back to my previous builds. SO i recommend to go for NEW CM build,but in the end it's upto you.
and if u r still fearing about NIGHTLIES then flash the custom recovery(twrp) and then make backup of whole stock system and then do whatever U want to.
Click to expand...
Click to collapse
Oh nice idea. I think That's what I'm gonna do, thanks!
Benjamin_L said:
Btw this is the wrong forum to discuss things
Sent from my XT1562 using XDA-Developers mobile app
Click to expand...
Click to collapse
Is it? I apologize then. Even if I want to talk about CM I should use the General Help forum?
Prosis said:
Oh nice idea. I think That's what I'm gonna do, thanks!
Is it? I apologize then. Even if I want to talk about CM I should use the General Help forum?
Click to expand...
Click to collapse
Original development is for devs posting their work usually
Hi all,
Have been using the 1+5 since launch day, bought this beast at midnight on launch day and since then it's just amazed me....but I've been stuck picking a ROM due to the encryption decryption worry, I'm currently decrypted on xXx
What ROM are you using and why?
Not looking for the best, just for the points of why one over another.
Cheers.
Hi!
dladz said:
What do the other ROMs offer over OOS? If anything? Easier theming?
Click to expand...
Click to collapse
Different ROMs are build above different sources -- OOS, AOSP, LineageOS... -- and contain various modifications -- theming options, kernel tweaking, features ported from other devices, ability to streamline the system experience, stellar stability or release-early-release-often, etc. Every ROM is different, though at some point they offer more of less similar features -- eck, it's all Android at the core! Still, they represent what their devs feel is important for a joyful experience. Read the first post of a topic, you should have a general idea of what you get.
Alexandre-P said:
Hi!
Different ROMs are build above different sources -- OOS, AOSP, LineageOS... -- and contain various modifications -- theming options, kernel tweaking, features ported from other devices, ability to streamline the system experience, stellar stability or release-early-release-often, etc. Every ROM is different, though at some point they offer more of less similar features -- eck, it's all Android at the core! Still, they represent what their devs feel is important for a joyful experience. Read the first post of a topic, you should have a general idea of what you get.
Click to expand...
Click to collapse
Thanks, maybe I didn't explain it enough, what I meant was what do you use and prefer and why?
What features sell you the ROM of your choice over others.
I think you can see by the amount of phones I've had that I've seen quite a few.
What are you using at the moment and why?
Benefit over OOS?
I've always been in love with Codename Phoenix, and I still am. I flashed everything there is out there, and every kernel. My conclusion: either OOS, or Phoenix. All the others either have some bugs or annoying problems. I choose Phoenix over OOS because it is just as smooth if not even smoother & faster while providing much more features than OOS. Also, 2 stable builds a month. That's much faster updates than OOS.
Mash1ro said:
I've always been in love with Codename Phoenix, and I still am. I flashed everything there is out there, and every kernel. My conclusion: either OOS, or Phoenix. All the others either have some bugs or annoying problems. I choose Phoenix over OOS because it is just as smooth if not even smoother & faster while providing much more features than OOS. Also, 2 stable builds a month. That's much faster updates than OOS.
Click to expand...
Click to collapse
Nice one I'll give that a crack.
dladz said:
Nice one I'll give that a crack.
Click to expand...
Click to collapse
The guy deleted all of the G+ and xda threads, because he hated the drama. All he wanted to do at the end of the day is just share the builds he makes with his friends and his loyal users, so he only just has a telegram where he posts fully stable builds around two times per month. MOD EDIT: LINK REMOVED
---------- Post added at 12:57 PM ---------- Previous post was at 12:52 PM ----------
Mash1ro said:
The guy deleted all of the G+ and xda threads, because he hated the drama. All he wanted to do at the end of the day is just share the builds he makes with his friends and his loyal users, so he only just has a telegram where he posts fully stable builds around two times per month. MOD EDIT: LINK REMOVED
Click to expand...
Click to collapse
The rom also has OOS cam working. The ROM itself is closed source, but it's stellar, so I am sure there's a reason behind him making it closed source. I bet he is some ex developer of some other mainstream rom who really knows his stuff.
The rom that give Codename Phoenix a head to head competition is AOSIP, I have used both and settled down on latter.
DevilRockr said:
The rom that give Codename Phoenix a head to head competition is AOSIP, I have used both and settled down on latter.
Click to expand...
Click to collapse
Aye i was looking at that one, again though it aims towards encrypted devices, I'm currently decrypted and have fallen foul of the memory becoming unreadable and thus losing data before, that noverity is that all you flash after the rom?
ROM / Gapps / Noverity
In that order right?
Mash1ro said:
The guy deleted all of the G+ and xda threads, because he hated the drama. All he wanted to do at the end of the day is just share the builds he makes with his friends and his loyal users, so he only just has a telegram where he posts fully stable builds around two times per month. MOD EDIT: LINK REMOVED
---------- Post added at 12:57 PM ---------- Previous post was at 12:52 PM ----------
The rom also has OOS cam working. The ROM itself is closed source, but it's stellar, so I am sure there's a reason behind him making it closed source. I bet he is some ex developer of some other mainstream rom who really knows his stuff.
Click to expand...
Click to collapse
Sounds superb, i'll give that a shot, nice one for that mate. :good:
dladz said:
Aye i was looking at that one, again though it aims towards encrypted devices, I'm currently decrypted and have fallen foul of the memory becoming unreadable and thus losing data before, that noverity is that all you flash after the rom?
ROM / Gapps / Noverity
In that order right?
Click to expand...
Click to collapse
I am decrypted as well, yes order is correct just flashing magisk after the rom makes sure that you will stay decrypted.
DevilRockr said:
I am decrypted as well, yes order is correct just flashing magisk after the rom makes sure that you will stay decrypted.
Click to expand...
Click to collapse
Ok cool, cheers pal.
Will look into it this week sometime. :good:
I went with AICP, firmware 5.1 at this point is needed with it. Modded Gcam working, modded oneplus cam also working. Alot of features, uses LOS and others for base. if your a flashaholic like myself they have nightlies close to every night even. If you want a custom kernel most of the LOS compatble ones (EX, Flash, Franco) work. Battery life is great, and I like the feature set. Eneough tweaking I dont need substratum to have the look I want. Using Magisk 14.4 beta for root. solid eneough to be a daily driver for sure. Bluetooth works perfect for me as well, no wifi issues.
Still using Pure Fusion 7.1.2, as it's aosp-based yet has oos camera fully working(with portrait and slow-mo).
dladz said:
Ok cool, cheers pal.
Will look into it this week sometime. :good:
Click to expand...
Click to collapse
So I am going to do this later...I am on XXX 10.5 right now, Oreo.
I am unencrypted...
To put Phoenix on my OP5 and not lose data...
In TWRP:
1. Wipe everything but internal storage...
2. Flash Phoenix
3. Flash GAPPS
4. Flash Magisk
Done?
lunafag said:
Still using Pure Fusion 7.1.2, as it's aosp-based yet has oos camera fully working(with portrait and slow-mo).
Click to expand...
Click to collapse
+1
Super stable for me, with magic batterylife. Do U run the beta-version or the stable? I am on #TeamBeta
Gustav Karlsson said:
+1
Super stable for me, with magic batterylife. Do U run the beta-version or the stable? I am on #TeamBeta
Click to expand...
Click to collapse
Beta as well. It had only one problem for me - stock alarm app is broken so I pulled it from another ROM.
thevirgonian said:
So I am going to do this later...I am on XXX 10.5 right now, Oreo.
I am unencrypted...
To put Phoenix on my OP5 and not lose data...
In TWRP:
1. Wipe everything but internal storage...
2. Flash Phoenix
3. Flash GAPPS
4. Flash Magisk
Done?
Click to expand...
Click to collapse
Have to say I'm more than curious about this ROM now, it is also Friday so I have the weekend to spend, no excuse for me now, I'll be doing the same pal.
:good:
lunafag said:
Beta as well. It had only one problem for me - stock alarm app is broken so I pulled it from another ROM.
Click to expand...
Click to collapse
Not a worry for me that, I've got a Lumie that gets brighter in the morning and tweets at me, wakes me up better than a normal alarm.
How's theming on pure fusion? Been having some issues with my preferred theme lately, in fact so many themes these days don't work.
Google just wants to be lighter and lighter, how they haven't got a dark side I'll never know.
Besides robbing everyone's data
Just like OP, i'm running xXx oos based rom since the beginning, and i'm pretty happy with it.
I'm interested in trying some custom roms, but i've read almost everywhere that custom roms can't get close to camera quality of OOS, is this still true ?
I don't mind flashing any magisk camera mod module if that could help :good:
Hi. I'm really disappointed in this device's custom rom development. I thought that with easy bootloader unlock and kernel sources and overall popularity we would have a large selection of custom roms.
Any thoughts?
There's a fair amount of development going on for the 8/8Pro. Things have gotten a little quiet now that A11 has been released, but slowly the Roms/ Kernels are being released.
If you are that disappointed you have options. You can either start developing your own work, you can sell the device and move on to something else that has more developer support, or you can be patient and wait for things to pick back up.
My thoughts... your post is pointless, there's been others like this in the forums that are just as pointless.
Great answer, that was just the push I needed to start developing my own rom. Just wait for it.
Never felt limited development with the OnePlus 8 Pro! Btw it has an excellent stock oos!
Honestly, the OOS stock, plus root, plus elementary kernel, you will never miss a custom ROM (although it is already a customization).
The gain in performance and battery life will make you forget about it. Give it a try.
Install PPH's AOSP build. Treble.
There's also lineage 18 for treble. I've been meaning to flash then this weekend
Make a few guides on what works and what doesn't.
I just needed a completely pointless post to motivate me
engcristiano said:
Honestly, the OOS stock, plus root, plus elementary kernel, you will never miss a custom ROM (although it is already a customization).
The gain in performance and battery life will make you forget about it. Give it a try.
Click to expand...
Click to collapse
Link to elementary kernel? Didn't see it in development for combined or standalone
c_86 said:
Link to elementary kernel? Didn't see it in development for combined or standalone
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...kernel-oneplus-8-pro-elementalx-1-02-t4098217
Once you install the app from Playstore, you'll have it. Click on link above and read it.
engcristiano said:
https://forum.xda-developers.com/on...kernel-oneplus-8-pro-elementalx-1-02-t4098217
Once you install the app from Playstore, you'll have it. Click on link above and read it.
Click to expand...
Click to collapse
That's elemental kernal lol
You said elementary so I thought there was another kernel out there...
Thanks!
c_86 said:
That's elemental kernal lol
You said elementary so I thought there was another kernel out there...
Thanks!
Click to expand...
Click to collapse
Sh****t man! My bad! Lol!
It is good tough. Give it a try.
bogdyro said:
Hi. I'm really disappointed in this device's custom rom development. I thought that with easy bootloader unlock and kernel sources and overall popularity we would have a large selection of custom roms.
Any thoughts?
Click to expand...
Click to collapse
We ha e Resurrection Remix rom. That's all we need really since it has more features than any rom