So I've made vendor blobs and gapps for shamu using 6.0.0(MRA58K) files. I'm posting them here incase anyone wants to help or make them work for your builds. I figure collaboration is always better than none.
vendor_motorola_shamu - GitHub
Google Apps (nodpi) - files.oceighty.co (WORKS)
There they are. Feel free to use them how you want to. I just ask you spread them around so we can get this going!
@xanaxdroid I've had success with the ROM booting up with these binaries but have had the issue where the SIM card isn't being recognized. Is the same problem happening to you as well?
JJD does apologizes, but he has to be that "guy". Please use the button to show your thanks to the OP, vice posting. Now if you have input into development, please do post........
Thread Cleaned.
zephiK said:
@xanaxdroid I've had success with the ROM booting up with these binaries but have had the issue where the SIM card isn't being recognized. Is the same problem happening to you as well?
Click to expand...
Click to collapse
There seems to be an issue no matter what blobs are used @zephiK
We pulled the binaries directly from Google and same thing happened. I tried using @xanaxdroid's blobs which btw don't match up with what Google put out and came up empty as well
Mazda said:
There seems to be an issue no matter what blobs are used @zephiK
We pulled the binaries directly from Google and same thing happened. I tried using @xanaxdroid's blobs which btw don't match up with what Google put out and came up empty as well
Click to expand...
Click to collapse
These are the binaries Google put out with the rest pulled from the shamu system image.
xanaxdroid said:
These are the binaries Google put out with the rest pulled from the shamu system image.
Click to expand...
Click to collapse
Gotcha, guess I'm just used to pulling them from Google not the actual image.
Anyways, going to troubleshoot this data/signal issue and see what I come up with
Let me know if you guys come up with anything, really don't care who fixes it as long as the result is the same
zephiK said:
@xanaxdroid I've had success with the ROM booting up with these binaries but have had the issue where the SIM card isn't being recognized. Is the same problem happening to you as well?
Click to expand...
Click to collapse
Same is happening to me as well.
Team Octos -Nexus 6
zephiK said:
@xanaxdroid I've had success with the ROM booting up with these binaries but have had the issue where the SIM card isn't being recognized. Is the same problem happening to you as well?
Click to expand...
Click to collapse
Yeah same thing. I pushed an update. Getting ready to try it again now.
I couldn't post on your g+ post @Mazda so came here, I haven't yet compiled(doing now) but I did notice that the blobs @zephiK & @xanaxdroid are using don't have alot of the radio related files, no wfc, and misc radio stack ones that I had figured out during 5.1.1 those helped immensely for fi and sprint, etc along with a number of radio related functions. Maybe those need to be used this go around?(Google doesn't supply these on their released blobs btw) I will let you guys know how it goes on my end when build finishes. Fingers crossed
Sent from my Nexus 6 using Tapatalk
BeansTown106 said:
I couldn't post on your g+ post @Mazda so came here, I haven't yet compiled(doing now) but I did notice that the blobs @zephiK & @xanaxdroid are using don't have alot of the radio related files, no wfc, and misc radio stack ones that I had figured out during 5.1.1 those helped immensely for fi and sprint, etc along with a number of radio related functions. Maybe those need to be used this go around?(Google doesn't supply these on their released blobs btw) I will let you guys know how it goes on my end when build finishes. Fingers crossed
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Just for clarification, the ones I used are the same ones from xanax so they're exactly identical as his.
zephiK said:
Just for clarification, the ones I used are the same ones from xanax so they're exactly identical as his.
Click to expand...
Click to collapse
I know, that's why I included you both in my comment. But you are missing all the wfc blobs, same with Google they only have really given us the "mandatory" blobs since the device was released. Not really sure why.. We had to source the ims and wfc ones ourselves previously from the factory images.
Edit: didn't something similar to this happen when volte was first introduced?
BeansTown106 said:
I know, that's why I included you both in my comment. But you are missing all the wfc blobs, same with Google they only have really given us the "mandatory" blobs since the device was released. Not really sure why.. We had to source the ims and wfc ones ourselves previously from the factory images.
Edit: didn't something similar to this happen when volte was first introduced?
Click to expand...
Click to collapse
Before they had different releases for different carriers. I used the binaries from Google and the system image to try and match the L release ones plus with newer files and files that had been removed. I don't remember about the VoLTE and WFC, but I just posted these as a starting point just in case someone knows what's missing they could post theirs and we can get on rolling and pushing out these builds.
BeansTown106 said:
I know, that's why I included you both in my comment. But you are missing all the wfc blobs, same with Google they only have really given us the "mandatory" blobs since the device was released. Not really sure why.. We had to source the ims and wfc ones ourselves previously from the factory images.
Edit: didn't something similar to this happen when volte was first introduced?
Click to expand...
Click to collapse
Currently, the baseband isn't being recognized. If I remembered correctly, when 5.1 came out the baseband was already recognized the only thing that didn't work was VoLTE which made the phone drop down to HSPA during a phone call. So on 5.1 blobs provided by Google, you could still have mobile/cellular data but on 6.0.x it doesn't.
Me and Sykopompos worked on this for quite awhile to get VoLTE working. I remembered in one of the batch of blobs we used, we had a SIM card problem and it was resolved by swapping several files from factory image.
I've also asked the question on the Android building Google group, if this is a flub or a new policy. I hope we'll get an answer soon.
Y'all remembered this commit right? https://github.com/CyanogenMod/andr...mmit/7b51319cb06ac99386ceba84d5aaee5a1c905937
jamieg71 said:
Y'all remembered this commit right? https://github.com/CyanogenMod/andr...mmit/7b51319cb06ac99386ceba84d5aaee5a1c905937
Click to expand...
Click to collapse
Yeah that was part of the initial bring up for a few of us
@xanaxdroid assuming the reason you removed SetupWizard from your 10/07 gapps was because of SetupWizard FCs reported on several devices, have you tried keeping setupwizard, and also adding GoogleTTS and libs to system/app to see if the FCs are gone? from logs i've seen, it looks like SetupWizard is crashing because of missing TTS. http://pastebin.com/nkdtkd7y
BeansTown106 said:
I know, that's why I included you both in my comment. But you are missing all the wfc blobs, same with Google they only have really given us the "mandatory" blobs since the device was released. Not really sure why.. We had to source the ims and wfc ones ourselves previously from the factory images.
Edit: didn't something similar to this happen when volte was first introduced?
Click to expand...
Click to collapse
How did your build work out Beans? Any luck?
Team Octos -Nexus 6
dankoman said:
@xanaxdroid assuming the reason you removed SetupWizard from your 10/07 gapps was because of SetupWizard FCs reported on several devices, have you tried keeping setupwizard, and also adding GoogleTTS and libs to system/app to see if the FCs are gone? from logs i've seen, it looks like SetupWizard is crashing because of missing TTS. http://pastebin.com/nkdtkd7y
Click to expand...
Click to collapse
That was the reason. I'll give it another go today using Google TTS. Thanks
Radio logs are crying for a libxml2.so, which is apparently related to RILD. Pull libxml2.so and push to system/lib and pray for results
Related
So a few of us have now started working on AOSP 5.1 and we have noticed that when making phone calls through the standard internal speaker, you can't hear the person calling and they can't hear you.
What I have tried so far:
Radios - tried older ones and current and no difference
Kernels - Again tried a few different kernels and still did not make any difference
gruesomewolf extracted the binaries from the factory image. I have added into my rom and hasn't worked. I am trying another build now.
Here is a link to my source code, so you can see what changes I have made:
https://github.com/StephenAOSP
The only changes I have made from stock 5.1 are:
Disable encryption
Disable recovery
Add in Vendor binaries
Use ota_from_target_files from scrosler's guide
Change device name
Disable restrict vendor files
Created bootanimation folder in prep for final build
I thought this would be a good place for Dev's to work on the issue and share findings. Pinging a few dev's to make them aware of the thread:
@gruesomewolf @fhem @scrosler @zephiK @rascarlo @simms22 @jakew02
Guys
Remember this is a high level discussion forum. Please keep posts related to fixing this issue.
Click to expand...
Click to collapse
Found an interesting post here:
hondajohn88 said:
zephiK...I got the voice call working without the speaker in stock aosp 5.1. It's in the mixer_paths.xml, a couple of missing lines in the 5.1 version. I copied over the lines from 5.0.2 and that fixed the problem.
I copied over lines 466 - 496 to replace those in the 5.1 mixer_paths.
(device/moto/shamu/mixer_paths.xml)
Hope this helps
Click to expand...
Click to collapse
Pinging @hondajohn88 to make sure he is aware of this thread.
Also here is a logcat attached with making a phone call.
I can confirm the above fix works on latest radio, stock kernel and latest 5.1 vendor files.
heres a flashable zip for those those whose roms havent updated yet https://drive.google.com/file/d/0B-W-PFSvgML0Mm5NdHIyQjlPeXc/view?usp=sharing
@Stephen
Just adding lines back in to the mixer_paths probably isn't the best approach to this. The commit that broke it is here:
https://android.googlesource.com/device/moto/shamu/+/b3816857ca7463f5e776ea1e5efbf59f714a96d0%5E!/#F0
I'm willing to bet if you revert that, it will fix the issue.
I'm actually not having this issue at all myself. Have you guys merged in the 5.1 kernel and updated the vendor files to LMY47D?
jakew02 said:
@Stephen
Just adding lines back in to the mixer_paths probably isn't the best approach to this. The commit that broke it is here:
https://android.googlesource.com/device/moto/shamu/+/b3816857ca7463f5e776ea1e5efbf59f714a96d0^!/#F0
I'm willing to bet if you revert that, it will fix the issue.
I'm actually not having this issue at all myself. Have you guys merged in the 5.1 kernel and updated the vendor files to LMY47D?
Click to expand...
Click to collapse
Could that commit break VoLTE activation on aosp based Roms? Not only did I have the earpiece issue but also cannot activate VoLTE service at all. I can on stock factory. @Stephen I see you have that issue as well.
Sent from my Nexus 6 using XDA Free mobile app
Good point. I wonder if rather than just adding in those two lines into the xml file, if I replace it from the 5.0.2 rom, will it get VoLTE working?
Like I said, I'm not having this issue at all on 5.1 stock or Omni (device trees are extremely similar), on T-Mobile in an LTE-area (Philadelphia).
I know that @dhacker29 had to call a number or something to enable VoLTE for VZW.. maybe he can fill everyone in on what he did to get it activated.
Stephen said:
Good point. I wonder if rather than just adding in those two lines into the xml file, if I replace it from the 5.0.2 rom, will it get VoLTE working?
Click to expand...
Click to collapse
I was told that this guy may have fixed VoLTE. I picked the last 3 commits and although my ROM is a little larger in size I now register as no SIM found on Verizon. Anyone know what lib(s) may affect that specific portion?
https://github.com/razrqcom-dev-team/proprietary_vendor_motorola/commits/cm-12.1
Sent from my Nexus 6 using XDA Free mobile app
cjkacz said:
I was told that this guy may have fixed VoLTE. I picked the last 3 commits and although my ROM is a little larger in size I now register as no SIM found on Verizon. Anyone know what lib(s) may affect that specific portion?
https://github.com/razrqcom-dev-team/proprietary_vendor_motorola/commits/cm-12.1
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
im using same vendor, as is @zephiK in Chroma5.1 howver VoLTE seems only be working for his TMo device. Noone has seeemed to figure out the No Sim issue on first boot, the only way around this is to dirty flash over a 5.0.X rom and then your 5.1 rom will see the sim and work just. Again no VoLTE but everything else is working well on my Verizon N6.
Edit: I no longer own this phone. Information in the OP may be outdated and/or incorrect. Please go to the new thread at http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-nightlies-snapshots-t3363769
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
It was a fun round of unofficial nightlies but the official upstream CM13 builder for shamu is active! Please use the new download links below to grab the official nightlies. Dirty flash seems to work fine if you go from my unofficial 11-29 build to the official 11-30 one. As mentioned in the first post, I will be ceasing my personal builds for now and leave it to the CM team.
Notes: CyanogenMod's stock kernel forces encryption of storage. Please download one of the third party kernels if you wish to avoid this. Also this thread assumes you have kept up to date with bootloaders and radio. At the time of writing, the latest is from the MRA58K release and can be downloaded here.
CyanogenMod 13.0 Nightlies: Download
Open GApps: Download (I recommend arm, 6.0, micro)
Changelog: CMX Changelog
Third party kernels:
Elite Kernel
Hells Core
XDA:DevDB Information
CyanogenMod 13.0, ROM for the Nexus 6
Contributors
djh816
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-11-22
Last Updated 2015-12-06
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
HipKat said:
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
Click to expand...
Click to collapse
Correct, but not nightly and as far as I can tell albinoman887 is also making fixes which implies altering of upstream code. My thread intends to serve as a purely upstream source build.
djh816 said:
Correct, but not nightly and as far as I can tell albinoman887 is also making fixes which implies altering of upstream code. My thread intends to serve as a purely upstream source build.
Click to expand...
Click to collapse
I would like to say thank you, and I believe that this ROM deserves its own thread respectfully. Since there isn't much action from that other Alpha build and if you are truly building on a nightly basis then this is much appreciated and I look forward to testing.
Thanks!
HipKat said:
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
Click to expand...
Click to collapse
A Thread with Zero Support from the Thread OP and no Nightlys , its good to see this Thread with hopfully regular updates since I currently have working in the border guarding Work and never have time for building. But what i know from @djh816 updates come many times.
Tylog said:
A Thread with Zero Support from the Thread OP and no Nightlys , its good to see this Thread with hopfully regular updates since I currently have bodybuilding in the border guarding Work and never have time for building. But what i know from @djh816 updates come many times.
Click to expand...
Click to collapse
Thanks for the support and glad to build it. Just to make sure credit is given where due, any bug fixes will be made only by the CyanogenMod team and/or any git contributors. Not sure if you'll get much support from me either but I'll certainly be glad to give any tips I find. For example, if this one specific bug rears its ugly head again, you may need to rename the SetupWizard apk inside /system/app-priv/ as that has been constantly force closing for me prior to today's build.
djh816 said:
Thanks for the support and glad to build it. Just to make sure credit is given where due, any bug fixes will be made only by the CyanogenMod team and/or any git contributors. Not sure if you'll get much support from me either but I'll certainly be glad to give any tips I find. For example, if this one specific bug rears its ugly head again, you may need to rename the SetupWizard apk inside /system/app-priv/ as that has been constantly force closing for me prior to today's build.
Click to expand...
Click to collapse
MAybe test other Gapps, i had this isues with a few cm 13 builds in combination with banks gapps , i like Banks gapps but for now not with CM13 . No support for me no problem , only 1 builds in 3 Weeks in this early stage is a problem , thats what i mean . I have at the moment zero time , i am one day in the week at home and thats time for my son and my wife
Thanks for the builds. I tried (unsuccessfully) to build my own, so this helps out a lot!
nightlies has not started yet.. looking forward..
Awesome! Thanks!
Sent from my Nexus 6 using Tapatalk
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
mexiken said:
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Still is not working.. I'd love to know of a fix, if any...
mexiken said:
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I modified build.prop just fine.
---------- Post added at 03:10 AM ---------- Previous post was at 03:08 AM ----------
Thanks OP, for bringing this to us. Seems pretty good for such an early build. I just barely flashed it but seems great so far.
Does ad away work on this build? It wouldn't work on the previous build.
Is security disable on the ROM?
cz829x18 said:
Does ad away work on this build? It wouldn't work on the previous build.
Click to expand...
Click to collapse
Doesn't seem to just yet. As others have mentioned, no /system writing just yet.
evolishesh said:
Is security disable on the ROM?
Click to expand...
Click to collapse
Doesn't seem like it, I've tried "adb shell" with "su" after but still drops me to a "$" shell rather than "#"
Will you be adding any features or will this be more of a slim to stock cm13 builds? Also thanks for your contributions
nighthawk626 said:
Will you be adding any features or will this be more of a slim to stock cm13 builds? Also thanks for your contributions
Click to expand...
Click to collapse
No features added whatsoever If they add it upstream (included in CM) it'll be here, otherwise no. Absolutely stock. Consider me a third party buildbot slave
Very nice ROM. Just to let everyone know I just finished flashing with the Open GApps Pico and it's working fine. I know, it's bad form to use something that's not recommended.
One quick question, do we get any notification that the new nightly is ready to flash or do we just check the download site?
dlbarron said:
Very nice ROM. Just to let everyone know I just finished flashing with the Open GApps Pico and it's working fine. I know, it's bad form to use something that's not recommended.
One quick question, do we get any notification that the new nightly is ready to flash or do we just check the download site?
Click to expand...
Click to collapse
For now just the download site. I may setup something similar to the pushbullet feed Chroma has if people are interested but haven't spent the time to do it yet. New 11-23 build is up now though
Edit: Woot, looks like they fixed the system rw mounting. Hm but my test file disappeared on reboot.. maybe not yet
The good stuff: https://github.com/jcadduono/android_kernel_lge_msm8996/commits/android-7.0
Fork it!
Update: CAF branch has some problems at the moment, use this one instead for now.
So this is currently the v10d release. It's compatible with V20 Nougat v10d and G5 v20a.
Place toolchain (pick one up from here) in ~/build/toolchain & tar xf.
git clone https://[email protected]/yourname/android_kernel_lge_msm8996.git
If you want to change any config options:
./menuconfig.sh (optional target, ex. twrp or lge)
Ready?
./build.sh h850/h830/h918/us996/any model you want
Models are applied onto the target base defconfig, so your V20 kernels will build for all V20 variants and for all variants of the G5 as well.
Create your own by copying arch/arm64/configs/lge_defconfig to arch/arm64/configs/your-awesome_defconfig!
Grab:
build/arch/arm64/boot/Image.lz4-dtb [or] build/arch/arm64/boot/Image.gz-dtb
build/lib/modules
Place in:
https://github.com/jcadduono/lazyflasher/tree/kernel-flasher
make
You got yourself a magical all-powerful custom kernel installer, complete with your own custom kernel!
Notice that there's a few branches:
opensource is where I merge LG changes, when it's updated, android-7.0 is rebased on it
android-7.0 is a starting off point closest to absolute stock, base off here
android-7.0-security adds security and bug fixes from CAF on top of android-7.0 branch
twrp-7.0 is for Team Win Recovery Project (yes, it's ready, come with an unlocked device and I'll give it to you)
nethunter-7.0 is for the Kali NetHunter project (if you dare, some fun there)
Another issue was their weird build system, I dropped that. Replaced tuxera's exFAT prebuilt downloader with Samsung's GPL'd exFAT drivers instead. Unsure how well it works replacing it like that, we'll have to see.
I also added Qualcomm's Core Control which they just released the sources to somewhat recently. I believe it's already included on the G5 and probably V20 as a kernel module. Their released version doesn't have module support yet but it's fairly easy to add I guess with the leaked proprietary module version out there to pick pieces from.
Have fun!
Great Man !
thanks for this..
I've been following the root process since the beginning and I'm amazed at the relatively short amount of time it took. Huge kudos to @jcadduono! I will purchase this phone. Now, since the kernel needed to have it's encryption support modifed, are the patches added to a branch on your Github fork? I would like to compile a custom kernel, along with patching it with SultanXDA's SafetyNet boot bypass. Which branch will be appropiate to fork to flash on the TWRP/Rooted V20?
Thanks much @jcadduono! I'm going to start poking around in here and see if I can find anything particularly interesting.
zabracks said:
Thanks much @jcadduono! I'm going to start poking around in here and see if I can find anything particularly interesting.
Click to expand...
Click to collapse
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
jcadduono said:
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
Click to expand...
Click to collapse
I've got an H918, if you need somebody to test a kernel.
jcadduono said:
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
Click to expand...
Click to collapse
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
albinoman887 said:
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
Click to expand...
Click to collapse
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
jcadduono said:
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
Click to expand...
Click to collapse
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
jcadduono said:
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
Click to expand...
Click to collapse
which branch/repo is the one that boots but messed up display?
albinoman887 said:
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
Click to expand...
Click to collapse
Would absolutely LOVE to see CM on our phones! Not that it'll make things move faster, but I'll throw 100 bucks your way if it's done before Christmas
lightninbug said:
Would absolutely LOVE to see CM on our phones! Not that it'll make things move faster, but I'll throw 100 bucks your way if it's done before Christmas
Click to expand...
Click to collapse
I want Nethunter too
I'll be around to test any of the stuff, usually at night.
The v20 kernel is available on the lg open-source site, at least the h990 one is.
Sent from my LG-H990 using Tapatalk
---------- Post added at 03:36 PM ---------- Previous post was at 03:25 PM ----------
Artcrime said:
The v20 kernel is available on the lg open-source site, at least the h990 one is.
Sent from my LG-H990 using Tapatalk
Click to expand...
Click to collapse
There is v10d version for 918. opensource.lge.com forgive me if this is old news. a|c
albinoman887 said:
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
Click to expand...
Click to collapse
slayerh4x said:
I want Nethunter too
I'll be around to test any of the stuff, usually at night.
Click to expand...
Click to collapse
albinoman887 said:
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
Click to expand...
Click to collapse
Sent from my LG-H990 using Tapatalk
I updated all the branches earlier today...should work fine now, so apparently was a source code issue that needed v10d update, not sure though no one's volunteered for testing (I don't do requests/testing over the forum, only on IRC)
Is a kernel the main thing stopping us from a CM rom?
what toolchain should we be using? got a link to a compiled one? i'm getting build errors I know are related to the toolchain but i've been out of the game for awhile. last i knew we needed gcc-4.9?
jcadduono said:
I updated all the branches earlier today...should work fine now, so apparently was a source code issue that needed v10d update, not sure though no one's volunteered for testing (I don't do requests/testing over the forum, only on IRC)
Click to expand...
Click to collapse
I'm there.
albinoman887 said:
what toolchain should we be using? got a link to a compiled one? i'm getting build errors I know are related to the toolchain but i've been out of the game for awhile. last i knew we needed gcc-4.9?
Click to expand...
Click to collapse
gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu.tar.xz .Be sure to change the PATH in menuconfig.sh
@jcadduono , thank you. You are truly an inspiration
Wondering if anyone can help me learn how to do this right...
So I was able to compile the kernel, but I didn't get an Image.gz (which im sure is fine). I did get an Image.lz4, Image.lz4-dtb, and Image (no extension). I figure only the .lz4* files are needed. I added all 3 to the lazyflasher, and ran make. The resulting zip flashed, but sent me straight to Bootloader. I then tried to fix by flashing the stock kernel, but this still did not boot. ReFlashed my ROM and it's booting now.
I used this toolchain gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu
Any guidance? My guess is it's flashing at the wrong point?
Here is the ZIP. DO NOT FLASH. This is only for someone who knows what they are looking at to tell me what is wrong with it. No modifications were done. Source was forked from OP, and compiled with default menuconfig, then build.sh h918
G'day guys and girls
I haven't seen PN source code updated for a while on the r33 side, seems they are focusing on the kernel a little bit
So I merged the tags myself and add some features to the ROM
I'LL TRY TO KEEP THE THREAD UPDATED, BUT THERES NO GUARANTEE ON THAT, THE REPO WILL PROBABLY BE UPDATED, IF YOU WANT TO BUILD YOURSELF, GO TO THE REPOSITORY DOWN BELOW
PLEASE NOTICE
This version was NOT signed by the PureNexus's certificates, please do a FULL FACTORY RESET if you are from the offical build.
I'm sorry for the inconvenience, but this is compulsory
Features
Built in GAPPS (no gmail, Google News and weather and play magazines, don't find them useful since I've got outlook and other replacement)
Built in Greenify
Android 7.1.2_r33 August security level
VoLTE tested
Lineage Terminal
ElementalX 1.15 Kernel (NTFS rw, exFAT, High Brightness Mode, Digital Gain control)
USB Patch for using the phone as a USB HID keyboard/mouse see here
All PureNexus Features
Untested
Since I am in Australia, there's no actual way to test whether Wi-Fi calling works, but it should work considering Project Fi was prebuilted. Please tell me if I need to add anything.
Magisk
https://forum.xda-developers.com/apps/magisk/unofficial-google-pixel-family-support-t3639262
Goodwin_c's magisk seems to work very well, thanks @goodwin_c
Known Bugs
OK Google detection is known to be not working in some languages (eg. Japanese)
MusicFX don't seems to open
Screenshots
https://ibb.co/m9XXz5
https://ibb.co/fL0Ke5
Downloads
https://drive.google.com/file/d/0B5ns3qw5ULWhTkZMQ2dVN0Z3LUU/view?usp=sharing
Flashing - How to
Please unzip the zip file, flash using fastboot commands
fastboot flash system_a /path/to/system.img
fastboot flash system_b /path/to/system.img
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
GitHub Source
manifest
patched kernel
Credits
the PureNexus Project https://github.com/purenexusproject
LineageOS https://github.com/lineageos
Pelya https://github.com/pelya/android-keyboard-gadget
flar2 (aka. Aaron Segaert) https://github.com/flar2
One thing I noticed is, I couldn't get Ok Google to work. Would say this language isn't supported
Sent from my Pixel XL using Tapatalk
It's asking me to flash NZH54D Vendor image but i'm on T-Mobile shouldn't my Vendor image be NKG47S...?
BHermes211 said:
One thing I noticed is, I couldn't get Ok Google to work. Would say this language isn't supported
Click to expand...
Click to collapse
Ok Google works fine for me but I still haven't updated the vendor image. I'm worried I'm gonna screw up the rom. I'm gonna test it now after flashing the correct vendor image.
Ok vendor has been updated and everything is working fine.
why is this being made ? is PN dead ? curious since i've been using my pixel less since i got the s8+
Delete.
TheUndertaker21 said:
why is this being made ? is PN dead ? curious since i've been using my pixel less since i got the s8+
Click to expand...
Click to collapse
If the official PN doesn't have a feature that a user wants, they are within their rights to build a version that incorporates that feature.
And in most cases, if the builder marks it as Unofficial (as is the case here), they are welcome to share it others, on the understanding that no support will likely be given from the official builder.
BHermes211 said:
One thing I noticed is, I couldn't get Ok Google to work. Would say this language isn't supported
Click to expand...
Click to collapse
Hey, there, actually I'm also having this problem. What language are you using? I am using Japanese and this problem presents, I thought it was Google's problem so I didn't care, I'll try figure it out.
EDIT: fixes typo
TheUndertaker21 said:
why is this being made ? is PN dead ? curious since i've been using my pixel less since i got the s8+
Click to expand...
Click to collapse
No, they aren't dead. they seems to focusing on other things especially the kernel and they are preparing for O since all the repos are being moved to the PureNexus-Legacy repo now. So I just built myself also add things for my own use.:fingers-crossed:
Pøîñtßlåñk said:
It's asking me to flash NZH54D Vendor image but i'm on T-Mobile shouldn't my Vendor image be NKG47S...?
Click to expand...
Click to collapse
I think it's probably fine. Since I'm using the international version so I'm just flashing the NZH54D vendor
cydia2020 said:
I think it's probably fine. Since I'm using the international version so I'm just flashing the NZH54D vendor
Click to expand...
Click to collapse
Worked fine thx.
BHermes211 said:
One thing I noticed is, I couldn't get Ok Google to work. Would say this language isn't supported
Click to expand...
Click to collapse
Do you see the same thing here
Pøîñtßlåñk said:
Worked fine thx.
Click to expand...
Click to collapse
Can you get OK Google to work? What language are you on. Cheers.
cydia2020 said:
Can you get OK Google to work? What language are you on. Cheers.
Click to expand...
Click to collapse
Works fine here English.
I was using English...
Sent from my Pixel XL using Tapatalk
BHermes211 said:
I was using English...
Click to expand...
Click to collapse
Hmm, that's weird. I'll try compile the official version on my 5x and see what happens
cydia2020 said:
Hmm, that's weird. I'll try compile the official version on my 5x and see what happens
Click to expand...
Click to collapse
Thank you. I'll be more than happy to give it a try again
Sent from my Pixel XL using Tapatalk
MusicFX don't seems to open in case you're concerned.
cydia2020 said:
Hmm, that's weird. I'll try compile the official version on my 5x and see what happens
Click to expand...
Click to collapse
Question... Is there a way to remove system apps on this rom? I've tried to remove the YouTube app even with magisk installed it gives apps that are able to remove system apps root permission but in the app remover app itself it says that I'm not rooted
Hi guys,
as LineageOS 15.1 is just around the corner and I had a few spare CPU cycles, here's the current build which I did as a 'code of honor'-member. Just flash with TWRP as usual, add gapps (stock are too big) and optionally root.
Watch out as the whole rom might still lack a few features.
Sources are on https://github.com/LineageOS
Credits to anyone who worked on them including intel for their buggy CPUs enabling me to build.
Build date: 2018-03-02
Download: https://go.stargazer.at/bacon
FAQs.:
Q: What patches did you include?
A: None. Pure LineageOS as it would come from the build server
Q: So this IS the official LineageOS rom?
A: In theory it's the same thing, but I am NOT a linageos developer
Q: What Gapps package did you use?
A: Nano. Stock is too big as it wouldn't fit on /system
Q: Support?
A: None officially. But ask - maybe someone has an idea.
Q: What works?
A: Phone rings, I'm able to answer and do calls, BT works, Wifi... annoying texts already arriving. I assume it's working.
Q: Bugs?
A: You tell.
Q: Is it complete?
A: I doubt it. Some translations are still missing. Keep in mind it's an early version of lineageOS
Q: Why did you build it?
A: Because I did not want to wait for the official release and live on the edge.
Q: Why does a girl build roms?
A: Short answer: because I can.
is the camera working? apparently that is the reason why the official build have been delayed
borzowsky said:
is the camera working? apparently that is the reason why the official build have been delayed
Click to expand...
Click to collapse
Honestly, I did not check yet as camera is not one of my basic needs. Will do so as soon as I get home.
If it does not work yet, I do not intend to fix too much stuff as I want to stay on the official sources. If there's a patch to cherrypick from gerrit, it's something we may talk about.
Camera does not work yet, but as far as I can see there are a few things in review to be submitted. Stay tuned as I will be building the rom again as soon as those changes are merged. In the meanwhile I may do some tinkering on my local build.
References:
https://review.lineageos.org/c/206914/
Long live bacon
cb5264 said:
Camera does not work yet...
Click to expand...
Click to collapse
I noticed that your build has SELinux enforcing but this may be why the camera isn't working; something that still needs fixing.
cb5264 said:
Camera does not work yet, but as far as I can see there are a few things in review to be submitted. Stay tuned as I will be building the rom again as soon as those changes are merged. In the meanwhile I may do some tinkering on my local build.
References:
https://review.lineageos.org/c/206914/
Click to expand...
Click to collapse
I've been keeping tabs on this every day and no one has touched it for weeks [emoji24] hopefully they just have code they're working on offline and just have to upload it and merge. Waiting is killing me though. Good to know it's getting close but probably will still wait since I'll probably do a full wipe once it's ready and don't want to do it twice.
Sent from my Nexus 7 using Tapatalk
remedya said:
I noticed that your build has SELinux enforcing but this may be why the camera isn't working; something that still needs fixing.
Click to expand...
Click to collapse
I doubt that it's SELinux. Looking at the logcat the problem root seems to be the HAL and that we should use the CAF stack. Besides that some clocks seem to be out of sync (mainly front camera). If it would be SELinux, logcat/dmesg would show.
Download doesnt work
I will fix it as I compile the next version.
cb5264 said:
Camera does not work yet, but as far as I can see there are a few things in review to be submitted. Stay tuned as I will be building the rom again as soon as those changes are merged. In the meanwhile I may do some tinkering on my local build.
References:
https://review.lineageos.org/c/206914/
Click to expand...
Click to collapse
Some changes on 19 March.
Download link fixed btw
remedya said:
Some changes on 19 March.
Click to expand...
Click to collapse
Are these the changes needed to fulfill the LineageOS Device Support Requirement/camera recorder?
cb5264 said:
Download link fixed btw
Click to expand...
Click to collapse
Error 7
---------- Post added at 08:37 PM ---------- Previous post was at 08:19 PM ----------
Lol and now the download link is gone. Just stop. Wait for the official there is clearly a reason why its not been officially released yet.
First look at Build 2003 is really fine. Thanks for your hard work, Lady
Cam seems "two steps from hell" ...
https://review.lineageos.org/#/q/project:LineageOS/android_device_oneplus_bacon
interesting enough ?
The_Voice_70 said:
First look at Build 2003 is really fine. Thanks for your hard work, Lady
Cam seems "two steps from hell" ...
https://review.lineageos.org/#/q/project:LineageOS/android_device_oneplus_bacon
interesting enough ?
Click to expand...
Click to collapse
You had no problems flashing?
It's happening!
Sent from my A0001 using Tapatalk
TbagBaggins said:
You had no problems flashing?
Click to expand...
Click to collapse
Nope. No Problems.
The_Voice_70 said:
Nope. No Problems.
Click to expand...
Click to collapse
Im getting error 7. No other rom gives me error 7. Download link works on and off have tried installing twice same error.
Use latest official TWRP 3.2.1.0. No Problems with it. Error 7 seams to be old Recovery.