Database Users

Samsung lock-screen kind of problem

Im having some issues with my vibrant and since today, everytime I lock the screen, then i try to unlock it, it stays black and nothing comes up or anything i just can seem to unlock it without holding the power button which causes the vibrant to restart. is anyone having this problem? Any solution to it other than formating maybe? Its rooted and I have a lag fix on it.

I'm assuming you've rebooted?

no i didnt. i didnt try to do that because i didnt want to lose everything. i was hoping its some app and i tried uninstalling some apps but still got the same problem. It keeps happing to me everytime since earlier today. you think that would work?

s15274n said:
I'm assuming you've rebooted?
Click to expand...
Click to collapse
I thought the same thing.

Ok. Something must be in the air. Exact same thing happening to me today.
Each time the screen times out the phone becomes unresponsive. Blank screen, soft keys don't light up. If I hold the power button too long it just reboots.
Rooted
Flashed lag fix
Clockwork recovery
Set CPU

Ya know what, as soon as I posted the details on my phones configuration it dawned on me that it could be a setcpu problem... Looking into it.

Set CPU was my problem. When I looked at the min/max they were both set at 19 out something ridiculously low like that. NO MORE SET ON BOOT!

I bought SetCPU but have not installed it on the Galaxy... I really don't see the point right now unless you want to underclock, and yes, it has been reported (perhaps fixed now?) that set on boot could cause issues.
I would just uninstall till we have a kernel we can OC.
OP, what would you lose by rebooting? Yes... I do believe that would work (and uninstalling SetCPU if you have it or change the aforementioned)

Set CPU profiles cause the phone to reboot and or freeze. See this thread forum.xda-developerscom/showthread.php?p=7808723#post 7808723

lagginess
Just to clear the setcpu is useless without a proper kernel i had it everything bogged down badly like reported went down to 19 from 10000. I would just take off the setcpu and wait for a kernel my phone def sped up after but thats my own experience.

GT-i9000m has been locking up recently to the point of removing the battery.

It went from extremely rarely doing it to three or four times just the other night in the span of a few hours. I can't reproduce it on command but it happens when I lock the screen and put it in my pocket. Then sometimes when I take it out it is entirely non-responsive, even the power button doesn't work. I have to remove and reinsert the battery.
It could be ADW Launcher or WidgetLocker since those are the only two programs always running, but I was hoping someone else experiences a similar issue. It hasn't happened when I normally lock it yet though, so it could also be the proximity sensor maybe?

Having the same issue (on Bell as well), but not running either of those two apps. Was almost to the point of returning the phone and then installed JM7 and it's been better, although not perfect. Last night it locked up with NoLED displaying an icon, so I've deleted that app to see if that's the issue. It hasn't locked up today, but it did reboot a few hours ago seemingly at random. :shrug:

Your internal sd card might be failing like all the other i9000m phones I see on this forum bricking themselves .

clubtech said:
Your internal sd card might be failing like all the other i9000m phones I see on this forum bricking themselves .
Click to expand...
Click to collapse
Oh, that doesn't sound pleasant at all...
I'm outside of Bell's 30 day exchange period plus I've talked for over 30 minutes, so I'll have to go through Samsung if it completely breaks. On the plus side, a phone from them should be three button recoverable.
Although I can't be without a phone for weeks, I hope it's not the SD card.

Mine Lags like crazy once every few days till the point I need to restart it. Any idea why this is do?
Sent from my GT-I9000 using XDA App

Hold your horses people....
before you jump about the lag, and or one click lag fix and such
first you have to investigate what is running on your phone.
just over the weekend (since XDA was down) i stalled over 400 Apps
my phone slowed down to snail speed, then i ran my Startup Manager software (many to choose from)
I suggest Startup Cleaner 2.0 then uncheck everything, leave only the apps that you want to run during start up
reboot your phone and presto, fast as new!
if you can find version 2.1 of startup manager that one is even better
keep note, start up manager apps are not the same as task killer apps
it only run once during start up, and it helps you easily select what should and should not run during start up, so it doesn't stay in memory after it runs
on the same topic
you should also configure your Task Killer apps to kill everything, and add only the wants you want to be running to the ignore list.
that will keep the phone working smoothly even without the "one click lag fix"
i'm still running stock on my JH2 i9000m

