Database Info

Is there a fix to make the Touch Pro camera flash less useless?

I'm sure all of you know that the Touch Pro camera flash turns brighter during the actual taking of a picture. The problem is that the camera doesn't adjust the brightness accordingly! The brightness is adjusted during the preview but thats with the camera flash at a lower luminence.
Here are two examples of the lack of adjustment, in comparison to my Sony Ericsson W810 with its flash as well.
Touch Pro: http://www.mylilsite.net/images/compare/sdtpw8v3/tppaperflash1.jpg
W810: http://www.mylilsite.net/images/compare/sdtpw8v3/w8paperflash1.jpg
Touch Pro: http://www.mylilsite.net/images/compare/sdtpw8v3/tpheatsinkflash1.jpg
W810: http://www.mylilsite.net/images/compare/sdtpw8v3/w8heatsinkflash1.jpg
As you can see, the W810 (which also makes the flash brighter during the actual taking of the picture) is properly programmed to compensate for the change in brightness while the Touch Pro doesn't do anything. Whats the point of having the flash if it just ruins the picture?
Is there anything I can install or modify to get the Touch Pro camera to be smarter like the W810??

Bump!
How about disabling the flash from getting brighter during the actual taking of the picture?

You could always:
1) turn off flash in the camera app
2) run nueLight3, htorch, or another flashlight app and enable the "bright" flash
3) run the camera app (which should compensate for the brighter flash), and take the photo.

Sorry to say, i dont think so - well i havent found anything atleast. Had the TP for a year (just upgraded to the Leo a few weeks ago) and never found anything to make the camera take a decent pic (flash or not) in all that time. Sorry!

