Related
I noticed that Tilt's camera is extremely laggy when using in dark/dim environment. From what I read it seems that it related to infamous crappy driver issue..
I know it's related to brightness, since when I turn the camera on a, say, lamp or a well-lit object - it speeds up by A LOT.
It seems that it's trying to process or compensate for darkness... Is there any way around it? Let it be dark, but hell - it's so slow it's unusable.
I have the same experience, but since the camera has no external flash or light source, you must ensure adequate lighting conditions to get the best functionality out of the camera. I think the auto focus and or the flicker adjustment get really jerky in low light conditions. I thought something was wrong until I figured this out. It takes pretty good pics, and great video considering its a phone once you get the lighting right.
compared to just about any other camera phone I've used, it requires a LOT of light. This thing is virtuallly unusable inside. I have never, ever, gotten the picture I want to get. If you are taking a picture of people you need to click the camera, say cheese, and still wait for the picture to take. No way to take candid shots as people have always moved by the time it snaps.
Forced to carry my real camera.
I know I know...it's a phone, not a camera. That's for sure...
DarkDvr said:
It seems that it's trying to process or compensate for darkness... Is there any way around it? Let it be dark, but hell - it's so slow it's unusable.
Click to expand...
Click to collapse
I assume you didn't take the time to read the other 20 threads about the camera.
Go here:
http://forum.xda-developers.com/search.php
I like using Sports mode rather than camera mode indoors. A burst of pics generally will yeild a couple that are tolerable.
I did search.
What I'm asking in this thread is whether somebody found a temporary workaround for this problem, like increasing brightness, turning off some kind of "low light compensation" in the registry or something of that nature.
The answer is YES. It is inside another thread. I dont recall the settings, but indeed there are options to adjust, new cameras to install. They are just in different threads that are already established and waiting on people with questions to explore, read and learn from.
Well, I'll run another search and dig through pages of posts.. =)
Try the Google search of this site as apposed to the "search" option on the forums. Google is easier to preview and decide how relevant the search return is. Use more than one search term. If you are looking for a solution to Wi-Fi, search for Wi-Fi, WiFi or wireless router, etc....
http://www.google.com/advanced_search?q=+site:http://forum.xda-developers.com&hl=en&lr=&as_qdr=all
Just be thankful there are pages of information here. Some of those "pages" are repetitive threads like "How do I".... or "Does anyone know what...." if there weren't so many repetitive threads, there wouldn't be so many pages to search through. Know what I'm saying?
Yup, I run my own forum and I know what you mean.
Anyway, no sense arguing, I'll see what I can find. You're right about one thing - there's lots of info here.
Good luck DarkDrvr. I've read a lot here and tried several things. Not much success for me on the camera. Improvment, yes, worth a darn, no.
I'm hoping that, as they said, the video drivers that someone may eventually come out with help the camera too.
Since suggesting use of the Sports mode rather than the camra mode, I've come to realize that the difference that I'm seeing may more be the result of the udated camera version I'm running (version 5.04 build 29195). See this thread for info:
http://forum.xda-developers.com/showthread.php?t=355587
found a fix
turn on the camera.. then hit the power button. the screen will go black. wait like 5-10secs. hit the power button again and it tricks the camera to turn off the low-light compensation. after that you should be able to shoot away. found it here
http://www.youtube.com/watch?v=jqJcmJc8y_s
found a fix
the answer is in the comment section
way to go on pulling up an old thread and posting a solution that has been repeated way too many times
Greetings XDA users! As you can see, this is my first post on this forum. I have registered here in order to get some answers from other users of the HTC One concerning some problems that I have experienced. I have been using the device since more than a week now, and these are the issues I've come across so far, so please let me know which ones of these you are experiencing as well:
1. YouTube audio / video out of sync
I noticed this the first time I used YouTube on my HTC One. Lip sync simply looked horrible while watching some videos. To test if you have this issue as well, you should try something like this video where it can clearly be seen in action: Link (Since I cannot post links due to below 10 post count, simply search YouTube for "BBC HD audio sync test")
2. Simple games lag / do not play smoothly
The first game I tried on my HTC One was Doodle Jump. It's a very simple game, and before purchasing the One, I have read about other recent HTC smartphones having problems with such simple games because some HTC devices don't know how to properly use their GPU/CPU in situations where games don't have high demands. If this is still the case with the HTC One, and not just some issue with my own, it is simply unacceptable. After all, a new flagship smartphone should not have any issues when playing the most simple of games that any old android smartphone can do perfectly.
Note: I have already tried to cure both of these problems by doing it with / without power savings enabled. I have also tried with / without Beats, Bluetooth, NFC and so on. Nothing helps.
Please let me know if you are experiencing these two issues on your HTC One as well.
Other issues and annoyances I have noticed, that come to mind right now:
3. Blinkfeed share bar at the bottom of the screen is very annoying, and apparently can't be removed at all. It's doubly annoying because sometimes you can hit this bar when trying to use the back button.
4. 3-dot-menu bar at the bottom of the screen in some apps. There even used to be a built-in feature in the setting menu to get rid of this, but HTC seems to have removed this in the final software versions, for questionable reasons.
5. Video camera settings such as 60-FPS-HD or slow motion keep resetting themselves each time the screen gets locked and go back to "Normal".
6. Audio issues (cracks / pops) when using YouTube (maybe other apps as well). This happens especially often with Beats turned on, but I have also heard it happening with Beats off.
7. Odd volume jump that happens around 80% volume when increasing volume while streaming music via Bluetooth. (Volume actually goes down instead of up, and the next step after this sounds much louder than just 2 "clicks" more.)
8. Wifi reception gets a lot worse when covering the upper side of the device with my hand. And by covering I mean holding it normally in landscape orientation, I'm not intentionally trying to smother the signal. This is quite noticeable in areas where the signal is not that strong to begin with, as I've experienced multiple times that I've choked my wifi signal by simply holding it that way to watch some YouTube videos. The wifi bar can jump from 2-3 bars to just the dot by doing this.
I am rather disappointed to see this thread buried on page 3 already without any replies at all. All I asked for is a simple yes-or-no answer if your device also exhibits un-synchronous YouTube playback and/or unsmooth Doodle Jump gameplay.
So I guess this either means that I am the only one experiencing these problems and should promptly return my phone to get a properly working One, or it means people here simply do not notice these problems or accept to overlook them.
(By the way, the Bluetooth volume oddity seems to have been a randomly caused bug, as it was working fine again this afternoon)
I'm having the same issue with YouTube. It's basically unusable, the sound and lip sync gets progressively worse. Tried wiping the app data, re-installing YouTube, disabling Beats. Still no luck, this is the only beef I have with an otherwise excellent bit of tech. I tried the test videos and it looked spot on.
If I watch the same videos on my Asus Infinity there is no problem, so it's definitely the phone. I'm pretty much out of ideas.
YouTube audio / video out of sync
is indeed very horrible.....
ive never experienced anything like that, are you guys running stock rom?
For me, it's everything BUT YouTube. Games, apps, anything, there's about a 1/4 second delay between the on-screen action and when I hear the accompanying sound. Audio sync is one of my pet peeves, so this drives me absolutely crazy. I can only assume there's some kind of processing going on with the audio that's causing it, but damned if I can figure out what it is. The only audio switch I've seen to turn stuff on and off is Beats, and that has no effect on the latency.
I'm running stock ROM. Friend of mine with a ROMd unit says his doesn't do it.
I'm also having issues with the YouTube...
Sent from my LG-P768 using xda app-developers app
So is there no solution? I'm have the same problem...
Sent from my HTCONE using Tapatalk 4
So I run CM12.1 on this tablet, and it is rooted; however, this problem occurred far before I decided to modify it.
This problem is that when the device is put onto landscape mode, the resolution is stretched across to fit the whole screen. This does deform images and videos in such way where when switching between portrait and landscape, its rather noticeable and looks off.
Now my question, is there a way to keep the same aspect ratio (I don't mind black bars at the side), and if so how?
Also, just to clarify, is anyone else having this problem?
Any help would be appreciated , thanks!
There is currently no fix. There may never be a fix. It seems the actual pixels in the screen are not perfectly square, that is the cause.
Please search before creating a thread, there are other threads on this.
blueberry.sky said:
There is currently no fix. There may never be a fix. It seems the actual pixels in the screen are not perfectly square, that is the cause.
Please search before creating a thread, there are other threads on this.
Click to expand...
Click to collapse
- Ah, I see. That makes sense, thanks for the info.
- Oops, my bad; probably should've checked... Sorry!
Also, it bears mentioning that everything on the screen is always stretched all the time, regardless of what orientation the screen is in. It's just that some people's eyes/brains may only perceive the distortion under certain circumstances. In the main thread on this topic, there are those who say they don't notice it at all. Others (like myself) can't not notice it and it drives us crazy every time we use the device.
theophile2 said:
Also, it bears mentioning that everything on the screen is always stretched all the time, regardless of what orientation the screen is in. It's just that some people's eyes/brains may only perceive the distortion under certain circumstances. In the main thread on this topic, there are those who say they don't notice it at all. Others (like myself) can't not notice it and it drives us crazy every time we use the device.
Click to expand...
Click to collapse
I notice it, but the fact that this tablet is like 10x faster than my old Kindle Fire (1st Gen) makes it worth it to me. Running SlimLP on this is amazing.
My 2 day old, 5a with 5g just overheated. I have no case on it and it wasn't charging at the time. I was in a FBM video call and at about the 30 minute mark, I got the overheating warning. A few minutes later, the phone froze for about 60 seconds and then resumed. The phone was very hot to the touch! Ironically it was propped up against a laptop screen that was in hibernation mode and there is a table fan approximately 8 inches from the device blowing directly at it.
I reported it to Google Support and 1st level was very understanding. 2nd level told me to try some tips that he would send me because I was probably just overusing it. I told him I was using it exactly the same way I used my 2xl, but that didn't seem to make a difference.
I'll keep this updated as I continue to use my new "hot" phone.
Interesting. There's a known issue with recording 4K video, but this is the first time I've heard of an issue just streaming video.
Keep us updated for sure.
I have not tried the video recording at 4K...but I have been streaming YouTube videos and no overheating for me. YMMV
I have experienced the overheating issue while using video recording at 60 fps 4k. The phone didn't seem warm at all though so here's hoping it's just a software fix Google can implement.
If anyone can reliably reproduce the error, would you want to run some testing to see if the option for "Store videos efficiently
Use H.265/HEVC format" makes it better or worse?
I only had a heat issue when I first started my 5a, and it was installing all my apps in the background. Building the cache is notorious for its CPU use, so I can't say I'm surprised by overheating then. I've done a couple 5 minute 4k 60 videos without overheating since then.
I noticed the same thing today on my new Pixel 5a. Wasn't doing anything other than participating in a Whatsapp video call and browsing text messages.
I do have a Spigen case but the ambient temperature was low 70's inside.
This could be concerning...
luciferin said:
If anyone can reliably reproduce the error, would you want to run some testing to see if the option for "Store videos efficiently
Use H.265/HEVC format" makes it better or worse?
I only had a heat issue when I first started my 5a, and it was installing all my apps in the background. Building the cache is notorious for its CPU use, so I can't say I'm surprised by overheating then. I've done a couple 5 minute 4k 60 videos without overheating since then.
Click to expand...
Click to collapse
I had a similar heat issue when setting up my phone the first time as well. It was when I was just going through the setup, and transferring everything from old phone to the new one. I, unlike you, have never experienced the heat build up, that occured with this phone, on any other phone in my many years of flashing ROMs and setting up phones (unless I was flashing it multiple times due to issues). So, this post does leave me a bit concerned....
I hope once I get my case that this doesn't start occurring for me.
I have experienced the video camera causing the over heating. It appears that any app using built in video recorder will produce the heat. Google camera, Duo, … Zoom. I did a little searching before checking here on xda.
Google admits that the issue is with the 60 bpf 4k recording that is the cause. And of course they do not have a fix available at this time.
I was hoping to find a way to lower the setting to 30 bpf but I cannot locate a way to change the setting. Can anyone help with that please? Or is it possible to install a different camera from the play store with custom video settings, and set that as default for all video?
Edit: I use the system wide dark mode, so I didn't see the camera drop down arrow which opens the settings popup. Open the camera, select video mode, touch the drop down arrow at the very top center of screen. The default setting for Frames/Sec is Auto. The other 2 options are 30 bfs and 60 bfs. Select 30 bfs. Touch outside the popup to dismiss.
I left the resolution at Full HD which is the default. Most users report the issue is while using 60 bfs at 4k.
My wife, who is traveling in another section of the country, also reports over heating. She was not actively using any app when the heating issue occurred. After rebooting the device she saw that the WebEx Meet app was attempting to connect in the background. A persistent silent notification was displayed in the notification tray. This app was one of many that she had transferred from her old device to her 5a during the initial setup process. I told her to uninstall that app. Then review all apps and remove any not needed. Probably should do the same as I have not looked at which of them may also be outdated and needlessly using system resources.
Grr, time for an update. I've had the overheat warnings every few days, but no noticeable effects from it. Until today!
I was in a long video call, maybe an hour or so and got the warning. Shortly after that, the phone shutdown. It was not charging at the time, battery was at 51%
I contacted support and they listened to my complaint and asked all the same questions as last time... except for the new question to confirm that I bought it from the US Google Store (I did of course, but not sure why they would ask that). They said a specialist will contact me via email within 2 days.
Having this issue as well. Shut down the phone for 10m and still got the issue when I powered on.
Crazy
I had a 5a for about 2 wks. I was in Facebook video chat for about 15min when overheated and dropped internet connection. I was holding phone in hand parked in car 80 degree day. I had one day left to return it, so I rma'd it. No way to report hardware problem as reason for return. Charged me $35 restocking fee. I loved the phone, but they need to solve this. If they fix it, I may buy again.
The phone overheating at all is unacceptable. I've never even personally seen/felt a phone "overheat". That's crazy.
Obviously some kind of defect that google will ignore for 1 year as per protocol.
I've only had my 5a 3 days so far but mine has yet to overheat. And I'm a heavy user. Now my OnePlus n10 after the android 11 update would overheat multiple times a day, sometimes when just sending a text. When it was on Android 10 it never overheated.
Im starting to have those issues too. I cant record for more than 1 minute sometimes
Was this solved in the new update? I havent updated due to root, so just wondering.
Thanks
Deadmau-five said:
Was this solved in the new update? I havent updated due to root, so just wondering.
Thanks
Click to expand...
Click to collapse
No, I still can't record for over about 30 seconds to a minute
Unfortunately no... I'm still getting the overheating after the update.
This happened to me initially, like one user mentioned, when I got the phone and it was building the cache. More recently this happened to me while on a Caribbean vacation to Anguilla; was using the phone for pictures outside. It never got hot enough for a general overheat error, just always warning me that the camera was too hot and flash was disabled, or at one point camera was too hot when I was taking video and said the video could be unstable. I was filming in 1080/60. Switched to 1080/30 and it was ok. I have a Spigen Tough Armor case, so I wasn't surprised at that.
UPDATE: The phone finally died. I had been receiving the overheating issue about once a week since the beginning. Google support didn't care. Now, while I'm travelling in a foreign country, the phone died.
I called support and they said as a 1 time deal, they will replace it free of charge. However they only ship to the US and I have to send back this one in 14 days. That is an issue because mail from here takes months sometimes to reach the states. I"m not due back in the states until this summer.
WORST part: the password safe app that I use on my phone unlocks with my fingerprint. Never requires the actual password, so SHAME ON ME, I forgot that password. I have the password app on my laptop and it has current info, but I can't access it because I don't remember the actual password. :-(
PSA: use your actual password from time to time to ensure you don't forget key passwords!
I've been scouring the web trying to find *current* info about the overheating issue, but all I'm finding is stuff from last year. Nothing new about whether it was ever fixed by a software path, or if current inventory has a hardware fix, or if Google just ignored it as they often do. I'd like to know if I buy a new Pixel 5a today, directly from Google, if it still may have the problem. I'd be grateful for any info, thanks!
IMissPalmOS said:
I've been scouring the web trying to find *current* info about the overheating issue, but all I'm finding is stuff from last year. Nothing new about whether it was ever fixed by a software path, or if current inventory has a hardware fix, or if Google just ignored it as they often do. I'd like to know if I buy a new Pixel 5a today, directly from Google, if it still may have the problem. I'd be grateful for any info, thanks!
Click to expand...
Click to collapse
I don't play games and I don't use 4k video on my camera. For me phone is great didn't get worm once, but that is just my use, pictures, fullHD video, chat, video calls, phonecalls and browsing and watching videos.
I meet this problem when I take photos or video ([email protected]).
I have had issues by simply using Android Auto in my vehicle in less than 10 minutes of use. I have also experienced the overheating when recording videos even though I have followed all of the tips in Google's support email.
If I'm using Android Auto, I have to keep the phone in front of an AC vent in my car - otherwise all radios shut off within 1-2 minutes, followed a few minutes later by an overheat message (at that point it's already throttled so bad that the phone is completely unusable anyway).
Any teleconference app that uses the front camera causes it to shut down all radios about 1-2 minutes before popping up the overheat message with no warning before turning off radios (Zoom, Mychart, CVS Minute Clinic, Teladoc, even a Facebook Messenger video call). Drove me crazy trying to do a telemedicine appointment with my doctor, he finally called me instead.
Even just trying to do a phone call with Google Maps running during the call makes this damn thing overheat. Taking it out of the case (Spigen Slimarmor) seems to delay it by about a minute.
Honestly, if Fi didn't require me to keep it active for 120 days to keep the discount I got on it, I would have run the damn thing under an 18 wheeler by now. The only benefits over my old OP8T are the camera app and the physical size. That's it. Luckily I still have it, so once I hit that 120 days, I'm going back to the 8T.
Has anyone tried alternate ROMs to see if they handle the overheating issue any better? I'm especially interested in LineageOS. I imagine some kernel changes to scheduling and clocks could handle things better for this processor.