AllGamer said:
Hold your horses people....
before you jump about the lag, and or one click lag fix and such
first you have to investigate what is running on your phone.
just over the weekend (since XDA was down) i stalled over 400 Apps
my phone slowed down to snail speed, then i ran my Startup Manager software (many to choose from)
I suggest Startup Cleaner 2.0 then uncheck everything, leave only the apps that you want to run during start up
reboot your phone and presto, fast as new!
if you can find version 2.1 of startup manager that one is even better
keep note, start up manager apps are not the same as task killer apps
it only run once during start up, and it helps you easily select what should and should not run during start up, so it doesn't stay in memory after it runs
on the same topic
you should also configure your Task Killer apps to kill everything, and add only the wants you want to be running to the ignore list.
that will keep the phone working smoothly even without the "one click lag fix"
i'm still running stock on my JH2 i9000m
Click to expand...
Click to collapse
All gamer has a good sugestion here BUT we are going to get people flaming the fact that Android shouldnt need task managers.....
Ho hum..
TBH in my experience, I have found (after a couple of hard resets) that there appears to be a size limit for installed apps. Once I get over this size limit, I get LAGTASTIC, phone slows to a snails pace, then I remove a few of the apps and I am back at light speed again....
I cant say what the limit is, but I know when I have hit it - I would then uninstall a lame app or two and get back running.

Yes a lot of people "claims" that, but yet you do a search in Android Market, you see LOTS of Task Manager / Killer apps for every phone.
they were not designed for Galaxy S, they were designed long ago for all the other phones that had and still have the same problems of memory management causing lags
Android is not robust enough to survive without one
heck not even Windows 7 or Windows Mobiles phone

I just read that possibly the phone freezes while trying to find a signal. As this problem has only recently started, and I just recently moved into university, and many buildings receive little to no wireless signal, I think it's more than a coincidence. I'll try going to plane mode before entering lecture halls and basements.

Frostshock said:
I just read that possibly the phone freezes while trying to find a signal. As this problem has only recently started, and I just recently moved into university, and many buildings receive little to no wireless signal, I think it's more than a coincidence. I'll try going to plane mode before entering lecture halls and basements.
Click to expand...
Click to collapse
i don't think that is the case with the Galaxy S
however back then my Treo 650 did suffer from that.
if you believe that is the problem then try this
http://forum.xda-developers.com/showpost.php?p=7999389&postcount=28
more cool apps here http://forum.xda-developers.com/showthread.php?p=7999389

Random HD2 Freezes!

Hi guys. I've been running the Android Stock Desire build from Cotulla for a few months now. Every once in a while I'd get a freeze, but then a battery in, and out would fix the problem (usually within the first try. sometimes I need to do this a few times, but no more than 5 times)
However, since last Friday my phone has been crashing like crazy! Constant crashes at random stages, and even reboots. Removing the battery also didnt guarantee a fix. I think I may have tried it about a hundred times, and Android just crashed at a random point in time during every boot. Eventually it booted, but since then it has crashed again! I figured that perhaps I should try a newer build.
I've decided to try out this build: [08.MAR.2011][CWM]TyphooN CyanogenMod 7 RC2 v2.5.4[2.3.3][A2SD/RAM][rafpigna OC 1.8]. Since I already have radio 2.15.50.14, these are the steps I've taken:
- Flash Task29 (ShaDrac version).
- Flash MAGLDR 1.13
- Flash ClockworkMod Recovery v1.3 135M System
- Flash CM7
Now, even during the various stages before flashing the CM7 rom, I would get freezes during the MAGLDR 1.13 bootscreen, or recovery won't load and I'll get stuck on the GOGOGO screen. Also, copying the zip file over in the MAGLDR mass storage mode won't work, and causes a freeze when I start the copy. Reset, or Battery removal seems to get me to the next step again.
Eventually I've flashed CM7, but now it freezes at the setup stage.
I'm starting to think maybe its not the various Android builds that I'm trying, but perhaps the problem lies somewhere else on the phone? Any ideas? Is my radio perhaps not the best one for the phone (even though its the latest)?
Any help will be much appreciated.
Regards,
XA83

