Database Develop

[Q] Torch problem

I have been having some issues with the torch/flashlight LED programs recently. I didn't used to have problems and prior to this when I used the HTC torch it had the same problem. When I used older versions of MIUI I didn't have this problem with flashlight apps that I had. But now with the most recent versions (since December or so I think when they added the torch button in the notification bar) I am having the problem again.
The problem when using a flashlight app (or the button in the notification bar) the light will turn on for about a second and then turn off. It will still show it off in the app or on the notification bar. If it does not do this it does one of 2 other things. It turns on and then after one second becomes brighter and then after about 1 more second turns off. On rare occasions in an app I can turn it on and it will stay on... but then when I try and turn it off there is usually a delay of a few seconds before it actually turns off. Then it is back to turning on for a second then off.
I had seen this same problem when I used the HTC Torch previously but it went away when using different ROMs and such so it makes me believe it is some kind of software problem. Seeing that the LED does seem to work and if I use the camera it seems to actually work properly with the program I am pretty sure there is nothing actually wrong with the hardware. Has anyone else seen this problem or know what could be causing it? Is there some way or some test program I could use to find what exactly is causing the problem? If someone has had this issue before... do they know how to fix it?
EDIT: I tried manually turning on the flashlight via "echo 1 > /sys/devices/platform/flashlight.0/leds/flashlight/brightness" and it turns the light on but then after about a second gets brighter then after another second turns off. When I did a "cat /sys/devices/platform/flashlight.0/leds/flashlight/brightness" it seems something changed it from the "1" which I wrote to the file to "127". Also, when I tried to "echo 0" to the file... the change did not stay. After doing the echo and then trying to cat the file it was still "127". I then tried to the torch app in the notification bar to turn it on and then off. After I turned it off via the application, I check the file and it was then set back to 0.
EDIT: I have witnessed the issue on 3 seperate Nexus One phones... surely someone else has had the same problem and possibly come up wit a solution.

