Related
I'm still getting touch screen freezes with any of the Cyanogen Mod Froyo builds, Bangsters/HyperDroid, assumed to be associated with the g-sensor.
I re-formatted my SD-Card and re-installed and I'm still getting freezes.
This is the 1 thing that is stopping both from becoming a perfect build, as everything else is amazing.
Any suggestions? Does it have something to do with AXI/NOAXI/EVO kernels? Under-overvolting? Is it the kernel?
Ive had problems with screen freezes with almost every rom, but i got barely any on this one. http://forum.xda-developers.com/showthread.php?t=790374
It also is a very good looking rom.
scbrother said:
Ive had problems with screen freezes with almost every rom, but i got barely any on this one. http://forum.xda-developers.com/showthread.php?t=790374
It also is a very good looking rom.
Click to expand...
Click to collapse
Yeah, I've experienced similar results, though I dislike SENSE based builds and prefer a Cyanogen Mod. I know Sense builds are more stable in the sense that they don't have as many touch-screen freezes, but would like to find a solution for the other builds.
:-/
FriedSushi87 said:
I'm still getting touch screen freezes with any of the Cyanogen Mod Froyo builds, Bangsters/HyperDroid, assumed to be associated with the g-sensor.
I re-formatted my SD-Card and re-installed and I'm still getting freezes.
This is the 1 thing that is stopping both from becoming a perfect build, as everything else is amazing.
Any suggestions? Does it have something to do with AXI/NOAXI/EVO kernels? Under-overvolting? Is it the kernel?
Click to expand...
Click to collapse
I didnt get any touch freezes with this setup: http://leoandroid.com/viewtopic.php?f=212&t=168
Are the devs trying to fix this problem/Are they aware of it? I'm asking because I have not heard anything about this issue since months and the release notes list g-sensor as "working" (freezes are definitely related to or caused by g-sensor). The freezing problem still exists. I can even reproduce it perfectly when g-sensor is activated. Compass is shaky too.
I've tried a LOT of builds since September, mostly Mdeejays (love them ) the last few weeks. Could reproduce it with any build. Also tried many radio ROMs, many WinMo ROMs -> no change.
It's the kernel. Try one of the builds that use a current kernel (such as Hastarin's, rather than the old desire-based kernal on most of the stock builds). They still get the occasional, very short, freeze, but it is almost un-noticable. I'm using Darkstone's stock build (from here) with hastarin's 7.8 and it's fine with screen rotation left on.
The freezes are caused by saturating the i2c bus on the device. G-sensor is one of the things on that bus, but not the only one. The current kernels have increased the speed of the bus to help keep it clear, but it is now set to its maximum speed. I'm not sure if there where other fixes done as well.
I was using different versions of hastarins kernels. I don't get the freezes (only sometimes) when I hold the device in a normal way. But I get them EVERY time when the camera is facing down (for example when I look on the ground in streetview in Google maps with activated compass function, or when I play teeter). It's the same position you have to lay down the device for calibrating the g-sensor. The air bubbles will freeze almost every time in this position. All other orientations work very well.
I've made some videos where you can see the problem (sorry for the quality):
http://www.youtube.com/watch?v=-RlCuITimvM
http://www.youtube.com/watch?v=A8PWNIhwTqM
There is workaround which works: http://forum.xda-developers.com/showthread.php?t=803242... new hastarin and mdeejay kernels include this patch... and no, freezes aren't caused by saturating i2c bus but by occasionally not releasing i2c bus by g-sensor chip after reading its state...
Hi everyone,
I would like to hear what changes you noticed if you have made the transition from Liberated R12 to Liberated FroYo FR007.
I don't know anything about kernels, setcpu or stuffs like that — I'm just a regular fella who love coffee and just made a proper installation of FR007 2 days ago and reverted back to R12 today because:
1. I noticed that its' performance is a tad slower (I think).
2. eBuddy kept crashing, mostly after the phone goes to sleep.
3. Wi-fi network stopped after phone goes to sleep (but it was already noted in the thread to download FR007).
4. Responsiveness isn't quite as nimble (ie. swiping between homescreens, launching apps, connecting to networks, etc).
5. It hangs quite a bit
While it may have some drawbacks, there are also some nice things that came with the FR007 ROM, most noticeably:
1. Better UI interfaces
2. More options in some features/settings
3. Cooler OS name (what's cooler than Frozen Yogurt?)
I bet there are much more powerful stuff and greater potential in the FR series that most regular users like myself won't understand, and that this is just the precursor/preview to a stable version. However at the moment it's R12 vs FR007.
So at the moment I'm going to stick with R12 and patiently wait for future releases of the FR series.
What are your observations? Thanks for sharing!
Each to their own! I'm using FR007 on my Aria which was purchased in USA and the only problem I have is sometimes the Weather Widget sometimes hangs. That's all.
I, too, am running FR007, however my ebuddy hasnt crashed at all for me. I do notice a little bit of lag swiping homescreens but having a LWP on would affect that for sure.
i havent noticed a hang unless im tryin to multitask several apps around.
Those are pretty small issues for me for my previous phone was the Hero CDMA.. and this is like a million times better.
I agree with most of what you're saying. I've been using FR007 for a while now, but I feel like it's a little slower than R012 was. I turned off the LWP and I'm using LauncherPro, but it skips and jerks a little more than R012 did on homescreens.
Still debating whether I want to switch back, I just don't want to not have Froyo on there. I do like the apps and features that Froyo provides (Gmail upgrade, etc)
emigre said:
Hi everyone,
3. Wi-fi network stopped after phone goes to sleep (but it was already noted in the thread to download FR007).
What are your observations? Thanks for sharing!
Click to expand...
Click to collapse
WiFi sleep policy may be defaulted to "After 15 minutes". Look into Menu>Settings>Wireless & networks>Wi-Fi settings>Menu>Advanced>WiFi sleep policy. That is one buried setting!
Thanks for sharing your thoughts everyone.
I am still running on R12 and everything is running smooth as a babys' butt! Gonna keep rocking with this at the moment.
Sent from my HTC Liberty using XDA App
no trackball wake which is a a little turn off. i download trackwake.zip, flashed it, but didn't see anything change in the settings. anyone has any ideas? thanks
leonle said:
no trackball wake which is a a little turn off. i download trackwake.zip, flashed it, but didn't see anything change in the settings. anyone has any ideas? thanks
Click to expand...
Click to collapse
I believe that Liberated FRxx ROM is waiting for HTC to release the 2.6.32 Froyo kernel source for the Aria/Gratia to see how to fix the trackball wake issue.
The trackball wake is working in CM 6.1 RC2.
Anyone else? Im not exactly sure if its Phone.apk, DialerTabeActivity.apk, or simply the act of voice calls that is causing it. But it seems as though whenever i make a call, or have an incoming call, my phone almost cant handle it. It lags out like crazy.
This morning, my phone started ringing. There was so much lag that i couldnt answer the phone in time. Also, when i go to hang up a voice call, it often takes the "end call" button almost 10seconds to respond. Lastly, just earlier, i ended a call with my buddy. It LITERALLY took 3 minutes between the time i ended that call, and started a new one. Thats how bad the lag was.
Anyone else experiencing this? Any ideas how to fix it? Maybe its the modem?
This lag is literally intolerable, and a major inconvenience to efficiency.
PS - No, im not running a lagfix. I experimented with and without, and i determined that overall my phone performs better without it.
PPS - This is not me being oCD about my phone or a ROM. Im not being that "never satisfied" guy. Everything else with the ROM is great, its just this one thing.
Im using Eugene's B_Stock_1120_100 kernel, found here: http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=28
TopShelf10 said:
Anyone else? Im not exactly sure if its Phone.apk, DialerTabeActivity.apk, or simply the act of voice calls that is causing it. But it seems as though whenever i make a call, or have an incoming call, my phone almost cant handle it. It lags out like crazy.
This morning, my phone started ringing. There was so much lag that i couldnt answer the phone in time. Also, when i go to hang up a voice call, it often takes the "end call" button almost 10seconds to respond. Lastly, just earlier, i ended a call with my buddy. It LITERALLY took 3 minutes between the time i ended that call, and started a new one. Thats how bad the lag was.
Anyone else experiencing this? Any ideas how to fix it? Maybe its the modem?
This lag is literally intolerable, and a major inconvenience to efficiency.
PS - No, im not running a lagfix. I experimented with and without, and i determined that overall my phone performs better without it.
PPS - This is not me being oCD about my phone or a ROM. Im not being that "never satisfied" guy. Everything else with the ROM is great, its just this one thing.
Im using Eugene's B_Stock_1120_100 kernel, found here: http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=28
Click to expand...
Click to collapse
I would try starting from stock and working back up to nero v4.1.
I appreciate eugenes work but thats where most of my problems come from. Using nero v3 and experimenting with eugenes kernals(I was bored) I had constant lag, random reboots, panic/safe mode, freezes, couldnt access external sd card etc... Try starting from stock. Are you using titanium backup with system info.
intruda119 said:
I would try starting from stock and working back up to nero v4.1.
I appreciate eugenes work but thats where most of my problems come from. Using nero v3 and experimenting with eugenes kernals(I was bored) I had constant lag, random reboots, panic/safe mode, freezes, couldnt access external sd card etc... Try starting from stock. Are you using titanium backup with system info.
Click to expand...
Click to collapse
It sucks because this particular kernel of his offers almost everything i want in a 2.2 kernel (BLN, bootup/shutdown animations, lagfixes, OC/UV, and i also love the recovery menu).....although, with this ROM at least, the only lagfix that works is Voodoo, and the OC is only clocked at 1120ghz.
I was wondering if maybe this was causing it. And im mildly depressed to learn that it very well may be. I like TW's kernels, but they just seem to be battery destroyers.
So are you saying not to use this Eugene kernel at all? Should I try a TW one instead? Sorry but stock kernels suck and i want to avoid them if possible.
PS - I dont know what youre asking in terms of TiBu
I just tried it while on Wi-Fi, call came in, no lag answering it, I browsed engadget website, and no out of ordinary lag.
Flash back to stock and go back to the ROM, see if it resolves the issue.
EDIT: I am using Voodoo though
had same problem and i had just come from a fresh odin to stock. couldn't take it and went back to axura latest rom. plus vringo and video tonez don't work with roms with voice start and shutdowns.
Hello everyone, I'm having a few problems with eb13 I havnt seen in any of the bug threads, forgive me if I overlooked. But anyway, compared to di18 the dropdown notification bar is very stuttery and laggy whenever the menu is slid down. I'm also seeing a touchscreen responsiveness delay in any scrolling menu. The fps of the scroll is fine but it seems to take the epic a half a second longer to relize that your finger has moved on eb13. I have flashed the new rom every possible way, odin, samsungs exe, update.zip from di18. It also applies to every eb13 custom rom I've tried so far as well as the stock rom, but not the miui rom or cyanogen beta1. I'm just curious to see if anyone else is seeing the same problem as me or if its just my phone. Thanks for any input, this is driving me crazy.
Sent from my Samsung-SPH-D700 using XDA App
I'm not having this problem. Currently using supernova with ext4. Wasn't on stock long enough to test it.
Zoen22 said:
Hello everyone, I'm having a few problems with eb13 I havnt seen in any of the bug threads, forgive me if I overlooked. But anyway, compared to di18 the dropdown notification bar is very stuttery and laggy whenever the menu is slid down. I'm also seeing a touchscreen responsiveness delay in any scrolling menu. The fps of the scroll is fine but it seems to take the epic a half a second longer to relize that your finger has moved on eb13. I have flashed the new rom every possible way, odin, samsungs exe, update.zip from di18. It also applies to every eb13 custom rom I've tried so far as well as the stock rom, but not the miui rom or cyanogen beta1. I'm just curious to see if anyone else is seeing the same problem as me or if its just my phone. Thanks for any input, this is driving me crazy.
Sent from my Samsung-SPH-D700 using XDA App
Click to expand...
Click to collapse
im not getting alot of panning lag. Seems the same as eclair. But the stop down drawer is jerky and stutters alot. Eclair was very smooth, don't know why froyo does that. I mentioned it several times when the initial leaks were available. Pretty much ppl said that its beta so most likely it will be better on the official release. Well... Here we are.. Still jerky.
ever since eb13 I have noticed way too many fingerprints on my screen
Nope. My phone flies. Running SuperNova w/ Gingerbread theme on EXT4.
both of those issues seem to me to be the difference between a set rate or maybe a couple that the dropdown and the app list move at... on DI18. It seems froyo is more responsive to what your finger actually does, than just go 'ok, drop down at X rate'... could be just me... most roms I have tried are awesome that way... I like that its really responsive.... like the dropdown for example, if you slide your finger up 1/3 of the way, if follows the speed of your finger, pull away at that point and it continues at a set speed... I kind of like it... it seems like the stutter is where your finger leaves the screen, if I go all the way to the top, as fast at I can with my thumb in a normal grip on the phone, it does seem like it could use some framerate, or maybe its hitting little increments along the way... idunno... I like it better to be able to throw it up there fast than watch it nice and smoothly take a second.
for the record, on midNIGHT ROM, Genocide Kernel, 200-1200 on SetCPU, conservative scaling- dont remember stock EB13 being too much different in this particular case...
While I don't seem to get lag when scrolling, when it's not plugged in, it does take a second or so for the power button to register a press and wake the phone up.
Oddly enough, when plugged in, it turns on instantly.
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...