Related
Hi,
i have an Italian version of i9000 with jf5 firmware.
I have upgraded whit samsung kies my firmware.
now i have
pda xwjm3
phone xxjm2
csc itvjm1
now sometime my phone goes off
anyone have the same problem?
i read that this is a bug......
You read its a bug? Of course it's a bug.
It's either a bug with the firmware or with an application. I had the same problem when using SetCPU.
Sent from my GT-I9000
i have setcpu me too.
so the problem is this app?
just uninstall it?
I experienced it (no response completely unless I reinsert the battery) when with lag fix and GPS on, regardless eclair or froyo ROM.
then I reflashed and turned GPS off for most of the time on my 2.1 lag-fixed ROM, the problem seemed not to trouble me any more. I have also underclocked my CPU with "Overclock Widget" to 800/400 MHz on screen, and 400/400 MHz offscreen.
I have a feeling that the problem was due to GPS or due to the 0513 pit, but I'm not sure - so far it's been okay so I bother not to break it for tests.
SetCPU shuts my device down... out of nothing...
i uninstalled setcpu and never happened again
mystaka said:
then I reflashed and turned GPS off for most of the time on my 2.1 lag-fixed ROM, the problem seemed not to trouble me any more. I have also underclocked my CPU with "Overclock Widget" to 800/400 MHz on screen, and 400/400 MHz offscreen.
Click to expand...
Click to collapse
Slightly off-topic but... That'd actually be an overclock if I'm reading those numbers correctly. The default frequency is 1000/100mhz with a conservative setting, meaning it'll try to be as low as possible more or less. What you've done is set min-frequency to 400mhz, which in my book is an overclock from the stock 100mhz.
Back to semi on topic... SetCPU is known to cause problems on Galaxy S, and likely other devices aswell. Most problems has been more specifically caused by using ondemand setting when setting up profiles - for some reason the phone doesn't handle this setting well when it wakes from sleep.
I'm pretty sure I managed to get it working more or less flawlessly with an screen off profile at 400/100 with Conservative setting, though I reflashed shortly after those settings so never got to test it properly. Regardless, they might work if you want to mess about with it.
I had a similar problem with JM5 and SetCPU.
Removed and it didn't happen again.
gettons said:
I had a similar problem with JM5 and SetCPU.
Removed and it didn't happen again.
Click to expand...
Click to collapse
The way to have SetCPU working is to do the following:
Scaling: conservating
Freq Step: 100
insty said:
The way to have SetCPU working is to do the following:
Scaling: conservating
Freq Step: 100
Click to expand...
Click to collapse
Great!This work
Thank you
I don't use setcpu but I have this problem in my two SGS. Using m5 and m6..
My phone is rooted and has s-off but I have a few issues. One is almost half the time when I hit the power button the screen doesn't turn on instantly but the soft buttons light up. It usually takes me hitting it 2-3 times swiftly to get my screen on. Another issue is sometimes wifi calling gets screwed up so it doesn't work and it drains my battery as a background task stuck on restarting. I really only want my phone overclocked so just have baconbits kernel. is there a newer version I should put on that fixes these issues?
legato89 said:
My phone is rooted and has s-off but I have a few issues. One is almost half the time when I hit the power button the screen doesn't turn on instantly but the soft buttons light up. It usually takes me hitting it 2-3 times swiftly to get my screen on. Another issue is sometimes wifi calling gets screwed up so it doesn't work and it drains my battery as a background task stuck on restarting. I really only want my phone overclocked so just have baconbits kernel. is there a newer version I should put on that fixes these issues?
Click to expand...
Click to collapse
Baconbits, to my knowledge, is the only OCd kernel available for the stock ROM. Your screen issue might actually be caused by underclocking though, do you have a screen off profile or a minimum set?
Sent from my T-Mobile G2 using XDA App
I just have it set to 368-1497. Should I up the minimum?
legato89 said:
I just have it set to 368-1497. Should I up the minimum?
Click to expand...
Click to collapse
Give the overclock widget a try. Its available free on the market. In the advanced setting, set your screen off profile to 245 min and 806 max. Scroll down and hit "save" before you exit settings. That will keep your phone running at stock speeds while the screen is off and should stop the wake issue you're having. When you're using the phone you'll be at the higher speeds.
I already had the widget. Did what you said but it still occurs.
legato89 said:
I already had the widget. Did what you said but it still occurs.
Click to expand...
Click to collapse
245 is *way* too low, especially if you have things running in the background ... just start raising the lower end up until it stops happening.
Sent from my T-Mobile G2 using XDA App
Setting it to stay at 800 while the screen is off seemed to fix it. Any ideas about wifi calling bugging out? It usually doesn't happen very often, I think when my phone has been on for a while without a restart.
overclock widget doesn't overclock anything.... it controls the speeds AFTER you've installed an overclock kernel. I highly suggest using flippys turbocharged 1.8ghz kernel. Just because it is capable of 1.8ghz doesn't mean that you need to run it at 1.8ghz. you can just do something like 1.1 or something in between. Give it a look.
dietotherhythm said:
overclock widget doesn't overclock anything.... it controls the speeds AFTER you've installed an overclock kernel. I highly suggest using flippys turbocharged 1.8ghz kernel. Just because it is capable of 1.8ghz doesn't mean that you need to run it at 1.8ghz. you can just do something like 1.1 or something in between. Give it a look.
Click to expand...
Click to collapse
Nobody said the OC widget overclocked anything. Did you read the OP's first post? It was suggested so as to enable a screen off profile because the OP is having a wake issue while using baconbits.
Sent from my HTC Vision using XDA App
EdKeys said:
Nobody said the OC widget overclocked anything. Did you read the OP's first post? It was suggested so as to enable a screen off profile because the OP is having a wake issue while using baconbits.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
set the off screen profile to the lowest speed 200/200mhz and 100% priority and he wont have anymore wake issues, don't know what I was reading hahaha
The screen on issue doesn't happen anymore but I'm not satisfied with my battery life. In the past something was causing my battery to drain insanely fast so I un installed a bunch of unused apps and started checking background tasks but when browsing the internet for 20 minutes on my way home I use 30% of the battery, bluetooth on.
Sent from my T-Mobile G2 using XDA App
Anyone know if it is possible to run Pershoot's kernel on the stock rom that comes with the device? Any side effects?
I don't know enough to say 100% one way or the other, but I read in a post I can't find right now that only BaconBits is made to work with the stock rom.
FWIW, I tried to flash the 1.8 GHz kernal on my stock G2 this morning, and got stuck in a boot loop.
On AndroidCentral people are saying they have improved battery life with CM7 nightlies. I'd like to try running a ROM finally. Do I need to get rid of my Baconbits kernel before proceeding? I already backed up everything with Titanium.
legato89 said:
On AndroidCentral people are saying they have improved battery life with CM7 nightlies. I'd like to try running a ROM finally. Do I need to get rid of my Baconbits kernel before proceeding? I already backed up everything with Titanium.
Click to expand...
Click to collapse
NO. The first thing you need to do is flash clockworkmod 3.0.0.5, which is totally different than ROM Manager. As of right now the latest clockworkmod available through ROM Manager is 2.5.1.3. If you haven't flashed that yet (2.5.1.3) do that first through ROM Manager. The best way to flash 3.0.0.5 is to find the .img file, place it on your sd card and run the commands from terminal emulator. After that just wipe data/factory reset, wipe davlik cache and flash the latest nightly .zip, reboot, then the latest gapps .zip. Go to the development forum and the first post in the nightly vendor vision thread has all the links you'll need.
Hello, I have my Epic 4G rooted with One-click, running Twilight Kernal 1.1.0 and SyndicateROM Frozen 1.1.0.... I've got two issues that I can't figure out.
1. It seems whenever I play a game, my phone freezes up while I'm playing and I can't do anything except pull the battery. (Which leads to number 2)
2. So far (except once) whenever I pull the battery to reboot the phone without turning it off first, When it boots back up the majority of my apps all FC on boot. My only option that I have found for this is to wipe the phone and restore with Titanium, although that can be a big pain (not as bad as without a backup lol)
So I have no idea what's going on or how to correct these issues. I've googled my issues and have found situations close to mine, but not close enough to count towards me taking any steps toward it. Thanks in advance.
Number 1- your phone is freezing due to the undervolts that are present in the kernel. U need to flash another kernel.
2. The reason for all the force closes is journaling is disabled so that is causing corrupted data. You can turn journaling on if you just make a backup and restore from that backup. Then you would t have all the force closes the next rime u do a battery pull.
Sent From My Evo Killer!
infamshxr said:
Hello, I have my Epic 4G rooted with One-click, running Twilight Kernal 1.1.0 and SyndicateROM Frozen 1.1.0.... I've got two issues that I can't figure out.
1. It seems whenever I play a game, my phone freezes up while I'm playing and I can't do anything except pull the battery. (Which leads to number 2)
2. So far (except once) whenever I pull the battery to reboot the phone without turning it off first, When it boots back up the majority of my apps all FC on boot. My only option that I have found for this is to wipe the phone and restore with Titanium, although that can be a big pain (not as bad as without a backup lol)
So I have no idea what's going on or how to correct these issues. I've googled my issues and have found situations close to mine, but not close enough to count towards me taking any steps toward it. Thanks in advance.
Click to expand...
Click to collapse
Let's deal with number 2 first. Because you have journaling off, there is no write verification on your phone so whenever you do an improper shutdown it will corrupt a lot of data. The fix is to turn journaling on. Easiest way is to go into Clockwork, do a nand backup and restore.
For number 1, what clock speeds are you running? Words with Friends locks up on me on ANY overclocking or undervolting. So running either SetCPU or Voltage control try capping out at 1GhZ and try your game again.
Guess we were answering at the same time MH, you beat me by a few seconds LOL.
Thanks for the replies so far. So to turn on journaling, all I have to do is boot into clockword and make a backup? If not could you please give me some easy steps or point me in the right drection? I'm still really new to this. As far as the cpu undervolting, I know setcpu isn't free, at least not that I found. I'm gonna check voltage control (hopefully its free). Are there any other recommended cpu control apps?
infamshxr said:
Thanks for the replies so far. So to turn on journaling, all I have to do is boot into clockword and make a backup? If not could you please give me some easy steps or point me in the right drection? I'm still really new to this. As far as the cpu undervolting, I know setcpu isn't free, at least not that I found. I'm gonna check voltage control (hopefully its free). Are there any other recommended cpu control apps?
Click to expand...
Click to collapse
Backup and restore in CWM. Your freezes will be solved by switching to VisionKernel 1.1 or Genocide.
infamshxr said:
Thanks for the replies so far. So to turn on journaling, all I have to do is boot into clockword and make a backup? If not could you please give me some easy steps or point me in the right drection? I'm still really new to this. As far as the cpu undervolting, I know setcpu isn't free, at least not that I found. I'm gonna check voltage control (hopefully its free). Are there any other recommended cpu control apps?
Click to expand...
Click to collapse
Like K0nane said you have to then restore that same backup. And Voltage control works very well with Genocide and there is very detailed instructions in Genocide OP.
Soo... Now that mothers day is almost here, and im done with all that crap, now I have time to work on this lol. So what do you guys suggest? Vision or genocide? Are there ups and downs to choosing one over the other? Btw, I did the backup/restore thing and so far no issues, thanks again for that.
infamshxr said:
Soo... Now that mothers day is almost here, and im done with all that crap, now I have time to work on this lol. So what do you guys suggest? Vision or genocide? Are there ups and downs to choosing one over the other? Btw, I did the backup/restore thing and so far no issues, thanks again for that.
Click to expand...
Click to collapse
Both kernels are fantastic. Read their descriptions for their varying features. Be sure to use VisionKernel 1.1 for now rather than 1.2.
I have looked around and completed a few searches but cannot find any direct answers to this.
I have CPU Spy installed and have been checking it off and on since I got the phone. I have noticed that my phone does not run at any speed other than the absolute max. The phone does go into Deep Sleep without issue, but the only CPU speed it uses is 1728. I have tried a few ROMS without any change.
Currently running Juggernaut 5.0 with Darky's Kernal.
I have tried different Governers. I have tried Antutu's CPU Master, SetCPU and No-Frills. I just cannot get this phone to run anything other than MAX speed. Since I am constantly having things run in the background like music, this is effecting my battery life.
Anyone have any input, ideas or suggestions? Other than running stock.
Turn down your minimum CPU settings in set CPU and check set on boot?
Sent from my SGH-T989 using Tapatalk
You've done just about everything possible. Only option left it to Odin back to stock, root it and check cpu Spy to see if it is acting normal. If it is back to normal flash back to your favorite distro!
Perhaps something got messed up along the way of flashing all those roms? Shouldn't, but you never know.
da_dragon2k3 said:
You've done just about everything possible. Only option left it to Odin back to stock, root it and check cpu Spy to see if it is acting normal. If it is back to normal flash back to your favorite distro!
Perhaps something got messed up along the way of flashing all those roms? Shouldn't, but you never know.
Click to expand...
Click to collapse
I was really hoping it would not come to this :'(
*update....
I re-flashed Darky's Kernal and removed all OC apps and now I am showing full utilization of the different seed steps.
Quite glad it did not result in me having to start over again.
my galaxy nexus has a problem since a few months.. the phone get stuck and the screen go weird (sometimes totally black, or "noisy"), nothing works, not even the power button, i have to remove the battery to make it work again.
this has happened most of the times while downloading and installing something from goole play or while i get emails notifications and im doing something else in the phone. it does not reboot, like i said, just totally dies till i remove the battery and turn it on again.
now i updated to stock jellybean and i had the same issue. is not all the time like i said, just happens once in a while.. but i do not think is normal..
could it be a hardware issue?? i've been thinking that maybe it could be that the internal storage has some demaged sector and when android tries to write or read from that area make the phone crash.
is there any app for android to find and isolate demaged sectors??? what else could it be??
perhaps it's a hardware issue, probably with your cpu not being able to handle the load
rhed said:
perhaps it's a hardware issue, probably with your cpu not being able to handle the load
Click to expand...
Click to collapse
it seems, it is a common issue called "sleep of death", i wanna think it is a software issue, because users of the nexus 7 are experiencing this too..
but i cant find a solution for this.. everyone seems to know this issue but i have not find a solution..
it is not an app, im sure because this has happened in stock, after a factory reset without any app installed.. i've tried wipe cache also..
in other forum a guy said that could be that the device cant support low voltages and when the cpu go to its minimum frequency it shuts down.. that sounds kind of logical to me, because when the phone crash the battery usage is in its minimum (saw it in the battery statistics)..
i wanna try uncreasing the voltage a little but i cant do it in stock.. if anyone found the solution to this weird and annoying issue please help!!!
Use a uv-capable kernel, disable smartreflex, increase voltages for core, mpu and iva by 10 mV.