Good day to all Galaxy W, I've just notice when I installed AndroSensor that the light sensor of the galaxy w is not working, I've found similar threads that also discuss this problem and i think its more appropriate to post this issue in our forums section....
Some say's that it's a driver problem.. Any Help in fixing this problem will greatly improve the experience of using our galaxy W... by the way here's the thread that I've been talking about http://forum.xda-developers.com/showthread.php?t=1360881
by the way i'm very new in forums so please excuse me for being noob here..
dragz12 said:
Any Help in fixing this problem will greatly improve the experience of using our galaxy W...
Click to expand...
Click to collapse
I don't believe that it will "greatly improve" our experience, it is such an unnoticeable feature. I don't think it has ever worked, and I've to say, I don't think anyone even realises.
BUT, I'm sure Samsung will fix it with an update one day!
dragz12 said:
Good day to all Galaxy W, I've just notice when I installed AndroSensor that the light sensor of the galaxy w is not working, I've found similar threads that also discuss this problem and i think its more appropriate to post this issue in our forums section....
Some say's that it's a driver problem.. Any Help in fixing this problem will greatly improve the experience of using our galaxy W... by the way here's the thread that I've been talking about http://forum.xda-developers.com/showthread.php?t=1360881
by the way i'm very new in forums so please excuse me for being noob here..
Click to expand...
Click to collapse
Galaxy Wonder does NOT have a light sensor. It is detected wrong. It was supposed to be there in development stage, but later they decided to drop it. Unfortunately some manuals still say it is in the phone, but there isn't any.
fender90 said:
Galaxy Wonder does NOT have a light sensor. It is detected wrong. It was supposed to be there in development stage, but later they decided to drop it. Unfortunately some manuals still say it is in the phone, but there isn't any.
Click to expand...
Click to collapse
I thought it had the Sharp GP2A Ambient Light Sensor?
Which I _think_ is the same sensor used for proximity.
The Galaxy should have a light sensor. I asked Samsung and they responded saying, it definately has a light sensor. Also the number of sensors would be to many. Check yourself.
greets
THE-E
fender90 said:
Galaxy Wonder does NOT have a light sensor. It is detected wrong. It was supposed to be there in development stage, but later they decided to drop it. Unfortunately some manuals still say it is in the phone, but there isn't any.
Click to expand...
Click to collapse
There you are wrong. It has a light sensor and this sensor also worked in my SGW till the update from 2.3.5 to 2.3.6. The new firmware disabled it totally but it was working for sure, just not like it should.
The screen was dimmend when the sensor was covered but the brightness didn´t come back to the preset value. I managed to disable it by enabling it in the Quick Settings App and to enable it by doing the opposite in this Application.
So now it´s not working at all and I don´t care about.
I read an explanation that showed clearly that it didn't have any light sensor. Unfortunately it's in Italian, but for those who can understand it, here it is:
http://www.androidworld.it/forum/sa...sore-luminosit%E0-chiarimento-completo-34539/
To sum up what it says, we have a http://www.sharpsme.com/optoelectronics/sensors/ambient-light-sensors/GP2AP002S00F proximity sensor. 2 versions of this sensor exist, one with the light sensor, and one without it. We have the one without.
Some apps detect it as a light sensor because those 2 use the same drivers, but one lacks the light sensor while still having the proximity one.
Looks like fender90's Italian friends have done good work researching our device sensors.
I was on the right track with the Sharp sensor, and happy to have it clarified for us conclusively.
SGW has no light sensor. I don't see that as a problem though
Thanks for that fender90
Strange this is what our Samsung support in Germany replied:
Sehr geehrter Herr XXXX,
vielen Dank für Ihre Anfrage.
Im Samsung Galaxy W ist ein Lichtsensor eingebaut.
Bei weiteren Fragen können Sie uns gern kontaktieren.
Mit freundlichen Grüßen aus Schwalbach
i.A. Sara Kamps
Click to expand...
Click to collapse
It says: "A light sensor is installed in the SGW"
So who is right ?
Besides that, what are the senors in the front ?
Two sensor for proximity ?
greets
THE-E
I thinks the sgw has a light sensor 2 apps already saying that it has a light sensor.. and i really wish that samsung could fix it in the near future ^_^
dragz12 said:
I thinks the sgw has a light sensor 2 apps already saying that it has a light sensor.. and i really wish that samsung could fix it in the near future ^_^
Click to expand...
Click to collapse
Read my post, it explains why apps detect a light sensor
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I got your explanation fender, but Androsensor is a pretty extensive app, and it is in no doubt that there's a light sensor in there. Plus, how de we explain the TWO distinct probes to the left of the speaker?
Sent from my GT-I8150 using XDA App
Well, I also have read in different places around the web (and heard in a video review) that our beloved phone DOESN'T HAVE a light sensor.
A good indication of this is that you can't set the LCD brightness to "AUTO".
What the italian guy has said is true.
2g11 said:
Plus, how de we explain the TWO distinct probes to the left of the speaker?
Sent from my GT-I8150 using XDA App
Click to expand...
Click to collapse
Exactly. There are TWO of them. One is the proximity sensor and the other the light sensor. And like said it worked for me with 2.3.5, but not like supposed to be.
So either Samsung can´t fix the issue with it or is to lazy to do that and so it´s easier to say now there is no sensor. The old datasheet also was mentioning the light sensor but after the update to 2.3.6 was aviable, they removed it in the new datasheet, as their 2.3.6 ROM does not support it anymore.
banelicious said:
A good indication of this is that you can't set the LCD brightness to "AUTO".
What the italian guy has said is true.
Click to expand...
Click to collapse
There was an AUTO option in 2.3.5 which dissappeared after updating to 2.3.6
So before just beliving what is now told by Samsung or other pages, use your own brain. Get an older 2.3.5 ROM, flash it and see yourself.
honeyx said:
Exactly. There are TWO of them. One is the proximity sensor and the other the light sensor. And like said it worked for me with 2.3.5, but not like supposed to be.
So either Samsung can´t fix the issue with it or is to lazy to do that and so it´s easier to say now there is no sensor. The old datasheet also was mentioning the light sensor but after the update to 2.3.6 was aviable, they removed it in the new datasheet, as their 2.3.6 ROM does not support it anymore.
There was an AUTO option in 2.3.5 which dissappeared after updating to 2.3.6
So before just beliving what is now told by Samsung or other pages, use your own brain. Get an older 2.3.5 ROM, flash it and see yourself.
Click to expand...
Click to collapse
I was in a hurry before so I couldn't better argument my knowledge so far.
I bought the phone in mid-December, and it came with GB 2.3.5.
All the video reviews I saw pointed out that indeed there was the option to set the brightness to AUTO, but it was not working, thus suggesting that a light sensor is not present.
The first thing I checked was obviously that fact (as I think that the autodim feature is a HUGE battery saver).
To my great disappointment, while still on GB 2.3.5, the option for "auto" was there, but it was not working at all.
After updating to 2.3.6, the option is long gone.
So what we have now:
- Websites telling both that either the sensor is not present OR is it present but not working.
- Samsung that keeps changing position about the issue (and believe me, I don't trust anyone from the customer support, never)
- Apps that are supposed to use the light sensor are not working.
So either way, we're stuck with a gimped phone.
(I checked the user manual that came with my phone and nowhere it mentions a light sensor, but just the proximity one)
I simply think they still didn´t fugure out how to get it working correctly. Might be just a driver issue or hardware related. Don´t know. But I was able to disable it in 2.3.5 and the proximity sensor still worked fine.
honeyx and 2g11,
There is no light sensor in our GP2A module. I'm on 2.3.5 and I have the auto option, it doesnt work, the auto option should not have been there, Samsung forgot to remove it, and in 2.3.6 they did.
GP2A looks like this..
If you look on your phone, to the left of the top speaker you can see two holes or dots, which is the same as in this picture.
If we had THREE holes, we would have the light sensor too.
As both are called GP2A, they both use the same driver for Android, so all apps and system checkers are telling us its there, but only as the driver allows for it, but PHYSICALLY, it is not there.
You can't make up a software based light sensor without some hardware.
So to end this topic and chat, i8150 DOES NOT HAVE A LIGHT SENSOR.... EVER!
Well. This is the GP2A sensor obviously in a iPhone. There is just one round hole for both.
And this is the GP2A sensor used in a samsung i9000. Again different to the two ones in your pic. (at least the distances are not the same)
So well, you can even use one sensor for both and there are obviously more than two types of the GP2A sensor. Also a light sensor allone can also act as a proximity sensor.
So maybe you are right or maybe the SGW uses a different newer GP2A sensor that just needs two probes.
Like I said at the beginning I don´t care that much it´s there but not working or it´s not there.
It looks the same to me...
Showing the GP2A with 3 "holes" for Proximity and Light.
Ah ok. Was looking at the bigger part. LoL. So yes it´s looking the same in the I9000, but the iPhone seems to use a totally different sensor with just one probe for both, though they claim it´s also a GP2A sensor.
Related
------------UPDATE------------
This issue has been solved: this is a hardware error. I ended up having to send my phone back to HTC for warranty repair. They replaced the main board and now the phone works again.
------------END UPDATE------------
I'm offering a $50.00 (USD, via PayPal) reward to the first person who figures out a fix for the microp error that is causing some Diamonds to lose the screen backlight.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After getting the microp error, the screen backlight no longer functions, and I also recently noticed that Wi-Fi cannot be enabled.
More details on the microp error here:
http://forum.xda-developers.com/showthread.php?p=3026104
Like I said - $50 for the solution. Thanks to all in advance!
why not to try installing new os(rom)?
intel286 said:
why not to try installing new os(rom)?
Click to expand...
Click to collapse
Because that doesn't work, it's been tried.
I suggest taking the phone back on warranty instead of paying to have HTC's software bugs fixed.
1. take a towel put it on the ground and htrow the htc diamond carefully sometimes on it
2. take out the battery do a little bit heavy pressure on the device where usually the battery would be.
3. bridge battery connectors of the device "WHILE BATTERY IS NOT INSERTED" with screwdriver
4. leave the battery out for a while. ( some hours)
should be caused by some connectors that dont work properly anymorei nside the diamond ? did it fall on the floor ?
cross fingers
alphazero said:
1. take a towel put it on the ground and htrow the htc diamond carefully sometimes on it
2. take out the battery do a little bit heavy pressure on the device where usually the battery would be.
3. bridge battery connectors of the device "WHILE BATTERY IS NOT INSERTED" with screwdriver
4. leave the battery out for a while. ( some hours)
should be caused by some connectors that dont work properly anymorei nside the diamond ? did it fall on the floor ?
cross fingers
Click to expand...
Click to collapse
I did it about three or four times - but without towel I was little bit angry so did it my way
If I remember it well - on the beginning the display was only dark, but I could use my Diamond, but after the fourth "throw" display didn´t work no more
Edited: But this wasn´t only problem - it started with wi-fi connection - I was unable to switch the wi-fi on and then the "reset" button stopped its work..
alphazero said:
1. take a towel put it on the ground and htrow the htc diamond carefully sometimes on it
2. take out the battery do a little bit heavy pressure on the device where usually the battery would be.
3. bridge battery connectors of the device "WHILE BATTERY IS NOT INSERTED" with screwdriver
4. leave the battery out for a while. ( some hours)
should be caused by some connectors that dont work properly anymorei nside the diamond ? did it fall on the floor ?
cross fingers
Click to expand...
Click to collapse
Err... This is a SOFTWARE problem.
http://www.gizmodo.com.au/2008/12/htc_touch_diamond_backlights_permanently_dying_no_fix_yet-2.html
No, it's a hardware problem. I think it's caused by big temperature shifts, creating condensation on a part of the diamond. It only occurs in a very few diamonds, probably leaving a hot house to cold? You live in Canada or something? I doubt it is a software problem as it would be in much more diamonds.
I don't know, maybe putting it in the freezer may work? Well it worked when my hard drive killed itself, maybe it'll work on diamond too?
here is exactly what happened when my phone stopped working:
i was in my apartment with my phone, it was sitting on my desk.
i went outside and walked over one block - it wasn't even cold outside (50-60f?).
i pulled out the phone, unlocked it, went to the photo tab, started the camera, and took a photo.
after taking the photo, i sent it via sms.
when i tried to click back to take another photo, the phone said "cannot start camera"
i used reboot manager app to reboot the phone.
when the phone started, the backlight was no longer working and i was given the "microp error" screen.
since then, my backlight doesn't work, no matter what i try.
the phone was never dropped. there was no significant change in temp. etc. - it was working fine one min, then after a reboot it stopped working.
I have read about this in a lot of different Phone Expert articles...boy Genius, ect....here is just one....They say HTC does not have a fix for it yet
http://www.gizmodo.com.au/2008/12/htc_touch_diamond_backlights_permanently_dying_no_fix_yet-2.html
theorie said:
here is exactly what happened when my phone stopped working:
when i tried to click back to take another photo, the phone said "cannot start camera"
when the phone started, the backlight was no longer working and i was given the "microp error" screen.
since then, my backlight doesn't work, no matter what i try.
Click to expand...
Click to collapse
yes this is a hardware problem. I faced the exact same problem with HTC Touch : camera not working, then screen fading to black forever
Had to replace the screen and everything went back
(for a hardware issue, you need a hardware change, a soft fix will never do much)
Pumpiron579 said:
I have read about this in a lot of different Phone Expert articles...boy Genius, ect....here is just one....They say HTC does not have a fix for it yet
http://www.gizmodo.com.au/2008/12/htc_touch_diamond_backlights_permanently_dying_no_fix_yet-2.html
Click to expand...
Click to collapse
they got that tip from me. i showed them my phone when they hosted Gizmodo Gallery here in new york this past weekend.
the reason gizmodo said HTC does not have a fix - is because i told them that. i called numerous HTC tech support numbers and every tech i spoke to said the same thing, "sorry we have no idea, and can't help"
they're talking about me (Tom)...haha
theorie said:
they got that tip from me. i showed them my phone when they hosted Gizmodo Gallery here in new york this past weekend.
the reason gizmodo said HTC does not have a fix - is because i told them that. i called numerous HTC tech support numbers and every tech i spoke to said the same thing, "sorry we have no idea, and can't help"
they're talking about me (Tom)...haha
Click to expand...
Click to collapse
But if HTC can't fix it, they'll have to replace it, right? You have warranty?
theorie said:
they got that tip from me. i showed them my phone when they hosted Gizmodo Gallery here in new york this past weekend.
the reason gizmodo said HTC does not have a fix - is because i told them that. i called numerous HTC tech support numbers and every tech i spoke to said the same thing, "sorry we have no idea, and can't help"
they're talking about me (Tom)...haha
Click to expand...
Click to collapse
Interesting. That has spread quite fast to a lot of other Forums.
WOW
guess what...
tonight i left my apt, got on the subway, and after i got off i went to check my phone - out of nowhere, THE SCREEN BACKLIGHT IS WORKING AGAIN!
wtf!??!
i haven't done ANYTHING to the phone today. it sat on my desk all day. so why the heck did the backlight start working again?!?
now, it seems the phone has fixed itself! i haven't done anything to it! when i left my apt, it wasn't working, and 15 minutes later, it's working agian.
very, very strange.
apparently i owe the phone-gods $50. thanks phone-gods. haha
Congrats man
If I only had so luck like You I´m still waiting for some info from service center where I sent my Diamond. But right - 1 month ago messages on forums about this prob were very rare - on last saturday when my PDA "died" I was searching for any info (and found few topics about that) and when I´m looking for it today there are much more responses to this error on internet...it seems that this issue has arisen in last few weeks
Nice to hear that, looks like what ever hardware was playing up has decided to play nice It's just temperature shifts I think from what i've heard from lots of people with this problem. Moisture forming inside the PDA. Or so I think
But my Diamond didn´t fix itself for 3 days..... Unfortunatelly after that I couldn´t do anything more than to send it for repair
Ok so today I got a message from our HTC service centre that they have found HW problem, changed display and the whole front panel n sending my Diamond back to me
And it was classified like a standard warranty repair
tommm said:
Ok so today I got a message from our HTC service centre that they have found HW problem, changed display and the whole front panel n sending my Diamond back to me
And it was classified like a standard warranty repair
Click to expand...
Click to collapse
What country do you live in and where did you send your device to (which repair centre) ?
In Holland official HTC support sends it to Eurotwice in Belgium. I had the same microp error and when I got it back, the problem was still there. Eurotwice couldn't find any problem.
So I'm curious where you sent your device.
Also look at this post: http://forum.xda-developers.com/showpost.php?p=3048690&postcount=1
It metnions that the bootloader displays a microp version. My bootloader never displays this.
For Microp ERROR
Hello,
Im in france "FRENCH", if you leave in france and your diamond have a MircropERROR no probleme you can contact me i can repair it.
@+++
A moderator over at the nokiausa.com forum is asking people to PM him details about phones that have the "purple tint" screen issue. His name is Kosh and he can be contacted HERE. He wants a PM with very specific information. He says to PM the following information...
Kosh said:
ref; Purple_tint
Device model:
Device IMEI number:
OS version:
firmware revision :
Hardware revision :
a short but detailed desctiption of your experience with this
You will find this information in Settings > About > more information
Click to expand...
Click to collapse
He made this request in a thread about the "purple tint." Just create an account and PM Kosh the requested information in a succinct message. Hopefully they will figure out what is going on.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The image on the left is medium brightness and the image on the right is the same phone on low brightness. The "purple tint" issue goes far beyond a different color keyboard while texting. The entire screen is affected no matter what you are viewing.
Update: I exchanged my phone
I exchanged by black Lumia 900 for a white Lumia 900. The new phone does not have the purple tint issue. It took some work to find a phone that doesn't have the issue. I had to go to three seperate at&t corporate stores over the course of three days.
The first thing I did at each location is walk in and set all the Lumia 900 display phones to LOW brightness. I then set my phone to LOW brightness. I then started a new text message on each phone and compared the keyboards. Most of the time the display phones will not have the purple issue or you may find 1 out of three with the issue.
Next tell the sales staff what the issue is with your phone. Every place I went into this week had no clue about the purple screen issue. Most people will be pretty accommodating and will easily do one swap out without any fuss. Unfortunately you may also encounter some people that will tell you that the purple keyboard in the text messaging screen is just a "feature." All you have to do is politely point out all their display models do not have this "feature."
Unfortunately in my neck of the woods there are a lot of Lumia 900s with the purple screen issue. So you may have to go through 3 phones at a location before you find one that functions as expected. Usually you will be told after two phones and certainly after three phone swaps they no longer have any in stock. I suspect in a lot of cases that is a lie but what are you going to do? Move on to the next location.
Try different colors. Be flexible. I went though something like 6 black phones before I tried a white one. The white one didn't have the issue. As the poll indicates there are problems across the product line. But it doesn't hurt to switch it up just for fun.
Interestingly the white phone I picked up this week did NOT have a green dot on the box. It had the latest firmware. I don't know if that means anything.
The phone on the left is medium brightness. The phone on the right is low brightness. The color balance on my digital camera which I used to take these pictures was not calibrated perfectly for the lighting conditions. I can assure you though there is no obvious color cast on the screen at both settings. Problem solved.
One rather unfortunate thing happened during this saga. I went to the at&t corporate store located at 172 Deming St Manchester, CT. As usual when I walked into the store they had no clue about the purple screen issue. The salesman that helped me out did a full exchange BEFORE checking the screen. When he finally fired up the screen and checked it it was purple. I wandered off to give him a chance to rectify the problem. I believe he checked another phone and it had the same problem. The first issue is they should not do all the paperwork for the exchange before confirming everything works as expected. It's a waste of time.
After his first mistake the next thing the guy did was finally come back and feed me this BS story...
The white male sales clerk, who shall remain nameless, with a straight face told me he did some checking and that a message had gone out to managers that this is a known issue and that Nokia is working on a firmware fix that should be out in less than a month. So this guy went from never hearing about the issue when I walked through the door to knowing exactly what the problem is and what the fix will be. Anyone else hearing this story or did I get filled full of bologna?
Anyway who knows what the issue really is. My philosophy is either return the phone and pick up a product from a different manufacturer or go out and aggressively try and find a working Lumia 900. I suspect once word gets back to corporate that people are coming in and trying out 3-4 different phones they are going to clamp down and start giving people BS about a "firmware update."
Thanks for the info. I was going to buy a Nokia Lumia today but after reading I guess I will wait
My friend has this same problem on her cyan Lumia 900. The screen was fine before the firmware update and just afterwards the screen turned to the purplish hue. :/
Definately interesting here as I too follow the Nokia Discussion-US Board forums, and my first White L900 had this purplish hue at the Low Brightness settings...
So I went to another AT&T Corp store and made sure that my second exchanged unit (White) did not have this purplish hue...making sure the store personnel were aware that I would also return this unit if it indeed displayed the issue after updating to the latest firmware: 2175.1002.8112.12084.
They documented my account for this: Updated through Zune went I got home and all was fine...no purplish hue.
However other issues still remain, and hopefully Nokia will rectify these troubling issues with an upcoming firmware update...
Has anybody tried re-flashing their phones to eliminate this issue? I went through six phones with a rattle before finding one that did not rattle. It has the purple issue, so guess what, I'm dealing with it. I rather an issue I can fix by changing the brightness than one that sounds like it's ticking when it vibrates. Lol.
This is definitely driver related guys. Take your phone, turn it to auto if you have the issue. Let it mess up the colors. Put your phone to light so it changes its brightness. Go back into darkness so it goes to low again. & your low setting will be normal colors.
Sent from my Lumia 900 using Board Express
FiyaFleye said:
This is definitely driver related guys. Take your phone, turn it to auto if you have the issue. Let it mess up the colors. Put your phone to light so it changes its brightness. Go back into darkness so it goes to low again. & your low setting will be normal colors.
Sent from my Lumia 900 using Board Express
Click to expand...
Click to collapse
on mine, allowing it to go to bright in light, then low in dark does NOT fix the problem.
But I agree, its probably software related. If it started happening after the firmware upgrade for some than it has to be software.
Nokia just responded to me on twitter, check wpcentral.com for the story as I made them aware of the tweet
Sent from my Lumia 900 using Board Express
Just saw the info on twitter. You should post a URL for those who may have trouble finding it...
Sent from my Lumia 900 using Board Express
Also, lets hope this isn't a software workaround for a hardware problem!
Sent from my Lumia 900 using Board Express
Called Rogers Corporate support today for some un-related stuff...
Asked about the purple screen, they said this "isn't a normal issue, and they are not aware of it, if you experience it, you should replace your phone as it sounds like a hardware issue, and we haven't heard of any other users experiencing this"...
How are they not aware of it?
You're asking people who read off scripts... Not all of them are knowledgeable
Sent from my Lumia 900 using Board Express
WPCentral.com is reporting today (May 7th) that Nokia have found the source of the problem (firmware) and will be posting a patch 'soon'.
What if my phone doesn't have a problem?
drtolson said:
WPCentral.com is reporting today (May 7th) that Nokia have found the source of the problem (firmware) and will be posting a patch 'soon'.
Click to expand...
Click to collapse
What I find curious about this is why did I have two phones with the same "firmware" but only one phone was affected? I am not an electrical engineer or computer scientist. Does this pass the sniff test with you guys?
Secondly if my phone is okay now with the current hardware/firmware combination... what will a "fixed" firmware do to my phone? Is the firmware "fix" just removing the low brightness option from ALL phones?!
Same reason not all of us suffered the connection bug, so you're obviously congested. It could be a simple driver error.
Sent from my Lumia 900 using Board Express
sitizenx said:
What I find curious about this is why did I have two phones with the same "firmware" but only one phone was affected?
Click to expand...
Click to collapse
Yep, you're absolutely right. It looks like Nokia is trying to minimize their potentially loss (because of defective screens) by firmware fixes. My replacement is on the way from Amazon Wireless (fortunately I have no problem at all with AmzWL - they just said "sorry" and send me a new phone). Hope that one will be fine.
However, I'm very upset of poor Lumia 900 quality, never expected from Nokia Too many problems for the "flagship" WP7 handset: "purple tint", "purple spot", short battery life with 4G/LTE, poor/noisy camera quality in low light etc. and so on... Never had that kind of problems with my old good "cheap" (he-he - see stupid topic in WP7 "General" forum) Samsung Focus!
sitizenx said:
What I find curious about this is why did I have two phones with the same "firmware" but only one phone was affected? I am not an electrical engineer or computer scientist. Does this pass the sniff test with you guys?
Secondly if my phone is okay now with the current hardware/firmware combination... what will a "fixed" firmware do to my phone? Is the firmware "fix" just removing the low brightness option from ALL phones?!
Click to expand...
Click to collapse
one scenario could be they may have used a part from two different suppliers that turned out to be mildly different. A firmware update would detect the different part and adjust the color output depending on the detected part (whatever it may be)
FiyaFleye said:
Same reason not all of us suffered the connection bug, so you're obviously congested. It could be a simple driver error.
Sent from my Lumia 900 using Board Express
Click to expand...
Click to collapse
I was not around for the connection bug so I cannot speak to that.
Some people were saying that the N8 had a similar issue with the physical screen that required actual replacement. That was my understanding anyway.
Did I get bad information?
hash008 said:
Re: Nokia n8 display issue - purple screen
Options
26-May-2011 08:47 AM
Hello Everyone,
I had the Purple Screen Issue. And I got the confirmation from reliable sources that the issue is with the hardware (Display itself) and not with the software/ firmware.
Click to expand...
Click to collapse
I mean, its pretty obvious that firmware problems can cause this. Maybe whoever supplied the screens changed something so minor during the production process that causes this. Or maybe a ROM on their servers was corrupted. For a company that just handed out $100 to every owner, regardless of issues or not, well after a fix was available, I doubt they would have any sort of conspiracy theory. They're focused on mindshare & satisfaction, they wouldn't try to screw you.
Sent from my Lumia 900 using Board Express
Hi,
Am from India, and am observing a screen flex on my HOX. When I press at the corners of the screen I see very annoying screen flexing effect. My device serial number starts with HT24. And I havent observed this problem in the units with serial number HT23. Is there some defect in this particular HT24 lot ???
Do anyone observe this problem?? Please let me know.
chaithubk said:
Hi,
Am from India, and am observing a screen flex on my HOX. When I press at the corners of the screen I see very annoying screen flexing effect. My device serial number starts with HT24. And I havent observed this problem in the units with serial number HT23. Is there some defect in this particular HT24 lot ???
Do anyone observe this problem?? Please let me know.
Click to expand...
Click to collapse
The problems are present in all batches. I had it on my first phone and replaced it the next day.
Just take your phone to a HTC service center get a DOA certificate and exchange the phone in the shop where you bought it from.
its pretty well explained on this forum
if the screen is physically moving on pressure ie up and down, its a defect
if you mean LCD ripple on out edge pressure, its in most of them, unless its very bad, its ok it gets less with time
saranyan said:
The problems are present in all batches. I had it on my first phone and replaced it the next day.
Just take your phone to a HTC service center get a DOA certificate and exchange the phone in the shop where you bought it from.
Click to expand...
Click to collapse
- Thanks for the information.
I had visited one of the service center here, and when I showed them the mobile, they said it will be common for all LCD screens. So, I just re-checked in one of the outlets here and observed no issues in the demo One X mobile present in the stores.
And it is worsening day by day. So, I have decided to return the phone. After we return the Phone HTC will give me a DOA certificate ? Or, service center people are authorized to do that ?
Am out of one month period after purchase, then it might not be possible to get a replacement ?
chaithubk said:
- Thanks for the information.
I had visited one of the service center here, and when I showed them the mobile, they said it will be common for all LCD screens. So, I just re-checked in one of the outlets here and observed no issues in the demo One X mobile present in the stores.
And it is worsening day by day. So, I have decided to return the phone. After we return the Phone HTC will give me a DOA certificate ? Or, service center people are authorized to do that ?
Am out of one month period after purchase, then it might not be possible to get a replacement ?
Click to expand...
Click to collapse
In India its a 14 day replacement period. Now they can only repair your phone, Go to the service center tell them that the issue is not there on all devices. They must and should repair your device otherwise call up the customer care and complain to them.
hamdir said:
its pretty well explained on this forum
if the screen is physically moving on pressure ie up and down, its a defect
if you mean LCD ripple on out edge pressure, its in most of them, unless its very bad, its ok it gets less with time
Click to expand...
Click to collapse
Hamdir, what do you means about "if the screen is physically moving on pressure ie up and down"? Can you show it with a video?
hamdir said:
its pretty well explained on this forum
if the screen is physically moving on pressure ie up and down, its a defect
if you mean LCD ripple on out edge pressure, its in most of them, unless its very bad, its ok it gets less with time
Click to expand...
Click to collapse
Are you telling me this is normal on the one x?
This is really bad. Am facing similar kind of behaviour but the flex was not so prominent like what you shared, now I feel that if I don't take a necessary action It may get worse.
And I do find a click sound on right bottom corner of the phone. This all feels like some problem in screen lamination.
Did you replace your mobile ?
Sent from my HTC One X using XDA
Chad_Petree said:
Are you telling me this is normal on the one x?
Click to expand...
Click to collapse
That really bad...
echo_rc said:
That really bad...
Click to expand...
Click to collapse
Did any one got a replacement (or got the problem solved ?) after sending the "HOX suffering from Screen Flex" to htc service center...
I am planning to send my HOX for service and wonder whether HTC can fix this up or will they send back with problem???
i also had a similar problem here is the video and my batch started with SH24WW
http://www.youtube.com/watch?v=eYX8s41L694&feature=plcp
so was mine a defected unit or its suposed to be like that either way i returned my one x and im never geting a HTC
You haven't got the reply from HTC ? Is that what you are referring to?
Sent from my HTC One X using XDA
chaithubk said:
Did any one got a replacement (or got the problem solved ?) after sending the "HOX suffering from Screen Flex" to htc service center...
I am planning to send my HOX for service and wonder whether HTC can fix this up or will they send back with problem???
Click to expand...
Click to collapse
Yes i get replacement for my hox but i still have the flex and still waiting for the good batch for another replacement
echo_rc said:
Yes i get replacement for my hox but i still have the flex and still waiting for the good batch for another replacement
Click to expand...
Click to collapse
Do HTC acknowledge this Screen Flex issue ? (Like Wi-Fi issues)
If they acknowledge we can be sure that, we can get the problem solved when we send it for service.
How to bring this up to HTC notice ??? Any senior XDA member route this thread to HTC notcie... !
(Like, someone did it for showcasing the Wi-Fi gripping problem).
You can read this http://crave.cnet.co.uk/mobiles/htc-one-x-screen-flex-flaw-we-would-never-let-that-ship-50007596/
echo_rc said:
You can read this http://crave.cnet.co.uk/mobiles/htc-one-x-screen-flex-flaw-we-would-never-let-that-ship-50007596/
Click to expand...
Click to collapse
HTC's Quallity Control lately is awful insted of quiently brilliant its quiently crapy and this is coming from a big htc's fan
SGS3's are being reported with hairline cracks on the bezel that surrounds the front of the phone when they're taken out of the box.
Some also have gaps on the left side where the display meets the body of the phone and it collects dust.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The display also cracks easily under stress.
Here's the difference between One X owners and SGS3 owners. People on the SGS3 forum realize any device produced in the millions means a certain percentage are going to have issues. On the One X forum everyone screams like Chinese tree monkeys and starts a poll every time an issues's discovered. My HT23 has been perfect since I got it. I'm assuming it's not the only one. And God, please don't respond "but the One X has more issues than the SGS3." Any evidence of that is purely based on the chatter between users on this forum which is the most emotional I've ever seen on XDA.
BarryH_GEG said:
SGS3's are being reported with hairline cracks on the bezel that surrounds the front of the phone when they're taken out of the box.
Some also have gaps on the left side where the display meets the body of the phone and it collects dust.
The display also cracks easily under stress.
Here's the difference between One X owners and SGS3 owners. People on the SGS3 forum realize any device produced in the millions means a certain percentage are going to have issues. On the One X forum everyone screams like Chinese tree monkeys and starts a poll every time an issues's discovered. My HT23 has been perfect since I got it. I'm assuming it's not the only one. And God, please don't respond "but the One X has more issues than the SGS3." Any evidence of that is purely based on the chatter between users on this forum which is the most emotional I've ever seen on XDA.
Click to expand...
Click to collapse
Sure that you are right there is no phone without issues or a manufactor without manufacturing issues but c'mon i my self had an headache because of the one x man too many problems im not saying that the s3 is without issues but i hope its not like with the one x man does that phone have issues and one thing with any phone or device (tablet,pc,laptop..etc) there is a chance to get a defected one but with the htc one x its the way around,there is a chance that you'll get a working phone but mostly thats not the case and you get a "defected one".Mine had screen flex issues and also ripple and flickering also 2 days after using the phone startet to get yellow spots and it overheated a lot and the battery sucked i tried 3 devices and all had similar issues mostly screen flex overheating and bad battery life you cant call the last one a defect or an issue but for me it is hope the galaxy s3 is better if not then apple here i come (iphone 4s)
Mine had screen flex before it some how went away. Didn't do anything just used it. It wasn't very bad to begin with though. I won't be pushing so hard on my display anyway. Its capacitive, no need for all the pressure. But thats just me. :laugh:
Mine has the same issue on both the corners. I wont consider this as an issue as long it dose not get worse. mine is just 2days old and i have already rooted it and i am running the phone on insertcoin ROM. I am little concerned about this issue getting worse in the future. But now that i have rooted it the question is will the HTC service center replace my phone? I live in India (Bangalore). Has any one from India had luck in getting their phone replaced after rooting and installing a custom ROM and then restoring it to the stock ?
I have an issue with the network drop as well. if i move in to a place where there is no network and then come back to a place where i can get a complete network the phone still wont connect. i will either have to restart it or will have to switch on the airplane mode and switch it off. This is a little annoying as i really cant keep checking my phone for the network connectivity. And this is not a rare case i have seen a lot of other people complaining on the same issue. Now i get this flex issue too Not really happy with the phone as it should not have the very basic problems as the network connectivity Common HTC do something about this.
My phone is showing gray static with dots. Is the flex cable the root of the problem? The problem will disappear when I slide down the gamepad but comes back again when I slide it inside again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(c)PyroKirby (It's the same as my phone screen)
Is the flex cable is the problem?
Yes I'm 99.9999% sure its the flex cable
Sent from my ATT Samsung Galaxy SIII using TapaTalk
This is a classic sign of flex cable problem. So, yes.
Take it from me who has had 5 flex cable replacements for my Play.
I've got the same problem today....what do i do now...plsss hellpppp!!!!!!
You need to buy a flex cable and replace it
Broken flex cable. Buy a new one and replace it.
Strangest problem with camera
olokos said:
Broken flex cable. Buy a new one and replace it.
Click to expand...
Click to collapse
hi guys..thanks for replying..it was indeed a flex cable problem..i managed to replace the flex cable with a friend's help and by following youtube vids..now although my slider and screen are back to normal I've a strange and peculiar problem of which i never heard of and still couldnt find any solution to..my camera app is acting totally weird ..it can record a video and play it but it cant take a pic..i mean it appears to click a pic..but i can't review it and it doesn't even appear anywhere in the gallery( unlike the vid )..and whats more strange is the front cam takes pics and saves in the sd only the rear cam is having the problem and also the camera app becomes unresponsive afterwards...
list of stuff i check
1.checked with different sd cards
2. tried other camera apps..same result
3. changed roms/kernels
4.fully re-flashed stock re locked bootloader
i even checkd with the xperia diagnostic tool ..all the sensors..touches..touchpads ..evrythings working..but whenever i click on camera it fcs.
Please please help me out!!!:crying::crying:
I'd try to dissasemble the phone yet again and make sure that you haven't messed up any of the connections. Those cables are really tiny. Also check whether one of them is not broken. When I replaced my flex cable the digitizer cable got a small crack. Had to buy a new one. My friend actually messed up and I have no idea whether he broke it or it broke by itself, so check that.
Please remember to reply with quotes so I'd get a notification about it
Olokos is right. You must have missplaced flex cable from rear camera while reassembling. Just open it again, but only lower part (where motherboard is, should be easy), and remove and instert camera flex cable again
Bakisha said:
Olokos is right. You must have missplaced flex cable from rear camera while reassembling. Just open it again, but only lower part (where motherboard is, should be easy), and remove and instert camera flex cable again
Click to expand...
Click to collapse
Hi,thanks for replying man.I checked the camera flex was already inserted properly ..still re-did it but didn't work.
I guess iwill have take it to Sony service center tmorow.Btw do i need to re lock the bootloader before i hand over the phone to the service center right?
eddynoob said:
Hi,thanks for replying man.I checked the camera flex was already inserted properly ..still re-did it but didn't work.
I guess iwill have take it to Sony service center tmorow.Btw do i need to re lock the bootloader before i hand over the phone to the service center right?
Click to expand...
Click to collapse
I guess it would be good idea to flash Stock firmware and relock bootloader if you know how (i don't).
Sent from my C6502 using XDA Free mobile app
Bakisha said:
I guess it would be good idea to flash Stock firmware and relock bootloader if you know how (i don't).
Sent from my C6502 using XDA Free mobile app
Click to expand...
Click to collapse
hehe u r kidding right?.....cuz i know you dev people are geniuses
anyway here's that thread http://forum.xda-developers.com/showthread.php?t=1134334..
..so i just got back frm the service center..missing my xplay already.
The service guy was as confused as me when i showed him the problem and yes i relocked the bootloader before giving the phn to them..actually few months back a friend's phone was rejected a paid service cuz he had his bl unlocked ..i dont know why ..but they use seus or emma tool maybe to flash stock fw to solve the common users software problems ..i think thats their preliminary to troubleshoot a device,and also seus displays "the user has modified the device' or something similar kind of message so i did it just to be safe...hope they find out whats wrong with my phone and fix it...
eddynoob said:
hehe u r kidding right?.....cuz i know you dev people are geniuses
anyway here's that thread http://forum.xda-developers.com/showthread.php?t=1134334..
..so i just got back frm the service center..missing my xplay already.
The service guy was as confused as me when i showed him the problem and yes i relocked the bootloader before giving the phn to them..actually few months back a friend's phone was rejected a paid service cuz he had his bl unlocked ..i dont know why ..but they use seus or emma tool maybe to flash stock fw to solve the common users software problems ..i think thats their preliminary to troubleshoot a device,and also seus displays "the user has modified the device' or something similar kind of message so i did it just to be safe...hope they find out whats wrong with my phone and fix it...
Click to expand...
Click to collapse
Please ask them what happened after they fix it. It's really interesting
olokos said:
Please ask them what happened after they fix it. It's really interesting
Click to expand...
Click to collapse
@olokos haha ya sure..even m really curious to know....but theres a bit of info that i think could be imp and im sorry i missed out on that while i posted here at the first place...the thing is that since i didnt get the flex cable individually anywhere so i ordered the whole slider board from ebay
http://www.ebay.in/itm/New-Flat-Cab...ny-Ericsson-Play-R800-Phone-OEM-/281330850312.
my friend who helped me fix the slider flex cable replaced that whole part and took the front cam and its flex from the old one and attached to the new one cuz the new one was missing the front cam..and after putting up the phone together during the first time front cam was inverted and rear wasnt working,so he reopened and placed the front cam correctly to get it right..
and as I posted before the front cam is working fine since then...so could it be in any way the real problem behind my back camera not functioning.
...
and i didnt mentioned all these to service guy
New problem
hi all..
bad news ..i got it back frm service center today..they couldn't get it fixed..said there might be a problem with the eeprom ac or the circuits near to it (idk what it means)..then i thought to myself i can live without the cam and brought the phone home..now upon charging the screen is getting ghost touches i mean the touch screen has gone automatic since i switched it on..( though the ts was working fine when i tried it in service center)...
whats possibly wrong with it now.??..pls help guys..
eddynoob said:
they couldn't get it fixed..said there might be a problem with the eeprom ac or the circuits near to it
Click to expand...
Click to collapse
whereas I know what are the circuits I've got no idea what do you mean by eeprom "AC".
olokos said:
whereas I know what are the circuits I've got no idea what do you mean by eeprom "AC".
Click to expand...
Click to collapse
@olokos .. i have zero idea about circuits man..i just wrote what the service guy told me.....
can u pls tell me me about the touchscreen problem that m facing currently..the screen behaves like it being pressed all the time..this happens randomly though but more when charging
eddynoob said:
@olokos .. i have zero idea about circuits man..i just wrote what the service guy told me.....
can u pls tell me me about the touchscreen problem that m facing currently..the screen behaves like it being pressed all the time..this happens randomly though but more when charging
Click to expand...
Click to collapse
I also had this problem. I can't tell for sure where the problem is, but I'd suggest you to take a really close look at the digitizer flex cable.
My HTC 10 32GB grey from Taiwan can't read any of my NFC cards, which my LG G4 has no problems with.
However, the 10 can do NFC Android beam with the G4 just fine.
Over at the Taiwanese forums, most users can't get their 10 to read NFC cards too.
I'm using the latest 1.30 ROM.
Any ideas?
What NFC App do you use?
I can read nfc cards with the HTC 10 w/o any problems, the sensor is at the top, placed at the camera.
My USA unlocked HTC 10 can't read my Suica card using the https://play.google.com/store/apps/details?id=yanzm.products.suicareader&hl=en app but my old phone can. So I too am having NFC problems!
My USA Verizon branded phone does Android beam no problem but will not read any tags. I have a Sony camera with a factory embedded NFC tag it won't even acknowledge. HTC clearly has something screwed up with NFC.
Sent from my HTC6545LVW using Tapatalk
My unlocked HTC 10 Connects nexus 5x and my Sony soundbar via NFC just fine.
Sent from my HTC 10 using XDA-Developers mobile app
Works for my taiwanese phone with NFC Tools
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Im also having issues with the HTC 10 not reading NFC tags.
I have come from the HTC M8 which worked flawlessly with my NFC tags. As soon as it was within range of a tag, it would read it effectively.
Now with the HTC 10, I'm putting the phone close to the NFC tag and..... nothing. No beep, no nothing. I'm having to sit there and wave the phone around for a good 30 seconds before the phone even recognizes that there is a NFC tag near by, and even then, it doesn't read it properly. It takes a good 2-3 tries to get it to read an NFC properly.
I'm hoping it is just a DOA device, so am putting a warranty call into my telco to have the phone replaced (since I purchased it from them directly).
Unless there are some other troubleshooting steps I could try ?
TRLOS said:
Im also having issues with the HTC 10 not reading NFC tags.
I have come from the HTC M8 which worked flawlessly with my NFC tags. As soon as it was within range of a tag, it would read it effectively.
Now with the HTC 10, I'm putting the phone close to the NFC tag and..... nothing. No beep, no nothing. I'm having to sit there and wave the phone around for a good 30 seconds before the phone even recognizes that there is a NFC tag near by, and even then, it doesn't read it properly. It takes a good 2-3 tries to get it to read an NFC properly.
I'm hoping it is just a DOA device, so am putting a warranty call into my telco to have the phone replaced (since I purchased it from them directly).
Unless there are some other troubleshooting steps I could try ?
Click to expand...
Click to collapse
Try to toggle NFC on/off quick from the drop down menu and retry the scan.
Sent from my HTC6545LVW using Tapatalk
Haldi4803 said:
What NFC App do you use?
Click to expand...
Click to collapse
I did more testing...
I have tried 2 NFC apps from the card providers in my country called FlashPay & ezlink with 8 NFC cards, as well as Easy Wallet NFC with a Taiwanese NFC card.
Out of the 8 cards, 2 could not be detected while the rest could be detected and read with careful positioning.
The Taiwanese card could be detected but not read, and will "crash" the NFC function of the phone every time, requiring a toggle of NFC off and on before it can read any card again.
It seems that NFC communications on the HTC 10 with cards is extremely weak / directional, while it works better with other devices because the signal from them is active.
In my testing, I can increase the success rate of reading cards with the 10 by holding the NFC card upright, with the long edge horizontal and the front of the card facing me. Then bring the card and phone together with the top edge of the phone aligned to the top edge of the card. I can post a picture if anyone needs it.
dottat said:
Try to toggle NFC on/off quick from the drop down menu and retry the scan.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
That did absolutely nothing. Besides, on the HTC 10, there is no quick NFC Toggle from the drag-down menu.
In saying that though, one of the other posts on here gave me a completely crazy and wacky idea for testing.
Normal NFC circuitry and phone builds are designed to read the NFC tags/cards from the back of the phone., because in HTC10's case, the NFC circuitry is built around the camera lens. Since NFC stands for Near-Field-Communication, why wouldn't it work from the front of the phone as well ?
So I tried it, and guess what. it started reading every single tag I have, from the first attempt, without fail.
Just place the NFC tag/card up near the top speaker on the front of the phone.
Would love for people to actually test this out and provide feedback/results if they could.
If this does work for everyone, then I would call it a major design flaw with HTC10's NFC.
TRLOS said:
That did absolutely nothing. Besides, on the HTC 10, there is no quick NFC Toggle from the drag-down menu.
In saying that though, one of the other posts on here gave me a completely crazy and wacky idea for testing.
Normal NFC circuitry and phone builds are designed to read the NFC tags/cards from the back of the phone., because in HTC10's case, the NFC circuitry is built around the camera lens. Since NFC stands for Near-Field-Communication, why wouldn't it work from the front of the phone as well ?
So I tried it, and guess what. it started reading every single tag I have, from the first attempt, without fail.
Just place the NFC tag/card up near the top speaker on the front of the phone.
Would love for people to actually test this out and provide feedback/results if they could.
If this does work for everyone, then I would call it a major design flaw with HTC10's NFC.
Click to expand...
Click to collapse
Guess ours are setup differently out of the gate.
Sent from my HTC6545LVW using Tapatalk
dottat said:
Guess ours are setup differently out of the gate.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
WTF?! Mine looks exactly the same except I have the calculator where you have NFC. Is there no way to modify this?
goodtimes50 said:
WTF?! Mine looks exactly the same except I have the calculator where you have NFC. Is there no way to modify this?
Click to expand...
Click to collapse
There is if you are rooted. (I'm not)
It's in /system/customize/ACC/default.xml
Sent from my HTC6545LVW using Tapatalk
goodtimes50 said:
WTF?! Mine looks exactly the same except I have the calculator where you have NFC. Is there no way to modify this?
Click to expand...
Click to collapse
Ditto. Also have the Calculator there.
Why does it always seem that the more we 'upgrade', the less features and the dumber things actually get ?
The M8 (a 2 year old phone) has more features and abilities than the HTC10 (which has only been out for a week and a bit).
How is this progress ?
Is there an app or a utility that allows modifying that drop down menu easily (even with root) ? Maybe something along the lines of a Sense Toolbox or something ?
dottat said:
Guess ours are setup differently out of the gate.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
What Rom?
This is 1.30.709.1
I just tested it with a bunch of nfc tag stickers and android pay across the street. It read them all from the back when placed right above the camera and it read from the front around the speaker area..
TRLOS said:
That did absolutely nothing. Besides, on the HTC 10, there is no quick NFC Toggle from the drag-down menu.
In saying that though, one of the other posts on here gave me a completely crazy and wacky idea for testing.
Normal NFC circuitry and phone builds are designed to read the NFC tags/cards from the back of the phone., because in HTC10's case, the NFC circuitry is built around the camera lens. Since NFC stands for Near-Field-Communication, why wouldn't it work from the front of the phone as well ?
So I tried it, and guess what. it started reading every single tag I have, from the first attempt, without fail.
Just place the NFC tag/card up near the top speaker on the front of the phone.
Would love for people to actually test this out and provide feedback/results if they could.
If this does work for everyone, then I would call it a major design flaw with HTC10's NFC.
Click to expand...
Click to collapse
Had a Problem reading my card Today.
So I turned nfc off and back on again. Worked instantly.
Haldi4803 said:
Had a Problem reading my card Today.
So I turned nfc off and back on again. Worked instantly.
Click to expand...
Click to collapse
That's kind of what I was seeing too and that's why I asked if anyone else was seeing that. Almost like nfc is getting put to sleep.
Sent from my HTC6545LVW using Tapatalk
Well the good news with that is I guess then the issue can be fixed in software