Related
Hi . I'm going to replace my vox for TyTn 2 (!) . I need to know , what I need to check if i want to avoid sending phone to services (I think Construction , some problems like bad joystick ... ) ?
i purchased my kaiser brand new in may 2008...so you will probably get better advice from those that have gotten refurbished or second hand units.
anyway, heres a list of items you might want to check (based on my own observations as well as based on the readings/reports of various issues i've read about here on the forum):
1. hardware keys should work 100%. some users buying off ebay, for example, report that the phone works and the FRONT buttons work but the slide out keyboard is shot. just an example, it could be the other way around. but the point is to check and make sure each and every button works.
2. usb connector should work 100%. best way to check is to see if the phone can establish an activesync connection (with a known working cable) and if the orange charging LED lights up. next, hook up a wired headset (that is known to work correctly) to see if the pins for the audio signals are functioning on the usb connector. long press the button on the wired headset to see if the device starts to dial the last number dialed.
3. look out for "dead pixels". there should be NONE. because the kaiser has a relatively low resolution screen with less pixel density, i don't think it is acceptable for there to be ANY dead pixel at all because even one can become an eye sore. a quick way to check is to bring up an all-black screen and see if all the pixels are black. next, bring up an all-white screen and see if all pixels have turned white. also remember that sometimes dead pixels come and go. i've had TWO dead pixels during my ownership of the kaiser. one went away as soon as i flicked the device from the side and it never came back. another one lasted for a week and had me quite worried because it happened after my warranty period was over. i tried "dead pixel 'sweepers'" and maybe they helped because that particular dead pixel also eventually went away after a week and never reappeared.
4. scratches on the camera lens. note that the kaiser has a plastic lens "cover" on the back cover of the device. this part is known to get easily scratched and i don't think it is reasonable to be anal about this part. HOWEVER, if you take the back cover OFF, then the actual camera lens underneath the back cover should be spotless. check BOTH cameras to see if they work and can capture decent images (test the main camera with the back cover OFF to get better results).
5. the slide mechanism should be relatively "solid". look for distortions on the image displayed on the screen as you slide. ensure that the sim remains detectable when the keyboard is slid out. ensure that the front buttons work when the keyboard is slid out. ensure that the microsd card slot continues to work when the keyboard is slid out. all of the above mentioned items are connected to the main motherboard via "ribbon cables" (hidden underneath the sliding mechanism) and sliding out the keyboard can cause faulty ribbon cables to act up. look out for that!
6. make sure the status/notification LEDs work. read the WIKI/manual for information about the normal/expected behavior of the LEDs.
7. the earpiece should work. the loudspeaker should work. the microphone should work.
8. the touch screen should work! try out bubblebreaker so that you can check the responsiveness of the screen across its entire surface. recalibrate the screen if you have to. remember, the kaiser's touch screen can occasionally be a bit fussy if a screen protector is present.
9. look for obvious scratches/damage to the screen and body. try to see if the damage really matters to you (as an eyesore) or to the device (can it affect the device's normal functioning?).
10. check the water exposure stickers under the battery to make sure they have not turned a pinkish color. if they are pink, there is a chance that the device was exposed to some amount (or a lot of) water in the past. while you're at it, check the battery contacts for corrosion (might cause power issues later) and check the battery compartment for any signs that a previous battery may have leaked (extremely unlikely). who knows, maybe the owner had it properly serviced after the water exposure so no harm in asking. if properly serviced at the right time after water exposure, there have been many success stories here on the forum of the device continuing its normal functioning.
ummm thats about it from my side, hope this helps!
TYVM ... i have this phone ... I'm really exited . I'm going to do Hard SPL tomorrow ... I want some good rom ... so what is fast ... and have that D3D driver ??
congratulations!
i answered your original question because it was a bit of a unique question.
but your second question about "which ROM is good and fast" cannot be answered by anyone except for YOURSELF. go ahead and explore the Kaiser ROM Development Section. read about some of the ROMs that seem to interest you. try out a few of them and see what you like and dislike. good luck!
OK ... can you tell me ... what does thet D3D driver ??? and why 101 MB ram and D3D not working together ???
And one more thing ... i try ANYTHING but i cannot set up android and run it .... And also I don't know how to make that default.txt
And can you explain me this ??? : http://www.youtube.com/watch?v=qL8uq4FtduY
didoop said:
OK ... can you tell me ... what does thet D3D driver ??? and why 101 MB ram and D3D not working together ???
And one more thing ... i try ANYTHING but i cannot set up android and run it .... And also I don't know how to make that default.txt
And can you explain me this ??? : http://www.youtube.com/watch?v=qL8uq4FtduY
Click to expand...
Click to collapse
How about you do some searching and explain it yourself or post in threads related to your topic.
ASCIIker isn't your personal guide through this site.
OK I have been using my N1 for almost 2yrs now. I love it, but out of nowhere the connections on bluetooth, wifi, 3G, and occasionally cellular drop. Coincidentally it happened when 2.3.6 was released and I refused (updated since no change) the update. When I use my bluetooth headset I'm told I sound like I am underwater. I installed CM7 thinking that would solve it (maybe it's a stock ROM issue) but it was still the same. I can put my phone next to the router and still show (1bar) a poor connection .
OK so what can I do to fix this? I don't want to purchase a new phone (besides this glitch it looks mint) right now. Also I don't really have the cash for it either. Someone said the antenna may be loose (don't know how that would happen) and I could open it up and fix it.
Now you all Mod software but has anyone actually opened up an N1 and is there really a way to tighten the antenna? Please let me know if anyone else has had this issue or is there a way to test for a solution.
Thanks
A little more info
Was just on a cell call and noticed that the green cellular indicator turned white (no idea if that's related) it is back to green now and full. However this seems to be a pattern of being green 3G and Cell strength to white. Hope that provides so more info to someone trying to help me.
Green/white is an indication of connection to Google servers, nothing else.
Radio is only responsible for 3G data, bluetooth and WiFi are completely different entities and aren't related to radio. If you're experiencing bad reception - most probably your antenna contacts need cleaning or are misplaced, open the lower cover (not the battery one) and look there (this cover IS the antenna - just don't know which one).
Special tools?
Jack_R1 said:
Green/white is an indication of connection to Google servers, nothing else.
Radio is only responsible for 3G data, bluetooth and WiFi are completely different entities and aren't related to radio. If you're experiencing bad reception - most probably your antenna contacts need cleaning or are misplaced, open the lower cover (not the battery one) and look there (this cover IS the antenna - just don't know which one).
Click to expand...
Click to collapse
OK found a teardown on youtube of the Nexus one so I understand the antenna is on the bottom. However it looks like they used a special tool to open the case on the bottom. Where would I get that? Also considering I paid for it outright (yep unsubsidized direct from Google); even if I'm out of warranty would you recommend (if this is something more complicated) I send it to HTC for repair? Someone else said the Broadcom chip may have gone bad if both the wifi and bluetooth seem to stop working or have poor reception. Not sure if that seems correct since if it went bad I would think it wouldn't work at all but before I make tool marks trying to take it apart I figured I'd ask.
I'm not sure the repair will be worth it, financially.
If you want to open the lower part of the case - you may only need a small flat screwdriver and good hands, to avoid scratching the surface.
Something else now
OK now voice dial command isn't working when I hold the bluetooth button. Maybe indeed it is the chip. I was able to take off the plastic cover but I need to get a T5 screw driver (lol for some reason smallest I have is T6) so I will get one tomorrow and see how it goes. There is one more cover to remove and put back on. Financially since I paid full price I'm not sure why it's not worth fixing? I figured HTC would charge around $100 for a repair. Which is less than going price for a new (i.e. Galaxy Nexus II) phone . Also I haven't seen any new phones with a trackball (which I love for the notifications and when I need precise movement) so I really don't want a new phone till they add something like an optical trackball or improve precision on finger location. Also I might get lucky if the credit card I purchased it on will cover a repair (they double warranties) and I still have a few months left.
Nope!
Jack_R1 said:
I'm not sure the repair will be worth it, financially.
If you want to open the lower part of the case - you may only need a small flat screwdriver and good hands, to avoid scratching the surface.
Click to expand...
Click to collapse
OK got the required tools and took it apart (both covers on the bottom) and then re-assembled it back, making sure I seated the vibrator motor back carefully. Turned on the wifi and still have same issue. So guess my phone is broke further than I can repair it. Thanks for your advice but unless there is software to check that chip it looks like only option is HTC.
Yes, looks like it might be damaged beyond the home repairs capability.
Financially - If I were you, instead of spending $100 on Nexus One repair, I'd sell it for parts for $70 or so, added the $100 you wanted to spend on the repair, and bought a used MT4G in good condition. You'll lose colored trackball (and get a trackpad - which, if you use Sense ROMs that this phone runs perfectly, will be absolutely useless), but gain WAY better phone, in just about every aspect you can think of. The same applies to any phone you can get for cheap from "outdated" MSM8x55 family - Desire HD/Desire Z/G2/Desire S (some of them aren't compatible with T-Mobile frequencies, put attention). I know this from first hand experience, since until recently I had 3 of them - Nexus One, MT4G, and Desire S for my wife. Guess which phone did I get rid of?
But - just in case you'll want to follow this advice and settle specifically on MT4G - make sure you read MT4G forums thoroughly before you do. There are 2 weak points for MT4G - the screen (more important) and the eMMC chip (less important, but still counts). Both can come in 2 variations, better and worse. Make sure you choose the better.
Since the last few days I've been getting some strange issues with my touchscreen. Sometimes parts of the screen (or the full screen) do not respond, and even the softbuttons are affected. When I take the phone out of my pocket, it either responds normally (I use pattern lock) or tries to use the emergency dialer or emergency contacts, and sometimes even tries to call a number from the emergency dialer (number 2 and luckily not 112..)
When in the launcher, it sometimes opens an app (like my calendar) and slowly scrolls either sideways or vertically. Turning the screen off and on again once or twice usually solves it for a (short) while.
I've already read some threads about it and ruled out the following causes:
The phone is not connected to any charger when this happens.
It still happens after cleaning the screen (just with a cloth, no liquids)
It still happens after disabling CPU Tuner. I didn't overlock the system, but used some custom power settings and different governors which apparently can also affect this behaviour.
The battery is still original since nowadays I prefer to use external chargers instead of buying a big battery for every new phone
The only things that changed recently are:
I installed the OwnCloud app, but that doesn't seem related.
We moved to another office building, in which the carpet generates more static electricity.
I gained some weight which may put a bit more pressure in my pant pockets than before
It started happening a few days ago, after using the .215 ICS leak for a few weeks without issue. I seem to get the problem less at home than I do at work, which makes me think it's either the static electricity or CPU governor (since battery percentage is lower by the time I get home again, so it might use a different governor). However, I've been using CPU Tuner for quite some time before this issue started, and the issue persists after disabling it.
So I am guessing it's any of the following causes:
Static electricity
Keeping the phone in my pant pockets which may put some pressure on the screen
A problem with the battery or screen somehow (moisture?)
Some other hardware issue
Some software issue
Does anybody have any tips or other ideas about this? Thanks in advance.
Edit: I enabled some development options to show touch pointer location (white dot) and trails. Screenshot added. Phantom touches seem to be focused in the bottom center part of the phone, which is probably around where I grap it when I take it out of my pocket. Trails usually disappear the next time you touch the screen, but in this case the trails kept growing / adding. I made some real swipes (upper half of the screen) and they 'stuck' without the phone responding to them (the application did not scroll) due to the parallel phantom touches in the bottom. In this case the phantom touches blocked my real input, in other cases they cause some behaviour (scrolling etc.). However, sometimes when the screen is not responding, there are no phantom touches visible in this display mode.
Edit 2:The no-touch input problem seems to be 'triggered' most of the time I open the keyboard. Sometimes this is followed by the phantom touches, but usually they start occuring in the portrait mode lock screen.
Sjaakbanaan said:
Since the last few days I've been getting some strange issues with my touchscreen. Sometimes parts of the screen (or the full screen) do not respond, and even the softbuttons are affected. When I take the phone out of my pocket, it either responds normally (I use pattern lock) or tries to use the emergency dialer or emergency contacts, and sometimes even tries to call a number from the emergency dialer (number 2 and luckily not 112..)
When in the launcher, it sometimes opens an app (like my calendar) and slowly scrolls either sideways or vertically. Turning the screen off and on again once or twice usually solves it for a (short) while.
I've already read some threads about it and ruled out the following causes:
The phone is not connected to any charger when this happens.
It still happens after cleaning the screen (just with a cloth, no liquids)
It still happens after disabling CPU Tuner. I didn't overlock the system, but used some custom power settings and different governors which apparently can also affect this behaviour.
The battery is still original since nowadays I prefer to use external chargers instead of buying a big battery for every new phone
The only things that changed recently are:
I installed the OwnCloud app, but that doesn't seem related.
We moved to another office building, in which the carpet generates more static electricity.
I gained some weight which may put a bit more pressure in my pant pockets than before
It started happening a few days ago, after using the .215 ICS leak for a few weeks without issue. I seem to get the problem less at home than I do at work, which makes me think it's either the static electricity or CPU governor (since battery percentage is lower by the time I get home again, so it might use a different governor). However, I've been using CPU Tuner for quite some time before this issue started, and the issue persists after disabling it.
So I am guessing it's any of the following causes:
Static electricity
Keeping the phone in my pant pockets which may put some pressure on the screen
A problem with the battery or screen somehow (moisture?)
Some other hardware issue
Some software issue
Does anybody have any tips or other ideas about this? Thanks in advance.
Edit: I enabled some development options to show touch pointer location (white dot) and trails. Screenshot added. Phantom touches seem to be focused in the bottom center part of the phone, which is probably around where I grap it when I take it out of my pocket. Trails usually disappear the next time you touch the screen, but in this case the trails kept growing / adding. I made some real swipes (upper half of the screen) and they 'stuck' without the phone responding to them (the application did not scroll) due to the parallel phantom touches in the bottom. In this case the phantom touches blocked my real input, in other cases they cause some behaviour (scrolling etc.). However, sometimes when the screen is not responding, there are no phantom touches visible in this display mode.
Edit 2:The no-touch input problem seems to be 'triggered' most of the time I open the keyboard. Sometimes this is followed by the phantom touches, but usually they start occuring in the portrait mode lock screen.
Click to expand...
Click to collapse
clean you phone with an air duster than a alcohol swab make sure you dry it quickly and use 72% not 90%. make sure you get the corners... get a screen protector and apply that as well. then sbf to 217... and wipe data,,,, that should work.
if not it could be the ribbon cable,,, it may be frayed...
how to fix
http://forum.xda-developers.com/showthread.php?t=1584260
where to get the part
http://cellphone-repair-shop.com/motorola-droid-4-lcd-screen/
myfishbear said:
clean you phone with an air duster than a alcohol swab make sure you dry it quickly and use 72% not 90%. make sure you get the corners... get a screen protector and apply that as well. then sbf to 217... and wipe data,,,, that should work.
if not it could be the ribbon cable,,, it may be frayed...
how to fix
http://forum.xda-developers.com/showthread.php?t=1584260
where to get the part
http://cellphone-repair-shop.com/motorola-droid-4-lcd-screen/
Click to expand...
Click to collapse
Thank you, let me try that. Couldn't find the right alcohol pct. so I'd have to use some generic screen cleaning liquid, would that be okay as well?
My screen was having issues too. So I turned the dot thing on from the dev part as well. The dot seems to freeze as I'm opening my keyboard. And the dot stays frozen in place until I close the scree again. Any ideas on how to fix it? Also if the screen is open and I touch a spot nothing happens, but then when I close the screen it will sense correctly where I touched while it was open.
Sounds like the same problem, so I'm getting the feeling it might be due to the connectors rather than the screen digitizer itself. After cleaning it, I didn't have any issues for a while, but they started occurring again now.
The replacement part is not available right now, a bit expensive, and excludes the price for the required tools which I don't have yet. Warranty may be tricky as I didn't get my phone from Verizon directly. So if it turns out to be a connector issue I will say goodbye to the Droid family and just get another non-QWERTY phone.. at least until Motorola starts selling them (as 'Milestone' since 'Droid' is a Verizon brand) in Europe again. The Droid 4 is the best phone I ever had, this is potentially making it unusable for me though. Glad I didn't order a Lapdock yet!
Motorola will repair your phone for 168... out of warranty and all... I found this cheaper and easier then fixing it myself and guaranteed done right in 5-7 days..
Sent from my DROID4 using xda app-developers app
Mine is still within the one year warranty. So I want to send it in. But I'm afraid they will check for the root stuff and they will consider voiding my warranty because I was rooted. I unrooted and did a factory reset to see if it would fix the issue. So this is my only chance left. I heard clearing the data wouldn't remove the qe process they use to know that I'm rooted. So I'm not sure if its worth the chance.
Flash SBF restores everything to my knowledge. No way to see what happened before the SBF flash.
I read in the original post for the DROID 4 ICS root tool that a sbf will not remove the part that says you were rooted at one point. I checked that first. An sbf flash is really easy. I was really hoping that it would work.
they dont take the time to check that stuff... if you sbf they wont know a thing...
bty found what u need on the cheap
Motorola DROID 4 XT894 Flex Cable Ribbon 27$
http://www.ebay.com/itm/Motorola-DROID-4-XT894-Flex-Cable-Ribbon-/150849219594
If they don't check it then why should I even bother? Does an sbf change something a factory reset doesn't? I've already reset it. I'll look into the fix though. It will depend on if I have the tools to do it or not.
SBF/fastboot will revert rom changes.
About that ribbon cable how would that work as the lcd is fused to the cable?
The Old One said:
SBF/fastboot will revert rom changes.
About that ribbon cable how would that work as the lcd is fused to the cable?
Click to expand...
Click to collapse
Cant be... it is glued in place and has connectors... how else could he sell you the cable by itself... http://www.ifixit.com/Teardown/Motorola-Droid-4-Teardown/7759/1
Just to weigh in on the whole root checking thing, SBFing or fastbooting back to stock DOES NOT remove evidence of root. qe still picks it up somehow in stock recovery.
That being said, they cannot void your hardware warranty for software modifications, it's the law (in the U.S.)
Of course, if you somehow softbrick your phone, they have no obligation to help you.
Edit: Just to clarify, I tried this myself just this morning. Full SBF back to stock + a factory reset, and qe shows 0/1, which indicates currently unrooted but previously rooted. No idea how their security works, but it does.
podspi said:
Just to weigh in on the whole root checking thing, SBFing or fastbooting back to stock DOES NOT remove evidence of root. qe still picks it up somehow in stock recovery.
That being said, they cannot void your hardware warranty for software modifications, it's the law (in the U.S.)
Of course, if you somehow softbrick your phone, they have no obligation to help you.
Edit: Just to clarify, I tried this myself just this morning. Full SBF back to stock + a factory reset, and qe shows 0/1, which indicates currently unrooted but previously rooted. No idea how their security works, but it does.
Click to expand...
Click to collapse
your right but most ppl dont inspect the phone that hardcore... it takes time, and time is money
Yes
Sent from my DROID4 using xda premium
myfishbear said:
your right but most ppl dont inspect the phone that hardcore... it takes time, and time is money
Click to expand...
Click to collapse
I agree it's probably not anything most people need to worry about... I still plan on sending my D4 in before the warranty is up, I've been having terrible wifi + 4G drops, even on stock (that's why I fastbooted in the first place)
I am a bit nervous though, because I've heard horror stories about Moto replacements. That being said, if Ops phone is under warranty, I'd send it in rather than trying to repair it. If it isn't under warranty, then I'd go for the flex cable, the Moto phones are built well and reasonably easy to work on.
Sent from my Galaxy Nexus using xda app-developers app
I probably have some kind of warranty with the seller, not with Moto directly as I have no way of obtaining a QWERTY phone from them (they don't sell those in Europe for some reason). But I really can't miss my phone for an extended period of time, so I'd either need to switch to an old one while I'm waiting, or get a new one.
Since I don't have the tools available to open the phone properly and I don't want to spend any more money on this thing, I'll probably sit it out until it breaks. For now, switching the screen on and off one or two times seems to 'solve' it.
Sjaakbanaan said:
I probably have some kind of warranty with the seller, not with Moto directly as I have no way of obtaining a QWERTY phone from them (they don't sell those in Europe for some reason). But I really can't miss my phone for an extended period of time, so I'd either need to switch to an old one while I'm waiting, or get a new one.
Since I don't have the tools available to open the phone properly and I don't want to spend any more money on this thing, I'll probably sit it out until it breaks. For now, switching the screen on and off one or two times seems to 'solve' it.
Click to expand...
Click to collapse
all u need is a $0.60 guitar pic and a t5 screwdriver(can find at home improvement store). none of those silly tools they try to sell you help that much
myfishbear said:
all u need is a $0.60 guitar pic and a t5 screwdriver(can find at home improvement store). none of those silly tools they try to sell you help that much
Click to expand...
Click to collapse
I still have tons of guitar picks so I just ordered a Torx set for this and future problems.. hope that pushing the connector around a bit can solve it already.
Hey all! So as a bit of a computer/tablet/phone geek and and a bit of an RC Hobbyist, Ive decided to take on a little personal project to combine the two. At least a little bit to start. In the world of RC quadcopters (aka drones) the big thing that everyone is into is buying these expensive 1080P/4k go pros and other gimbal devices to record video. But not only do we want to record, we want to be able to view a live stream of what the drone sees. You can buy these FPV Cameras on the higher end for $500+.
When I bought ny first drone a fair sized flyer at nearly 2ft diameter, my first flight I decided to strap my old Galaxy S3 to the bottom and catch some cool video. Everything went well, and the video was high def and crystal clear. While there are FPV apps such as AirBoss available, unfortunately its a bit glitchy and crashes often so i didnt bother with FPV, just hit record and flew. After this I decided to start looking into purchasing a gimbal and maybe a gopro hero 3. Seems a bit silly buying a $400 camera to carry on a $100 drone, but I considered it and started browsing.
Before buying anything, I had a buddy want to see the drone fly, so on a semi full charge, I took it up, no phone attached, and after about a minute of flight, the battery went low, lost contact with the controller and helplessly watched it drift into the woods, still haven't found it.
So now instead of looking for an expensive camera, im looking to strip down my old s3 and use it as a camera, but also as a GPS locator, which will have data/gsm/gprs connections. The idea being, that not only a does screen less, make shift house, remotely controlled android device act as a camera, but it can be called from another phone (making it easy to track via sound) or worst case scenario be pin pointed on Google maps, in the event of another downed drone.
I have all the apps installed to make this work exactly how I need it to and want it to. In fact I already have the motherboard stripped out of the housing, and am able to do exactly what I want, except one thing.
The only way the phone will turn on, is with the main components from the screen housing plugged in. Its one ribbon, but its the ribbon the feeds the Screen, the digitizer the home, back and menu buttons and the micro phone and the vibrator pod. All of the components on the back side of the board, the front and rear facing cameras, the sim/tf card readers, the loud speaker, led, volume rocker etc can be disconected, as long as the main ribbon for the screen is attached, the motherboard will boot. After booting I can unplug the ribbon, and the phone will remain on, with everything working that I need to work, including remote access.
I guess the main question here is, how can I trick the phone into thinking the main ribbon is attached? Once I can get it to boot up without it being attached to that ribbon I can begin building a lightweight housing for the board and camer and a smaller battery. I thought about cutting the ribbon and just leaving it attached to the board, my only problem with that is IF it wont boot after doing that, I cant just repair the ribbon and I dont have a spare s3 for parts, which would pretty much leave me with nothing but a dead s3 in pieces lol.
I know most of what xda deals with is software development, but im hoping someone has tinkered with hard ware before. Sorry for the novel, just wanted to cover the details and eliminate getting asked why I want to do this. And for the record I want the s3 screen and housing gone for the simple fact that I can cut the weight from abouy 150 grams to less than 30 grams, which is a huge factor when flying quad copters
Hey there!
Recently I bought a Pixel 4 XL and I am loving it. However when it arrived, the 2X camera wouldn't work, and portrait mode neither. Luckily after disabling an app to get my SIM working on this AT&T Pixel, the 2X camera started working back. The problem is that today it stopped working again, and repeating the process of disabling the app didn't solve any problem. I know for sure the camera isn't broken as I took photos with it recently and I want to know how to get this working again.
Thanks in advance
I would force stop camera and gallery and wipe data on those two as well and reboot and see if anything was different. If not I would remove my accounts from the phone then factory reset.. Delete everything and maybe even do it two times just for the hell of it. I would use stock recovery and do this selecting "factory reset" with volumes keys and power button then reboot system afterwards. If nothing changed I'd sell it and I'd be honest online and explain my story and all. I'd pay the difference on a Google factory unlocked model Coral so that when I had any issues down the road I would be bootloader unlocked and I could then fastbood stock images and everything would be fine and dandy. I would also blast whoever sold me the AT&T 4XL that had a carrier encrypted bootloader lock on it on all social media networks, Ebay, Amazon and Swappa. Maybe then pee in a large bottle, like a 2 liter empty bottle and pop the top back on and keep going until it's full capacity screwing the lid on afterwards every time and leaving it some place where it could get maxium sunlight and decent heat like in a field by my house outside. Then I'd investigate them and try and find out anything and everything about them. All y'all need is a name and head over to Facebook and start searching and reading... When MY 2 LITER bottle wasfull I would GPS their address at some odd hour and try and figure out what vehicle belongs to them.. You could run vin and or license plates to see and make sure you have the correct vehicle. You definitely don't want to do this to an innocent person. Then once iz sure I had the proper vehicle I would dump the entire urine bottle in their vent where the defrost is, on outside of their front window where the dashboard is and walk away tossing the 2 liter either in the dumpster nearby or possibly in a trash bag and in a fire once I got home.
I had this done to me once by some punk neighbor in sone apartments I stayed in about twenty yrs ago and me and my gf had to sell her new high dollar sports car because regardless of what we did to do to eliminate the odor it didn't work. It was a goner, a TOTAL LOSS!!! Smelled like a truck stop urinal in the middle of nowhere that hasn't been cleaned in twenty years. I'm totally kidding. I wouldn't do this. Not at age 42. Now back in my teens and or twenties, idk, but not now. I would make sure it was known best I could. Write a few reviews on seller online. Shoot me the address I'll write one up for him to help you out.
While I'm not going to do such craziness this would be sufficient revenge I believe for selling me a carrier locked fairly new expensive Pixel and not telling me. The ole urine in the vent ruin the car maneuver. A one time thing that would cover almost anything anyone did wrong to you in about a minutes time max. Hopefully this made you laugh op and also anyone else who may read it. That is why I'm commenting it. Please don't ban me mods. Again I'm totally kidding. I'm too old for things like this now. Haha!!!I'd sure write reviews about him though online. Hook him up with some fantastic reviews from serval made up characters about how he lied and did this to me.
Hey,
fisrt sorry for tanking so long to answer. I did that but nothing. Sometimes both rear cameras stopp working and the only fix is factory reset, which only brings back the main camera, telephoto still doesn't work.
Yeah it wasn't great that he sold me a locked bootloader, but I mean I can live that and I pay really cheap, 170$ and phone is in perfect shape. Here in Europe the same phone is well over 350$, so I wasn't going to pay all that much for a 2 year old phone. Also I am researching a way to unlock it and I am confident. When I succed I may post a guide here on how to unlock.
However the seller was very kind, when I talk to him about the camera not working, as I know how to fix phones, I said to him if he could refound about 14$ to buy a new camera module. And surely after 5 minutes he refound 15$ to me, so I bought a new camera module and waiting for it to arrive.
Also very funny the history lol .
Hello all,
So I finally mange to find the issue.
As i didn't want to return the phone, I talk with the seller and he sent me 15$ to buy a new camera module and I would change them myself.
To open the phone is easy, at least for me. I saw a few videos online and followed the ifixit guide.
The funny part starts now, when I was going to disconnect the camera module(which have 2 conectors, 1 per camera) I found something interesting. One of the cables wasn't conected to the motherboard.
So when I connect it and test the phone, the camera started to work as it should.
I still don't know how this happened, the phone was never open before (I know because there is adhesive on some conectors, so if you remove them, when you glue them back they aren't perfect).
It would also be very strange for that to disconnect by it's own, because the cable is secure in place by a shield which don't allow the cable to move(or at least, that is what it should do).
Anyway, the problem now is fix. So if one of your cameras don't work, or work sometimes and them stop working, you should consider opening the phone and check the camera conector, It may have disconnected from the socket.
i got this problem too, portrait mode & zoom not working.
0xJ said:
i got this problem too, portrait mode & zoom not working.
Click to expand...
Click to collapse
Download the bsg gcam mod go into your gcam settings on "photo modes session config" and set interface to pixel 3
rchad2423 said:
Download the bsg gcam mod go into your gcam settings on "photo modes session config" and set interface to pixel 3
Click to expand...
Click to collapse
thanks for the reply, but I have been fixed it by disconnect the camera module and connect it again