Related
I've seen a few hit or miss issues that have been coming to light since the release of the TF700 infinity. On some devices, it seems to work and on others, not as well or not at all. From this, it seemed quite necessary to have a thread to identify the issues that others may encounter and for what they should check to know if they have a "good device" or whether it should be returned. Please let me know if their are any items that should be related to this list. If you wish to discuss your tablet's attributes (both good and bad) further, Pretoriano80 has made such a thread: [Infinity issues/defects/good features] Share your issues, defects or best features
Make sure you charge your tablet before using! Explanation in point 3.
Also, do not update past 9.4.5.26 during these tests if you want to use NVFlash!
1- Does your device have good build quality?
Some people have found that there are scratches on the device, frame's bent, the display is poorly set, the ports may be improperly mounted or other such things. It is recommended that if you encounter any of these that you return the device to get another one since you paid a lot of money for a "good" device. The tablet might click at corners, some of the backlight might bleed through around the edges of the display, or maybe show a slight but often not serious protrusion of the screen from the device. It's up to you to judge whether the extremity of this occurrence on your device are serious enough to warrant a return depending on your definition of "quality".
A possible test for "light bleed" is to take a picture from the camera in either a dark room or the camera lens covered (objective is to take a "black" photo). Open the image in the gallery app and turn up the brightness on the device. In this fashion you should be able to notice any "severe" cases of light bleed like this. If the light bleed is little and only noticeable during startup, then it's probably nothing to worry about.
2- Does your device have haptic feedback? (Does it vibrate properly?)
When you turn on and off your device, it should vibrate. This vibration will be subtle like the feeling of a working electrical appliance and not like a console joystick. If it doesn't, then it probably is defective. There are various methods to getting some type of jiggle out of the tablet if you want a more extensive test. One example is to add such feedback to your on-screen keyboard via Settings -> Language & Input. I'll just go over the basic "Android Keyboard". Select the sliders button next to the keyboard, look for "vibrate on keypress", put a little check next to that, then go into "advanced settings". By default, these vibrations are set to 1ms which is a duration too short to provide any feedback. Adjust the "Keypress vibration duration settings" to something like 100ms in order to ensure that the buzz happens. Finally, verify that your default keyboard is set to the "Android Keyboard" and then open up something like SuperNote where you can type. You should have some buzzing upon every keypress. When done with this test, just go back into the keyboard settings and disable the "vibrate on keypress".
3- Is your battery life ~9 hours in power-saving mode or ~6 hours in balanced mode?
Some people have noticed that they either never reach this amount or never come close to it. This is kind of an expected behavior since on the first page of the instructions manual (you did read the manual, right?) it mentions this:
"Fully charge the battery up to eight hours for the first-time use. The battery reaches its maximum capacity after one full charging and discharging cycle." Therefore, one is supposed to charge the battery for up to an 8 hour period prior to use and then discharge the battery (until ~10% or so). You may encounter a variant of this concerning "a few cycles" but still, right after tearing the plastic off the box like a rapid child at Christmas, ensure that you just plug it in and forget about it for 8 hours (or until the charging light turns off). Otherwise, it can have a lasting negative impact on battery life.
More information about Li-ion can be found here.
4- Does the GPS work?
The TF700 shares a few things with the TF201 Prime (which had notoriously bad wireless, including Wifi communication, Bluetooth, and GPS). Some owners of the Prime didn't remember to check GPS even when everything else worked and later needed to get a Dongle. Ergo, why I put it here high on the list. I believe many of the issues dealing with hardware and software have been addressed by ASUS so if your GPS doesn't work, try updating (not past 9.4.5.26!) the device or send it back since it might be hardware related. Make sure that when testing, you have the "find location via wifi" option turned off if using Maps. Otherwise, test with a tool from Google Play Store like GPS Status or GPS Test. Note: testing may involve going outside and dancing with the device as the first connection is often the most difficult to get.
When GPS is working, you should see a little circle with a blinking dot inside in the lower right-hand corner. Sometimes, the dot might not blink and can seem to influence how well GPS programs work. Its a strange thing but with a simple solution (from myself encountering it on both the TF300 and the TF700): just open the notifications bar and close it again. The dot should be blinking. If not, try actually turning off and then turning back on the GPS via the notifications bar.
5- Does mini-HDMI work?
Though not necessarily a tendency of faults in the infinity, it is important to check all the offered functionality of the device prior to making it a permanent fixture in your life. Remember that if you don't have a friend with a mini-HDMI cable, Walmart (and many other stores) will accept returns provided they are within a particular time period. Feel free to use this return policy to test your device.
6- Can you watch video/youtube/netflix/etc while using a bluetooth headset?
Some people have noticed that there is a huge decrease in speed when watching a video while using a bluetooth headset for audio. The cause of this is unknown and the only explanation we know of is "because wifi and bluetooth share the same antenna". This seems plausible except that many other devices also use the same antenna for both functionalities yet do not display this behavior. Due to the underlying fact we do not know whether it is software or hardware related, it is advisable to return the product.
7- Does the headphone jack work?
Just for thoroughness and ease-of-testing, plug in a set of ear buds and make sure you hear sound. Some have complained that the quality is mediocre due to a humming noise but that the noise is negligible. If the noise is too pronounced, there still is the mounted speaker and if point 6's test was successful, bluetooth is still an option.
8- Does your device feel quick to respond? If not, are you on firmware version .26?
It has been widely noted that version .26 of the firmware made the tablet very snappy. This also helped the device to recognize more microSD cards but also caused problems with NTFS-formatted drives. If you aren't getting the response you want, try upgrading to .26 (not beyond that). Additionally, if your microSD card is NTFS, you may want to reformat it (backup whatever you want to keep first) to FAT32 or exFAT until the issues with NTFS are ironed out. This point also concerns point 9 further down.
9- Can you receive OTA updates? (This should be fixed since Aug 7)
Provided that you are on version .21 or .22, you should be able to receive updates from ASUS for your device via the "About Tablet" option in settings. If you cannot, this might be indicative of another issue which has yet to be identified. You can apply updates without OTA via these methods:
(easiest way)[HOW TO]Tired to wait the .26 with WW TF700 device?
(another way)*** Firmware News & Alternative Install Methods*** Ver. 9.4.5.26 27/07
(requires root)[HOWTO] Manually updating firmware using "dlpkgfile" download via Asus FOTA server
(requires unlocked bootloader)[HowTo] Restore Stock Recovery and Install .26 OTA Manually with Unlocked Bootloader
(requires unlocked bootloader and TWRP custom recovery)[CWM] Repackaged OTA update 9.4.5.26 US/WW versions
Make sure you do not update past 9.4.5.26 if you want to use NVFlash!
10- (Only if this is important to you and then only if you are willing to forego any ASUS warranty) Can you unlock the bootloader? (This should be fixed since Aug 7)
Bonus Warning: ASUS has noted that using their bootloader unlocker will void your warranty and all OTA updates for your device will cease. However, without this unlocking, you will not be able to run custom ROMs nor will you be able to use NVFlash to make your device brick-proof.
[Device is unlocked][Video Added] Bootloader Unlock Tool Released [25.7.2012]
If you are still within your store's "grace period", you may want to try this out to verify if your device will ever be able to run non-ASUS android systems. There's no way of knowing at this moment if the bootloader unlocker will work on your device without actually trying to unlock it. If it does not work, it might be due to their service being unavailable, your serial number might not yet be in their database of devices for the unlock to succeed, your device serial number internally might not match your external serial number (on the sticker), or the problem might be something else entirely. Many of those whose bootloader would not unlock did not receive OTAs either so this shares the "issue which has yet to be identified" from point 9.
If you can give your tab a :good: to all of these points, then you have a good device! Congratulations! :highfive:
Maybe check out these threads next:
[INDEX]-[Updated -25 July 2012]-ASUS INFINITY TF700 - INDEX THREAD-DEVELOPMENT-PART#1
[RESOURCES] How to Root, Unlock, ROMs, Recovery, Tips & more [VIDEO TUTORIALS]
1.Yes
2.Yes
3.Yes
4.didn't try that yet
5.yes
6.yes
7.I don't care
Sent from my GNexus
Yep, mines a keeper.
Build quality is acceptable .. (I own an ipad also) ...I'm going to say 80% the build quality of the ipad. It does OTA and manual updates just fine. Headphone jack works. Has slight click if you press the screen by the speaker ...but only noticable because I read here that it clicks if you press by the speaker . Speed, temps, light bleed, battery life ....all as expected ...not perfect but perfectly acceptable. I am enjoying the tablet, and have no major complaints. I can only assume it will get better with JB when it comes out.
The ipad is more polished, faster, easier to use ....but not by a huge margin. And I make allowance for the immaturity of android tablets and the OS compared to ipad and iOS. I think the trade off is worth it for the additional control... and eventual rooting of the device.
Price ....hmmmm... perhaps a bit high compared to the ipad.... about $75 less would have been nice ....but it's basically a toy for me so I can't complain too much. And part of the whole thing is I wanted a tablet....and I wanted to support the Android market so it would stand a better chance at competing with the ipad... because honestly I think Andriod is the future of tablets ...not iOS.
I'd say the single disappointment is ....I bought the tablet to watch motorcycle racing videos from MotoGP.com, which I pay about $120 US a year to be a member ..... guess what...the tablet will not play the archived videos from this site ....it will stream live video fine, it will play all other "current" content fine...but will not play the archived videos ...... my iPad plays them just fine. I'm in contact with MotoGP.com trying to solve the problem ...but it's not a new problem ....its across the Asus tablet line.
Still.... I enjoy the TF700T, and think it's a good product ....although perhaps should be offered at a bit more of a discount compared to the iPad ....for now.
I have no regrets.
JohnnyB
ray3andrei said:
1.Yes
2.Yes
3.Yes
4.didn't try that yet
5.yes
6.yes
7.I don't care
Sent from my GNexus
Click to expand...
Click to collapse
Just want to mention these numbers are apt to change due to new things becoming evident as community use increases.
dataway said:
I'd say the single disappointment is ....I bought the tablet to watch motorcycle racing videos from MotoGP.com, which I pay about $120 US a year to be a member ..... guess what...the tablet will not play the archived videos from this site ....it will stream live video fine, it will play all other "current" content fine...but will not play the archived videos ...... my iPad plays them just fine. I'm in contact with MotoGP.com trying to solve the problem ...but it's not a new problem ....its across the Asus tablet line.
Click to expand...
Click to collapse
This thread is really just supposed to be a developing checklist for people to verify their tablets since it seems that not all problems are experienced by all users and some problems are more extreme than others. That being noted, how did you try to access said videos? Is there a specific program or application you are required to use? Did you try other such programs from the Play store? Since you are paying for your access, I doubt it would be something that a non-member would be able to assist much.
Yes it is a keeper
Plays HD content flawlessly
The GPS is sooper dup on the road
The WIFI sensitivity is exceptional
Can be viewed outside easily
I really like the hotspot tethering performance also
Pretty much a sweet package
I use it a lot around the house to help me with DIY project info...
1- Does your device have good build quality?
10/10, clicks a a little but IDGTF.
2- Does the GPS work?
Yes.jfif
3- Does mini-HDMI work?
Never tested, never will.
4- Can you watch video/youtube/netflix/etc while using a bluetooth headset?
>2012
>bluetooth headphones
ISHYGDDT
5- Does the headphone jack work?
Yes, makes beeping rarely when I start videos.
6- Does your device feel quick to respond? If not, are you on firmware version .26?
Yes, like butter. I still want jelly Bean though.
7- Is your battery life ~9 hours in power-saving mode or ~6 hours in balanced mode?
6 hours in balanced, yes. Never go to power saving because lag.
8- Can you receive OTA updates?
No, bootloader unlocked.
9- (Only if this is important to you and then only if you are willing to forego any ASUS warranty) Can you unlock the bootloader?
Already did
The only issue I've really had with my device after upgrading to .26 is occasional lock-ups. One lock-up concerned me enough to feel a need to return the device. The screen filled with vertical (if holding landscape) white bars. Has anyone else experienced such issues?
I haven't tested the HDMI yet. And other then the inability to OTA or unlock everything is working perfectly on the latest build
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
funtapaz said:
The only issue I've really had with my device after upgrading to .26 is occasional lock-ups. One lock-up concerned me enough to feel a need to return the device. The screen filled with vertical (if holding landscape) white bars. Has anyone else experienced such issues?
Click to expand...
Click to collapse
My friend found one at Best Buy here in NJ. I told him to return it (not exchange) because of the amount of light bleed alone. He was not able to update it, and it just kept crashing on him which made it almost impossible to use. He's going to try hard reset it again to see if any of that helps.
1- Does your device have good build quality?
Mine is perfect.
2- Does the GPS work?
GPS so far works great without using the AGPS to assist.
3- Does mini-HDMI work?
Have a cable from my Prime, both worked flawlessly as does my Bionic.
4- Can you watch video/youtube/netflix/etc while using a bluetooth headset?
Funny thing it does drop from about 20 Mbps to about 3Mbps down, but that won't change no matter how far from the router. The upload is 4Mbps on both no matter how far from the router. It's not the dual antenna that's the problem, it's that they both use one controller chip for the two.
5- Does the headphone jack work?
No problems on mine.
6- Does your device feel quick to respond? If not, are you on firmware version .26?
Was definitely laggy on .21, on .26 MUCH better especially in performance mode. I'm excited for JB.
7- Is your battery life ~9 hours in power-saving mode or ~6 hours in balanced mode?
I charged about 4 hrs till green/fully charged. Funny thing is you can't overcharge these new batteries now and days. They are set to auto stop charging once full (that's the benefit of them now) So I have never "overcharged" because it's not possible. That being said I did a full charge, and am working on the first full depletion to recharge. I'm at 62% and that's 3 days later lol. I have been using it light/moderate the past few days. At least 3.5 hrs of Netflix streaming, setting it up, and not turning it off overnight. We'll see but so far so good and Ifinitely (like that ) better than my Prime.
8- Can you receive OTA updates?
Not OTA, manual worked just fine
Good list, thanks. Mine has passed all of these so far but the headphone test. I forgot that one. I guess I'll give it a shot tonight.
" "Fully charge the battery up to eight hours for the first-time use. The battery reaches its maximum capacity after one full charging and discharging cycle.""
It says" upto 8 hours" It doesn't mean you NEED the full 8 hours. Once you go green and are 100% fully charged, the charger shuts down on its own so not to overheat the battery. The "upto 8 hours" is for folks charging their device via USB on their PC - - which can take up to 8 hours to getting that full charge.
I just got mine yesterday, and while I haven't had time to test either HDMI or full battery cycle (though it's doing pretty well so far) all else is wonderful. Great screen, OTA update to build 26, great wifi and gps, headphones work fine. Sound out of headphones and BT headset is actually great. I do have a millisecond lag with BT audio and watching streaming video, but I could actually live with it, it's not that bad.
This one is definitely a keeper.
I have a quick question while I'm checking my tablet, which arrived yesterday... my screen is uniform across the edge, no creaking or inconsistencies, but the entire surface is raised, or at least isn't flush like my previous Prime. Is that normal? Anyone have a completely flushed screen on their 700? Thanks.
Sent from my Incredible 2 using xda app-developers app
androidxen said:
I have a quick question while I'm checking my tablet, which arrived yesterday... my screen is uniform across the edge, no creaking or inconsistencies, but the entire surface is raised, or at least isn't flush like my previous Prime. Is that normal? Anyone have a completely flushed screen on their 700? Thanks.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
My Gorilla glass has about a quarter inch beveled edge going all the way around
xRevilatioNx said:
My Gorilla glass has about a quarter inch beveled edge going all the way around
Click to expand...
Click to collapse
So I guess the screen is higher due to the hardware improvements from the Prime. Good to know, just wanted to be cautious.
Sent from my Incredible 2 using xda app-developers app
xRevilatioNx said:
My Gorilla glass has about a quarter inch beveled edge going all the way around
Click to expand...
Click to collapse
Same here - more like 1/16th inch, maybe?
Mine looks perfect, but if I press a bit harder on the screen (you won't do this with normal usage) I get a hissing noice which sound like air is escaping from between the screen. At that moment I can see deformations on the screen. I have read other people do have the same issue, but wondering if this is normal (so all TF700 have it?) or if I should exchange. Any advice?
I have one really big scratch on the dockingstation. Going back to the store tomorrow to get another one.
Added xRevilatioNx's and neo1738's clarification regarding initial battery charge and the green charging light turning off.
Yeah, I agree with you that the new batteries can't be overcharged in the literal sense. It was merely to emphasize the fact that a "full charge" is necessary to receive optimum life out of the device's battery. We don't really know what type of charge existed on the device prior to our receipt, so it's best (or in a worse case scenario) just to charge it for the 8 hours regardless of the status of the light. Does it make a difference if it's 8 hours or until the green light turns off? Probably not. But for the Android neophytes just getting their hands on a tablet for the 1st or 2nd time, I think that my explanation is still applicable and satisfactory to provide a perspective easy to understand and beneficial to the consumer. Thanks for the detailed clarification though.
Received my champagne gold today and doesn't seem to be any issues at all. No light bleed, WiFi and bluetooth are perfect, and no I/O issues (updated as soon as I turned on the device). Seeing as the champagne golds seem to have come latter in the production cycle, it seems they are improving their processes slowly but surely.
I'm currently on a Moto x (2013), coming from a Galaxy Nexus. I switched because I needed a faster phone, and the GN hardware is just too dated. The moto x seemed perfect, until I found out I can't tether, root, or unlock the bootloader to save my life.
That being said, I'm in the market for a Verizon S3, which will likely already have 4.4.2 installed. My main concern is root access and native hotspot tethering (unlimited data). The following are what I have found thus far:
1) root: http://www.andromods.com/root-unlock/sch-i535-vzw-galaxy-s3-kitkat-rooted-nc1-ota.html
2) tethering: https://www.youtube.com/watch?v=PxBRrsucdLo <---- the guy who created the vid doesn't have VZN, so was hoping someone here can verify if that works.
3) bootloader: I found nothing on unlocking a VZN bootloader, but this is the least of my concerns
4) ROM: http://forum.xda-developers.com/gal...nt/rom-superliterom-v1-0-i535vrudne1-t2805797
My assumption was always that an unlocked bootloader was necessary to flash ROMs through custom recoveries. I'm unfamiliar with safestrap, but I'm all in for a bit of reading and enlightening.
Again, I don't necessarily need a custom ROM or bootloader. My main concerns are still tethering (main priority) and root access (second priority)
Thanks all, and I definitely appreciate any help at all!
rice923 said:
I'm currently on a Moto x (2013), coming from a Galaxy Nexus. I switched because I needed a faster phone, and the GN hardware is just too dated. The moto x seemed perfect, until I found out I can't tether, root, or unlock the bootloader to save my life.
That being said, I'm in the market for a Verizon S3, which will likely already have 4.4.2 installed. My main concern is root access and native hotspot tethering (unlimited data). The following are what I have found thus far:
1) root: http://www.andromods.com/root-unlock/sch-i535-vzw-galaxy-s3-kitkat-rooted-nc1-ota.html
2) tethering: https://www.youtube.com/watch?v=PxBRrsucdLo <---- the guy who created the vid doesn't have VZN, so was hoping someone here can verify if that works.
3) bootloader: I found nothing on unlocking a VZN bootloader, but this is the least of my concerns
4) ROM: http://forum.xda-developers.com/gal...nt/rom-superliterom-v1-0-i535vrudne1-t2805797
My assumption was always that an unlocked bootloader was necessary to flash ROMs through custom recoveries. I'm unfamiliar with safestrap, but I'm all in for a bit of reading and enlightening.
Again, I don't necessarily need a custom ROM or bootloader. My main concerns are still tethering (main priority) and root access (second priority)
Thanks all, and I definitely appreciate any help at all!
Click to expand...
Click to collapse
Root is still possible. Tethering *USED* to work on stock by using the FoxFi app. I haven't tested it in quite some time though. There's a limit for the free version, use it for testing though.
Sent from my SCH-I535 using XDA Free mobile app
I actually made the jump already. Sending this from my s3, boot loader unlocked, twrp, and running cm11.
Thoroughly enjoying this! Tether is flawless too
rice923 said:
I actually made the jump already. Sending this from my s3, boot loader unlocked, twrp, and running cm11.
Thoroughly enjoying this! Tether is flawless too
Click to expand...
Click to collapse
Do tell how. Especially if you did start with a Verizon galaxy s3 sgh-i535 that was not rooted and was running on stock Verizon Android 4.4.2
To clarify, I bought it set up this way. I knew clearly well that I wouldn't be able to get any of this with stock 4.4.2.
On the other hand though, the camera won't focus correctly when taking pics, and the charging is ridiculously slow. My only two complaints
rice923 said:
To clarify, I bought it set up this way. I knew clearly well that I wouldn't be able to get any of this with stock 4.4.2.
On the other hand though, the camera won't focus correctly when taking pics, and the charging is ridiculously slow. My only two complaints
Click to expand...
Click to collapse
Hey Rice,
I'm still on the GNex, but my wife just offered up her old GS3. It's still on 4.1.2 unlocked, rooted. I'm working on bringing it up to speed...still reading....
P.S. Is there no kernel fast charge option?
Rushead said:
Hey Rice,
I'm still on the GNex, but my wife just offered up her old GS3. It's still on 4.1.2 unlocked, rooted. I'm working on bringing it up to speed...still reading....
P.S. Is there no kernel fast charge option?
Click to expand...
Click to collapse
I remember seeing you around MWs FML thread! 5.0 is looking decent over there, so I'm very happy for them.
If you get the chance, I'd definitely recommend CM11. It make me feel like I'm running a nexus device again, except significantly faster than the gnex with a better camera.
Regarding the charging speed, I don't think it's a kernel issue. With the phone plugged in, I keep getting notifications that it's being disconnectedAnd reconnected spontaneously. I've done some reading and and it seems there is a bit of oxidation or hardware issue within the charging port. The port also requires soldering of the mother board to change. I've resorted to ordering some qi chargers[emoji106]
As for the camera, this seems to be an old issue of cm11. I flashed a camera fix zip, but to no avail. The focus issue seems to be problematic only at macro distances though. I can't find a fix besides touching to focus prior to taking macro shots
Rushead said:
Hey Rice,
I'm still on the GNex, but my wife just offered up her old GS3. It's still on 4.1.2 unlocked, rooted. I'm working on bringing it up to speed...still reading....
P.S. Is there no kernel fast charge option?
Click to expand...
Click to collapse
With 4.4.2 if that's what your referring to you can't change the kernel like those of us who are unlocked
From my CM11 S3
ShapesBlue said:
With 4.4.2 if that's what your referring to you can't change the kernel like those of us who are unlocked
From my CM11 S3
Click to expand...
Click to collapse
No, it's 4.1.2 I put her on Andy bonestock years ago and never touched it again.
Rushead said:
No, it's 4.1.2 I put her on Andy bonestock years ago and never touched it again.
Click to expand...
Click to collapse
Then yes there are several kernel options for fast charge. I know of lean kernel and ktoonsez off hand that are
From my CM11 S3
Don't want to start a new thread even though the title is irrelevant at this point, but was hoping someone could chime in regarding the camera auto focus issue. The camera focuses beautifully when I touch the screen, or when I allow it to autofocus. When I proceed to take the pic, it will try to focus again and take the pic right as it's completely blurry. This happens on both the stock CM11 camera and google camera.
I tried to flash the zip mentioned here http://forum.cyanogenmod.org/topic/85493-camera-wont-focus-cm11/ and nothing has improved.
Does anyone have any insight about this? These symptoms are identical to what many have mentioned in the thread above, so this is certainly not an isolated incident. Thoughts or input?
Who reads titles anyway?
I flashed Slim, and messed around with the camera a little, but I had wifi issues and am in the process of flashing cm11 11-09.
On Slim, the camera seemed to work fine. I took some "macro-esque" shots of text that came out pretty good (at least as good as the GNex, if not better).
I'll let you know how it fares with cm11...
So far, camera FCs on hitting the "No Thanks" button for location reporting.
OK, Camera is now functional (probably didn't wait long enough for the phone to settle on initial setup). The quality is mediocre. I'm still messing with it and will report back.
switching phones, want to keep/root the old Galaxy s3 as a lab/toy
Have an old Verizon Galaxy S3. Just got a new TMo Sony Xperia Z3 (which I am liking so far).
Will soon disconnect my Verizon service. Would like to root the S3 and use it wifi only as a experiment/toy thing, since there's no trade in value (cracked screen).
Possible? Cyanogenmod recommended?
I'm a total n00b at all this, and would steer totally clear of it for my main driver. But since I don't really NEED this phone anymore, thought this would be a safe way to dip my toes in. If I brick it in the process, no great loss.
Any advice or links would be much appreciated. Definitely want it to keep working as a wifi device and not brick once I cancel my Verizon service. Would be cool to be able to play with some of the fringier apps that require root. Those are my only requirements. Camera, cell service, etc all unnecessary. But do need wifi and don't want to create a big vulnerability to the rest of my home wifi network from this device once I'm done.
Thanks again!
evbb, depending on your current OS version, you might be able to root. If you are on the most current official OS, then you will likely just be staying with that.
Rushead, any update on how CM11 11-09 is going? If everything looks stable, I think I'll make the jump to that build.
Update about my charging times: The phone seems to charge at a normal rate if I use a 12V car charger made by Griffin (item does not specify amperage). I don't believe amperage has antying to do with my situation, as I've been yielding miserably slow charge times with the Nexus 7 (2.1 amp) charger. The phone is also very picky with cables. I've used 4 different AC adapters so far in different combinations with 4 different USB cables. I don't know what to think of my charging situation anymore...
When my wife had the phone it was extremely loose as far as cables went. I could use virtually any cable whereas my GNex is super picky.
I haven't had much time to mess with the camera yet. I'm using it as a WiFi device, too, so I can't comment on data, signal, etc. But so far it seems pretty stable. The battery drain is excessive imo. On standby for most of the day, battery was dead by 10pm. That's factory kernel.
For those looking for a decent tethering app there's one on sale, free on the Amazon app store. Easy Tether is the name of the app. It's free 11/14 & 11/15
http://www.amazon.com/s/ref=amb_lin...d_t=101&pf_rd_p=1973721462&pf_rd_i=2350149011
From my CM11 S3
rice923 said:
I've used 4 different AC adapters so far in different combinations with 4 different USB cables. I don't know what to think of my charging situation anymore...
Click to expand...
Click to collapse
You should try a very specific type of cable. The problem is the fact that you use a data cable at all. What I use is an aftermarket universal USB cable and it has the detachable tip for other phones. What this does is force the phone in "Charging (AC)" mode no matter what charger you use. Attached are 2 pictures to help identify exactly the kind of cable to solve your issue. I can charge my 7000 mah battery attached to my phone in 5 - 6 hours. A 2100 ah battery should be 1 - 2 hours with this.
Sent from my SCH-I535 using XDA Free mobile app
Some chargers identify as a USB hub rather than an AC adapter, and others do not. This is why on some chargers, it still charges slow. If ever the phone thinks it is on USB, it will not allow more than 650mah to pass through the cable. So even if you had a 10amp charger, it would not use that much if it identified as a hub.
Using the cable I mentioned removes the ability for any charger to send the identifier info to the phone. Reason? You are missing the data+/- cables that data is transmitted through. Only the +/-5v wires remain.
Sent from my SCH-I535 using XDA Free mobile app
But why would the phone have a constant disconnection and reconnection while being plugged in? That's the part that confuses me.
Regardless, I just received my qi charge in the mail! It's been pretty nice so far! I'm happy to answer any questions about it if anyone is interested
Rushead, wanted to give you a heads-up about the latest CM11 build I used. I clean flashed 11-15 and everything was great except for the camera, which consistently gave me a "cannot connect to camera" error. Otherwise, it seemed like a great build with some great options. I gave up and clean flashed 01-15. Camera is all great except for the autofocus issue mentioned before. GPS lock is great, and battery life is loads better than my GNex days.
Regarding my qi chargers, I am pulling a net positive charge of 315mA on my house charger (Nexus 7 2.1amp AC adapter). This is with the phone turned on, connected to Wi-Fi, screen off, and doing nothing.
My car qi charger is doing about the same. I ran the GPS with screen on (auto brightness) and the charger only charged the phone 3% in 2 hours with screen on and GPS running the whole time. I might switch the DC socket to the included one to see if I get better results.
PSA: *This will be crossposted in xda HTC One X and HTC One X+ forums, I hope cross posting is allowed, haven't seen it mentioned in rules.*
Hi all,
Quick disclaimer: I've been lurking parts of xda now and again for a couple years now, have flashed a couple of phones and tablets now and again for mainly practical reasons, recently getting more interested in it as a ""fun" interest or "hobby".
SO: I am very aware that this is my first post, the rules, search function, etc. ..
BUT: After extensively searching both google and specifically xda to help me resolve this issue *myself*, I decided to create an account and post. I'm sorry if this Q should have been put in the newbie thread, my assessment was that it probably has no place there.
ALSO PLZ NOTE: What was meant to be a succinct summary and question somehow turned into a condensed but complete rundown of events, so here is a...
TL;DR:
- Replaced HTC One X+ display/digitizer unit myself, ran fine for 5 weeks.
- Then: flashed twrp 2.7x or 2.8, not sure anymore, before installing Android HD Revolution 33.1 by mike1986, and following the official instructions, which ran great for about week until my phone spontaneously BRICKED THE F*CK OUT COMPLETELY.
(yes, true brick, paperweight, robot-corpse, whatever)
=> Question: IS "RETROACTIVE/RETROGRADE BRICKING POSSIBLE/A "THING"??
If so, what could I have done wrong? (POSSIBLY something to do with a bootimage of firmware that I was sure I had the up to date version of... dunno though).
=========================================================================
About 6 weeks ago:
- Cracked the display of my HTC One X+ badly by dropping it onto concrete-type floor at a rave/party
=> Decided to try and replace it myself, researched for a good while (talking several days here, 90s/00s kids),
=> Decided to replace the display/digitizer unit myself to save money and gain knowledge.
Repair process was challenging and nearly as nerve wracking as playing the WSOP (not kidding, have played it three times), had an issue immediately after putting it back together where it suddenly wouldn't charge AT ALL anymore (NO LED), and overheated, and had unusually fast battery drain of its remaining charge (which never ran out completely before resolving that issue, since I kept turning it off whenever possible).
=> Took it apart and put it together again XX times until realizing the power switch flex cable kept slipping out of its two (jawbone?) connectors during putting it back together (I was doing something wrong with the flex positioning).
=> This resolved the issue.
=> Felt like a hero and that I win at life (since this phone has a rep as being hard to meddle with, and this was my first time even opening, let alone taking apart a smartphone).
=> Continued joyful phone shenanigans for over one month.
=> THEN: Decided to root it, mainly because there was a particular app I wanted that required root ("Quick reply for Whatsapp/Pushbullet", for the curious).
My previous, very limited rooting/flashing experiences =
- Google Nexus One (CWM/Cyanogen) a few times, years ago
- Galaxy Tab 10.1 (CWM/Cyanogen 10.1 ages ago, TWRP/Omnirom Kitkat 4.4.4 recently) a couple times.
So, did my research (or so I thought..?) for this particular custom ROM, decided to go for Android Revolution HD for HTC One X/+ 33.1 by mike 1986 (because it looked fckin awesome, and it was, while it ran) and loved the sh*t out of my "new" phone for about a week. Especially the vastly improved battery life seemed almost surreal, a big deal for a fixed-battery phone.
Then, ONE FATFUL EVENING in a bar, I remember looking at my phone and seeing 35% left, (days before it would've been an amazing 70-80% on an avg. day), which may not be relevant as it was my birthday, so had been using it a lot that day => may be a moot point
- Next time I looked at the phone ( < 1 hour without active use for sure) it was dead.
"Hmmmm," thought slightly drunk me. Whatever, charge it later, weird sh*t happens.
- Got home later, charged it over night after booting it with usb cord attached (mains).
Seemed normal, I even set an alarm.
=> Alarm never rang because it was in a powered-off state again come morning, despite all-night charging.
=> It booted to HTC logo. Seconds later, it turned off again. Held down power again, all I saw was the soft touch buttons flashing red a few times. After this it unexpectedly became (or was secretly crowned):
!! COMPLETE AND UTTER FCKNG KING BRICK OF BRICK COUNTRY AND ATTACHED TERRITORIES !!
No power on with or without volume up/down held for whatever amount of time;
No charging, no heating up when "charging";
No LED in any colour or flashing frequency, ever;
No response after hours and days of charging on different USB cables on PC/wall socket;
PCs and laptops don't register a sign of anything when it penetrates their port parts, etc etc...
...
.Even that semi-mystical bright-light-exposure-while-charging "light sensor manipulation" thing (which apparently worked for a lo of people with similar issues) did nothing for the cause.
Promotion: *Paperweight status successfully acquired.* Yay.
=====================================================
Now, obviously my first thought was that the power flex that gave me trouble during display replacement probably slipped again., somehow (I had taped it down solidly I thought).
=> SO I opened it once again, flex position seemed ok, but I wasn't sure of its functionality as it did look kind of battered from the somewhat unprofessional repair I had conducted on it (which I openly admit to, though I really did try my absolute best).
- Spontaneously took mainboard/battery combo to a local independent phone/accessory shop after being told they'd take a look for free
(I was in there was in there buying a microsim adapter so I could use my ancient Nexus One, since my GF has my old S2 now, which she kindly offered back, but its hers now, so nah. Great phone though.)
=>Shop's advice echoed my thoughts: Flex cable may be screwed, I may have damaged it by bending in the wrong direction/too often, and that damage somehow didn't manifest until much later. I didn't mention the recent rooting + flashing as I deemed it irrelevant at the time.
Their secondary thoughts: Battery or mini-usb port fukt, (which would require soldering, which they don't even offer).
=> SO, feeling confirmed in my layman's assessment, I cheaply got a pristine new replacement flex on ebay, double checked all videos/tutorials, implemented the damn thing with considerably more skill/experience and even higher anticipation. What happened next was shocking:
Absolutely nothing, obv.
=> Did an additional epic f*ckton of internet/forum research, found similar problems and some resolutions, but no real answers, probably because my main problem translates to a kind of hybrid question.
So here I am now am with my core question:
Is it possible to FULLY brick an HTC/any smartphone but not become aware of this until one week later, when the device dies OVER ONE WEEK of reliable and amazing performance?
(and if yes, what aspect/stage of the flashing process is this likely related to?)
If the answer is NO, it must be a hardware fault with probability rank (I think)
:
1.) Battery dead for whatever reason
2.) Mini USB OR mainboard/integral component (equal rank as not sure), possibly caused by incompetent repair, but why or how would this express itself over a month later??
3.) Other, which I'm not aware of.
While researching new ROMS for the N1, I realized that I may have messed up on the "bootimg part" of the flashing process of the Revolution ROM, a part I found v. confusing in the instructions, even after rereading them many, many times. It was about the most recent firmware, which I was pretty sure I had anyway, since it was unrooted before and I do remember installing some firmware updates over the air.
I still did my best to follow the instructions though.
=> Maybe this has something to do with it, i.e. the hardware can't accept a charge because the software allowed it to become too uncharged (a fairly paradox concept to me, but apparently it can happen. Guess it's like a BIOS-type thing).
Thank you for anyone who read this far!
As it stands, I refuse to give up hope so soon after experiencing that rush of having fixed it myself.
Any specific or general help, tips, hints, pointers, replacement phones (One M8 or S5 plz., Iphones will go straight on ebay) would and will be greatly appreciated!!
The obvious choice is to get a new battery and see what happens, but I'm not sure if I wanna sink any more money into this phone, only to later find out the mainboard is at fault (not worth the money replacing), AKA "get a new phone without a contract", which would more than suck for me financially atm (Im ignoring my N1 here, which I love, but don't wanna be stuck with, esp. as it has the standard-issue broken power button (which I actually had repaired once under warranty, back in the ol' days of yore some prefer to refer to as 2009.
So guys: What's my move, if there is one, besides going to a local/online service centre (I live in Germany btw.) and probably paying unproportionate cash money to even have it looked at?
Cheers, thanks, merci, danke
PS: Just saw the polling function, so I attached one just for the hell of it, to see what happens (never used one before).
If you feel both qualified AND so inclined as to pass judgement on this here serious business, please indicate what you think may be the cause of my issue.
*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!
I have problem with my Nexus 6 (no warranty) from last two months. Phone is on 7.0
One night I noticed my phone says it is charging over USB when connected to the quick charger so it is charging very slowly (more than 8 hours from 0-100%).
I was using the Motorola Charger when it start to do only USB charge. I tried different "regular" chargers and multiple USB cords. All yield the same results. So it seems to be some faulty hardware but I don't know which part.
Also i noticed that PC has stopped recognize it when it's connected - it only show USB charging. I don't have option to set connection to MTP (alternative I found it in developer options - same result)
Already tried:
-different chargers
-different usb cables
-factory reset on marshmallow
-downloaded Nougat on phone
I sent it to 2 different repair centers of Motorola in India.
1 changed the port and still the problem persisted.
The other one was a more advanced service center. They took the phone for around 2 months and then they told me there is some hardware problem and it would cost around 60% of the device cost to repair the problem. (It is equal to Rs. 30000 which is more than even the price of a brand new OnePlus 3)
On asking the problem, they just kept telling there is some Hardware problem which they couldn't explain but they knew this would repair the device.
Now I'm a student. Somehow i bought a Nexus 6 that too when its prices were at peak (Rs. 48999) with my parents help.
I use it as my only primary gear. Now it takes around 7 hours to fully charge if kept on Airplane mode and that too without using it.
Its just a waste i am keeping because i cannot afford the repair and even cannot but a new Phone.
Choosing Motorola sucked! (I still trust Google and love it)
I saw TK using Nexus 6. I was much excited. I saw all his videos. It was fun but now even he has dumped the device.
Now i just keep on trying my luck on Giveaways by XDA expecting to get a device.
(I was too excited when they had a Pixel Giveaway by Rhinoshield but unfortunately i didn't win)
All my hope is XDA Giveaways coz i can only trust them.
If you find any solution to this problem please do reply here or mail me.
It would be of great help.
DivyanshuLeo said:
I have problem with my Nexus 6 (no warranty) from last two months. Phone is on 7.0
One night I noticed my phone says it is charging over USB when connected to the quick charger so it is charging very slowly (more than 8 hours from 0-100%).
I was using the Motorola Charger when it start to do only USB charge. I tried different "regular" chargers and multiple USB cords. All yield the same results. So it seems to be some faulty hardware but I don't know which part.
Also i noticed that PC has stopped recognize it when it's connected - it only show USB charging. I don't have option to set connection to MTP (alternative I found it in developer options - same result)
Already tried:
-different chargers
-different usb cables
-factory reset on marshmallow
-downloaded Nougat on phone
I sent it to 2 different repair centers of Motorola in India.
1 changed the port and still the problem persisted.
The other one was a more advanced service center. They took the phone for around 2 months and then they told me there is some hardware problem and it would cost around 60% of the device cost to repair the problem. (It is equal to Rs. 30000 which is more than even the price of a brand new OnePlus 3)
On asking the problem, they just kept telling there is some Hardware problem which they couldn't explain but they knew this would repair the device.
Now I'm a student. Somehow i bought a Nexus 6 that too when its prices were at peak (Rs. 48999) with my parents help.
I use it as my only primary gear. Now it takes around 7 hours to fully charge if kept on Airplane mode and that too without using it.
Its just a waste i am keeping because i cannot afford the repair and even cannot but a new Phone.
Choosing Motorola sucked! (I still trust Google and love it)
I saw TK using Nexus 6. I was much excited. I saw all his videos. It was fun but now even he has dumped the device.
Now i just keep on trying my luck on Giveaways by XDA expecting to get a device.
(I was too excited when they had a Pixel Giveaway by Rhinoshield but unfortunately i didn't win)
All my hope is XDA Giveaways coz i can only trust them.
If you find any solution to this problem please do reply here or mail me.
It would be of great help.
Click to expand...
Click to collapse
Greetings and welcome to xda. It looks like you found the correct place to ask your question already
http://forum.xda-developers.com/nex...harging-pc-t3481441/post69416407#post69416407
so I'll close this one up.
Good Luck
Sawdoctor
Hello all,
My 1 year old note 20 ultra bougth on wondamobile because it was cheaper that in my country and had the snapdragon version.
Just got this HUGE problem, i was watching a youtube video and the screen just got black all of a sudden, and for 2 days never lit up again.
I live in Europe and Samsung says they wont cover the warranty of it as it wasnt purchased in Europe.
This is completely ridiculous, the phone costed 1300 euros, top of the line.
And now all of the sudden just dies.
I have tried all the methods online and none of them works, conecting a hdmi usb c cable to the screen, the iphone conects but i can only see the hours and a lock, cant unlock the phone, even tried with a mouse and keyboard using a usb c hub and nothing works.
Anyone knows a real fix for this?
as a new screen is 400 € and i dont want to pay this value.
This never happened specialy with a high end phone.
The N20U has had some display issues... Sorry.
Likely the display, could be a connector, battery or mobo failure.
See if you have legal recourse, otherwise lean all over Samsung like a cheap suit.
In the end you may need to do it out of pocket.
Last drama free rollout from Samsung was the N10+Snapdragon (new ones still available for $800). I got a second one because of Samsung's and Android 11/12's lack luster performance.
Some don't think it's that bad...
I sure do, which why I stepped back and rejected 5G, variable rate displays, no flagships SD card slots and one of the most dysfunctional Android OS's ever released.
I'm in a holding pattern running on P and Q until the fallout settles. Minimum 1-2 years perhaps longer.
This problem also happens in the note 10, s20 and others.
The biggest issue is that its a phone from South Korea and im In Europe so the warranty isnt valid.
Was so happy with it until now. Its not the 5g, neither the Android version.
According to what i read this issue is caused due to the one ui 3.1 update.
Because if it was a screen problem the touch wouldnt even respond to touches and it does respond.
Battery was at 81 percent went this happened, and the mobo for sure is good as i can conect the phone to screen and see it like Dex problem is the phone is locked so i cant unlock it even using this option.
And once again as the screen is locked it isnt recognized by usb so no program will work to get the data out of it or try any solution using dex.
As its a version bougth in Sk when i called the assistence they say they cant even do nothing because they only get parts for European phones and that parts are diferent, but the screens must be the same in both versions what differs is the mobo.
This is giving me headaches
Are you saying the update is causing hardware failures or that the black screen is not hardware damage but a just firmware issue?
The phone was working fine.
Until with the last updates the wi fi got inconsistent and i have the best and fastrst internet in my country.
Also as in this image shows the phone does work , problem is i cant unlock it. If i could probably could reset the software.
As the screen only had a minor scratch, so it was never damaged.
Now a 1300 euros phone is just a paper weigth
If it's a firmware you may be able to pull up the boot menu... and go from there.
This is beyond my skillset but it's not a paperweight yet.
I tried it all.
Would be easy if it worked via usb or via dex.
But its stuck in it.
This is a Samsung problem on the latest phones.
Raid3n__pt said:
I tried it all.
Would be easy if it worked via usb or via dex.
But its stuck in it.
This is a Samsung problem on the latest phones.
Click to expand...
Click to collapse
Try letting it fully discharge until auto shutdown if possible.
Physically disconnect the battery, hard reset.
Try some Google searches to find more options.
You might need to pay a repair shop or Samsung to fix it.
It wont shut down. Its like this for 2 days
Removing the battery will be dificult also.
Yeah its going to cost 400 euros for a phone npw worth near 900 or less altough its unlocked.
Will never buy a flagship again.
You don't need to remove the battery, just disconnect it. Watch a tear down vid.
You need a heat gun or pad, anhydrous isopropyl alcohol to help break the rear cover adhesive, plastic picks and perhaps some drivers maybe not. A new OEM rear cover seal.
A good phone repair shop can easily do this for you. Start there and see what you got.
The QC was solid on the N10+ Snapdragon but less so after especially on the S21U.
If the display needs to be replaced that should be the end of your problems with it.
Not perfect but what are you gonna do?
With Samsung, all phones it's best to wait 6 months and see what crops up. Otherwise it's more of a gamble.
I was indeed going to buy the note 10 plus back then but then i saw the n20 and all the advertisement and let myself into the hype.
Even bougth first a oneplus 8 pro but it got stolen in spain and i was refunded
Well going to try for one more day and see if it comes back to life,wich seems like a dream rigth now.
In last case will try a techician but its going to be expensive as this is a korean phone in europe.
Raid3n__pt said:
I was indeed going to buy the note 10 plus back then but then i saw the n20 and all the advertisement and let myself into the hype.
Even bougth first a oneplus 8 pro but it got stolen in spain and i was refunded
Well going to try for one more day and see if it comes back to life,wich seems like a dream rigth now.
In last case will try a techician but its going to be expensive as this is a korean phone in europe.
Click to expand...
Click to collapse
May not be as bad as you think.
Shop around. Getting the right replacement parts is critical. I know on the 10+ the C port pcb, cam module, and obviously the mobo are different and not interchangeable, not sure about the display!
Lol, found out the hard way with the C port pcb, there are 2 variants for the Snapdragon! My C port wasn't bad but was replacing the battery so decided to do the C port for $20 more. No cell service, no internet... put the original one in, back in service. Rather irritating
Ricky tricky Sammy...
This seems to be a design fault so Wonda should honour a repair or replacement. I would pursue it with them.
I also have a N20U SD HK version bought from them but it's only 6 months old.
I take it their warranty is just one year then?
Yes its only one year. And i bougth last october
And the problem is that i live in europe, wonda mobile is from china.
I dont know if its a design flaw or update problem as the phone magicaly started to work witouth the screen theme i had but i puted it down and the screen once again went off.
The phone was working back again for 10 minutes and black out again.
So the screwn migth be good.
I got a message saying the one ui stoped working when i used dex.
Dex mode with a usb c hub now works, but i cant put the phone back to stock while in dex.
Its in portuguese language but what it says in the message is that a one ui error happened.
This after the screen black out again.
In dex i cant put firmware back to stock but can update the firmware.
This is just stupid a 1300 phone with a faulty screen or software problem.
Cant figure it out. As the touch isnt working while is conected to dex, only worked using a mouse and keyboard.
But the touch worked when the screen went back on even for 10 minutes.
So if it works on dex it cant be mobo or battery.
If its the screen i will be 400 euros in pain.
Who would guess this n20 purchsee on wonda mobile would be a nigthmare
Likely a hardware issue...
blackhawk said:
Likely a hardware issue...
Click to expand...
Click to collapse
But how if it works in dex mode, everything works in dex mode, internet, cameras as well, games open, so the mobo cant be bad.
Guess the crap screen is gone for once, as it was only on for 10 minutes. Or maybe something disconected as i droped like 2 or 3 weeks ago but that cant be checked witouth opening.
Raid3n__pt said:
But how if it works in dex mode, everything works in dex mode, internet, cameras as well, games open, so the mobo cant be bad.
Guess the crap screen is gone for once, as it was only on for 10 minutes. Or maybe something disconected as i droped like 2 or 3 weeks ago but that cant be checked witouth opening.
Click to expand...
Click to collapse
When I said hardware I was implying the display.
It still could be a loose/bad connector as well.
The mobo's not entirely ruled out yet but a less likely candidate.
This seems to have happened to a lot of other people too, and some of them have said the display has come back on.
Samsung need to get a grip and offer some advice to affected cusomers.
For sure it seems the display is gone.
Samsung would replace the screen if it was bougth in Europe amd the screen had no damage.
Mine has a minor scratch and a very small mark due to a drop.
Anyway seems there wont be any fix, as the crap screen only worked for 10 minutes so no hope for it to be back on again
Samsung never again