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.
Related
This is a pure AOSP 5.0 - Lollipop - build compiled from source .
I would highly recommend it to be used only by developers and advanced users.
The build just completed and am uploading the image files for you to do whatever you please.
The idea is to get it out there so others can take a look and use it to make it better.
Please give your comments and updates if you do plan to use it on your device.
ADVISORY -
First build -likely to be highly unstable.
I am not responsible for any damages caused whatsoever.
This is for test purposes only, however it should work well.
Link to Images -
https://www.mediafire.com/folder/c3mcyxash8z8y63,mx64j9929bp1zpw,nu1blqbnpu2siwe/shared
Credits - To clarify confusions
Team EOS - for device tree
Slim and Omni - for kernel.
Cyanogenmod - some common stuff.
Regards
Nice thanks can't wait to try it out much alohas
Which cm commits is it up to?
poczynek said:
Which cm commits is it up to?
Click to expand...
Click to collapse
Latest available
navendugoyal said:
Latest available
Click to expand...
Click to collapse
So its not AOSP.
keith.mcintyre26 said:
So its not AOSP.
Click to expand...
Click to collapse
Yes it is.
Just the Board changes to get everything working.
No CM source.
navendugoyal said:
I am out of town for next 24 hrs.. therefore can't provide too much hours into it as of now. Will await all of your responses.
Click to expand...
Click to collapse
have you tested it?
synergeticink said:
have you tested it?
Click to expand...
Click to collapse
testing
navendugoyal said:
testing
Click to expand...
Click to collapse
Images uploaded
navendugoyal said:
testing
Click to expand...
Click to collapse
Have you tested it? In all the builds I've worked on the hwcomposer library wasn't getting compiled, leading to display not working, although everything else is(I think). Although @Aaahh probably fixed it just now. Compiling though.
If it boots, mind telling me the things you changed?
lolzballs said:
Have you tested it? In all the builds I've worked on the hwcomposer library wasn't getting compiled, leading to display not working, although everything else is(I think). Although @Aaahh probably fixed it just now. Compiling though.
If it boots, mind telling me the things you changed?
Click to expand...
Click to collapse
Good work you guys.
I didn't have a problem with hardware composer.
The only issue i had was to get the kernel to compile inline.
so i compiled it separately and used the zimage as a prebuilt.
Not booting at the moment
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
No boot confirmed, stays on 1+ screen, and fastboot works from that screen as well.
Can people start testing their builds to see that it actually boots before making threads and sharing it with the community?
This is the second time in one day that this has happened.
Yeah that's building 101...don't make a thread until it boots :-/ smh
All the things wrong with this thread:
makes a thread without testing it.
Runs away for a day saying out of town.
2551990 said:
All the things wrong with this thread:
makes a thread without testing it.
Runs away for a day saying out of town.
Click to expand...
Click to collapse
Ok Now
It has taken very hard work to reach here and even get the rom to compile.
There are CM based roms already available which boot and work .
The purpose of posting this thread is to share my work so far on an AOSP build. The idea is, if I am missing something, someone else can pick it up and better it.
If someone still thinks it is a wrong idea, please delete this thread.
Happy for that, no worries.
navendugoyal said:
Ok Now
It has taken very hard work to reach here and even get the rom to compile.
There are CM based roms already available which boot and work .
The purpose of posting this thread is to share my work so far on an AOSP build. The idea is, if I am missing something, someone else can pick it up and better it.
If someone still thinks it is a wrong idea, please delete this thread.
Happy for that, no worries.
Click to expand...
Click to collapse
There's certainly no need to remove the thread. It's labelled appropriately as a test build, and this is what XDA is all about the core, this is development. Keep up the good work.
Transmitted via Bacon
timmaaa said:
There's certainly no need to remove the thread. It's labelled appropriately as a test build, and this is what XDA is all about the core, this is development. Keep up the good work.
Transmitted via Bacon
Click to expand...
Click to collapse
This AOSP rom is the work of Aaaah and lolbzballs so all credit should be given to them in the first post.
https://forums.oneplus.net/threads/development-lollipop.154589/page-305#post-7446071
daleski75 said:
This AOSP rom is the work of Aaaah and lolbzballs so all credit should be given to them in the first post.
https://forums.oneplus.net/threads/development-lollipop.154589/page-305#post-7446071
Click to expand...
Click to collapse
They are working totally different from what I am working upon.
It has nothing from their project.
Regards
As cm13 is available for other laser models but not for ze550kl... Any developer is working on it to make cm for ze550kl? Any light of hope left? 6 months from phone released and no ROM for ze550kl .. Waiting for reply if anyone is seriously working on it
Final Testing CM13(Android 6.0.1 Marshmallow)For ZE550KL/ZE500KL!
Yes I'm trying to port Cm 13!
For ZE550KL/ZE500kl
Wait For A Week!
Its Under Final Testing!
Erfan7788 said:
Yes I'm trying to port Cm 13!
For ZE550KL/ZE500kl
Wait For A Week!
Its Under Final Testing!
Click to expand...
Click to collapse
You know that ZE500KL is WAY different than ZE550KL?
Waiting for ze550kl... Hope this one boots
CM13 Will be Available For ZE550KL And ZE500KL!
LuK1337 said:
You know that ZE500KL is WAY different than ZE550KL?
Click to expand...
Click to collapse
CM13 will be Available for both device's
Erfan7788 said:
CM13 will be Available for both device's
Click to expand...
Click to collapse
Good luck
Sent from my Moto G 2014 LTE using Tapatalk
Thank you a lot. It's one of my dream to get CM 13 on my ZE500KL
Erfan7788 GOOD LUCK!
Pls if u port successfully then upload waiting from last 6 month...
I may be wrong, but it looks like both of CM13 developers are really don't like ZE550KL/500KL/500KG users for some reason. If this is impossible to release it for us, then tell at least why?
Valeev said:
I may be wrong, but it looks like both of CM13 developering are really don't like ZE550KL/500KL/500KG users for some reason. If this is impossible to release it for us, then tell at least why?
Click to expand...
Click to collapse
There is very serious issue regarding CM13 for ze550kl.
Generated CM13 kernel does not boot at all & developers are trying to solve this issue.
Oh really? You're phone was bricked is it alright now?
Erfan7788 said:
Yes I'm trying to port Cm 13!
For ZE550KL/ZE500kl
Wait For A Week!
Its Under Final Testing!
Click to expand...
Click to collapse
Are you able to boot it for ze550kl ?
Valeev said:
I may be wrong, but it looks like both of CM13 developers are really don't like ZE550KL/500KL/500KG users for some reason. If this is impossible to release it for us, then tell at least why?
Click to expand...
Click to collapse
ZE500KL/KG model is not unlockable,
ZE550KL doesn't boot on our sources so since we don't have the device it's not really easy.
Sent from my Moto G 2014 LTE using Tapatalk
Valeev said:
I may be wrong, but it looks like both of CM13 developers are really don't like ZE550KL/500KL/500KG users for some reason. If this is impossible to release it for us, then tell at least why?
Click to expand...
Click to collapse
Clearly they haven't ported CM to your phone out of spite. That's obviously the case here. Clearly. /sarcasm
Shanmugam k said:
Oh really? You're phone was bricked is it alright now?
Click to expand...
Click to collapse
ya,it s alright now
Plss release the cm13 for ze550kl soon plsss . I wilk give cash credits for the developer
I wish people would understand that these developers don't just magically have all the Asus phone models. They are all different inside, from CPU to GPU or screen size and partitions. They tend to buy a single model of their choosing for their own private use and then when they see no custom ROMs for their phone they decide to do it themselves. They are not working for Asus. They are every day people like you and me who are nice enough to release what they can for this community. If you wish to see CM or whatever custom ROM on your device you will either have to learn how to port it yourself or buy that specific model phone for someone who is willing to do it for you. Begging them to "make it soon" or "release now" makes you seem ungrateful and childish.
A big thanks to the people who work hard on these ROMs and release them for us to use.
-snip-
I appreciate all of done work by developers and very apologize for being ungrateful. I really understand that if we didn't get CM, we probably never would have it. Once I got answers, I have no more question and I hope for small chance to get it for our devices.
If I could help to them with testing for example, I would like to help, I have ZE550KL. But I have no skills in ROM stuff.
Valeev said:
I appreciate all of done work by developers and very apologize for being ungrateful. I really understand that if we didn't get CM, we probably never would have it. Once I got answers, I have no more question and I hope for small chance to get it for our devices.
If I could help to them with testing for example, I would like to help, I have ZE550KL. But I have no skills in ROM stuff.
Click to expand...
Click to collapse
We don't want testers, we want devs instead. People who can compile it on they own and fix it.
Hi everyone,
Just creating this thread to see if there is any developer who might want to port/ develop cyanogenmod to the SM-T350.
Currently Evervolv for our tablet is a big step forward, but development for it seems slow. I'm not saying anything bad about the developer, on the contrary, is a big step forward.
Anyone interested on developing some sort of Cyanogenmod or AOSP rom for our tablet, I'm more than willing to become a tester.
Good day to all.
itrof61 said:
Hi everyone,
Just creating this thread to see if there is any developer who might want to port/ develop cyanogenmod to the SM-T350.
Currently Evervolv for our tablet is a big step forward, but development for it seems slow. I'm not saying anything bad about the developer, on the contrary, is a big step forward.
Anyone interested on developing some sort of Cyanogenmod or AOSP rom for our tablet, I'm more than willing to become a tester.
Good day to all.
Click to expand...
Click to collapse
I was going to make one, but Cyanogenmod has died. I am currently working on LineageOS.
ParadoXGodzillA said:
I was going to make one, but Cyanogenmod has died. I am currently working on LineageOS.
Click to expand...
Click to collapse
Yeah, heard about the news about Cyanogenmod, but I can be a tester for Lineage OS also!!
ParadoXGodzillA said:
I was going to make one, but Cyanogenmod has died. I am currently working on LineageOS.
Click to expand...
Click to collapse
I would be willing to test for you too. Just let me know. I would actually like to learn how to get a device that is not currently supported onto a build like this. Porting?.. If so, What device do you use as the port device?
"Chance Favors the Prepared"
glockman4519 said:
I would be willing to test for you too. Just let me know. I would actually like to learn how to get a device that is not currently supported onto a build like this. Porting?.. If so, What device do you use as the port device?
"Chance Favors the Prepared"
Click to expand...
Click to collapse
I'm not really sure on how to port or compile, but I'm going to be searching some other websites (forums) and ask some people from LineageOS on how to port or compile a rom. And sure, you can be an alpha tester after I try it out myself because I don't want devices to be bricked.
ParadoXGodzillA said:
I'm not really sure on how to port or compile, but I'm going to be searching some other websites (forums) and ask some people from LineageOS on how to port or compile a rom. And sure, you can be an alpha tester after I try it out myself because I don't want devices to be bricked.
Click to expand...
Click to collapse
I completely understand. Let me know if I can help. I am kind of new at building but am trying to learn as much as I can. I am set up for building AOSP right now but would be willing to look into setting up for Lineage building. If I hear anything, or come across anything that may help your project I will be sure to let you know as well.
glockman4519 said:
I completely understand. Let me know if I can help. I am kind of new at building but am trying to learn as much as I can. I am set up for building AOSP right now but would be willing to look into setting up for Lineage building. If I hear anything, or come across anything that may help your project I will be sure to let you know as well.
Click to expand...
Click to collapse
Ok and thanks! You'll be the first person I will be telling what I will be doing while I look through forums. I will gather up information that might help you too.
Thanks again!
ParadoXGodzillA said:
Ok and thanks! You'll be the first person I will be telling what I will be doing while I look through forums. I will gather up information that might help you too.
Thanks again!
Click to expand...
Click to collapse
Any news?
SpookehAndroid said:
Any news?
Click to expand...
Click to collapse
Not yet so far. Will be after school duties and all that. I have a girlfriend too, so I got to take care of that too.
ParadoXGodzillA said:
Not yet so far. Will be after school duties and all that. I have a girlfriend too, so I got to take care of that too.
Click to expand...
Click to collapse
Good man! Haha
SM-T350
I was running Cyanogenmod on my Samsung Galaxy TAB A sm-t350 and it died yesterday Anyone would have a Lineage OS build yet?
Thanks
Marc-Andre
maleduc04 said:
I was running Cyanogenmod on my Samsung Galaxy TAB A sm-t350 and it died yesterday Anyone would have a Lineage OS build yet?
Thanks
Marc-Andre
Click to expand...
Click to collapse
If you have a CM build for the T350 would you mind sharing it? Also did it die due to CM or unrelated?
I've been tossing around what I want to develop on my T350. I would like to use it to learn how to build android from source and install a custom oem android. I'd also like to customize the stock 3E recovery, or fork CWM. A Custom Recovery or modified TWRP is what I'd like to do.
With Android 7.1.1 and 8.0 out now, maybe I'd like to get into a custom intertwined boot.img and recovery.img. Trying to decide how best to setup the dev box.
hi friends,
do you know, our nexus 4s get android Oreo by nitrogen or lineage or other roms? if yes, I know stable android Oreo version will release mid august, when we get custom rom?
we can't know this
When it comes fyi: asking for an ETA is kinda rude on xda
wait till October or November probably for a decently stable ROM
Excitedly expect first android Oreo Rom for nexus 4 on september 17
and first 32bit snapdragon android oreo port, fully work
https://forum.xda-developers.com/showpost.php?p=73494285&postcount=1356
so, now we have very big chance for our nexus 4...
and first nexus 5 android oreo port, booting and wifi working now, one similiar devices too
https://forum.xda-developers.com/showpost.php?p=73538437&postcount=6286
for now has boot problem but after all the first nexus 4 oreo
https://forum.xda-developers.com/showpost.php?p=73594437&postcount=231
I have compiled android 8 and I managed to get it booting(lots of changes on kernel and device tree). Need a lot of work but mako probably will get a fully fuctional android 8 rom.
good news
thanks for good news,
and maybe co-operation accelerates this work
equlog said:
I have compiled android 8 and I managed to get it booting(lots of changes on kernel and device tree). Need a lot of work but mako probably will get a fully fuctional android 8 rom.
Click to expand...
Click to collapse
If anyone wants to try Oreo in our lovely mako.
Original thread: Android 8.0 Mako
Download: here
equlog said:
If anyone wants to try Oreo in our lovely mako.
Original thread: Android 8.0 Mako
Download: here
Click to expand...
Click to collapse
Nice! At work and don't have my N4 to try it, but interested to hear how it is running, so I can try out when I get home. Is it mostly functional?
Can you share the device and kernel tree?
equlog said:
I have compiled android 8 and I managed to get it booting(lots of changes on kernel and device tree). Need a lot of work but mako probably will get a fully fuctional android 8 rom.
Click to expand...
Click to collapse
Just for my own curiosity, how do you know what changes need to be made to the device and kernel tree? Do you use officially supported device/kernel trees as a reference, or is there a guideline posted somewhere?
ariesgodofwar said:
Nice! At work and don't have my N4 to try it, but interested to hear how it is running, so I can try out when I get home. Is it mostly functional?
Click to expand...
Click to collapse
Really I haven't tested too much, busy at work... also my n4 have the touch screen broken and doesn't works very good lol.. but almost nothing works.
Its just to try out.
Renandelfanti said:
Can you share the device and kernel tree?
Click to expand...
Click to collapse
Sure, i'll upload to github later.
TheSt33v said:
Just for my own curiosity, how do you know what changes need to be made to the device and kernel tree? Do you use officially supported device/kernel trees as a reference, or is there a guideline posted somewhere?
Click to expand...
Click to collapse
The kernel is the used one in 7.1.2 and I added the Binder changes... the device tree is fixed by trying to booting and fixing the errors showed in last_kmsg .
equlog said:
Really I haven't tested too much, busy at work... also my n4 have the touch screen broken and doesn't works very good lol.. but almost nothing works.
Its just to try out.
Sure, i'll upload to github later.
The kernel is the used one in 7.1.2 and I added the Binder changes... the device tree is fixed by trying to booting and fixing the errors showed in last_kmsg .
Click to expand...
Click to collapse
Yes, I also flashed this and it boots. As you said, nothing works... But it is not less that it boots :laugh:
I've been trying since the source of O is released and could not boot it. Your work gives all mako users hope to see a working O build :good: Thanks for the work!
Nitin
I as well got a semi-working O build, but was a bit short on time to work on it. Could we collaborate somewhere? Perhaps a hangouts group?
I've flashed from mako 7.12, kind of like upgrade from 7.12
Sources up.
I used the vendor blobs from TheMuppets.
https://github.com/MakOreo
---------- Post added at 01:42 AM ---------- Previous post was at 01:24 AM ----------
Ziyan said:
I as well got a semi-working O build, but was a bit short on time to work on it. Could we collaborate somewhere? Perhaps a hangouts group?
Click to expand...
Click to collapse
:good:
I dont have too much free time, but I always follow the status of my devices. I Hope to see a fully working O rom asap.
Ziyan said:
I as well got a semi-working O build, but was a bit short on time to work on it. Could we collaborate somewhere? Perhaps a hangouts group?
Click to expand...
Click to collapse
That's a good idea... What do you say @equlog?
Thanks a lot for sharing the sources :good:
Nitin
as good as we hoped
Im thinking of making an unofficial lineage os 16 build for shamu will you be interested??
Wajdi Muhtadi said:
Im thinking of making an unofficial lineage os 16 build for shamu will you be interested??
Click to expand...
Click to collapse
yes it will be amazing to try it before the official release please make it and ican test it with you
I'm sure many users would be happy to test it if you did get build out.
Wajdi Muhtadi said:
Im thinking of making an unofficial lineage os 16 build for shamu will you be interested??
Click to expand...
Click to collapse
Please don't do it!
There is a reason why I haven't published any build yet.
deleted because maintainer asked to
Wajdi Muhtadi said:
guys this is only for testing purposes
https://www.androidfilehost.com/?fid=11410963190603895206
Click to expand...
Click to collapse
Nice, beeing asked by the maintainer not to do unofficial builds and post them nevertheless.
Perhaps you are going to be the new LineageOS maintainer for shamu if I drop support.
Elektroschmock said:
Nice, beeing asked by the maintainer not to do unofficial builds and post them nevertheless.
Perhaps you are going to be the new LineageOS maintainer for shamu if I drop support.
Click to expand...
Click to collapse
im sorry didnt know you are the aminyainer ill delete it now
deleted because maintainer asked to
Wajdi Muhtadi said:
deleted because maintainer asked to
Click to expand...
Click to collapse
Thanks!
I didn't want to sound rude, but it's not ready yet. Yes it works, but some things like offmode-charging are still broken with selinux enforcing.
And I really don't need unexperienced users who can't help themselfs or grab a proper log right now.
Official LineageOS builds will start soon, and shamu might be in the first batch of devices if I find some time to fix the remaining bug.
Elektroschmock said:
Thanks!
I didn't want to sound rude, but it's not ready yet. Yes it works, but some things like offmode-charging are still broken with selinux enforcing.
And I really don't need unexperienced users who can't help themselfs or grab a proper log right now.
Official LineageOS builds will start soon, and shamu might be in the first batch of devices if I find some time to fix the remaining bug.
Click to expand...
Click to collapse
I PM'd you a little while ago, but any progress with VoLTE? If not will this not be looked into? And I'd be happy to contribute, to help solve this. Thanks for everything and the continued support Kim.
wavedashdoc said:
I PM'd you a little while ago, but any progress with VoLTE? If not will this not be looked into? And I'd be happy to contribute, to help solve this. Thanks for everything and the continued support Kim.
Click to expand...
Click to collapse
To be honest I haven't spent any time trying to fix VoLTE for following reasons:
- I don't use VoLTE
- Volte isn't popular in my area
- I have no SIM in my shamus
- I have no way to test VoLTE
- I don't use my shamus anymore
- I'm busy with Pie bringup
So alltogether the changes you'll get a fix for it from me is close to zero.
But if someone comes up with a fix for it I'll happily apply it.
Elektroschmock said:
To be honest I haven't spent any time trying to fix VoLTE for following reasons:
- I don't use VoLTE
- Volte isn't popular in my area
- I have no SIM in my shamus
- I have no way to test VoLTE
- I don't use my shamus anymore
- I'm busy with Pie bringup
So alltogether the changes you'll get a fix for it from me is close to zero.
But if someone comes up with a fix for it I'll happily apply it.
Click to expand...
Click to collapse
Thanks for the response, yeah that's the vibe I've been getting about VoLTE. The angler users are also having the same issues. I'm going to dive into it more this weekend. See what I find now after a couple of months have passed.
Looking forward to 16.0 ?
wavedashdoc said:
Thanks for the response, yeah that's the vibe I've been getting about VoLTE. The angler users are also having the same issues. I'm going to dive into it more this weekend. See what I find now after a couple of months have passed.
Looking forward to 16.0 ?
Click to expand...
Click to collapse
FWIW this is what another Shamu LOS Developer, npjohnson1, had to say.
Shamu is already fully brought up to Lineage 16.0 (minus IMS functions like VoLTE/VoWiFi, which likely won't ever be fix-able).
Click to expand...
Click to collapse
https://old.reddit.com/r/LineageOS/...rting_shamu_to_80_or_later/ecg7bj8/?context=3
So wishing you the best of luck in a search for solution.
wavedashdoc said:
I PM'd you a little while ago, but any progress with VoLTE? If not will this not be looked into? And I'd be happy to contribute, to help solve this. Thanks for everything and the continued support Kim.
Click to expand...
Click to collapse
That's the open source spirit. The other devs seem to fallback to kanging me, making me the top contributor in any device_shamu repository.
Elektroschmock said:
That's the open source spirit. The other devs seem to fallback to kanging me, making me the top contributor in any device_shamu repository.
Click to expand...
Click to collapse
The problem is the error log for the VoLTE bug is difficult to read. I've posted it multiple times in search of someone who knows more. I tried fixing all paths in the IMS.apk and I also tried back porting the old IMS implementation from Oreo as well. But the ROM failed to build.
Here's the log once more:
10-24 23:04:04.303: D/RadioInfo(2183): setImsVolteProvisioned state: on
10-24 23:04:04.306: E/RadioInfo(2183): setImsConfigProvisioned() exception:
10-24 23:04:04.306: E/RadioInfo(2183): com.android.ims.ImsException: getConfigInterface()(131)
10-24 23:04:04.306: E/RadioInfo(2183): at com.android.ims.ImsManager.getConfigInterface(ImsManager.java:1809)
10-24 23:04:04.306: E/RadioInfo(2183): at com.android.settings.RadioInfo$15.run(RadioInfo.java:1292)
10-24 23:04:04.306: E/RadioInfo(2183): at android.app.QueuedWork.processPendingWork(QueuedWork.java:258)
10-24 23:04:04.306: E/RadioInfo(2183): at android.app.QueuedWork.access$000(QueuedWork.java:49)
10-24 23:04:04.306: E/RadioInfo(2183): at android.app.QueuedWork$QueuedWorkHandler.handleMessage(QueuedWork.java:278)
10-24 23:04:04.306: E/RadioInfo(2183): at android.os.Handler.dispatchMessage(Handler.java:106)
10-24 23:04:04.306: E/RadioInfo(2183): at android.os.Looper.loop(Looper.java:193)
10-24 23:04:04.306: E/RadioInfo(2183): at android.os.HandlerThread.run(HandlerThread.java:65)
Maybe a Google Dev could chime in as they were working on a test Pie build for Shamu a while back.
Hey Elektroschmock,
Will the pie version of lineageos for the Nexus 6 have additional features to the camera like the Pixel? ie. the ability to take lowlight pictures.
Thanks for your work? Looking forward to the release.
blackshoes said:
Hey Elektroschmock,
Will the pie version of lineageos for the Nexus 6 have additional features to the camera like the Pixel? ie. the ability to take lowlight pictures.
Thanks for your work? Looking forward to the release.
Click to expand...
Click to collapse
Those features are in the updated Google camera app from the Pixels. And no the Nexus 6 won't have them since it's a 32bit processor. The updated GCam has been ported to other devices with 64bit processor though like the OnePlus 6.
can someone tell me why other roms like Carbon rom with PIE are running on the nexus 6 and LineageOS not? Are the roms so different? (Off screen charging bug/voLTE bug)
Darius thebrain said:
can someone tell me why other roms like Carbon rom with PIE are running on the nexus 6 and LineageOS not? Are the roms so different? (Off screen charging bug/voLTE bug)
Click to expand...
Click to collapse
If you look at the other ROM's sources you'll see that most of the commits are taken from me (LineageOS).
Other ROMs can decide when they feel it's ready to release something. We have higher standards in stability and security.
We won't ship something half assed with deactivated selinux or selinux policies which grant nearly everything.
Elektroschmock said:
If you look at the other ROM's sources you'll see that most of the commits are taken from me (LineageOS).
Other ROMs can decide when they feel it's ready to release something. We have higher standards in stability and security.
We won't ship something half assed with deactivated selinux or selinux policies which grant nearly everything.
Click to expand...
Click to collapse
Best of luck man. This is a very tough nut to crack. I quit building this for the same reason. I cant get anything but a mostly working somewhat buggy build with piss poor battery life. Thats nothing Im putting the Velocity name on. I actually rolled all the way back to my Nougat build.