Shameless bump (hope I'm not breaking any rules!)
I realize this post should have probably been under the CM7 thread as well, but I don't have access to that yet due to my low post count...

Could be:
*Wrong CWM Size, check in the rom thread for information
*leftover data, task 29 and reinstall everything
*Corrupted data on SD card, try booting without sd card to see if this is the case.

Thanks for the reply.
I've removed both the SD card and the SIM card. Phone seems to work flawlessly. Boots CM7 without a hitch. Next step I've added the SD card back, and formatted the card from the CM7 settings page. Still perfect.
I've tried it about 5 times now and every time the SIM card is not present, the phone works like a dream. Every time I put the SIM card in, CM7 crashes within the first few seconds of showing the home screen.
Finally, some progress!! Thanks again for the assistance. However, what dis this mean? Could this be related to the actual SIM card I'm using, or does it have to do with the part where it initiates the network connection and possibly the 3g connection?
*Also, just for information, I believe that I do have the correct CMW size. The build indicates "Flash ClockworkMod Recovery v1.3 135M System" which is the one I've flashed.

maybe reflash back to winmo then do evrything all overagain to android

I doubt it's an issue with the phone and its initiating with the sim card. Just replace the sim card

the SAGA continues
Hi Guys,
So since my last posts I have actually managed to get the phone running Typhoon's CM7 and its been working great... for a while.
I'm currently on version 3.0.4 and I still get:
1) Freezes,
2) Reboots,
3) SOD,
4) This happened today: phone cuts mid-phone call and makes a loud buzzing noise until I pull the battery.
I'm thinking more towards hardware problem at the moment, but please let me know what you think, and what I can do to debug the sitaution. Is there perhaps a hardware monitoring app that I can install that logs the whole system every 1 minute that I'll be able to pick something up.
I was also thinking maybe the phone overheats. As explained in my original post, whenever a crash or reboot occurs, it would sometimes not restart the first time round after pulling the battery out and putting it back in. Sometimes I get crashes even during the MAGLDR stage with "fatal hit" and strange things like that. Or even when I boot into CWM sometimes.
Now, to test this overheating, I've experimented with placing my phone in the fridge for 5 minutes after a crash. Thusfar I've done this 3 times, and every time I get a clean boot when I put the cold battery back in and then the phone functions perfectly for a while.
So, overheating, or do I perhaps need another radio? I'm out of ideas.
Any help will be much appreciated. The problem now is that I'm so used to android that I wont be able to go back to winmo or even blackberry
Regards,
XA83

it happens to my phone, and did on my previous HD2.
I've tried every build, task 29, every radio...new sd card....everything.
matt

Are there any apps we can run to test battery temp, cpu temp, cpu voltage or anything like that? I'm pretty effecient at debugging PC hardware issues, but when it comes to my phone I feel like I'm back in the stoneage!
Please help

I have tried over and over and over and over on this kind of issue.
most if the time was some unfinished coppied file which can;t runs properly on roms.
Try to asks ROM developer.
- SD partition : how many partititons?
- SD partitions : what kind of partitions, is it using etc 2/3/4, does it comes with swap etc?
- Installation method : does it needs to clear phone ROM with cwr ? what is the size?
HD2 usually I will go for 400M size
- config.txt settings for SD/NAND.
A proper guide could helps you on in the installations

If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App

Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Possible solution, Thanks mate,
I changed the CPU speed to 1036 Mhz from stock 998 Mhz speeds and haven't had a Freeze yet,
before that The touch screen would freeze occasionaly when there was a lot of activity like in games such as fruit ninja ....
a Lower CPU speed such as 806 Mhz also seemed to do the trick ...
I don't understand why the Freezes would occur at stock speeds ...
I'll have to give it a few days though ...

Touchscreen Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Update:
Tried that with Interactive Governer, it still freezes on odd occasions, and the battery temp shows 33-36 Degrees Celcius on load when running games ...
i'm beginning to think the freeze is temperature related, as it never freezes while it's cool ...
I'm going to try running it with Smartass governer and see if it makes any difference ...
regards.

