LED issues - myTouch 3G, Magic General

I was wondering if anyone has a fix for the LEDS. I am running the jacheroski v2.1 and it seems to be the best one as far as stability and quickness. I have been exploring the forum as to how to get the leds to work. I fixed the wifi issue and would like to fix the leds. Does anyone know. Thanks

Related

[Q] NexusHD2-ICS-4.0.3-CM9-SD V1.0 Indicator problem

I encountered a problem with my HD2 phone with the tytung'ROM NexusHD2-ICS-4.0.3-CM9-SD V1.0
when the Battery power`s less than 15%,the Indicator light is always ON until the battery runs out,so what should i do to solve this problem?
anyone else has the same problem too?
Thanks!
You can't. Use another ROM.
Notifications and brightness control are not working yet.

[Q] ColdfusionX 15/05 build black screen problem

Hi all,
I've recently installed the ICS ColdFusionX ROM tillals 15/05 build, on my Orange Sanfrancisco (ZTE Blade) (gen1 - TPT'd to gen2).
After some initial problems I now only have one problem blocking me from using this ROM as my daily...
When I go to make a call (and possibly also when someone calls me) the call is established but the phones screen goes black. The UI and buttons then effectively become disabled meaning I can't hangup the call, or exit without removing the battery :-(
This is a real shame as it otherwise seems to be an excellent ROM... I really can't believe how fast and smooth it is!
I've looked around, and can't see anyone else mention this issue (when establishing calls from the device itself). The few posts I've seen suggest recalibrating the proximity sensor and rebooting, but I've tried that and no luck :-( any ideas???
Thanks greatly.
Update
After re-installing and experiencing the same problem, I managed to resolve it simply by recalibrating the proximity sensor (and not reseting/rebooting).
this problem has been fixed try fixed try flashing the rom again

Tab 4 10.1 SM-T530NU Brightness Not Changing

I've just noticed that the brightness slider moves from end to end with no change in screen brightness.
Anyone got a fix?
Android 5.0.2
Yes, I have the same problem. Mine is weird though. Mine will sometimes get bright and match the setting, but a majority of the time it goes to the most dim level on the screen regardless of where the brightness level is set. I'm hoping that it is something that I can fix, but I don't know if people will say that it's a hardware issue. My Tab is rooted again after I reinstalled the stock firmware again to try and fix the problem. Hopefully someone can offer an insight to this problem. I'm wondering if taking it apart and heating up the processor with a heat gun would cause it to work. That worked as a temporary fix on an Apple computer.
I have the same problem after I rooted the tablet. The only solution I found is install the app Screen Filter.
Are you on a custom ROM?
Can you reproduce the issue with a stock ROM?
If not,its probably the custom ROM have bugs.
Or maybe sth else

Brightness dependent yellow tint and black lines on the screen

Hello,
I've been having this issue for the past few weeks, where my screen will turn yellow and display lines across the screen at medium brightness. At max and min brightness it works normally, but at intermediate brightness it displays varying degrees of this issue.
Have anyone encountered this issue before? What can be done about it?
The issue just suddenly showed up. I went to bed and it worked fine, I woke up and it was like this.
I do not have any warranty, so any repair would be done myself. Issue occurs in TWRP as well, independent of the OS.
Video of the issue: https://streamable.com/zrvqh
The issue has been resolved by switching kernel. I was previously on the S8 NX kernel, and now tried switching to Velocity kernel and the issue is gone.
Should be pointed out the new kernel is "flicker-free", while the other is not. Not sure if that matters, but it's a screen related change in the kernel at least.
In case anyone else comes here looking for a solution, try a kernel swap.
Edit: Nope, for some reason this works as a temporary fix but doesn't last. Issue comes back.
Make.Sense said:
The issue has been resolved by switching kernel. I was previously on the S8 NX kernel, and now tried switching to Velocity kernel and the issue is gone.
Should be pointed out the new kernel is "flicker-free", while the other is not. Not sure if that matters, but it's a screen related change in the kernel at least.
In case anyone else comes here looking for a solution, try a kernel swap.
Edit: Nope, for some reason this works as a temporary fix but doesn't last. Issue comes back.
Click to expand...
Click to collapse
any luck with this issue ? happened to me now

snow screen when waking ambient screen ?

that static screen(snow) you get when your tv isnt on a channel, i get that flashed right before the ambient display shows. anyone one else have this issue ?
Probably have screen on/off setting on CRT in settings. Are you on a custom rom? I don't see the setting in OOS anywhere.
got same issue here
I've noticed the same thing randomly happening. Doesn't happen all the time so can't see what might be causing it. I'm using full stock and there is no setting I can see.
vuway said:
that static screen(snow) you get when your tv isnt on a channel, i get that flashed right before the ambient display shows. anyone one else have this issue ?
Click to expand...
Click to collapse
I get that since when I got the device last year but after update it show very less like maybe once a month. No way to fix it tho
Yup, Same here! Happens randomly on different custom kernels.
It's a feature, not a bug
I've noticed that it seems to happen when the screen lights up for a notification too.
I would only get this when on Smurf Kernel. When I switch to EX or RZ, the issue goes away.
thank you everyone for your input, its nice to know its a common issue. maybe ill try ex kernal. im currently on smurf. or i might just leave ambient turned off. doesn't seem to have much advantage over the regular lock screen anyway
I got this problem too a few weeks ago after trying out some kernels. I fixed it by dirty flashing OOS into both slots. It's a small but very annoying issue.
All kernels that use Dynamic FSync have this issue. You must turn OFF Dynamic FSYNC in EX Kernel Manager

Categories

Resources