Related
Morning guys - i'm a sort of noob (go easy.!) that needs help with my HTC desire. I took plunge and decided to try rooting & applying custom ROM, but now have problems with the screen freezing completely at any point, then on restart the phone boots into the home launcher but screen does not respond or will not wake.
So far:
Rooted with unrevoked
HBOOT flashed to Cm7r2
Latest version of clockworkmod recovery via app
Aurora 4.1 (all dalvik caches wiped at correct points).
V6 supercharger applied on setting 5 (balanced).
Tried with kernel built in ROM (0.7) & gingercakes 0.9cfs no2way havs.
SD card partitioned with GParted (fat32 primary, 2gb primary ext4).
I've had the ROM working fine, the only other thing i can place it to is swapping the SD card, which i've changed from 4gb class to, to a samsung 16gb class 6. Does anyone think that this error could be anyway caused by the fact the card readers i've used (tried 2 different readers) both have had trouble recognising the 16gb card?? (Gparted still recognised it however)
Is it possible to be a hardware issue? Please note recovery works perfectly - wiping caches, reinstalling zip files, backups etc.....only problem is now this freezing of home launcher and no response.
Any help be greatly appreciated, give me a nudge if i haven't given enough detail.
Regards, Nick.!
Additional:- Tried unsupercharging & rebooting - no difference.
Only other thing i can think that i've done prior to the fault is attempting to install busybox for V6 supercharger - which failed every time and affected my root access on the phone. I've found that the Aurora ROM has busybox installed already. However, is it possible me trying that install has somehow affected the rooting of the phone?
So many questions, sorry guys!
Bump.....would ADAO file manager (which isn't on google market I notice) affect anything on ext4 perhaps? That was one app that i downloaded from net.
Have you tried reverting your busybox to the default version? Also, are you overclocking and or overclocking? Going to high or to low with CPU speed can cause problems like that. It has also been said that partitioning an SD card can damage them, which may be an issue you have now. You could try formatting the SD card to its default state and run like that for a while. I ran a 16gb SD card in a Droid Eris for months and it never caused a problem like that. Of course, I didn't have a partition set up on it.
Sent from my ADR6350 using Tapatalk
I've literally left the settings for speed in daemon controller alone, although i'm still learning and not sure if they are default overclocked or not?
Possibility with the SD card, i'll give it a try for sure, that'd mean i'd have to revert to an alternate ROM would it, as Aurora specifies an ext4 partition?
Thanks again though, it's a start at least
Do you set profiles in SET CPU?
Accidentally sent from my Google Nexus S using XDA Premium
Excuse noobie brain here, where will i find those CPU settings?
If so, fully wipe and install again. And what rom are you using currently that causes freeze?
Accidentally sent from my Google Nexus S using XDA Premium
Aurora V4.1 ROM i'm using. Don't think it's the ROM itself as i have had it stable for week or so, before swapping SD card from 4gb to 16gb.
I'm thinking this may be the root cause as i've just tried a complete fresh partition with Gparted & fresh install of literally just the ROM itself and on first boot it froze again. Rebooted and now seems to be stable with nothing reloaded back on it but we'll wait and see. If it freezes again i'll try my 4gb card. Didn't want to revert back to that as its only class 2.
[Q] Noob help - Rooted desire keeps freezing.! Update...!
UPDATED - Still getting same problems - have now tried a different SD card & alternative ROM (Cool3d v5).
Is it possible it could be heat related fault? The more i use the phone the more readily it happens - from the occasional freeze (okay after reboot) to complete freeze and no response on every reboot.
Does the CPU therefore have a cut out or could be freezing based on the settings that are initially loaded through daemon controller? What are safe settings for the min/max values?
Only other thing i've noticed is once fault starts to occur - clearing dalvik cache in recovery is quite unresponsive - menu holds before allowing me to clear.
Got to get to the bottom of this - don't want to revert back to original, or throw my phone in the river!!
Save clock is 1ghz. No over clock is the safest.
Do your phone wear case? If yes, it may be the caused of heat.
I'm sure the rom caused you the freeze. You can try to change a more stabler rom, eg aosp
Accidentally sent from my Google Nexus S using XDA Premium
Bit more progress - as my phone literally would freeze on loading home launcher, i connected it to pc and mounted via recovery - and deleted everything i could see for V6 SUPERCHARGER - and hey presto, very slowly, but phone booted up and is now working again.
I see the devs of V6 say about removing hardtokill if any lags occur - i think it's this portion of the script affecting my bravo.
SO, i'm going to run it totally without V6, and may try to just run the memory portion, but the instructions to disable hardtokill are a little unclear to me, could you guys tell me in simple terms how to acheive??
Thanks again for all your responses, a great help
V6 now off and all fresh re-installed with cpu max turned down also, and set to ondemand gov, will see how we go
[Q] Noob help - Rooted desire keeps freezing.! PT3.!
Still no joy with this issue guys - pulling my hair out now - after a few hours use (usually overnight) phone just freezes, then freezes on reboot, before getting worse and now will not pass alpharev's boot screen.
Installing fresh gets me into home launcher, but becomes unresponsive and freezes again.
I've tried different ROM's, different SD's, basic clean install, all without any luck. I'm thinking now it is more a hardware issue with the phone?
nikh667 said:
basic clean install
Click to expand...
Click to collapse
Did you wipe data/cache partitions/dalvik cache before flashing the rom? Did you wipe dalvik cache and cache partitions after flashing the rom?
Yep all wiped before and after.
nikh667 said:
Yep all wiped before and after.
Click to expand...
Click to collapse
Have you tried flashing a new kernel?
Yep fault happens with any kernel I've tried (so far 0.9c no2way havs cfs, also 2way version, 0.8f cfs havs, 0.7c)
nikh667 said:
Yep fault happens with any kernel I've tried (so far 0.9c no2way havs cfs, also 2way version, 0.8f cfs havs, 0.7c)
Click to expand...
Click to collapse
Has your device went through any physical damage (around the time the problem started)?
No physical damage apart from the battery cover being pulled off more than once(!) and a lot of obscenities being flung it's way, lol! But no, not dropped or damaged at all.
I've used the phone now all afternoon, longer than normally, with the same details on same hboot, but left some of the sense widgets off the home launcher, and it hasn't locked up once.
Not only will My Galaxy S2 not let me install new apps (trying to install VX Connectbot at a little over 800K) although it has 1.97 GB of internal storage space free, it won't let me update four apps either. They were sitting there trying to update for about half an hour before I gave up.
There's nothing wrong with the (Wifi) Internet Connection, as proved by other apps on the phone as well as by the Google Play Store updater.
If I go into Settings, Apps to look at the Play Store entry, it never finishes updating the Cache and Data storage figures, so the 'Clear Data' button is greyed out. If it wasn't I could clear the data and force the app to re-download it from Google's server. I've also tried rebooting but this makes no difference.
I really don't want to have to do a factory reset to fix this so I'd be grateful for any ideas. The phone is running stock Jelly Bean supplied by Samsung.
garryknight said:
Not only will My Galaxy S2 not let me install new apps (trying to install VX Connectbot at a little over 800K) although it has 1.97 GB of internal storage space free, it won't let me update four apps either. They were sitting there trying to update for about half an hour before I gave up.
There's nothing wrong with the (Wifi) Internet Connection, as proved by other apps on the phone as well as by the Google Play Store updater.
If I go into Settings, Apps to look at the Play Store entry, it never finishes updating the Cache and Data storage figures, so the 'Clear Data' button is greyed out. If it wasn't I could clear the data and force the app to re-download it from Google's server. I've also tried rebooting but this makes no difference.
I really don't want to have to do a factory reset to fix this so I'd be grateful for any ideas. The phone is running stock Jelly Bean supplied by Samsung.
Click to expand...
Click to collapse
I don't think Stock JB is rolled out yet by Samsung. But anyways try to clear cache and dalvik cache from recovery. This mostly resolves issues in any ROM.
Secondly, what are you referring to when you mention internal storage? If it's data partition then 1.97 is total size and not free. So please check that.
Lastly what ROM are you coming from? If its ICS then a factory reset is strongly recommended.
Sent from my GT-I9100 using Tapatalk 2
acekay said:
I don't think Stock JB is rolled out yet by Samsung. But anyways try to clear cache and dalvik cache from recovery. This mostly resolves issues in any ROM.
Click to expand...
Click to collapse
Sorry for the confusion. I'm trying to handle a million things at the same time, which is always when something else goes wrong. It is, of course, running ICS 4.0.4. I thought about clearing the cache via recovery and I'll do that if I don't find another solution. The phone won't be out of action for too long.
Secondly, what are you referring to when you mention internal storage? If it's data partition then 1.97 is total size and not free. So please check that.
Click to expand...
Click to collapse
Ooops! Quoted the wrong figure. There's 834 MB free.
Lastly what ROM are you coming from? If its ICS then a factory reset is strongly recommended.
Click to expand...
Click to collapse
It was running Gingerbread when I got it but I did the factory reset before doing an OTA update to ICS.
No issues
Since you are now on 4.0.4 do not do a factory reset since your kernel might have the Brick bug.
There are threads that provide steps on re flashing ROM over 4.0.4. You will need to first flash a custom kernel that does not have this bug like Siyah or cf-root and then flash a ROM.
Just ensure that you follow the steps properly to get a clean install.
Edit: Check below thread:
http://forum.xda-developers.com/showthread.php?t=1756242
Sent from my GT-I9100 using Tapatalk 2
I powered down and booted into Recovery, wiped the cache, and rebooted. It only took about 40 seconds to reboot which seems strange to me as under 2.2 and, I think, 2.3, it took a few minutes to rebuild the cache. Then the first thing that happens on keying in my pin and reaching the home page, I get the message, "Unfortunately, eBay has stopped." Maybe this has something to do with the problem, maybe it doesn't.
One other thing I noticed earlier but didn't mention as it didn't seem relevant is that some apps have changed their name in Settings, Applications. For example, Picshop Lite is now listed as air.ca.esdot.PicShop.Lite.
Anyway, it has made no difference. I look at any app in the list and it sits there saying "Computing...". I can force-stop running apps but I can't install apps, uninstall apps, or update apps. I'm going to leave this overnight (it's late here) and if I can't think of anything else before tomorrow I'll have to do a factory reset and reinstall everything.
Thanks, acekay, your post appeared while I was still editing mine. I knew absolutely nothing about this bug so you might have saved me from bricking the phone. The page you linked to mentions CWM. Since mine is a Samsung stock ROM it would be the stock recovery I'd be using. Is this likely to brick the phone? I guess it's better to be on the safe side and follow the instructions.
I'm also wondering about my legal position here. I got the phone from Virgin Mobile (UK) on a monthly plan. It was running Gingerbread before I did the OTA update to ICS and the update went OK. If the phone messes up and I do a factory reset and that bricks the phone, who is responsible, I wonder, Virgin Mobile or Samsung...
It took some lateral thinking but I think I've solved it. I powered down the phone, took out the micro-SD card, and powered up again. I went into Settings, Applications, Google Play Store and cleared the Data. I then ran the Play Store app and ran the four updates that were pending and everything went OK, so I tried installing VX Connectbot and that went OK, too, as did uninstalling the original Connectbot. As a precaution I uninstalled the eBay app just in case that was causing the problem. It's possible that somehow the eBay app got installed onto the SD card in error and that might have something to do with it stopping with an error every time I rebooted the phone.
I've noticed that the names in Settings, Applications are all now back to normal so I'm guessing that in fact it was something in Play Store's data that was messed up. Of course, that might have been caused by the eBay app. <Sarah Connor> God, a person could go crazy thinking about this. </Sarah Connor>
Anyway, thanks again, acekay. Working through my problem and your responses led to a solution.
Good to know its solved. So the issue was with moving the apps to SD . Better still that you tried this before a reset.
In case you plan on playing with custom ROMs in future just keep this bug in mind. Better to be cautious than sorry.
Cheers...
Sent from my GT-I9100 using Tapatalk 2
acekay said:
So the issue was with moving the apps to SD .
Click to expand...
Click to collapse
Well, I can't be sure. I'm nowhere near needing to move apps to the card yet, and since I've uninstalled the eBay app I've no way of knowing if that's where it was. Or if it was causing the problem. But I do know that I won't be staying on ICS forever. If Samsung ever get round to giving us JB, I'll update to that. If they don't I'll look for a non-stock (and non-Touchwiz, thankfully) ROM. So thanks for telling me about the bug.
Same problem with SGS2 4.1.2, stock rooted rom. No external SD card.
I noticed one thing. When I do the following:
Settings->Application manager->All
it displays about 200M free and 1.7GB used, but after few seconds it changes to about 450M free and 1.5G used.
At the same time it (long pressing home button and select memory usage->storage) shows 1.77GB/1.97GB free memory of system storage. So only about 200M is free. The same result is obtained in Teminal Emulator by inputting DF command. So it is very strange that in Application manager the free system memory is increased from 200M to 450M but in terminal and memory manager system manager is constant 200M.
So what the algorithm to solve the problem of install or update apps from market?
sercherry said:
Same problem with SGS2 4.1.2, stock rooted rom. No external SD card.
I noticed one thing. When I do the following:
Settings->Application manager->All
it displays about 200M free and 1.7GB used, but after few seconds it changes to about 450M free and 1.5G used.
At the same time it (long pressing home button and select memory usage->storage) shows 1.77GB/1.97GB free memory of system storage. So only about 200M is free. The same result is obtained in Teminal Emulator by inputting DF command. So it is very strange that in Application manager the free system memory is increased from 200M to 450M but in terminal and memory manager system manager is constant 200M.
So what the algorithm to solve the problem of install or update apps from market?
Click to expand...
Click to collapse
Try clearing cache using some application like ES Task Manager, I had useless cache data of about 400Mb once and the biggest contributor was chrome at 100Mb.. And try using apps like SD Maid which will help you clean out clutter.
Sent from my GT-I9100 using xda app-developers app
I have a problem with occasional hot reboots of my device.
Description of the device: international galaxy s3, omega Rom (from the day of purchase, now it's 33.3), siyah kernel (also from the very beginning, now it's 1.8), extsd2intsd mod. No OC or UV is required to replicate the problem.
Typical situation when it happens: I read news in flipboard, use touch translator to translate selected word, goldendic opens.I try to edit the word in the search bar of the dictionary (by pressing backspace), and at this moment device hot-reboots itself. Hot reboot also happened in other programs (one time I was also editing search bar when it happened, another time I tried to copy a text fragment).
I thought that Swype keyboard might be the cause. So I froze it in Titanium backup. However, reboot happened with Samsung keyboard.
It's important to mention that sometimes I can replicate the reboot (playing with flipboard and dictionary), but often device works perfectly despite my attempts to cause hot reboot.
Finally, the most important part: hot reboots do not happen when I have either V6 Supercharger or Bestmultitaskingfix working. That's why I think that it's a software problem. However, supercharger causes TW redrawals plus bad multitasking (at least the version which comes with omega Rom), and Bestmultitaskingfix causes lags on my device, so I don't find them to be a decent solution.
I tried to overload ram with opened apps, but nothing happened, old apps simply closed.
So, I think that the solution could be a bootable tweak which is used in both V6 Supercharger and BestMultitaskingFix. However, I'm not aware of the structure and tweaks used in these scripts. May be someone with experience in this area could suggest something?
I would like to hear your suggestions about the problem. Any ideas will be greatly appreciated!
Update: vibration is not the cause. Device rebooted even with tactile feedback turned off.
Make a nandroid backup, and flash stock rom + kernel and do a full wipe. Test it for a little while, and see if it persists.
xSpeced said:
Make a nandroid backup, and flash stock rom + kernel and do a full wipe. Test it for a little while, and see if it persists.
Click to expand...
Click to collapse
Flashed the stock firmware (ICS - I had nandroid backup), did full wipe. So far, no reboots were observed (intentionally played with flipboard and golden dictionary). Seems that it's a software problem. Still, I need to fix my omega rom somehow...
A clean flash for Omega might be a good idea.
Frequent random boots can be the beginning of "sudden death"... look for this thread in General section....
So the other day i flashed a new ROM i forget which one (flashaholic)
Anyway when it loaded the initial setup enter gmail etc.
The screen started flickering then turned off it done this each time i turned the screen on
I rebooted it done the same again
After i eventually got it setup it stopped
I have since flashed several other roms Dual boot etc.
Some of these roms i have used before with no problems BUT
Now the roms seem to run fine for the better part but become unresponsive for a few seconds when installing apps from market
I use go backup and phone screen has turned of in the middle of restore several time with several roms and wont come back on unless i reboot
I have tried alternative backup restore apps with the same outcome
It seems my internal memory has suffered some sort of problem as these problems only seem to occur when the internal memory is being written to
For the record i use superwipe script before each rom install
Anyone else experience anything like this
The short "stuttering" when installing an app from Play Store also happens to me, but well not really a big deal.
Did you try to flash a stock rom and stock kernel to start with? In addition maybe a mega wipe would also help to format all partitions (except the important once of course).
I believe it is the megawipe script i am using the problem persists when apps are updating phone becomes unresponsive
It reminds me of my HD2 days when the system was installed on both the internal and external memory
chrismast said:
The short "stuttering" when installing an app from Play Store also happens to me, but well not really a big deal.
Likewise over the last few versions of JB #Especially on multiple installs .
Same on Note 10.1 so it looks like a Google problem .
jje
Click to expand...
Click to collapse
Hi,
Before creating this topic I tried to run some research but I haven't found anything useful that would explain my phones recent behavioural problems. The problem with my i9300 is that the phone freezes at random while Android is operating. This happens in settings, while apps get updated, when getting phone calls, when opening an app, when registering a google account (new setup), when opening SMS app... The sreen stops responding, none of the hardware keys do anything and all I can do is take out the battery. It's just crazy and does not seem to have any rules to this madness. The problem started after flashing a new version of Sentinelrom (and CMW supporting android 4.4.2 installations). This is what I already tried to troubleshoot/resolve:
- flashing another recovery (now on latest PhilzTouch)
- flashing other roms (UltimaAOSP Valhalla, latest CM11 nightly, CM10.2 stable, Slimkat ROM) with full wipes, dalvik cache cleanup etc.
- flashing boefla kernel (during Slimkat tests)
- formating \modem
- formatting externalSD (was and is on exFAT)
- taking out externalSD for a longer period
- restoring apps from google instead of titanium backup
- not restoring any apps and settings from google
- installing apps selectivly
Nothing helped although the phone was running most stable on UltimaAOSP Valhalla (3 freezes during one day). The freeze never happened during playing a movie or listening to music. The freeze never happened while in recovery mode.
Does anyone have any other suggestion on what I can do? Any input appreciated!
Maybe your device is affected of the Sudden Death Syndrome.
Try eMMC brickbug Check from Google Play.
mischa_martin said:
Maybe your device is affected of the Sudden Death Syndrome.
Try eMMC brickbug Check from Google Play.
Click to expand...
Click to collapse
Thanks for input. I run the check. The chip may be affected by sudden death, but all of the roms I've tested (now testing Android Revolution based on 4.3 stock - 3 freezes just today) have the fix implemented. Also I have had this phone for almost 2 years now. The internal memory check within this app also found no errors. So I guess it's not related to SDS.
Freezing is usually due to nand memory having bad blocks, read the freezing thread in general forum.
Sent from my GT-I9300 using Tapatalk