you have to be careful with the flashlight apps esp with the high brightness setting. the LED is not designed to be on constantly on the nexus one and i have heard of people burning out their LED's from leaving it on too long both in normal and high brightness modes.
i have found out while using mine esp in high brightness if its left on too long it will overheat it and flicker. ever sense i seen mine do that i never use high brightness in fear of burning it out and when i use it in normal mode i try to keep its use as short as possible and i have not had it shut off on me sense. if yours is shutting off in normal mode then i'm afraid you may have already damaged it too much and that is why its turning itself off. thats my opinion anyways.
(if roms matter, i've always ran CM6 and now currently have been running CM7 nightlies and RC's

Frito11 said:
you have to be careful with the flashlight apps esp with the high brightness setting. the LED is not designed to be on constantly on the nexus one and i have heard of people burning out their LED's from leaving it on too long both in normal and high brightness modes.
i have found out while using mine esp in high brightness if its left on too long it will overheat it and flicker. ever sense i seen mine do that i never use high brightness in fear of burning it out and when i use it in normal mode i try to keep its use as short as possible and i have not had it shut off on me sense. if yours is shutting off in normal mode then i'm afraid you may have already damaged it too much and that is why its turning itself off. thats my opinion anyways.
(if roms matter, i've always ran CM6 and now currently have been running CM7 nightlies and RC's
Click to expand...
Click to collapse
Well... I would expect... if the LED was "burned out" then it shouldn't turn on at all. The simple fact that it turns on at all means the LED isn't burnt out. Also, I would suspect that to be the case if I had not witnessed it happen on a brand new Nexus One (Old one of a friends was replaced because it was stolen). Her's had to go in for repair (turns out a cable inside the phone going to the camera was loose) and I had reverted it back to an original ROM. Once it was reverted the LED didn't have problem. Another thing that indicates to me that it is a software problem is I have seen the exact same thing before on previous versions... and it went away when changing to other ROMs. Tonight I am thinking I will wipe and flash CM7 and test it with a light app and make sure... if that has the same symptom I will flash to a shipped ROM and test it. I am pretty sure it is a software issue though. I just don't know... what... is causing the problem.
EDIT: I also forgot to mention... when it was working properly... I never witnessed it overheat and flicker though I never had it on for long periods of time. One last thing, I only saw the symptoms after a flash to a new version. When it was working properly it was always working properly. When it was acting like this on a ROM it always acted like this.
UPDATE: I did flash to CM7 nightly and the torch app works perfectly as do other apps on the market. After being back on CM7 and with the advent of the theming engine for it... I think I may just end up moving back to CM for daily use. I would like to know if anyone else has run into this issue still and/or has a solution just in case I run into the same issue later. For now I think I will just chalk it up as a kernel/ROM problem... though it doesn't explain why others didn't have the same issue =/.

Screen turning on randomly but...

So here is the thing my screen is turning on randomly, but i've noticed 2 things
1 - When the phone is charging the screen does not turn on
2 - when i'm downloading anything the screen does not turn on too.
So my question is, is there a way to fool my system pretending that i'm downloading something that never ends or something like that? the battery comsumption is making me crazy.

whyzack_br said:
So here is the thing my screen is turning on randomly, but i've noticed 2 things
1 - When the phone is charging the screen does not turn on
2 - when i'm downloading anything the screen does not turn on too.
So my question is, is there a way to fool my system pretenfing that i'm downloading something that never ends or something like that? the battery comsumption is making me crazy.
Click to expand...
Click to collapse
You probably have some app that is making a mess. Do you use some lockscreen or notification app? Or something similar to those.

shut_down said:
You probably have some app that is making a mess. Do you use some lockscreen or notification app? Or something similar to those.
Click to expand...
Click to collapse
I don't think so, I Just applied the Cyanogen with Gapps, nothing more, and wiped everything but the problem always come back. /=

This might be a hardware issue. I faced a similar problem a few months back. I fixed it by cleaning my phone's micro USB port and the earphone jack.
In my case, it was caused because of build up of dirt.. my phone often "assumed" that I plugged in my USB cable and/or my earphone, that's why its display would turn on randomly.

[Q] [CM] phone / audio issues in recent nightly?

Folks;
not sure where to put this - apologies if this is the wrong forum: Using CM11 nightlies (downloaded via CyanDelta) on my p880, I update to the recent builds fairly often. With the last two or three nightlies, I experience repeated audio issues while doing outgoing or picking incoming calls: By then, it seems the phone audio is muted or not working, I am not able to hear anything, but obviously the "other end" does hear what I say. I don't get no dialtone then, either, even though the call obviously is being established. In some situations, trying this two or three times helps. Sometimes rebooting the device helps. It's not generally there but a bit annoying. Is this a known problem? Anything I can do about this? In cm-11-20140920-NIGHTLY-p880, this problem(?) is still there.
TIA and all the best,
Kristian

kr428 said:
Folks;
not sure where to put this - apologies if this is the wrong forum: Using CM11 nightlies (downloaded via CyanDelta) on my p880, I update to the recent builds fairly often. With the last two or three nightlies, I experience repeated audio issues while doing outgoing or picking incoming calls: By then, it seems the phone audio is muted or not working, I am not able to hear anything, but obviously the "other end" does hear what I say. I don't get no dialtone then, either, even though the call obviously is being established. In some situations, trying this two or three times helps. Sometimes rebooting the device helps. It's not generally there but a bit annoying. Is this a known problem? Anything I can do about this? In cm-11-20140920-NIGHTLY-p880, this problem(?) is still there.
TIA and all the best,
Kristian
Click to expand...
Click to collapse
if you check official cm11 thread, you will see that the issue is recognised and is being worked on.
other than that, you can install 23.9. nightly, or wait till it's fixed.
cheers.

Thanks a bunch for your reply!

Phone randomly auto-mutes itself, can't increase volume [video inside]

Hey guys,
I have a weird issue with my Moto X 2014 (stock Lollipop, no root or anything), and I can't find anything helpful around the web.
I have a video of the issue - I can't post the link as I don't have enough messages, but go to vid.me and add this code to the URL: /tMXf
Basically every few days, I find the phone is on vibrate. The volume rocker is suddenly all the way down, even though it should be maxed out, and I can't physically turn it up as you can see in the video. Even in audio settings, the ringer options is greyed out.
Android's quiet hours setting is NOT active. I have Moto Assist set to kick in at night time, but this happens randomly during the day, plus I tried removing it but nothing changes. It's not something to do with calendar events silencing the phone either, as Moto Assist only has scenarios for driving and the aforementioned night time.
Anyone knows what could be happening here? Thanks, much appreciated.

That IS strange... Have you tried rebooting your phone?

cole_15 said:
That IS strange... Have you tried rebooting your phone?
Click to expand...
Click to collapse
Thanks for the reply, man... yes, of course I tried that, but it's definitely not a temporary glitch. It happens again and again, every few days. A reboot does fix the issue when it occurs (in fact, it's the only way to get sound back), but only until the next time.

Volume drops randomly using Google Music (Bluetooth / Headset)

Hello there, I have a frustration with my Nexus 6 running 6.0.1
While there is similar probs around, none seem to explain mine.
When using Google Music on Bluetooth/Headset I get normal operation and then randomly (sometimes immediately, sometimes up to about 5 minutes) the volume drops down. The Volume slider still shows 100% volume.
I thought at first it was the ear-saftey thing we used to have where it does this, but then allows you to change it back to full volume. But I didn't get any message around that or cannot find a way to override it.
Then I thought it was another system process stealing focus and the phone getting confused, eg dropping volume for a notification and then just not returning it.
Tried rotating phone to see if it was a portrait/landscape bug
Everytime. I restart the phone, it's fine again before the random volume drop occurs 1 sec-5 mins after playing a song. Once it does it, it gets stuck that way.
I've lived with it for a long time but it's doing my head in now so hopefully someone can help it advise?
Not even sure if a factory reset will fix.
Cheers

Jansy said:
Hello there, I have a frustration with my Nexus 6 running 6.0.1
While there is similar probs around, none seem to explain mine.
When using Google Music on Bluetooth/Headset I get normal operation and then randomly (sometimes immediately, sometimes up to about 5 minutes) the volume drops down. The Volume slider still shows 100% volume.
I thought at first it was the ear-saftey thing we used to have where it does this, but then allows you to change it back to full volume. But I didn't get any message around that or cannot find a way to override it.
Then I thought it was another system process stealing focus and the phone getting confused, eg dropping volume for a notification and then just not returning it.
Tried rotating phone to see if it was a portrait/landscape bug
Everytime. I restart the phone, it's fine again before the random volume drop occurs 1 sec-5 mins after playing a song. Once it does it, it gets stuck that way.
I've lived with it for a long time but it's doing my head in now so hopefully someone can help it advise?
Not even sure if a factory reset will fix.
Cheers
Click to expand...
Click to collapse
Try a factory reset. Ive had it fix many a strange bug before.

Jansy said:
Hello there, I have a frustration with my Nexus 6 running 6.0.1
While there is similar probs around, none seem to explain mine.
When using Google Music on Bluetooth/Headset I get normal operation and then randomly (sometimes immediately, sometimes up to about 5 minutes) the volume drops down. The Volume slider still shows 100% volume.
I thought at first it was the ear-saftey thing we used to have where it does this, but then allows you to change it back to full volume. But I didn't get any message around that or cannot find a way to override it.
Then I thought it was another system process stealing focus and the phone getting confused, eg dropping volume for a notification and then just not returning it.
Tried rotating phone to see if it was a portrait/landscape bug
Everytime. I restart the phone, it's fine again before the random volume drop occurs 1 sec-5 mins after playing a song. Once it does it, it gets stuck that way.
I've lived with it for a long time but it's doing my head in now so hopefully someone can help it advise?
Not even sure if a factory reset will fix.
Cheers
Click to expand...
Click to collapse
I've had the same problem, running N developer preview 1 listening with wired headphones. I've learned that I just kind of have to wait for it to pass, try force stopping play music, or restart the phone.
Are you streaming your music, or is it downloaded onto your device? I manually copy music onto my phone from my computer, and this is when I've got the issue, as I stream with Spotify fairly often and never have the problem. I've always thought it was just some bug reading all of these crazy 3rd party audio files in the storage.
Hasn't been much of a problem for me... Just jumped at the opportunity to share when I saw this thread. If it bothers you that much, try a full wipe of internal storage and reinstall everything. Cheers! Hope I helped.