Discussion in 'Android Devices' started by whoshotjr2006, Mar 6, 2017.
This phone has unlocked bootloader,root, custom recovery but few dev's for custom ROM development.
If any dev needs help, he should let us know, i will help, if is in my domain.
Good thing you didn't get the Boost Mobile version.
just a odd suggestion.... have you tried taking a diff command to camera bits from the ls kernel and the stylo kernel to see if there is a major difference somewhere? sometimes its something small. especially with lg. and anyone whos been around the stylo block might remember me from the original development. i only stumbled across this because my sister was having issues with my old stylo that i left bradys cm build on. she got my stylo when i upgraded to a oneplus 3. if someone on the buil can get me a dmsg and kmsg on a fresh boot after opening the camera i could see if theres anything noticable
i remembered early in development we had camera issues and someone fixed them with some commits
dont know if theyd help any but either way
Any more development on this ROM? It's nice and smooth, so hoping that data will soon be working. I'm willing to pay in (root) beer if needed.
are you planning to post 2nd alpha?
Definitely would like to see this ROM Completed , its just one or 2 things away from being a perfect ROM.
Is the Katana ROM better than this one based off of the functionality ? Or is this ROM better because its running the Android Nougat
its been a while since the last update. ive been busy.
using caf kernel from lg k10 devs. working sound, camera, camcorder, etc.
still fighting sensors and data. knock on isnt a priority yet. rom works great except for sensors and data. it has to be in the hal somewhere, kernel driver builds for sensor works because i can use shell and cat values from sys/devices/virtual/input/lge_accelerometer etc and they are working but android isnt picking them up.
if anyone can help on those two fronts let me know and ill post sources to my github. im also exploring building oreo, had a completed build but was fighting with new twrp trying to get it to compile in lineage 14.1 source.
Awesome, wish I could help.
device vendor and kernel trees for what im currently working on if anyone wants to pitch in and help
Lg may have failed us with software updates but I promise I wont Big huge humongous news coming soon.
Beta 1 is uploaded.
Data works, remember to select your apn in network settings.
Video recording isnt working, use a 3rd party app like Google Camera or something for now.
No DT2W yet
Bluetooth audio isnt working yet.
Everything else is working well.
Feel free to update to twrp 3.2.0 in the op also
beta 2 will be uploaded sometime soon.
bluetooth audio is fixed
camcorder is fixed
still no dt2w and needs a small wifi bandaid. after that we are stable. dt2w might take a while.
on a related note, based off of our trees and lg k10 devs trees for the k10, i can get lineage 15 based on oreo 8.0 to boot. zygote dies immediately which takes down the system ui leaving only notification bar and buttons working. anyone want to collaborate?
beta 2 uploaded
dt2w works, bluetooth audio works, camcorder works.
wifi is still flaky but is a wip and will be fixed then on to lineage 15
Nice job, Mang!
Where do ya find dt2w commits to add to kernel?
Plus I had to modify some problem functions to make it compile. I can't remember everything off the top of my head but my GitHub will have all the changes if you want to review. Mit300 touchscreen users luck may vary, might have to use the unified driver the k10 uses for them but I don't have that model so I can't test.
wifi is fixed and the end? of lineage 14.1 dev is here. everything seems to work.
release 1 posted in the op.
installed last night, everything seems to be working for me except dt2w. not a big deal though - stll an awesome rom. Thanks for all your hard work!
Sorry about that, I forgot to mention that mit300 dt2w is a work in progress. I imagine you have the other touchscreen. Shouldn't be too hard to figure out, just have to modify one of the configs that lg k10 used. If I have something for you to test soon I'll send you a pm. Thanks for using the rom.
radio seems to have diminished reception compared to stock. Would it work to flash the efs1 from the Marshmallow rom after installing LOS14.1? Had Substratum somewhat working but (depending on the layer app) the app malfunctions if certain settings used and will have to reflash rom and start again. Wish it had kept the LG Quick Memo app, and voice announce for text and calls. Nova Launcher (Prime) works excellent for this rom.
Will keep for good if can get better reception for calls.
You can reflash efs, but your already still using the one from marshmallow if you were running stock marshmallow before flashing this rom. Flashing this doesn't touch that partition.
Getting cellular data to work in general was a huge undertaking (pain in the butt) that took forever and it was libs from lg k10 nougat stock rom that fixed it so it could be some incompatibility there. From what I see it either works on the network your on, in my case TMobile business, or doesn't get signal at all which is unlike stock rom which jumps to att for me with calling text and data blocked.
Where I work has terrible TMobile reception except for two maybe three on a good day 5x5 areas outside the building and I still get a decent signal in those spots. Anywhere around home for me calling text and data work great.
It may be that radio reception is weakened but it also could just be the way that it gets reported to lineage that affects the way lineage shows your signal bars. Have you tried running any of the signal tracking apps to see if anything is actually different in terms of signal strength from stock rom?
As far as substratum is concerned, sorry I've never used it. Is lineage supposed to natively support it? I know some other roms have the capability built in, maybe you can take the device trees in the op and build one of those roms that natively support it for the community. I'm willing to give advice on building if needed.
THank you for the fast reply and info on the radio. It is mostly noticed in the weaker reception areas where it now loses clarity (did not stock), which is on my way to work. I can be patient to see if a fix comes out. Substratum layers do work well on this - just be careful which theme because I used a Blu one and it affected my boot menu. Back to material glass now and is really nice.
Well unfortunately I don't think I'll be able to continue development of any sort on the h631. My phone blew up in my hands this morning and released the magic smoke and poof it's completely dead and done for. No saving it and I'm still confused as to what happened exactly but it's d e a d dead.
Sucks but its the way she goes. Its been fun guys and I'm glad I could at least get a mostly working lineage 14.1 tree for the stylo and hopefully someone can pick up where I left off. Bye for now.
that sucks thanks for the work you put in with the stylo, its much appreciated.
can anyone here help me with a issue i'm having? so first of all i was using my LG G Stylo and it turned died on me, so i plugged it in on charge and tried to turn it on right after only to be greeted to a frozen MetroPcs logo. this isn't the first time this happened. last time i had just factory reset my phone a truly sad day losing all that data. Now once again it has occurred but i don't want to lose all my data and files again, not to mention the countless passwords i don't remember by heart. if anyone has any ideas, or has been through this before please reply a meaningful answer so i don't have to reset again. So far ive tried the battery remove for 30 sec and hold all 3 buttons and the method on letting it completely die then charge it too 100%.