Related
haptiClock vibrates you the time (haptic feedback) if you shake/bump/tap your phone. It works when your screen is off, doesn't use much battery. The pattern to decipher the time from the pulses is simple to learn.
Great for checking the time on the sly, or when you can't pull your phone out.
Free version for trial then limited, and then paid for full version. Send me feedback, I want to make this a useful app! QR code at ... well as a total newb here I can't post links even a barcode, but lookitup!
-Phil
Permission: Prevent phone from sleeping
Makes me very nervous about battery life.
Otherwise, very interesting idea, and I'll check it out.
EDIT: I'm getting constant force-closes just reading the tutorial. Galaxy S phone (Android 2.1)
"I'm getting constant force-closes just reading the tutorial. Galaxy S phone (Android 2.1) "
Wow thanks for the info, I'll look into it... been tested on Droid, Droid X, Nexus
edit:<strike>The battery use isn't as bad as I thought it would be</strike>!
apparently it is using more juice than I had seen during beta testing
Android is really challenging- lots of hardware (IMO this is a good thing) and versions make testing unreliable...
Version 1.1 just uploaded should fix problem Izkata had... THANKS FOR THE INFO!
Just a quick test this morning, and it does appear to be fixed.
I'll test it more thoroughly later today.
I just downloaded the free version of this and it looks really promising.
While the screen was on and the app still open it worked perfectly, but when I turned the screen off and activated it again, it did hours fine and the rounded min fine, but the 2nd activation didn't work.
OK, noted ADeadlySpoon... thanks.
There is a time window to second tap to get the exact minutes, it's 10 seconds, you can also just go into "one tap" mode and time to exact minute every time. Still, I'll try to re-create your issue.
Wont work if screen is off.. on my EVO
drummer2780 said:
Wont work if screen is off.. on my EVO
Click to expand...
Click to collapse
Same with Desire HD which makes it useless for me atm.
But it's a nice App, hope this will work soon.
Okay, so - I left it running with the screen off and phone unused for about an hour and a half, to check the battery usage.
(Phone: Samsung Captivate (Galaxy S on ATT))
Normally, on average, I lose just under 1% per hour when the phone is not in use. With haptiClock active, I lost right around 1% per 10 minutes, while the phone was not in use. So the drop isn't as bad as I was expecting (yay!), but it's not something I'd leave on all the time, either.
No force-closes, ether, so the fix earlier seems to have fixed it entirely.
I have a habit of discreet time-checking, so this'll be great. Best trigger for me seems to be about 13 or 14 - juuust enough that I don't have to whack my phone/make an obvious movement to trigger it.
I have to change the language on the help, because when it did appear in my battery use stats it was always about the same as Cell Standby, which didn't seem to make sense, I should have grabbed Izkata's app (and will now) to check battery usage. It is important to turn off when you don't anticipate needing it.
On the Desire HD & EVO, I have no idea why ATM, but will look into it over the next 24hrs. I did test it on an HTC myTouch 3G and it worked.
If either of you get a chance, could you post OS version / API level and any mods?
Thanks for checking it out.
-Phil
upperTriangle said:
I have to change the language on the help, because when it did appear in my battery use stats it was always about the same as Cell Standby, which didn't seem to make sense, I should have grabbed Izkata's app (and will now) to check battery usage. It is important to turn off when you don't anticipate needing it.
Click to expand...
Click to collapse
Yey, thanks
It's not the best thing for measuring usage like this, though. To get the numbers in my previous post, I just recorded the percent before and after, and manually divided. 'Tho you can see in the History graph when it drops faster, so that helps.
upperTriangle said:
If either of you get a chance, could you post OS version / API level and any mods?
Click to expand...
Click to collapse
Android 2.1-update1 / API 7, rooted, but with no mods.
When screen is on, it works alright. But when screen turned off, no response from the app. Great idea though. I'm using a wildfire btw..
To those of you for whom the app doesn't work when the screen is off, this is an Android bug affecting certain phones. I believe it is a problem (be it a feature whereby the manufacturer is trying improve battery usage profile, or a bug) with the firmware. The HTC phones with Sense UI seem to be among the more commonly afflicted devices.
I remember seeing this bug report I started working on the app:
http://code.google.com/p/android/issues/detail?id=3708
BUT by the time it was getting close to done, my impression was that this had basically been fixed, and I didn't mention it anywhere in the release, none of the phones I tested on had this problem.
Now, there is another newer Android bug report regarding this issue, please STAR it (upper left of page)
http://code.google.com/p/android/issues/detail?id=11028
and hopefully we will see more rapid resolution of this issue, I think the OS isn't the problem, but perhaps manufacturer firmware updates could help resolve it.
Please don't leave negative comments on the Market if the app doesn't work with the screen off. Because of users doing this (which I should have seen coming) my star rating is started to go down. I have included language on the Market entry which should prevent people from giving the app a low rating solely because of this issue.
Lastly, there is a workaround of sorts for this which will fix the problem on some phones. I will implement it, but am going to proceed very cautiously, because last thing I want to do is break the app for users for whom it is currently functioning appropriately.
As such, I would really appreciate it if people who are experiencing this issue would beta test a new release with the workaround prior to my releasing it on the market.
So drummer2780,Testuser_01,thunderskain, ADeadlySpoon(?) ... if any of you would be so kind as to receive an APK file from me for testing on your device, in return I'll try to somehow get you the full version gratis of course (how we'll do that I'm not sure as I don't want an APK with licensing disabled floating around out there!, perhaps you can buy it from the Market and I'll refund the payment)
Izkata, for your help I'd like to do the same (give you free version) so if you buy it I will refund. I don't *think* a refund will invalidate the licensing, but I'm not sure, it is unclear from the Google distribution agreement language.
Thanks for checking out my app, I'm hoping people are finding it useful!
Izkata said:
Best trigger for me seems to be about 13 or 14 - juuust enough that I don't have to whack my phone/make an obvious movement to trigger it.
Click to expand...
Click to collapse
Since you are using it at a pretty sensitive setting:
Go to settings->overall sensitivity and select "Make more sensitive" and you'll find you can be a little more in the middle of the range and will have better precision for where you'd like the trigger to be, of course set it back if you want to use it and you're being more active.
-Phil
upperTriangle said:
So drummer2780,Testuser_01,thunderskain, ADeadlySpoon(?) ... if any of you would be so kind as to receive an APK file from me for testing on your device, in return I'll try to somehow get you the full version gratis of course (how we'll do that I'm not sure as I don't want an APK with licensing disabled floating around out there!, perhaps you can buy it from the Market and I'll refund the payment)
Izkata, for your help I'd like to do the same (give you free version) so if you buy it I will refund. I don't *think* a refund will invalidate the licensing, but I'm not sure, it is unclear from the Google distribution agreement language.
Click to expand...
Click to collapse
Since we both have a paid version of an app out, we could just do a "trade" and buy each others' apps, assuming you haven't already. The difference in pricing is small enough that I wouldn't really worry about it. Or we could try out the refund idea, then have experience to advise others in the future (I haven't bought haptiClock yet, and might not for a while - various stuff going on IRL)
upperTriangle said:
Go to settings->overall sensitivity and select "Make more sensitive" and you'll find you can be a little more in the middle of the range and will have better precision for where you'd like the trigger to be, of course set it back if you want to use it and you're being more active.
Click to expand...
Click to collapse
I'll take another look at the setting(s) eventually, and try and remember to post my comparisons in this thread once I do. (However, I'm starting a new job this week and don't want to mess with stuff/might not have time to mess with stuff until next weekend)
Great app! I've been looking for an app that did this for a really long time.
I was thinking though. The vibrate system's a little confusing, and I don't really need to know the exact time. Usually I only need to know it to the closest 15 minutes. Perhaps you could set toggles for the 10/15 minute vibe, the 5 minute vibe, and the 1 minute vibe?
SamUserInterface said:
Uually I only need to know it to the closest 15 minutes. Perhaps you could set toggles for the 10/15 minute vibe, the 5 minute vibe, and the 1 minute vibe?
Click to expand...
Click to collapse
There is a setting which allows you to only receive the 10/15 vibe (at least it requires an add'l tap to get the exact minute)... but I do like your idea of being able to specifically set where to stop. It would be a fairly extensive task for me to implement, as I basically have it set up to do just to the minute, or require add'l tap. We'll see how it goes, I can't say I'm going to be spending a bunch more time on this thing unless it attracts more users.
Thanks for the feedback!
Doesn't work with the screen off on the dell streak running dj steves 1.6.0 froyo ROM. Would definetly be interested in buying when (if) it can.
Well, it looks like all workarounds I've tried for phones which don't respond to the sensor when the screen is off (in standby mode) have failed. This is likely a firmware issue which ought to be addressed by the manufacturer. The code should run the same on all devices, this is the point of Android!
Given that it works on most phones, it is a "bug" or "defect".
Please take a moment to star the issue at code.google:
Issue 11028
Also, contact your phones manufacturer rolleyes: HTC) regarding this issue.
I think there are lots of possibilities here and hopefully it will get fixed because there are similar apps I'm creating which rely on the accelerometer working in standby as I've implemented in haptiClock.
Thanks
Phil
GROUND RULES:
Who should keep reading:
Current owners of Triumph or perspective buys who are trying to cut through all the trolls, flame wars, useless and/or misleading information from the (many) other threads, to find out what or if anything was wrong with their phone, how to identify these problems and most importantly, how to make intelligent decisions on whether to return or exchange before the 30 days run out.
Who should stop now and go read a book instead:
People who have (or think they have) perfect phones and feels it’s necessary to defend the Triumph’s honor at any mentioning of a problem. People who believes everybody else is clueless therefore it’s necessary to advertise basic settings changes as cure-alls (i.e. enable “use wireless networks,” it will fix your GPS problems). please give others more credit than that. And last but not least, people who hate the T and thinks it’s just the worst phone ever made… you have no reason to stay here.
Still with me? Good…
I have personally owned two T’s. the first one had several problems that I ended up returning, the second one was much better but not problem free. I also have access to two other T’s owned by friends. Everything I post here are based on facts that I have personally observed, not second-hand info or hear-say.
** GPS problem:
First of all, Google Map does NOT depend on GPS. Being able to see your location on the map means NOTHING when it comes to GPS location. In order to test if you have a GPS problem you have to either use an app like GPS Test or start Google Navigation. All tests should be done outdoors under open sky and while you have a valid data connection (for A-GPS data download). The GPS should lock-in within 2 minutes or less (Google Navigation should start showing your real time location as a blue arrow and start giving you turn by turn instructions).
A few minutes after a gps lock, you should have a location accurate to within 15ft or less. If google nav consistently shows a visible blue circle (of any size) around your current location, then it is unable to give you an accurate location lock, it is a problem.
If you have any problem at all with GPS lock or location accuracy, your phone has a broken GPS. Take it back for an exchange! Do not listen to people saying that you could fix it by running some magical software or do a special gps dance. You are wasting your time. If it wasn’t broken in the first place then you would have no need for those “fixes.” My first phone had an almost unusable GPS, the replacement and both of my friend’s phones have no problem whatsoever. Using GPS Test app, I was able to clearly see how the satellite signal levels were 30-50% lower on the previous T when compared to my OV, while the replacement had levels that are comparable to the OV.
** Data disconnect and/or drop to 1x when GPS is turned on.
I did not notice this behavior on any of the 4 Triumph I tested on. GPS and wireless signal can not interfere with each other, so if this happens consistently and is making data connection unstable or GPS lock problematic then there’s most likely a hardware problem. the phone should be exchanged.
** Screen flicker, white out, color cast:
If your screen ever turns white completely, or has a VERY heavy color cast, the answer is obvious, get it exchanged. meanwhile, all Triumph’s screen have overall “cooler” color when compared to my V. there were slight variations between each phone but as long as it was not extreme (i.e. making white look blue and red look purple) it should not be considered a problem. Just make sure you have removed the top layer screen protector before making a judgement.
slight screen flicker while turning on/off the phone repeatedly might not be worth an exchange for that reason alone. My first phone and one of my friend’s phone had the flickers, while my replacement and the other friend’s phone did not. The slight flicker did not both me or my friends at all.
**screen protectors:
Yes, there are two screen protectors. No, there’s absolutely no reason to keep the top layer. The second layer is very well applied and I doubt it’s meant to be taken off. You will never be able to apply another protector as well as that. If you have screen sensitivity issues, I’d suggest exchanging the phone rather than taking off that second layer of protector. None of the 4 phones I tried had any sensitivity issue with the protector attached. If you had to take it off then your phone has a problem.
** visible touch screen sensor elements:
If you can see “dots” on the screen under normal use, you are seeing the sensor elements embedded in between glass players. You should NOT be able to see them in any way during normal use. Exchange the phone if you do. it was a known LCD panels manufacturing problem on some earlier phones (mostly HTC). None of the Triumph I have seen had that problem.
** Signal level:
All four of the Triumphs had lower signal dbm numbers when compared to my OV. However, with my borderline coverage (-105dbm at home and -110dbm in the office), I had not experienced any drop calls on the T. Data connections were marginal but no worse than the OV. Do not make any decision based on dBm numbers alone. dbm is a relative value and do not mean what a lot of people seemed to think it means. In any case, exchanging the phone is not going to help in any way.
** WIFI disconnect:
I have not run into this with Triumph however, I had similar issue running AOSP rom on my OV while having no problem with other roms. This is likely something caused by the combination of router and phone software. My suggestion would be to try as many different routers as you can also try router settings such as G vs N, WEP vs WPA, hidden vs broadcast… if you have same problem everywhere then by all means try an exchange, I doubt it would help however.
** Touch button in sensitivity:
This happens randomly on all the T I have tested. It is likely a software problem that will not be fixed by exchanging the phone.
** Camera clicking while focusing:
All 4 phones had slight clicking noise while focusing but none had trouble actually gaining a focus. Exchange if you can’t get it to focus at all. the clicking seems to be normal however.
** Camera color cast:
None of the phones I have tried had problem with “green/blue color cast in the middle of the screen” as some have reported. If you have already removed the green screen protector on the camera itself then you probably have a real problem and should exchange the phone. just check your expectations – cell phone cameras have cheap plastic little fish eye lenses. Don’t expect results like your Canon or Nikon.
** phone stops charging while on:
I noticed two things: 1. some micro-usb chargers such as the one that came with OV would at times refuse to charge while the phone was turned on. Unplugging a couple of times may fix it. I haven’t had problem with stock T charger or the charger that came with my BlackBerry. 2. The charger will shut off once the phone temperature reaches 42c. this is most noticeable while in a hot car with phone on the dashboard. This is normal and is the result of an (over)sensitive overcharge protection.
** light leakage around bottom edges:
All the phones I have tired had various degrees of light leakage. It is consistent with problems reported on other versions of the same phone released earlier. the leakage was only visible in relative darkness so personally I did not think it was worth worrying about.
** Mismatched MEID:
To check your phone’s MEID, go to settings-> about phone -> status. The MEID should be an 18 digit number matching the stickers on the box, outside of the battery door and behind the battery on the back of the phone. Both of my phones had mismatched MEID. The phone itself was showing a 17 digit number while the stickers all have 18 digit numbers. an 0 in the middle is missing on the phones. One person (VM rep?) in an earlier thread had said VM was aware that 3,000 phones had this MEID mismatch so it seemed to be a known problem.
Some people have reported trouble using Google Voice on phones with mis-matched MEID. I have not been able to verify that myself.
** software version 38 vs 39:
Both of my Triumphs had version 38 software. the previous one had horrible GPS and some screen flickering while the replacement did not. There were also some obvious software differences between the two phones, despite the same software version. The replacement phone camera default to 5mp, while the previous one default to VGA resolution. The previous phone gallery had four random pictures referencing some Chinese websites (seemed to be leftover web cache). These pictures were in the ROM and did not go away after hard reset. The replacement phone had an empty gallery. One of my friend’s Triumph came with v.39 software which also had some screen flickers.
By itself, the software version did not indicate a good or bad phone. test everything!
The main thing to keep in mind is that there are many reported problems, not all of them were all that crucial. Given the obvious inconsistencies in build quality, it is a real possibility that the exchange would turns out to be much worse than the original phone. you really have to look long and hard at each problem and make an educated decision for yourself. Meanwhile, there’s absolutely no reason to put up with major things like a broken LCD or gps or insensitive touch screen. Take it back to the store!
This list was put together over several days, mostly as notes to myself. So please excuse me if it rambles a bit. Let me know if there’s something else you would like me to check.
Thanks and good luck.
I never even realized the 2 screen protectors but sure enough, they are there. As far as the light issues at the bottom of the screen, I definitely see it on mine as well.
microphone is awful.. sounds like there is tape on it. i checked, there isn't.
Heading to exchange it.
awesome write up. thank you sir
Another issue I just found out Im having is with my bluetooth. I have a Jawbone Icon and the sound seems overloaded. When I connect my older motorola BT headset to it, it works fine. Strange indeed!
My 30 day return period ends this weekend so I have to make a decision. GPS is really the only problem I have, and it is intermittent. I was hoping a software fix would come out so i wouldn't have to worry about exchanging.
As far as my bluetooth issues with the sound overpowering, I actually just bit the bullet and bought the a MOTO BT today to see how it would work. No issues. Fishy...
my biggest problem is that i cant seem to be able to stream music properly in google music. does everyone have this problem or should i exchange?
I even had full bars yesterday, and it was barely sputtering out any music.
crxmax said:
my biggest problem is that i cant seem to be able to stream music properly in google music. does everyone have this problem or should i exchange?
I even had full bars yesterday, and it was barely sputtering out any music.
Click to expand...
Click to collapse
I doubt that is a hardware issue. Probably a result of VM's network. Try running a speed test app and see what kind of speeds you are getting. I prefer "Open Signal."
the speeds i got on all the tests were all drastically different. I say an average of about 350kbs...is that normal?
Hi everyone,
I bought a Oneplus One in past July with enthusiasm.
After few days of use, began the "ghost swipes" issue (as every owner of the One) and multitouch issues (my phone is basically recognizing 1 finger at the same time) preventing any pinch to zoom or notification expand gesture.
But that's not the worst, after few weeks of use, began the most annoying issue I ever had on a device : my touchscreen is going crazy detecting contacts on the touchscreen by itself.
This issue began slowly but is getting worse over time. I noticed that the issue appears only after keeping my phone on my pocket for a while... I need to wait up to 10 mins after taking it out for the problem to disappear.
At first, a simple reboot was temporary the issue but not anymore. It's simple, I only can use my phone 10% of the day... During the remaining 90% it calls numbers, takes photos, deletes messages by itself...
Watch this video, it speaks for itself :
I do not know if anyone else has the same issue or not and I can't determine if it is a software problem, a hardware one or a combination of both...
I opened a support ticket on Oneplus website (but it seems I won't have answer before a few weeks... ) and I don't even know if they will accept doing a swap (OPO support is one of the worst I know).
What's sure is I am really disapointed by this device, whatever its price tag... And I won't recommend it to anyone and I won't give out my invites.
Guys, don't buy this phone and wait for the next Nexus device with which you'll have a high quality device at a decent price...
I let them a little while to find a fix to this situation and if nothing comes, I'll buy another one and use all means at my disposal to be refunded (the French law is quite helpful in the field).
.ant1
There are many users facing this issue. Check around the forums you'll see numerous threads about this issue, you might also find some tips to reduce the issue.
AFAIK this is as of yet not permanent fix for this issue, but since i dont have this issue i havent been following it so i might be wrong. Good luck though.
Google "bacon 55"
Sent from my OnePlus One using Tapatalk VIP
The only solution is to RMA the device. Took me 6 weeks of haggling with One Plus but finally the RMA is in process.
Anyone else have their flash led always dimly lit? Even when the phone is off my camera flash is dimly lit.
This is most likely the heart rate monitor. There is currently an issue with Google Fit and the S6 which causes the heart rate monitor to stay on. The only solution st this point is to uninstall Google Fit until Google releases an update that fixes the app.
Sent from my SM-G900W8 using Tapatalk
msavic6 said:
This is most likely the heart rate monitor. There is currently an issue with Google Fit and the S6 which causes the heart rate monitor to stay on. The only solution st this point is to uninstall Google Fit until Google releases an update that fixes the app.
Sent from my SM-G900W8 using Tapatalk
Click to expand...
Click to collapse
I'm not sure Google Fit is the only possible source for this problem.
I have the same problem as OP. I got my S6 (non-edge, 32GB) about 24 hours ago and last night noticed the faint yellow glow on the back of the unit. I haven't been impressed by the battery life (admittedly a very limited time with it so far) - but this could explain the less than stellar battery life so far.
I don't have Google Fit installed (in fact if I go to the play store, I get a message saying that it's not compatible with this version"). S-Health is disabled too.
One other thing, when I use the flashlight feature, I notice that the light isn't nearly as bright as on the S3 - not sure if this is relevant, it is the same LED.
I rebooted the system, and even turned it off, the faint light stays on. If the unit wasn't sealed I'd pull out the battery just to confirm this light can go out :-/
I have this issue on mine as well. I first noticed it when I went to charge my phone over night next to my bed. I lay the phone on its face so the LED notification doesn't show. I noticed a slight glow from the flash diode. I thought at first it only happened when I was charging my phone. Today, while at work, I powered down my phone and again noticed the light. For me, its always on. I just got off the phone with T-Mobile and they are going to over night me a replacement. I mention this thread to the T-Mobile support rep and she looked it up while I was on the phone with her. My friend's S6 does not have this issue, so not all of them are having this. I encourage everyone to go into a dark room and check your flash diode.
verboten said:
I have this issue on mine as well. I first noticed it when I went to charge my phone over night next to my bed. I lay the phone on its face so the LED notification doesn't show. I noticed a slight glow from the flash diode. I thought at first it only happened when I was charging my phone. Today, while at work, I powered down my phone and again noticed the light. For me, its always on. I just got off the phone with T-Mobile and they are going to over night me a replacement. I mention this thread to the T-Mobile support rep and she looked it up while I was on the phone with her. My friend's S6 does not have this issue, so not all of them are having this. I encourage everyone to go into a dark room and check your flash diode.
Click to expand...
Click to collapse
Just dropping into say I also have the issue . 32GB, Standard S6, T-Mobile. I will call them and get a new one overnighted as well.
Sorry to mention this and I don't mean any disrespect but there is a small plastic cover over the camera fnt rhw rate monitor did u peal it off ?? It should be OK now
demmo81 said:
Sorry to mention this and I don't mean any disrespect but there is a small plastic cover over the camera fnt rhw rate monitor did u peal it off ?? It should be OK now
Click to expand...
Click to collapse
I know I've done that on both of my s6s and still occurs.
demmo81 said:
Sorry to mention this and I don't mean any disrespect but there is a small plastic cover over the camera fnt rhw rate monitor did u peal it off ?? It should be OK now
Click to expand...
Click to collapse
No disrespect taken, man those are hard to get off (thanks for confirming this, it looked like there were).
However, that might explain the flashlight function being a bit dimmer than on the S3, but it wouldn't explain the constant light source itself.
How can we possibly check this in store where there is substantial amount of light anywhere. I'd definitely check my S6 in store for this.
Mine doesn't have this dim light at all I checked and I closed all the lights to make sure nothing is coming out . I don't know I wish I can help
KristianKenneth said:
How can we possibly check this in store where there is substantial amount of light anywhere. I'd definitely check my S6 in store for this.
Click to expand...
Click to collapse
I think it would be difficult to see unless you ask them to let you into a dark storage room without windows That's how I can verify mine is still doing that during the day, though at night when I wake up with the phone next to me, the glow is comparatively quite substantial.
Plus, you'll have to wait about a week before you can see them in the store.
I have two S6's and can confirm both of mine has this dim lit light only noticeable in the very dark.
The problem with us getting the device early is we don't know if this is hardware or software problem., that might get noticed and fixed with an update. Many say after the actual launch Samsung/Tmobile pushes an update. We can assume they at least will to fix the cell standby draining battery with VOLTE issue. Plus how many will we have to get shipped to us before we get one that doesn't do this, very different than being able to have the associate check it in the back office with lights off.
Can anyone that did get a replacement comment on this.
tenxo said:
I have two S6's and can confirm both of mine has this dim lit light only noticeable in the very dark.
The problem with us getting the device early is we don't know if this is hardware or software problem., that might get noticed and fixed with an update. Many say after the actual launch Samsung/Tmobile pushes an update. We can assume they at least will to fix the cell standby draining battery with VOLTE issue. Plus how many will we have to get shipped to us before we get one that doesn't do this, very different than being able to have the associate check it in the back office with lights off.
Can anyone that did get a replacement comment on this.
Click to expand...
Click to collapse
Mine is doing it too. If it is indeed the case that not all GS6s are doing this, that does make me concerned that somehow my unit is defective. I'm wondering if I should just hold onto it hoping that Samsung will fix it with a software update or if I should try yo exchange it.
poweroutlet said:
Mine is doing it too. If it is indeed the case that not all GS6s are doing this, that does make me concerned that somehow my unit is defective. I'm wondering if I should just hold onto it hoping that Samsung will fix it with a software update or if I should try yo exchange it.
Click to expand...
Click to collapse
I spoke with a tmobile rep. He said online orders get 20 days return exchange from the day of delivery not purchase. He also said there should be an update on a day or two after the official April 10th launch. I told him to document my account that I called about this issue. He said I could get another (two) overnight to me, but there's no way to guarantee if the new ones won't have this.
How come more people are not jumping in here to say theirs is doing it too. If its just us few maybe we do have a problem. But giving it's only noticeable in the dark maybe they haven't seen it on theirs?
Sent from my SM-G900T using AllianceR(●)m
tenxo said:
I spoke with a tmobile rep. He said online orders get 20 days return exchange from the day of delivery not purchase. He also said there should be an update on a day or two after the official April 10th launch. I told him to document my account that I called about this issue. He said I could get another (two) overnight to me, but there's no way to guarantee if the new ones won't have this.
How come more people are not jumping in here to say theirs is doing it too. If its just us few maybe we do have a problem. But giving it's only noticeable in the dark maybe they haven't seen it on theirs?
Sent from my SM-G900T using AllianceR(●)m
Click to expand...
Click to collapse
I think you are right, unless you have the phone next to you at night you probably won't notice it., still odd, I would have expected others to notice it too. And, even as dim it is, it can't help with battery life. I hope it's a software issue and can be easily patched that way.
Edit: just noticed tonight that my phone does in fact have the LED issue. It's odd because I spent some time yesterday in the dark looking for the problem and it was no where to be found. Been laying in bed messing with my phone while it's charging, decided to flip it over and low and behold, dimly lit flash on :/.
-Matt
Roflwafflez said:
Mine does not seem to be having this issue. I checked it out last night in a completely dark room and couldn't see anything. To see if I could get an idea of what it looked like though, I turned on the torch for about 20 seconds, then turned it off and looked again and it did replicate the faint glow that it seems most people are speaking of, however it faded away in about 30 seconds.
-Matt
Click to expand...
Click to collapse
This is making me think some S6s just have this defect where the LED never turns off and some don't. I think it might be best just to return my S6 and repurchase the phone after its official release date. I think these earlier phones might be more prone to defects. My gut feeling is that this is something that won't be fixed via software. I don't think exchanging the phone for a new one will help too much given that so many other S6s also have the issue, you have a good chance that the new phone you get will also be defective.
poweroutlet said:
This is making me think some S6s just have this defect where the LED never turns off and some don't..
Click to expand...
Click to collapse
My guess is it's a hardware issue (perhaps they used a different supplier/component for this part) since all of the phones are presumably running the same software (some with the OTA update that was waiting from T-Mobile - like myself, others perhaps without it). If it can be patched with software is another issue.
Actually, perhaps it would be useful to know if those experiencing the problem have applied the OTA update and those without haven't. My hunch is it won't be a factor, but curious, so people reporting should state their situation.
For my non-edge S6 (black 32 GB) I have the OTA and my flash stays on dimly all the time.
I noticed this last night and I thought it could have just been some sort of burn in from using the flashlight. (64gb regular tmo S6)
It's basically impossible to tell with any sort light around whether or not this is happening, even just with residual light, but mine does seem to be dimly lit in a pitch black room.
Could it have something to do with the selfie feature on the camera? Using the heart rate monitor as a picture button, that is.
I have a 64 GB T mobile regular GS6 with the OTA and I do have the issue.
I have noticed this happening for the past two to three days now, where after charging my phone to 100% and taking it off the charger, the phone feels sluggish overall in some apps and any videos - be it local on device videos shot from my camera, videos that I have received via WhatsApp, Instagram videos and reels or YouTube videos and shorts do not play at all. I just see the video buffering or loading (the circle keeps going round). Only thing to fix this is a restart. I am not sure what is causing this behaviour but it is very strange and ridiculous. I bought the Pixel thinking pure Android from Google would be the best UX but this sucks tbh.
Anyone else facing a similar issue and any tips on what the reason could be? I have been trying to get in touch with Google support but could not get through to them today, will try again tomorrow.
Edit: it is now happening randomly throughout the day and the camera app is almost frozen during such an episode if I try to use it.
Can you use something like geekbench app to profile the phone when it's at like 20 % after a restart vs 100% no restart?
Thorin_Stone said:
Can you use something like geekbench app to profile the phone when it's at like 20 % after a restart vs 100% no restart?
Click to expand...
Click to collapse
Yes will try to post it tomorrow, thanks for your reply.
Thorin_Stone said:
Can you use something like geekbench app to profile the phone when it's at like 20 % after a restart vs 100% no restart?
Click to expand...
Click to collapse
Here are the screenshots of Geekbench scores. Today's scores are from when the phone was exhibiting this strange behavior of videos not playing.
Unfortunately, this has started happening randomly through the day (and not necessarily after a full charge). I have seen that even the camera just freezes or is non responsive during such an episode. So I guess it is some sort of video driver issue?
I restarted the phone in safe mode and checked but don't see this issue happening in that mode. I've uninstalled apps that I've installed over the past few days. Still not sure what's the issue.
I checked with Google support yesterday and they told me to check in safe mode (done) or else perform a factory reset. Not sure if paying 1000€ for a phone only to factory reset it within a month for a wired issue seems justified. I have the same apps on my 6 year old One plus 3 and face no problems whatsoever apart from the phone being slow.
griswaalt said:
Here are the screenshots of Geekbench scores. Today's scores are from when the phone was exhibiting this strange behavior of videos not playing.
Unfortunately, this has started happening randomly through the day (and not necessarily after a full charge). I have seen that even the camera just freezes or is non responsive during such an episode. So I guess it is some sort of video driver issue?
I restarted the phone in safe mode and checked but don't see this issue happening in that mode. I've uninstalled apps that I've installed over the past few days. Still not sure what's the issue.
I checked with Google support yesterday and they told me to check in safe mode (done) or else perform a factory reset. Not sure if paying 1000€ for a phone only to factory reset it within a month for a wired issue seems justified. I have the same apps on my 6 year old One plus 3 and face no problems whatsoever apart from the phone being slow.
Click to expand...
Click to collapse
Hey, I don't mean to be a stickler here or tell you what kind of experience to have.
As a guy who deals with a lot of tech issues, I would recommend a Factory Reset along with google.
Things happen, and not EVERY device is perfect, try not to be done with the phone over resetting. I know it can be a pain but all devices need it from time to time. I work in IT and you would not believe the number of times resetting fixed an issue.
The time for concern is when that does not fix the issue or you are having to do it across multiple patches of a phone.
TLDR; ELECTRONICS BE WEIRD