Related
I have an ATT Streak, with the Dell 2.2 froyo installed and updated. With the stock 1.6, the initial 2.2 and the updated 2.2, sometimes I can't unlock the phone. The green unlock tab will not slide across the screen. Most of the time it's fine but it happens at least a few times a day when attempting to answer calls. I've found that I can get it to unlock if I move the slider enough to reveal the white dot under the speaker icon, and then press that. Pressing the dot under the speaker icon makes the unlock slider move all the way over so I'm not dead but it's still rather frustrating. Usually everything is fine. Anyone have any ideas? This is my first Android but I've had Kaisers, Raphaels and Rhodiums and have gone through a fair amount with them. Do the DJ_Steve ROMs fix the problem? Is this a known issue?
Thanks in advance
See thread 'Touch screen unresponsive after pocket time'
You can also get Menu unlock from the market...it allows you to just tap the menu softkey to unlock the phone.
Also, check out NoLock from the market...you can have it set so that when you hit your power button, your phone opens to the homepage.
I had exactly the same problem, would miss phone calls as I couldn't slide to answer either. This happened almost systematically when I left my wifi hotspot - but would happen also if wifi was turned off.
In the end, recalibrating my screen did it. Since, I haven't had a single sticky/frozen slide to unlock
calibrating did not help but returning it did
I couldn't make myself think the phone was worth the troubles so I brought it back and went back to my old Tilt 2/TP2 while I wait for the aTrix or a slider version of the 4.3" HTCs or Samsungs like the Epic. Thanks for the advice.
Try "easy answer button" off the market, it allows you to have a button to answer the phone.
Touchscreen out when in pocket
bartsplanet said:
See thread 'Touch screen unresponsive after
pocket time'
Click to expand...
Click to collapse
Agreed, see that thread and remember to make sure the touchscreen is facing away from your body when you place it in your pocket. Something about the heat/magnetic sensitivity that get's thrown off when it's in your pocket and facing skin. Worked like a charm for me...no issues with unlocking or touchscreen responsiveness...
strvmarv said:
Agreed, see that thread and remember to make sure the touchscreen is facing away from your body when you place it in your pocket. Something about the heat/magnetic sensitivity that get's thrown off when it's in your pocket and facing skin. Worked like a charm for me...no issues with unlocking or touchscreen responsiveness...
Click to expand...
Click to collapse
It's the static build up on touch surface; not avoidable totally but above suggestion would minimize it to non annoying level... antistatic pouch would also help no matter how it is carried.
Sent from my Dell Streak using Tapatalk
I've delaminated the resistive screens on a bunch of HTCs
carring them in my pocket screen in. I thought the glass on the streak wouldn't have any of those issues. I'm leaning towards an aTrix when it comes out and I think it's also gorilla glass. You think it's the heat, or static that causes the problem?
I also had this problem, and it got solved when I uninstalled my App Killer!
I have a Q, since I cannot find "menu unlock" on the market, can I download it and install it over PC (without rooting etc.)
I'm using froyo 2.2 official 318 build
Recalibrating it did the trick for me
Sent from my Dell Streak using XDA App
Bob Simons said:
carring them in my pocket screen in. I thought the glass on the streak wouldn't have any of those issues. I'm leaning towards an aTrix when it comes out and I think it's also gorilla glass. You think it's the heat, or static that causes the problem?
Click to expand...
Click to collapse
Gorilla glass is a chemical treatment to harden glass not really helps or solves static build up like issues.. I am guessing top layer glass is very thin on streak (lowest margins are .5 - .75mm for tempered glass and even less than .5mm for polycarbonate surfaces) hence the static build up, which is impossible to prevent, rather easily interferes with streak's touch sensor. There are safety margins for gaps between LCD and touch as well as touch glass thicknesses for proper signal capture by adc before fed into touch controller (if discrete IC is used) and there is a big chance streak design took the lowest possible of those margins and since the surface is rather large, static build up could temporarily hinder touch recognition...
Sent from my Dell Streak using Tapatalk
Recalibrating fixes this issue and its not due to gorilla glass or due to storage of the phones in your pockets.
Nish
Sent from my Dell streak using XDA app
Nischithkm said:
Recalibrating fixes this issue and its not due to gorilla glass or due to storage of the phones in your pockets.
Nish
Sent from my Dell streak using XDA app
Click to expand...
Click to collapse
Just b/c it worked for you doesn't mean it's the only answer. Recalibrating did not fix the issue for me. Changing the way I carry it in my pocket *did*, but that doesn't mean it will solve *everyone's* similar issue. We're just trying to help by providing suggestions...
I use noLock and shaketoanswer from the marketplace
didnt fix the problem, just bypassed it.......
damo182 said:
I use noLock and shaketoanswer from the marketplace
didnt fix the problem, just bypassed it.......
Click to expand...
Click to collapse
No lock works great. The lock screen is a pain in the assets anyway
Dell Streak, 2.2 froyo (318), custom kernel, OC to 1.2ghz, quadrant 2002, hspda signal mod,
Hello, just one simple question: where's proximity sensor in the A500/A501? I have the Acer flip case but if I close it the screen stays on... Should I enable it somewhere in the settings?
Are you referring to the ambient light sensor? If so, its on the top left bezel, between the volume rocker and the rotation lock. If you look at the black glass there in bright light, you will see a small dark spot, that is the sensor.
As for a setting, the screen will dim based on ambient light levels, not shut off. The setting for it is located by tapping the clock, then the settings button, then the word "auto" next to the brightness slider.
Was this post helpful? If so give thanks
The correct answer is a question... What proximity sensor?
this is driving me nut
the Acer case will always partially cover this one and the dispaly will fluctuate the brightness in random... ;(
pushing A500 firmly into the case solves for a while before happening again - think I need new case...
Based upon this site that contains the tech specs, http://gadgetian.com/10395/acer-iconia-tab-a501-specs-price, the A501 should contain a "proximity sensor to turn it on or off". Please note that if you google for "Acer iconia tab proximity sensor" you will get a number of results, so I doubt that it's just a mistake of one site.
So there's no way to turn the screen off while the tab is properly fitted in its sleeve?
Couldnt the light sensor be used as a proximity sensor? With software I mean.
I have checked my tablet from top to bottom and even made some sensor test to make sure that everything is working and I never saw a listing for a proximity sensor so I'm sure that we don't have one (or a barometer... that was also one of the things that was possible to test ).
@cd85233: Probably yes but I wonder what kind of impact it would have on the battery.
there is no proximity sensor on the A500 nor A501. refered to spec sheet and hardware implementation... unless they changed it since last release.
who told you so ?
Guys, there's an app called tasker. You can use that to tell the tablet to lock up when it receives less than 3 or so % light reading from the light sensor. It works great on the gtab. Still waiting for the case for my iconia to test it out.
sanaell said:
there is no proximity sensor on the A500 nor A501. refered to spec sheet and hardware implementation... unless they changed it since last release.
who told you so ?
Click to expand...
Click to collapse
Just google for "iconia tab proximity sensor", you'll get a bunch of results
Sent from my A501 using XDA App
still an ambient light sensor, not proximity sensor. As for if it could bbe used as one by software I'm not sure. For the case, look up roocases for the acer iconia on amazon. I have the folio multi-angle black n love it!
goodintentions said:
Guys, there's an app called tasker. You can use that to tell the tablet to lock up when it receives less than 3 or so % light reading from the light sensor. It works great on the gtab. Still waiting for the case for my iconia to test it out.
Click to expand...
Click to collapse
This works 100%. Just did it on my Iconia.
Set the trigger to be light between 0 and 5% and the action to be "Display"->System lock.
Let me know if you guys need help but this is easy and works AMAZINGLY. I don't know if more battery use occurs to poll the sensor though. Will report if I see it in the battery usage.
-cd85233
cm0901 said:
Just google for "iconia tab proximity sensor", you'll get a bunch of results
Sent from my A501 using XDA App
Click to expand...
Click to collapse
Google FLAT EARTH and you will get plenty of results -
Just because someone calls it that doesn't make them right.
Go ask a PC repairer how any times a customer has asked to have their hard drive partition fixed when what the customer means is something completely different. Meaning people often use what they think is technical jargon to imply knowledge they don't actually possess
cm0901 said:
Just google for "iconia tab proximity sensor", you'll get a bunch of results
Sent from my A501 using XDA App
Click to expand...
Click to collapse
and if you enter the word 'unicorn' into google you'll also get a bunch of results. still doesn't mean they exist!
Ok, no need to attack Just asking, and just telling you from where my speculation came from Various sites lists it in the tech specs so I was trying to understand whether I have a faulty sensor or not. End of the story!
cm0901 said:
Ok, no need to attack Just asking, and just telling you from where my speculation came from Various sites lists it in the tech specs so I was trying to understand whether I have a faulty sensor or not. End of the story!
Click to expand...
Click to collapse
I get it, now you know n its kinda like how one off the wall chinese tablet has a "gravity sensor". Is it an accelerometer? Gyroscope? Our does it merely sense the presence of gravity? Will the device go haywire if used in outer space? Who knows! Lol tech specs can be painfully vague and inaccurate. Especially on a company who can't even figure out to name the source code for their kernel something that doesn't make it look like a help file, THEN place it in the documentation portion of the site, good job Acer! Point being I get the confusion
tonyblack said:
and if you enter the word 'unicorn' into google you'll also get a bunch of results. still doesn't mean they exist!
Click to expand...
Click to collapse
LOL ...
Just enter that into XDA search... no need to go as far as Google ...hahaha !
So I found out the hard way that the Tab 2 10.1 doesn't come with a proximity sensor (not sure how I missed this). Has anyone found an app that turns the screen on/off by opening and closing a case?
My assumption is that this isn't possible without a proximity sensor but thought I'd ask.
Sent from my Kanged Tab2
Shouldn't be impossible at all.. the device auto senses what the screen light should be I do not know if it uses the camera for this or if there is a second sensor to accomplish this.. but it sounds totally feasible to write a program that senses total darkness to tell the device to sleep Im not so sure how turning it back on would work..this would be am awesome app please post back if you find one
Sent from my GT-P3110 using xda app-developers app
Here there, sorry I don't think it is possible, even smart cover app relys on proximity sensor.
And no, light sensor wouldn't work in dark places or at night.
I believe proximity sensor is only present in cellular models. If so, on your dialpad/keypad, type *#0*# -> sensor -> and place an object near the top of the tablet where the speaker and light/prox sensors are located.
Screen should turn green, and PROXIMITY:0.0 -> PROXIMITY:1.0
Im not much on coding but you would see some light at night from the screen unless the sensor just sucks or the case lets too much light escape i dont see why it wouldnt.
Sent from my KFTT using xda app-developers app
mrkhigh said:
Im not much on coding but you would see some light at night from the screen unless the sensor just sucks or the case lets too much light escape i dont see why it wouldnt.
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
The sensors are only effective if light in shinning directly above it. If light sensors were this sensitive (picking up light from screen), I adobt putting a smart cover on or putting it in your pocket isn't going to work since neither pockets or smart covers are completely light proof as sensors are near the top picking up reddish/faint light.
Cover isn't flat enough to stop screen backlight from traveling accorss the surface of tab and therefore sensors won't be triggered.
Common sense
do you try the Power Switch Pro?
Power Switch Pro works with my Tab 2 7.0 and I would think it would work with the 10.1. There is a lite version on Play that you can try. I liked it well enough to buy it.
chriscsh said:
do you try the Power Switch Pro?
Click to expand...
Click to collapse
Tel864 said:
Power Switch Pro works with my Tab 2 7.0 and I would think it would work with the 10.1. There is a lite version on Play that you can try. I liked it well enough to buy it.
Click to expand...
Click to collapse
I'll get it a shot and see if it works. Are you using the wireless or cellular version?
Sent from my NOTEworthy smartphone
Must be user error because power switch pro didn't work on my10.1
Sent from my Kanged Tab2
emeraldayotte said:
I'll get it a shot and see if it works. Are you using the wireless or cellular version?
Sent from my NOTEworthy smartphone
Click to expand...
Click to collapse
I'm using the wireless version. It works on my Samsung and also on the wife's rooted Nook tablet. It actually works the best when using the motion sensor and laying it upside down when you want it to turn off. A couple of times it didn't respond as quickly when lying on the back, but it works 100% of the time when laid upside down.
emeraldayotte said:
Must be user error because power switch pro didn't work on my10.1
Sent from my Kanged Tab2
Click to expand...
Click to collapse
i guess this only work on rooted device
emeraldayotte said:
So I found out the hard way that the Tab 2 10.1 doesn't come with a proximity sensor (not sure how I missed this). Has anyone found an app that turns the screen on/off by opening and closing a case?
My assumption is that this isn't possible without a proximity sensor but thought I'd ask.
Sent from my Kanged Tab2
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.sourcespark.app.casesensor&feature=related_apps#?t=W251bGwsMSwxLDEwOSwiY29tLnNvdXJjZXNwYXJrLmFwcC5jYXNlc2Vuc29yIl0.
Here you go its not free but 0.99 is not alot works off light sensor
My p3100 has a proximity
__________________
Sweet Devil >_<
GT-P3100 | Android 4.0.4 ICS | Sun Cellular
PM me if you need help
OptimusLove said:
My p3100 has a proximity
__________________
Sweet Devil >_<
GT-P3100 | Android 4.0.4 ICS | Sun Cellular
PM me if you need help
Click to expand...
Click to collapse
and...
perhaps we should buy your p3100....no comment
There is also a app at google play called Killswitch Lite.
power switch pro seems to do the job to a certain point. it works good outside, but when you are inside a room or place with a litle less light it starts to pop up that notification window and shut down the screen. maybe be it can be adjusted with the light sensor sensitivity but i found that so disturbing that i disable it.
for me it doesnt do the desired job. if someone has some idea how to make this useful will be thankful.
karaern said:
power switch pro seems to do the job to a certain point. it works good outside, but when you are inside a room or place with a litle less light it starts to pop up that notification window and shut down the screen. maybe be it can be adjusted with the light sensor sensitivity but i found that so disturbing that i disable it.
for me it doesnt do the desired job. if someone has some idea how to make this useful will be thankful.
Click to expand...
Click to collapse
Like I said earlier
searsh smart cover on google play best one is about 2 $
I use Case Sensor on my Tab 10.1" and it does it's job. It does use the light sensor so during night time or dark areas, it won't activate thinking the case is still covering the light sensor. This app is clever in that when you press the power button, it will override the app for a temporary amount of time. Good enough until someone else can think of a better way to execute or use a combination on different sensors to control the screen
Initial releases almost ALWAYS flesh out some build issues that quickly get fixed (even Apples, but not so often), so hopefully the title says it all. Since we already have seen a few issues with the initial builds, such as camera sensor quality, case gaps, dead pixels, etc., maybe this thread will be a good place to keep watch on the progress of the HTC One issues being remedied, as many of us wait for HTC to perfect the One before we make our order. We don't want to get stuck with hardware issues that may be quickly remedied after initial release.
So you early adopters can help the lurking masses who are anxiously waiting for the right time to buy. Once we have a lot of people reporting what is or isn't good, we can then get an idea of when issues are not really issues anymore.
Please list any hardware issues you have noticed (software too, but no so important since software can be fixed after purchase), and/or list any fixes to these issues or opinions on whether these have become non-issues, so that many of us who are waiting can check the problems off our lists. If there are ways of identifying which hardware versions have the problems vs. which ones do not, that would be great info for this thread as well so that we can check a device in the store or quickly return a device before committing to a purchase.
Hardware issues:
-- Camera sensor yielding image issues such as mis-focus and/or color banding in a small percentage of units, partly due to a HUGE number of image sensor being rejected and causing initial release delays.
-- Gaps is the seams of the case materials such that the unibody design doesn't seem so smooth and seamless.
-- Stuck display pixels or observable differences in displays on a small percentage of sold units, possibly due to HTC using more than a single screen manufacturer.
-- Is black anodize hard enough that resistance to scratching and chipping is on par with other brands out there?
-- Signal reception issues
Software/driver issues:
-- GPU tests not scoring as expected, in comparison to similar phones currently coming out.
-- Volume level adjustability more granular in the low volume end.
-- Capacitive buttons not responding when they should.
-- Battery Drain issues
-- Acceptable menu button solution / HTC logo touch digitizer mapped to become a button (not necessary, but would love to see developers make this happen!)
gruuvin said:
Initial releases almost ALWAYS flesh out some build issues that quickly get fixed (even Apples, but not so often), so hopefully the title says it all. Since we already have seen a few issues with the initial builds, such as camera sensor quality, case gaps, dead pixels, etc., maybe this thread will be a good place to keep watch on the progress of the HTC One issues being remedied, as many of us wait for HTC to perfect the One before we make our order. We don't want to get stuck with hardware issues that may be quickly remedied after initial release.
So you early adopters can help the lurking masses who are anxiously waiting for the right time to buy. Once we have a lot of people reporting what is or isn't good, we can then get an idea of when issues are not really issues anymore.
Please list any hardware issues you have noticed (software too, but no so important since software can be fixed after purchase), and/or list any fixes to these issues or opinions on whether these have become non-issues, so that many of us who are waiting can check the problems off our lists. If there are ways of identifying which hardware versions have the problems vs. which ones do not, that would be great info for this thread as well so that we can check a device in the store or quickly return a device before committing to a purchase.
I'll start it off. So far hardware issues to look out for:
- Camera sensor yielding image issues such as mis-focus and/or color banding in a small percentage of units, partly due to a HUGE number of image sensor being rejected and causing initial release delays.
- Gaps is the seams of the case materials such that the unibody design doesn't seem so smooth and seamless.
- Stuck display pixels or observable differences in displays on a small percentage of sold units, possibly due to HTC using more than a single screen manufacturer.
- Is black anodize hard enough that resistance to scratching and chipping is on par with other brands out there?
And possible software/driver issues with:
- GPU not testing where expected, in comparison to similar phones currently coming out.
- Volume level adjustability more granular in the low volume end.
- Acceptable menu button solution / HTC logo touch digitizer mapped to become a button (not necessary, but would love to see developers make this happen!)
Click to expand...
Click to collapse
The sometimes-not responding capacitive buttons which are most likely a software issue.
Also:
-Fix the color temperature of the screen, it's too much on the cooler side
-Fix the audio hissing in some 1080p videos made in a quiet environment
-Sense drains too much battery in stand-by
-Improve 4G/LTE signal reception
-'msm_hsic_host' wake lock keeps the phone awake on stand-by and drains battery
darkgoon3r96 said:
The sometimes-not responding capacitive buttons which are most likely a software issue.
Click to expand...
Click to collapse
I get this aswell...
Also, whether its me or not but sometimes im on the phone and it randomly turns on speaker phone.... Going to wait n see how this one pans out tbh. It might be me touching it with my ear.
Xperia23 said:
I get this aswell...
Also, whether its me or not but sometimes im on the phone and it randomly turns on speaker phone.... Going to wait n see how this one pans out tbh. It might be me touching it with my ear.
Click to expand...
Click to collapse
If it is you touching it with your ear, then that is still a problem, as the proximity sensor should sense that the phone is close to your head and then shutdown the screen and touch sensor input so that touching the screen does nothing.
Maybe u could add links for each of the problems to related threads so users can get more info?
Sent from my Desire HD using xda premium
I just checked out the one at a nearby at&t store. I had such a hard time with the capacitve buttons that I am reconsidering the phone. Not once did I get them to work on my first touch. Extremely disappointed. Hoping it was that one model in that store. Will check out another store. Also looking at xperia zl as an alternative now. So disappointed though as it was pretty awesome looking and extremely light.
Sent from my SPH-L710 using xda app-developers app
gruuvin said:
- Acceptable menu button solution / HTC logo touch digitizer mapped to become a button (not necessary, but would love to see developers make this happen!)
Click to expand...
Click to collapse
My biggest issue with the lack of menu button is that I've always used it to quickly pull up the address bar on my browser. If you gently scroll up or down on the browser it will pull it up, but it doesn't always work very well. That is what I would like to see a solution to, first and foremost.
The home and back buttons are not very sensitive and don't always react on my first attempt. Also the battery is draining extremely quick. I'm losing 12% per hour.
Sent from my HTCONE using xda app-developers app
There's a fix for the capacitive buttons. Someone found a sensitivity setting.
Sent from my Nexus 7 using xda app-developers app
Element515 said:
There's a fix for the capacitive buttons. Someone found a sensitivity setting.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Care to share the light on this? A link or instructions?
I don't quite remember where I read it... I've been stalking these forums for a while because I really want the phone... If you play around in your settings, somewhere there's an option to adjust/calibrate the sensitivity. Then, if you just very lightly touch the buttons, it will calibrate to that sensitivity and then fixed!
gruuvin said:
-- Acceptable menu button solution / HTC logo touch digitizer mapped to become a button (not necessary, but would love to see developers make this happen!)
Click to expand...
Click to collapse
Does the hardware support this? As there might not be touch sensor on the logo... :/
Pr20 said:
I just checked out the one at a nearby at&t store. I had such a hard time with the capacitve buttons that I am reconsidering the phone. Not once did I get them to work on my first touch. Extremely disappointed. Hoping it was that one model in that store. Will check out another store. Also looking at xperia zl as an alternative now. So disappointed though as it was pretty awesome looking and extremely light.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
So I went and checked it out at another store and there was no problem with sensitivity. It had a weird problem where home would just bring up whatever screen you are on. Must be particular to that phone. Either way the sensitivity of the buttons was totally fine which was the main issue.
Also liked at xperia zl which is a fine phone in its own right but it just does not compare to the one. Although it does have one advantage which is that it is much easier to hack and get aosp and also get klp when it comes out.
Sent from my SPH-L710 using xda app-developers app
Element515 said:
I don't quite remember where I read it... I've been stalking these forums for a while because I really want the phone... If you play around in your settings, somewhere there's an option to adjust/calibrate the sensitivity. Then, if you just very lightly touch the buttons, it will calibrate to that sensitivity and then fixed!
Click to expand...
Click to collapse
I think this is the thread.
Solution to irresponsive back/home key
Case pitted
Got my 64bg on the 19th via mail direct order ATT. Top of aluminum case near power button front side chamfered edge had 2 pitted dents. Put back in box and immediately went to ATT store to return for new order replacement. I also noticed some rough finish in edges of aluminum casing where it meets plastic fill. Not at the level of my Iphone 5 fit and finish. Will see what replacement looks like in the next few days once received.
I'm glad I'm not the only one who feels the need to stab the hell out of the capacitive buttons when it comes time to go "home" or "back."
One of the few things that has agitated me about this phone is the effort required to press the back and home buttons. I actually began wondering if they were pressure-sensitive or something. After all, my Note 2 would often register inadvertent presses of the back and menu capacitive buttons because they were so sensitive. With the Nexus 4, the buttons are responsive, if not hypersensitive.
I have just set my calibration and the home /back buttons are immediately more sensitive.
omar302 said:
I think this is the thread.
Solution to irresponsive back/home key
Click to expand...
Click to collapse
Worked for me, thanks
Sent from my HTCONE using Tapatalk 2
g2525 said:
Does the hardware support this? As there might not be touch sensor on the logo... :/
Click to expand...
Click to collapse
Consensus is: yes, the hardware might support it, while software currently does not.
The sensor array likely completely covers a rectangular area but the coded area does not include the logo area. This might be hackable at the kernel layer.
I am using my GS4 running armband with my G2, it fits well actually but there is one MAJOR issue. The phone will NOT wakeup when double tapping the screen. It will however turn off when double tapping the status bar. Has anyone else gone running with their G2? If so how has it worked out and what armband are you using?
Be sure the proximity sensor isnt covered, if this is covered it doesnt listen, probably to prevent from turning on in your pocket.
wargreymon89 said:
Be sure the proximity sensor isnt covered, if this is covered it doesnt listen, probably to prevent from turning on in your pocket.
Click to expand...
Click to collapse
Yep...sounds like the culprit.
Sent from my Nexus 7 using Tapatalk 2
The ar band I am using doesnt cover it, I wonder if maybe its too thick and is possibly messing with the sensor?
KnockOn is also affected by the orientation of the phone. If it doesn't detect that it is in an appropriate orientation for typical phone use it will ignore the KnockOn feature.
Sent from my LG-D800 using xda app-developers app
zxrax said:
KnockOn is also affected by the orientation of the phone. If it doesn't detect that it is in an appropriate orientation for typical phone use it will ignore the KnockOn feature.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I have tested that, it turns on at all angles and even upside down. I don't think that is very accurate, even if LG advertises that. I am guessing my arm band is too thick.
TechSilver13 said:
I have tested that, it turns on at all angles and even upside down. I don't think that is very accurate, even if LG advertises that. I am guessing my arm band is too thick.
Click to expand...
Click to collapse
Anything touching the screen prolly jacks with it as well!
TechSilver13 said:
I have tested that, it turns on at all angles and even upside down. I don't think that is very accurate, even if LG advertises that. I am guessing my arm band is too thick.
Click to expand...
Click to collapse
Just got my international version yesterday and was really bummed to discover the same issue this morning.
It definitely has sonething to do with the proximity/light sensor next to the LED getting thrown off my the plastic of the armband view area.
I experimented by pressing the plastic flat against the phone and it then worked. Obviously not practical to try and do while running, but its a start. I imagine that, while not ideal, cutting a section from the armband window may help
Will post if I find something else