[Q] Noob help - Rooted desire keeps freezing.! - Android Q&A, Help & Troubleshooting

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.

Related

Help with some issues I don't understand

Hei guys, I'm new to this, barely managed to get adb working for the 1st time.
I kinda have 2 or 3 questions that I couldn't figure out entirely by my own.
1st - What's dalvik-cahce ? what does it do? what gets erased if I wipe it and what do I have to gain if I move it to the sd card?
2nd - How exactly does A2SD work? I'm currently using Link2SD and I don't know how it works and what exactly does that "linked" mean.... Or why should I use A2SD in the first place and not just use App2SD (which actually moves everything it's able to) from the market.
3rd Why does my phone crash? I tried noejins, mik's and andy's roms and they all crashed sooner or later, I got this black screen of death with some white writing on it for 1 second and the phone turned off. Is it because I'm overclocking to 122/787? That's the only common thing I could find - and - it didn't crash before I started overclocking. I think they call it "kernel panic" or something like that.
Thanks in advance.
1. Java bytecode compiler cache
2. No data lost, it is just cache. Will get recreated as needed or on reboot.
3. Link is a symbolic link pointing to another location. Google it.
Sent from my LG-P500 using XDA App
some of the phones(lg-p500) cant be overclocked above 768 OC'ed >768 = Kernel Panic and uneven shutdowns like i face after overclocking above 768.
a2sd is different from app2sd....we cannot move dalvik cache and widgets to memory card using app2sd...using a2sd you can create a partition of the memory card where these things can be stored as if it is being stored in the phone memory....it saves you some space in the phone memory....
Kernel Panic is the UNIX equivalent of what you've been seeing all your life as a Windows user, the Blue Screen of Death.
When your operating system encounters an error it cannot recover from, it dumps all the information about it in a log file and reboots. The error is usually called 'fatal'.
See it this way, it's the computer version of jumping off a cliff, realizing that you're going to die and then having your sweetest memories flash in front of your eyes Only in this case the OS comes back to life.

someone please help me with all this LAG on my fascinate

i have tried TSMressurection, and Powerwashed GB roms (followed the ops directions to the T)and i cannot get around all this lag. it seems after about 1 or 2 hours of using the phone i have to reboot. menues open SUPER slow, sometimes screen freezes for about 10 secs...i installed these roms thinking it would get rid of it...i am using Voodoo...
what can i do? what have you all done/used to make it run better? i have tried the supercharged scripted as well and nothing changes...
help me cause i LOVE the screen on this phone and want to keep it..
thanks
**OH CRAP, i did not realize i was posting this in the DEV section...MODS can you please move for me? thanks and sorry!!**
try miui or cm7 with glitch kernel, the difference is night and day.
Sent from my MIUI SCH-i500
dvigue said:
i have tried TSMressurection, and Powerwashed GB roms (followed the ops directions to the T)and i cannot get around all this lag. it seems after about 1 or 2 hours of using the phone i have to reboot. menues open SUPER slow, sometimes screen freezes for about 10 secs...i installed these roms thinking it would get rid of it...i am using Voodoo...
what can i do? what have you all done/used to make it run better? i have tried the supercharged scripted as well and nothing changes...
help me cause i LOVE the screen on this phone and want to keep it..
thanks
**OH CRAP, i did not realize i was posting this in the DEV section...MODS can you please move for me? thanks and sorry!!**
Click to expand...
Click to collapse
There is a huge debate about this, but if you are not ready for a new Kernel, you can try an app call Autokiller Memory Optimizer and set it to the Optimum setting.
This will kill apps that are eating up your RAM and over time can slow your phone. This is one simple and quick solution.
This app adjust the memory killer that is already used by the phone. This just helps it to work more efficiently.
dvigue said:
**OH CRAP, i did not realize i was posting this in the DEV section...MODS can you please move for me? thanks and sorry!!**
Click to expand...
Click to collapse
Join the club; I just did the same thing
Has anyone seen John Connor?
moved
sageDieu said:
try miui or cm7 with glitch kernel, the difference is night and day.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
Big plus one to this. It's like CM7 (CyanogenMod) or CM7-based MIUI should have been released for our devices from the start. I couldn't believe how smooth my Fascinate was after installing andmer's MIUI.
Here's his twitter where he links to his releases: http://twitter.com/#!/andmer_
And here's the latest release as of this post: http://goo.gl/Pja9F (includes jt's CM7 kernel) + patch: http://goo.gl/OquBU
Relaxasaurus said:
Big plus one to this. It's like CM7 (CyanogenMod) or CM7-based MIUI should have been released for our devices from the start. I couldn't believe how smooth my device was after installing andmer's MIUI.
Here's his twitter where he links to his releases: http://twitter.com/#!/andmer_
And here's the latest release as of this post: http://goo.gl/Pja9F (includes jt's CM7 kernel) + patch: http://goo.gl/OquBU
Click to expand...
Click to collapse
oh trust me i want to be on CM7 or MIUI, but i CANNOT get around the SD mount error. i have another thread about it. i have tried everything and nothing works. i was thinking of ordering a smaller 8 gig card to try and see if its my cards, what class/type card should i get just to install and MTD rom?? i cant CM7 and MIUI bad
Where's your other thread? I had an SD Card mount error but found a fix and posted it here:
http://forum.xda-developers.com/showthread.php?t=1296694&page=2#post18859876
Let me read your thread and I'll see if it's the same issue.
here is mine http://forum.xda-developers.com/showthread.php?t=1325525
Jsut so I have the steps down:
1) You have the ROM zip file on your SD Card
2) Reboot into ClockworkMod
3) Select install Zip from SD card
4) Navigate to the Zip file
5) Install
You're saying the process breaks for you at #3 because CWM can't read your SD Card?
If the above problem is true, try using rom manager to find and flash the file. if not try a different sd card.
Sent from my MIUI SCH-i500
back to the lag issue...when running these roms are you restoring backups from Titanium. If so, are your backups from a froyo rom, that could be part of the problem if you also get force closes. I had the same problem a while back. I have also noticed if changing fonts(such as with absolute system root tools) certain more elaborate fonts can cause some lag as well. also check into the widgets you are using, even on CM7.1 i get insane lag and launcher force closes if I use Fancy Widgets but everything else is fine.
Hopefully one of those things will solve the issue...if not wipe it clean and start fresh lol but seriously hope you figure it out
after re-reading the op it really sounds like your problem could be with restoring apps, it sounds identical to when I first switched to the GB roms. You run smooth as butter for a while the it all goes to hell. I would start with wipe data/factory reset but when intalling backups try WITHOUT DATA if you still get lag, wipe again and install your apps manually from the market or where ever. I ended up going with the latter and haven't had issues since.