Yeah, there's been alot of HD2 owners who've had high-temp related freezes, one guy even went as far as to dissassemble his phone, re-bond the cpu to his mainboard, and add a home-made heat sync to prevent further overheating (successfully)
I just figured changing the cpu freq or governor might reduce cpu load, or increase efficiency, resulting in less overheating. But I feel pretty confident in saying that you guys' freezes are very likely coming from heat. It was even a problem in stock WinMo roms
Sent from my HTC HD2 using XDA App

Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly

Touchscreen Freezes
Dylan Wilson said:
Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly
Click to expand...
Click to collapse
Thats wierd, I'd have thought that such a High Temp as 44 Degrees C would cause more freezes ....
regards.

i'm getting freezes from cyanogenmod android too. i recently restored my ROM to the original 2.13 and believed to have all previous settings related to android deleted.

freezing
i realy didnt undrestand what the exactly means of freeze, my phone freeze after change rom ,i can't use "TyphooN CyanogenMod " becuz my phone freeze at the android logo and it didnt any animation to boot !!!
i have hspl8 , radio 2.15.50 ,Recovery_130M_system_4M_cache[v3.0.2.4],mgldr 13.
i install windows then install android but it steel frezz, i can install just HyperDroid-GBX rom !!
it this problem fix with cpu temp ??
i get it in Refrigerator still feee !!

Temperature
Hi guys. It's definitely the overheating causing all the freezes. I've now succesfully "fixed" my phone 11/11 times by placing it in the freezer and then it works flawlessly for at least a day.
I'll try setCPU to try and lower the CPU frequency from stock and prevent heat issues.
However, ideally I'd like to return the phone to the manufacturer as a defective one! Only problem - how do you convince the 'genius' tech guy that the phone overheats. Last thing I want is to send the phone in, and only get it back after a few months with some response that they found nothing wrong.
Hence, I'm still looking for some sort of app to prove in a way that the overheating is causing crashes... At least in that case they may be more likely to issue a replacement immediately. Any ideas yet?
Regards,
XA83

Just a follow up:
My phone has been sent back to HTC. After a long wait, tech support said they replaced the hardware components - I'm assuming the phone mainboard.
I've reflashed CM7 since, and it hasn't crashed a single time!
Verdict: Random freezes was caused by hardware problems on the phone, and the crashes was most likely due to overheating of the components.
Regards,
XA83

Droid X touch screen freezes after unlocking

I noticed lately that when I get a phone call, I can't slide to answer when the phone is locked also when it is sitting for awhile charging or not, when I slide the lock button, the touch screen freezes and takes a few minutes to recover before I am able to make calls, text or use any application.
My DX is rooted andI am running leaked Gingerbread, however I was having the same issue with the Stock rom. I do not use any task killers.
I have installed Droidwall and Titanium back up.
Any help will be greatly appreciated.

rdeluis said:
I noticed lately that when I get a phone call, I can't slide to answer when the phone is locked also when it is sitting for awhile charging or not, when I slide the lock button, the touch screen freezes and takes a few minutes to recover before I am able to make calls, text or use any application.
My DX is rooted andI am running leaked Gingerbread, however I was having the same issue with the Stock rom. I do not use any task killers.
I have installed Droidwall and Titanium back up.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
Are you overclocking?
Sent from my ADR6400L using XDA App

No overclock, no task killers. I use titanium back up and did not freeze or remove any apps. It is strange and reminds me of a laptop coming back from the hibernate estate, it takes a few minutes to reset and then is good to go.

Mine has been doing the same exact thing!

I have removed fancy widgets which is a nice Clock/Weather combo widget but I have a feeling that it might be the culprit.
I'll keep posting any findings and again help from the experts will be greatly appreciated.

We need to compare our installed apps to see if there is a common one. I don't have fancy widgets but I have MUIU clock/weather app and it seems really wonky.

I have pretty much traced this down to a bad MicroSD. Oddly, my PC will still be able to use them. My Nexus One wouldn't even touch the SD card that was freezing my Droid X.
Looks to me like Motorola left something out of its SD or FAT driver.

Is there a fix?

