hi guys,
I'm working on CM-11-20140606-NIGHTLY.
currently I'm facing two problems:
1- when i plug my headset, if anyone calls ringing be in the headset it self, so if i'm not beside my note i'll never hear it.
i didn't face this issue in stock rom as ringing works with both mobile itself and headset at the same time.
so, is there any way i can follow to make it act as stock rom??
2- some times when i press home button to use it, soft buttons lightened but screen still black and no way to make mobile works again unless i restart it.
3- on stock rom i used to install xposed installer and apply "enable call recording" and was working flawlessly by replacing add button by record, now it doesn't work and need it sometimes.
any suggestions?
NaAZoOR said:
hi guys,
I'm working on CM-11-20140606-NIGHTLY.
currently I'm facing two problems:
1- when i plug my headset, if anyone calls ringing be in the headset it self, so if i'm not beside my note i'll never hear it.
i didn't face this issue in stock rom as ringing works with both mobile itself and headset at the same time.
so, is there any way i can follow to make it act as stock rom??
2- some times when i press home button to use it, soft buttons lightened but screen still black and no way to make mobile works again unless i restart it.
3- on stock rom i used to install xposed installer and apply "enable call recording" and was working flawlessly by replacing add button by record, now it doesn't work and need it sometimes.
any suggestions?
Click to expand...
Click to collapse
Hey there! Let's see:
1. I really have no idea what could be happening...try asking on the CM11-Nightlies Discussion forum or the devs at the Development thread.
2. Are you sure the screen STAYS black?? On my phone, I get the black screen with softkeys lighting up, but display turns on after a good 10 second lag...
3. What exactly is the problem here? Is the record button not displaying? Does the module support KitKat?
Try disabling the module>reboot>re-enable>reboot. If that doesn't help, uninstall and re-install the entire Xposed Framework.
Xposed-related problems don't usually get support but you can ask at the discussion thread linked above.
The Dork Knight Rises said:
Hey there! Let's see:
1. I really have no idea what could be happening...try asking on the CM11-Nightlies Discussion forum or the devs at the Development thread.
2. Are you sure the screen STAYS black?? On my phone, I get the black screen with softkeys lighting up, but display turns on after a good 10 second lag...
3. What exactly is the problem here? Is the record button not displaying? Does the module support KitKat?
Try disabling the module>reboot>re-enable>reboot. If that doesn't help, uninstall and re-install the entire Xposed Framework.
Xposed-related problems don't usually get support but you can ask at the discussion thread linked above.
Click to expand...
Click to collapse
1- I'll check above links, thanks.
2- may be i didn't wait for a whole 10 seconds, usually i restart it after a press or two.
will wait and check.
3- probably module isn't compatible as it was updated 25-7-2013.
I've tried uninstall and reinstall both module and Xposed framework.
many thanks for your interest.
NaAZoOR said:
1- I'll check above links, thanks.
2- may be i didn't wait for a whole 10 seconds, usually i restart it after a press or two.
will wait and check.
3- probably module isn't compatible as it was updated 25-7-2013.
I've tried uninstall and reinstall both module and Xposed framework.
many thanks for your interest.
Click to expand...
Click to collapse
You're welcome(though you COULD just hit the Thanks button next time, yknow )
And yeah, try waiting for a few seconds for the black screen problem...I'm pretty sure we're having the same problem...
Related
I am running the Slide2Unlock Pro 1.4 and I am having trouble with this app activating during phone calls and making it difficult to get back to the dialer.
Two questions
1. does anyone know how to stop this from happening?
2. How can I get the phone to maintain the back light etc on during the call so I do not have to hit extra buttons to wake the phone up again.
Thanks again.
1 word. kaisertweak
I had enough trouble with Slide2Unlock that I had to un-install it. The problems that I had were:
1. the latest AT&T ROM did not obey KaiserTweak settings
2. this led to the problems that you are having
3. the program (I have no idea how) was draining the battery way too fast. Removing it has seemed to stop the battery drain.
Bill
download said:
I am running the Slide2Unlock Pro 1.4 and I am having trouble with this app activating during phone calls and making it difficult to get back to the dialer.
Two questions
1. does anyone know how to stop this from happening?
2. How can I get the phone to maintain the back light etc on during the call so I do not have to hit extra buttons to wake the phone up again.
Thanks again.
Click to expand...
Click to collapse
Hi there, guys.
I did a wide search in Google/XDA/whatever and didn't manage to find anything related to my problem, so I'm posting it here :good:
My S3 Mini (I8190N) runs flawless and quite smooth on NovaFusion/Maclaw 20140524. Using Gravity Box for enabling navbar (since the I8190N loses its capacitive buttons when changes the kernel) did the trick and fully usable...
Except for one little BIG bug: everytime I receive a notification (Whatsapp, Gmail, FB, SMS, calls, doesn't matter which app) while the screen is off, it reboots. Every. Single. Notification. Cause of this, my battery lasts just a couple of hours, since is rebooting non stop, and I lose a lot of important things (calls, alarms, SMS, you name it)
I tried some things:
- Installing today's NovaFusion release (didn't solved);
- Clean installing 20140524 again (nope) and clean installing today's release (nope again);
- Removing Xposed and Gravity Box (I thought it could be some incompatibility, but nope);
- Disabling lockscreen (to test if the problem was with lockscreen itself, but no).
Following the logic, it appears to be something related to notifications waking up the screen (the phone even vibrates a little before restarting again), but I didn't find any configuration related to this.
So please, anyone? Any advices? Any solutions? This issue is getting me heads off
Strange bug indeed and i have no idea why. The vibration on boot is always there to tell that bootloader boots. Its easier to troubleshoot a black phone that way, according to the service manual.
Sent through time and space from my s3mini/CM11
Jucarez said:
Hi there, guys.
I did a wide search in Google/XDA/whatever and didn't manage to find anything related to my problem, so I'm posting it here :good:
My S3 Mini (I8190N) runs flawless and quite smooth on NovaFusion/Maclaw 20140524. Using Gravity Box for enabling navbar (since the I8190N loses its capacitive buttons when changes the kernel) did the trick and fully usable...
Except for one little BIG bug: everytime I receive a notification (Whatsapp, Gmail, FB, SMS, calls, doesn't matter which app) while the screen is off, it reboots. Every. Single. Notification. Cause of this, my battery lasts just a couple of hours, since is rebooting non stop, and I lose a lot of important things (calls, alarms, SMS, you name it)
I tried some things:
- Installing today's NovaFusion release (didn't solved);
- Clean installing 20140524 again (nope) and clean installing today's release (nope again);
- Removing Xposed and Gravity Box (I thought it could be some incompatibility, but nope);
- Disabling lockscreen (to test if the problem was with lockscreen itself, but no).
Following the logic, it appears to be something related to notifications waking up the screen (the phone even vibrates a little before restarting again), but I didn't find any configuration related to this.
So please, anyone? Any advices? Any solutions? This issue is getting me heads off
Click to expand...
Click to collapse
Since there seem to be issues with the capacitive button lights on your device, I would assume that the problem is with BLN (Back light notification) which activate the capacitive button backlights when you receive a notification and the screen is off.
I would suggest that you check to see if BLN is enabled and disable it. There is a BLN Control App in the Play store :good:
Meticulus said:
Since there seem to be issues with the capacitive button lights on your device, I would assume that the problem is with BLN (Back light notification) which activate the capacitive button backlights when you receive a notification and the screen is off.
I would suggest that you check to see if BLN is enabled and disable it. There is a BLN Control App in the Play store :good:
Click to expand...
Click to collapse
This makes a HUGE sense! :victory:
(still weird, tho, that only the I8190N loses its capacitive buttons on new kernel, but not entering this discussion haha)
Will try this, @Meticulus. Thanks in advance
Download Disable_BLN.zip and flash in recovery. See if it works. My backlight are always off with this flashed.
https://app.box.com/s/ybzhlojc807u8srw8lep
Sent through time and space from my s3mini/CM11
i have the i8190 and have the same problems
So I'm using Carbon and Slimkat, works perfectly fine
Jucarez said:
This makes a HUGE sense! :victory:
(still weird, tho, that only the I8190N loses its capacitive buttons on new kernel, but not entering this discussion haha)
Will try this, @Meticulus. Thanks in advance
Click to expand...
Click to collapse
Did you try it ?
tys0n said:
Download Disable_BLN.zip and flash in recovery. See if it works. My backlight are always off with this flashed.
https://app.box.com/s/ybzhlojc807u8srw8lep
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
Thank you! Now it works perfectly fine Finally found the solution after few months, thank you!
Hi guys,
I tried it. It's working perfectly. Hallelujah!
Now I'm discovering the Xposed to do a lot of other things (autohide the navbar, disable the "3-dot" button on apps, etc)
Thank you very much!
down
tys0n said:
Download Disable_BLN.zip and flash in recovery. See if it works. My backlight are always off with this flashed.
https://app.box.com/s/ybzhlojc807u8srw8lep
Click to expand...
Click to collapse
LMH1998 said:
Thank you! Now it works perfectly fine Finally found the solution after few months, thank you!
Click to expand...
Click to collapse
Jucarez said:
I tried it. It's working perfectly. Hallelujah!
Click to expand...
Click to collapse
Unfortunately, the workaround "patch" is not available anymore :crying:
would it be possible to upload it again anywhere, maybe here?
or is there another possibility to fix that problem yet?
Hi all... I basically have two problems. First of all, I got the Z3C happily rooted... The problems are:
1- Tap2wake simply doesn't work, regardless of how I tap... fast, slow, super fast, thumb, index finger, etc... enable it/ disable it... same issue... refuses to work.
2- I use exDialer for my dialer... It works great (I've been using it for a couple of years)... the problem arises when I miss or reject a call. When this happens, Sony'x Phone apk (forgot the exact name) crashes. I have to acknowledge the notification of the crash and everything continues to work... strange ha?
Any ideas what can be going on? Thanks!
Carlos
Did you uninstall Xperia Home? That will cause the phone app to crash on calls as you describe.
I assume you have the option for tap to wake checked? Possibly you uninstalled something that it needs? Never ran into that particular issue.
Can't comment on issue #2, but T2W works flawless for me in 99.9% of the cases (with firmware .98).
Did you (now it might be too late) check whether both problems were there before you unlocked the BL?
What firmware version are you using?
Thanks.. Yeap. too late... already rooted...
Regarding #1, still doesn't work. Even after unfreezing Xperia home, which indeed fixes #2...
Thanks!!!
Carlos
so I've frozen some apps on the z3c, but I can't quite figure out which one controls the tap2wake function. I've tried the trial and error way (freeze/unfreeze), but can't narrow it down. Any of you have any ideas which apk controls that?
Thanks again!!
Carlos
Chaleman said:
so I've frozen some apps on the z3c, but I can't quite figure out which one controls the tap2wake function. I've tried the trial and error way (freeze/unfreeze), but can't narrow it down. Any of you have any ideas which apk controls that?
Thanks again!!
Carlos
Click to expand...
Click to collapse
You can just turn it off in Display settings.
Kev1000000 said:
You can just turn it off in Display settings.
Click to expand...
Click to collapse
Thanks Kev. What I ment to say is that I want to be able to ENABLE it... I have it ticked on, but since I froze some APKs, it's not working. I wish to know if anyone knows which one is it to unfreeze it (if that's the case). I've tried but I havent been able to figure it out.
Best regards,
Carlos
I brought nexus 6 few weeks back and I am facing below issues. Are these known issues and something to do with settings
1. Apps randomly hangs and doesn't close cleanly
2. Lag in display in caller while dialing through caller history
3. Incoming call doesn't display automatically when in battery saver mode
4. While on speaker at high volume some blur kind of noise
5. At times notifications on lock screen doesn't respond even after double click
6. Overall OS sluggishness at times randomly.
Yes, most of them are common.
Capri72 said:
I brought nexus 6 few weeks back and I am facing below issues. Are these known issues and something to do with settings
1. Apps randomly hangs and doesn't close cleanly
2. Lag in display in caller while dialing through caller history
3. Incoming call doesn't display automatically when in battery saver mode
4. While on speaker at high volume some blur kind of noise
5. At times notifications on lock screen doesn't respond even after double click
6. Overall OS sluggishness at times randomly.
Click to expand...
Click to collapse
Most of these are common gripes, none can be corrected natively, but some can be corrected through different Rom's and such.
so basically all these problens could be fixed by the android 5.1 upgrade right? cause i have most of them issues... freezing apps is the worst.
ripped85 said:
so basically all these problens could be fixed by the android 5.1 upgrade right? cause i have most of them issues... freezing apps is the worst.
Click to expand...
Click to collapse
nobody knows that, since android 5.1 is not released, and nobody knows what is included with it. but most of these issues that are reported here are user types of issues. meaning its your setup that will fix or break these things. like freezing apps you said.. that doesnt happen over here. usually its your setup or types of apps used that will cause that(apps not ready for lollipop).
That opens a big can of worms.
simms22 said:
nobody knows that, since android 5.1 is not released, and nobody knows what is included with it. but most of these issues that are reported here are user types of issues. meaning its your setup that will fix or break these things. like freezing apps you said.. that doesnt happen over here. usually its your setup or types of apps used that will cause that(apps not ready for lollipop).
Click to expand...
Click to collapse
MMV, but the update should make things more definable. What apps a user may have and whether or not they are updated to work on lollipop should not be such a drastic issue, In a perfect world, Google should provide for backward compatibility or come out with a whole new version of their operating system; I.E. Windows 7 as opposed to Windows 8.
I recently put a different ROM in and used open minded Gapps for some idotic reason and now Nexus just reboots to password needed which I don't remember and it won't go into recovery at all so I can't factory reset it.
[email protected] said:
I recently put a different ROM in and used open minded Gapps for some idotic reason and now Nexus just reboots to password needed which I don't remember and it won't go into recovery at all so I can't factory reset it.
Click to expand...
Click to collapse
You should still be able to enter recovery using the key combination:
- power off the phone; can usually be done by pressing the power button a very long time.
- hold volume down and power button to power up. This should get you to the bootloader screen.
- here, select recovery using volume + power keys.
PS: it's better to start a new thread rather than reuse an old one that doesn't exactly match your problem.
runekock said:
You should still be able to enter recovery using the key combination:
- power off the phone; can usually be done by pressing the power button a very long time.
- hold volume down and power button to power up. This should get you to the bootloader screen.
- here, select recovery using volume + power keys.
PS: it's better to start a new thread rather than reuse an old one that doesn't exactly match your problem.
Click to expand...
Click to collapse
Sorry lol had to hook it to laptop and run Nexus toolkit
Hi, i've faced op7 pro sensor's frustrating issue , screen lights while im in a call , when listening to voice notes , etc..
after 7 hours of trials , simply i found a solution , it's a lifesaver
the solution is to download Proximity Sensor Reset/Fix (+Overrider service) app from playstore , skip the first step , second step put your phone to your ear and press next , third step Keep it out of your ear and press next, you're done , restart your phone & keep the app installed so the saved parameter keeps loading whenever you restart your phone , now try to make a call or listen to a voice note and press thanks button :good:
I tried this before on my OP7 and it didn't help.
KhaledMohamed26 said:
Hi, i've faced op7 pro sensor's frustrating issue , screen lights while im in a call , when listening to voice notes , etc..
after 7 hours of trials , simply i found a solution , it's a lifesaver
the solution is to download Proximity Sensor Reset/Fix (+Overrider service) app from playstore , skip the first step , second step put your phone to your ear and press next , third step Keep it out of your ear and press next, you're done , restart your phone & keep the app installed so the saved parameter keeps loading whenever you restart your phone , now try to make a call or listen to a voice note and press thanks button :good:
Click to expand...
Click to collapse
Work perfectly now thanks but I made all the steps and rebooted the phone.
KhaledMohamed26 said:
Hi, i've faced op7 pro sensor's frustrating issue , screen lights while im in a call , when listening to voice notes , etc..
after 7 hours of trials , simply i found a solution , it's a lifesaver
the solution is to download Proximity Sensor Reset/Fix (+Overrider service) app from playstore , skip the first step , second step put your phone to your ear and press next , third step Keep it out of your ear and press next, you're done , restart your phone & keep the app installed so the saved parameter keeps loading whenever you restart your phone , now try to make a call or listen to a voice note and press thanks button :good:
Click to expand...
Click to collapse
I can confirm this works, thx (Y)
ok.. too early to report back.. will keep it installed and see if it works.
Proximity sensor was indeed a headache in OP7pro
The phone need to be rooted right? I tried covering the sensor, but the app doesn't seem to be registering any action.
GalosSide said:
The phone need to be rooted right? I tried covering the sensor, but the app doesn't seem to be registering any action.
Click to expand...
Click to collapse
I set it without root, and it works with no problem here !
Just flash that persist image in fastboot and all will be solved
Hi, which persist image is this and is this just a simple flash via fastboot? Will I lose recovery when doing so? Any other precautions to take?
thznutz87 said:
Just flash that persist image in fastboot and all will be solved
Click to expand...
Click to collapse
amirage said:
Hi, which persist image is this and is this just a simple flash via fastboot? Will I lose recovery when doing so? Any other precautions to take?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/help/request-stock-persist-img-t4093885
Fastboot flash persist persist.img
KhaledMohamed26 said:
Hi, i've faced op7 pro sensor's frustrating issue , screen lights while im in a call , when listening to voice notes , etc..
after 7 hours of trials , simply i found a solution , it's a lifesaver
the solution is to download Proximity Sensor Reset/Fix (+Overrider service) app from playstore , skip the first step , second step put your phone to your ear and press next , third step Keep it out of your ear and press next, you're done , restart your phone & keep the app installed so the saved parameter keeps loading whenever you restart your phone , now try to make a call or listen to a voice note and press thanks button :good:
Click to expand...
Click to collapse
Hi,
Wouldn't it better to provide the application link ?
solid.snake said:
Hi,
Wouldn't it better to provide the application link ?
Click to expand...
Click to collapse
Are you that bored that you had to make such a comment on a thread 6 months old?
And if you're still so lazy to actually look for the apk, here you go. https://play.google.com/store/apps/details?id=com.mobiledirection.proximitysensorreset
hallo dare said:
Are you that bored that you had to make such a comment on a thread 6 months old?
And if you're still so lazy to actually look for the apk, here you go. https://play.google.com/store/apps/details?id=com.mobiledirection.proximitysensorreset
Click to expand...
Click to collapse
Thanks, but no, Im not lazy, just head to Playstore and hit for "proximity sensor reset" and you tell me then.
Are you that bored that you had to make such a comment on a thread 6 months old? >> Indeed
solid.snake said:
Thanks, but no, Im not lazy, just head to Playstore and hit for "proximity sensor reset" and you tell me then.
Are you that bored that you had to make such a comment on a thread 6 months old? >> Indeed
Click to expand...
Click to collapse
Funny that i was able to find it no problem based on the exact wording of the OP. Bye
Gotta love the non-toxic spirit of these forums. Heartwarming.
@OP thanks a lot. Tried this on the OP7T Pro and it actuallz worked. Do I have to keep the app installed though?
Edit: interestingly enough, this wiped my entire keyboard config (florisboard).