DaveLinger said:
You could always:
1) turn off flash in the camera app
2) run nueLight3, htorch, or another flashlight app and enable the "bright" flash
3) run the camera app (which should compensate for the brighter flash), and take the photo.
Click to expand...
Click to collapse
Hey, thats a good idea!
Unfortunately...
What I did #1:
1) Ran the Camera app and left the light turned off
2) Pressed Home button
3) Ran nueLight3 and turned on "High Beam"
4) Triggered ArkSwitch and selected Camera
5) Took this screenshot with Shake And Save:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6) I couldn't find nueLight3 running in ArkSwitch or Task Manager and couldn't even run the app again. I was only able to turn off the light by resetting the phone. I guess the error experienced by Camera crashed nueLight3 as well.
What I did #2:
1) Ran nueLight3 and turned on "High Beam"
2) Ran the Camera app (triggered by holding PTT button)
3) Took this screenshot with Shake And Save:
4) nueLight3 was still running this time.
Has your idea worked for you?
@Beeble, yeah I agree the camera itself also sucks (my SE W810's is much better), but when outside or just needing a quick picture.. I'd go with my phone. However, it better be able to take pictures properly with its own included hardware and features . So I want this flash issue fixed.

Are there any other ideas?

I've taped a piece of paper to the inside of the backplate over the 'flash' LED. It manages to diffuse it slightly, but I still get a 'bleed' of light from the direction of the flash.
I think having the ability to adjust the behaviour of the flash LED would be great... If the timing of it could be changed so it goes brighter just before the photo was taken, then dims for the actual shot, it would work similar to red-eye reduction in regular cameras.
Any luck in finding an app to help with this since your last post?

hate to say it but, theres no absoluetly no way you can fix how the flash reacts when taking a picture, HTC is not good at specializing in cameras unlike Sony, but the suggestion the guy above was saying is something i would try out, if it doesnt work out for you, theres no other alternative at this moment

Man, really wish some solution was found, hopefully someone finds one. I just had a bad experience using the flash, it was great to have, but that totally bites how it doesn't compensate for the extra flash at the end. Defeats the purpose of the flash. I got the same error trying with htorch.

[Q] No response from sensors until reboot.

My accelerometer and other various sensors stop responding randomly, making pretty much any app that requires them unusable, including games, anything with auto-rotate, the camera (photo spheres mostly) etc. All the sensors appear to fail at once and the only way to get them working again is a reboot. I'm stock, rooted, with franco kernel, and running Xposed with only gravitybox installed. I'm not sure exactly when this started so i'm not able to trace it to a particular app, but I don't think it would make much of a difference because I have tried restoring the system partition as well as removing Xposed and reverting to the stock kernel. I wasn't able to format /data and test because for some reason the nandroid backup failed when trying to back up the data partition. (not sure if this could be related...). Anyways I checked logcat and there doesn't seem to be anything helpful: there is no output at all when trying to auto-rotate etc. but I will continue troubleshooting... Does anyone know the best way to approach this or has had this happen before? This is weird and frustrating...
Here is a screenshot of Sensor Node from the play store after the sensors go dry...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Apparently proximity still works... yay?

Alias.TDP said:
My accelerometer and other various sensors stop responding randomly, making pretty much any app that requires them unusable, including games, anything with auto-rotate, the camera (photo spheres mostly) etc. All the sensors appear to fail at once and the only way to get them working again is a reboot. I'm stock, rooted, with franco kernel, and running Xposed with only gravitybox installed. I'm not sure exactly when this started so i'm not able to trace it to a particular app, but I don't think it would make much of a difference because I have tried restoring the system partition as well as removing Xposed and reverting to the stock kernel. I wasn't able to format /data and test because for some reason the nandroid backup failed when trying to back up the data partition. (not sure if this could be related...). Anyways I checked logcat and there doesn't seem to be anything helpful: there is no output at all when trying to auto-rotate etc. but I will continue troubleshooting... Does anyone know the best way to approach this or has had this happen before? This is weird and frustrating...
Here is a screenshot of Sensor Node from the play store after the sensors go dry...
Apparently proximity still works... yay?
Click to expand...
Click to collapse
If a reboot fixes it, then it's probably a software side problem. Do you have the latest CWM verson? Try using TWRP to backup.

I am on stock at the moment. I decided to try wiping /data manually and reinstalling a few apps at a time to see if I can recreate the problem
Sent from my Nexus 5 using Tapatalk

Alias.TDP said:
I am on stock at the moment. I decided to try wiping /data manually and reinstalling a few apps at a time to see if I can recreate the problem
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
As much of an effort as this is, it really is the best way to help identify the problem.

Do you use the barometer? It is a known bug that after some time the barometer and other sensors stop working.
Sent from my Nexus 5 using xda app-developers app

Yes I do have an app that constantly probes the barometer
Sent from my Nexus 5 using Tapatalk

Had the same problem using the app PressureNET. Uninstalled it and now everything is fine.
Sent from my Nexus 5 using Tapatalk

Same problem happened here around the time I installed some barometer reader. I will try to remember posting a follow up in about a week after just having deleted the app and rebooting.
Thanks so far for a possible candidate on what causes this and also thanks for starting a thread and mentioning the app used for verifying the sensor read outs.

After a clean wipe no problem until I re enabled my barometer widget...
Sent from my Nexus 5 using Tapatalk

[Q] Camera Error

Hi, someone have error on camera ? suddenly fails today, I rebooted it worked and now the error again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What is the error message, do you know?

I had the same thing.. The error I have is can't connect to camera.
Any help is appreciated.

I had the same problem in the last few days. Most of the times another try to open camera app helped. But one time I had to reboot.
Ok, let's collect some information. I am on
176.44.1.falcon_umts.Retail.en.de
And I had these problems after I updated to latest KitKat version (but could be a coincidence).
Which versions are you on?
Gesendet von meinem XT1032 mit Tapatalk

Try clearing cache on the camera app
Sent from my Nexus 7 using xda app-developers app

Hi, i uninstal the google goggles app and so far I had no more error

same camera Error
Mleunam said:
Hi, someone have error on camera ? suddenly fails today, I rebooted it worked and now the error again
Click to expand...
Click to collapse
Hi I do have same camera error.
Error is "Camera Error" or "Fail to initialise"
Also tried to clear cache and tried to start camera again but all fails.
After rebooting Camera works fine.. some one should help us out to solve this problem.
My moto g is also running with 4.4.2

Camera error
I recently got the same error. It occurs maybe once a day for me and flashing my flashlight helps, but it sure is frustrating when you want to snap a quick picture.

Here:
http://forum.xda-developers.com/showthread.php?p=50591578
Sent from my XT1033 using xda app-developers app

Thank You
sakitobaki said:
Here:
http://forum.xda-developers.com/showthread.php?p=50591578
Sent from my XT1033 using xda app-developers app
Click to expand...
Click to collapse
Thank you very much !!! Camera cache clear, data clear force stop application and start again is woking fine..:good:

Again same issue
Hey guys,
Sometime above mention don't work and need to do restart only.
I believe that Motorola should work on this issue.

Same issue.. Tried everything... Camera error... This kitkat upgrade has slowed down my phone... Skyfire, times now, and many more applications force closes
Sent from my XT1033 using Tapatalk 2

Same issue here on my new phone- "Camera error: Camera error". Tried factory reset, cache clear, force stop, etc - no joy. Have now uninstalled two apps - "Flashlight" and Google Goggles. Let's see how this goes...
Very frustrating issue
EDIT: feel I should describe exactly what the issue is.
A period of time after the last reboot, the camera will stop working. When I attempt to start the camera app, I get a black screen and almost immediately the words "Camera error: Camera error" come in a dialog box. I click OK and the camera app closes.
I've tried an alternative camera app, Camera Zoom FX, but this behaves oddly. It starts up just fine, but only shows black - the image from the camera clearly isn't coming through to the app. Just black. Then, when I try to take a picture (the menus work just fine), the app force closes ("Sorry, Camera Zoom FX has stopped working.") Very strange!
As I said, I've removed some apps and will report back in a few days if it's fixed, or as soon as it breaks. My phone is fully up to date.
EDIT 2: this error has not completely stopped, but after installing the app "Camera MX" as suggested, I have been able to access the camera when needed. (Sometimes I need to start Camera MX and press the top-right "swap cameras" button, which IIRC looks like a refresh button.) Sometimes this isn't even necessary, but the issue seems better now for some reason. Maybe it's the beer.

I have now been having this issue with the camera as well as teslaled (flashlight app). I think it may have been caused by the ota update.

Hi guys
Here is a workaround for the issue
CameraMX can reset the camera resource if gets the error. So my trick is to simply start CameraMX and wait for the camera to reset. Takes
1-3 seconds and then it's fine. Better than a reboot
Sent from my XT1033 using Tapatalk

remove skype
xgt001 said:
Hi guys
Here is a workaround for the issue
CameraMX can reset the camera resource if gets the error. So my trick is to simply start CameraMX and wait for the camera to reset. Takes
1-3 seconds and then it's fine. Better than a reboot
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
I removed Skype and returned to work again.
:cyclops:

Nexus 5 freezing, screen acting up, camera unresponsive, WiFi stuck on 'turning on'?

Hi all, new member here, so apologies for any mistakes I make.
A friend of mine has passed on to me his Nexus 5 (2013), stating that there were a number of issues he was having with it. After using the device myself for a couple days I can confirm that the following issues are present:
- The screen will sporadically freeze and become unresponsive to any touch input, and the only way to solve this is to lock the device and unlock it again. The time between instances of this is random.
- The screen will occasionally cut to black, but the display is still active (i.e. you can only see the backlight). This happens for a number of seconds before returning to normal on it's own.
- The camera is completely unresponsive/broken (See picture 1 below). Possible loose connection?
- The WiFi is stuck on 'turning WiFi on' in the settings, and stuck at searching for networks in the notification bar(See pictures 2 & 3 below).
The device was dropped at some point in the past, but the damage is typical (See picture 4 below) and I see no immediate reason why this damage should cause these issues in particular, but I'm by no means an expert, hence why I'm here. =) The device has only been dropped one time, and has not suffered any other damage, including water damage.
My first instinct was to boot into recovery mode (where it should be noted that the freezing and display issues I mentioned above didn't occur, leading me to believe it is more of a software issue?) and clear the cache partition, which did not solve the issue, and neither did a full factory reset.
So, with all that being said, what would you guys suggest? Should I try flashing the factory image to see if that works? Rooting? Flashing a custom ROM? Any suggestions would be most appreciated!
If you require any additional information let me know and I'll happily oblige.
Thanks in advance guys!
Picture 1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Picture 2
Picture 3
Picture 4

It could be the motherboard or screen. You won't know for sure until you replace one or the other.
The wifi chips do fail on the Nexus 5. I a motherboard that also tries to turn on wifi but turns itself off after a few minutes.

audit13 said:
It could be the motherboard or screen. You won't know for sure until you replace one or the other.
The wifi chips do fail on the Nexus 5. I a motherboard that also tries to turn on wifi but turns itself off after a few minutes.
Click to expand...
Click to collapse
My first thought was that it was a hardware issue to begin with, but due to the sporadic nature of the issues (excluding the camera obviously), and the fact that it didn't happen whilst in the recovery menu, I'm more inclined to believe it to be a software issue? I could be wrong of course, I'm just wondering if it's worth flashing the factory image on to see if that solves the issue?

You may as well flash the stock image and see what happens.
The lines showing on the screen does not look like a software issue to me.

audit13 said:
You may as well flash the stock image and see what happens.
The lines showing on the screen does not look like a software issue to me.
Click to expand...
Click to collapse
Those lines are what appear when I open the camera, they're not there otherwise. THAT is almost definitely a hardware issue, granted.

I have a Nexus 5 that has the wifi issue. I flashed a bunch of different Android versions (like Android 7 and 6.0) which none have worked. At one point I opened my Nexus 5 and left it like that for about a month, then afterwards I assembled it back together and the wifi worked for a little bit and then went back to its broken state. I've concluded that it is a hardware issue since data was working fine and was the only way I could get internet on my phone.

xsacter said:
I have a Nexus 5 that has the wifi issue. I flashed a bunch of different Android versions (like Android 7 and 6.0) which none have worked. At one point I opened my Nexus 5 and left it like that for about a month, then afterwards I assembled it back together and the wifi worked for a little bit and then went back to its broken state. I've concluded that it is a hardware issue since data was working fine and was the only way I could get internet on my phone.
Click to expand...
Click to collapse
Hmm. I have to be be honest after looking online it appears that wifi failure is a somewhat common issue on the Nexus 5 devices. It has to be a hardware based problem it would seem.
Thanks for letting me know, I appreciate your input. =)

