Hi fellow forum members!
I recently found great ROMS at Kevin's web storage. I tried them all and they work amazingly well except for one thing. When I make a call for a first time after a clean boot everything is fine. But when I make another call I can not hear anything nor the person I'm calling. After a reboot I have one shot again. Each time I want to call I need to reboot my phone. It only happens on CM 11 based GPROJ ROMS. Anyone encoutered this issue before? Any suggesting? Solutions?
Thanks, Zunex
nuraH6 said:
Quote:
Originally Posted by ShorelineDroid
Can anyone confirm the new nightly still has the call issue?
Alright, so after chatting with a CM maintainer we've been able to narrow it down to an upstream CM issue along with the phone not going into deep sleep. So, point is, no matter how many of our commits I revert it still won't fix the problem until CM fixes it on their end. I'm told it shouldn't take too long and will keep an eye on CM gerrit to see when an update is pushed into their code to fix these issues. So its not just PAC it's an LGOG gproj that sync'd to CM after 10/4.
Until the issue is resolved you can use the nightly 10/4 as it doesn't have the dialer or deep sleep issues and I will update when I hear more.
Click to expand...
Click to collapse
Same problem here on PAC-man ROM
I am facing the same issue with 10/13 nightly build. Its so frustrating to miss out so many important calls due to this call issue. They pulled back their 10/16 and 10/17 nightly build citing some major issue with the builds. Expecting a build asap with fixed call issue.
I had same problem. I was going back to CM snapshot-M11. This doesn't have call problem.
Is it fixed yet? Any news on this?
Updated today to cm-11-20141025-NIGHTLY-e975 but the calls bug is still there...
So, what should we do to solve this?
Fotonic said:
Updated today to cm-11-20141025-NIGHTLY-e975 but the calls bug is still there...
So, what should we do to solve this?
Click to expand...
Click to collapse
Thanks for the heads up. I don't know. I really don't wanna go back to stock because of dsp manager but this bug forces me to. Hope it gets fixed soon.
Reading This I found the solution to audio-caf problem. The solution is replace in system/lib/hw the library audio.primary.msm8960.so for a working one, I used the library from official M11 and now everything is OK. Attached is the library I used.
I installed the stock rom after this issus. I think the stock rom has a good battery life.
cabe2001 said:
Reading This I found the solution to audio-caf problem. The solution is replace in system/lib/hw the library audio.primary.msm8960.so for a working one, I used the library from official M11 and now everything is OK. Attached is the library I used.
Click to expand...
Click to collapse
Confirmed working!
Thanks cabe2001.
Does anyone have the skills to create a flashable zip that overwrites audio.primary.msm8960.so with a working version?
Is it as simple as deleting everything from a standard CM zip?
Related
Currently on this rom and gps is not working for me,.......Is it a bug? are there any specific gaps to use with this rom,..... maybe i need to change some permissions in the app security section? @deedwar
logcat file https://drive.google.com/file/d/0B1dyEUF7ImLrSlFQcHdhM1E1VWM/edit?usp=sharing
matej18 said:
Currently on this rom and gps is not working for me,.......Is it a bug? are there any specific gaps to use with this rom,..... maybe i need to change some permissions in the app security section? @deedwar
logcat file https://drive.google.com/file/d/0B1dyEUF7ImLrSlFQcHdhM1E1VWM/edit?usp=sharing
Click to expand...
Click to collapse
No problem i will take a look at it and see what i can do. Very busy at work over the next 2 days but i will see what i can do.
@deedwar This is probably known, but anyway, i decided to make a logcat; Installed today the new version, beta 4, ....and at first i noticed that the lightbulb does not work, gps problem goes on, and the camera app in this version will not even start,........, done a fresh install, wiped everthing,........, then went back to my recovery, started up version 3 and suddenly the camera in version 3 shows the same problems,.....this kernel of ours, hmmmm, just cant wait to see how the camera thing is going to fixed,..................... i like your work....
logcat: https://drive.google.com/file/d/0B1dyEUF7ImLrMkV1MlVZbHg0YTQ/edit?usp=sharing
after installation of some non stock camera app, the functionality of my camera is back on stock application and is working(version 4 rom)........,kinda strange and i hope this will last
matej18 said:
after installation of some non stock camera app, the functionality of my camera is back on stock application and is working(version 4 rom)........,kinda strange and i hope this will last
Click to expand...
Click to collapse
Camera and video sometimes takes a couple of reboots before it is working. Not sure why this is the case but it does solve the issue for me.
Thanks for the great work on XS, deedwar, could you elaborate more on the GPS issue? Have you experienced it?
Today I installed BETA4, and I am very satisfied with battery life and smoothness.
05/07 PA build has the same bug CM had where during a call every 10 seconds or so you hear two beeps. CM base already did a revert to fix this (see here) but I was wondering if there's a way this can be fixed while already running on PA? That is, can this be fixed without needing a new nightly.
no it needs to be compiled in.
Pirateghost said:
no it needs to be compiled in.
Click to expand...
Click to collapse
Think I found a quick/dirty fix for it. Replacing the files system\lib\hw\audio_policy.default.so and audio_policymsm8960.so with ones from a working build seems to have fixed it.
I would really like to know when someone finds a fix for this!
Click to expand...
Click to collapse
I can confirm that @bobbarker2's solution actually works! After a reboot of course.
Thanks,
-Elo
Q&A for [ROM+KERNEL][4.4.4] Stable CyanogenMod 11 [October 5, 2014]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
contacts issues
I am unable to import my contacts. I have tried to do so from my sim and also from a vcf file on an sd card. when trying from sim it simple doesn't work no message, nothing. When trying from the vcf file it says downloading and then nothing shows up once it says it is complete. I have verified using cm10.2 that the sim is readable (it works to get contacts there) and the vcf file is readable there also. I would love to use this rom but this issue makes it unusable not just a glitch. This is with the 9-23 version. I have also been unable to install the oct 5 version. I simply get install aborted error I have verified the sums and still con't install. Thank you for any help.
T989, Running 4.4 Stable, Calling doesn't work?
Title says it all. I recently flashed the 4.4 stable this past Sunday. The ROM runs really smooth compared to CM 11 nightlies, however when I receive a call and answer, I cannot hear them nor they can hear me. Have any ideas? I had the same problem on CM 11 nightlies as well.
Zzchechi said:
Title says it all. I recently flashed the 4.4 stable this past Sunday. The ROM runs really smooth compared to CM 11 nightlies, however when I receive a call and answer, I cannot hear them nor they can hear me. Have any ideas? I had the same problem on CM 11 nightlies as well.
Click to expand...
Click to collapse
I'm having the same problem. I can fix it temporarily by re-flashing the ROM, or even just going into recovery and wiping cache and dalvik cache. But after a day or so, the problem comes back. I know it's not a hardware mic/speaker problem because Hangouts calls work fine. This is very vexing.
I'm running CM 10.2.0.
Zzchechi said:
Title says it all. I recently flashed the 4.4 stable this past Sunday. The ROM runs really smooth compared to CM 11 nightlies, however when I receive a call and answer, I cannot hear them nor they can hear me. Have any ideas? I had the same problem on CM 11 nightlies as well.
Click to expand...
Click to collapse
pixbuf said:
I'm having the same problem. I can fix it temporarily by re-flashing the ROM, or even just going into recovery and wiping cache and dalvik cache. But after a day or so, the problem comes back. I know it's not a hardware mic/speaker problem because Hangouts calls work fine. This is very vexing.
I'm running CM 10.2.0.
Click to expand...
Click to collapse
Using Hangouts Dialer or video recording with the newest version of Snapchat causes this issue.
Sultanxda said:
Using Hangouts Dialer or video recording with the newest version of Snapchat causes this issue.
Click to expand...
Click to collapse
I uninstalled Hangouts Dialer, and have never used Snapchat, and I still have this problem.
Glad to have the Sultan back!
Hi Sultan,
I cannot post yet in the Development Forum but I am very glad that you are back developing again for the Hercules. I really love your ROM and Custom kernel.
Hercules 4.4.4 sultan issue 4x msaa
Hi I need some guidance, 4x msaa Will not save after reboot Along with many dev options also miecraft will freeze and reboot it 4x msaa is not on I was thinking permissions were incorrect but I tried some stuff to no avail. I can't help but feel there is a simple fix, plz help as I love this ROM and sultan and ghost and others work?
Hi all, I'm just wondering if there are others that have similar issue than mine?
The problem is that after updating my phone to CM13 20160922 version and any newer version, the touch screen would not work anymore on the ROM. Touch screen would still work in recovery.
I've tried to clean wipe before installation of ROM and the same problem persists.
If it helps, when I tried to install a new kernel (Xcelerate one) on the working ROM, the touch screen would also break.
Any help would be appreciated.
Do a clean install (by wiping cache, system, data) if you havent, and see if it helps. Can only suggest to take full logs (incl dmesg, and lastkmsg) and fetch it to fefifofum on the respective thread. Is the behaviour consistent or random? I face it randomly but I guess mine is a hardware fault.
The behavior is consistent. It always breaks the touch screen on the newer roms. I'll try to fetch the logs and maybe it would help. Thanks.
Anyone can help me with getting logs without a touch screen? ADB can't seem to connect and the device is unauthorized. Thanks for any help.
Well you are not the only one. Its all about drivers in kernel. I changed my digitizer and then with 6 or 7 touchscreen does not work although all fine in TWRP 3.0.2 Someone has to port those drivers to new kernel used in Android 6. i have little knowledge about it but i will try to fix it and if it works i will post it here-
mobaddict said:
updating my phone to CM13 20160922 version and any newer version,
Click to expand...
Click to collapse
wait do you mean it was working on cm13 before those versions ???
bauuuuu said:
wait do you mean it was working on cm13 before those versions ???
Click to expand...
Click to collapse
Yes, older CM13 version works. According to CM13 thread, it is the driver that doesn't work. I don't know how to fix the issue since this is a replacement screen and the driver works on older CM13.
... i will check
mobaddict said:
Yes, older CM13 version works. According to CM13 thread, it is the driver that doesn't work. I don't know how to fix the issue since this is a replacement screen and the driver works on older CM13.
Click to expand...
Click to collapse
OK.. I found the issue and fixed it. Atleast on my phone now the touch screen is working. I do not know the characteristics of you changed touchscreen but i can give you newly compiled version of cm13. You can confirm me if thats working for you !
bauuuuu said:
OK.. I found the issue and fixed it. Atleast on my phone now the touch screen is working. I do not know the characteristics of you changed touchscreen but i can give you newly compiled version of cm13. You can confirm me if thats working for you !
Click to expand...
Click to collapse
Okay. I can try. This is a replacement touch screen and is not an original one. I can try the compiled version that you made and see if that would fix the problem. Thanks
mobaddict said:
Okay. I can try. This is a replacement touch screen and is not an original one. I can try the compiled version that you made and see if that would fix the problem. Thanks
Click to expand...
Click to collapse
https://github.com/armani-dev/andro...mmit/7687212b3b2c083ac1929d3957239c76098bd886 its merged in the main device tree so i hope all the builds (and not only cm13) henceforth will be ok. i didnt get the time to compile everything yet.
bauuuuu said:
https://github.com/armani-dev/andro...mmit/7687212b3b2c083ac1929d3957239c76098bd886 its merged in the main device tree so i hope all the builds (and not only cm13) henceforth will be ok. i didnt get the time to compile everything yet.
Click to expand...
Click to collapse
Thank you. I'll try to check if this would work.
mobaddict said:
Thank you. I'll try to check if this would work.
Click to expand...
Click to collapse
I'll just wait for a kernel build since I don't know how to do this hehe
I am also facing the same problem after replacing my original broken touchscreen. I am not able to upgrade my rom to cm-14.1. Please suggest some help.
debasarkar said:
I am also facing the same problem after replacing my original broken touchscreen. I am not able to upgrade my rom to cm-14.1. Please suggest some help.
Click to expand...
Click to collapse
I think we just need to wait for a new build of the kernel and test if this solves our problem. I'm also waiting for a kernel build and will test it out if this would fix the issue. :good:
I don't know if the commit that was made by @bauuuuu was used in the new build of CM14.1 but the latest rom still has the touch screen issue. The new TWRP 3.0.2-1 is now also facing the same problem.
Looking at the source of CM14.1 kernel, the commit used was there so this means that this modification did not fix the touch screen issue for my device. Hoping to be able to find another solution
mobaddict said:
Looking at the source of CM14.1 kernel, the commit used was there so this means that this modification did not fix the touch screen issue for my device. Hoping to be able to find another solution
Click to expand...
Click to collapse
https://review.cyanogenmod.org/#/c/174024/
keep eye on new build there are more changes to match your touchscreen
bauuuuu said:
https://review.cyanogenmod.org/#/c/174024/
keep eye on new build there are more changes to match your touchscreen
Click to expand...
Click to collapse
Oh, wow! Hope that the 100Hz does the trick for my touchscreen and for others that are facing the same issue as me. Thank you for posting that. :good:
TWRP test build
Here is a test build for those with touchscreen issues. Please let me know if it works:
https://www.androidfilehost.com/?fid=313042859668276642
LineageOS 14.1 has been started.
https://download.lineageos.org/d2tmo
I'm running latest nightly with no problems so far.
Sent from my SGH-T999 using XDA-Developers Legacy app
Awesome to see this. I'm waiting on a few things to wrap up but will updating my t999 ASAP.
Questions, which exact gapps did you use ? Does lineage have their own forums ?
toro143 said:
Awesome to see this. I'm waiting on a few things to wrap up but will updating my t999 ASAP.
Questions, which exact gapps did you use ? Does lineage have their own forums ?
Click to expand...
Click to collapse
For Gapps: http://opengapps.org/
Lineage OS community: http://lineageos.org/community/
So far I'm loving it! Tried to dirty flash from CM but got an error.
So clean install and so far so good, must play with it some more and feels familiar
Thanks!
Camera crashes when going to movie mode. Open camera works fine.
Today weekly it's not installed. It gives an error code 7...
This problem was on cm roms before i ran linageos on my t999, usb tethering this service doesnt work when i turn on the wifi but when i restart my device and active it emediatly it works ,is there any solution ???
hi guys, i install this rom in my t999, and now i have a very rare problem ... i can't call, and no show signal ... (look the image), the problem become rare because i can recieve calls (says call from emergency service) and SMS ... i'm looking for this problem in google .. and nothing...
https://drive.google.com/open?id=0BxMZVpOD7gCdeWVEbHJjRlZ4UW8
https://drive.google.com/open?id=0BxMZVpOD7gCdd3FINWdEUUNnSDQ
what modem and nightly?
No sound at all
I recently experienced a problem after using CM 13 for quite a while on my S3 T-999. The phone doesn`t make any sound at all. Neither the speaker nor the microphone. I flashed LineageOS a few days ago but the problem still persists. I also tried Mokee rom but it also couldn`t get rid of this issue. I finally flashed stock rom and the sound is back. I can make calls and use youtube, the audio is just fine on stock rom.
The only problem is jellybean is too slow and battery consuming for my aging S3. Guy do you have any idea how can I make the sound work on this rom ? Any help would be appreciated.
What are the best custom Kernels to go with this ROM ???
is there any news about supporting d2 verisons or say goodbye to this device
hasan.sy said:
is there any news about supporting d2 verisons or say goodbye to this device
Click to expand...
Click to collapse
Support is discontinued.
hudson: Pull d2
* I don't have time to maintain these anymore
Click to expand...
Click to collapse
This device is still Rock solid and it's a shame we don't have support on this device anymore. I understand the developer though and I thank him for all his effort up until now. I hope someone else could continue his work on this great phone
pcaseiro said:
I hope someone else could continue his work on this great phone
Click to expand...
Click to collapse
Mokee rom updated every day. Carbon rom supporting too.
Hey, guys. Autocorrect for me isn't working even though it's on. When I type text in the virtual keyboard, it doesn't correct misspelled words. Any way to fix this?