yashsingh1/xdaforums huggingface dataset:
[Nexus 7 General] JaSauders:
Was it even detemined as an absolute fact that the DAC was a very cheap one, or is that just what everybody assumes since a few reviews got out about sub-par audio quality when it's more than likely they were listening to poorly compressed audio tracks? There's been enough reviews swaying the other way, citing it's better than a lot of tablets out there to suggest it's not nearly as bad as some people once said.

On the topic of the USB port, it's almost inheret by design that this would be an issue. I've seen the usb ports fall out of phones already. It really comes down to how the tablet is treated when plugged in. After all, there's very little depth to a micro USB port, and the stiff end of it is long enough (as some users have already said) to create some serious leverage.
[Nexus 7 General] Soldier-2Point0:
I managed to bend the USB port back to shape. I will add the pictures to this thread if anyone else wants to try and fix.
[Nexus 7 General] EvilDeadFan:
A good reminder never to drop any electronics.

It's better to be safe than sorry. Don't hold it while on the phone and while paying little attention etc. ;) A little patience goes a long way. Thanks for the repair tip, some users will benefit from that, but be careful with how much force you put on it.

Better results might be better had with some needle nose pliers.
[Nexus 7 General] altimax98:
Seems a lot like the original Nook Color
[Nexus 7 General] Luxferro:
If we're lucky the 4 pin pogo-pin contacts on the side of the N7 are actually USB pins (VCC, D+, D-, and GND), so we can use it for both charging and USB stuff. Then we can get a dock and not have to worry about wearing out or damaging the USB port.

The Galaxy Nexus only had 3 contacts, and could only charge via the contacts.
[Nexus 7 General] Nexcellent:
This a million times. Thank you for speaking my mind! :D
[Nexus 7 General] Soldier-2Point0:
My USB Port has worked fine after performing the fix.

Sent from my Nexus 7 CM10
[Nexus 7 General] srry20wnu:
I have this EXACT same problem. Same bend/break in the usb and the EXACT same spot. Same reason too, is there any way to get this fixed?? I bought mine through gamestop unfortunatly but i did pay for the warrentee and i took it in they said to call a number on the box and see what they can do about physical damage.. gamestop says they only replace for nonphysical damage.. wtf. lol... but anyways. is there any way i can get this nexus 7 fixed 100% or replaced for a new one?.... please help.. i really want this fixed.. worked all summer for mine.. :(
[Nexus 7 General] Soldier-2Point0:
Look at the pictures I posted on the first Page. This is what worked for me and I still use the tablet without issues charging.

Sent from my Nexus 7 on official CM10
[Nexus 7 General] JD914:
This is the very reason I wish wireless charging was the standard for all mobile devices.
[Nexus 7 General] Soldier-2Point0:
Lumia will release a batch of devices that charge when placed on top of a pad.

http://www.techgoondu.com/2012/09/09/nokia-reboots-lumia-phones-with-pureview-and-wireless-charging/

http://www.youtube.com/watch?v=8Q8tlSDpVDI&feature=youtube_gdata_player

Sent from my Nexus 7 on official CM10
[Nexus 7 General] AJ Bryant:
This really did work lol. And I was out of warranty. They wanted to charge me $75.. Thanks OP
[Nexus 7 General] espionage724:
The USB port's design could be intentional. If it was just one piece without that cut, and you drop the N7 with something in the port, you'd run the risk of snapping the entire port off the board, which would be far harder to fix.
[Nexus 7 General] gsmyth:
I have the same issue, the original cable actually broke and would no longer charge (just replaced the USB cable), my nexus still charges but can be a bit loose when plugged in/doesn't feel as solid a connection as previously.

When you plug in the cable, where are you pressing/putting pressure with the tool? Are you pressing below the port on the case itself and with the large end or the screwdriver end? Cant make it out from your photos sorry.
[Nexus 7 General] alfmetal:
That's what I did , I preordered the pogo pins charging dock and I use a wireless USB stick on the back of my router to transmit files ( mostly custom Roms and music ) . I only use the n7 usb port when there's no way to avoid it , like restoring to original when I soft brick the tablet.

I did the same thing for my galaxy s4, pre ordered the wireless charger since day one.

I know they are expensive buy worth it.
[Nexus 7 General] arsene28:
this is helpfull, it fix my charge problem when it's turned on. but there still other several problems...
[Nexus 7 General] lexritz:
nexus 7 charging port / micro usb

The micro usb charging port on the nexus 7 is notorious for becoming useless b/c cords fit loosely in the port right out of the box. Micro usb cords get wiggled and jiggled because of the size of the opening and then the port will no longer charge b/c solder breaks from the board, or the tongue inside the port partially breaks apart.

You can buy the replacement micro usb / headphone jack assembly for about $50 and do the repair yourself (hopefully) ...or you can send it to us and we'll replace just the jack and ship it back to you all for $54.95

More info and our repair form is on this page:

www rockhoptec com/services.php#t...

Visit us at: www rockhoptec com

please call or email with any questions!

(585) 487-8220

alex @ rockhoptec
[Nexus 7 General] nikitis:
Don't put any pressure on that glass when you try to bend that port back. My glass on my nexus 7 cracked when I went to sleep and woke up the next morning. Nothing at all hit it or touched it. I can't explain it, but some people have had issues with sudden glass cracks on the device.
[Nexus 7 General] Netero Pito:
Thank you !!!
[Nexus 7 General] mnelsoneorm:
Qi charging?

My wife completely broke the USB connector so I was looking into building a charger to connect via pogo pins but I've also seen some info on adding a Qi receiver under the back cover (of course you would still need a Qi charger). I ordered a galaxy S4 receiver on amazon for $10 and I'm going to wire it to the inside of the pogo pins. From what I've read you can still charge via wire after the mod. I may still attempt to build a pogo charger but the drawback to that is that it will be difficult to stop someone from reversing the connector. I'll have to carefully mold the connector to the case shape and see if I can be sure that it cannot be connected backwards. I'm guessing that this is the very reason ASUS didn't ever make a pogo charger for this unit.

BTW - the dock is currently $100 on amazon which is why I'm not going to go with that solution. I already bought my wife a N7-2013 (and I've told her she can only use the Qi charger) so I can freely monkey around with the old 2012 N7.
[Nexus 7 General] lostinthetriangle:
Brought my n7 2013 in May 2014 just before I was to have spine surgery, figured it would be better than staring at a small phone screen! I loved it from the first time I turned it on from the screen to the "just right size to fit in my hand" That was until it stopped charging about 6 weeks later....

No service center here in the triangle so I decided to take it apart. That was easy, had a look at the port and it was looking good n strong put it back together still no charge. Took it apart again and had a look at the pins from the port soldered onto the board, turns out that's the problem. After a little heat from a soldering iron it started to charge again.

There is very little solder and one of the pins was just about making contact. Almost like a common cold solder issue. Why in this day we should be putting up with this kind of crap is beyond me. A lot of people have had issues with the usb port on the N7, Hell the usb port itself in almost any device, it is to problematic and I will be happy to see it gone!

Will re-flow the solder and order a new board.
[Sony Xperia P, U, Sola, Go] awaprc:
Thanks to the members of this forum, I re-flashed the Gingerbread OS on an Xperia S purchased in China, with a generic UK system. This enabled me to install many Google apps. including Google Play, that were otherwise unavailable to me.

I am now able to upgrade to ICS (going by my SI number) but if I do so, what version with I get? Will it revert back to a Chinese OS with no Google or will it realise I have a generic UK OS and update that?

As before, I look forward to your advice and guidance.

AWAPRC
[Sony Xperia P, U, Sola, Go] gm007:
Yes it will realize that you have uk firmware and will update according that.

I think ics for uk users are not out yet,so flash any ics firmware from the stickies in general forum.
[Sony Xperia P, U, Sola, Go] awaprc:
OK thanks,

So, if my SI number is on the Sony website http://talk.sonymobile.com/thread/42096 but ICS is not available for the UK, that would make it sound like I would get the Chinese version, which, is less than desirable.

AWAPRC
[AT&T Samsung Galaxy Note I717] liftedzuki:
Everytime I screen off, and go back setcpu says its 1836, enter the app, says 1512 is max.... I set it back and it says 1836 til I screen off.

WTH? Ditch SetCPU? or what.
[AT&T Samsung Galaxy Note I717] Jorge81:
I had to disable my roms oc for it to stick, what are you running?

---------- Post added at 06:24 PM ---------- Previous post was at 06:03 PM ----------

Originally Posted by flappjaxxx

to disable the andrev_oc in my mod just delete /system/etc/init.d/83aroc then reboot. this will fix my mod from overwriting OC/UV settings

This worked for me...hope it works for you.
[AT&T Samsung Galaxy Note I717] liftedzuki:
I checked, I deleted it but it came back..... I might have reflashed after the matter.. Been messin with alot of stuff.

I deleted it again and rebooted, will see if it works.

You diggin the FJ ROM? You using SetCPU as well?
[AT&T Samsung Galaxy Note I717] Jorge81:
Just delete then flash manually....

Love the rom and at 1890 using setcpu, no force closes.
[AT&T Samsung Galaxy Note I717] liftedzuki:
Good to go. I mustve reflashed after.
[AT&T Samsung Galaxy Note I717] Jorge81:
I would recomend trying twrp2 with goo manager, love the features...
[AT&T Samsung Galaxy Note I717] liftedzuki:
Benefits over the CWM touch?
[AT&T Samsung Galaxy Note I717] Jorge81:
On screen keyboard got my attaction, just install with goo manager last night so just breaking it in. Search on youtube for video
[AT&T Samsung Galaxy Note I717] liftedzuki:
You should put your specs in your sig. I see a few people do it, so I did it, kinda nice to when you post people know what ya got :D

Just a suggestion.

I'm new to droids and rooting so I'm learnin.

Will check it out. I just used ODIN, but been reading about goo.
[AT&T Samsung Galaxy Note I717] merlinsrealm:
I had the same issue. I deleted /system/etc/init.d/83aroc then rebooted. Worked perfect!

Eric
[AT&T Samsung Galaxy Note I717] LittleRedDot:
What rom and kernel are you using?
[AT&T Samsung Galaxy Note I717] liftedzuki:
I forgot to reboot after deleting 83aroc. Works goodgood now on FJ rom and hot wire r2 kernel
[AT&T Samsung Galaxy Note I717] JB calhoun:
Im using bigfaus better then stock rooted rom ocd 1.83 heres a antutu

sent from nitro powered.note clockin 1.83 in a quarter mile!!
[Sprint Samsung Galaxy S III] SharpHawk:
I bought the Epic 4G on launch day about two years ago. At the time I was unaware of the huge quality control issues that phones (even highly hyped ones) often encounter. After two years of dealing with that POS, instead of telling you where that phone went wrong, I'm here to tell you what the Galaxy S3 does right:

- Great in-hand feel. Also feels great against my face during phone calls.

- GPS actually works!

- Battery life is great, even with 4G LTE turned on.

- No wakelock problems. The awake time graph matches the screen-on graph perfectly.

- Browsing the Internet is a joy due to the large hires screen.

I've also switched from Sprint to AT&T and couldn't be happier. Even though I've lost unlimited data, I can't help but feel that it was Sprint that was ripping me off with modem-level speeds.

So yeah, thrilled with the phone so far!
[Sprint Samsung Galaxy S III] knyque:
Hmm, I bought the Epic 4G the day after launch, and I loved it. I had CyanogenMod 9 on it, and I had no issues. I hated to give up the keyboard, but I am a techie, and needed the upgrade.

Don't get me wrong, the GS3 is much better, but the Epic 4G was a great phone as well.
[Sprint Samsung Galaxy S III] KappaG9:
The only problem I have with it is that it is kinda hard to use with one hand especially if you have to reach across the screen with your thumb or something
[Sprint Samsung Galaxy S III] SharpHawk:
I think at least some of my issues stemmed from the unit itself, but there are other problems that have been widely confirmed (horrible GPS, poor reception). CM9 is the only reason I was able to hold onto my sanity while using that phone. It was the only ROM that caused my Epic to behave predictably. Many thanks to the CM team, can't wait to see what they can do with this one.
[Sprint Samsung Galaxy S III] sabre31:
Ok phone not stellar wish it had 4.5 inch screen thus screen feels a little to big to use one handed. But happy with phone otherwise.
[Sprint Samsung Galaxy S III] RaymondPJR:
Look into a product called "Flygrip". Makes one-handed phone operation a breeze. Can also double as a kickstand. I intend to get one!
[Sprint Samsung Galaxy S III] ExodusC:
I too love that this phone seems to handle Android properly in the regard that there aren't random wakelocks everywhere.

My old Droid 2 Global, regardless of ROM, and with a virtually identical app configuration would get lots of random wakelocks.
[Sprint Samsung Galaxy S III] FormulaLT1:
I had the original Epic 4G, then purchased the Epic Touch and now switched to Verizon and purchased the GSIII but I loved every phone. I actually at times miss my Epic Touch , mostly due to having a easier platform for modification (verizon sucks for locking the bootloader) but otherwise the GS3 is definitely the best of the 3 so far and I am sure in due time the bootloader will be cracked,
[Sprint Samsung Galaxy S III] Kchitown1977:
Try fly grip qbking has video on you tube
[Motorola Droid X2] Scur827:
Since the last time I flashed CM7, RSD (any version) with any SBF file doesn't wipe my phone the way it used to. It's gotten to the point I can no longer flash custom ROMs. If I don't wipe data/cache first, it will flash a new SBF yet leave the apps that were on it before hand. And when I try to flash a custom ROM, I get an error every time. Did I mess up something down in the locked areas that can never be fixed? Is there another way to wipe the phone to a more original or basic point? Right now I'm completely wiping the int and ext sd-cards, wiping data/cache/dalvik, SBFing to 2.2.2, and OTAing back up to see what happens, though I'm doubting it will help.

edit: Didn't work. Still can't flash a custom ROM. I can run rooted stock 2.3.5 though, guess that's what I'm stuck with. Better than nothing.
[Motorola Droid X2] RyanThaDude:
Performing an SBF does not wipe any user data from the phone. Wipe the phone using the stock recovery before performing the SBF. There are many threads on here on how to SBF, root, and install your favorite ROM.
[Motorola Droid X2] Scur827:
It doesn't matter if I wipe everything or not, I still can't flash a custom ROM. Get an error every time, and have to SBF to get it bootable again. I had weird issues the first time I ran CM7 and tried to SBF back to stock. Took multiple battery pulls and random button pushing while rebooting before I could get it back into RSD mode. This last time let me SBF back fine, but I get the PASS result instead of the REBOOT PHONE MANUALLY now and can't flash anything.
[Motorola Droid X2] Pixelation:
Try this a files sometimes corrupt.

Download all new. Perform the sbf, while the phone reboots do the volume down power button thing to get into Android Recovery. Once there wipe data and cache....

I have about 10 cables in my house...only two or three work for flashing and such...try a different cable....

DROID DOES, Apple did...like I forgot when
[Motorola Droid X2] Scur827:
I have a couple good cables that always work, tried them both. Wiped data and cache on SBF reboot, too. Rooted with One click and Pete's both. So far, nothing works.
[Motorola Droid X2] sd_shadow:
are you sure, sbf is flashing correct?

try different version like 2.2.3 or 2.3.5

and check system info after to verify

then update.zip or flash 2.3.4 sbf

or try ezsbf to flash and/or root
[Motorola Droid X2] sd_shadow:
i've seen usb cables work with one device and not another, can be hard to tell
[Motorola Droid X2] Scur827:
I've tried 2.2.2, 2.3.3, and 2.3.4 all, then updated. I've tried 3 different versions of RSD. Exact same result. Haven't heard of ezsbf though, I'll check it out.
[Motorola Droid X2] sd_shadow:
http://www.droidxforums.com/forum/droid-x2-hacks/41697-tool-ezsbf-dx2.html

it's an iso file you burn to cd or thumb drive, reboots pc to a Linux os

with options to flash sbf and root with zergrush