General OneUI 4.1 march broke accessibility

I use an accessibility app from here that allows long press volume up + down to activate and deactivate flashlight. Worked fine even screen off no aod on OneUI 4.0 Feb but after updating to 4.1 it barely works and only with screen on.
So, I decided to test other stuff and yeah it completely broke accessibility.
The touch and hold delay setting does nothing, it always takes like 2-3 seconds for anything to activate even when set to very short 0.3s, no longer works screen off at all.. GG Samsung..

Lol, my one N10+ is still happily running on Pie.
Upgrades and updates can and do break things.
It's a Samsung tradition... Samsung will eventually patch it.
Try clearing the system cache as that may correct it.

blackhawk said:
Lol, my one N10+ is still happily running on Pie.
Upgrades and updates can and do break things.
It's a Samsung tradition... Samsung will eventually patch it.
Try clearing the system cache as that may correct it.
Click to expand...
Click to collapse
Clearing cache didn't help but thanks for the tip. And thanks Samsung for not allowing us to access recovery without the usb-c plugged in.
It doesn't work on aod either. Only when fully waking the device. I wonder if this is intended behavior or just a huge bug.
Can anyone else on a S21/+/Ultra with march 4.1 test accessibility shortcuts on screen off state?

Imprezzion said:
Clearing cache didn't help but thanks for the tip. And thanks Samsung for not allowing us to access recovery without the usb-c plugged in.
It doesn't work on aod either. Only when fully waking the device. I wonder if this is intended behavior or just a huge bug.
Can anyone else on a S21/+/Ultra with march 4.1 test accessibility shortcuts on screen off state?
Click to expand...
Click to collapse
Your welcome.
Try in safe mode to rule out a 3rd party app interference.
Try clearing the data in the accessibility apk.
Turn off Developer options temporarily.
Play with it, there's probably a fix or work around.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

