Going to upload latest build of cm10.2
I made this rom for myself because Llior has removed his cm10.2 work. So, I started to compile again and made it again through sources. But I am going to upload soon. I want to see who are interested in this rom. By the way dont ask for eta. Well, I will make cm11 though too after this in my free time. Thanks Llior for device & kernel sources.
Known Issues:
Yes !!! They are still there -
1. No front camera
2. No led notification
Semi Working -
1. Wifi need workaround
2. Camera no gps error at all.
All other things are perfect.
Good job dude.
you need to check the call volume, make a phone call and see if you can hear or the other person can hear you.
Lloir said:
Good job dude.
you need to check the call volume, make a phone call and see if you can hear or the other person can hear you.
Click to expand...
Click to collapse
Thanks alot and Yes !!! But call-in-audio is very low... I didn't found mixer_paths.xml to incerase it. I set minimum cpu at 700mhz and max at 1000mhz no heating issues or Battery Drain too.
Well, I have a question I repo sync the cm-11.0 but while compiling there is error related to awesomeplayer.cpp audio.cpp which is basically related to audio files.
Error was something like "warning initializers failed (wreoder) error 1".
I think vendor is cause. Can You give some tips or help me? Or I have to do any commits?
veer.killerboy said:
Going to upload latest build of cm10.2
I made this rom for myself because Llior has removed his cm10.2 work. So, I started to compile again and made it again through sources. But I am going to upload soon. I want to see who are interested in this rom. By the way dont ask for eta. Well, I will make cm11 though too after this in my free time. Thanks Llior for device & kernel sources.
Known Issues:
Yes !!! They are still there -
1. No front camera
2. No led notification
Semi Working -
1. Wifi need workaround
2. Camera no gps error at all.
All other things are perfect.
Click to expand...
Click to collapse
I'm with you if you happen to get your work back. (Stolen laptop, sucks.)
I have a 32gb international HOX but bought this HOX+ recently because camera and sim werent working.
Plus, the 62gb is better.
There is android 5.0 development for the internation 32gb
So I think it would be great for anything 4.4 or higher for the HOX+
Even finding a decent 4.2 for the ATT seems difficult
International versions were hard to find in the states.
Thanks!
Ever get this out:?
veer.killerboy said:
Going to upload latest build of cm10.2
I made this rom for myself because Llior has removed his cm10.2 work. So, I started to compile again and made it again through sources. But I am going to upload soon. I want to see who are interested in this rom. By the way dont ask for eta. Well, I will make cm11 though too after this in my free time. Thanks Llior for device & kernel sources.
Known Issues:
Yes !!! They are still there -
1. No front camera
2. No led notification
Semi Working -
1. Wifi need workaround
2. Camera no gps error at all.
All other things are perfect.
Click to expand...
Click to collapse
Got link for the rom and what was the wifi fix again?
Tmobilefan906 said:
Got link for the rom and what was the wifi fix again?
Click to expand...
Click to collapse
Check 2nd post...
veer.killerboy said:
Check 2nd post...
Click to expand...
Click to collapse
Tried that. Didn't work
Tmobilefan906 said:
Tried that. Didn't work
Click to expand...
Click to collapse
WiFi can be used only through static IP or make your router IP static. Sources are not up to date so WiFi was never solved. This is the only work around. Change last 3 digit of IP. Count how many devices are connected if there is already 3 then make yourself 104 or 105... 101,102,103 is already allotted.
veer.killerboy said:
Check 2nd post...
Click to expand...
Click to collapse
Too bad you couldn't have made an updated rom for att
There was no need to escalate this with racial offenses by the OP. XDA will not tolerate any abuse from anyone in any form.
I did a thread cleanup and OP was temporarily banned.
Related
Whenever active data I get a popup window
"Call forwarding services has been disabled" in all roms lolipop.
Help !!!!!
dorantes_4 said:
Help !!!!!
Click to expand...
Click to collapse
i have been getting the same thing on illusion rom build 1/02. It is quite annoying. i am using this phone on ATT.
It seems to happen when I switch from lte to 3g
nemofbaby2010 said:
It seems to happen when I switch from lte to 3g
Click to expand...
Click to collapse
Seems to only affect people who are using the Verizon LG G3 on a GSM network.
Any idea which app is causing the popup?
This is on every 5.0 rom I have used
i have this problem toם ....????
I got this problem too, as long as I turned on data it pops up and never stop popping. I've tried to adjust the call forwarding option on the phone app, but it doesn't work. It happens only on one specific sim card which is without call forwarding service itself. It happens on all 5.0 roms that's a pain!
hope this helps
only work around i have found is to change to 2G and the popup will only show up once and after you dismiss it all is well. downside is that 2G is quite slow to browse and download but is works well for messaging like whatapps etc. i hope they can find a fix for this soon its the only reason why i changed back to stock..
same problem here. subscribed, hopefully someone finds a fix!
Apparently connect 2G this problem is significantly reduced.
It worked rom illusion.
Sent from my LG-VS985 using XDA Free mobile app
Connect to WiFi it should help out as well
help!
Please help!!!!
Subcribed
Same issue for me. Really sucks. Ive been using a latest version of pac roms untill a fix is found. If anyone knows of a way to read what causes the pop up i will work on that. Something like notification tracker but for popups. Also using this phone on straight talk.
Subscribing.
tengo el mismo problema?
solution 100% working
I got extremely tired of these pop ups as I'm sure many of you are tired as well so i took a chance all or nothing with a theory @daniel4653 came up with.
NOTE: Its not a fix for the VS985 ROMs just a bypass until the VS985 ROMs are fix.
Disclaimer: This procedure worked for me 100%. I dont take any responsibility for any issues you may or may experience. Understood? Ok. Proceed at your own risk!
With that said.
Download AT&T version of Illusion ROM.
here
http://forum.xda-developers.com/att-lg-g3/development/rom-illusion-2-1-d850-android-5-0-2-t2981226
Download Optimized SM-4.9.3 Kernel V2.2 for VS985
here
http://forum.xda-developers.com/verizon-lg-g3/development/kernel-optimized-sm-4-9-3-kernel-t2997489
Put both on your sdcard or internal memory
Boot into recovery
DO A FULL WIPE
Install illusion ROM
DO NOT REBOOT AFTER FLASHING THE ROM!
Install Optimized SM-4.9.3 Kernel V2.2 for VS985
Reboot and enjoy a pop up free lollipop ROM
I installed gapps after i saw that the ROM booted.
I have been using it for about 2hours and no pop ups in sight and all seems to be working. I've tested camera/video recording, calls in/out going, mic and speakers work and all sensors seems to be functional also. Not sure if I will experience any battery issues I will have to test it out and see.
I'm guessing this should work with other lollipop AOSP ROMs as long as they support other kernels.
I'm going to compare the ROMs and see if i can figure out a fix for the VS985 ROM until then this should work for all GSM users. :highfive:
r3al_0g said:
I got extremely tired of these pop ups as I'm sure many of you are tired as well so i took a chance all or nothing with a theory @daniel4653 came up with.
NOTE: Its not a fix for the VS985 ROMs just a bypass until the VS985 ROMs are fix.
Disclaimer: This procedure worked for me 100%. I dont take any responsibility for any issues you may or may experience. Understood? Ok. Proceed at your own risk!
With that said.
Download AT&T version of Illusion ROM.
here
http://forum.xda-developers.com/att-lg-g3/development/rom-illusion-2-1-d850-android-5-0-2-t2981226
Download Optimized SM-4.9.3 Kernel V2.2 for VS985
here
http://forum.xda-developers.com/verizon-lg-g3/development/kernel-optimized-sm-4-9-3-kernel-t2997489
Put both on your sdcard or internal memory
Boot into recovery
DO A FULL WIPE
Install illusion ROM
DO NOT REBOOT AFTER FLASHING THE ROM!
Install Optimized SM-4.9.3 Kernel V2.2 for VS985
Reboot and enjoy a pop up free lollipop ROM
I installed gapps after i saw that the ROM booted.
I have been using it for about 2hours and no pop ups in sight and all seems to be working. I've tested camera/video recording, calls in/out going, mic and speakers work and all sensors seems to be functional also. Not sure if I will experience any battery issues I will have to test it out and see.
I'm guessing this should work with other lollipop AOSP ROMs as long as they support other kernels.
I'm going to compare the ROMs and see if i can figure out a fix for the VS985 ROM until then this should work for all GSM users. :highfive:
Click to expand...
Click to collapse
Hey man you stole my theory and wrote up a guide. That is not cool.
I'm JP lol. That's exactly what i did. I figured it out on the 15th when I flashed the ATT ROM and it wouldn't boot up, so I went ahead and flashed the Verizon 5.0 kernel after and sure enough it booted.
http://forum.xda-developers.com/showthread.php?p=58203287
daniel4653 said:
Hey man you stole my theory and wrote up a guide. That is not cool.
I'm JP lol. That's exactly what i did.
Click to expand...
Click to collapse
lol.. i made sure i pointed out it was your theory all thanks goes to you. i just made a guide for everyone else to follow.
r3al_0g said:
lol.. i made sure i pointed out it was your theory all thanks goes to you. i just made a guide for everyone else to follow.
Click to expand...
Click to collapse
No worries. I'm glad you wrote it up. I was going to do it but I got caught up with work.
So I have built PAC LP Alpha, and everything works great except for the signal. Now if I remember correctly there was someone long ago that was working on getting the KK RIL working, anyone know who that was or if anyone wants to take a stab at it and see if they can fix the RIL or point me in the right direction. PM me if you'd like to try the LP Alpha, can't release til RIL is fixed and til the PAC team is ready to drop their 5.0.x nightlies.
Screenshots if people want to see some life for this phone.
MDMower has an operation CM12 build you can find info at http://forum.cyanogenmod.org/topic/104580-cm12-unofficial-for-fireball/. It boots and runs no problem, I can't check Signal issues because I don't have a Verizon SIM anymore. He does run a modified recovery to swap internal storage and data to make more room. Looks like this is the CM commit that gets radios working http://review.cyanogenmod.org/#/c/81243/.
Beeko said:
So I have built PAC LP Alpha, and everything works great except for the signal. Now if I remember correctly there was someone long ago that was working on getting the KK RIL working, anyone know who that was or if anyone wants to take a stab at it and see if they can fix the RIL or point me in the right direction. PM me if you'd like to try the LP Alpha, can't release til RIL is fixed and til the PAC team is ready to drop their 5.0.x nightlies.
Click to expand...
Click to collapse
Thank you I messaged him, and now I'm really curious how he got his CM12 to boot up, because when I built mine it wouldn't even boot.
wmuflyer said:
MDMower has an operation CM12 build you can find info at http://forum.cyanogenmod.org/topic/104580-cm12-unofficial-for-fireball/. It boots and runs no problem, I can't check Signal issues because I don't have a Verizon SIM anymore. He does run a modified recovery to swap internal storage and data to make more room. Looks like this is the CM commit that gets radios working http://review.cyanogenmod.org/#/c/81243/.
Click to expand...
Click to collapse
Pretty incredible what has been accomplished here.......I am going to be charging the old DINC 4g tonight!
IMPORTANT INFO:
-You must be on the VRUAMDK bootloader or you aren't going to be able to use this ROM. I'm sorry =(
(run this in a terminal to find out: getprop ro.bootloader )
-We have de-unified the Galaxy S4 line. This is for the Verizon variant (SCH-I545) only
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Download Links
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=jfltevzw&type=nightly
We have de-unified the Galaxy S4 line. Too many issues with having them all in one and a maintainer's nightmare. Look for jfltevzw builds now as opposed to the jflte builds you previously used.
Google apps addon:
Download: http://wiki.cyanogenmod.org/w/Google_Apps
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][Official] CyanogenMod 12.1 Nightlies for the Verizon Galaxy S4 (jfltevzw), ROM for the Verizon Samsung Galaxy S 4
Contributors
invisiblek
Source Code: http://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Firmware Required: VRUAMDK bootloader
Version Information
Status: Nightly
Created 2015-04-20
Last Updated 2015-04-19
I guess I'll post first.
Up and running on 4/20 (flashed a few hours ago). So far I have noticed:
As soon as you open the stock messaging app a notification appears saying a message could not be sent. Choosing "Discard" from the menu of the unsent message does not discard it.
The compass is not working properly. Orientation is slow to respond and is off by 180 degrees. This only happens when stationary. When viewing the sensors using Advanced Sensor Tester the magnetic sensor is showing some changes, the gyroscope sensor shows very little changes, and the orientation sensor shows one line out of three showing very little change. Don't know if it means anything.
Not sure if I am using the correct term here, but, Adaptive brightness does not seem to be responding well and overall the lower brightness setting of the display seem to be too dark. In an outdoor environment any brightness setting below 50% is pretty much unusable and the brightness when in direct light doesn't increase enough. (May not have described that correctly).
BT seems good with a Jabra earpiece. I have yet to test it with something like music play over Ford's Sync and vehicle BT.
Not sure if it is an Android 5.1 issue or not but I have had to reinstall several third party apps since going to CM12.1. Opening them results in a force close. If I navigate to the APK using root explorer, selecting it, and choosing install (to reinstall it) the app works correctly afterwards.
So far everything else seems to be working.
Logcat attached:
https://www.dropbox.com/s/khdo1uicmj8l7j8/Log_2015-04-20_14-07-16.txt?dl=0
ran the 4/18 and 4/19 build. BT works, connects but won't stream anything. First my "Music" app was force closing every time it tried to play, it kept trying so it was a loop of force closes from it. I disabled the Music app, i then started getting bluetooth share has forced closed errors.
im flashing the 4/20 build but won't be able to test bluetooth playback to my car until tomorrow.
i also have the damn #in my status bar all day long. can't get rid of it, have no idea what its doing up there. even stays through reboots.
Ok, I have come across another issue. I disconnected my Jabra BT earpiece earlier. Now it will not reconnect. BT has turned off and will not turn back on. Cycling airplane mode does not help.
Logcat:
https://www.dropbox.com/s/h86esc88wmth8pd/Log_2015-04-20_17-55-16.txt?dl=0
---------- Post added at 09:01 PM ---------- Previous post was at 08:57 PM ----------
Ok, a reboot seems to have straightened BT out for now. It is on and I can connect my earpiece.
BT was not playing nicely with my car, tried rebooting with no change. BT would connect, but I would get a "Bluetooth share has stopped" message
Sent from my SCH-I545 using Tapatalk
gmp029 said:
BT was not playing nicely with my car, tried rebooting with no change. BT would connect, but I would get a "Bluetooth share has stopped" message
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
get the same error. welcome to the club, looks like more bluetooth issues.
dansan382 said:
get the same error. welcome to the club, looks like more bluetooth issues.
Click to expand...
Click to collapse
I actually expected it, happens after every version change.
FernBch said:
I actually expected it, happens after every version change.
Click to expand...
Click to collapse
yup, i didn't think it would be any better but was worth on a shot. can tell you on the 4/20 build it connects to my car (with a little convincing) but only recognizes the hands free profile. won't push any audio across. also turning on bluetooth is super buggy, it never really turns on and just switches the slider back to off.
I've heard euroskank builds have it working but i really dont want to full wipe my device again for the 3rd time in a week lol. i signed up for a motorola credit account, waiting for the account number to come in the mail and then ordering my 64GB nexus 6. my nano sim card came yesterday which I know verizon will give me a hard time activating. I also have a sim card cutter, some cases and a screen protector coming tomorrow so either way this is happening.
dansan382 said:
yup, i didn't think it would be any better but was worth on a shot. can tell you on the 4/20 build it connects to my car (with a little convincing) but only recognizes the hands free profile. won't push any audio across. also turning on bluetooth is super buggy, it never really turns on and just switches the slider back to off.
I've heard euroskank builds have it working but i really dont want to full wipe my device again for the 3rd time in a week lol
Click to expand...
Click to collapse
I was on skank's 12.1 build until 4.17 version and BT did not stream in my car at all. It would connect, then i'd go to play music and DoubleTwist would just keep skipping to the next song without playing any audio. Then BT would be wierd and wouldnt connect/reconnect after that until a reboot.
So far I'm seeing the same funcionality on this ROM so it seems like something with the 12.1 base to me
vanberge said:
I was on skank's 12.1 build until 4.17 version and BT did not stream in my car at all. It would connect, then i'd go to play music and DoubleTwist would just keep skipping to the next song without playing any audio. Then BT would be wierd and wouldnt connect/reconnect after that until a reboot.
So far I'm seeing the same funcionality on this ROM so it seems like something with the 12.1 base to me
Click to expand...
Click to collapse
good to know. there is a never ending battle with this phone on bluetooth, the compass and MMS lol
dansan382 said:
good to know. there is a never ending battle with this phone on bluetooth, the compass and MMS lol
Click to expand...
Click to collapse
MMS was the easy fix. I made a few APN edits and it has worked ever since. What I did is in either the official thread or euroskanks thread. BT they will eventually fix. The compass, as we all know all too well, is a whole different story.
FernBch said:
MMS was the easy fix. I made a few APN edits and it has worked ever since. What I did is in either the official thread or euroskanks thread. BT they will eventually fix. The compass, as we all know all too well, is a whole different story.
Click to expand...
Click to collapse
Yea I followed your APN edits awhile back, still was hit or miss. the MMS would eventually come in but wasn't 100%. great roms though, i'm really liking lollipop
I started a bounty for the compass - http://forum.xda-developers.com/galaxy-s4-verizon/general/bounty-make-compass-cm-12-1-t3088991
Hello,
Thanks for you working on this ROM. My issue is I can't install it.
So I was running JFLTE-GPE 5.0.1 for a while now by Danvdh. I noticed that at one point the Model Number changed to the GPE and device was jltegpe (or something like that). It didn't bother anything until I tried to install this ROM when I received an error in TWRP that I can't install the ROM because it is only for the jfltevzw. Does anyone know how to fix this issue. I am now running Hyperdrive and build.prop is back to jfltevzw but I am still getting the same error message in TWRP.
I am on the Verizon model of the S4 running MDK, loki'ed the bootloader, and installed TWRP.
Thanks in advance.
Otakulad said:
Hello,
Thanks for you working on this ROM. My issue is I can't install it.
So I was running JFLTE-GPE 5.0.1 for a while now by Danvdh. I noticed that at one point the Model Number changed to the GPE and device was jltegpe (or something like that). It didn't bother anything until I tried to install this ROM when I received an error in TWRP that I can't install the ROM because it is only for the jfltevzw. Does anyone know how to fix this issue. I am now running Hyperdrive and build.prop is back to jfltevzw but I am still getting the same error message in TWRP.
I am on the Verizon model of the S4 running MDK, loki'ed the bootloader, and installed TWRP.
Thanks in advance.
Click to expand...
Click to collapse
You may have to go back to stock first (either by nandroid restore or via Odin).
FernBch said:
You may have to go back to stock first (either by nandroid restore or via Odin).
Click to expand...
Click to collapse
Thanks. I was thinking about that but since they are only nightlies and not everything is working, I'll wait.
well its been fun boys..
just got back from best buy with my unbranded nexus 6.. the GS4 was a great phone and a blast to use but these roms and their problems were driving me insane. enjoy the development, i'll probably keep an eye on whats going on. if anyone has a friend looking for an MDK bootloader GS4 on verizon let me know lol
dansan382 said:
well its been fun boys..
just got back from best buy with my unbranded nexus 6.. the GS4 was a great phone and a blast to use but these roms and their problems were driving me insane. enjoy the development, i'll probably keep an eye on whats going on. if anyone has a friend looking for an MDK bootloader GS4 on verizon let me know lol
Click to expand...
Click to collapse
another one bites the dust - first rajones19 and now you. I might follow soon. Too bad considering the jfltexx variant has no issues.
I am test running a Nexus 6. Next weekend is the final return date. It is big but I am getting used to it. Let's see if I want to keep it.
My decision will also depend on Google's wireless network announcement. If it sounds good, I will return this Nexus 6 and buy one from the play store and leave Verizon.
dansan382 said:
well its been fun boys..
just got back from best buy with my unbranded nexus 6.. the GS4 was a great phone and a blast to use but these roms and their problems were driving me insane. enjoy the development, i'll probably keep an eye on whats going on. if anyone has a friend looking for an MDK bootloader GS4 on verizon let me know lol
Click to expand...
Click to collapse
Well, you'll be missed here but you gotta do what you gotta do......
I've talked jumpin ship before but I'll probably hang on till the bitter lonely end. I'm just hardheaded like that. [emoji14]
Seriously though, if I want decent coverage across my work area (10K sq miles in eastern AZ and western NM) Big Red is the only real choice. Who knows, maybe when I do decide on a new device it will be rootable and possibly even exploited.
phonedawg said:
another one bites the dust - first rajones19 and now you. I might follow soon. Too bad considering the jfltexx variant has no issues.
I am test running a Nexus 6. Next weekend is the final return date. It is big but I am getting used to it. Let's see if I want to keep it.
My decision will also depend on Google's wireless network announcement. If it sounds good, I will return this Nexus 6 and buy one from the play store and leave Verizon.
Click to expand...
Click to collapse
FernBch said:
Well, you'll be missed here but you gotta do what you gotta do......
I've talked jumpin ship before but I'll probably hang on till the bitter lonely end. I'm just hardheaded like that. [emoji14]
Seriously though, if I want decent coverage across my work area (10K sq miles in eastern AZ and western NM) Big Red is the only real choice. Who knows, maybe when I do decide on a new device it will be rootable and possibly even exploited.
Click to expand...
Click to collapse
well its time to move on, i really love the GS4 even more than my galaxy nexus but its been 2 years. I had this GS4 since launch date, actually had it 3 days early. she served me well and i honestly could have gone a little longer with it but I got tired of dealing with flashing stock roms on my phone just for certain key things not to work right. Got tired of having to explain to people when something didn't work it was because of custom software. Plus looking at my GS4 it just feels small now. Honestly would have preferred a 5.5inch phone but I dont see this thing being a problem once i get use to it. I'll probably keep the GS4 around as a mess around device so I'll probably still flash some roms with it. Don't think there is much of a demand in the resale space for a 2 year old phone like this. I've learned my lesson though, and I should have learned it from having a galaxy nexus but from now on out I'll only be using nexus devices.
I debated switching to T-Mobile and honestly I'm still very interested in doing so. Like others, coverage is a big concern and even though here in Southern PA (right outside of Philly) I get great T-Mobile coverage, I'm still worried about the one time to go somewhere that has 0 coverage. I drive back and forth to Long Island, NY where I'm originally from every few weeks and T-Mobile coverage is outstanding that entire trip so that would be nice. If I was still on the island I would switch in a heartbeat. Being in PA now, 75% of this state is a blackhole for T-Mobile coverage which very much worries me, even though I never really go that far. Maybe by the end of the year I might make the switch but for now I'm sticking with big red, unfortunately.
Hi all
Please bare with me as I'm not the best when it comes to typing out what im thinking or trying to say
This info is mainly for our awesome devs but also for everyone else. Shout outs to @Unjustified Dev @DrakenFX @tdm and anyone else who can fix this
I was just wanting to help get this fixed as this one bug is keeping a lot of users including myself from moving away from stock and enjoying all the other roms available. I believe the bug has to do with the the work our beloved anonymous dev who helped correct the speaker issues a few months ago. Specifically this---> https://review.lineageos.org/#/c/168154/.
I'm pretty confidant it has nothing to do with any of the different modems people are flashing. I have tested this with all of the different modem versions for my G variant and none have made a difference
Also, there are other users that are getting this bug confused with another potential bug that has to do with distorted sound coming out when activating speakerphone while in call or something like that. I have not experienced that bug so I dont know the specifics. People are just using the term "Speakerphone bug" as both of these bugs involve the speakerphone
Now I can create the bug at will and have attached logcats below in the different scenarios. Hopefully the info is there for those who know how to fix
The steps I do to recreate the bug are as follows
1 - unlock phone and using the volume buttons, make sure the ringtone is NOT set to vibrate/silent and Do Not Disturb is NOT activated.
2 - Make a call. Call comes through earpiece as expected, no issues. Person on the other side can hear perfectly. Repeat as many times as you want, sound always comes through earpiece
3 - using volume buttons, reduce ringtone volume to vibrate/silent or turn on Do Not Disturb
4 - Make a call. Call comes through earpiece as expected, Hang up
5 - With the ringtone still set to silent/vibrate, turn the screen off using the power button and let it sit for about 5 - 10 seconds
6 - Unlock the phone and try to make a call. Call will connect but no sound will come from earpiece. Person on the other side can hear everything as per normal but we cant hear them
7 - While in call, toggle the speakerphone or if you have dial pad sounds enabled in the sound menu, press a number on the dial pad, sound now comes through earpiece as expected
From my testing and the procedure above, you can see that the bug happens when the phones ringer is put in silent/vibrate or when do not disturb is activated and the phone is locked/unlocked.
logcat 1 is with everything working normally, ringtone set to sound and call coming through earpiece as expected
logcat 2 is with ringtone set to silent and making a call. No sound comes from earpiece
logcat 3 is the same as 2 but during the call toggling speakerphone to fix
Now I dont know what is going on in the logs but I do see a lot of errors from "TFA9890"
This was all done on a fresh install of the universal bootloader, twrp 3.1.1.0, A2017G N Modem, latest LOS and Open Gapps mini and logcats were captured with MatLog on my G variant
Oh see this is Incredibly interesting, because tfa4990 is the route being used.... This is potentially incredibly helpful!!!!
I'm going to analyze these I've the weekend and see if I can figure something out. Thank you for the logs
Interesting timing on this post. I've been working on the axon7mini the past 10 days or so, and it also uses the tfa9890 amp. So I've started to familiarize myself with how all this stuff works. (I have pretty much zero experience with android audio in the past).
Fantastic post, well done. I have only encountered the problem a couple of times but upon reading what you wrote a little light bulb went off, that is exactly the situation that it occurs for me as well. It's this sort of interaction and support between the users and devs at xda have that makes it all so worthwhile. Thanks again.
As someone who's dealt with this bug for a long, long time... I have to commend you on a fantastic post. Thanks, and I hope this leads to a solution!
I hope this is looked into in the process of porting LOS 15. Would be cool to see this issue disappear.
Would this bug also happen on the U variant? I tried to recreate it using the steps above and it worked fine.
arecad said:
Would this bug also happen on the U variant? I tried to recreate it using the steps above and it worked fine.
Click to expand...
Click to collapse
I think I have read somewhere that it is not affecting U which might be the reason this has not yet been fixed but I cannot remember where I read this.
We would need the logs from an U variant to check if it looks the same.
sToRm1nG said:
I think I have read somewhere that it is not affecting U which might be the reason this has not yet been fixed but I cannot remember where I read this.
We would need the logs from an U variant to check if it looks the same.
Click to expand...
Click to collapse
It does affect the U variant. I have one and it happened a few times that when I would call someone I had no ringing tone coming from the earpiece unless I toggled the speakerphone on/off.
same problem here in a2017g aosp extended...
So I take it we can give up trying to solve this? Seems to exist in all non stock roms.
Wish someone would fix it. I don't even know where to begin, and with what I've read about the axon 9, i wont be switching phones for quite some time.
Knuxyl said:
Wish someone would fix it. I don't even know where to begin, and with what I've read about the axon 9, i wont be switching phones for quite some time.
Click to expand...
Click to collapse
simply use macrodroid fix it when phone call is activated.Speakerphone on ,speakerphone off .
Thats it
Dodgexander said:
So I take it we can give up trying to solve this? Seems to exist in all non stock roms.
Click to expand...
Click to collapse
Knuxyl said:
Wish someone would fix it. I don't even know where to begin, and with what I've read about the axon 9, i wont be switching phones for quite some time.
Click to expand...
Click to collapse
did you guys try the fix that @Miustone plasters all over XDA?
@Miustone Could you make a flashable zip with ONLY THAT ONE FIX for the Fluence stuff? Pretty please?
Choose an username... said:
did you guys try the fix that @Miustone plasters all over XDA?
@Miustone Could you make a flashable zip with ONLY THAT ONE FIX for the Fluence stuff? Pretty please?
Click to expand...
Click to collapse
Fluence settings will not fix driver implementation. Miustone's claims are misleading. I have tested it to death
The only way to fix would be by a Dev with audio skills. Good luck finding one. I've tried
Stay on a stock roms or risk not hearing in calls in other roms
Tebor said:
Fluence settings will not fix driver implementation. Miustone's claims are misleading. I have tested it to death
The only way to fix would be by a Dev with audio skills. Good luck finding one. I've tried
Stay on a stock roms or risk not hearing in calls in other roms
Click to expand...
Click to collapse
I fixed all Mic Bugs, Just the Echo is left which seams to came from /system/vendor/etc. Don't blame Me for the Bugs, i never touched the Sources of the Axon 7 and besides Kranoner has No Dev ever asked Me about it again. That My Patch is fixing Bugs means Just that there are Things Missing which are working and present on other Devices too...
I was coming from the LG G5 which has used almost the Same Fluence and Mic Configs as currently present in the Patch. Point.
Miustone said:
I fixed all Mic Bugs, Just the Echo is left which seams to came from /system/vendor/etc. Don't blame Me for the Bugs, i never touched the Sources of the Axon 7 and besides Kranoner has No Dev ever asked Me about it again. That My Patch is fixing Bugs means Just that there are Things Missing which are working and present on other Devices too...
I was coming from the LG G5 which has used almost the Same Fluence and Mic Configs as currently present in the Patch. Point.
Click to expand...
Click to collapse
Well, you have a chance to prove it! Make a flashable zip with ONLY the call bug fixes. If it actually fixes their problems then they'll believe you. otherwise they're right not to.
It's next to pointless using a custom rom if you want a good daily driver.
I bought this phone because I thought things like this could be solved this day and age but I won't be making that mistake next time!
Sent from my ZTE A2017U using Tapatalk
Miustone said:
I fixed all Mic Bugs, Just the Echo is left which seams to came from /system/vendor/etc. Don't blame Me for the Bugs, i never touched the Sources of the Axon 7 and besides Kranoner has No Dev ever asked Me about it again. That My Patch is fixing Bugs means Just that there are Things Missing which are working and present on other Devices too...
I was coming from the LG G5 which has used almost the Same Fluence and Mic Configs as currently present in the Patch. Point.
Click to expand...
Click to collapse
Omg who is blaming you for bugs? Your claiming you fixed it but many others still have this issue
This thread is not about mic issues. Please re-read first post and for the hell of it, check out the logcats. They might help you actually fix it
Unless your digging into the audio/dac driver code, I'm doubtful it will ever be fixed
Why do yall think its the driver? I dont have any problems with audio, its how the Phone app is handling it. If i was to debug this I would check the source for the Phone app and trace it from there. It seems like something might not be using the driver correctly, but the driver seems to be working fine. I could be wrong but I'm not new to linux and android, just no experience with audio development.
Maybe try installing stock phone app on LOS or RR and see if it still has problems. That would either show where the problem is or eliminate Phone app from being source of problem.
deleted
Do you mean RR.O hellsgate fixes the issue?
I do not understand your post.
nfsmw_gr said:
Do you mean RR.O hellsgate fixes the issue?
I do not understand your post.
Click to expand...
Click to collapse
OP updated.Not only flash Hellsgate.
hello all, i tried the fix on my RR-O 20180422 with hellsgate 2.1 from kraoner, it isn't still not working for me, i don't have any audio using the second sim.
del_piero3 said:
hello all, i tried the fix on my RR-O 20180422 with hellsgate 2.1 from kraoner, it isn't still not working for me, i don't have any audio using the second sim.
Click to expand...
Click to collapse
This isn't the bug you are thinking of.
The bug you have is related to dual sim.
Right now on oreo you can only make a call to the sim you are currently using data with. It is a separate bug.
Dodgexander said:
This isn't the bug you are thinking of.
The bug you have is related to dual sim.
Right now on oreo you can only make a call to the sim you are currently using data with. It is a separate bug.
Click to expand...
Click to collapse
hello,
thanks for your answer, then i didn't understand what the fix was made for.
Do we know already when the bug i am talking about will be fix roughly ? It is pretty annoying because the rest of the ROM works really good ...
Can anyone confirm if the OP's fix (Kernel and Mixer.zip) works for fixing the call bug? I previously tested a few of the common Oreo builds on my A2017U and ran into the 'call bug' with just about every build. It happened to me most often with incoming calls where I had to turn the speaker on and off to workaround it. I just finished flashing my Axon 7 or I would test this myself.
del_piero3 said:
hello,
thanks for your answer, then i didn't understand what the fix was made for.
Do we know already when the bug i am talking about will be fix roughly ? It is pretty annoying because the rest of the ROM works really good ...
Click to expand...
Click to collapse
No one seems to be able to fix it. All you can do is pray there is an official release from ZTE and someone is able to source a fix then. I have same problem as you and I hate it but there is nothing that can be done. Best to assume there will be no fix.
2000impreza said:
Can anyone confirm if the OP's fix (Kernel and Mixer.zip) works for fixing the call bug? I previously tested a few of the common Oreo builds on my A2017U and ran into the 'call bug' with just about every build. It happened to me most often with incoming calls where I had to turn the speaker on and off to workaround it. I just finished flashing my Axon 7 or I would test this myself.
Click to expand...
Click to collapse
I don't have any problems even without this zip using the latest AEX on oreo but as far as I know this has never been announced as being fixed so it wouldn't surprise me that it still exists.
Dodgexander said:
No one seems to be able to fix it. All you can do is pray there is an official release from ZTE and someone is able to source a fix then. I have same problem as you and I hate it but there is nothing that can be done. Best to assume there will be no fix.
I don't have any problems even without this zip using the latest AEX on oreo but as far as I know this has never been announced as being fixed so it wouldn't surprise me that it still exists.
Click to expand...
Click to collapse
As far as i know, the A2017G was supposed to get an official Oreo rom by end of this month, should arrive quite soon. The thing is that A2017 from China already have an official Oreo Rom, and i don't think these 2 phones have such different hardware component in it, don't you think ?
del_piero3 said:
As far as i know, the A2017G was supposed to get an official Oreo rom by end of this month, should arrive quite soon. The thing is that A2017 from China already have an official Oreo Rom, and i don't think these 2 phones have such different hardware component in it, don't you think ?
Click to expand...
Click to collapse
Yes but it's not really easy for someone to use the phone in Chinese and see if these bugs are there. If there is any chance of them being solved having an official English release will help more than an unofficial Chinese one.
With things to do with mobile networking this is even more the case which the dual sim bug is probably related to. (There are different basebands that the U & G models work with for example).
Dodgexander said:
Yes but it's not really easy for someone to use the phone in Chinese and see if these bugs are there. If there is any chance of them being solved having an official English release will help more than an unofficial Chinese one.
With things to do with mobile networking this is even more the case which the dual sim bug is probably related to. (There are different basebands that the U & G models work with for example).
Click to expand...
Click to collapse
i don't really understand what you're saying..?
The A2017 build obviously comes with other languages, why would you think otherwise (or not even check before saying that)? ?
Now, it being crap is beyond the scope of this comment of course
Choose an username... said:
i don't really understand what you're saying..?
The A2017 build obviously comes with other languages, why would you think otherwise (or not even check before saying that)? ?
Now, it being crap is beyond the scope of this comment of course
Click to expand...
Click to collapse
That's okay, I have yet to grasp what you are saying either.
Dodgexander said:
That's okay, I have yet to grasp what you are saying either.
Click to expand...
Click to collapse
all right, let's help each other
The Chinese ROMs come with English language, so nobody needs to use their phone in Chinese
Your dual sim statement is pretty weird