I'm on CM 7.0.2 and using the Tiamat 3.3.5 (no SBC) kernel. No other special overclocking or undervolting rules set up.
Sometimes, things will just go awry since I've flashed CM7. It never occurred on Sense.
Things like:
Keyboard disappearing
SMS/MMS application force closing
Text messages refusing to send
Etc.
All requiring a reboot in order to get working again.
What might be the issue?
flash 7.0.2.1 over it first (wiping cache/dalvik), the 7.0.2 build was buggy and pulled hours after it released. If that doesn't work, try fixing permissions in ROM manager. If that doesn't work, a fresh install is always best. COMPLETELY wipe everything (use VR ultrawipe for ease) then start fresh. I did it recently with 7.0.2.1 and it's running flawlessly.
Related
Hi All,
Been having a problem with the touchscreen randomly becoming unresponsive or the phone rebooting on its own ever since when I'm (trying) to run MIUI ROMs.
By "random" I mean that it sometimes occurs while typing, switching home screens, opening an app, or even just when the phone's idle.
Not experiencing any unexpected FCs throughout the MIUI ROMs that I've tried however... so at least that's a good thing?
I don't experience any of these problems at all when running a stock Sense ROM, so I'm hoping it's not the same rebooting problem described in another thread that requires sending it in for repairs as that would be very troublesome.
The phone's a HKCSL Desire that was rooted using unRevoked. The problems occur even when I don't install any apps onto the phone and when the phone's just idle with the screen off (for randomly rebooting).
Any suggestions would be greatly appreciated =) and I hope I'm not just SOL for MIUI ROMs since no one else seems to really be having these problems.
---
List of things I've tried:
1. Full wipe with Dalvik & cache before flashing a ROM (many, many times)
2. Updating to 32.48.00.32U_5.11.05.14 radio and downgrading to the suggested 32.44.00.32U_5.09.05.30_2 (Thought it might've been caused by WiFi connection as I always have it on... but doesn't seem like it)
3. Using different versions of Clockworkmod (2.5.0.7, 2.5.0.1, 2.5.0.1 modified by MIUI.cn)
4. Repartitioning/formatting SDCard before/after flashing a new ROM
5. RUU-ing the phone and redoing everything from scratch
6. Using an untranslated base MIUI-Desire ROM
7. "Upgrading" the ROM by flashing on top of the 10.15 build
Versions of MIUI ROMs I've tried:
Pretty much all the releases of 10.15 and 10.22. Currently fiddling around with eevek's stock 10.29 and mobiousdigital et al.'s 10.29 builds.
Hopeful bump =)
I just received a new incredible from verizon after rma'ing my first one and it is now constantly freezing while doing anything from browsing the web to texting. I rooted it with unrevoked 3 and then with forever. So I have s-off. I am running Skyraider 3.3.2. I thought that it might be a kernal problem so I have tried the stock htc kernal, kings, and ziggy's but none of them have fixed the problem and i have frozen up on all of them. I have not had it overclocked. Could it be a radio problem? I have my radio updated to 2.15.00.09.01.
Any further information needed?
Did you try another ROM? Did you try the phone with the stock HTC setup before rooting and flashing SkyRaider, and was it acting up then too?
Is there any mention of this on the Skyraider thread?
Abesnt that, go to Settings>Applications and look through each one, see which one(s) have a lot in the cache, and clear it.
Also, how many apps are you syncing, and with what frequency?
Finally, prior the the freeze-ups beginning, did you d/l and install any apps?
Solving for (working backwards) you uninstalling the most recently installed apps, one-by-one, and see whether those impact the freezing.
Didn't try with stock setup. I will try to redownload/reflash SR and if that doesn't work I'll try another rom.
I have glanced over the skyraider thread and there hasn't been any mention of it to my knowledge (the thread has 4500+ posts). The only apps that are syncing are Gmail, Fbook (was 2 hours, now 8), News (4 hours), and Weather.com (not sure). I haven't done dl'd any new apps since I downloaded the apps that I used on my previous phone.
I am with Mark. I would definitely try another ROM / Kernal setup. The Radio could cause slowness but not likely.
Redemptive rEVO 2.1
Hydra Kernal
Switched to Redemptive rEVO and I am still getting the same freezing problems. Thinking that this refurbished phone from verizon is junk and may have to RMA it aswell
Hey what about trying the ROM manager then fix permission. She if that might work.
Sent from my ADR6300 using XDA App
I am running CM7 on my EVO and for some reason every now and then the phone decides to reboot on its own. Is it something within CM7? DId the fix it if others were experiencing the same problem? I haven't d/l the newest one as of yet. Thanks in advance.
You can get the random reboots if you didn't flash correctly, or over clocking too high. So I would suggest to:
-Download the latest version
-perform a full wipe [factory/data, cache, dalvik]
-flash latest gapps
And you should be good to go.
It's great
mjs1231 said:
Evo running cm7. My done started rebooting in the last two days. I. think its the new update to 1tap clleaner on the market. Lowered my CPU to 245-800. Still reboots . Wiped dalvik and cache part. Still rebooted. NOTE. Cm7 has been working fine since it was posted online. Its some app fubar
Click to expand...
Click to collapse
What kernel are you running? Some kernels are undervolted quite a bit, and some phone's don't tolerate undervolting well. Reboots can possibly result. I had flashed the 3.3.7 Tiamat kernel the other day, running salvage mod. I was getting major and constant reboots. I used ViperBoy's overvolt script, and I've had no reboots since. My phone simply doesn't like to be undervolted, and getting rid of the the undervolt fixed it. So possibly if your kernel is undervolted a lot, your phone may not agree. So consider flashing viperboy's over volt script. His thread is in the dev section.
I have some issues with my Defy, it worked great for about 5 weeks with Quarx's CM7 the i started to get random lags, all apps crashing and freezes. I wiped the cache and dalvik cache, still not working.
After that i installed MIUI, worked pretty good for 2 days then got the same problem. Wiping the cache didn't worked here either so i decided to re-install CM7 (7.1.0-jordan) but still got the same problem.
I tried lowering the CPU settings to the default but it had no effect.
What else can i do?
I'm kinda new to this so please, have mercy.
Thanks in advance!
Could it be the RAM (not enough available)? Use an app like this or similar and see if there's any difference.
Also, if you like CM7, go for CM7.2 - it already has a RC version, and it's stable and fast (bug fixes included, tweaks, interface optimizations, etc). Regarding the CPU: it's not necessary to underclock to the stock 800mhz value, just be careful about the voltages (don't go too low suddenly, or you'll get freezes or random soft restarts - try to undervolt progressively).
Plus, it's a good habit to wipe Cache and Dalvik cache before and after flashing a ROM/nightly.
it's not the ram, i used netqin from the beginning which has a widget that shows available memory and a task manager and the lowest memory i ever had was 100MB. currently on cm7.1 i have 213mb available.
is there a way to completely revert all changes, like a factory reset?
Actually, task managers on Android don't fix any problems, they even cause problems - I would get rid of that if I were you.
Like a factory reset? Wiping data from custom recovery (but you'll lose all data, settings, apps, etc on the phone), but you keep your current ROM.
Give CM7.2 a shot, it might be better.
Edit: Did you have these problems before installing that task manager?
i really don't care about the current ROM, i would go for the stock android just to have a working defy. do i need to flash a sbf before installing 7.2?
could it be a hardware problem?
Don't flash a SBF!
If you are already on CM7 just flash a CM7.2 version like a nightly (wipe Cache and Dalvik cache, before and after flashing). When I used CM7.2, I was happy with a version by maniac103, from 27 February. Stable, fast, good battery life.
If you really don't care about all of your settings and apps and data and so on, you could try to wipe Data in custom recovery before installing CM7.2, it might solve that issue (but I'm not sure, and it's not really worth it to try it now, only as a last solution). But if you do that, remember to flash gapps too, after the ROM.
But first try CM7.2 and use your phone for a while without that task manager.
No, I don't think that it's a hardware problem, especially if it worked fine after you flashed MIUI.
just installed cm7.2, will update if problem still occurs.
Thanks!
You're welcome.
Great, I hope you'll get rid of those issues. Did you also remove that task manager?
Yes, kept just the basic stuff for now. i have a problem with the proximity sensor, after a call the screen stays off and i have to remove the battery. I tried loosing the back screw and several ways of disabling the sensor but none worked.
Any ideas?
Within 30-40 seconds after opening any application (including the android system ones that auto-load @ boot), they crash ; promting: "__ has stopped unexpectedly. please try again."
Recent changes:
installed avast! (recently uninstalled)
set up swift key X
any ideas/fixes?
on cm7 btw.
As a last resort, if nobody is able to come up with a specific fix for you, I would suggest reflashing the ROM or restoring to factory settings within the ROM. It can be a pain in the butt, but if nothing else works, it's like starting from scratch in the ROM. That tends to be what i do when i have problems that are widespread like that and it always fixes it for me.
Out of curiousity which build of CM7 are you using? I have the latest nightly (420) of 7.2 and it is the most stable and customizable DInc ROM I've tried.
EDIT: I am flashing CM 7.2 RC2 right now, I didn't realize it came out a few days ago. Until further notice though, I still would recommend the nightly just because I haven't really tried this yet, knowing CM though they wouldn't release an RC if it wasn't ready. Hopefully they will start work on CM9 for dinc soon if we cross our fingers.
of course >.<
i believe its a standard build of 7.0.2, i cant check though because settings crashes immediately
ugh.. now its bootlooping.
flashed to 7.2 RC2;
please lock.
vassskk said:
flashed to 7.2 RC2;
please lock.
Click to expand...
Click to collapse
I hope it works out for you!! if you have anymore problems, come on back and someone will try to help you out.