Hi Guys,
I installed Darky's A few weeks ago and done a reinstall recently because I seem to be having a problem making calls and the screen lock.
When I make a call wether it be using the speaker or not the screen goes dark after about 20 seconds after the call is initiated then a few seconds later the screen lock kicks in and disconnects. I have reinstalled the rom and updated to the core 1.4 but no matter what I do it still does it.
Does anyone know of a fix for this? It seems to be just when making calls. In a call it's fine but making one it does it every time.
cheers
Well reflashed Darky's 9.5 set it all up, Set the screen timeout to 10 minutes which works for 10 minutes until I try make a call then it lasts about 10 seconds.
Installed v10 rc6 and the problem has gone
Related
Hello, I've recently set up ActiveSync for 15 minute intervals during peak time. I set "Vibrate" for New E-Mail Messages. Usually it vibrates for a few short bursts, but at least once per day the vibration motor freezes up and won't stop vibrating until I press the power button. The only other recent change to my settings was that I installed Bandswitch to keep connected to the Edge network and disconnect after 120 seconds. I don't know if this change is related to the vibration problem. Anybody have any suggestions?
if you have Magic Fingers installed, you might try uninstalling it
thanks for the advice, but I don't have Magic Fingers installed
hey. weird cause i used to have the same issue before, my phone whenever it received an email it would not stop vibrating until i removed the battery. lol weird i know. r u using the stock rom? ever since i changed rom's from stock i havent had that problem before.
try flashing ur rom to an upgraded att or htc rom, maybe it would solve ur issue as it did to me
best of luck
I have the exact same issue with incoming emails. For now I have turned off notification. Configuration is pretty generic.
This happened to me...
This happened to me once with the stock ROM. I have since upgraded to the leaked AT&T Tilt ROM and it hasn't happened since.
Any Hints?
MadMatt- Any hints about where to find the "leaked" ATT Tilt ROM ?
ATT Leaked ROM
benmorris said:
MadMatt- Any hints about where to find the "leaked" ATT Tilt ROM ?
Click to expand...
Click to collapse
Here you go...Hope this helps.
http://forum.xda-developers.com/showthread.php?t=341886
One more
I also have this problem, but its not with every e-mail. I receive between 10 and 20 e-mails a day and the continuous motor only happens about once every other day. I'm also on the stock ATT ROM. Anyone figure out what's going on with this?
emmit said:
I also have this problem, but its not with every e-mail. I receive between 10 and 20 e-mails a day and the continuous motor only happens about once every other day. I'm also on the stock ATT ROM. Anyone figure out what's going on with this?
Click to expand...
Click to collapse
I'm glad I'm not the only one.
this issue is a bummer
oh yeah this is becoming a real pita
Me too...
Using Blackberry connect on stock ROM on Tilt, new messages occassionally cause a constant vibration until I hit the power button.
Would love to know how to stop this,
ncdave
In my experience I have found that this is caused by the device being forced to do something, i.e. check email, recieve email, before the device is fully "awake". The solution for me was acheived through the use of kaiser tweak. This also means there's a registry mod. for it as well, unfortunately I left my Kaiser at home today. If ylou change the device wake up to something more acceptable such as 15 seconds or 30 seconds instead of the 1 second default you may find this fixes your problem as it has for me!
If you did that, wouldn't you stand the chance of missing most of your phone calls while the phone is sleeping?
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!
I got a little problem with my g1.
When my phone is in standby and i get an incoming call it lags like hell.
After a delay of about 5 sec. the screen wakes...
I experienced this problem a long time, but always thought it's a ROM problem. After i tried various ROMs, i realized i still have this bug.
i don't no exactly when this problem started, but I think it came with the first donut ROMs.
I also think that it's no spl problem since i got this delay with the stock spl and the danger spl.
Does anyone have the same problem or even know a fix?
Can confirm this. I have a delay of a few seconds between the first vibration, the ringtone and the screen turning on and displaying the incoming call screen.
Zappza said:
Can confirm this. I have a delay of a few seconds between the first vibration, the ringtone and the screen turning on and displaying the incoming call screen.
Click to expand...
Click to collapse
i have the same problem
I have 2 G1s and this happens to me occationaly. I only have a few apps on my phone but my wife has lots of icons and apps on hers. i notice i only get a delay once in a while but she has a delay all the time. last night i updated both a Eclair 2.1-V1.5 from CYM 4.2.13 so far 2.1 seems to be a little faster so we will see...
used to get this a lot
on CM. admittedly i had never done a full wipe from 4.1.99 onwards so it was getting pretty laggy by 4.2.12. i've noticed a huge improvement when running dwang 1.17 and even more so on super d 1.6.
this bug really sucks...i get it on every rom...sometimes i cant even answer the phone...
Does nobody know a soloution?
Flashed latest xROM Eclair by JAC. Under idle, the phone almost always rings after the caller hears the 1st "do do" and before the 2nd.
If the phone is being used, especially with heavy apps (e.g. browser), then it's another matter...
have a Captivate that I recently flashed Di11i's 7.1.1 to, before that I had flashed my first ROM which was Serendipity 6.2. Both times I have found that I don't get incoming calls. People calling me get 2-3 rings, and then a traditional "busy signal" sound. On my end, either the phone vibrates once but the screen doesnt change from whatever screen I'm on. Or, The screen goes black like its going to the incoming call screen, but the black screens only flashes and goes away, as does a force close message box that goes away quickly without me clicking it.
Everything else on my phone works as far as I can tell, I've been running my current ROM for about 5 days without issues other than this one. This same exact problem also happened when I flashed Serendipity 6.2 (which I only kept for like a day because of this problem)
Try flashing to stock then master clear. Try flashing new rom after that.
Sent from my SGH-I897 using XDA Premium App
What are you restoring after a flash
MIUI
Hello Guys,
a Friend bought a used i9000 on ebay for 130€ from a business man, which got a ne phone from his company and sold hin mobile on ebay and he asked me for a litte work around of his "new" phone.
Optically is the phone perfect BUT if I take a call on Android 2.3.6 display stays black (with backlight) and I can make the call. But I can't do anything more, hang up etc. If the opponent hangs up, I hear the hang up sound but display stays black and thephone wount do anything. So it's needet to pull battery, put it back and restart the phone. On doing a call, the phone has similar problems, it freezes.
After a couple of re-flashes with odin nothing changed.
So I tryed to switch to actual android OS. I flashed SlimBean 2.7. Every thing workes well. but even call-issues. If i receive a call, the phone woun't do anythin and it keeps ringing and "holds" the call for exactly 32 seconds. Now I can talk with the caller. But most callers don't wait 32 seconds to call to me If I do a call in JB I can talk from the first second on, but display freezes and I can't hang up. Thats the state for around 28 seconds and then phone will response normally and I can hang on and do everything I whant.
Even in Slim I tryed reflash a fiew times with no cahnge.
Has anyone an idea?
I think thats a hardware related problem. But in fact its possible to do a call, but only with that issues/delays. So I need a solution, that JB (SlimBean 2.7) don't "hold" the call/freezes for 32 seconds. I think because its every time 32 seconds, thats a fix value in JB. so I need something to cahnge the value from 32 secs to may be 0 oder maximum 5. But thats only guessed by me so I need help of a PRO here to solve that nerving issue.
I also tryed to install other dialers, but thats not a good solution, because the use for calling the stock rom dialer (phone.apk), damn
Please help me guys (sorry for my bad english )
UPDATE: I did read a litte in web and found, that the light sensor could cause issues in calling (start and end). So I downloaded a app whitch will show me he values of the light sensor. Ands its true, the sensor will show me whole time same values. I changed the sensor od the device of my friend and mine but that does not solve the problem. same issue.
In second Post I'll load a some Pictures of both devices up. My device shows around 30 lux and the one of my friend around 5.
UPDATE 2: After some more reading in web I found more guys with same call problem but no solution. May be it could help to disable GP2A Driver oder better only to overwrite the lightsensor value with a fix one.
UPDATE 3: OK I tested with 3 apps and the proximity sensor of the phone is broken ...now i need a solution to disable it or set a fix value in android so that the sensor is unused.
Any ideas?
UPDATE 4: I downloaded the "Hardware Disable" app from Play store and disabled GP2A.
It works for now, I just have to switch off the screen manually by pushing power button at a call and turn it on by pushing power again. But thats no problem for me anf my friend and much better as the call related freezes.
But I need at every startup to confirm to disable the sensor. So I'm looking for a permanent solution for this. Also because the device feels a little bit laggy now.
Pics
SOLUTION
So Guys I found a good working solution fpr proximity sensor delay, 32 second freeze by taking a call.
I wrote my Solution in SlimBean thread
http://forum.xda-developers.com/showpost.php?p=32809014&postcount=4406
Schould work on any ROM (GB, ICS and JB) because they all use the same Hardware .so (sensors.aries.so in this case)