Hello,
I am wondering if there is a possible bug with the Auto Brightness Mode in CM7 7.1.0.1 (Latest Stable).
Whenever I enable Auto Brightness through either QuickSettings or the Android Settings Menu, the device will lockup and fail to Power On (Via Power Button) and requires a Battery Pull to get the device working again.
I've also noticed that sometimes when the battery is pulled, the Time and Date Settings will be lost.
I think CM7 is great but I want to try and rule everything out here.
ROM: CM7 7.1.0.1
Kernel: 2.6.35.14 nFinity
Radio: 13.55.5524H_3.35.20.10
Hboot: 1.02
S Off / Rooted
S2E
Apps on SD-EXT
Dalvik Cache on SD-EXT
I use the same rom is also set to auto-brightness and I have no such problems. Try reflesh rom, and before that wipe cache and Dalvik cache and just in case nandroid backup.
Thanks for that, I've since wiped and performed all the above steps and can confirm that the issue is still present.
More so during a call
Related
Hi.
I'm running CyanogenMod7.1.0 on my Moto Defy, and recently, when I turn on mobile data the phone crashes (restarts) within a few seconds.
After restarting, the phone boots regularly, and then reboots every few seconds.
The last lines (before the crash) taken from adb are at: gist(dot)github(dot)com/1134269
a much longer logfile is at gist(dot)github(dot)com/1134231 (new user, can't post urls..)
each crash is marked (by me) with '=======================' and some newlines.
any help would be greatly appreciated.
As this works for almost everyone running CM7 (not seen any other reports of mobile data crashing/causing instability) it would seem sensible to clear cache/dalvik cache from Recovery (reboot, 'vol -' when the blue light shows) then Recovery - Clear Dalvik cache is under Advanced....
Also, if you're overclocking, reset to stock clocks/voltages and see if that fixes it..
You could also try the latest nightly builds - I'm using 'cm7-110809-0713-NIGHTLY-Jordan' without any issues (think I've tried almost every nightly build they guys have created!) and would strongly recommend it over your version.
Working brilliantly so far. THANKS russtyd.
And thank you for the detailed explanation, I didn't know about this recovery in cm7.
Sent from my MB525 using XDA App
I'm glad it was that easy to fix
As it turns out, I spoke too soon..
clearing the dalvik cache worked for about an hour, but than the problem came back.
Here's what I know so far:
using 2G network (with data) is OK.
Installing the 2 latest nightlies (110809 and 110806) - does not crash the phone when data is enabled, but it does kill all 2G/3G network connectivity.
Right now, I'm afraid of a hardware issue, so I'm gonna flush some stock sbf (any recommendations? would love a good tutorial, since it's my first time going back..) to check if it works there.
Anything else I might be missing?
If you want to go back to a 2.2 froyo then the CM7 FAQ is helpful for links to the sbf and drivers etc:
http://forum.xda-developers.com/showthread.php?t=1065798
Just download the following two files (links are in the FAQ):
- RSD Lite and Motorola Drivers (updated)
- SBF 3.4.2-177-005 NORDIC
Install Motorola drivers and run RSDLite, and then follow the first 2 steps of "2) How can I install CM7 RC0?", ie
- Power your phone with Volume Down pressed to enter Stock Recovery, then do "Wipe data/Factory reset" and "Wipe cache"
- Reboot from Stock Recovery with Volume Up pressed to enter Bootloader Mode, then open RSD Lite and flash Nordic
There are more sbfs here http://forum.xda-developers.com/showthread.php?t=966537 but having needed to do a clean install myself of CM7 last week (stuck on 'M' logo after a messed-up nightly install) I know this one works and gets you back to 2.2.2....
Hi guys,
I've just installed ICS CM9 4.0.3 for HTC Desire and decided to use Darktremor A2SD+ to move the dalvik cache to my SD card. After doing this the volume of the ringer and notification sound is very low.
In the ICS CM9 ROM thread there are others that reported this issue but they said it can be fixed by wiping cache and dalvik-cache, but it did NOT work for me.
I did 3 times a clean install and it did not work. I also had this issue when I switched to GingerVillain first and never got to fix it until a full wipe and install of
Oxygen ROM.
Is this a known problem ? Is there a fix for it ?
Maybe at least someone can point me in the right direction to search for the problem (I just started working with Android ROMs, so I'm not very skilled at this, but I can give it a try)
Thanks.
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?
I have a ton of variables, and hope there is one file to delete for a solution. I'm avoiding a data wipe, I don't want to restore the bad setting.
I backed up my data via MyBackup Root, shut down my phone, replaced the digitizer, and restarted my phone; this is when my problem was noticed. When I restart my phone the screen will be back-lit bright. After I force the phone to sleep via the power button or allow it to sleep via timeout, when I try to wake the phone the screen will be dim (fine indoors, unreadable outside, ~30% back-light?).
The Screen Brightness setting is settable and Auto Brightness is selectable, both settings will set and retain the setting, even through restarts.
I am HW V002, after the problem started I upgraded to 4.67 Odex ROM from Brad560 and radios (android 2.3.5, baseband 2.15.00.12.19, kernel [email protected] #1, build 4.67.651.3 CL239674 release-keys, software 4.67.651.3, browser WebKit/533.1 PRI 2.33_003, PRL 60686) I've disabled Power Saver, tried screen brightness widgets, searched every term I can think of. The phone is logging Awake, Screen On, and Deep Sleep time
Thanks for the replys. Obviously a helpful community, I've gotten this far with search.
Assuming all your settings that you've done are correct and haven't looked past anything:
You could use Titanium Backup to back up all your data and apps and settings that you'd like to keep. This might be saving too many settings but you can limit how much you'd want to carry over post flash. Then see if the problem insists once you do a complete wipe put the same ROM or a new ROM on. I use titanium backup all the time as i'm continually flashing Deck's new ICS pre betas. works like a charm. Data wipe isn't that bad of an idea if you know how to back everything up.
If your skeptical of doing a complete wipe you could try wiping the dalvik cache and cache and re-installing the current ROM you have on there now. I'm not sure if this is going to correct your problem but it could be worth a shot.
But i suggest before moving forward
1. Do a complete backup of your ROM through Recovery. You can always go back to this EXACT point. No data loss.
2. Get Titanium backup and backup the data you want.
3. Try something, see if it works knowing you can restore from step 1.
Hey,
dont use auto brightness, do you have any apps that have permission to be playing and over writing with those settings? I would do a full back up and wipe your caches and see if that does anything if not maybe try flashing a new rom or wiping data!
Keep us posted!
Hi guys, I use the Revo v. 4.0 a2sd + since its release with great satisfaction (for me it is important that the battery has to come in the evening).
In recent days, however, being on holiday at the sea, I'm having continuous blocks of Desire and I have to remove the battery to restart the device.
I have not recently installed new app and I can continue assigning these blocks to the fact that the phone is often roaming, which the city does not happen ever.
Have any of you noticed anything like this? Do you have any advice for me?
Carry the software information of my Desire:
Revolution and Easter. v.4.0 a2sd +
Baseband 32.56.00.32u_5.17.05.23
Kernel 2.6.35.14-0.9-avs-gingercakes
Build 3.14.405.1 cl 96875 release keys
RIL 2.2.0028HM (sep 20 2010)
This might be problem with your Radio, so you can try to reinstall only your Radio or:
1. Run recovery
2. Wipe cache
3. Wipe dalvik cache
4. Reinstall your system (Revolution and Easter. v.4.0 a2sd +)
You will have fresh system without losing data
If the roaming problem still exist you should run recovery and wipe data(/factory reset) and reinstall ROM