[Q] bln and cm9 kernel - Fascinate Q&A, Help & Troubleshooting

I just updated from cm7 to cm9 and it's great. I used the latest SKankwich rom and the latest icy glitch kernel. However I had no bln which is important to me. I tried using version 3 of icy glitch as well as siriyah and the apps nstools, bln control, and extweaks in different combinations but nothing works.
Can someone tell me what to use and walk me through the process step by step? Maybe I'm not erasing the right stuff. I'm willing to start from stock. Thanks!

I read somewhere that I should be able to get the bln to work if I use an older version of icy glitch but I'm not sure which one to use.
Again, can someone walk me through this from stock? I can get to cwm but after that I'm not sure the proper order of applying things to get this to work.
The end goal is if I get a text or other notification, I don't want the soft keys to turn off at any point until I check that message. Whatever kernel gets me there on cm9

Icyglitch version 3? The latest version is B6.

Yeah it's up to 6. But on 6 I got no bln. Maybe I got bad info but I read someone say that the last time icy glitch was compatible with bln was version 3 or 4

Just throwing this out there too. No matter what I do, my screen won't rotate. All the right boxes are checked under display...

I don't have any of these issues.
As for rotation, you may need nova or apex. Look under launcher settings for rotation there.
Use nstools to set led notifications. They work perfectly here.
Did you wipe data prior to flashing the ics rom?
Sent from my SCH-I500 using xda premium

Yes I believe I wiped data. Did factory reset, wipe cache, wipe dalvik.
Looking at nstools, my led timeout was set to 0. I thought that meant it would never timeout. I just set it to 1800. Think that was the problem?
Also what is cmled?

Related

[MOD][4.1.2011] Fixed (shortened) touchkey backlights (Powerwashed ED05 8.31.2011)

The one thing I've hated about DJ05, DL09, and now our Froyo releases is that the timeouts on the capacitive touchkey backlights have gotten longer and longer. In DI01 it was a couple of seconds, in DJ05 it was the length of your screen timeout, and by EB01 and beyond it's now the length of your screen timeout AND reset every time you touch *anything*.
Well, I've finally gotten around to figuring out where the change was (setScreenOffTimeoutsLocked() in PowerManagerService.smali in services.jar) and modding it back. Now, as in DI01, the keys will only light up for a few seconds after you press one. I haven't reverted the recent change of regular screen touches resetting this time after the touchkeys have gone on, though: since the baseline is very short, this isn't a big issue.
Note that the version of services.jar on which this is based is from Super Clean 2.9.2. However, a diff seems to show that the only difference between adrynalyne's services.jar and the stock EB01 is the inclusion, in the former, of the battery notification/data throttling removal mods. So it *should* work with any deodexed EB01-based framework, though I've only tested on the self-customized SC292 I'm running.
The mod does *not* interfere with BLN.
UPDATE 4/28: I've removed the previous EC01/ED01 versions because they were turning on the lights a bit too often (screen press as well as button press). Instead, here are two fixed Edify-script versions for ED01.
Evil Fascination/stock ED01 folks should use shortlight-evil341, which basically just includes the light fix and the sbrissen mods. Community ROM folks should use shortlight-community12, which has a couple of other options unique to that framework.
The new files include a permissions fix, so just install the zip and reboot. (Those installing the original file -- SC292/EB01 and Amend only -- still need to manually mount /data and /dbdata and run the fix permissions script in CWM 2.5 after installation.) First boot will take a while.
UPDATE 5/17: From version 3.5 forward, Evil Fascination folks should use the community zip as well. Evil341 is still good for stock ROM users.
UPDATE 6/13: New version (shortlight-cROM2) uploaded for Community ROM 2.0. Edify only, like the 4/28 version.
UPDATE 8/31: New version for Powerwashed (ED05). Edify only.
To be honest I like it when the keys are lit up. Especially in the dark and you're trying to hit one of those buttons. But I do agree that they shouldn't be on after you lock the screen....
Syn Ack said:
To be honest I like it when the keys are lit up. Especially in the dark and you're trying to hit one of those buttons. But I do agree that they shouldn't be on after you lock the screen....
Click to expand...
Click to collapse
Do your keys really stay lit up after you lock the screen? What rom are you using these days?
I'm running Adyn's latest superclean (2.92) and jt's ec10 kernel (TW_kernel-0327-2) and haven't seen this issue. I'm wondering if there is a bug somewhere that is causing this issue with other people.
I don't have a problem with their time staying on..I do wish they weren't so bright..
Has anyone noticed that the in-call "buzz" is related to the soft-key lights being on? I haven't used a Touchwiz ROM in a while (including Superclean), but this is something I've noticed running other ROMs.
This fix might help with that.
Awesome!! Thanks, I can't stand the long backlight time. This is perfect!
DeezNotes said:
Has anyone noticed that the in-call "buzz" is related to the soft-key lights being on?
Click to expand...
Click to collapse
Yep.
It's funny, a bunch of people like the long lights -- and it's their complaints, I think, that made Samsung edit the behavior in later firmwares. But I'm also sure there are a bunch of people who don't, so now there's a choice.
I also think if the lights were as muted as they are on, say, a Captivate, things might be different.
I tried this out. If I wake up my phone the lights stay off but as soon as I press one they never go off until the phone goes to sleep again.
Sent from my Fascinate
Superclean 2.9.1
EB16 voodoo kernel
EA28 radio
No current theme
s44 said:
I also think if the lights were as muted as they are on, say, a Captivate, things might be different.
Click to expand...
Click to collapse
Yea, the lights help locate the buttons in the dark, but they are so bright that they almost overpower the screen. As handy as they are, I'd rather do without them all together personally. But this is a great compromise.
scarfman4 said:
I tried this out. If I wake up my phone the lights stay off but as soon as I press one they never go off until the phone goes to sleep again.
Click to expand...
Click to collapse
You sure it flashed? This is basically the standard behavior.
s44 said:
You sure it flashed? This is basically the standard behavior.
Click to expand...
Click to collapse
I believe so. I booted into CWM, wiped data and cache twice, flashed it and rebooted.
Sent from my Fascinate
Superclean 2.9.1
EB16 voodoo kernel
EA28 radio
No current theme
Yikes, you wiped data!
Don't do that, this is a tiny framework change. (I think I'll add that to the OP.)
Not sure what could be off -- I assume the framework didn't change between 2.9.1 and 2.9.2. You used Red clockwork and not Orange, right? Maybe try reflashing...
(Since you're also in the SC thread, note that flashing any ROM will undo this change.)
Thanks! I have been looking for this!
Superclean 2.9.2
EC10 voodoo
s44 said:
Don't do that, this is a tiny framework change.
Click to expand...
Click to collapse
It worked perfectly for me, and I didn't wipe anything - data, cache or dalvic.
thank you very much s44, I've always wanted this!
This by far is the best mod yet. Not to dis the other great developers but I really hate that the backlights are brighter than my screen and always on.
Sent from my SCH-I500 using XDA App
s44 said:
Yikes, you wiped data!
Don't do that, this is a tiny framework change. (I think I'll add that to the OP.)
Not sure what could be off -- I assume the framework didn't change between 2.9.1 and 2.9.2. You used Red clockwork and not Orange, right? Maybe try reflashing...
(Since you're also in the SC thread, note that flashing any ROM will undo this change.)
Click to expand...
Click to collapse
My mistake, I didn't wipe data, only cache and dalvik (that's what I get for typing in a hurry).
I have Red clockwork, the latest from 3/30. I'll try again after my battery finishes charging.
Bizarrely, the lights seem to revert to "always on after touch" mode while the screen is in power-low super dim mode. Not sure if or how I can do anything about this.
s44 said:
Bizarrely, the lights seem to revert to "always on after touch" mode while the screen is in power-low super dim mode. Not sure if or how I can do anything about this.
Click to expand...
Click to collapse
I bet that was why it wasn't working for me. I was only at about 5% battery when I tried this.
Works perfectly for me.
Nice job.
Also just a heads up for any noob. My first reboot after took extra long but went fine. No problems.
Sent through mental telepathy

[Q] Rick's MIUI (1.12.9) and LED Notification

I decided "hey, I should probably update my MIUI" so I wiped data / cache / dalvik a million times, and installed Ricks MIUI.
I have no LED notifications for texts or whatever it may be, however before I upgraded I did. I see that in the new menu there is no "Trackball" or "LED notification" in the system settings anymore. I downloaded BLN to enable it and still nothing.
I just want my led to light up when I have a text or whatever.
Thanks!
Sometimes upgrading turns out worse than before. What version did you upgrade from, and is Rick's version different than the official releases over at MIUI?
I have rick's 12.9 MIUI and I am using BLN Control Pro and it is working.
uzumaki82 said:
I have rick's 12.9 MIUI and I am using BLN Control Pro and it is working.
Click to expand...
Click to collapse
Hm, I've tried BLN control (free) and blinky from the market and had mixed results. Blinky worked well, and allowed more control over the notification, but seemed to have a battery drain issue. BLN control only worked for one notification and stopped working after that.. I'm assuming you're running the glitch kernel that Rick's MIUI comes with?
I'm using Glitch V13 with Ricks MIUI, so yes. Before I had a JT kernal from 11/09 or something like that which worked perfectly
I think it might be kernel related then, I think I remember seeing sixstringsg say that there were going to be some changes to BLN in the next glitch release that should fix things. I suppose if you really need it, use that jt kernel. Personally, I couldn't deal with the color and lack of ability to change it with voodoo control on that kernel.
Glitch13 has the BLN notification bug, and CM7.1 has the in-call volume bug. Pick your poison.

[Q] Photon CM9 Beta - Capacitive buttons (Menu, Home, Back, Search) not lighting up?!