Phone seems slow and unresponsive

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

Freeze Crash (Kernel Panic?) Problem Rooted Samsung Galaxy Proclaim

So right, StraightTalk Samsung Galaxy Proclaim, stock, rooted.
This phone comes with issues. I read a lot about a bug with apps on the external SD and infinite reboots, I don't have that issue.
Rooted using ShabbyPenguin method (Odin flash pre-rooted ROM, reflash stock). Applied SD card computer recognition (edit vold.fstab changing lun0 to lun1).
Installed Link2sd and BusyBox (Stericon?). This solves the reboot loop problem and gives back my internal storage.
Installed script manager and used V6SuperCharger.
Everything runs fine with a few minor exceptions. I have set SuperCharger to clear cache every hour and used the calculator for the oom settings and I have set currently to Die Hard launcher with Soft Rock panic settings.
The only issue I have is if I try to run Dolphin Browser or the stock browser or the Facebook app, my phone will freeze and I have to hold the power button until it resets.
How can I figure out what is causing this problem? I have tried having those apps linked and not linked (installed on internal storage). The problem still happens. I don't think the stock browser is that memory intenselive. I have a game on my phone, Major Mayhem, that I think is more memory intensive than that and it doesn't cause my phone to frewze.
Any ideas?
Sent from my SCH-S720C using Tapatalk 2
If it helps, the only logs generated when tthis happens are a "dumpstate_dpramfail.log" and "dumpstate_app_error.txt.gz.temp"
Sent from my SCH-S720C using Tapatalk 2

[Q] Razr Doesn't Recognize Internal Storage Running Liquid Smooth