blackhawk said:
Your welcome.
Try in safe mode to rule out a 3rd party app interference.
Try clearing the data in the accessibility apk.
Turn off Developer options temporarily.
Play with it, there's probably a fix or work around.
View attachment 5569505
Click to expand...
Click to collapse
Did that, no difference. I did figure out what Samsung did actually.
They changed it so that long press volume up + down is 3 seconds and ignores the long press delay setting completely. And it also no longer works screen off while it used to work fine.
They also changed auto rotate sensitivity which makes it rotate with the slightest motion which is annoying as hell when reading something I'm bed for example as it constantly rotates..
Rolling back to Feb 4.0...

Do you have com.samsung.SMT disabled or removed?

Imprezzion said:
Did that, no difference. I did figure out what Samsung did actually.
View attachment 5569635
They changed it so that long press volume up + down is 3 seconds and ignores the long press delay setting completely. And it also no longer works screen off while it used to work fine.
They also changed auto rotate sensitivity which makes it rotate with the slightest motion which is annoying as hell when reading something I'm bed for example as it constantly rotates..
Rolling back to Feb 4.0...
Click to expand...
Click to collapse
This is one reason why I almost never upgrade or update. I don't like rude surprises.
Still running on Android 9 and 10; if it runs well I leave it be.
Funny what you say about the display flipping too easy; I get tired of waiting for it to transition.
They should have user settings for that by now.
Wonder if there's a 3rd party app to dial that in?