Database Develop

VoIP and sleep during calls -> no call possible

Hi folks,
thought i write down my problem since i've been trying for quite a few months now to get rid of this problem:
First of all i need to tell that i am using dutty's v4 rom. I did not have the problem at all with some other roms, but i'd like to keep on using Dutty v4 since it is very fast, non-laggy with manila3D, and rock-stable.
So here is the deal:
After setting up my VoIP account, tweaking WLAN to keep attached to the AccessPoint even when the Diamond goes into sleep - I managed to make a VoIP test call to my provider via WLAN.
Everything works just fine - until the device falls into sleep after a couple of seconds.
Annoying thing is that it perfectly works with normal GSM calls even when it goes to sleep, but not with VoIP calls.
Not that i needed the display to work during the call - but audio as well as recorded audio - which gets lost as soon as the Diamond falls into sleep. I have to reactivate the display to hear/speak with the other person. So after i've done that it takes a random time until it falls asleep again. This takes about 2-10 seconds.
I've tried everything - DiamondTweak, Advanced Config, nosleep!!.cab, registry tweaks - nothing works. After i had that problem the first time with Dutty's rom v3.4, i also wrote him while ago. He fixed this issue in v3.7. Somebody got an idea what he did?
Now that v4 is out, the problem sometimes persists. It worked fine just after flashing the rom, then it suddenly stopped working after 3 Weeks. Now i made a hard reset, first thing afterwards i did: install all the voip stuff needed and it didn't work from the beginning.
It seems to be a problem affecting certain types of roms and their configuration, but i couldn't find out by now what's the exact matter. Even if the screen would turn off, but audio keeps on just to talk to each other (if i remember right, the Diamond is a phone too? this would be awesome!
After spending days with searching for it, the ultimate solution hasn't been posted on this forum so far. So if someone knows what to do about this, even if it means to recook a rom - please tell me!
Please read what i already tried before giving answers, and thanks in advance for any real help!

Slow to start dialing

Does anybody know why my hero might be a bit slow at dialing? When I touch a number in my contacts, it takes up to 30 seconds before it starts connecting the call. Sometimes its instant, sometimes its a long time. If I press it twice, it'll try to three way call the person later.
What causes this, and how do I fix it?

I have this problem too as does my hubby's phone.
We have tried damagecontrol and fresh roms and it happens on both of them.
We also get issues with the internet and gps not working on and off so we have to reboot. Not sure at all if this is any way related to the phone calls being so slow to take.
would LOVE an answer to how to fix this!

a dialer without haptic feedback usually solves this, here's one for damage/fresh/sprint based roms. Other wise, try zen's slide rom, dialer works GREAT, fastest yet for me even with haptic on!

gapoochi said:
We also get issues with the internet and gps not working on and off so we have to reboot. Not sure at all if this is any way related to the phone calls being so slow to take.
Click to expand...
Click to collapse
I get the same problem as well. Usually its fixed by turning wifi on then off, or turning gps off then on respectively.
danaff37 said:
a dialer without haptic feedback usually solves this, here's one for damage/fresh/sprint based roms. Other wise, try zen's slide rom, dialer works GREAT, fastest yet for me even with haptic on!
Click to expand...
Click to collapse
I get this problem without even using the dialer though. E.g. going into people, touching a contact, then touching the phone number to call it. The phone just does nothing for a little bit then suddenly it initiates the call. Would changing the dialer still fix this problem?

not entirely sure... possibly, I think it still has to load the dialer app when you do that. Best I could say is just try it. If it doesn't, and you want the old dialer, just pull it from the original zip you flashed and adb push to system/app to replace the one I posted. But that dialer works much better, in my opinion

Mine does this too and has on the stock ROM as well as every version of damagecontrol since 2.06. Sometimes it will dial right away and other times it will wait 10-20 seconds, then turn the screen off and immdiately back on and then dial and other times it just waits however long it wants to start dialing.
I know when I was still on stock and not rooted it would sometimes go into a state where it wouldn't respond to any commands that would make it dial but every other function seemed to be fine. I don't believe that's happened since I rooted and ROM'd it though.
I've used the stock dialer and well as SuperDial and Dialer One and all have had the problem. I've had this problem with haptic turned off/removed and still on. Sometimes waiting a few seconds after unlocking will help but not always.

So far for me, 100% fix has been the slide rom or darch droid (which finally booted for me today!). Both those, not one issue.
-------------------------------------
Sent via the XDA Tapatalk App

[Q] at times lost the signal

Hello!
Congratulations for the job!
I have installed the last xdandroid on my Touch Diamond2.
Everything perfect, but when the mobile is going in sleep mode, the green LED lights up, when it stays in this state I can not receive calls until restart it, although when I call my number, tone is heard ..
Any ideas?
Thanks

iupu said:
Hello!
Congratulations for the job!
I have installed the last xdandroid on my Touch Diamond2.
Everything perfect, but when the mobile is going in sleep mode, the green LED lights up, when it stays in this state I can not receive calls until restart it, although when I call my number, tone is heard ..
Any ideas?
Thanks
Click to expand...
Click to collapse
Thats a known problem on most xdandroid devices.

Problem without a solution, wow ...
Very good job anyway! And go!

iupu said:
Problem without a solution, wow ...
Very good job anyway! And go!
Click to expand...
Click to collapse
I am sorry but the problem is in the kernel and there is nothing that can be done right now only by fixing the kernel.

no problem, xdandroid is a great work, thanks for the answer.

Hi,
I am real wondering that people ask for ROMS when this bug is still there.
I can live without sound, Flash, maybe WIFI but to receive calls is a basic.
-Are there people do not have this problem
- Is this depending if you have Monodie or not?
- Is there something I can help with debuging? It looks for me the whole call service is geting struggeling when green LED comes.
Please understand,
The developement is so incredible to change from a crap WM6.5 phone to Froyo the MUST HAVE feeling is so strong.
That's why
Cheers and thanks
Dirk

ReWind402 said:
I am sorry but the problem is in the kernel and there is nothing that can be done right now only by fixing the kernel.
Click to expand...
Click to collapse
I'm reading that too, but on the other hand many people are stating they're using XDAndroid for days without the call sleep bug. And they have the same kernel as me, so that makes you wonder...

Has anyone tried this possible workaround?

Lost Signal Workarround
Hi, I tried,
If Startup.txt is with ...pm_sleep_mode=3 then it works but lot of draining
if standart startup.txt have sleep problem
Greets
Dirk

I'm using pm_sleep_mode=2 which seems to be a good trade off between battery and the sleep problem. Sometimes after the phone has been going awhile outgoing calls don't work but incoming ones do. That can be fixed by going into airplane mode and back out again.

I tried all values 0 to 4 for pm_sleep_mode, but no luck. I even made sure I had a new data.img created every time for every value. Nothing. First incoming call immediately goes wrong.

Incoming call screen disappears - can't answer call!

Hi all,
Friend and I both have the Incredible S, loving it! He has a slight issue and I can't for the life of me solve it. Everything was working fine but now when he has an incoming call and the screen is off the incoming call screen flashes up briefly then disappears and device shows normal 'desktop' - you can't answer the call!
If you call his phone and the screen is active, incoming call screen pops up as expected and you can answer call.
Any ideas peeps?
Thanks
Ant

Hmmm,
I'm having the exact same problem. Running Fresh Evo on HTC Evo. Would love to know why this is happening. Any ideas?

Sliphorn said:
Hmmm,
I'm having the exact same problem. Running Fresh Evo on HTC Evo. Would love to know why this is happening. Any ideas?
Click to expand...
Click to collapse
Never worked it out, friend did factory reset in the end to fix it.
Ant

Bummer. Here's some info:
Latest Fresh EVO
Rom Manager
Rom Manager Janitor
Juice Defender Ultimate Juice
Titanium Backup Pro
Cachemate for Root
ShootMe
Adfree Android
adbwireless
Call Control (problem before this, though)
Launcher Pro
Any hints?

Having the same exact issue. This sucks... This started today for me around noon ( no calls before then), and has persisted throughout the day. Yesterday was fine.
I use Google voice for all of my calls.
The only thing I've done today that I haven't done every other day was that I installed the Gtalk app this morning. In the past, I've used Gmail directly. However, my computer was off during at least one of the phone calls I received today, so I can't imagine this could be it...
Perhaps because I installed gAlwaysIdle (an addition to Gtalk that makes you never go idle or always be idle) as well?
Does this correspond with anyone else's experience?
I'll probably just reflash my phone
<Rooted Atrix 4g running GingerBlur>

hmm this sounds like a serious firmware problem tho..
all i could suggest is flash a firmware that the most of the ppl are using, and dont got probs with...

well doing a good reboot seems to help alot these days. So disable the fastboot option en turn it off, wait a while (10 secs should be enough) en start the device again.
Also had some of the trouble like crashing things and this solved it for me. Give it a try and hope it will fix it.
Otherwise there seems to be no other way than a factory reset (go htc!)

CM10 Bug Thread

As poeple keep aksing the same questions over and over again in the official CM10 thread I tought it might be a good idea to have a dedicated bug thread. I will try to maintain the first post as good as possible. It should give you an overview of bugs and workarounds.
Following are known bugs with workarounds:
Slow charging bug
Restart phone with cable pluged
Battery drain on wifi
In advanced settings of WLAN don't choose the option to keep activated always the wifi
Apollo chrashes
Clear cache and data of appollo app in "manage apps" menu
Noise during Call, muted mic
Use a CM Rom for the new bootloader
Following are known bugs withouth workarounds:
Voice/Video call in Gtalk doesn't work (FC)
Panoramic photo mode chrashes somtimes
only continuous autofocus in videocam
notification bar isnt able to be tranparent, even with themes
no CRT on/off animation
non selectable pieces in enrgy-switch-widget
Bluetooth is loosing connection
Camera flash does not work without tapping-to-focus before hitting the shutter
No face unlock
HDMI output is rotated by 90 degree
Fixed Bugs
Screen turning randomly turning on (CM 1105)
Headset button works. This concerns those who use a proper Android headset that has a button for answering calls and pausing music. (CM 1105)
Other things to know
No LED Notification. This is actually not a bug. It is a feature which is not implemented yet.

Voice/Video call in Gtalk doesn't work (Gtalk gets FC'ed).
There is already a post maintained in another thread (can't tell which one) with an exhaustive list of known bugs, but I've only got these (as far as I know), gtalk and no audio in call.

screen randomly turning on. happens much more with wifi on, like constantly, but now i changed to 1105 nightly, so ill see if this is gone or not.

every time after rebooting phone resets «vibration + sound»... after reboot: only sound (no*vibration)

kukharski said:
every time after rebooting phone resets «vibration + sound»... after reboot: only sound (no*vibration)
Click to expand...
Click to collapse
Can't confirm this bug. I still have vibration after reboot.

After 1day of use (and a full charge), microphone didn't work need to reboot
(1104)
(NOT solve in 1106)
The Parnoramic photo mod can't save picture
(1104 + CWM 6.0.12)
Datetime zone (solve in 1106)

aze2 said:
After 1day of use (and a full charge), microphone didn't work need to reboot
(1104)
The Parnoramic photo mod can't save picture (sdcard problem?)
(1104 + CWM 6.0.12)
Click to expand...
Click to collapse
I don't think it's a sdcard problem as I do not have any issues with the sdcard. Sometimes I am able to shoot Panorama fotos. Somtimes I am not.

charged all night. woke @ 75%. bad =/

1. only continuous autofocus in videocam
2. notification bar isnt able to be tranparent, even with themes
3. no CRT on/off animation!
4. non selectable pieces in enrgy-switch-widget

R0B3RTF1SH3R said:
charged all night. woke @ 75%. bad =/
Click to expand...
Click to collapse
What did you have on?
If you left it with wifi on it kinda makes sense it charged really slowly... if you believe that wifi is that enormous battery drainer everyone says it is (since I flashed v30a BB I have a battery life very similar to what I had with CM7, which was pretty good).

Flash light in photo camera is not working for me even when set to flash on.
With other camera apps it works. Can someone confirm?

My phone having randomly BSOD's.
Phone won't wake after sleep, have to take out battery. I have noticed some others have reported this in CM10 thread..

Bluetooth often does not connect to my car handsfree right away and often I have to turn BT off then on again on the phone to connect.
Bluetooth calling often gets cut off mid-call or briefly interrupted by waterfall noises.
Camera flash does not work without tapping-to-focus before hitting the shutter. Also the viewfinder lags a lot.
Whenever a new nightly is flashed on, it tends to disrupt the Bluetooth settings and force me to manually delete and repair.
The touch buttons don't light up during a notification when the screen is off (they used to in CM7).

Caller id, hidden number not functionnal in phone parameters / additionnals settings
Sent from my LG-P990 using xda app-developers app

Would help a lot if all of us shared the ROM version because some bugs are ROM related.
With 1107:
No face unlock
No full size panorama
Only continuous autofocus in videocam
Camera flash does not work without tapping-to-focus before hitting the shutter
Other bugs are not important to me so far.

Camera flash works for me,you need to turn that in options,works in cm and 4.2 camera

xilw3r said:
screen randomly turning on. happens much more with wifi on, like constantly, but now i changed to 1105 nightly, so ill see if this is gone or not.
Click to expand...
Click to collapse
got the same problem. Really annoying.
Only solution i found is this: http://forum.xda-developers.com/showthread.php?t=1674661
But i really don't want to do it, upgrading to the newest nightly and checking if the problem persists.
Edit: Updated it per CM-Updater (the one in "About the phone") and it's working great now, no random lightening up)

McKevin78 said:
Flash light in photo camera is not working for me even when set to flash on.
With other camera apps it works. Can someone confirm?
Click to expand...
Click to collapse
yes , same problem .. but after install Ucam pro flash is OK , and Ucam is much better :good: Try Ucam

help i cant restore a nandroid backup of cm10
it says error while restoring /system
any help??
Sent from my Optimus 2X using xda premium

With more than 10 installed Apps, that will open slow, need around 3 sec
RAM has space enough (80-100MB)
The Apps are working fine.
Otherwise no problems, Stop, the Akku Drain under WIFI:crying: