Related
hi,
i want to disable the vibration when unlock my phone in Cm7 nightly. i did search the forum but cannot get an answer. just know i have to do something with "framework.jar", can anyone help?
thanks,
Cospo
Sent from my Nexus One using Tapatalk
I seriously don't think Google knows this issue exists within stock ICS, which is kinda were because this happens to me nearly every time I lock my Nexus S.
Sent from my Xoom
Have you installed the Voodoo app ?
Yea you can try by going to display and turning the brightness to 26. I remember doing that on the miui roms bc.of green flash on the on/off.animations
sent from an HTC sensation on CM7 alpha #10
If you use the lock animation you will get rid of it
Sent from my Nexus S using XDA App
Install a new kernel, like Matr1x Kernel.
Or use voodoo plus app.
Heeter
That sort of fixes it
turkobr said:
If you use the lock animation you will get rid of it
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
sent from an HTC sensation on CM7 alpha #10
Voodoo plus doesn't fix Its a voodoo color driver issue with ICS
guess Supercurio releasing new one soon
Sent from my Nexus S using xda premium
demo23019 said:
Voodoo plus doesn't fix
Its a voodoo color driver issue with ICS
guess Supercurio releasing new one soon
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
No matter what I do, the settings either give me a green screen flash or it flashes the clock screen vaguely, it is so weird.... does Matr1x rid me of this? I am using ICUP.
Sent from my Nexus S
Smokexz said:
No matter what I do, the settings either give me a green screen flash or it flashes the clock screen vaguely, it is so weird.... does Matr1x rid me of this? I am using ICUP.
Click to expand...
Click to collapse
Yes, the latest Matr1x kernel (14.5) has the green screen fix. I believe the Steve Garon kernel has it too.
Sent from my Nexus S using XDA App
Smokexz said:
I seriously don't think Google knows this issue exists within stock ICS, which is kinda were because this happens to me nearly every time I lock my Nexus S.
Sent from my Xoom
Click to expand...
Click to collapse
I have this problem also using the latest GlaDOS cfs 2.8 kernel, & the only way I can cure is to use voodoo gamma set to defaults which is lame really coz every time I reboot I have to reset it again!
After searching for a while i've found an app that can succesfully control the LED for notifications. Light flow and other led ctrl apps never worked for me but i've found one that works like a charm: https://play.google.com/store/apps/details?id=com.koo.lightmanager
I'm currently on stock rooted 4.2.2, i don't know this works for previous fw's.
The only problem is, it doesn't work in stamina. Adding the app to the exeption list in stamina mode doesn't work. Using the alternative mode in the app or making it a system app don't work either.
Does anyone have an idea on how to resolve this problem?
Yes,that's right...
It works,with 4.1.2,and I used it with my old X8 (GB),and with xperia mini (ICS)...
I think,too, that it's the best LED control app,ever!
Lightflow working fine for me.
Sent from my C2105 using xda app-developers app
Tidzsi said:
Lightflow working fine for me.
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
What rom? Are you using special settings in lightflow or something?
It worked for me with the 4.1. 2 and now with 4.2.2, both stock. You should set it in the accessibility after instal, and thats all. G mail is working strange in it, there are to much options.
Sent from my C2105 using xda app-developers app
Tidzsi said:
It worked for me with the 4.1. 2 and now with 4.2.2, both stock. You should set it in the accessibility after instal, and thats all. G mail is working strange in it, there are to much options.
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
Accessibility was always enabled, guess i'll have to give it a try again.
Try it, many people use it.
Xperia L locked Bl rooted, android 4.2.2
Tidzsi said:
Try it, many people use it.
Xperia L locked Bl rooted, android 4.2.2
Click to expand...
Click to collapse
Yesterday, i tried it again. But i keep facing a bug --' The notification LED now works, but without a new notification, my LED blinks(white) when i turn off my screen. Rebooting and stuff doesn't help. i always seem to have these strange issues nobody else has --' but whatever, lightmanager works for me nevermind
Light manager doesn't seem to work, even after I reboot. Rooted 4.2.2 stock.
Edit: On the other hand light flow works
Sent from my C2104 using XDA Premium 4 mobile app
Sorry, is a bug:|
Is the bluetooth stack in the kernel or the ROM? I'm running the latest AOKP nightly and I get no ID3 info over bluetooth, and my Pandora app won't connect to the Pandora app on my car stereo. So I'm thinking it's a stack issue. So, before I start flashing random kernels to try to fix it I thought I'd ask to see if that was even a viable option.
Thanks in advance!
Sent from my Nexus 5 using Tapatalk
Anyone have any input? I'm on a different kernel now and still same issue.
Sent from my Nexus 5 using Tapatalk
my95z34 said:
Anyone have any input? I'm on a different kernel now and still same issue.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Bluetooth, Wifi and Mobile radio are all in the baseband, neither the kernel, nor the ROM.
kangelov said:
Bluetooth, Wifi and Mobile radio are all in the baseband, neither the kernel, nor the ROM.
Click to expand...
Click to collapse
Correct, to an extent. I believe the stack is in the ROM or the kernel. Just like the jump from 4.2 to 4.3 brought many bluetooth features on the exact same hardware / baseband.
Sent from my Nexus 5 using Tapatalk
I don't know how much this helps but when I was on the s3, I was told the reason custom kernels couldn't boost bluetooth audio was because it was controlled by the radio itself
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Any other input?
Thanks!
Sent from my Nexus 5 using Tapatalk
It depends. On the nexus it should be in the ROM.
I say in the ROM but the Bluetooth stack should be a kernel module/binary.
On other devices kernel modifications required modified sets of modules to work with their kernels but I don't think this is an issue with the nexus line.
You will usually know if a kernel uses modified binaries because firstly it will be a flashable zip rather than a boot.img and secondly because they will usually include a revert zip for changing back to a default one.
Now I know this doesn't help you much but I can't comment certainties because I haven't got my n5 yet
Sent from my Nexus 4 using xda app-developers app
Anyone else having issues with swiftkey staying at default? I know there was an issue when you reboot the phone, the keyboard would reset but, it happens when the screen is off or the phone goes into deep sleep.
Was wondering if anyone knows of a fix??
Stock rooted ROM and kernel
Sent from my Nexus 5 using Tapatalk
asd87 said:
Anyone else having issues with swiftkey staying at default? I know there was an issue when you reboot the phone, the keyboard would reset but, it happens when the screen is off or the phone goes into deep sleep.
Was wondering if anyone knows of a fix??
Stock rooted ROM and kernel
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sorry cannot reproduce. Been using swift key every since i got the phone and not had any problems keeping it as a default, even after rebooting.
That happened to me on KK as well as JB. I simply disable the stock keyboard in Settings.
jlevy73 said:
Sorry cannot reproduce. Been using swift key every since i got the phone and not had any problems keeping it as a default, even after rebooting.
Click to expand...
Click to collapse
That's weird... You think GravityBox could be causing it? That's the only "modifications" I've made.
I've tried the official release and the new beta release and still have the same problems.
Sent from my Nexus 5 using Tapatalk
asd87 said:
That's weird... You think GravityBox could be causing it? That's the only "modifications" I've made.
I've tried the official release and the new beta release and still have the same problems.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It could be as I don't have that Mod installed.
Wakamatsu said:
That happened to me on KK as well as JB. I simply disable the stock keyboard in Settings.
Click to expand...
Click to collapse
They fixed it on JB but I'll try that and see what happens.
Sent from my Nexus 5 using Tapatalk