Right on the dot. I removed the SD card and "voila" no more slow downs. I guess must be something. related to the drivers, as you mentioned.
Today, I put back the Sdcard and gotfrom the Market place an overclock applicatkon called Droid Over lo k. So far is going good and very fast, however overclocking is always risky and shortens the life of any processor.
I'll keep you updated.

didn't work for me... seemed to help at first but I got the lock ups again today. About to move on from Motorola.

OK! After trying different combinations such as SD card, no SD card, Rooted, UN-Rooted etc.
Finally, out of desperation, I got my old HTC and pulled out the 16G SD card, put it on my DX and used it for 3 days with no freezes or lock ups so far. The funny thing is that this SD card that I put in, is a low end cheap Polaroid brand.
I'll keep you updated

It is a known fact that the SD cache is low on the Droid X. Higher class cards will have problems unless the cache size is raised. Even than, it's not a guarantee for success. I have a Class 10 card that caused crashes daily until I installed a mod for the cache size. Didn't solve all of my issues, but it stop the crashes.

You are absolutely right. I have been doing ok with the low end card. Recently I got from the market an app called SD Speed which raises the card cache and no matter which card I use now the systrm runs very smooth.
Thank you all for the help and feedback.

Freeze after 10-20 seconds of operation on CM7 running on SD

Hello all,
Really new to the android game here and I have a problem with my nook. I looked around the forums and didn't see anything that was just like mine so I thought it wouldn't hurt to ask. I'll give you (whoever is willing to read this and give me some suggestions) as complete of a picture as I can.
I recently bought a refurb nook color. I put the latest stable build of CM7 on a 32gb class 4 sandisk card. Everything was working great. I tweaked the CPU settings (voltage too) and everything was running smooth as butter for the past two or three days. A few days ago I also upgraded the stock OS to 1.4.1.
This morning I woke up to a dead nook. I thought it was mostly charged before bed but I figured I had made a mistake. I plugged in, rebooted, got it to work for 10-20 seconds (VERY shaky performance) and then it froze up and I had to reset. It did this 3 or 4 times in a row until I gave up and booted into stock OS, which is working flawlessly. On the way home I was still having the same problems with the CM7 so I decided to take out the sd card and reinsert and that seemed to do the trick! I was able to use it for a good 1-2 hours and everything was flying. However, I went to plug it in and it froze up again. If I have it plugged in and when I drain the power (by holding the power button) it boots right back up, works for 10-20 seconds, then dies on me again. Stock OS is still working great, but I don't know what to do with CM7.
Was it messing with the CPU settings (though I reset all of them in my 20 second window at some point and that didn't help)? If it was the CPU settings, what are some suggestions for what I should set them to if I just start over? I know that not every chip is the same and thus not all of them will respond well to overclocking.
Was it my upgrade to 1.4.1 on the stock OS (why would that effect CM7)?
Is there any way to fix this? Should I just start wipe the card and start over? Any suggestions on what to or not to do next time?
Thanks in advance for your help!

If you are not using Nook Tweaks, download from market. Set minimum to 300 MHz and maximum to 1200mhz. Set scaling to "on demand". Leave or reset CPU voltage settings to the standard settings. Messing with the voltage settings will result in instability, especially if you do not know what you are doing. If there is a "set on boot" setting, enable it. Reboot.
Upgrading to 1.41 has no effect on the SD cm7 install.

hwong96 said:
If you are not using Nook Tweaks, download from market. Set minimum to 300 MHz and maximum to 1200mhz. Set scaling to "on demand". Leave or reset CPU voltage settings to the standard settings. Messing with the voltage settings will result in instability, especially if you do not know what you are doing. If there is a "set on boot" setting, enable it. Reboot.
Upgrading to 1.41 has no effect on the SD cm7 install.
Click to expand...
Click to collapse
Thanks, but I just tried this and it didn't work. I've been noticing that it's hanging most, if not all times, when giving superuser permission in the background, mostly to "autokiller memory optimizer" app. Can this be doing it?
EDIT: Never mind, still crashes/freezes even when no superuser permissions are being granted and with all of hwong96's suggestions in place. Any other suggestions? Thank you.

Uninstall that app and reboot. If system is stable after reboot you have your answer.