Hi Everyone,
I recently put CM7 on my wife's Fascinate, and there is some strange behavior I'm not sure how to fix.
In a nutshell, whenever she has a notification, any notification, the front buttons light up until they're dismissed. I searched around in settings, but I can't find anyway to disable this "feature".
Is this a bug or is there a way to fix this behavior?
Thanks!
I had similar issues... my soft keys would light up for no reason at all... plus 3G connection problems as well... what I did was wipe all cache, Delvik, and factory reset.. then I flashed the kernel with Glitch v13. I've had no problems so far. Glitch fixes a lot of the stock CM7's kernel issues IMHO...
If you don't want to flash the kernel, try BLN Control app from the Market. a lot of ppl say it fixes issues like that. personally... i like the Glitch fix better.
I hope this helps you.
I'm a bit noobish with the Fascinate... it's my wife's phone.
What kernel would you recommend? Will I need to reinstall the ROM if I factory reset? Can I flash a kernel without blowing the ROM out?
if you're on CM7.1... I would highly recommend Glitch v13 kernel.
and I would, to be safe, wipe out all cache and factory reset first. then immediately flash glitch v13 before you reboot.
make sense?
no need to reflash the rom... unless you want to
Can I flash the Kernel via Clockwork Mod or do I need to use one of the tools on my PC?
http://androtransfer.com/tk-glitch/CM7-kernels/Glitch/Fascinate/
Assuming the one at the bottom?
Yes you must flash via clockworkmod recovery... whichever fits your phone.
Sent from my SCH-I500 using xda premium
you need to odin cwm4 fixed for mtd(CM7), then 3 finger into recovery, wipe cache and dalvik, install gitch v13.zip from sd.
-Boot up once, then reboot into recovery via long pressing the power button and selecting recovery.
-Find glitch menu in recovery, then select screenstate scaling, select conservative.
-Go back, then select configure leakage setting, start with medium leakage.
-reboot, then download voltage control from market.
-start with -50uv across the 100-1000mhz steps, 1200-1440mhz try -25uv. (this is a good starting point to undervolt). Your phone may handle more undervolts and overclocking, but you will have to tweak it from there. Most fascinates are not stable past 1440mhz.
Related
I have searched fairly thoroughly on this and have yet to see even one post. I am on MIUI 1.10.28.1 and *trying* Glitch v.12. (although I did try with older versions of both to no avail). My touchkeys become completely non-functional upon install of the Glitch kernal with MIUI. If I leave it with the stock kernal---no issues. But I know the Glitch runs much more efficient and want to use that one.
Has anyone had this problem occur? Just to note, I'm not talking about BLN, but total functionality. Makes it a real pain to use your phone of you cant go back a screen.
did you wipe cache and dalvik in cwm before flashing glitch?
On top of the cache wipes, I also use Kernel Cleaner script, before flashing.
I'm using JTs 1016 Kernel on Miui right now.
I have done BOTH of those to no avail. I am so confused by this...
If you can afford it, try the glitch kernel updater app: https://market.android.com/details?id=com.glitch.updater
it will give you gltich v13 which fixed that issue.
I installed Cyanogenmod 7 a week ago, and everything was pretty much working fine.
Randomly today, all 4 of the soft buttons stopped working in the middle of me using my phone. I believe I was checking scores on an NFL app. Regardless, reapplying the CM7 zip didn't fix it. I tried factory reset, wipe cache, wipe dalvik cache. Nothing.
Decided to try to reroot. Reapplied ED05, which is what I did before I installed CM7. Got back to essentially factory... soft buttons still don't work. Reinstalled CM7... took, but soft buttons won't work.
I thought I read somewhere that this is an issue with gapps, but I can't seem to find that page or people discussing it again. Installing gapps again didn't work.
I'm willing to get my phone back to it's most basic level, and even erase the SD card if I need to, but not sure how to clear my phone moreso than my reverting back to ED05.
Thanks for your input guys.
Also, I had reinstalled my apps using Titanium, but not the app data. Again, everything was just fine for a week.
Also, having done a bunch of flashing and what not, I dont' know what happened, but now when I long press the power button, the menu comes up. When I try to use volume up/down to navigate to power off, all I get is volume going up and down
So, i know this thread is sort of dead, but this happened to my fascinate a while back with a version of CM7 mtd (55 maybe?)... I'm fairly convinced that the sensors for the buttons (and the lights for that matter) are completely shot, but I can't really test that. I have flashed back to stock, re-rooted it,and done everything I can think of to fix it.
You probably messed the phone up for good... my advice (if you haven't already done it): get a new phone.
I've noticed that when I revert back to stock ED05, and flash CM7 on top of that, it doesn't work right. minor to major glitches appear...
What i did was flash back to stock ED05, then ran the update to Gingerbread EH03... Then flashed CM7 with Glitch v13 kernel. seemed to fix a lot of my issues.
idk if this helps or it's just a flook, but just sayin...
Will try this out
JJ5150 said:
I've noticed that when I revert back to stock ED05, and flash CM7 on top of that, it doesn't work right. minor to major glitches appear...
What i did was flash back to stock ED05, then ran the update to Gingerbread EH03... Then flashed CM7 with Glitch v13 kernel. seemed to fix a lot of my issues.
idk if this helps or it's just a flook, but just sayin...
Click to expand...
Click to collapse
Thanks for the suggestions. I'm having the same issues as the OP with failing soft keys after flashing through CM7 to an android 4.1 based ROM, Paranoid Android. Is the Glitch kernel built into Cyanogenmod 7 or did you load it separately?
Charcaroth said:
Thanks for the suggestions. I'm having the same issues as the OP with failing soft keys after flashing through CM7 to an android 4.1 based ROM, Paranoid Android. Is the Glitch kernel built into Cyanogenmod 7 or did you load it separately?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1488976
If you are already on ICS just wipe cache and dalvik cache and flash. If not just flash up to ICS and flash kernel with ROM (same cwm session). You may want to do some reading in that thread first to make sure you get right version for your ROM.
Sent from my SCH-I500 using xda premium
Hi all,
I installed CM7 on my TP a ways back but never really used it and stuck with WebOS. I decided to upgrade to CM9 Alpha2 yesterday and did without any issues. I then got curious about CherryKang and decided what the heck. I was able to install CherryKang but now I am having a few issues:
1. When booting CM is still listed in MoBoot and CherryKang is not. If I select CM, then I get the CM boot screen for a sec and then CherryKang boot screen comes up. Not that big of a deal, just hoping to get it setup right.
2. The Gallery force closes every single time.
3. Occasionally unresponsive when trying to wake it up. I always put it to sleep when I am done by pressing the power button, but I have to reset it to wake it up about 30-40% of the time.
Those are my only issues so far. Other than that I'm diggin' ICS.
1. CherryKang is based on CM9, if you don't like it change the name to cherrykang. Or something that suits you.
2. Reflash?? I had CherryKang before and I had no issues, try gallery++cm from market or play store whatever
3. Reflash?? + maybe wipe everything??
svenerator said:
1. CherryKang is based on CM9, if you don't like it change the name to cherrykang. Or something that suits you.
2. Reflash?? I had CherryKang before and I had no issues, try gallery++cm from market or play store whatever
3. Reflash?? + maybe wipe everything??
Click to expand...
Click to collapse
I tried wiping the cache, dalvik cache from CWM but no luck. Then re-downloaded and reflashed but still no luck. Ended up going back to CM9 Alpha2 and so far has been stable. I've been able to wake it up without issue far....
You may want to try and restall CM9 with the Acmeinstaller2 method. I read that although you can use CWM to go from CM7 to CM9, you can get leftover files/directories that could may or may not cause issues in CM9.
after using Acmeinstaller2 to get to CM9, you can safely use CWM to flash other CM9 roms. Also, before you flash, use classicnerd's moboot uimage and tga cleaner to wipe out previous boot images left by other roms.
Many people just wipe the cache and dalvik caches before flashing, and don't do the factory reset. I always do, because the roms seem to have less issues if I do the factory reset.
I've had a couple of instances in more than one rom where the lock screen doesn't respond (touch screen doesn't work) and I have to reboot, so I just disable the lock screen all together.
Gallery is currently working on my install of cherrykang, but I prefer Quickpic from the market, and usually install it right away.
I believe the boot option issue is because it uses the standard CM kernel, so that's what it boots up. If you flash the Bricked kernel, and entry will appear for that, even though you're using the CherryKang.
I too was getting the problem where it became unresponsive. What seemed to mostly work was setting the minimum clock up to 384mhz. You can use SetCPU from the market, or CPU Master (free in the market -- that's what i used). I had some problems again last night, but overall it seemed to help. His latest version did set the min clock speed to 200-something.
Thanks for all the tips guys. Still running strong with no lockups after going back to the original Alpha2.
I actually tried setting the min CPU higher prior to going back to [email protected] but that didn't work either. I still have my kids TP to install CM9 on so I might try CherryKang on that.
After previously flashing NEAK kernel 2.0.5x, today I've flashed the Dark Knight kernel on my ICS 4.0.3 SGS2. I did a cache clear in CWM. After rebooting the phone my touch key light is always on, no matter what settings I choosed for touch key's light duration.
I flashed the NEAK kernel 2.0.5x again - a message with "Moving init.d folder to init.d-old" was displayed while flashing.
After reboot the touchkeys are functioning properly.
But I want the dark knight kernel, not the unstable NEAK - yeah, NEAK kernel is turning the phone unstable in many applications if you dont buy his app to properly set voltages. I dont want to play with Neak Configurator PRO. I frankly suspected this kernel to screw with touchkey light settings. Now the touch keys light work properly only with NEAK. Please correct me if I'm wrong. Any solutions to have touchkey lights functioning properly with any kernel?
Clearing cache
Probably obvious solution, but I'll give it a try -
Tried clearing cache partition / Dalvic cache after flashing kernel?
Perhaps the installation ****s it up, but clearing cache should in theory fix it
Nope. I already mentioned I cleared cache-and yeah, dalvik too. So I'm waiting for solutions. For now I'm using the new unstable neak kernel 2.0.6x...
one thing I hated on ics is the back light keys settting,it was always on or wouldn't turn off, on flux kernel you can turn them off in xtweaker
I have asked a few times on the forum if this could be related to the baseband of my device. Basically what happens is in call, he proximity sensor seems to cause the touchscreen to go haywire. I receive what amounts to phantom button presses. Basically voiding the functionality of the proximity sensor to begin with, the calls get put on hold, muted, dropped or whatever. A new symptom has now appeared, the dreaded black screen bug. When a call gets dropped, screen goes black and nothing but a battery pull solves this. Contacts are suddenly missing and I need to resync to get them back
I have tried many different roms, every single kernel. The only solution I personally can think of, is disabling the proximity sensor altogether. Can anyone tell me which line in the build.prop would disable this?
Its my everyday phone, so this is rather urgent, any help would be appreciated
You need to add either of these 2 lines (not sure which, or if it matters):
gsm.proximity.enable=false
gsm.proximity.enable=0
Oh, and apparently MIUI ROMs have that option in the settings.
I can spend 20 min to try solving this or just give you a clue
Try this:
-install ROM Manager and install the custom recovery for your phone if you already haven't got one
-go into recovery, wipe dalvik cache and cache, and most importantly WIPE DATA...
Now flash the custom rom and wait for it to boot...
Wiping data should delete everything from the old rom, so incompatible data when sw roms will be erased...
Backup your sd apps, contacts trough google servers - do not forget...
Sent from my LG-P500, GingerSnap 2.3 using xda premium !
Left4DeadMW said:
I can spend 20 min to try solving this or just give you a clue
Try this:
-install ROM Manager and install the custom recovery for your phone if you already haven't got one
-go into recovery, wipe dalvik cache and cache, and most importantly WIPE DATA...
Now flash the custom rom and wait for it to boot...
Wiping data should delete everything from the old rom, so incompatible data when sw roms will be erased...
Backup your sd apps, contacts trough google servers - do not forget...
Sent from my LG-P500, GingerSnap 2.3 using xda premium !
Click to expand...
Click to collapse
I usually mount and format /system when i do flash a new rom. Thanks for your reply, but as I stated before, this happens on every rom I have flashed before