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.
Related
Hi, masters of ROMs!
As I can see - there is already Google Edition ROM was ported from i9505 phone. Is there possibility to port another greatest ROM - Android Revolution HD to i545? I will ask owner for permissions.
No need to wait or ask for a port, that rom most likely will be a multi carrier rom very soon. His work with the G3 version was awesome. Give him time. Actually it is the works now, he was waiting on a solid working aroma installer to work.
TheAxman said:
No need to wait or ask for a port, that rom most likely will be a multi carrier rom very soon. His work with the G3 version was awesome. Give him time. Actually it is the works now, he was waiting on a solid working aroma installer to work.
Click to expand...
Click to collapse
I asked him for permission for porting and he said - "no problem, go ahead". If he had in mind to port on i545 - he would tell me for sure.
Actually, I tried to install his ARHD for i9505 on my i545 - and Aroma Installer was working properly till the end. But ROM won't boot because of Verizon's security check (accordingly to the message on screen). I will try also to put in archive different kernel and to check through build.prop settings.
Also I am planning to take VRUAMDK base for porting, if none of developers will help me I was on HTC devices before and have some ROM-building experience.
Zer0r said:
I asked him for permission for porting and he said - "no problem, go ahead". If he had in mind to port on i545 - he would tell me for sure.
Actually, I tried to install his ARHD for i9505 on my i545 - and Aroma Installer was working properly till the end. But ROM won't boot because of Verizon's security check (accordingly to the message on screen). I will try also to put in archive different kernel and to check through build.prop settings.
Also I am planning to take VRUAMDK base for porting, if none of developers will help me I was on HTC devices before and have some ROM-building experience.
Click to expand...
Click to collapse
You got the warning message because you neglected to patch with loki.
Sent from my SCH-I545 using Tapatalk 4 Beta
najaboy said:
You got the warning message because you neglected to patch with loki.
Click to expand...
Click to collapse
May I ask you please to point me - where I can read about this loki patch?
Zer0r said:
May I ask you please to point me - where I can read about this loki patch?
Click to expand...
Click to collapse
The official faq is in the development forum.
Sent from my SCH-I545 using Tapatalk 4 Beta
Well, first run is successfull. Everything is working so far, except NFC and CDMA-networking (minor for me - I am using mostly GMS).
Any testers-volonteers? Was ported ARHD v. 2.0
UPD: No, NFC is also working.That was message about pay-over-NFC turning off.
GPS - tested. Camera, calls, SMS, USSD - everything is working. S-view cover support is also working. Running ktoonez's KT kernel - everything is just flying!
GSM was started up and even APN was set automatically and properly and 2G (EDGE) is working.
3G (HDSPA) is also working. Voice calling was testet both in 2G and 3G GSM networks.
UPD2: And I forgot to say - yes, Aroma Installer is working perfect.
Where is this file? I'll test it.
Thanks
TheAxman said:
Where is this file? I'll test it.
Thanks
Click to expand...
Click to collapse
Here it is. I am running it now as my daily driver also.
I have changed a little version number to 2.1, but this is only for make difference between original i9505 version and i545 port.
https://mega.co.nz/#!2Nhy0ZyI!CH4I7TEiEkpenrY6jnRDBW9BK_Ik-2X1AlCUXppJXBg
help
Hello Buddy,
I am new to this forum can u pls send me a link which can help me upload this rom to my verizon i545 i m having sms problem on internantional format
thanks in advance
parvinder
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
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
Hello to all
First of all i would like to say sorry if my english aren't so well
but i hope you readers can still get my point.
Here we go.
Straight to the topic, does anyone having this in-call bug while using an AOSP based roms?
Here is my situations,
If i call someone, or someone call me, i can only hear them.
In the contrary, they can't hear me.
It happens for me on Xenon HD 7.1.2 last build, AOSPExtended 7.1.2 last build and Cardinal AOSP 8.0 last build too.
I once have it working while using Xenon HD by flashing some zip and change some line in build.prop from "fluence" to "none" but i get no sound in speakerphone mode.
The reason i wrote this is because i really want to use AOSP based custom roms and i also need both call mode (normal call & speakerphone mode)
I really don:t think that this was a hardware issue since i got it working right on global stable MIUI8 and MIUI9, it works too on XIAOMI.EU latest rom.
For your information, i already try all fixes regarding this sound bug (on my side) i found here in this MIDO thread.
It's too much if i ask for fixes in this stage so i just need someone who are in the same state like me to confirm that they are facing the same problem.
or is it just me?
Thank you guys
it was really only me and Mr @nasko_spasko have this bug? no other? really?
Did you check these posts already? Did you try them already?
https://forum.xda-developers.com/showpost.php?p=73914743&postcount=188
https://forum.xda-developers.com/showpost.php?p=73870036&postcount=186
The problem is known for ages now and - as you can see - there is a solution with explanation.
What are the fluence related built.prop values in your ROM?
crok.bic said:
Did you check these posts already? Did you try them already?
https://forum.xda-developers.com/showpost.php?p=73914743&postcount=188
https://forum.xda-developers.com/showpost.php?p=73870036&postcount=186
The problem is known for ages now and - as you can see - there is a solution with explanation.
What are the fluence related built.prop values in your ROM?
Click to expand...
Click to collapse
Thank you for replying @crok.bic
I got it fixed by doing 2 steps as @mirfatif explained here
Editing fluencetype in build.prop from "fluence" to "none"
manually adding this line to "audio_platform_info.xml
<device name="SND_DEVICE_OUT_VOICE_SPEAKER" acdb_id="50"/>
Click to expand...
Click to collapse
reboot and profit
I've updated the unofficial ROM for LineageOS 14.1 on the Moto E4 Plus (Qualcomm).
CDMA Carriers such as Verizon, Sprint, Boost, and possibly more now working fully, mms and all with no gimmicks!
Known Working:
Sound
Camera
GPS
Gyroscope
Bluetooth
Fingerprint Scanner
Wifi
CDMA Carriers, Verizon, Sprint, Boost, and possibly more!
FMRadio NEW!
Prerequisites:
Unlocked Bootloader
TWRP Recovery for Moto E4 Plus (Qualcomm)
Stock ROM installed to your device, for mobile data provisioning.
Installation:
Have stock ROM installed and data provisioned correctly. This is an important step to have any chance of LTE working for your device.
Download ROM zip below and move to external sd storage
Boot into TWRP recovery and make a backup of stock if you wish.
Wipe cache, system, and data.
Flash the lineage ROM zip provided on this thread.
Wipe cache/dalvik and reboot system.
Complete setup.
March 6th 2018:
FM Radio added! Hotspot fixed for Sprint and Sprint MVNO's (Boost)! CMActions coming soon!
Download March 6th 2018 Build
Download March 6th 2018 Build Mirror
XDA:DevDB Information
LineageOS 14.1 for Moto E4 Plus (Qualcomm), ROM for the Moto E4 Plus
Contributors
SeanStar, squid2
Source Code: https://github.com/MotoOwensDevel
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Based On: LineageOS
Version Information
Status: Beta
Created 2018-01-12
Last Updated 2018-03-17
Is the build not available to test?
Cleanser2012 said:
Is the build not available to test?
Click to expand...
Click to collapse
Take a look at the downloads tab of the project. There is a build available.
SeanStar said:
Take a look at the downloads tab of the project. There is a build available.
Click to expand...
Click to collapse
You may want to put the download link in the OP so that those using one of the XDA apps can access it easier as there is no download tab in the app.
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
SeanStar said:
Take a look at the downloads tab of the project. There is a build available.
Click to expand...
Click to collapse
Also is selinux enforcing?
Everything seems to be working fine on my end, I installed this on my boost version seems to have sim unlocked it. Currently using it on T-Mobile
Gonna try this when I get home
Cleanser2012 said:
Everything seems to be working fine on my end, I installed this on my boost version seems to have sim unlocked it. Currently using it on T-Mobile
Click to expand...
Click to collapse
This ROM actually sim unlocked your phone? I may be half tempted to get a boost Owens when my harpia kills over...
jasonmerc said:
This ROM actually sim unlocked your phone?
Click to expand...
Click to collapse
Yes, calls and text messages seem to work fine, mms as well. I don't have data on the sim I'm using so can't test that. I noticed the last lineage build by ReimuHakurei had sim unlocked it for messages at least but calls wouldnt work. Im assuming calls didnt work because sound didnt work on that build. I had flashed the stock firmware from the unlocked version onto my boost version hoping it would unlock it but it didnt. So far this build everything is working really well
soaringowl2145 said:
You may want to put the download link in the OP so that those using one of the XDA apps can access it easier as there is no download tab in the app.
Click to expand...
Click to collapse
Thanks, added that.
soaringowl2145 said:
Also is selinux enforcing?
Click to expand...
Click to collapse
Yes, it is. Take a look: https://drive.google.com/file/d/11bhIyHmlPjP1KoQYcJNb7xokqFEWHdyr/view
Cleanser2012 said:
Yes, calls and text messages seem to work fine, mms as well. I don't have data on the sim I'm using so can't test that. I noticed the last lineage build by ReimuHakurei had sim unlocked it for messages at least but calls wouldnt work. Im assuming calls didnt work because sound didnt work on that build. I had flashed the stock firmware from the unlocked version onto my boost version hoping it would unlock it but it didnt. So far this build everything is working really well
Click to expand...
Click to collapse
Good to hear. Owens is a great device, I'm glad you now have some stable trees to continue development with. As a matter of fact, I'm in the process of porting another ROM for this here.
jasonmerc said:
Good to hear. Owens is a great device, I'm glad you now have some stable trees to continue development with. As a matter of fact, I'm in the process of porting another ROM for this here.
Click to expand...
Click to collapse
What rom?
Only thing not working for me is videos so far. YouTube will work on the website but not the app. Snapchat videos also aren't playing for me. Sound works but no video. Anyone else having this issue?
Cleanser2012 said:
Only thing not working for me is videos so far. YouTube will work on the website but not the app. Snapchat videos also aren't playing for me. Sound works but no video. Anyone else having this issue?
Click to expand...
Click to collapse
Thank you for reporting this, I'm looking into it now.
edit:
Seems to be a build.prop issue, I'm fixing it now.
Have no data on boost
SeanStar said:
Thank you for reporting this, I'm looking into it now.
edit:
Seems to be a build.prop issue, I'm fixing it now.
Click to expand...
Click to collapse
Have you fixed this? And can we fix it without reflashing the ROM ourselves?
TheJAYpoop said:
Have you fixed this? And can we fix it without reflashing the ROM ourselves?
Click to expand...
Click to collapse
Yes, though I'm packing another ROM with it now.
Flash the attached zip to fix it without downloading the new ROM I'm about to upload.
SeanStar said:
Yes, though I'm packing another ROM with it now.
Flash the attached zip to fix it without downloading the new ROM I'm about to upload.
Click to expand...
Click to collapse
Thanks dude, trying it out now!
Everything working great thanks for the effort
rom works great thank you brother. look forward to possible nightlies and oero.
Any findings on the boost data not working? I want to try this but am on boost