Does anyone else have a dead pixel?
I just found one... (you can find lots of dead pixel test apps in the playstore, I used this one: http://goo.gl/OA935). I will return my device. This and the loose hardware buttons are too much to handle...
Related
I have this thing for almost 2 years now and am disappointed as hell with it.
Hardly anything could be done with it, hanging all the time, slow as hell and some hardware issues like the brightness sensor faulty in low light situations leading to flickering.
All I did with it at the end was reading with Kindle, because once started that at least worked. Even browsing the net...impossible.
First I hoped they would fix it with a new rom. But after one year, like I guess a lot of us, I gave up hope.
The second year I was tied in with my exams and really needed the device for reading and could not send it back.
Would they even swap it for that reason?
Now almost two years after I bought it, and that is the warranty time here, I finally send it back.
It now had some other hardware issues too, like the power jack was bend in all directions.
They changed the complete motherboard and now I can't recognize my device anymore.
That thing is suddenly snappy as hell! I mean you still can't compare it to my Nexus4 but it is definately usable now.
I can even install&update apps and surf whilst, this crashed the device not only once before!
I wonder what happend. Was the board really (memory) that faulty?
Or did they swap the slow memory with newer modules that may not have the same restrictions as the old ones.
Can I find this out somehow (without opening the device)?
Did you have to pay or did they do warranty repair? It's a faulty device as is, and like you hubby and I have been super disappointed. Of course, we just unlocked to try a new rom Any hope of getting it fixed??
No it was fixed under warranty.
I recently got my hands on one of these really unique devices, clearly a prototype as I've never personally seen something like this before, I've attached pics I took with my oneplus one, device powers on, WiFi and Bluetooth work, android 2.2.1, odd sized 22gb storage..
But I know NOTHING about it, what brand, what model, what CPU, ram and so on,
Google does not give me anything about it, so I'm at a loss of knowledge here, I'd like to find out more info about this unique device..
Anyone with some insight here please chime in and gimme an idea what I'm working with here
I remember working on this phone. It was definitely ahead of its time..
Hi there!
First off: I used the search, but am not confident I haven't overlooked something.
If so I'm sorry!
I have a google pixel with lineage-for-microg, whose battery I had replaced some months ago.
Afterwards I wanted to reflash stock android to start afresh and then reflash lineage.
I'm back on lineage 17 (derived from Android10) and have the following problem:
During calls the microphone in speaker mode doesn't work at all, meaning, the person on the other side doesn't here a thing.
The same happens for speaker calls in other apps.
What still works, is audio in videos I take with the camera.
Also the ambient light sensor seems to have stopped working as the automatic luminosity doesn't work and I have to set the light by hand.
And then the proximity sensor during calls doesn't work.
I'd like to fix these and therefore I would like to find out, whether it is more probably a software or a hardware problem.
I found on this forum that it may have to do with the persist.img, that may have been corrupted by twrp.
Unfortunately I don't know where to get a hopefully working persist.img to try that out.
Things that are maybe relevant are these:
1. The battery was changed, so maybe the engineer doing that broke something
2. During reinstallation of lineage17 I had some problem with twrp not working. Afterwards using lineage recovery worked for installing lineage, but I'm not sure, twrp might have broken something.
3. The same issue also is there on stock android 10.
Can anyone point me in some direction?
I realized that the easiest check for software/hardware distinction would be to just flash a new persist.img.
Is anybody out there, that has a pixel sailfish device with working android 10 that would drop me a message? I should be able to just transplant your persist.img to my pixel sailfish.
I would greatly appreciate it!
Edit: Sorry, I misread your post. You're having microphone issues and not speaker issues. Don't have much advice.
In my experience the proximity sensor and ambient light sensor on Pixel XL's never fail. I've repaired dozens and never seen it.
Bongzerker said:
Edit: Sorry, I misread your post. You're having microphone issues and not speaker issues. Don't have much advice.
In my experience the proximity sensor and ambient light sensor on Pixel XL's never fail. I've repaired dozens and never seen it.
Click to expand...
Click to collapse
Nonetheless, thanks for your time!
If I may ask for even more of it:
Not sure, whether Pixel XL and Pixel are similar when it comes to their hardware ( I have a Pixel, not a Pixel XL), but if you have repaired many of them, do you think it is at all possible, that the hardware shop that changed my battery somehow broke these sensors or forgot to reattach a cable to them?
I don't plan to hold them accountable, as I really like them, just would like to have a hint, whether going to the hassle of bringing my phone there and thus not having it for a few days has a reasonable chance of success.
Hey there yall, so I've had the LG 360 cam for ages now. Found it recently while cleaning out my junk draw and it holds a charge but I can't seem to get it to connect to anything. Searching the play store there are no apps compatible with it. Anyone know of a way to use it or is it just a dead device?
I'm currently trying to find any information on how to fix a hard brick with a pixel 2 where it shows up in windows device manager as Qualcomm hs-usb qdloader 9008 or qusb (without drivers). I always seem to find myself back at This post on how to fix this but no one seems to have an answer. In that pose he says
I need to use QFIL to flash correct, prog_emmc_firehose_xxxx.mbn, together with rawprogram_XXX.xml. What is that? Does anyone happen to know where to get it?
I believe that those two files are the key I also seem to find that Google does not release them for the pixel. I'm hoping that someone has somehow managed to obtain them and put them online.
Please reply with any information you know.
I also have this issue on my Pixel 2, it seems that there is no other fix for this but to replace the motherboard. I'm still waiting for the motherboard that I ordered online, hopefully it works.
I had a version pixel 2, and I put the motherboard in mine, but I'm bummed because the one I bricked was an unlocked 128g model. I'm hoping I can figure it out in my spare time.