I'm running the CM9 beta 0.2.0 by jokersax11 ([Ics] cm9 beta with camera CDMA/GSM/UMTS/HSDPA/WCDMA/roaming 2/22/12) and my capacitive touch buttons at the bottom of the screen*(Menu, Home, Back and Search) are not lighting up at all! I can't figure it out at all and I really need these buttons to light up, due to my recent switch from the LG Optimus S, and before that I had an AT&T HTC Inspire 4g (which have the home and menu buttons reversed). I use my phone alot at night and I desperately need to get this fixed! Is there something in the CM9 settings I'm overlooking? Or is there an app or mod that I could use to get control of them and get them working again? PLEASE HELP! I WOULD REALLY APPRECIATE ANY ADVICE OR ANY INFO ON HOW TO GET THESE BUTTONS TO LIGHT UP AGAIN! This is really frustrating!
Click the link below for the answer ...
http://forum.xda-developers.com/showthread.php?t=1526546
EDIT - Well that was fun. If you haven't figured it out, the link above goes to the other thread you started, with the same title, and the same body, in the same forum .... You should not create duplicate threads. For future reference best practice is create 1 thread and wait a minimum of 24 hours between bumps.
With that out of the way my actual advice is as follows, i dont believe the capacitive buttons are an issue with jokers CM build although i dont personally use it. This would indicate the answer lies in a) something you did b) something you didnt do c) something you installed
1. You can eliminate a and b without losing any info by going into your custom recovery and wiping cache and dalvik cache then doing a dirty flash on the rom (dirty flash = don't wipe data/factory). In this case there would be no reason to reflash gapps.
2. If that doesn't work, do a full wipe (data factory/system/dalvik) and reflash the ROM, then gapps. Be slow to in stall your apps and test the capicitive buttons frequently to ensure you haven't done anything to break them
Set the phone's brightness to Automatic.. Fixed..
People are so over dramatic sometimes lol.
Sent from my MB855 using Tapatalk
Thanks, that pointed me in the right direction. My auto brightness isn't working. I'm gonna do a "dirty flash" and see if that helps. Oh and btw,the second post was an accident and you can't delete your own thread.So, sorry about that.
eszumlas1985 said:
Thanks, that pointed me in the right direction. My auto brightness isn't working. I'm gonna do a "dirty flash" and see if that helps. Oh and btw,the second post was an accident and you can't delete your own thread.So, sorry about that.
Click to expand...
Click to collapse
Please come back and update the thread on if it works or not. Others may experience the same issue in the future and this thread could assist them.
Cheers!
i just now notices mine dont light up but o well my thumb pretty much know ware to push
Well, it's fixed. Don't know what the heck was going on but reflashed my CM9 & Google apps and voila my automatic brightness switch in settings started working again. No more problems and capacitive buttons work fine. Strange but at least it's fixed
Sent from my MB855 using xda premium
And sorry to anyone that needed a fix to this. I was involved in the tornado that hit Branson, Missouri and was unable to keep phone charged due to the power outage that lasted over a week, and had bigger things to worry about at the time, like getting shelter and food. But everything is ok now and hope this thread helps anyone that has this problem. Check to see if your automtic brightness switch is working under settings (mine wasn't working) So if it isn't working just reboot into recovery, wipe dalvik cache & /cache, and reflash your rom and gapps, then check in your settings to see if your automatic brightness is now working. If so your problem should be fixed and your capcitive buttons should now light up. It worked for me, hopefully it will work for you.
Sent from my MB855 using xda premium
eszumlas1985 said:
Check to see if your automtic brightness switch is working under settings (mine wasn't working) So if it isn't working just reboot into recovery, wipe dalvik cache & /cache, and reflash your rom and gapps, then check in your settings to see if your automatic brightness is now working. If so your problem should be fixed and your capcitive buttons should now light up. It worked for me, hopefully it will work for you.
Click to expand...
Click to collapse
Thanks man i just had to set the screen brightness to automatic and reboot once. It worked like a charm

Keyboard issues with ICS

So I recently took the leap and took my rooted S2 and put various ROMS on it. For the life of me I cannot figure out the keyboard lag. It starts fine, and, then at times it will slow down so much it's almost impossible to type. It happens on CM9, Ultimatium, SHOstock is the worst and i tried Foxhound, love it, but same issue. And it's not the screen, it's recognizing the buttons pushed from what I can tell, but the device just does not register every keystroke.
I have read and read and just cant find a solution.
Any ideas?
I have only noticed that my t or h key doesnt always get registered, otherwise its fine.
Sent from my SGH-I777 using Tapatalk 2
Have you tried fluxxi kernel? It has extensive touch settings so people with screen protectors (maybe you have one?) can really tweak the sensitivity. There's also a "gingerbread" preset that people, incl. myself have been happy with. Also, have you tried changing the touch sensitivity setting on CM9 (and some other ROMs)? It's in System settings > Advanced (or Device Settings) IIRC.
Siyah kernel also has adjustable sensitivity via the ExTweaks app.
stone_ship said:
Have you tried fluxxi kernel? It has extensive touch settings so people with screen protectors (maybe you have one?) can really tweak the sensitivity. There's also a "gingerbread" preset that people, incl. myself have been happy with. Also, have you tried changing the touch sensitivity setting on CM9 (and some other ROMs)? It's in System settings > Advanced (or Device Settings) IIRC.
Siyah kernel also has adjustable sensitivity via the ExTweaks app.
Click to expand...
Click to collapse
Thank you!
I got the Fluxxi kernel. Any chance you might be able to tell me where the "gingerbread" preset is?
I'm going to play around with CM9 again, I'm using AOKP right now, and it seems to be ok.
Did you install the xxTweaker app from here: http://forum.xda-developers.com/showpost.php?p=26350589&postcount=1 ? All of the configurable settings are controlled by xxTweaker.
If not, do that first, and then open the app. You'll find it under "Display".

[Q&A] [ROM][4.4.4][CyanideMod]

Q&A for [ROM][4.4.4][CyanideMod]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4][CyanideMod]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
CyanideMod V2 volume
I am currently having a problem. The volume buttons on the phone are not working for Ringtone and Notification. They will only adjust the volume of the music, games & other Media. I have it set in Sound/Volumes, but it is not working. Also, I am not able to adjust the volumes in the profiles, they just stay set at defaults.
ke7vng said:
I am currently having a problem. The volume buttons on the phone are not working for Ringtone and Notification. They will only adjust the volume of the music, games & other Media. I have it set in Sound/Volumes, but it is not working. Also, I am not able to adjust the volumes in the profiles, they just stay set at defaults.
Click to expand...
Click to collapse
After media volume shows up click to make the volume extendable and then adjust the notification volume. I just noticed this so I'll be looking before I start working on it again
Sent from my SGH-I317 using XDA Premium 4 mobile app
In v3, the classic (stock) recent apps panel seems to crash systemui. Slim recents works OK.
radoo7701 said:
In v3, the classic (stock) recent apps panel seems to crash systemui. Slim recents works OK.
Click to expand...
Click to collapse
Will you check if omniswitch can be set as default recent app still? I fixed the stock recent issue before I uploaded but if omniswitch can still be selected as default then I uploaded the unfixed version. I'll upload V3.5 soon. Working on a kernel/recovery mod at the current time
Sent from my SGH-I777 using XDA Premium 4 mobile app
Yes I can set omniswitch as the default for recents. Just to be sure I did a clean install and still have the issue with stock recents.
radoo7701 said:
Yes I can set omniswitch as the default for recents. Just to be sure I did a clean install and still have the issue with stock recents.
Click to expand...
Click to collapse
Well poop lol. That's actually good tho. Like I said I did already fix this, I just apparently uploaded the unfixed version. Oops. I can run a build fairly quickly as a still have the s2 build cached but I'm using build environment to build and make some recovery changes at the moment
FUSE support?
Hi,
I found this ROM last night and flashed it, and want to say thanks. I was having trouble with other ROMs aborting installation, but this one installed without a hitch. Everything works as it should, and way better than my old CM9 ROM. This was completely painless.
Question: Does the kernel have FUSE support?
I'm trying to get SSHFS working; I can ssh into the target server via terminal emulator, but SSHFS will not mount. It appears to mount but doesn't really. When I click unmount, It complains:
fusermount: error getting lock: Invalid argument
I know this isn't the place to get help with SSHFS, but it will only work if the kernel has FUSE support, so that enters into your bailiwick.
Oh, and a possible issue: It seems I'm not getting as strong a network signal now as I did before flashing this ROM. Is it even possible this could be due to a software issue?
Thanks again for the great work. You are awesome!
Stock recent panel is not working. Could just be my dirty flash. Thank you for your hard work. This ROM is amazing.
Sent from my SGH-I777 using XDA Free mobile app
modem not working
I've been running a CyanogenMod-9 version for quite awhile, until about a week ago when I decided to upgrade. I tried some of the CM-10 versions, and installation aborted midway, leaving me stuck with a non-working phone for a few days.
I flashed CyanideMod-V3-S2 a few days ago, and was very pleased to see it install effortlessly. It looks great, and everything seems to be working, EXCEPT the modem.
The network signal is very weak. I can make calls if I am in town, or on top of a high hill, but often I get no signal at all. I do live in a rural area, but it has never been this weak. Even when I get full bars, they are always white, never blue as they should be. I have no access to data.
I don't know much about AT&T's network; frequencies, etc., but my semi-educated guess is that I'm not picking up all the frequencies I should.
In my settings:
Mobile network is on.
Data is enabled
Preferred network type is set to 3G
Network operators is set to ATT
Access Point Names was set to ATT LTE. I stopped in today at an ATT store, and the rep's phone was set to "ATT Phone" so I experimentally changed to that and rebooted, but saw no change. The settings in the 7 available choices match the setting in other working phones in our household, so I don't think this is a settings problem.
I found the "Consolidated Modem" thread on this site, which lists 13 choices for modems. My phone reports a "Baseband version of i777UCKK6, which is one of the choices in that page, which I assume was installed with the ROM. I don't know if the modem is my problem, and wouldn't have a clue which of these to try. Are they installed through recovery in the same way as the ROM and gapps?
I love this ROM, but the phone is nearly unusable as it is. Has anyone else had this problem, or does anyone have any pointers?
Thanks so much for all your hard work.
Newest modern is UCMD8. Rom wouldn't affect the modem other then the usual kk signal issues
Thanks for the update. Amazing!! Stalk recents still does not work (maybe because of dirty flash, please confirm with other users). Also the power menu-reboot menu does not have reboot to recovery. Reboot to recovery is available in stweaks. But it would be nice to have again in power menu.
dagwoodmash said:
Thanks for the update. Amazing!! Stalk recents still does not work (maybe because of dirty flash, please confirm with other users). Also the power menu-reboot menu does not have reboot to recovery. Reboot to recovery is available in stweaks. But it would be nice to have again in power menu.
Click to expand...
Click to collapse
If you uncheck and recheck Advanced Boot in Developer Options you should get the boot to recovery to show back up. It still shows for me after update.
I am getting FC on Google play services after update and cannot access my account. Would reflashing gapps fix that?
radoo7701 said:
If you uncheck and recheck Advanced Boot in Developer Options you should get the boot to recovery to show back up. It still shows for me after update.
I am getting FC on Google play services after update and cannot access my account. Would reflashing gapps fix that?
Click to expand...
Click to collapse
Thanks for helping him. Yes just reflash gapps. Not sure why it's like that but for some reason it is. I don't need it while testing but then do later on. Strange
Awesome build (V4). Coming from CM of a few months ago, everything is real snappy (also due to flashing afresh).
A few bugs so far:
1) Tapping on notifications in the pull-down drawer doesn't seem to link to anything (the animation works, but the associated action doesn't fire). Additionally, the Halo/Quick Settings buttons at the top of the notification drawer seem to get pushed off the edge of the screen (Would be nice if the Halo button could be removed/Halo disabled).
2) Lock screen slider shortcuts cover up cLock
3) Volume buttons (including from home screen) control system volume, not ringer/notification volume.
Amazing work, in any case! Some day I'll need to get a new phone.
b
Gonna be starting from scratch here.. can you give me a quick runthrough.. I have a bricked i777 that I will be starting with.. starting with an Odin tar(stock rooted 4.1.2?) to get it back up and running. It' s been years but I'll figure it out. just need a simple outline like which stock Odin tar.. then which android versions and recovery to install to get to your 4.4.4 .
thanks
tri0xinn said:
Gonna be starting from scratch here.. can you give me a quick runthrough.. I have a bricked i777 that I will be starting with.. starting with an Odin tar(stock rooted 4.1.2?) to get it back up and running. It' s been years but I'll figure it out. just need a simple outline like which stock Odin tar.. then which android versions and recovery to install to get to your 4.4.4 .
thanks
Click to expand...
Click to collapse
I'm driving but maybe @creepyncrawly could point you there. Flash odin rom, flash odin custom kernel for recovery, make a backup, do a factory reset and wipe system, flash shift kernel, tenor to recovery abs flash rom and gapps. Use V3 of this rom. It's all here. You could probably fine before he sees this. I'm voice typing or I'd help you out
Sent from my SGH-I317 using XDA Premium 4 mobile app
tri0xinn said:
...which stock Odin tar.. then which android versions and recovery to install to get to your 4.4.4 .
thanks
Click to expand...
Click to collapse
Use latest stock 4.1.2, I777UCMD8 which you can get from the download repository (link in my signature) Also some other stuff there if you need it, but not the recovery and firmware you need.
thanks a ton, got everything back to square one with that I777UCMD8 tar, easy after that and now running cyanidemod and it's running as slick as my gs5.. at least it seems to be. thanks again:good:
After a couple days of use its still running super slick.. only issue thus far is pretty bad battery life.. any settings i can adjust to improve things? Or another kernel maybe.. anyone else have issues with battery life?

Categories

Resources