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".
Does anyone know who are the best known recognized developer groups making Roms for the G3 (if any)?
rumors, maybes, confirmed?
I've heard cm is on it, but other than that idk
---------- Post added at 06:36 PM ---------- Previous post was at 06:24 PM ----------
Also think I they I heard dirty unicorn is working on it, and I knoe OctOS had plans to support, but I don't think they've started yet
Cm probably do a great job on this device like others but we don't know any others yet because G3 used to have a bootloader lock.
Let's hope plenty of developers jump on board now the boot Loader problem had been circumnavigated.
Apparently LiquidSmooth is being worked on.
I would love to see purity rom on this beast also.
Can't wait to get Dirty with some Dirty Unicorns :highfive:
I haven't bothered rooting because there are no roms yet. Would be interesting to know what to expect. Cm is at least something promising.
Ohh! Purity ROM on this phone will go blazing fast! Can't wait for the flood of ROMS
shadehh said:
I haven't bothered rooting because there are no roms yet. Would be interesting to know what to expect. Cm is at least something promising.
Click to expand...
Click to collapse
I'm the same shadehh regards rooting. Untill the main stream rom makers are churning out top quality stuff I'll hold on.
I'd love to see Archidroid here. Some of the finest IMHO.
i have asked on the g+ page of aicp and test builds will be made as soon as the sources are released to bump the roms
miui
Hi guys...i love to see miui offical rom also is there any news about that.
Maybe we should let'em know about bump...
reza1995live said:
Hi guys...i love to see miui offical rom also is there any news about that.
Maybe we should let'em know about bump...
Click to expand...
Click to collapse
Bump! has already gained enough publicity from some tech blogs for ROM devs to know about it. Let's wait and give Team Codefire time to release the bumping process & I'm pretty sure we'll see a couple of ROMs pop-up soon after that!
CandyKat are working on a ROM. I asked the other day https://plus.google.com/114490049576855321482/posts/CAoWbPPn2cF (scroll to the bottom).
biron_w said:
CandyKat are working on a ROM. I asked the other day https://plus.google.com/114490049576855321482/posts/CAoWbPPn2cF (scroll to the bottom).
Click to expand...
Click to collapse
Yes we are. We have a sprint build waiting to be bumped already. Working in some device trees for other variants. We are very interested in developing for this phone as a few of us on the team have it.
I'm not too bothered about custom roms but would love to see custom kernel, something like boeffla on S3, that would be awesome
Cuzz1369 said:
Yes we are. We have a sprint build waiting to be bumped already. Working in some device trees for other variants. We are very interested in developing for this phone as a few of us on the team have it.
Click to expand...
Click to collapse
Good news Hopefully you will do a build for the d855 and if you need a tester I'm more than happy to help.
Cuzz1369 said:
Yes we are. We have a sprint build waiting to be bumped already. Working in some device trees for other variants. We are very interested in developing for this phone as a few of us on the team have it.
Click to expand...
Click to collapse
Excellent news I was running CandyKat on my Nexus 4 before I upgraded to a G3 so I'll be very happy when it's available :good:
if you need a tester I'm more than happy to help.
Click to expand...
Click to collapse
I'll happily test builds as well for the D855. Anything to help get CandyKat up and running.
Cuzz1369 said:
Yes we are. We have a sprint build waiting to be bumped already. Working in some device trees for other variants. We are very interested in developing for this phone as a few of us on the team have it.
Click to expand...
Click to collapse
Thanks for your interest in creating ROMs for the G3. Seeing the increase in developer participation over the past week or so has been great. If you plan to put out any VS985 builds, I'd be happy to give them a test run.
--------------------------------------------------------
Candykat maintainer
Ville (2.15/2.16 Hboots)
M7gsm
M8 (current device)
OnePlus One (coming soon)
i9300
gsw5700 said:
I'm not too bothered about custom roms but would love to see custom kernel, something like boeffla on S3, that would be awesome
Click to expand...
Click to collapse
thats my greatest hope!!!! that kernal was amazing
Yo peeps,
Code:
[COLOR="Red"]For people who say I will wait for official update STAY OUT![/COLOR]
So i was trying to port the G2's Lollipop update to G1. Many of you may think itz quite useless, well i just decided to try because i am a big dev here to compile AOSP or CM12 roms without a proper device tree. So while we wait for Official Update or until CM/AOSP becomes stable i thought maybe i could try porting. So i managed to get the system and boot.img made a zip and now the problem seems with the kernel. I get a fall through to fastboot mode when i use their kernel and when i use ours it gets stuck on bootlogo. Both the kernels are of 3.4.42 and i am not good at kernels like the way i am at kang so if someone could help me with the kernel part maybe we can get L earlier.
This thread is for only people who can encourage and try helping! Others please excuse.
I unpacked both the boot.img made a zip of it and uploaded so that it would be easier for people to help. I dont mind testing it numerous times. Willing to listen and try anything and everything that can make it boot. So here are the kernels.
Hope to find help!
@VictoriousShooter
@rr46000
@S0bes
@yajnab
I think it is impossible without kernel source... This way you can play with Ramdisk only. Moto g2 has little bit different hw..
only difference is screen size and camera, the processor, graphics chip, ram, battery and sensors are the same. so it is possible to port g2 update to g1.
AgentChaos said:
only difference is screen size and camera, the processor, graphics chip, ram, battery and sensors are the same. so it is possible to port g2 update to g1.
Click to expand...
Click to collapse
The ROM itself-yes
Kernel-no.
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
S0bes said:
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
Click to expand...
Click to collapse
I have flashed ZTE warp cm10 on ZTE v9a with kernel built by myself and it was also working... But with warp kernel there was no chance to boot v9 device up.
I think with flashing g2 lollipop over g1 shouldn't brake your phone permanently, unless you are not flashing modern etc. (just flashing system and kernel). But I cannot promise nothing will be broken
Try using a CWM flashable version of the G2 rom along with the CM12 kernel? You might be able to get some kind of result from it?
Justice™ said:
Try using a CWM flashable version of the G2 rom along with the CM12 kernel? You might be able to get some kind of result from it?
Click to expand...
Click to collapse
cm kernels wouldnt work on stock roms bro.. tried it.
fabus said:
I have flashed ZTE warp cm10 on ZTE v9a with kernel built by myself and it was also working... But with warp kernel there was no chance to boot v9 device up.
I think with flashing g2 lollipop over g1 shouldn't brake your phone permanently, unless you are not flashing modern etc. (just flashing system and kernel). But I cannot promise nothing will be broken
Click to expand...
Click to collapse
S0bes said:
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
Click to expand...
Click to collapse
@S0bes i thought you may know something so kinda tagged u bro btw i tried flashing g2's stock firmware image it doesnt brick or anything but since they have a different kernel it still goes to fall through to fastboot mode even on g2's stock roms. the main difference is that 5.0 uses ART and ours DALVIK and hence i believe that what the issue.
yeshwanthvshenoy said:
i tried flashing g2's stock firmware image it doesnt brick or anything but since they have a different kernel it still goes to fall through to fastboot mode even on g2's stock roms. the main difference is that 5.0 uses ART and ours DALVIK and hence i believe that what the issue.
Click to expand...
Click to collapse
I do not believe so. Neither Android 4.4.4 Moto G LTE nor, Moto G (2014) Kernels (or ROMs) boot on Moto G (2013.)
@yeshwanthvshenoy I know you stated you are a big dev, but since you are, you already know kernels can't be ported from an image. You need the source code. Unless you have a magical way of changing code without needing to decompile.
Still... if you are having fin making zips, go ahead, don't let my words discourage you. But... this is a dead end.
Agreed with @fermasia
if porting kernel without source was such an easy task by this time we had so many kernels
Only way is directly flash 2nd gen kernels to try our luck if some things work
All the best [emoji4]
reversegear said:
Agreed with @fermasia
if porting kernel without source was such an easy task by this time we had so many kernels
Only way is directly flash 2nd gen kernels to try our luck if some things work
All the best [emoji4]
Click to expand...
Click to collapse
I dont think there will be any luck since G 2014 has a different MSM board and that has to do with the result you will get. So if you manually flash XT1064 firmware on an XT1032 just expect a beautiful soft brick in the best of the cases... Just wait for official OTA, there are just days left for it!!! Next week we will se some news.
for this you need a new kernel for G1, which we dont have. (and even if we had it then we had the ROM too)
you will have to use the old kernel with the new ROM. which will obviously create tons of error.
have you tried CM12 kernel with the ROM?
For the kernel, try following and check if there is some progress.
Decompile both the kernels with dsixdia kitchen. You will get ramdisk and Zimage for each kernel. Try following combination.
4.4.4 Zimage (G1) + 5.0 Ramdisk (G2) + Modules (G1)
If no, try using init.rc of G1 and give another try.
I'm not planning on helping you do this, but the g2 and g1 use the same kernel. You only have to enable certain things in the defconfigs...
Somcom3X said:
I'm not planning on helping you do this, but the g2 and g1 use the same kernel. You only have to enable certain things in the defconfigs...
Click to expand...
Click to collapse
They are using the kernel source, but even kernel source for g2 hasn't been released so far...
fabus said:
They are using the kernel source, but even kernel source for g2 hasn't been released so far...
Click to expand...
Click to collapse
You don't really need it, decompile the boot.img and replace the zimage inside with a compiled one.
I don't recommend doing this. Porting in this case is pointless.
By the way, kernel source was released a while ago.
Good luck on the kernel. Though I highly suspect that Motorola will give us Lollipop on the Moto G before anyone is able to come up with a working port.
Somcom3X said:
You don't really need it, decompile the boot.img and replace the zimage inside with a compiled one.
I don't recommend doing this. Porting in this case is pointless.
By the way, kernel source was released a while ago.
Click to expand...
Click to collapse
thanks for the info and help all of u are extending i know maybe this may not work out but itz just a try. and @Somcom3X can u please a little more of the above statements u said about changing defconfigs and few other stuff. Should i use G2's zimage and G1's ramdisk or any file that u think would make it boot? Can u specify the file name if so.
Get the basic source of the G1. Match the changes made to G2 for the L. Best to getthe old G1 kernel source and modify the things needed for the L. Test and Go.
Unless its creating changes in filesystem its good to play with.
---------- Post added at 03:13 PM ---------- Previous post was at 03:13 PM ----------
yeshwanthvshenoy said:
thanks for the info and help all of u are extending i know maybe this may not work out but itz just a try. and @Somcom3X can u please a little more of the above statements u said about changing defconfigs and few other stuff. Should i use G2's zimage and G1's ramdisk or any file that u think would make it boot? Can u specify the file name if so.
Click to expand...
Click to collapse
G2 device board name differs. It will be just foolish and waste of time
So , Android nougat is finally here , but unfornately only for nexus for now. I dont know about you guys , but i cant wait for it , so Will anyone port it Today ? Or its already porting ? If Yes , update me about the situation, If not guide me to an tutorial of porting, i dont know many things about porting , but i am willing to try If is there no true devs available, and please guide me to a working tutorial. Thanks !
Kcotias said:
So , Android nougat is finally here , but unfornately only for nexus for now. I dont know about you guys , but i cant wait for it , so Will anyone port it Today ? Or its already porting ? If Yes , update me about the situation, If not guide me to an tutorial of porting, i dont know many things about porting , but i am willing to try If is there no true devs available, and please guide me to a working tutorial. Thanks !
Click to expand...
Click to collapse
Lol, we can't build with the aosp source. We have to wait for cm or caf. Be patient
Kcotias said:
So , Android nougat is finally here , but unfornately only for nexus for now. I dont know about you guys , but i cant wait for it , so Will anyone port it Today ? Or its already porting ? If Yes , update me about the situation, If not guide me to an tutorial of porting, i dont know many things about porting , but i am willing to try If is there no true devs available, and please guide me to a working tutorial. Thanks !
Click to expand...
Click to collapse
Why you didn't buy a Nexus device then??
GtrCraft said:
Lol, we can't build with the aosp source. We have to wait for cm or caf. Be patient
Click to expand...
Click to collapse
This is not true at all. You can take the AOSP source, the Moto kernel source, all the binaries you need and then spend some days to get this running.
domenukk said:
This is not true at all. You can take the AOSP source, the Moto kernel source, all the binaries you need and then spend some days to get this running.
Click to expand...
Click to collapse
Ok, go ahead then and make it
GtrCraft said:
Ok, go ahead then and make it
Click to expand...
Click to collapse
Not saying it's time well spent or that I want to do it, just saying it's possible. Resources are available here on xda and elsewhere like http://www.xda-developers.com/xda-university-how-to-port-aosp-roms-from-source/ or you can do it exactly as if you were porting cm, https://forum.cyanogenmod.org/topic/15492-general-cyanogenmod-porting-discussion/ or https://wiki.cyanogenmod.org/w/Doc:_porting_intro .
As there already is a cm port for Marshmallow, you could try to see what they did and reapply those changes to aosp.
However probably some stuff changed so finding an Android 7 rom for a phone with very similar hardware and replacing the kernel might be a better idea. All in all as I said it's days of work or even weeks. It's just not true that it can't be done.
Already running Nougat on my nexus 6 and I gotta say there's not much that changed.
Like all the other major updates from GB, ICS,JB, KK ,LP & MM , its over rated.
By tomorrow people will be complaining about N ,like always.
I really hate when major updates happen cause it seems like people are running around like chickens without heads asking when will we receive N. https://drive.google.com/file/d/1EE21MBRWQxvR9xM-iVSBrGs_Pljd4YgYsw/view?usp=docslist_api
Sent from my du_lux using XDA-Developers mobile app
You are forgetting proprietary drivers. Until there aren't drivers compiled for 7.0 you can't build neither a working rom. Be patient and wait for Motorola to release a working rom, at least a soak one. If you can't, buy a Nexus device.
Hey guys!
NEWS 1: Guys, with help of another developer we are working on the device tree. The builds currently are booting up and there are bugs to be fixed. We have currently released LineageOS 15.0 first test build only to the insiders (.i.e. testers of K10 - K420DS/N).
NEWS 2: We will also be working on K10 MS428. We will be compiling LOS 14.1 for the phone.
Source: https://github.com/LG-K10/android_device_lge_m216
does k430dsY also counts in this project, sir?
EDIT: im a pure noob both in android and english grammar
black_is_colour said:
does k430dsY also counts in this project, sir?
EDIT: im a pure noob both in android and english grammar
Click to expand...
Click to collapse
Yes.
I'd also love to see the LG K10 K410 Dual or Single SIM variant ROM. Is that possible?
abittercoffee73 said:
I'd also love to see the LG K10 K410 Dual or Single SIM variant ROM. Is that possible?
Click to expand...
Click to collapse
yes.
pvineeth97 said:
yes.
Click to expand...
Click to collapse
Good to hear that. But is the 1 or 1,5 GB of RAM enough to maintain a smooth run of the Android 7? And, well, when we can expect the earliest results? Sorry for that, but I'm really interested in this project.
Woohoo!
GuyInDogSuit said:
Woohoo!
Click to expand...
Click to collapse
I already updated my guide.
https://forum.xda-developers.com/lg-k10/development/unofficial-metropcs-428-t3578814
GuyInDogSuit said:
I think so. He ported TWRP to the MS428, so it's possible.
@pvineeth97, any word on this?
Click to expand...
Click to collapse
I will start compiling 7.1 soon
I am busy with my course projects and exams. I will start compiling it in May.
Once AOSP is available I'll gladly build and maintain LineageOS. I don't have the time to work from scratch, porting is a ton of work I'm not ready to commit to! Good luck with this, looking forward to it.
Can you post link from device tree if it's online? (Not for TWRP but for AOSP/LineageOS)
Professor Woland said:
Can you post link from device tree if it's online? (Not for TWRP but for AOSP/LineageOS)
Click to expand...
Click to collapse
I am not ready with those yet. I am working on the device tree. Once I finish compiling LineageOS I will upload the device tree.
LineageOS/AOSP for k430 too?
Please keep on topic within this thread! Thanks all
Forum moderator,
Matt
a_lewicki said:
LineageOS/AOSP for k430 too?
Click to expand...
Click to collapse
Yeah. Later for K430/MTK.
Take my kiss, thnx; Waiting for your work.
+ I have a k430dsy device.
I'm working on the k428/ms428 variants and pvineeth97 is working on the 420 variants. Others may come down the road.
I'm building the device tree now based on a few unofficial builds for devices with the msm8909 SoC, so with some luck it may not take too much work to get it going for us. All depends on how much time I can dedicate to it.
JoeMoDo said:
I'm working on the k428/ms428 variants and pvineeth97 is working on the 420 variants. Others may come down the road.
I'm building the device tree now based on the BQ Aquarius X5 tree I forked from the LineageOS github. It has the same SoC as the K428, so with some luck it may not take too much work to get it going for us. All depends on how much time I can dedicate to it.
Click to expand...
Click to collapse
Right on! Good job and good luck!
Once I'm done, and have it compiled and bootable, I'll need a couple beta testers to help me iron out kinks before releasing publicly (unless of course it just works flawlessly ). This is only open to k428/ms428 owners who can competently recover from brick on their own, and are willing to produce adequate logcats regarding any issues. Hoping to have a bootable rom in the coming weeks, we'll go from there. Keep in mind bootable may mean far from stable. Many things may be broken at first. If you're not willing to dedicate the time and work to help me fix such issues (ie, camera not working, audio not working, data not working, everything not working), please don't volunteer. If you aren't competent with adb, don't know how to produce a logcat, and don't know what to do with a bricked device, please don't volunteer. I won't have the time nor patience to walk anyone through fixing their device, and work on the port. If you feel competent, you can message me with your interest.