Hello Guys,
I'm experiencing issue with touch screen on my N7 (2013) 32gb, Build number: JSS15R , Unrooted
When I put my N7 on the pillow, or sofa (Not wood or metal surface) , the touch screen NOT responding in some area on screen (on the picture below), otherwise, when I hold my N7 in both hands or just one hand it seems to work just fine!
Do you have this issue or only me ?
Note: I used Multi-Touch test app (by TPYXA software) also for this test, and I did factory reset with no any apps install (only Multi-touch app)
{
"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"
}
sauofee said:
Hello Guys,
I'm experiencing issue with touch screen on my N7 (2013) 32gb, Build number: JSS15R , Unrooted
When I put my N7 on the pillow, or sofa (Not wood or metal surface) , the touch screen NOT responding in some area on screen (on the picture below), otherwise, when I hold my N7 in both hands or just one hand it seems to work just fine!
Do you have this issue or only me ?
Note: I used Multi-Touch test app (by TPYXA software) also for this test, and I did factory reset with no any apps install (only Multi-touch app)
Click to expand...
Click to collapse
I was the first to post this. People think we are crazy. But you are right mine works perfect unless its on a pillow or couch or cloth. On the table it works perfect.
http://forum.xda-developers.com/showthread.php?t=2448015&page=13
lespaulman67 said:
I was the first to post this. People think we are crazy. But you are right mine works perfect unless its on a pillow or couch or cloth. On the table it works perfect.
http://forum.xda-developers.com/showthread.php?t=2448015&page=13
Click to expand...
Click to collapse
Same here. Thought my Nexus 7 was fine for a couple weeks. I have no clue what could cause this but I've tested it a lot and it is definitely fine in my hands or on a hard surface and always really bad on a soft fabric surface. It makes no sense, maybe a hard case on the back would help? Has anyone with this problem tried that, are you using it with or without a case?
lespaulman67 said:
I was the first to post this. People think we are crazy. But you are right mine works perfect unless its on a pillow or couch or cloth. On the table it works perfect.
http://forum.xda-developers.com/showthread.php?t=2448015&page=13
Click to expand...
Click to collapse
What you think, is that hardware or software problem?
will this be caused by statics on certain fabric? (really wild guess)
roytse said:
will this be caused by statics on certain fabric? (really wild guess)
Click to expand...
Click to collapse
I will tell you what I think. I think it has to do with the wireless charging coils in the back of the tablet.
I am using a slimline Moko case. I tried it out of the case and it still did same on couch and pillow. On solid surface works great.Is there anyone out there that has taken the Nexus 7 apart. Unplug the wireless charging see if it fixes the screen issues.
This problem is also known as the grounding issue, although some say that's not an accurate description. Regardless, I had this issue and this thread fixed it. http://forum.xda-developers.com/showthread.php?t=2428133
Take a look and see if one of the files will fix your problem.
Skinnysloth said:
This problem is also known as the grounding issue, although some say that's not an accurate description. Regardless, I had this issue and this thread fixed it. http://forum.xda-developers.com/showthread.php?t=2428133
Take a look and see if one of the files will fix your problem.
Click to expand...
Click to collapse
The ts10 file fixed this issue for me.
fuser-invent said:
Same here. Thought my Nexus 7 was fine for a couple weeks. I have no clue what could cause this but I've tested it a lot and it is definitely fine in my hands or on a hard surface and always really bad on a soft fabric surface. It makes no sense, maybe a hard case on the back would help? Has anyone with this problem tried that, are you using it with or without a case?
Click to expand...
Click to collapse
Wow, just tried it and seems like you right.
Screen going nuts when placed on my bed.
When i touching it with all ten fingers, screen automatically turns off and on, endlessly sometimes.
Seems like thats a hardware problem, i dont think any app able to wake up the screen.
Just made a video. Sorry for quality, my dorm roommate havent back yet, so i were filming alone with power of my ankle.
Google or asus or both should begin talking about this and what is the answer/solution they are going to give us. Mine is going to asus tomorrow, let's see what thy do. I know they have change screen, front and gps to another user, and did not even talk about gps problems at all, so they may know something.
bokoy said:
Google or asus or both should begin talking about this and what is the answer/solution they are going to give us. Mine is going to asus tomorrow, let's see what thy do. I know they have change screen, front and gps to another user, and did not even talk about gps problems at all, so they may know something.
Click to expand...
Click to collapse
Wireless charging coils. Its causing a magnetic field on the back of the tablet. causing something like a grounding issue but really not.
If you take your USB cable and plug it in to your Nexus 7 and run the cord around the screen it will go nuts. It should not do that. Same with head phone plugged in to Nexus 7 and the head phone wire touches the screen it causes issues. There is a shielding problem. or its the wireless charging coils needing taken out.
Electromagnetic Interference
Large power lines, electric motors, kitchen appliances, and other devices may directly interfere with a display picture. Many devices are not properly shielded and their electromagnetic fields can cause disruption. Most modern display devices have sufficient shielding to prevent interference, but damage to the shielding may allow for signals to penetrate. Older displays and economy brands may have minimal shielding, leaving these devices vulnerable. Cables and audio/video equipment are also vulnerable to electromagnetic interference.
Read this guys
http://www.silabs.com/Support Documents/TechnicalDocs/Minimizing-Touchscreen-EMI.pdf
@ lespaulman67
I agree with you :good:.
For me , when I plug my headphone into my N7 the problem with touch screen disappear even if I put it on Fabric ground.
Also, I have Galaxy Note II with QI wireless charging (QI wireless charger with the coil purchased from ebay 6 months ago), until now I don't have any issue with touch screen or charging itself.
Yes, I think the wireless coil caused touch issue.
Thank you all for the information , hope Google and Asus fix this very soon
Here is a logcat for touchscreen fail and sudden screen off/on turning.
Not sure if i did it right though
Note that NFC turning on/off by itself as well.
I have a couple of other tablets that I do amateur Dev work on, so I decided I can do without the nexus for a while and send it in for "repair" to see what happens. I'm curious to find out if they will change out any hardware or just flash a different firmware version and then send it back. I've tried every stock version if firmware with no luck, it seems to work fine for a couple if hour up to a day and the goes back to sucking. I'll report back in this thread when it gets mailed back and let everyone know what turn around time is like and if it actually helps. I have mentioned the ASUS customer service rep on live chat was excellent and its really easy to RMA it back.
I got my tablet back from he service center. It was a pain, they shipped it to the wrong address and then fedex delivered it to a neighbor, had to retrieve it and re-deliver it. Turnaround time at the service center was only one day but shipping in both directions was about a week total.
Even though I requested it, there was no notes on what they did so I contacted customer service. They looked up the notes and told me they had to open the tablet to re-calibrate the touchscreen and also loaded a "newer driver" to fix the issue. They also said it was safe to update the firmware if a new version is released.
So far the tablet is fine but I'll report back after using it for longer to see if the issue really is fixed. If they had to open the tablet, that sounds like people with this particular issue do have to send it in for repair because no firmware update can fix it.
fuser-invent said:
They looked up the notes and told me they had to open the tablet to re-calibrate the touchscreen and also loaded a "newer driver" to fix the issue.
Click to expand...
Click to collapse
Could you do me a favor?
assuming you are rooted, reboot your tablet
then type
su
dmesg | grep "ektf3k" | grep "firmware"
PM or post the output.
sfhub said:
Could you do me a favor?
assuming you are rooted, reboot your tablet
then type
su
dmesg | grep "ektf3k" | grep "firmware"
PM or post the output.
Click to expand...
Click to collapse
What do you need from the output? That command doesn't work together but I can grep them separately. I'm not nearly set-up enough to copy/paste the dmesg, so I'll have to type it out for now. Relevant parts, let me know if you need more:
grep for firmware:
firmware version: 0xa042
firmware id: 0x3029
grep for ektf3k:
x resolution: 0x007e
y resolution: 0x00d2
boot code id: 0x6047
Max X=2239, Max Y=1343
Don't know if you need the rest but I'm guessing not.
Mine got back from asus one week ago, they replaced screen, front and gps. Nothing was fixed, multitouch is still going mad, single touch is a bit improve, as before it works nearly well grounded but over a table or a sofa it works worst.
One friend got it back for a second time, the first time they did the same they have done to mine, now they changed main bd-2g, rear camera, screen, front and gps, 24hrs later he is reporting me that problems are back. Do you know what main bd -2g is? Motherboard?
Where did you type those commands?
bokoy said:
Mine got back from asus one week ago, they replaced screen, front and gps. Nothing was fixed, multitouch is still going mad, single touch is a bit improve, as before it works nearly well grounded but over a table or a sofa it works worst.
One friend got it back for a second time, the first time they did the same they have done to mine, now they changed main bd-2g, rear camera, screen, front and gps, 24hrs later he is reporting me that problems are back. Do you know what main bd -2g is? Motherboard?
Where did you type those commands?
Click to expand...
Click to collapse
Just download any terminal emulator from the play store. I use this one.
As for the touch issues, mines obviously still got the multi-touch thing going on when you get several close fingers together. In my opinion that really has nothing to do with the Nexus 7. I've owned 8 tablets, not including the this Nexus and they all do the same thing if you put a bunch of fingers on the screen and then group them in close together. I'm pretty sure if you were to go to a Best Buy or something and play with all their tablets you would be able to reproduce the same thing on every single one.
The whole "only works when I'm holding it" thing was new to me though. It literally didn't work on any surface or even suspended on a stand. I've been playing around with it more since I got it back and putting it on various things, so far it works on every hard and soft surface, it also works whiles charging via USB and wireless charging. Another thing to note is that it came back with JSS15Q loaded. I haven't updated and don't plan on doing that for a while, even though the customer service people "guaranteed" me that it would be fine.
No clue about the bd-2g though.
fuser-invent said:
firmware version: 0xa042
Click to expand...
Click to collapse
Ok, you didn't get any "newer" touchscreen firmware. This is the standard one that came with JSS15Q/R.
So it is possible you have a screen that now behaves best with the latest touchscreen firmware.
Related
Ok, so the battery died on my play yesterday so, as you do, I went and got the charger and plugged it in. Once it was charging I turned it back on. However, when I went to use it all I saw was this:
{
"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"
}
My first thought was to take the battery out and reboot so I did - as I was taking out the battery I saw a flash of the old screen for a second just before the power went.
Rebooted but no change.
I tried to backup and restore with the SE sofware but I couldn't put the phone in media something mode and it wouldn't allow me to.
So I reinstalled using SEUS instead, powered back on and no change.
It's really bugging me. The screen starts up with "SonyEricsson" which says to me the screen is surely not broken or disconnected, ut then I get this fuzzy / static mess and nothing else.
It's only a few months old so it's probably under warranty, but I really don't want to have to send it back - it's been less than 24 hours and I'm already missing it!!
Anyone have any ideas?
P.S. - I've also tried rebooting without the memory card and/or sim card, but no diff.
zacseph said:
Ok, so the battery died on my play yesterday so, as you do, I went and got the charger and plugged it in. Once it was charging I turned it back on. However, when I went to use it all I saw was this:
My first thought was to take the battery out and reboot so I did - as I was taking out the battery I saw a flash of the old screen for a second just before the power went.
Rebooted but no change.
I tried to backup and restore with the SE sofware but I couldn't put the phone in media something mode and it wouldn't allow me to.
So I reinstalled using SEUS instead, powered back on and no change.
It's really bugging me. The screen starts up with "SonyEricsson" which says to me the screen is surely not broken or disconnected, ut then I get this fuzzy / static mess and nothing else.
It's only a few months old so it's probably under warranty, but I really don't want to have to send it back - it's been less than 24 hours and I'm already missing it!!
Anyone have any ideas?
P.S. - I've also tried rebooting without the memory card and/or sim card, but no diff.
Click to expand...
Click to collapse
do you think it is software or hardware related. you could try WotanServer or flashtool to flash stock I think the bootloader doesn't need to be unlocked for official files.
Fma965 - Forgottencoders.co.uk
fma965 said:
do you think it is software or hardware related. you could try WotanServer or flashtool to flash stock I think the bootloader doesn't need to be unlocked for official files.
Fma965 - Forgottencoders.co.uk
Click to expand...
Click to collapse
Since the screen was showing the logo when booting, I assumed it must be a software issue - just used flashtool and it said everything was successful... but the screen is still the same - and now "SonyEricsson" doesn't come up at the start anymore...
its the screen damage or motherboard problem...i faced thr same issue..take it to sony care
Sent from my R800i using XDA App
I have this same problem.......can it be related to the slider flex cable??? How did you get it resolved your answer really would help me. My location restricts me from returning it and its not under warranty anymore.
jessepow said:
I have this same problem.......can it be related to the slider flex cable??? How did you get it resolved your answer really would help me. My location restricts me from returning it and its not under warranty anymore.
Click to expand...
Click to collapse
i went to SE care. At first, they told me that they had replaced the display along with the flex cable. Then the phone wouldnt charge. So they changed the motherboard also. But this entire process took over a month. Was really unhappy that they couldnt identify the problem at first. But i wasnt charged any money because of warranty, so its all good. i Suggest you take it to any care center and first get the problem diagnosed. If you are paying for replacing it the motherboard , it is as good as purchasing a new phone.
Had almost the same problem when I slided my phone when it was 3 degrees Celsius "cold". I destroyed flex cable and my screen started to freeze and show random RGB pixellation.
I think it's 99% broken flex or 1% motherboard. I suggest you to give your Xperia PLAY back to Sony if it's under warranty.
Cheers.
its ridiculous I have the same problem when I unlock my phone. i emailed the company i got it from but im still waiting for a reply haven't dropped it or anything, but for now i slide the phone and have to use it like that and even then it the screen flickers a few times.
http://imageshack.us/photo/my-images/849/120223225408.png/
http://imageshack.us/photo/my-images/830/120223225431.png/
http://imageshack.us/photo/my-images/13/120223225440.png/
http://imageshack.us/photo/my-images/194/120223225525.png/
I have the same problem, just happened out of no where as the phone has been working fine. It pushed me into buying a GS3 but I still want the play for gaming. I've had mine for over a year and I bought it off ebay so I'm not holding out much hope for warranty.
It is Flex Cable. I had exact same problem, boot logo was showing like normal and then w00t.
hi everyone
same problem as every1 fuzzy screen can anyone be 110% sure it is the ribbon
as my warranty is finished and i have to do it myself
Yeah it's flex cable stuff. I had to get a new phone because of this. When you get it fixed, just start being careful with sliding your phone open.
Erikwithafro said:
Yeah it's flex cable stuff. I had to get a new phone because of this. When you get it fixed, just start being careful with sliding your phone open.
Click to expand...
Click to collapse
100% sure?
I hate to bring up a dead thread but I now have 2 plays with this issue...
Pretty sure I can fix it myself...
I had this problem too. You can bring it to your store and give it Tod sony. You will get a new working phone.
Gesendet von meinem R800i mit Tapatalk 2
Flex cable swapped out, Play number 1 successfully fixed. It really wasn't that hard to fix either.
same issue here.. looks like it's a very common issue with the Xplay
Ok, so after I first posted this thread, I brought my play to the nearest repair centre and had it fixed up. However, a few days ago it started back up again... Since its out of warranty ill probably just try fix it myself, but it's kinda creepy that it's almost exactly a year since it first happened...
GTDarthYoda said:
Flex cable swapped out, Play number 1 successfully fixed. It really wasn't that hard to fix either.
Click to expand...
Click to collapse
Sorry to bump an old thread but this happened to my phone this week also. I'd like to be able to fix it myself but I have literally no experience with doing such a thing - is it a straightforward case of screwing the cover off and simply replacing the cable or is there certain pitfalls that I should avoid?
My phone is not in warranty (bought second hand) so would rather pay 20 euro for a flex cable on ebay than pay double or triple that to have it repaired.
baddler said:
Sorry to bump an old thread but this happened to my phone this week also. I'd like to be able to fix it myself but I have literally no experience with doing such a thing - is it a straightforward case of screwing the cover off and simply replacing the cable or is there certain pitfalls that I should avoid?
My phone is not in warranty (bought second hand) so would rather pay 20 euro for a flex cable on ebay than pay double or triple that to have it repaired.
Click to expand...
Click to collapse
You have to take the device apart fully, inclusive of the screen half of the Play to replace the ribbon.
Some things you should be aware of are:
- The tiny ribbon cable on the upper side of the motherboard that is connected to the Touchpads. This is EXTREMELY delicate and is an even worse pain in the ass to replace than the main flex cable.
- When putting it back together, ensure the L and R buttons work correctly before screwing it back together again.
- The flex cable is quite difficult to get through the space it's required to go through (you'll see), you have to CAREFULLY twist and turn it to get it in.
- When attaching the flex cable to the motherboard (It's quite difficult to secure it properly as it's such a small gap) be sure not to use any sharp tools or to press too hard. I've killed a new flex cable in the past by doing this.
I've had to replace the cable 7 times so far on 5 different Plays. (None of which have been my own) - Although when my friend's died and he gave it to me to repair, he simply brought a new one anyway and I kept the Play after I fixed it. xD But yeah, very common issue. No idea why it hasn't happened to me yet though. *touch wood*
Thanks for the reply Spizzy.
Hmm seems like there's quite a few pitfalls to taking this on myself - may be best to leave this one to the experts
Hi does anyone have a problem with proximity sensor of the Galaxy s4? I noticed after owning the phone for 2 months and flashing lots of Rom's now the proximity Sensor is not working no matter what Rom I install. When I make a call the screen turns off and doesn't come on until I press the home button. And some apps that use the proximity Sensor don't work. So I called t-Mobile and they are sending me a new
Sent from my
samomamo said:
Hi does anyone have a problem with proximity sensor of the Galaxy s4? I noticed after owning the phone for 2 months and flashing lots of Rom's now the proximity Sensor is not working no matter what Rom I install. When I make a call the screen turns off and doesn't come on until I press the home button. And some apps that use the proximity Sensor don't work. So I called t-Mobile and they are sending me a new
Sent from my
Click to expand...
Click to collapse
Hi..I had the same problem..but mine started after 3 weeks..Never flashed a rom just rooted..I took it and they just game me another phone..you might have a defective phone..but if you're gonna take it back I suggest you flash it to stock and use Triangle away app. This one I had I flashed custom rom 2x..had it for 2months..No problems:good:
what things use a proximity sensor? never heard of it
You using an Otterbox? I only ask because it can cause headaches with the proximity sensor, but it's an easy fix.
No the phone is naked
Sent from my phone
Bump
Sent from my LG-E980 using xda premium
samomamo said:
Bump
Sent from my LG-E980 using xda premium
Click to expand...
Click to collapse
I got another one; are you using a screen protector at all?
I'm starting to be pretty sure the S4 got shipped with a bad batch of proximity sensors.
Mine has suddenly failed as well with no case or screen protector or any of that kind of thing involved.
Same story as everyone else who has this problem. The sensor reads as though it's being covered 100% of the time, so as soon as the phone.apk is initated and looks for the sensor value, it says the sensor is covered and blacks out the phone. Nothing brings the screen back on until the call ends.
I searched around Google and found quite a few message boards with various people describing the same exact problem.
I have tried various things to fix it.
I have cleaned the glass thoroughly to no avail.
I have tried the sensor recalibration from this thread . But that did nothing.
I installed this app from the Play store. That was very interesting because it tells me how long it has been since the sensor was last uncovered, and that value grows indefinately as long as the app is on. Meaning the sensor never reads as uncovered.
I even tried to mask the problem by getting apps that are supposed to keep the screen on during calls but they also fail.
I'm going to Odin back to stock tonight and see if that helps, but I think I've got hardware failure. Mainly because this started to go downhill over a couple weeks where the screen off during calls slowly started to work worse and worse until now when it just totally locks me out.
If I have to get this phone replaced and they send me a refurbished one I'm going to be super pissed. I had to do that with a MyTouch4G with T Mobile and that was an absolute nightmare. Every replacement phoen they sent me had a different defect, and then they had the freakin' nerve to try to charge me $10 each time they sent me a refurbished phone. So I had what was basically a defective brand new phone that was 2 months old that they wanted me to pay $60 more to be replaced with a used phone.
Well I called T-Mobile they send me a new GS4 and it works perfect
Sent from my XT1058 using XDA Premium 4 mobile app
O
samomamo said:
Well I called T-Mobile they send me a new GS4 and it works perfect
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I just called about mine too and they are sending a new one.
Just kind of annoys me that I spent full price on a new phone 2 months ago and now I will have a refurbished one despite paying full price. Especially since this is the second time this has happened with a new phone from them.
Does yours seem and look like new?
Sent from my SGH-M919 using xda app-developers app
Skipjacks said:
O
Yeah I just called about mine too and they are sending a new one.
Just kind of annoys me that I spent full price on a new phone 2 months ago and now I will have a refurbished one despite paying full price. Especially since this is the second time this has happened with a new phone from them.
Click to expand...
Click to collapse
That sucks! Did they really send you a refurb? When my wife broke her screen and we went through insurance, we got a brand new one which amazed me -- it means we got an extra battery sand stuff.
I'm having the SAME problem with my M919 now. I thought I was going crazy over the last week being unable to hang up calls (can't get the screen on!) or dial codes mid-call.
I ended up recalibrating the sensor by doing this procedure directly on the sysfs stuff: http://forum.xda-developers.com/showthread.php?t=2045569&page=2
It works now but I see now why it failed initially -- there's a TON of dust under the glass right over the proximity sensor! Needless to say, I am getting it replaced under warranty because that's just not cool at all. I've had this one for 2 months, tops.
It was weird, CPU-Z was showing the sensor as dead but when I was reading the state over sysfs it seemed to actually be doing something, indicating to me the calibration was way off.
Well, at least I don't have to be bothered with the sensor problem for now as I wait for my (BACKORDERED!) RMA...
EDIT: Oh and it's doing somethng fun. I flashed a nightly a few days ago and it wouldn't boot until I later decided to reflash + wipe cache. OK, that was weird because no one else had to. Well, earlier I turned it off and when I turned it back on, same deal! Had to go into recovery and wipe cache.
I'm starting to get disappointed with the build quality on both the S3 and S4. My (retired) S3 has the most "fun" problem -- its eMMC likes to get corrupted periodically. It doesn't manifest as problems while running (no file corruption that I can tell), but if I ever have to Restore Backup, it usually fails and then I have to not only fsck it in recovery mode but usually do some other tricks like remove the duplicate lost+found inode and use the alternate superblock with fsck (fsck -b 32768).
i have had a replacement device now for about 2 months. the proximity sensor worked for about 2 weeks before failing again. There is clearly an issue. i am going to try a 3rd device or ask for a different device entirely.
samomamo said:
Hi does anyone have a problem with proximity sensor of the Galaxy s4? I noticed after owning the phone for 2 months and flashing lots of Rom's now the proximity Sensor is not working no matter what Rom I install. When I make a call the screen turns off and doesn't come on until I press the home button. And some apps that use the proximity Sensor don't work. So I called t-Mobile and they are sending me a new
Sent from my
Click to expand...
Click to collapse
Just as a test, do this:
using the stock dialer, enter *#0*#
then when the menu pops up, hit "Sensor" square.
then place your palm with an open hand about 2.5 inches away from the top right front area where the sensor is located. Yhe upper area of the screen should turn green, and also should vibrate.
if that test passes, then the sensor is not the problem.
I've seen a lot of places that indicate the proximiy sensor is prone to failing due to dust build up. This is often be solved by using compressed air shot into the speaker grill on the front to un-foul the sensor.
It might not save every phone with a failing sensor, but it can't hurt to try and I've seen a couple people say it was an instant cure.
I don't think you evne have to be able to see the dust for it to cause fouling. Just a spec or two can mess it all up. But the compressed air cleans it right out.
Check if fast dormancy is enabled
I had the same problem after installing Crash ROM v13, my phone was working fine with JB 4.2.2, the only thing I changed after flashing the new rom was "fast dormancy", after trying different configurations what I did was to toggle back fast dormancy to enabled and now my screen and proximity sensor works perfectly fine.
It also could be related with the kernel, I'm using Perseus Kernel, I was using Adam Kernel previously.
proximity sensor fix
I had same problem and i fix The problem in both of my s4 .buy the air spray and spray in earplug for about 20 sec .and try it will work
I'm having the same issue, did this test and it turns green and vibrate but never turns off when I remove my hand....I've been checking around and people have said it is an issue with dirt/lint getting through the speaker grate and gathering on top of the sensor. I tried some compressed air and it resolved the issue for a short time. Seems like the only real fix would be to pull the screen and add something to block the opening between the sensor area and the speaker grate.
bobolinko said:
Just as a test, do this:
using the stock dialer, enter *#0*#
then when the menu pops up, hit "Sensor" square.
then place your palm with an open hand about 2.5 inches away from the top right front area where the sensor is located. Yhe upper area of the screen should turn green, and also should vibrate.
if that test passes, then the sensor is not the problem.
Click to expand...
Click to collapse
Recently I have been searching for solutions to fix my i9505 from. the screen going black when i make a phone call. I had posted a work around recently... This has been working for me but in order ive had to get rid of my lock screen...
Well I think I may of found a solution to my problem and for what I can v see many others. So no more blowing you're sensors clear with air...
ALL U NEED-
an awesome custom ktoonsez kernel and the KTWEAKER
Open kteeaker app which comes included in KT kernel. Go to mainsetting/wakesleepsetting then proximity setting and alter the value. Easy as that.
WITH IN K TWEAKER APP KT HAS ADDED OPTION TO TEST AND MODIFY YOUR PROXIMITY SENSOR.
ONE OF MY PHONES WAS SET TO 43 OUT OF 255, AN THE OTHER WAS SET TO 8 WHICH I ASSUME AS DEFAULT BUT JUST INCASE I SET TO (1), NOW BLACK SCREEN WON'T GO ON TILL U NEARLY TOUCH THE SENSOR THEN SCREEN COME BACK ON AS SOON AS U PULL AWAY.... AS IT'S SUPPOSED TO....
HOPEFULLY This will help some of you.!!!
All credits to ktoonsez!!
PS. If you don't know how to do it don't.... Confirmed. This worked for me.
I had the same problem. Cleaning it had no effect; THIS however DID fix it!!
trueking7 said:
Download terminal emulator and enter the following....
{
"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'm not taking credit for the fix just too lazy to link to it.... Again
Click to expand...
Click to collapse
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
{
"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"
}
So I've been looking at these mounts and am on the fence about it. Costs a bit more than you would usually drop on a mount ($70-$100), but reviews of it are quite amazing. The sticky/suction pad is apparently really good, and the arms are stable and have a smooth release. On top of that it has a built in NFC chip. Now the Wireless Charging is where i get a little iffy. This device puts out 750mA. Comparitively the Nexus 4 charging orb puts out 1,000mA. I also have read in various places that some of Nokia's wireless chargers have a cycle issue where the device charges/stops/charges/stops. This effect might be visible on a Nexus 4 using this charger at this video (53seconds). Anyone have one they can test, or have recommendations to a similar mount?
I've read a lot of reviews about a critical part breaking easily.
Sent from my SGS3.
So, did anyone tried it? Does it work with Nexus 5?
From the info that i could dig, the nexus 4 does not work, probably because the location of the charging coil.
cracksmurf said:
I also have read in various places that some of Nokia's wireless chargers have a cycle issue where the device charges/stops/charges/stops.
Click to expand...
Click to collapse
From what I've read and researched, the problem wasn't with Nokia's chargers but the first versions of the N4, later revisions worked fine.
Watcher07 said:
From what I've read and researched, the problem wasn't with Nokia's chargers but the first versions of the N4, later revisions worked fine.
Click to expand...
Click to collapse
No, it doesn't work. Has the Start Stop charging fault. Shame, I appear to have wasted £56.....
MarkyH said:
No, it doesn't work. Has the Start Stop charging fault. Shame, I appear to have wasted £56.....
Click to expand...
Click to collapse
Could you explain a bit more in depth please?
Sent from my Nexus 5 using Tapatalk
undercover said:
Could you explain a bit more in depth please?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
When you put a Nexus 5 in the Nokia CR 200 it initially shows charging. Some time later (5, 10 ,30 seconds, maybe a few minutes - it seems to vary) it will stop charging. If you leave the phone in the dock, it will intermittently charge.
In my test over a couple of hours, the phone discharges pretty fast.
My conclusion is that it's useless as a charger for the Nexus 5.
If anyone has a workaround, I'd love to know, as the CR 200 is an otherwise sturdy bit of kit and I'm not sure what QI Wireless alternatives are available.
MarkyH said:
No, it doesn't work. Has the Start Stop charging fault. Shame, I appear to have wasted £56.....
Click to expand...
Click to collapse
Thanks for letting us know. I've been actively seeking a qi car mount with nfc and this one was the prime choice aside from building my own. I wonder if it has to do with the bottom piece that sticks out for holding your phone in portrait mode, maybe the qi coils just aren't close enough together.
Nokia CR 200 works with Nexus 5 without any problems.
I received the Nokia cr 200 from Amazon yesterday and can confidently say it works brilliant. I haven't got any problems as mentioned in this thread. Just place the phone in the charger and the light at the bottom goes green and charged as it should. NFC is OK but got to know where the NFC chip is at the back of Nexus 5. I used the Google maps navigation and BT music streaming to my ford sony dab unit at the same time for about 50mins and the battery percentage just stays at the same level as before putting on charge. With BT music streaming it actually charges as the screen is switched off I guess. Its a good quality car mount but he clip is not the strongest I would say. Suction is absolutely fine as it has a stickiness to the suction. I don't know what app I got to use to check the charge voltage etc. Pls let me know if u want to know any details. But it works as it should very happy.
Out of curiousity, if NFC is so important, why not just buy an NFC sticker and slap it on there? Is it because it wouldn't look as cool?
Pictures
krishna9349 said:
I received the Nokia cr 200 from Amazon yesterday and can confidently say it works brilliant. I haven't got any problems as mentioned in this thread. Just place the phone in the charger and the light at the bottom goes green and charged as it should. NFC is OK but got to know where the NFC chip is at the back of Nexus 5. I used the Google maps navigation and BT music streaming to my ford sony dab unit at the same time for about 50mins and the battery percentage just stays at the same level as before putting on charge. With BT music streaming it actually charges as the screen is switched off I guess. Its a good quality car mount but he clip is not the strongest I would say. Suction is absolutely fine as it has a stickiness to the suction. I don't know what app I got to use to check the charge voltage etc. Pls let me know if u want to know any details. But it works as it should very happy.
Click to expand...
Click to collapse
Can you post some pictures. Thanks in advance.
robertlwalters said:
Can you post some pictures. Thanks in advance.
Click to expand...
Click to collapse
Will do over the weekend as I work all day by the time I finish work its really dark. So will post pics over the weekend.
Found this video maybe it helps http://www.youtube.com/watch?v=2WUraI9aLfY
MarkyH said:
When you put a Nexus 5 in the Nokia CR 200 it initially shows charging. Some time later (5, 10 ,30 seconds, maybe a few minutes - it seems to vary) it will stop charging. If you leave the phone in the dock, it will intermittently charge.
In my test over a couple of hours, the phone discharges pretty fast.
My conclusion is that it's useless as a charger for the Nexus 5.
If anyone has a workaround, I'd love to know, as the CR 200 is an otherwise sturdy bit of kit and I'm not sure what QI Wireless alternatives are available.
Click to expand...
Click to collapse
have a look at what "OWL" has to offer...I ordered One....we'll See what this thing can Do.
More of a note to myself so I can find the thread again, but also just ordered one. Have a long car journey next week so should be able to give it a good run in, if it arrives in time.
Amazon seem to be doing it for £54 which seemed to be the cheapest outside of ebay
So it arrived today from Amazon and have had a bit of a play
Initial thoughts is that it is quite sturdy and looks good. Did the shake test and it did not come away, however a point of note is that it seems to grip but give it another squeeze to make it go a couple more notches in which kept the back flush with the charging plate. Just squeezing the grips until it makes contact won't hold it firmly in place and you get movement like on the Youtube review.
I've connected it to my bench supply as I'm at work. With the screen off/no GPS running its charges from 72% to 100% in just over an hour. The screen seems warm to touch and the back hotter which was expected. I've not had it been or connect/disconnect charging as mentioned in some reviews but I stress that this is on my desk at work.
Tonight drive home is about 40 min so will run TomTom and see if there is any power drop and tomorrow I have a 200 mile round trip so I can get some good testing done then as well. I'm hoping I will see the battery stay at the same level as when it was connected.
Does anyone have any suggestions of a launcher tailored to cars (car mode)?
Hi More testing done and I'm impressed so far.
Setting back home last night, I set TomTom up, the Settings of the phone was
GPS - Device Only
Automatic Backlight
TomTom in night mode
The battery at the start was 66% and at the end of the 2 1/2 hour journey it grew to 79%. So the phone charged while the screen was on and was using GPS.
Now admittedly this was not during the day, I did not have time to check the battery on the journey to the destination, however I did not notice any really drop in the battery from the icon. However halfway through the journey I noticed that the battery was not charging as I was rushing when I placed the phone in the cradle it was not fully flush with the back plate and/or I did not squeeze the clips that would hold it in place securely.
I need more testing but I think using this would be fine, potentially if you had full backlight and GPS running with TomTom in day mode I guess there may be a drop in the battery, but not much.
spikeeee said:
Hi More testing done and I'm impressed so far.
Setting back home last night, I set TomTom up, the Settings of the phone was
GPS - Device Only
Automatic Backlight
TomTom in night mode
The battery at the start was 66% and at the end of the 2 1/2 hour journey it grew to 79%. So the phone charged while the screen was on and was using GPS.
Now admittedly this was not during the day, I did not have time to check the battery on the journey to the destination, however I did not notice any really drop in the battery from the icon. However halfway through the journey I noticed that the battery was not charging as I was rushing when I placed the phone in the cradle it was not fully flush with the back plate and/or I did not squeeze the clips that would hold it in place securely.
I need more testing but I think using this would be fine, potentially if you had full backlight and GPS running with TomTom in day mode I guess there may be a drop in the battery, but not much.
Click to expand...
Click to collapse
How well does it work with a bumper case?
h0lyc0w said:
How well does it work with a bumper case?
Click to expand...
Click to collapse
I'm sorry but I do not have or use a case. If someone would like to send one to me for a few days I'm more than happy to test.
Next week when I have a chance I will attach it to my bench supply and do some testing at different levels of brightness and more than happy to test with bumpers/cases if people like to send them
I'm rather surprised by those of you getting it to charge, mine wouldn't put through enough charge when GPS, screen on and streaming music.
(My follow up to the video someone kindly posted earlier.)
I have an Tab S 8.4 LTE. Since upgrading to stock android 5.0.1 (from Sammobile), I have been getting screen flickering, screen freezes, and also random shutdown/restarts. None of that happened on 4.4.2, which the device came with. I've tried the following to correct the problems, with no luck: reinstall 5.0.1, cache wipe from recovery, factory data reset. Is my problem common? Is there a solution? Should I go back to 4.4.2?
A lot of problems you have mentioned is supposedly caused by an faulty/loose battery connector on the 8.4" , a lot of people say it started after upgrading to lollipop which is still not confirmed.
You can try the fix in the link below, but if it is a faulty battery connector a repair is your only real remedy to you problem.
This problem is quite common, have search you might find a more help.
http://www.problogbooster.com/2014/06/on-screen-display-flickering-error-android-xda.html
John.
{
"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"
}
Tinderbox (UK) said:
A lot of problems you have mentioned is supposedly caused by an faulty/loose battery connector on the 8.4" , a lot of people say it started after upgrading to lollipop which is still not confirmed.
You can try the fix in the link below, but if it is a faulty battery connector a repair is your only real remedy to you problem.
This problem is quite common, have search you might find a more help.
John.
Click to expand...
Click to collapse
I had this problem. Service center in Poland (CCS) replaced screen and repaired motherboard.
Video on youtube that shows the problem :
https://www.youtube.com/watch?v=4iBDVirN_XM
corvus.corax said:
I have an Tab S 8.4 LTE. Since upgrading to stock android 5.0.1 (from Sammobile), I have been getting screen flickering, screen freezes, and also random shutdown/restarts. None of that happened on 4.4.2, which the device came with. I've tried the following to correct the problems, with no luck: reinstall 5.0.1, cache wipe from recovery, factory data reset. Is my problem common? Is there a solution? Should I go back to 4.4.2?
Click to expand...
Click to collapse
This is a common problem of Samsung tablet, battery connector is prone to crack: flickering screen, random shutdown/restart, quick discharge, battery capacity fluctuation.
If you look at Galaxy Note Pro 12.2 threats, flickering problem is the same as this model. However, the fix is simple: re solder the battery connector. Go to a repair shop or anyone knows how to re work for assistance , the work takes only under 5 minutes. No need to remove the main board, just disconnect battery cable and do the re work of battery connector's solder joints.
This battery connector is not exactly but similar to yours:
In fact, it did start after the upgrade to Lollipop, so I want to say that, for me, that is confirmed. It never happened prior to that. Nevertheless, it could be a pre-Lollipop problem. Since the unit is still in warranty, I will try to explain the problem to Samsung here. They are usually pretty good about it when I get the chance to talk with a repair tech.
Try this fix in the thread below, it worked foe an Tab S owner the other day with screen flickering.
http://www.problogbooster.com/2014/06/on-screen-display-flickering-error-android-xda.html
John.
corvus.corax said:
In fact, it did start after the upgrade to Lollipop, so I want to say that, for me, that is confirmed. It never happened prior to that. Nevertheless, it could be a pre-Lollipop problem. Since the unit is still in warranty, I will try to explain the problem to Samsung here. They are usually pretty good about it when I get the chance to talk with a repair tech.
Click to expand...
Click to collapse
Tinderbox (UK) said:
Try this fix in the thread below, it worked foe an Tab S owner the other day with screen flickering.
http://www.problogbooster.com/2014/06/on-screen-display-flickering-error-android-xda.html
John.
Click to expand...
Click to collapse
Thanks. I'll give that a try. It is worth noting that since I put 5.0.1 on my S4, it's been running smoothly.
Sefto said:
I had this problem. Service center in Poland (CCS) replaced screen and repaired motherboard.
Video on youtube that shows the problem :
https://www.youtube.com/watch?v=4iBDVirN_XM
Click to expand...
Click to collapse
Be aware that some depot techs are lack of technical skills to troubleshoot correctly, this one is a typical one.
When replacing new screen and motherboard, this guy virtually gave you a new tablet.
Beut said:
Be aware that some depot techs are lack of technical skills to troubleshoot correctly, this one is a typical one.
When replacing new screen and motherboard, this guy virtually gave you a new tablet.
Click to expand...
Click to collapse
Repaired motherboard But I don't know what exactly they did
Well, I followed the instructions to force GPU screen renderiing and for about a day, it seemed to fix the flicker/restart problem. Then, boom, it came back. So it must be a hardware issue. Off to Samsung I go.
I wonder how hot the cpu gets when the screen starts to flicker, you can download free cpu temp apps from Google Store
John.
I took the tab s to Samsung and they found it was a battery problem. They replaced the battery and all seems well after a week. Now my question is, if I use my S4 charger, which has a little lower output than the tab's charger, will that cause any problem to the battery, beyond slower charging?
Slower charging as you said will most likely problem, use the free app below to check you charging rate, look at the average ma, and press refresh a few time, on the pro version you do not have to press refresh.
https://play.google.com/store/apps/details?id=com.abmantis.galaxychargingcurrent.free&hl=en
John.
corvus.corax said:
I took the tab s to Samsung and they found it was a battery problem. They replaced the battery and all seems well after a week. Now my question is, if I use my S4 charger, which has a little lower output than the tab's charger, will that cause any problem to the battery, beyond slower charging?
Click to expand...
Click to collapse
That's PERFECTLY WORKS...
vinayak.etx said:
That's PERFECTLY WORKS...
Click to expand...
Click to collapse
I wonder what did you do to fix the problem ?
Soldering worked.
I had the screen flickering problem and also random reboots on Galaxy Tab Pro 12.2 (SM-T900) and figured out that it is probably to do with the battery connector based on this post and an other post. When I opened the back cover and touched the battery connector, it just came out from its position. Samsung did a very poor job in designing this very important component which is the lifeline of the device.
However, following your advice, I first hesitated to solder it myself. I called up a repair guy and explained him that I need soldering the battery connector and he prompted $65 as the cost for it. So I decided to give a shot myself. I tried my hand at it and was able to get it done.
IMPORTANT: The connector ends are very very small and so you would need a soldering iron having a pointed tip. All you would need is to clean the battery connector ends with a hair brush and apply a very thin coating of soldering flux and have the solder lead on the pointed tip. The points on the circuit board are very close to couple of IC's and so be very careful not to touch them at all. Also, the plastic used in the battery connector component is not a good quality plastic and so be very careful in handling it.
Once the battery connector is soldered, I haven't seen any flickering so far and random reboots are gone. So far so good. I shall update this post if I see any deviation or any other update relevant with this issue.
Thank you @Beut for your post and providing insight about the problem.
Beut said:
This is a common problem of Samsung tablet, battery connector is prone to crack: flickering screen, random shutdown/restart, quick discharge, battery capacity fluctuation.
If you look at Galaxy Note Pro 12.2 threats, flickering problem is the same as this model. However, the fix is simple: re solder the battery connector. Go to a repair shop or anyone knows how to re work for assistance , the work takes only under 5 minutes. No need to remove the main board, just disconnect battery cable and do the re work of battery connector's solder joints.
This battery connector is not exactly but similar to yours:
Click to expand...
Click to collapse
Don't forget that a loose white battery connector also a factor of flickering, usually when disconnected it many times, this white connector may not make good contact with pins of black battery connector. I had one that black battery connector already resoldered but it still flickered at 70% batttery. I did a simple fix by pushing the opening tip closer. Many good batteries were wasted because most users don't know this simple trick, just disconnect and connect battery may fix auto reboot problem and don't know why.
This is what it looks like when a cable removed from the connector:
This is a bad contact, pin sits in the middle of opening of cable clip.
This is the adjustment to make the opening closer:
How to do it with a thin knife:
https://www.youtube.com/watch?v=PU0OoZSbma8&feature=youtu.be
Then, this is a good contact
After the fix of male and female battery connectors ( black and white ), I guarantee that flickering, freeze, auto restart, auto shutdown problems will not return, unless you have a bad battery.
Beut said:
This is a common problem of Samsung tablet, battery connector is prone to crack: flickering screen, random shutdown/restart, quick discharge, battery capacity fluctuation.
If you look at Galaxy Note Pro 12.2 threats, flickering problem is the same as this model. However, the fix is simple: re solder the battery connector. Go to a repair shop or anyone knows how to re work for assistance , the work takes only under 5 minutes. No need to remove the main board, just disconnect battery cable and do the re work of battery connector's solder joints.
This battery connector is not exactly but similar to yours:
Click to expand...
Click to collapse
Hi @Beut,
I followed your post and fixed my tab by soldering the battery connector as you mentioned.
Do you happen to know what's the type of battery connector is it? I mean, if I want to buy that connector online, what should I be looking for?
Thanks.
Uresh
replied using Tapatalk
uresh.kuruhuri said:
Hi @Beut,
I followed your post and fixed my tab by soldering the battery connector as you mentioned.
Do you happen to know what's the type of battery connector is it? I mean, if I want to buy that connector online, what should I be looking for?
Click to expand...
Click to collapse
I don't think you can find it online. Re solder is sufficient, no need to replace a new one.
But why you need a new connector ? Broken or damaged ? If you need one I may help you where to find it, but change this connector is not simple as re solder unless you know how and have right equipment like hot air gun, hot plate ...etc....
in a worst case scenario.
Beut said:
I don't think you can find it online. Re solder is sufficient, no need to replace a new one.
But why you need a new connector ? Broken or damaged ? If you need one I may help you where to find it, but change this connector is not simple as re solder unless you know how and have right equipment like hot air gun, hot plate ...etc....
Click to expand...
Click to collapse
As of now, things are fine. The tablet is working fine even on longer duration of usage like playing videos on YouTube app continuously or video calls. The battery charge is lasting long besides there is no overheating like it happened before when the connector was loose. Thanks again.
However, when the connector got detached earlier, I observed that the plastic used to design that component is of pretty cheap quality and I doubted if it would stand even before I soldered. Anyways, I managed to solder that without breaking/damaging it. My fear is that the plastic base on which the (metal) connector components were placed in side-by-side fashion would disintegrate if when the plastic base gets damaged and that is my worry. I hope you understood my point.
Also, I would appreciate if you point me to any links that would explain a little more about these components.
Hi,
I've seen many people making threads out if hardware issues, so I thought about making a roll-up sticky thread (if mods agree with it) about them.
In my case, I'm experiencing 2 really irritating ones that made me contact Razer Support already, currently waiting for an answer.
Whenever my phone hits 100% of battery, the phone stops detecting the charger (probably to avoid killing the battery, which okay, it's nice), but then after just 1 single second, it detects it again. In loop. This is the second time I let my phone charge overnight and I fear my screen will burn because of this, since there's no option to avoid the screen to turn in when charger is plugged in.
Also, in the 4 days I've had it, in a random moment of time whenever I'm just using my phone for WhatsApp, or Chrome, and I transition to another app while the previous app was handling the camera, I can see my screen freezing with a few colourful stripes all over it, on the left hand side most of them. After that happens, 1/4 of the times it happened I managed to get it working again, the rest 3/4 my screen turned off after that and, don't ask how but even though the panel is off, it detects touch input, and the only way to turn it back on is a force reboot pressing all three buttons in the device.
Shall I request an exchange unit? I've had this one for 4 days and idk how normal this is.
NFC hardly ever worked and when it did each terminal said I was trying to use 2 cards at once
Speaker grill at the bottom was lifting off
FP scanner stopped working had to do 5 factory reset and rub the scanner with a wipe constantly to get it to work again
Charger was making very bad buzzing noises when charging (this was completely replaced by razer in have the replacement already)
RMAd to razer (after a fight with Three) was a green one had to get a silver one :/ it's en route to razer ATM so using a Stupid wileyfox phone to get by and it's driving me nuts. I swear if they say the speaker grill was damaged by me and thus the cause I'll freak! Buying the phone was a pain in the ass enough just for it to be a crappy model.
Thinking bout selling it and getting a different phone when it comes back but I'm still torn as everything else was perfect for me.
Roxas598 said:
NFC hardly ever worked and when it did each terminal said I was trying to use 2 cards at once
Speaker grill at the bottom was lifting off
FP scanner stopped working had to do 5 factory reset and rub the scanner with a wipe constantly to get it to work again
Charger was making very bad buzzing noises when charging (this was completely replaced by razer in have the replacement already)
RMAd to razer (after a fight with Three) was a green one had to get a silver one :/ it's en route to razer ATM so using a Stupid wileyfox phone to get by and it's driving me nuts. I swear if they say the speaker grill was damaged by me and thus the cause I'll freak! Buying the phone was a pain in the ass enough just for it to be a crappy model.
Thinking bout selling it and getting a different phone when it comes back but I'm still torn as everything else was perfect for me.
Click to expand...
Click to collapse
If you still see NFC issues with the new unit you get, it would be cool if you could drop me a bug report zip, I would take a look.
Alex
TheCrazyLex said:
If you still see NFC issues with the new unit you get, it would be cool if you could drop me a bug report zip, I would take a look.
Alex
Click to expand...
Click to collapse
If I decide to keep the device I will indeed Alex :good:
I had these horrible lines in my screen and the bottom speaker was messed up. I RMA'd and they fixed the speaker but the lines are still there just not as obvious.
I'm sending my unit back due to vibration motor issues. Besides that it seems good.
@TheCrazyLex, mind having a look at this (that's 1/2 of my issues):
{
"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"
}
Dunno if kernel related due to graphics drivers or actual HW issue. Support team considers it's hardware so I'm currently in terms of RMAing my unit. Want a logcat/dmesg of it? Happens specifically when there's a transition between apps, or when using the camera. Sometimes it happens to hang my phone right after those blue/green stripes appear, on the others hitting the home button restores the device back to it's normal state.
linuxct said:
@TheCrazyLex, mind having a look at this (that's 1/2 of my issues):
Dunno if kernel related due to graphics drivers or actual HW issue. Support team considers it's hardware so I'm currently in terms of RMAing my unit. Want a logcat/dmesg of it? Happens specifically when there's a transition between apps, or when using the camera. Sometimes it happens to hang my phone right after those blue/green stripes appear, on the others hitting the home button restores the device back to it's normal state.
Click to expand...
Click to collapse
I think it's a hardware issue because one of the two dsi lane communication failed.
linuxct said:
@TheCrazyLex, mind having a look at this (that's 1/2 of my issues):
Dunno if kernel related due to graphics drivers or actual HW issue. Support team considers it's hardware so I'm currently in terms of RMAing my unit. Want a logcat/dmesg of it? Happens specifically when there's a transition between apps, or when using the camera. Sometimes it happens to hang my phone right after those blue/green stripes appear, on the others hitting the home button restores the device back to it's normal state.
Click to expand...
Click to collapse
Yep that looks like a hardware issue, no logs should be needed here.
I hope the RMA process will be quick for you!
Alex
Right now I've had 2 issues.
1. The vibration motor is extremely rattly, especially when the phone is on vibrate or double tap power to open the camera.
2. I've got a stuck pixel at the top of the screen and a dead pixel at the bottom, along Whit what appears the screen ever so faintly flickering. I'm currently in contact with Razer to see what they can do about it.
Edit: I've just had a group of dead pixels form at the bottom of the screen a few days ago. I contacted Razer and they are going to do an RMA on it.
I guess mine is more software but the phone app keeps crashing.
I loved my Razer phone, I really did but had a few critical issues which led me to sell.
Vibration motor was week, kinda like a rattle but I think thats with everyone phone. Couldn't feel it in my pocket.
NFC was terrible, took me 10 attempts at a local Tesco to find the right spot, other places it just wouldn't work.
Screen was a tad too dim while using it as a satnav, probably more of my placement of the phone holder but the sun glare would always hit the screen making the viewing really hard.
I'd still recommend the phone though, great device but just for my usuage I couldn't cope.
Sent from my Pixel 2 XL using Tapatalk
I had a speaker issue with the first razer phone where the bottom speaker was distorted and top speaker was fine, then sent it in got a replacement phone and now the top speaker is having issues. Its not distorted but it is less louder and has less quality then the other speaker. Plus i used a noise generator app to test it and i started to smell a little bit of burning coil from the top speaker. I will send it in and get another one and hopefully its not messed up. The main reason to why i have not yet rooted is because i wanna make sure the speakers are fully functional. In my opinion these speakers shpuld not break under 3 weeks. Can you guys run some tests to see if your phones speakers have the same issue? Thanks. I love the phone btw. So good.
Had the phone 6 days and the speaker grills are lifting, gutted isn't the word
When I use the phone in landscape mode (with volume buttons on the bottom) the sound coming from speakers are inverted. Does anyone have the same issue?
Micro SD card only works in FAT32 file system, I formated to original exfat the SanDisk 400GB came with and phone said "unsupported file system,need format" I'm fine with fat32 but just 4GB file limit I don't like even phone itself uses exfat file system as u loaded 8gb file to phone from PC, I'm talking with customer support about this but no luck they just go around and say "did I reset phone" or did I tried micro sd card as internal storage, I tried, no way to put file then as nor pc nor file manager sees micro sd then, and internal storage is about 250mb read and 100mb write, while micro sd is about 80mb read and 60mb write on SanDisk A1 400gb micro sd ps. Card works on Xperia z and Xperia Z2 with exfat file system just fine
---------- Post added at 03:14 AM ---------- Previous post was at 03:13 AM ----------
el4nimal said:
When I use the phone in landscape mode (with volume buttons on the bottom) the sound coming from speakers are inverted. Does anyone have the same issue?
Click to expand...
Click to collapse
YouTube -> stereo sound test and top speaker is right bottom is left
sonyzz said:
YouTube -> stereo sound test and top speaker is right bottom is left
Click to expand...
Click to collapse
Yes, but when I tried to play Dolby Atmos Demo is inverted, which is ironic
el4nimal said:
Yes, but when I tried to play Dolby Atmos Demo is inverted, which is ironic
Click to expand...
Click to collapse
But you don't watch demo everyday lol
sonyzz said:
But you don't watch demo everyday lol
Click to expand...
Click to collapse
You never know :-b
el4nimal said:
You never know :-b
Click to expand...
Click to collapse
No exfat support for micro sd is still bigger issue than stereo reverse since, not deal breaker but can't load 1080p bluray movie which is 16gb in size even I have 400gb micro sd card - limited to 4gb by out dated fat32