1.) (Probably the least relative to optimization) I'm almost positive that my phone may be financed. Although it may seem bad, it's really not. I purchased this phone for $300 on eBay. I then called a service representative about it being financed; he gave me a refund and told me I could do what I wanted with the phone. Just to be clear, I do not have factual evidence of it being financed. All I know is that the person selling it had a negative review on his profile from 10 days prior to me buying it saying "Sold a financed phone. Refused to take it back. Had to get eBay involved". The phone happened to be the same phone that I purchased, and when I booted it up, I opened T-Mobile's Device Unlock app and was presented with: "Your device is network locked at this time, which prevents it from operating with other compatible wireless networks", when I hit the continue button, it says "Server is not responding, please try again later". I called T-Mobile's customer service and the representative could not give me explicit information but did tell me that generally, that means the phone is being financed. What I'm wondering is, do you think it is financed? How can I tell if it actually is or not? I put the IMEI into T-Mobiles website and they do not recognize it. Also, there is no SIM card currently installed in the phone.
2.) The phone is quick.. and I mean VERY QUICK compared to my Honor 5x. The only issue I'm having with it is the SnapChat quality. Oh my is it bad! I've read the reasons for its low quality on several Reddit posts. I understand that since android's version of snapchat just screenshots the screen, the 18:9 image doesn't use the cameras full quality (or at least I think that's what the problem is supposed to be). The main issue I've noticed is its ability to handle low light. Truly, it records at 30 fps with high quality when there is proper lighting. When the lighting gets slightly worse, it records at 15-20fps with a SEVERE quality drop. Happens on both the front and back cam. Is there a way to fix this? I hear so much complaining but nobody suggesting fixes. Would a flashed ROM such as LineageOS help this? Also since it screenshots the snap, I feel as though it would make sense that rescaling it to 16:9 would work, but the only problem is, the option to change snapchat's scale is not in the options . Please let me know if anyone knows of a fix.
3.) I'm new to XDA-Developers and I was wondering if there are any general optimization threads or recommended apps or settings or ANYTHING really. I've been searching around and haven't been able to find anything useful.
Thank you so much for reading! Sorry for such long questions!
Related
hi, been searching the forum on this but with no results:
right now i have the cm9 update 27.04.2012 running with semaphore 1.1.1. kernel.
My modem seems to be activated when it shouldn't. No data connection is running, and yet the phone seems to send signals more often and in a wider extent then i'm used to register with other phones that only check their network status. It tends to keep transmitting, which I can hear in my loudspeakers as a steady sound which can go up to half a minute, as opposed to the regular rhythmic, morse-like interference which ceases after a few seconds, that we all know.
I wonder if anyone can point me to the reason for this, as it uses battery, gets on my nerves, and might even be rooted in some kind of intrusive piece of software.
Maybe someone also knows an app with which I could see what exactly uses the modem, and how?
On a side note: A few weeks ago I had a similar experience, but it didn't seem to be related to my phone, as moving it around didn't change the sound in the speakers. This was the strangest thing, because I only had this phone, and the noise kept going even though I had removed the battery. The only explanation would be another phone somewhere around my room in another appartment, although the next possible spot would be through the wall in the next house, which is the next building, which is highly improbable. Any ideas on what else besides a cellphone let alone an electronic device could have caused this?! i have even been thinking about surveillance measures by the police...
better ask in the cm9 thread ull get better answer
thanks, i'll do that...
Hello. I received my handset on Saturday morning from P4U and have been very impressed so far, especially compared to my experience with the One X last year where I had to swap 3 handsets before finding one without a major problem.
I have noticed however a possible glitch with the camera. When using the camera outside in bright sunlight I sometimes get glitches on the screen in the form of a jumping/rippling effect which is sometimes accompanied by a faint crackling/clicking notice. On one occasion it would not focus at all, with the screen rippling the whole time and refusing to focus. Following turning off and on again I have not had the problem to the same same degree, although it does happen occasionally with maybe just one of two ripples before the image on the screen settles down. The issue does not seem to arise in other scenarios (indoors, etc). Had I not had the situation where the camera could not focus at all I would just have put it down to the particular way that the camera focuses
Also I noticed that when the issue was most pronounced, I was standing outside our house in a bad/poor mobile reception area, just on fringe of out Wifi connection within the house. The phone was also set to auto update and was trying to do so. Could this therefore be some sort if interference issue interfering with the camera sensor or imaging chip?
Hs anyone else experienced anything similar? I am very pleased with the handset so if this is standard I would not exchange it. However if this is an indication that I have a dodgy camera module or imaging chip I would want to do something about it now.
Many thanks.
Just tried to use the camera to take photos at the theatre in combination of dark foreground and bright background. Camera struggled to focus on a number of occasions, with repeated clicking and pulsing/ripples on the screen as before. Never seen anything like it with a digital camera. Might be something to do with ultrapixel technology but it can't be right can it? Any ideas? Looks like an exchange may be necessary...
Reminds me of another thread...you should check out this thread : http://forum.xda-developers.com/showthread.php?t=2196059
Might be the same problem.
Thanks - I had seen that one too. Not the same effect, but I have seen that issue as well.
I called P4U today and got given a swap code to exchange the handset in-store, which I did earlier today. Not had a chance to test the new one, but hopefully it won't have the same issue as I have not seen anyone else complain about it before.
pclark666 said:
Thanks - I had seen that one too. Not the same effect, but I have seen that issue as well.
I called P4U today and got given a swap code to exchange the handset in-store, which I did earlier today. Not had a chance to test the new one, but hopefully it won't have the same issue as I have not seen anyone else complain about it before.
Click to expand...
Click to collapse
Do you have a video clip to show the ripple effect you have mention?
So before Android M came out, the one major thing I was waiting for was the new Camera features that were promised to come for the S6. When it did come out, I was disappointed to find no extra camera features. I never really looked into it.
Now some context to this post. I've gone through at least 5 different Camera2 API apps trying to get something that produces sufficient quality pictures and doesn't have that strange 8MP limit while using C2API. Of course, none of them worked.
I've recently realized, surprised that this has never been brought up before, that the stock Camera App is the incorrect version (cue dramatic music). The camera app in Android M for the S6 Active is v4 (the one for lollipop) of the camera app, while on the standard S6 (from my knowledge) it is v5. v5 of the camera app adds the fabled extra controls to the S6, including shutter speed control, and perhaps a fixed C2API. Can anyone else attest to my suspicious? And what kind of solutions are there? I've tried tweeting both AT&T and Samsung with no luck.
I have attempted to install v5 manually from an extracted APK, but it was sourced from an s7, which may or may not be of any use. It said "failed to install".
Any assistance would be greatly appreciated.
Wow, I just got in contact with Samsung, and after a bit of complicated explaining, the Rep has passed the bug on to their devs, and hopefully there will be an update soon enough that updates the Camera to add the new features.
Tada?
Hey.
I also noticed that after updating to 6.0, there is no RAW shooting mode and no shutter speed control. Samsung has still not done anything in this regard.
Xa33M said:
Hey.
I also noticed that after updating to 6.0, there is no RAW shooting mode and no shutter speed control. Samsung has still not done anything in this regard.
Click to expand...
Click to collapse
Yeah. I didn't want to bring this thread back from the dead but the Samsung Rep was just trying to get me off their back. I've made several requests more recently and the best response I've gotten is they'll "take it as feedback". I'm honestly fed up with Samsung, and I never plan on purchasing another Samsung device ever again. I wish I wasn't stuck on this stupid contract, I plan on getting a OnePlus 4 when it's released.
FevenKitsune said:
Yeah. I didn't want to bring this thread back from the dead but the Samsung Rep was just trying to get me off their back. I've made several requests more recently and the best response I've gotten is they'll "take it as feedback". I'm honestly fed up with Samsung, and I never plan on purchasing another Samsung device ever again. I wish I wasn't stuck on this stupid contract, I plan on getting a OnePlus 4 when it's released.
Click to expand...
Click to collapse
Last night, I talked to 3 samsung Reps on their chat service. One told me to wipe the cache partition, the other told me to boot in safe mode. I did all that, still nothing changed. The third one told me that I have to get my device examined physically, like there was some hardware problem. I tried to tell him that maybe it is an outdated camera app, that just needs to be updated, but he wouldn't listen.
I also own a DSLR and I love those RAW shooting modes and shutter speed control. I have take some great long exposure shots. In S6 and Edge, the shutter speed control allows for upto 10 second long exposure, which means that you can take some beautiful shots in low light and also dial down the ISO for low noise.
Xa33M said:
Last night, I talked to 3 samsung Reps on their chat service. One told me to wipe the cache partition, the other told me to boot in safe mode. I did all that, still nothing changed. The third one told me that I have to get my device examined physically, like there was some hardware problem. I tried to tell him that maybe it is an outdated camera app, that just needs to be updated, but he wouldn't listen.
I also own a DSLR and I love those RAW shooting modes and shutter speed control. I have take some great long exposure shots. In S6 and Edge, the shutter speed control allows for upto 10 second long exposure, which means that you can take some beautiful shots in low light and also dial down the ISO for low noise.
Click to expand...
Click to collapse
Sounds like my experience with them as well. Also, just for some clarification on my Original Post, based on my tests it's Lollipops Camera2 API (by Google) that isn't implemented at all. I am pretty sure the S6 had it implemented which allows them to access the RAW features. However, knowing Samsung, they could've just as easily made their own knockoff version of Camera2 API just to say "f**k you we're innovative" (/sarcasm).
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.