Hi from NZ
I find that I reject calls a lot as I pull my phone out of my pocket. I believe it is because I hit the back soft key, which is a CyanogenMod thing? See this thread: http://forum.cyanogenmod.com/topic/22382-disable-back-button-rejects-incoming-call/
Can anyone advise a way to disable this "feature"? The CM forum has nothing, and Googling around has failed to help..
I'm running CM7 111107 (http://forum.xda-developers.com/showthread.php?t=1068766) with the current franco kernel.
Appreciate any suggestions or workarounds.
I have the same issue, would be nice to disable it.
Sent from my u8800 using XDA App
<bump>
Can anyone help?
Why is there no participation in this? Surely an issue that causes hangups, isn't a problem on the stock ROM, and will affect more people as more devices move to soft keys, deserves some sort of response?
Sent from my u8800 using XDA App
I think it is here
overlay/packages/apps/Phone/res/values/config.xml
at...
<!-- This is a device with capacitive buttons, so disable the feature
where BACK rejects the current incoming call. (Since it's so
easy to press the key accidentally as you pull the phone out of
your pocket.) -->
<bool name="allow_back_key_to_reject_incoming_call">false</bool>
Click to expand...
Click to collapse
EDIT:
Here is the link for brave genokolar's port of CM7 to our phone!
btw, you shouldn't bump your threads... imagine if everyone did it!
thanks @priestx much appreciated.
I can make some noise about apologies, excuses etc but I won't
I've PM'd genokolar about this, I have no idea how to fork a code tree and compile this up
I believe this "fix" should be in the 111128 CM7 build genokolar released yesterday.
Problem is, I'm running franco.kernel, which has a compatibility problem for geno's latest build. Am hoping that compatibility is returned when franco kernel is updated later this week.
hmm I updated, and the back button still rejects the call..
["Somebody's" CM10 & "That" rom] Bug/fix reports & newest info (26-Oct-2012)
Firstly, I would like to give a big Thanks to "somebody" as well as the dev team at the behind of these roms for their efforts to bring ISC & JB as great things to our device.
Recently, I've tried both the ICSROM (known as the tune of leaked Rom under CWM flashable zip - Let's click Thanks for Upndwn4par) and "somebody's" CM10 (let's click Thanks for ticiano_arraes) and saw that they both have identical issues as reported by people such as the battery life, the deep sleep, the camera flash... including working fixes. But the fixes spread over the pages of threads caused inconveniences for us to track or update info. So I would like to open new thread just for purpose of collecting bug reports and the fixes from and for both users and our devs to get latest info on these roms quickly.
Admins please feel free to delete if this thread is already opened or if it's just not neccessary.
Belows are lists of great things of ICS/JB given by these roms that you can taste right now, and also the list of bugs/issues along with the best possible solutions that you can try for workaraound while waiting for the perfect release. The lists will be updated upon report from you guys. So please provide any thing from your experiences on these roms.
* Great things:
** For both roms:
+ Touch sensitivity is a big improvement in speed and accuracy (this might be inherited from Butter Project)
+ HDMI mirror works fine.
+ Others (pls share your experiences...)
** Individually for each rom:
ICSROM:
+ Webtop 3.0: work like a charm!
+ New Camera/Camcoder by Motorola with various valued upgrades such as Auto continuous (live) focus mode even for camcoder, full HD capture...
+ FingerPrint scanner @first steps of working (worked but not yet supported by original ICS/JB).
+ New valued apps added, such as Smart Actions (similar to Tasker, Locale but more intuitive/friendly/efficient), MotoPrint (valued add not only for business man but even for home usage), Battery Tracer (for battery monitoring with rich info)...
"Sombody" CM10::
+ All great things from CM10 as you experienced with such as Epinter's rom...
+ Camera/camcoder: worked.
+ 2D hardware accelerator: worked.
+ Data/GPS/Wifi/Bluetooth...: worked fine.
* Bugs/issues and workarounds (Newest update info are sized in big text, this helps you guys to track info more quickly):
1. Camera flash doesn't work properly: (Fixing is in progress...)
- Temporary solution: Turn on the torch while capturing in dark (shouldn't keep the flash on continuously over 5 min for safety of the LED flash light)
2. Deep sleep problem (which causes your phone cannot wake up upon power key pressing): CM10 23-Oct build FIXED. But some users reported that the bug is still there on their Atrix. So, the best way is that you flash and experience yourself to check whether the fix works on your device
If this problem still persists on your Atrix, try one of solutions belows:
- Solution 1 (confirmed): Remove the external SD card.
- Solution 2 (Edited: seems not worked): Turn off any screen unlocker (Choose None in Screen Unlock Options)
- Solution 3 (needs more confirmation): Just reboot your phone once or serveral times after rom installation
- Solution 4 (provided by Pont91-unconfirmed):
+put all media files on internal SD;
+deleted all files created by any app on the external SD;
+set internal storage as main one for all the apps data (downloads, photo, rec, backups, etc.).
- Solution 5 (worked with many users): Set Never for Screen Timeout in Settings/Display, remember to press Power button to turn off the screen instead
3. Randomly reboot issue: (the phone suddenly reboots for unknown reason):
- Solution 1: (need more confirmations): Remove the SD card.
- Solution 2 ("Somebody's" CM10) : (need more confirmations): Turn off Wifi :cyclops: There are two guys who provided that:
+ Either turning off Wifi
+ Or set Wifi to NEVER SLEEP (Always on) by: Settings/Wireless & Networks/Wifi Settings/Advanced/Wifi sleep policy
can help stopping reboots. Not only for this problem, but even the issues of heat and deep sleep can also be improved. From their reports, it seems that there is some problem related to the Wifi driver with "those libs". So, try this solution at your own case and help our devs by confirming this way again. Tks.
4. The heat issue (the phone seems to keep hot all the time): The issue seems to walk along with the deep sleep problem, so the issue may be cleared when the fix for deep sleep is applied.
5. The battery life: So bad
Both ICSROM (known as the leaked ICS) and CM10 with "those libs" have an identical problem of battery life. As shown on my phone, the battery drains from 100% downto 50% just after a couple of hours in usual use, even if your phone is in idle state.
No fix yet for this issue But you can apply some of following improvements:
- Lock (freeze) unnecessary AT&T apps and services (ICSROM only)
- Turn off Auto Syn (Manually mode instead)
- Turn off or lock all tracking/reporting sevices you doubt
- Use static wallpaper instead of live one
6. Ram low or several other suggestions only for ICSROM: clike here
7. The I/O performance is a characteristic weakness of both roms which are using "those" libs. You can see this on the results report of Quadrant. Essentially, you can see that the data processing speed is significantly slower than the CM7.2 by using, for e.g, Call Log Backup & Restore, etc...
No yet improvement for this disadvantage of both roms
8. Blackscreen issue after a lock/unlock: CM10 23-Oct build FIXED. But some users reported that the bug is now still there on their Atrix. So, the best way is that you flash and experience yourself to check whether the fix works on your device
9. Black incoming call screen and blackscreen issue after a call: CM10 23-Oct build FIXED. But some users reported that the bug is now still there on their Atrix. So, the best way is that you flash and experience yourself to check whether the fix works on your device
...Other issues (please share and provide your own solution...)
Thanks for continuous reports from you guys!
(To be updated...)
flusshd said:
Firstly, I would like to give a big thanks to "somebody" as well as the dev team at the behind these this rom for the efforts to bring ISC & JB as great things to our device.
Recent days I've tried both the leaked Rom and "somebody's" CM10 and saw that they have the same identical issues as reported such as the battery life, the deep sleep, the camera flash... and some working fixes. But the fixes are spread over the pages of threads that cause inconveniences for us to track or update. So I would like to open new thread for collecting the bug reports and the fixes from and for people to provide quick update info on these roms.
Admins please feel free to delete if this thread is already opend or is not neccessary.
Belows are lists of great things and also the bug reports along with the possible or even just temporary fixes that you may should try to resolve. The lists will be updated upon report from you guys. Please provide any thing from your ecperiences on these roms.
* Great things:
+ Camera/camcoder worked.
+ 2D hardware accelerator worked.
+ Data/GPS/Wifi/Bluetooth... worked.
+ FingerPrint scanner @first steps of working.
+ Touch sensitivity is excellent (this might be inherited from Butter Project)
+ Others (pls share your experiences...)
* Bugs and most likely fixes:
1. Cammera flash doesn't work properly: No any fix yet.
2. Deep sleep problem (which causes your phone cannot wake up upon power key pressing):
- Solution 1 (confirmed): Remove the external SD card.
- Solution 2 (unconfirmed): Turn off any screen unlocker (Choose None in Screen Unlock Options)
3. Reboots issue: No solution yet.
4. The heat issue (the phone seems to keep hot all the time): The issue seems to walk along with the deep sleep problem, so the issue may be clear when the fix for deep sleep is applied.
5. Other issues (please share and provide your own solution...)
Thanks in advance for continuous reports from you guys!
Click to expand...
Click to collapse
Thanks For your report!
My phone is an US AT&T. Installed ICSROM yesterday (WOW!!!) and confirm what you posted.
Biggest bug is the battery. It seems to consume 1% every minute! In an hour I was down to 40% after full charge and using Play Store on wifi. Webtop/Mirror mode works awesome! Watched some HD videos and listened to some music... all good. After using the HDMI connection, I confirm that you will not get black screen until you reboot the phone. Turning off any screen unlocker does not fix the deep sleep bug. 1 reboot. Overall, it is very good.
Keep up the great work and thank you for your efforts! :highfive:
flusshd said:
* Bugs and most likely fixes:
1. Cammera flash doesn't work properly: No any fix yet.
Click to expand...
Click to collapse
I think I saw some workaround suggested by somebody to turn on the torch before using the camera. This way, you've a constant camera flash
Not sure whether it works as advertised, I've not used this ROM yet.
gkarthik16 said:
I think I saw some workaround suggested by somebody to turn on the torch before using the camera. This way, you've a constant camera flash
Not sure whether it works as advertised, I've not used this ROM yet.
Click to expand...
Click to collapse
Thanks for the suggestion !
gkarthik16 said:
I think I saw some workaround suggested by somebody to turn on the torch before using the camera. This way, you've a constant camera flash
Not sure whether it works as advertised, I've not used this ROM yet.
Click to expand...
Click to collapse
It works
Anyway, it seems i've stopped deep sleep reboot, with external SD inserted, in this way:
-put all media files on internal SD;
-deleted all files created by any app on the external SD;
-set internal storage as main one for all the apps data (downloads, photo, rec, backups, etc.).
Hope this can help you in some way
Sent from my beloved Atrix
Android03 said:
Turning off any screen unlocker does not fix the deep sleep bug. 1 reboot. Overall, it is very good.
Click to expand...
Click to collapse
Really this fixes the deep sleep bug? Have you made tests for a long time of usual use? Pls confirm.
Can anyone else confirm this fix again?
First of all, thanks for the report.
Regarding the FP reader - what's really working and what isn't? Could someone enlighten me there?
As I'm back to cm7 right now, I would like that if you find any bug/fix, PM me. I will put it on the OP in the dev section.
Oh, btw, the flash workaround was my idea
I heard removing the SD card fixes the reboots.
Sounds like this might be similar to what pont 91 talking about.
Is there any fix for the upside down front camera in "somebody's" cm10?
Sent from my MB860 using xda app-developers app
Not sure if this is a bug with the roms (Somebody's 10/19), but I'm not longer able to track total data usage on my phone. Some apps will show the amount used by individual apps, but none will actually total it up (They all say 0 total data usage).
Woah where you getting October 22 from???
Fixed
flusshd said:
Really this fixes the deep sleep bug? Have you made tests for a long time of usual use? Pls confirm.
Can anyone else confirm this fix again?
Click to expand...
Click to collapse
deep sleep fixed;
Fixed blackscreen issue after a lock/unlock
Fixed black incoming call screen and fixed blackscreen issue after a call
mediafire . com / ?p3cl9j16v828i6y
cm-10-20121023-UNOFFICIAL-olympus.zip
israelborges said:
deep sleep fixed;
Fixed blackscreen issue after a lock/unlock
Fixed black incoming call screen and fixed blackscreen issue after a call
mediafire . com / ?p3cl9j16v828i6y
cm-10-20121023-UNOFFICIAL-olympus.zip
Click to expand...
Click to collapse
So, no more random reboots?
quetzalcoatl2435 said:
So, no more random reboots?
Click to expand...
Click to collapse
Where is that link coming from?
Sent from my iPad using Tapatalk HD
Antieco said:
Where is that link coming from?
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
from here
http://forum.xda-developers.com/showthread.php?t=1934662
quetzalcoatl2435 said:
So, no more random reboots?
Click to expand...
Click to collapse
I'm trying it right now. I'll let you know
Antieco said:
Where is that link coming from?
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
israelborges pm'ed the link to me. He also pm'ed ticiano_arraes (and maybe more people), it seems.
quetzalcoatl2435 said:
israelborges pm'ed the link to me. He also pm'ed ticiano_arraes (and maybe more people), it seems.
Click to expand...
Click to collapse
Have you tried it? Can't stand black screen after call!!!
Sent from my iPad using Tapatalk HD
quetzalcoatl2435 said:
israelborges pm'ed the link to me. He also pm'ed ticiano_arraes (and maybe more people), it seems.
Click to expand...
Click to collapse
Yes, but it's not the first time he did this
Hello All,
I installed the latest CM12 build for Xperia X2, its been running good, apart from a couple of issues.
1. I use SBH20 bluetooth for audio and calls, and the connection to it keeps dropping. I've to reconnect it again n again.
2. The In-Call speaker mode is not functioning.
Hope someone can provide me with solutions.
No known solutions till Cyanogenmod Team fixes it.
Envious_Data said:
No known solutions till Cyanogenmod Team fixes it.
Click to expand...
Click to collapse
Ok . But the issues have been persistent, from the very first nightly. Wonder when they would fix them.
Thanks anyways
saggiboy231 said:
Ok . But the issues have been persistent, from the very first nightly. Wonder when they would fix them.
Thanks anyways
Click to expand...
Click to collapse
When its reached the bottom of the list
They are more focused on fixing more important things.
Hi guys, I've registered on XDA Dev just to write this thread, I want to share with the community this one little thing I found out on my own, compared to what our great developers do for us everyday.
Why am I writing this even though some people solved this issue following the already existing threads and guides? Because every solution I found on the web didn't work for me. I hope this is going to work on your devices as well
Let's start!
Basically I've just installed a custom kernel (in my case I used the @ak kernel) and set the Hysteresis Value to 6 instead of 8, and glitches are way more short and rare. This worked out on my Validus Rom running AK.
I wanted to try these settings because every solution I found was too battery unfriendly, and my screenshot proves that you don't need 2 cores running on a turned off screen. Let me know if it worked for you!
Hi. I come from a6020 forum. I write here because I've discovered we have a very common bug on ROMs with kernels that support dt2w/sweep2wake features.
The issue is as the title says: touchscreen won't respond after waking up from deep sleep, while having dt2w/sweep2wake features enabled.
Only the volume +/- and pwr buttons will work.
I just have to reboot the phone and the touchscreen will work again, but after a while the issue comes back.
The only way to get the phone working normal, is disabling those features from Kernel Adiutor.
I'm part of a telegram tester group for my device, but developers there can't find where the issue is.
my question here is:
Do you have a fix/workaround, other than just disabling? Or at least do you know why dt2w causes the touchscreen to bad working, specifically?
Surely, you know what I'm talking about, cause I've seen reports for this bug on some a6000 threads.
If you could response me, @dev_harsh1998, @ED300, @rohitsinha12, or @IvanHephaestus, I'll be grateful, for sure. thanks in advance.
I have same problem please help
walterfuster said:
Hi. I come from a6020 forum. I write here because I've discovered we have a very common bug on ROMs with kernels that support dt2w/sweep2wake features.
The issue is as the title says: touchscreen won't respond after waking up from deep sleep, while having dt2w/sweep2wake features enabled.
Only the volume +/- and pwr buttons will work.
I just have to reboot the phone and the touchscreen will work again, but after a while the issue comes back.
The only way to get the phone working normal, is disabling those features from Kernel Adiutor.
I'm part of a telegram tester group for my device, but developers there can't find where the issue is.
my question here is:
Do you have a fix/workaround, other than just disabling? Or at least do you know why dt2w causes the touchscreen to bad working, specifically?
Surely, you know what I'm talking about, cause I've seen reports for this bug on some a6000 threads.
If you could response me, @dev_harsh1998, @ED300, @rohitsinha12, or @IvanHephaestus, I'll be grateful, for sure. thanks in advance.
Click to expand...
Click to collapse
This is seen to happen on the devices with non original vendor panel or on those panel which fail to pass the firmware check btw if that happens upload the kernel logs i will write an patch to fix the issue prolly we need a condition resched somewhere. I haven't much bothered upon fixing it on our device because its seen happening only for people with damaged or non original panels
dev_harsh1998 said:
This is seen to happen on the devices with non original vendor panel or on those panel which fail to pass the firmware check btw if that happens upload the kernel logs i will write an patch to fix the issue prolly we need a condition resched somewhere. I haven't much bothered upon fixing it on our device because its seen happening only for people with damaged or non original panels
Click to expand...
Click to collapse
Here you are, bro. A lot of thanks: