yashsingh1/xdaforums huggingface dataset:
[Nexus 10 General] dalingrin:
Unfortunately, Google just doesn't want to target your use case. This latest iteration of the tablet UI shows that they are content with a tablet being a large phone. Since Google is primarily targeting media consumption it is not a big deal to waste a good bit of UI real estate on black bars, etc. Likewise, I don't think you'll see a Transformer-like keyboard dock because that is beyond what Google is targeting with the Nexus 10.

I personally don't agree with Google's approach. I want Android/Nexus 10 to be able to have multiple applications on the screen at once like the Windows 8 tablets and have a keyboard dock like Transformers. If I'm going to pay ~$500 for a tablet then it should be more than a phone with a larger screen.

I disagree here. Plastic != always bad. I prefer a soft coated hard plastic to a metal back any day. That's assuming the plastic isn't cheap flexible junk. The metal on the Transformers doesn't really add any real protection, it scratches way too easily, and its generally heavier. In other words, if the plastic is done well then it can be better than a metal backing.

From what I've seen most people enjoy the Nexus 7's plastic and from early reviews people seem to like the Nexus 10's as well.

I agree here, but again, Google simply isn't targeting your use case. In their eyes, the Nexus 10 is a dumb device that acts as a portal to media and if you do view or edit a document then it will be in the cloud.

From what I've seen the screen looks to be pretty great. I'm not sure why you think it would be that much better than the TF700's which already has one of the best screens available. Compared to the TF101 and most other previous Android tablets the Nexus 10 will look phenomenal.

I'm also not sure why you think the Nexus 10's screen will be such a large battery drain compared to the TF700. In reality, we have no idea which screen will be more power hungry. Yes, the Nexus 10 has more pixels than the TF700 but pushing a few extra pixels is nothing compared to backlight power drain. While one could argue that the Nexus 10 having more pixels than the TF700 will require more computational resources. However, the GPU and CPU in the Nexus 10 should be slightly more efficient than Tegra 3 making it mostly a wash. In terms of the backlights, I have no idea which requires more power and I don't think the reviewers do either.
[Nexus 10 General] Tomatoes8:
Let's get technical. Definition class!

issues

1an important topic or problem for debate or discussion: the issue of racism raising awareness of environmental issues

(issues) personal problems or difficulties: emotions and intimacy issues that were largely dealt with through alcohol I like him, though I have some issues with the guy

(issues) problems or difficulties, especially with a service or facility: a small number of users are experiencing connectivity issues

Does a plastic construction really fall under a problem? No. More like a solution to a lighter and more heat resistant product. It would be an issue if the construction affected durability or how well the product operates but I highly doubt that.

Is the lack of a micro SD card an issue? I might give him that one if I was really feeling generous but it's a tough sell. Maybe in the right context. If I had to transfer 16.5 gb of files to another system and the Nexus 10 was designed for that specific task then that would be an issue because it wasn't designed with enough memory to accomplish that specific task. However, I wouldn't call the lack of a micro SD card slot an issue or a problem because it was designed that way and manufactured to be that way, it is not a defect,

An issue would be closer to a problem or a defect rather than something that was just was not included on purpose.
[Nexus 10 General] Woody:
Before this becomes even more of a flamefest, I am going to close it.

@pierrekid, I am happy that you are staying with your current tablet and wish you all the best. It is too bad that the N10 specs don't fit your ideal tablet thoughts. Good luck in your future and if you do decide to get an N10, you know where we are.

Thread closed.
[Sprint Samsung Galaxy Note II] vwgti18:
Can this be done this is deffo one of the best music player I've used but I need the widget to work!!

http://xdaforums.com/showthread.php?t=1864562
[Sprint Samsung Galaxy Note II] mrnamster:
The JellyBomb ROM has the Walkman player. Not sure if it has the widget though.
[Sprint Samsung Galaxy Note II] vwgti18:
Yea I have Note cards comes with the player but no widget seems no one can get it to work with out that stock Xperia launcher. :(
[Nexus 4 Q&A, Help & Troubleshooting] Jay321:
i have sprint. does this phone have lte and will i be able to put my sprint service on it as well?
[Nexus 4 Q&A, Help & Troubleshooting] raptir:
The phone does not have LTE, and even if it did it would not work with your Sprint service. This is a GSM phone, Sprint uses CDMA. Even Sprint LTE phones still use CDMA for calls/texts/3G.
[Nexus 4 Q&A, Help & Troubleshooting] weaselp1:
http://en.wikipedia.org/wiki/List_of_United_States_wireless_communications_service_providers

-sort by GSM..any GSM carrier will work with the nexus 4....i am assuming you are US based.
[Nexus 4 Q&A, Help & Troubleshooting] eep2378:
dude, really? Come on! PLEASE read/search before cluttering these forums!
[Nexus 4 Q&A, Help & Troubleshooting] efrant:
The N4 is an HSPA device. It is not compatible with Verizon or Sprint.
[Xoom Q&A, Help & Troubleshooting] matkisson:
I have been looking around and can't find any information on this. If there is a radio update required for android 4.1.2 could someone point me in the right direction.
[Sprint Samsung Galaxy Note II] Xpertss:
Anyone know of flashable 5X6 TW non-themed for LJC rom? Rooted and Deodoxed
[Sprint Samsung Galaxy Note II] Xpertss:
?????

10char
[General Questions and Answers] captivatedroid.69:
im on samsung exhilerate ics, stock rom and recovery 3e, trying to root using the universal root. The instrucions say i can root using one of the files that i download using stock recovery 3e, but i keep getting signature error. HELP!
[Nexus 7 Q&A, Help & Troubleshooting] yoyodiaz:
Hello mi name is Rodrigo and I am from Chile.(sorry for my English)

I write because I need help with my Nexus 7, accidentaly I errase de bootloader, and the tablet don't start.

The PC only recognaise in APX mode but only a 2 seconds.

Can any help me to revive de Tablet.

Thanks
[Nexus 7 Q&A, Help & Troubleshooting] Travisdroidx2:
If you erased the bootloader then yes you are bricked sorry for your loss.
[Nexus 7 Q&A, Help & Troubleshooting] yoyodiaz:
Very bad notice

Uhhhhhh. That is so bad, ASUS Service can fix it or my Nexus is only for stand my Glass

Thank again
[Nexus 7 Q&A, Help & Troubleshooting] player911:
I thought there was a fix for this already some where in the forums. I have done this and luckily I was in my return window, so I just returned it.

APX mode is a low level connection with the Tegras. In the past, we've been able to use NVFlash to push files to devices. The N7 doesn't get too messy with APX mode since the bootloader is easily unlocked. I would keep digging in the forums though, I'm pretty sure that after I had returned mine, there were a few other similar cases and solutions.

I'm not sure the outcome of those solutions though. Travis seems to have been around the block a few times (you whore! :)) so there may not be a method yet.

Search Results:

http://xdaforums.com/sitesearch.php?q=Nexus 7 apx

Threads of Interest:

http://xdaforums.com/showthread.php?t=1789135

http://xdaforums.com/showthread.php?t=1882753

http://xdaforums.com/showthread.php?t=1879228

Spoiler Alert:

Doing the reading for you, I've found no answer to the problem. There is definitely some good reading and stuff you can try there to see if you can't revive it. At this point it looks as though ASUS repair needs to get involved as they have been replacing the motherboards in these type cases.
[Nexus 7 Q&A, Help & Troubleshooting] Travisdroidx2:
NVFlash is what you need. Now a few weeks ago that was still not available for the N7. however things move fast on these devices so hopefully it is available now or real soon. Good luck!
[Nexus 7 Q&A, Help & Troubleshooting] adamhlj:
Creo que puedes instalar uno de los "toolkits" que hay por el foro de android development. "Nexus Tool Kit" y sigues las direcciones. O si no entiendes el ingles tanto, instalas el tool kit, y desupes, escoge el numbero 6 "Flash Bootloader" o si queres empezar de nuevo, selecciona el numero 9 para devolver en nexus a factory settings y nuevocito. Espero que esto te ayude.
[Nexus 7 Q&A, Help & Troubleshooting] yoyodiaz:
Lo que pasa es que no reconoce la tablet ya que perdió el bootloader, de hecho lo perdió con un corte de luz mientras flash con Nexus Root Toolkit, ya probé también con Nexus 7 Toolkit ninguno de los dos reconoce la tablet ya que requieren que a lo menos la tablet inicie en bootloader.

Gracias por el consejo
[Nexus 7 Q&A, Help & Troubleshooting] adamhlj:
Wow, que mala suerte!! Tal vez les puedes decir que mientras hacias una actualizacion, se corto la luz y todo se quebro. Lo siento mucho.
[Nexus 7 Q&A, Help & Troubleshooting] adfad666:
I did the same to my Nexus 7, I deleted the bootloader. One of the links above is to my thread about it.

There is no fix available. You must send it to ASUS for repair.

I contacted them and I said "On my tablet was a notification for an update so I plugged it to the computer via USB and let it update overnight. In the morning it was dead."

ASUS collected my tablet and it was fixed in two or three weeks. This was in Europe, maybe it will be longer in Chile.

Good luck!
[Nexus 7 Q&A, Help & Troubleshooting] yoyodiaz:
Do you hear about jtag, is posible to return bootloader with this??

Thanks
[AT&T, Rogers HTC One X, Telstra One XL] Sailor Jerry:
Quick background: I purchased a One X from AT&T a few weeks ago. It came with the 2.20 firmware, so I used the X-Factor Exploit and unlocked the bootloader via HTCDev. From there I flashed TWRP Recovery and then AOKP.

Pretty much everything was fine at that point, except for the fact that once or twice a day I would pull my phone out of my pocket and it would be completely unresponsive. None of the buttons would wake the phone up, plugging it in didn't do anything, and it wouldn't receive calls. I would then have to do a hard reboot (Power + Volume Down) to get anywhere.

I thought maybe it was an AOSP problem, so I flashed a Sense-based ROM (CleanROM 5). I experienced the same issue.

From there, I re-locked the bootloader and ran the latest RUU. That was 4 days ago and I have yet to experience the problem again.

Has anybody else experienced this, and is there any way to prevent it?
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
power + Vol down puts you into the bootloader. What do you do from there to get the phone booted? Have you tried just holding the power button for 5 seconds or so, until the capacitive buttons flash (same as a battery pull)?

GPS on, by any chance?
[AT&T, Rogers HTC One X, Telstra One XL] Sailor Jerry:
I would just select reboot and it would boot normally. Power alone would also work, I believe. I usually just did power and vol down out of habit I guess.

GPS and WiFi were always on.
[AT&T, Rogers HTC One X, Telstra One XL] c5satellite2:
What radio/RIL were you running?

What hboot version?

You are on 2.20, did you flash the correct KERNEL manually and clear dalvik and cache?
[AT&T, Rogers HTC One X, Telstra One XL] Sailor Jerry:
HBoot 1.14. Didn't mess with the radio, so the stock AT&T 2.20 one (0.19as.32.09.11_2_10.105.32.25L).

Yes, I flashed the correct kernel. It did it with both the plain AOKP kernel and rohan's kernel.

Cleared caches several times.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
GPS on when this happens, by any chance?
[AT&T, Rogers HTC One X, Telstra One XL] Sailor Jerry:
I hardly ever disable it, so it was likely on. No idea if it was actually in use any of the times.

I can say one time it happened immediately after a call, one time it was immediately after a SMS notification, and the rest just seemed to be randomly in the middle of the day.
[AT&T, Rogers HTC One X, Telstra One XL] c5satellite2:
Try going straight to CR5 directly from the stock ruu rom and see if it persists. Maybe the aokp Rom borked something along the way and the ruu has restored it now. I have seen issues similar to this that only the ruu will fix.
[AT&T, Rogers HTC One X, Telstra One XL] nighthawk696969:
Have the same issue.Try going to ViperXl and see what happens.My phone constantly reboots and enters sleep of death.I always have the gps disabled.have 1.09 hboot.And currently I am on 1.85 stock at&t.This issue is kikling me
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
I only mention GPS, since my old phone (Desire Z) had an issue where leaving the GPS on, would make the phone shutdown, and only a battery pull would start it (never tried going into hboot). Which sounds similar to what you were seeing. In my case, no ROM, kernel, or radio flashing ever remedied it. And I could isolate the issue to the GPS being on. If the GPS was used, the phone was going to black screen within a couple hours, without fail. But rebooting the phone after using the GPS (and shutting off GPS) prevented it every time. A few other owners of the DZ had the same problem. One guy sent his into HTC, and they told him it was a defect of the GPRS module, and replaced the motherboard, which fixed the problem.

Hopefully, its not a similar hardware issue in your case. But the fact that you have the GPS on all the time, and the black screen hasn't cropped up like clockwork (like it did in my case) seems to point to the fact that it might not be the exact same issue.

These types of issues tend to be really hard to troubleshoot (and pinpoint the cause). In my case, it took me a couple months to realize it was the GPS, since I usually have it off, and don't use it all that often (usually just when travelling). And I also suffered a lot of "placebo effect" type incidents while flashing various ROMs and kernels trying to fix the issue. If the issue doesn't crop up again after running the RUU, I'd consider myself lucky, and leave it well enough alone.
[AT&T, Rogers HTC One X, Telstra One XL] nighthawk696969:
No it is not the same problem redpoint73.This only happens on Custom ROMS.I have tried every combo on the 3 ROMS i flashed.Could it be an int.d problem???My only is this.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
Yeah, I already said its probably not the same problem. But it doesn't hurt to check everything. As I mentioned, its easy to get sucked into thinking you have the cause isolated, when you really do not.
[AT&T, Rogers HTC One X, Telstra One XL] nighthawk696969:
I understand what you're saying but i have checked it,i'm sure..
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
It also doesn't sound like your problem is exactly the same as the OPs. You mention reboots, while OP does not (just BSOD, or shutdown requiring rebooting in hboot).
[AT&T, Rogers HTC One X, Telstra One XL] nighthawk696969:
No my main problem are the Sleeps of Death.There are no BSODs in android :P
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
Some people have been calling this condition BSOD = Black screen of death. Yes, its a little too derivative of things like Windows blue screen, XBox RROD etc. But you get the idea.
[AT&T, Rogers HTC One X, Telstra One XL] Sailor Jerry:
Update: I re-unlocked the bootloader and flashed CM 10.0.0 upon its release. I've yet to encounter this issue, so I'm thinking my stint on CleanROM might have buggered something. I probably forgot to wipe something somewhere along the line. D'oh.

I am, however, having a pretty severe albeit unrelated problem with an app called Voxer. Every time I listen to a message it kills the microphone until I Force Stop the app. I guess I'll pop over to one of the other AOSP ROMs and see if it persists.
[AT&T, Rogers HTC One X, Telstra One XL] area51avenger:
I was having a similar problem on king kang and pacman. I could turn the phone on and off with the power button, but the touch screen was completely unresponsive. Happened randomly, I would have to hold the power button down and watch the lights flash until the phone shut down, and would be fine after a reboot. When I tried installing viperxl, I had the same issue during the aroma installer, I had to try flashing it 7-8 times, because it kept freezing during the install. No issues running it after a successful install. I was using king kang and rohans b5 kernel when it was happening most often
[AT&T, Rogers HTC One X, Telstra One XL] StoleMacuk:
Hello folks, sorry for the dumb questions but this is new for me. I have HTC One X (AT&T) phone, bought in USA. This is my first android phone and I barely know android as a software. I unlocked the phone buying an unlock code from ebay and I am using the phone on another carrier. My question is, how can i manually update my phone (what is the newest update?:o) since AT&T is not a carrier in my country and I cannot update automatically.

At the moment my software information are:

Android version 4.0.3

HTC Sense version 4.0

Software number 1.85.502.3 710RD

Kernel version 3.0.8-01155-gca24d1eroot@ABM030 # SMP PREEMPT (why is there root in the kernel version, my phone has never been rooted?)

Build number 1.85.502.3_R2 CL63811 release-keys

Doing this manual update if possible will the phone be locked to AT&T again, or my phone will remain unlocked?

I'm sorry for my bad english and sorry if there is already a question like this (I watched the noob video and did use the search button:))

Thank you in advance
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
If you ever want to root or flash custom ROMs or other mods, I would advise not installing the latest (2.20) version AT&T firmware. Installing the official 2.20 firmware updates the bootloader, which plugs the holes by which kernels and radios can be flashed from recovery.

If you want root, I would root on 1.85, SuperCID, and unlock bootloader. Then you can install any firmware you want, including stock rooted versions that are more up to date than 2.20.

If you still want to install the 2.20 firmware, you can download the RUU (ROM updated utility) from HTC and run it on a PC, with the phone connected via USB. The phone should remain SIM unlocked after running the RUU. But RUU will wipe your data partition (but not the internal SD).

A lot of this may be over your head, so this may help: http://xdaforums.com/showthread.php?t=1784459
[AT&T, Rogers HTC One X, Telstra One XL] StoleMacuk:
Thank you redpoint73 for your answer, I will follow your advice and will root it on 1.85.

I suppose what I should do first is rooting my phone following this guide: http://xdaforums.com/showthread.php?t=1644167.

Than I should do this: http://xdaforums.com/showthread.php?t=1672284

Please correct me if I am mistaken

After doing all of that which firmware do you suggest or stock rooted version, or its just matter of taste? Now again the same question will I lose my SIM-unlock after rooting mt phone?
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
The root method you linked is actually for 1.73. You want to use this one for 1.85: http://xdaforums.com/showthread.php?t=1709296

The SuperCID method you linked is correct.

ROM/firmware is very much a matter of taste, and what features you are looking for. If you want stock, you can install the stock rooted 2.20 AT&T firmware in the Development forum (after unlocking the bootloader and installing TWRP). If you want something based on stock, but with cool added features and customizations, look at ViperXL, CleanROM, or Nocturnal LE. But that doesn't mean that any of the other ROMs are not also great. And that doesn't even mention the more "vanilla" (no HTC Sense) Android experience you can get from AOSP based ROMs, and their variants.

The differences and benefits of each are simply too extensive to discuss here. Just start looking at the ROMs and see what looks interesting to you.

Take a look at my index to see all the resources in an organized list:

http://xdaforums.com/showthread.php?t=1671237
[AT&T, Rogers HTC One X, Telstra One XL] galitore:
I have a doubt. As I'm no from USA, I'll have no option to update the firmware over the air. How must I proceed in this part of the manual method?

Won't I have any issues with this?

Thank you guys in advance...
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
My advice? Stop now. If, in fact, "This is my first android phone and I barely know android as a software," you're not ready to root.

You need to spend the next week (at least) reading and searching and reading some more. Don't come back until you can answer the following questions:

1. What does "rooting" mean, what exactly does it do to your phone?

2. What are you doing when you unlock the bootloader?

3. What's the difference between stock and custom recovery, and stock and custom ROMs?

Once you feel like you understand all this, you're ready to proceed. If you push forward now, you'll almost certain to get into trouble that you won't be able to get out of without extensive help.
[AT&T, Rogers HTC One X, Telstra One XL] galitore:
Hi iElvis,

actually it wasn`t me who said "This is my first android phone and I barely know android as a software"... it was another member.

I had an Motorola Atrix 4G which I rooted a coupe of times, but this one was made for my country market, differently than my HOX, that is at&t. But in one thing you`re right. I have not much experience with HOX. That`s true...

My question was regarding the part of the manual process which needs a communication between at&t and my cellphone. In this case I wouldn`t find any upgrade option to accept or deny. So i don`t know what would happen in this case... does anyone know?!?!
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
Whoops! Sorry about that.

As far as I know, the only way is to flash a custom rom with the base you want, or to run the RUU for that base, which will leave you relocked and unrooted.
[T-Mobile, Samsung Galaxy SIII] VibrantThemer:
Hello everyone,

I just wonder if anyone encountered such issue that your phone could not read the SIM card a few times a day?

For the last four days, my phone connection dropped a few times a day. And when I ried to check the network in the setting, it says I need to insert the SIM card even with different ROM.

Thanks for reading
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Probably need a new som. Take it to tmobile and theyll test and if needed give you a new one.
[T-Mobile, Samsung Galaxy SIII] VibrantThemer:
Thanks, Doc. You seem to have a lot of answers lol

The crazy thing is that where I live, the signal is very low. Sometime I don't even get one bar signal. Some phone likes LG, couldn't even get any signal at all. I hope you're not going to tell me to sell my house and buy a house near the cell tower. lol

I never had any connection problem with my vibrant for over two years until I got this phone. With this phone, from the cold boot, if the data was on, it's not going to get connected even if the signal is very strong. I have to turn the data off, reboot into recovery, wipe cache, and turn the data on again.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Have you tried flashing any of the other modems? Theres plenty to choose from and a map where people can post what the best modem was in their area per their test results.
[T-Mobile, Samsung Galaxy SIII] VibrantThemer:
Thanks, Doc. I tried all of them already, but no luck.