Obviously, I'm new to this site, as I imagine most are when they have their first big issue.
Right off the bat, I want to admit that this is solely my fault, and I have been trying to fix it for the past day... To make matters worse, the phone was a gift from my wife for our anniversary, so, I feel pretty bad about it...
The situation:
I rooted my phone yesterday with RazrBlade. I had to do a factory reset to get it to stick, but that was fine. I then installed Boot Menu Manager. I set up the necessary partitions, system_3 system.img (300mb), cache.img (300mb), and data.img (2Gb). I realize I probably should have given system more room... but I didn't think that was app related. I then flashed Liquid-JB-v2.8-OFFICIAL-spyder and gapps-jb-20130301-signed from goo.im. It didn't tell me the system partition was out of memory, so I assumed (like a fool) that everything was OK...
After a few reboots to the wrong system, namely the stock system, I decided to go into BMM and change the default to system_3, and then I did the dumbest thing possible: I thought to myself, "Wow, it would be a pain to see this bootloader each time my phone reboots. I'll turn the delay to 0!" So... I did...
The Problem:
My phone now boots straight past the recovery to system_3, which seems to have no space allocated for applications at all, including system ones. I attached a picture of the storage details. It goes through the setup process each time I reboot, and wipes any changes I make. I can't download apps, and I can't install them via APK because the phone thinks there is no space left. I don't have BMM installed in this system so I can't turn the delay up, to my knowledge. There is no file explorer on this system, so I can't go into the app files directly. I have tried connecting with "Android Commander" but it doesn't want to detect my device. I installed the ADT bundle for windows to get the usb driver, but still nothing... I also tried a factory reset again, but that does the same thing as rebooting for me now.
The Challange:
To my knowledge, I'm out of options, but I know most of you guys do this to see what you are capable of. I'm sure you've dealt with bigger issues. Can anyone help? Would Verizon techs be smart enough/have the right software to actually reset the phone?
Thanks!
RustyRazr said:
Obviously, I'm new to this site, as I imagine most are when they have their first big issue.
Right off the bat, I want to admit that this is solely my fault, and I have been trying to fix it for the past day... To make matters worse, the phone was a gift from my wife for our anniversary, so, I feel pretty bad about it...
The situation:
I rooted my phone yesterday with RazrBlade. I had to do a factory reset to get it to stick, but that was fine. I then installed Boot Menu Manager. I set up the necessary partitions, system_3 system.img (300mb), cache.img (300mb), and data.img (2Gb). I realize I probably should have given system more room... but I didn't think that was app related. I then flashed Liquid-JB-v2.8-OFFICIAL-spyder and gapps-jb-20130301-signed from goo.im. It didn't tell me the system partition was out of memory, so I assumed (like a fool) that everything was OK...
After a few reboots to the wrong system, namely the stock system, I decided to go into BMM and change the default to system_3, and then I did the dumbest thing possible: I thought to myself, "Wow, it would be a pain to see this bootloader each time my phone reboots. I'll turn the delay to 0!" So... I did...
The Problem:
My phone now boots straight past the recovery to system_3, which seems to have no space allocated for applications at all, including system ones. I attached a picture of the storage details. It goes through the setup process each time I reboot, and wipes any changes I make. I can't download apps, and I can't install them via APK because the phone thinks there is no space left. I don't have BMM installed in this system so I can't turn the delay up, to my knowledge. There is no file explorer on this system, so I can't go into the app files directly. I have tried connecting with "Android Commander" but it doesn't want to detect my device. I installed the ADT bundle for windows to get the usb driver, but still nothing... I also tried a factory reset again, but that does the same thing as rebooting for me now.
The Challange:
To my knowledge, I'm out of options, but I know most of you guys do this to see what you are capable of. I'm sure you've dealt with bigger issues. Can anyone help? Would Verizon techs be smart enough/have the right software to actually reset the phone?
Thanks!
Click to expand...
Click to collapse
I like to see you getting out of that one anyway,have you tried switching default storage? I mean try that I think that way the phone "thinks" your external sd is your internal memory and vice versa that might give you a chance to install BMM or a root explorer and debloat system..you got nothing to loose give it a try man,go to settings/advance and switch default storage,good luck.
Sent from my XT910 using xda premium
FIXED!
AztekSoul said:
go to settings/advance and switch default storage,good luck.
Click to expand...
Click to collapse
Unfortunately, I tried that. The problem was that it requires a reboot, which wiped any settings
HOWEVER, the fix was along that line, it just required me to go into android shell and tell it manually.
I followed these steps to make the phone install to the SD card (internal phone app partition really) by default (because I'm a newb, I can't post links, so just google "how-to-install-android-apps-to-the-sd-card-by-default-move-almost-any-app-to-the-sd-card").
After doing so, I still had a problem downloading BMM from the market, but I think that was due to the market being outdated and troublesome, so I had to find an apk version instead.
I installed it, and restored the boot delay to 30 secs.
I then immediately booted to system_1 to feel safe.
I may try loading the Liquid Smooth rom again once I've fixed the partitions, but I will NEVER turn BMM's boot delay to 0 s EVER again...

Categories

Resources