Hello,
There have been numerous attempts to reason this issue with galaxy, but none succeeded so far (as far as I saw)...
The problem is, that with any Froyo ROM for i5800 the phone has these "stutters" or breaks during a call and sometimes also while playing music.
Possible causes identified by me (what could cause this):
- CPU usage too high (unlikely)
- RAM too low (also unlikely)
- Battery problem (that is my guess)
- Some problem with the proxim. sensor
I think so because when I called with loudspeaker enabled, there was almost never when stutter occured. But when I called the regular way, after screen went off, stuttering became almost permanent...
I post this issue to find an answer regarding this, so please STICK TO THE TOPIC
Thanks!
Sent from my GT-I5800 using XDA App
Yeah, this was present with any Froyo ROM (stock JPF, JPM - and also with Kyrillo, Indro, Apoc, and Lesta as well). I'm currently testing with Eclair stock.
No it's not because of CPU overclock, coz it was present even before OC kernels.
I've got XXJPF and no problems(except inside contacts BackButton is not responting).
jihaa said:
Hello,
There have been numerous attempts to reason this issue with galaxy, but none succeeded so far (as far as I saw)...
The problem is, that with any Froyo ROM for i5800 the phone has these "stutters" or breaks during a call and sometimes also while playing music.
Possible causes identified by me (what could cause this):
- CPU usage too high (unlikely)
- RAM too low (also unlikely)
- Battery problem (that is my guess)
- Some problem with the proxim. sensor
I think so because when I called with loudspeaker enabled, there was almost never when stutter occured. But when I called the regular way, after screen went off, stuttering became almost permanent...
I post this issue to find an answer regarding this, so please STICK TO THE TOPIC
Thanks!
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=1030629
Not the problem, thanks however. I've tried everything. I don't want to risk any damage to the phone (these cracks sound like eletric discharges, and they can be heared via the headset too, if there is no music or call). I think these ROMs (JPM, JPF and JPN) are somehow handling the battery wrong. This can be the reason why the phone dischareges quiclky during calls.
Solution: I found no signs of these error on Eclair ROMs, however. Therefore I reverted back to 2.1. My only problem now is the lack of Froyo features - I feel much more safe, however.
Also, I made a custom Eclair ROM in the process for SG3. I will be posting it on the forums sometime, I think for people, who have the same problem...
Related
Once in a while when trying to answer an incoming call the unlock slider won't respond. I will slide my thumb to unlock and ...nothing. When this happens the call will just go to voicemail . The workaround is to touch the power button to turn off screen , then touch it again to wake it up ,then the slider will work and I can answer the call. Sometimes this takes too long and I miss the call.
This is not a deal-breaker as it only happens 5% of the time , still it is annoying. I have tried different roms with no real difference. Anybody else have this problem? Any advice other than get a new phone under warranty?
Ditto. And I always act as you did to work around the issue, only difference is, I haven't missed a call due to this.
In any case, based on experience, the chance of this happening could be minimized (if not eliminated) by always locking the phone from the "desktop" (e.g. do not lock the phone when an app is running).
BACK STORY:
I remember this happening (more than once) when someone called me up after a train ride. And the last thing I could recall is that I have locked the phone while playing Angry Birds / Fruit Ninja / Zenonia 2, etc.
But it still sucks that it happens.
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
question... are the phones plugged in to a wall charger when this happens?
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
DKYang said:
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
Click to expand...
Click to collapse
can happen any time any place
ransome7 said:
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
Click to expand...
Click to collapse
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
cygnum said:
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
Click to expand...
Click to collapse
Mine did it stock , I rooted and loaded roms to see if that would fix the problem , lessened but still there
My nexus s (i9020T) has exactly the same problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally. I connect my phone with adb, and tried to "cat /dev/input/event0" The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I've also read the driver code of nexus s, htc incredible and moto droid x, all using the same controlling chip. Both HTC and moto would send calibrate command to the chip during resume, but sumsang does not. I guess this might be the reason, but I'm not skilled enough to port the drivers
I experienced it twice so far i think, but only have the device for a little more than 2 weeks.
I am on stock 2.3.1 currently.
Beside the lock&unlock method, I discovered a new way of getting screen back to work: rub your hands a couple of times and touch again... Anyway it seem the screen is not well calibrated.
problem seems fixed with my customized kernel
Last night, I modified the touchscreen driver and mach settings a bit on the source of netarchy's nice kernel, and compiled a kernel of my own. The screen now seems working well with my new kernel
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
swa2k4 said:
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
May I know how to perform the suggested steps, i have been experience twice since i bought it on 2 weeks ago
I would like to bring this issue up again (after so long) as I am still randomly experiencing this exact issue even with Ice Cream Sandwich 4.0.3 (Stock & Custom ROMs). Any fix yet?
hi guys ,i tried to search with the keyword "flicker" but there's no similar result returned, so i decided to start this thread.
I'm using I9000 Asia set, stock firmware is DXJPA. Currently on Darky Rom 9.4.
Before this i was on DXJPA + speedmod K13A, things was fine(i suppose). Right after i flash my kernal to K13C, i notice sometimes my screen flickers, i thought its just some magnetic interruption. But the longer i observe, it seems to appear once in a while.
So i thought its the kernal that causes it, i flash it back to stock kernal and did a reset, apparently the problem still around. And even now i'm on darky rom 9.4, i'm still having this issue. So guys, did any of you faced the same problem ? and any of you manage to find a solution to it?
Ya I'm having the same problem. I always thought it had something to do with automatic brightness.. Not sure though...
Sent from my GT-I9000 using XDA App
Same with mine
Sent from my GT-I9000 using Tapatalk
I have the same issue, but only on wifi - while turning it on or when the signal is weak.
It must be hardware though - my roommates SGS, bought on the same day, doesn't have this problem.
I have the same problem too.
you guys on stock or custom rom?
I'm on stock.
Come to think about it, I only had this problem when I'm browsing internet..
So it could be related to wifi as mentioned above.
Anyone have better ideas?
I'm not really concerned about it since it rarely happens, but if someone can tell us the fix... it would be awesome!
Clear your phone flash stock rom Eclair with pit 512 and repartition checked .
If that solves the problem you can upgrade to Froyo .
That way you eliminate fault from a custom rom .
jje
I'm pretty sure it's not sw related, but it's hw defect - at least in my case.
I have the problem from the start and on 5 different roms - all stock (JG1 - stock default, JP3 and JP5 - got at the Samsung service, JPO and JPY - via Kies).
Someone with the same problem went to the service with the phone, where they've replaced the screen and the problem was gone. So I can assume that the screen was faulty or some connectors or something similar.
I wasn't comfortable when I first noticed the flickering, but it's not a big problem for me now. Thankfully it's not getting worse, but if it's going to, I will certainly service the phone.
I also have this problem, mainly when browsing internet (on both stock and opera browser), but occasionally in other apps too.
I am running an older docrom with damien's ultimate kernel.
I figured it is a hardware issue, because it only started happening after my phone got dipped in sea water (lol).
lets try to gather some info among us so that we can narrow down the possibilities.
I shall start 1st. Below are my configurations
1) Always on Edge (for battery saving purpose)
2) On Darky Rom 9.4
3) Flicker mostly in browser, sometimes in other apps, and homescreen as well
I'm still sure it's a hardware problem, but still, if it's going to help anyone:
- also always on GSM mode only (have tried on 3G - no difference)
- stock JPY (the problem persists through 5 different stock ROMs)
- only get it when turning wifi on until it is connected or it keeps flickering when wifi reception is bad and it doesn't connect
- it can be best seen if I pull notification bar down and turn on wifi
Now that I think of it, i've only noticed it with wi-fi on, and it doesn't matter whether i have an app running or not. i've seen it on the home screen many times.
GB 2.3.3 xxjvk
Change your bootloader
I also had it when I was using Darky's v9.4 and v9.5.
I flashed a new bootloader and upgraded to v10 RC3 and its gone.
To solve it, you will probably have to flash 2.3.3 with new bootloaders and then back to v9.5 if you want to keep Darky's FroYo. v9.5 is stable
Oh found the thread here
http://forum.xda-developers.com/showthread.php?t=1011701
Flashing bootloader is 1 thing that will likely brick your phone if accidents happen.
Kids, please do not try this at home.
is it possible to change my bootloader without flashing my rom?
Yes, but that's even riskier. If you flash an entire rom and it's going to fail, it will most likely fail during the factoryfs part as opposed to the bootloader part if flashing alone
Sent from my GT-I9000 using XDA Premium App
Hi,
many people still claim there isn't such a problem but there IS:
After ending a call the screen stays off and can't be turned on again. Hardwarekeys don' t do anything.
Only option: Hold the phone in bright light or take battery out -.-
I tried the most popular roms here (NAND&SD)
In WinMo everything works fine.
So here i want to show that not only i but many others suffer by this issue.
Hopefully some real CHEFS/Devs realize this.
Making tons of senseless customisations and graphics tweaks isn't enough to be a real Dev...
Here are some of the threads concerning this issue so far:
http://forum.xda-developers.com/showthread.php?t=1061481
http://forum.xda-developers.com/showthread.php?t=965123&highlight=call+screen
http://forum.xda-developers.com/showthread.php?t=1097531&highlight=call+screen
http://forum.xda-developers.com/showthread.php?t=1097531&highlight=call+screen
http://forum.xda-developers.com/showthread.php?t=735906
http://forum.xda-developers.com/showthread.php?t=946012
http://forum.xda-developers.com/archive/index.php/t-946012.html
srmemnoch2 said:
gsm.proximity.enable=false
you can include this in your build.prop file, locate in /system and reboot.
this never turn off screnn during calls..
but i think only run in froyo
im desperate i want update to gingerbread but this code do not run on ginger.
ragards
Click to expand...
Click to collapse
this really helps! But now the screen stys on all the time, must be careful not to end the call by touching the screen XD... But it's better than having a blocked phone.
But still the issue itself isn't solved ...
You could try http://www.xda-developers.com/android/proximity-sensor-re-calibrator-for-desire-hd/ this?
yes tried this already before, thanks, but didn't work.
I know this problem sounds weird to those who don't have this issue but it's real (i'm not crazy XD) The hardware is also working correctly as on WinMo everythiong's fine
I'm been having this problem since my first rom. I actually thought it was just my phone. It drives me crazy, as I found that plugging it in gets the screen to return. Very annoying!
Sent from my HD2 using XDA App
A new problem has started for me and and a Google search has shown some other people have also mentioned in but no solutions have come up.
Since iv started using any Android 2. 3. 7 roms around 1once a day to once a couple of days answering a call causes phone app to freeze and the phone speaker makes a constant buzz sound that eventually stops. After the phone signal and 3g returns all is well but trying to make a call result in a full phone freeze wich needs a battery pull. Best thing I do now after this crash is reboot normally.
Also good thing is the call is not answered as far as the carrier is concerned so I can still follow up on the call with voicemail.
I'm considering I have to go back to an older nexushd2 Rom or some sense Rom wich usually has Android 2. 3. 5
Anyone know a way to fix it? Maybe flash an Android 2. 3. 6 apk or a modded libaudio ?
I had that happening to my old phone.... freezing, buzzing, battery pull.
It started happening after I overclocked the phone to 1.5ghz . And then just kept happening even when i stopped overclocking. The phone would be hot on the bottom. And sometimes wouldnt boot till it cooled off. All i can say is hopefully you have insurance bc if its anything like with mine it'll be happening more and more often with time. After 3 months of it, it was happening a couple times a day , till i got a replacement.
Visentinel said:
A new problem has started for me and and a Google search has shown some other people have also mentioned in but no solutions have come up.
Since iv started using any Android 2. 3. 7 roms around 1once a day to once a couple of days answering a call causes phone app to freeze and the phone speaker makes a constant buzz sound that eventually stops. After the phone signal and 3g returns all is well but trying to make a call result in a full phone freeze wich needs a battery pull. Best thing I do now after this crash is reboot normally.
Also good thing is the call is not answered as far as the carrier is concerned so I can still follow up on the call with voicemail.
I'm considering I have to go back to an older nexushd2 Rom or some sense Rom wich usually has Android 2. 3. 5
Anyone know a way to fix it? Maybe flash an Android 2. 3. 6 apk or a modded libaudio ?
Click to expand...
Click to collapse
This is related to the No Sound bug alright. What other apps do you have - SIP/ Viber/ any other VoIP? And do you use BT? There were a few post in the No Sound thread and Tytung's kernel thread few days back about what libaudio.so works fine for what kind of a usage.
Android 2.3.7 is just a coincidence, me thinks
ph03n!x said:
This is related to the No Sound bug alright. What other apps do you have - SIP/ Viber/ any other VoIP? And do you use BT? There were a few post in the No Sound thread and Tytung's kernel thread few days back about what libaudio.so works fine for what kind of a usage.
Android 2.3.7 is just a coincidence, me thinks
Click to expand...
Click to collapse
None of the above and I don't use Bluetooth.
Guess it ain't a coincidence. I wouldn't of posted if I thought it was part of the no sound bug.
Sent from my Nexus One using Tapatalk
I had a similar issue some time ago: for me the problem was the cpu/governor settings and i fix it with an appropriate SetCPU profile. Using another rom though.
Try to set an "in call" profile as the phone won'to go under 400 Mhz (roughly) and see if it happen again.
mi too
i using miu rom, HD2 NDT GINGER and recovery 3.0.2.4 with this i don have this problem. with any sense rom I have that problem
Sorry my bad english
I'm having problems when using earphones from the first day I bought my Omnia7. The problem is:
Earphones are fully functional, and there are no problems with listening music etc. But, after I make FIRST phone call using earphones or after I answer the FIRST phone call, my phone becomes unresponsive within short period of time, and I don't hear other people during calls nor they hear me. So the first call triggers all this. That first call however goes through without any problems, problems come after that. I tried using several earphones with same results. After I reboot everything works fine again.
I'm pretty much sure it isn't hardware related problem since I listen to music without any problem and the first call works great every time.
I'm running the latest version of OS and I got these new drivers from Samsung few days ago, but still no improvement. Anyone here with similar problems and if so, did you manage to solve it and how?
...
Almost 300 views so far, but none reply... It can't be I'm the only one with this kind of problem?!
I have same problem! Please help
When did you guys get your phone. Where are you now, have you flashed your phone or messed with any functions with in the Diagnosis App at all.
Omnia 7 has original Rom with mango update, no modding or special things.
Finally, some activity in this thread!
I had this problem, with stock Rom and also with several custom roms, so it must be hardware related. On the other hand, it shows some signs of software related issues, so I'm still confused...
hatuna said:
Finally, some activity in this thread!
I had this problem, with stock Rom and also with several custom roms, so it must be hardware related. On the other hand, it shows some signs of software related issues, so I'm still confused...
Click to expand...
Click to collapse
Samsung in a nutshell