works for some, when rsd lite or rooting failed
[Motorola Droid X2] LordRalh3:
... Have you thought that maybe the recovery your using is corrupted? Download that apk again (the plain one not the patched cm7/9 version) and give that
[Motorola Droid X2] dragonzkiller:
The reason why you can't flash custom ROMs such as CM7 or CM9 is that you keep going to 2.3.5 or maybe even trying on 2.2.2 or 2.3.3. I have a check to prevent you from using any version besides 2.3.4. Restoring a nandroid won't cut it either. You must SBF back to 2.3.4, wipe data/cache, root (using zergRush or Pete's Root Tools), install the unpatched BSR, and flash CM7 or CM9.

As for why your apps show up still after an SBF, like you said, you didn't wipe data/cache and the apps are stored in the data directory on your phone. An SBF does not wipe data or cache.
[Motorola Droid X2] Scur827:
That's the only thing I haven't tried I think, I'll give it a try. Good idea.

Droid X2 > Eclipse 2.2.1 > Tapatalk
[Motorola Droid X2] Scur827:
I haven't tried to flash CM7 or CM9 since the last time I came off of it. I really like having the camcorder around my daughter. That was my only problem with either. they worked great when they were on. I've mostly been trying to get Eclipse back on.

I think that CM7 had something to do with my problem, though. I've flashed it twice before. The first time was hell coming back to stock, I thought my phone was bricked for about an hour. It took multiple boot attempts, battery pulls, and button mashing before I finally could get back to RSD mode to flash a SBF.

Everything seemed fine for a couple months, until I tried CM7 once again. When I tried to come back off of it the second time, RSD gave it a PASS at the end instead of hanging on REBOOT PHONE MANUALLY like it always did before, and has every time since then (was hit and miss before). Now I can still flash a SBF and update an OTA (but only after doing a *228 to download and install it, can't flash an OTA file from recovery), but if I try to flash any ROM (and I've tried a half dozen of them) while using any root method, I get an error while flashing, and have to wipe everything possible to be able to SBF back to stock. I've tried flashing ROMs at least 20 times over the past few days. Either something got messed up, somewhere in an area that both RSD and recovery don't touch, or it's a hardware issue. That's the only thing I can come up with.

Now, I don't believe it's CM7's fault. At all. There are just too many people who enjoy. I simply believe there was something odd or wrong about my phone.
[Motorola Droid X2] LordRalh3:
Its like you know the words but not which ones go with what things... Flashing and sbfing are two completly different things, and there is no button mashing involved pull your battery one time, hold power and volume up at the same time, that puts you in rsd mode to sbf, to get over a bootloop just go to android recovery (power button and volume down then cycle to recovery) you don't flash roms in this recovery just wipe data/cache. If you grabbed the right sbf file (check your android version in about phone should be 2.3.4 ) you can root with motorola one click and install the bootstrap recovery program NOT THE CM7 VERSION, Plug phone into the wall bsr WIPE DATA/CACHE and flash cm7, its a standard process and your phone is not special
[Motorola Droid X2] Scur827:
Fine, I don't FLASH an SBF file. But I've flashed ROMs on the X2 alone at least a hundred times, I know what's what. I know the difference between stock recovery and BSR. I know the difference between BSR and the CM7 version, and when to switch over. I know what wiping data does, what wiping cache does, what the Dalvek cache is and what wiping it does, what fixing permissions really does.

When I say I couldn't SBF out of CM7, I mean after flashing CM7 the first time, I ran RSD Lite and used SBF 2.3.4-380 to get back to stock. RSD gave me an error, and stopped. I couldn't reboot the phone, it just hung up on the red M. Holding vol down+power hung up on the red M. Holding vol up+power hung up on the red M. So I would pull the battery and try it again. And again. And again. No buttons, every button. Letting it sit on the red M for 30 mins. Eventually I got a weird RSD message at the top (and no, not the vol up+power RSD message), different from the others, and I could SBF again. I still got an error, but could vol down+power into the regular menus, so once I got into the standard RSD mode the next SBF went fine, except I got a pass at the end instead of having RSD hang up on the reboot phone manually message it always got before. And since then I don't get the boot loops after it reboots like it used to, though the pass message is hit and miss. I've SBFed dozens and dozens of times since then, used fresh downloads and different versions of everything, and I've never seen another boot loop afterwards. Something, somewhere, is definitively different. I have a few good cables that have always worked, and I've switched them out. I've wiped and formatted everything possible on the phone several times. It's just not the same as it was before CM7. And after coming off of CM7 the second time, I've gotten a pass at the end of the SBF every single time. Another new thing after a CM7 flash.

Like I said, I don't think it's a CM7 issue, I just think there is something wrong with my phone on a level I can't touch, and it really didn't like CM7. It isn't operator error. Give me any instructions you like for getting me on, say, Molten (since it's 2.3.4-380 and the simplest to flash). I'll follow them to the T, but it won't work. I can't *228 anymore, so I can't download a system update, and I get a file signature error if I try to flash an update from stock recovery. I'm stuck on stock 2.2.2, 2.3.3, 2.3.4, or 2.3.5. I can still root them using any method, except 2.3.5 since it requires carrying root over with OTA Rootkeeper from 2.3.4.
[Motorola Droid X2] LordRalh3:
Sorry if i came off too negatively btw its just that this phone is SOOOOO close to indestructible programming wise... Your next step is to burn ezsbf and head to someone elses computer and try that
[Motorola Droid X2] Scur827:
Me too, just woke up.

I tried ezsbf yesterday on a laptop, no change. Tried a fresh copy of BSR from a different source this morning, no luck there either. I'm completely out of ideas now, there's nothing I haven't tried alternatives to. But I have a fully functional phone rooted on 2.3.4, and sometime in the near future I'll be getting something new and shiny, so it could be worse. When I do get a new one, this one will be perfect to have GrooVe IP on it for my 8 yr. old daughter, and the big screen is nice for games.

Droid X2 > Eclipse 2.2.1 > Tapatalk