yashsingh1/xdaforums huggingface dataset:
[Nexus 10 General] SeaFractor:
So all kinds of checks and balances exist to keep from accidental entry of a product and not list the wrong vendor or product number?

I've seen it at a number of different stores and locations, even when they have product in stock and ready to sell.

Cool that your inventory system is that accurate and this far in advance.. Must have special phone line to Google HQS?

---------- Post added at 05:11 PM ---------- Previous post was at 05:03 PM ----------

Because it works 100% on yours, everyone else that has the problem must be a liar!! :p

In all seriousness though, I'm glad it's working for you.

My spouses N7 2013 is having the same problems. I've done a factory wipe, etc, and the touch screen is still poor results. Back to the store for exchange, as the problem looks to be both software and hardware. Hardware isn't an issue for all (just like the screen lift wasn't for all with the N7 first edition) and so it's fixed for most with the software patch.

Glad my N10 has been so solid. But yea, I'm not upgrading at this time.

Still works as it did when I purchased it.
[Nexus 10 General] rcatron:
This guarantees that I will not purchase the next Nexus 10. No Asus tablet for me. The Transformer Prime soured me for life...
[Nexus 10 General] HitBobLer:
Seen any more on this? Seeing as it wasn't announced with the Nexus 5
[Nexus 10 General] SeaFractor:
You'll see two models to replace the 16GB Nexus 10.

1. 64GB Samsung N10.

2. 64GB model with unlocked LTE.

Just like the 32GB and 3G/HSPA+ models of the Nexus 7 had when the 8GB model was discontinued.

My speculation is just that.

But I believe it to be more probable based on Sundar Pichai's tweet earlier this year.
[Nexus 10 General] Patroy:
so, rumors about N10 2013 come alive again:

http://www.gottabemobile.com/2013/11/02/nexus-10-track-holiday-release/
[Nexus 10 General] oldblue910:
I really hope there's an LTE version so I can replace my Xoom. The Xoom is still the only 10" Nexus tablet available with LTE.
[Nexus 10 General] SeaFractor:
Same sources saying (translation, not official quote):

Yeah we were certain beyond all doubt, but now that date has come and egg is on our faces we've come back with an even more certain date!

The Future!!! (Should have said that instead of November :) )

I'll tell you what, I believe ASUS is making a 10" tab and the specs are spot on, but I doubt it's for the Google Play Store.

I suspect if another set of N10's are released, it'll be a small revision bump to the existing hardware with 64GB storage with and without LTE.

I love my N10, but sales of this tab were no where near the number of the N7 first edition.
[Nexus 7 (2013) General] NexusChrist:
So, I just picked up my new Nexus 7, dinked around a bit with it, then wanted to unlock and root it for alternative rom support. I went about doing everything, except when I went to begin the root, which looked like it was going smoothly, I realized that I did not enable USB Debugging.

I am not able to put it back to stock, nor am I able to load anything to it. I can get into FastBoot but thats it.

Any help would be appreciated. I have searched, but I could not find anything on enabling USB debugging remotely from a Mac. I am on Mac OS.
[Nexus 7 (2013) General] di11igaf:
You're fine. Just search how to setup fastboot on a Mac. (Couldn't tell you, though I'm sure its close to you'd do it on Linux, and you'll need to find the Mac fastboot binary and new system.IMG(possibly a whole reflash)), then just do these commands-

fastboot oem unlock (if you've already done this skip this step)

fastboot flash system system.img

(If this doesn't work, find the entire flash all package and do)-

./flash-all.sh

(Will be something like this, you'll have to research yourself.)
[Nexus 7 (2013) General] Dawei87:
Your best bet might be to use fastboot to flash the stock recovery back on the device and then use adb sideload from recovery to flash a stock system image. That would take you completely back to stock and then you could start over.
[Nexus 7 (2013) General] NexusChrist:
Sorry, I should have been more specific. All of the steps listed for the all of the guides require me to eventually put my tablet into USB Debugging mode. I can't do that. I can't boot into the Android system at all. I get the lovely dead robot with read warning symbol.

Is there any way to enable USB Debugging without system access on the tablet? Is this just a paper weight now? I have rooted and such since my original Nook Color, so I am not dunce. I just don't understand how I can do any of the guides if all of them call for me to put the tablet into USB debugging mode.
[Nexus 7 (2013) General] NHLWil:
You only need debugging enabled to use ADB (in recovery or the OS). Fastboot will still work regardless.
[Nexus 7 (2013) General] tweaked:
Ddi11igaf told you wat to do.

Download the full image and reset it to stock. Start again.

You are never bricked if you can get to fastboot.

:good:
[Nexus 7 (2013) General] NexusChrist:
Perhaps this will help:

There is currently, for some reason, no OS installed on the tablet. I do not have any roms or a backups saved on the tablet. I just want to go back to stock and start over.

I can't get into the tablet to enable USB debugging.

Is there a way to get a rom onto the tablet without USB debugging? I realize that Fast Boot works, and so does my recovery, but there is no OS installed, and no way for me to put an OS on it if I don't have USB debugging.
[Nexus 7 (2013) General] NHLWil:
We understand, but you're under the false impression that USB debugging needs to be enabled to use fastboot and flash from there. It doesn't. All you have to do is unlock the bootloader (if you didn't do that already) and flash a stock ROM from https://developers.google.com/android/nexus/images. Download the stock ROM to your Mac and use the fastboot commands someone posted above. If it's not working, it's a driver issue with your Mac.
[Nexus 7 (2013) General] NexusChrist:
And how would one go about putting that image on the unit to flash it?

This is what I get when I try to use the one-click method from AndroidRootz:

***************************************************************

This script will: Unroot The New Nexus 7 to Stock 4.3 & Lock your Bootloader

For more details go to AndroidRootz

***************************************************************

Warning! This will delete everything on your device! BACKUP your device!

First make sure your in FASTBOOT MODE!

Press enter to continue

sending 'bootloader' (3911 KB)... OKAY

writing 'bootloader'... OKAY

rebooting into bootloader... OKAY

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

--------------------------------------------

Bootloader Version...: FLO-03.14

Baseband Version.....: none

Serial Number........: 07974778

--------------------------------------------

checking product... OKAY

checking version-bootloader... OKAY

sending 'boot' (6880 KB)... OKAY

writing 'boot'... OKAY

sending 'recovery' (7424 KB)... OKAY

writing 'recovery'... OKAY

sending 'system' (603495 KB)... ERROR: usb_write failed with status e00002be

FAILED (data transfer failure (No such file or directory))

Your device is now stock and unrooted

However the bootloader is still unlocked

Let your device boot up, set up your device or skip the set-up

Place your phone in USB debugging mode

Settings > Developer Options > USB Debugging, If you don't have that option

Use this guide:

Connect USB cable if your disconnected

Press enter to relock the bootloader

If I hit enter after that it simply says device not found. Again, it's asking me to put it into USB debugging, but I can't because it failed to put the OS on the device.
[Nexus 7 (2013) General] NHLWil:
Looks like it was working fine, until it went to write the OS (system). Perhaps the system.img is missing or corrupt. Try downloading it direct from the link I posted above and flashing with that.
[Nexus 7 (2013) General] NexusChrist:
Thanks, I have it downloaded. And installed ADB and FastBoot on my Mac.

Do you have the specific steps on how to flash a rom from my computer via fastboot?
[Nexus 7 (2013) General] NHLWil:
You should just be able to:

fastboot flash system system.img

If it's not working, then you'll probably need the fastboot executable from the official Android SDK for Mac, as I know someone from work had an issue flashing with one they got from elsewhere.
[Nexus 7 (2013) General] NexusChrist:
I was able to download it, and it sees my device, and I can perform most of the operations, however; As soon as I try to do a flash all this is what I get:

"OTT1-COMM-CK-MBP15-2400:android xxxxxx$ ./fastboot flashall flash-all.sh

error: neither -p product specified nor ANDROID_PRODUCT_OUT set"
[Nexus 7 (2013) General] NexusChrist:
So here is what I did, and all went well again until the System part: Run fastboot erase boot

fastboot erase cache

fastboot erase recovery

fastboot erase system

fastboot erase userdata

fastboot flash bootloader bootloader-flo-flo-03.14.img

fastboot reboot-bootloader

fastboot -w update image-razor-jss15q.zip

And this was the output:

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

--------------------------------------------

Bootloader Version...: FLO-03.14

Baseband Version.....: none

Serial Number........: 07974778

--------------------------------------------

checking product... OKAY

checking version-bootloader... OKAY

sending 'boot' (6880 KB)... OKAY

writing 'boot'... OKAY

sending 'recovery' (7424 KB)... OKAY

writing 'recovery'... OKAY

sending 'system' (603355 KB)... ERROR: usb_write failed with status e00002be

FAILED (data transfer failure (No such file or directory))
[Nexus 7 (2013) General] NexusChrist:
I just did the same steps on my wife's PC and it worked perfectly.

Maybe something weird with the PC, I'm not sure. But all is well.

Thanks for the help!
[Nexus 7 (2013) General] sfhub:
Boot into recovery using Power+VolDown

Then redo your above steps, but skip the erase lines at the beginning.

See if that helps.
[Nexus 7 (2013) General] di11igaf:
Pretty sure this error was your fastboot binary. You need the one from the SDK for a mac(I guess possibly a problem with your USB port, doubt it though since fastboot was talking to your device)
[Sprint Samsung Galaxy Note II] chris111690:
I have a note 2 (sprint bad esn) that I cannot get flashed to page plus.

I have had this phone on Verizon prepaid until it crapped out.

I then put it on boot mobile but could not get it to work

I then am now trying to get it on Page plus.

I have tried Wireless Workshop, manually doing it with CDMA and DFS, and have taken it to 2 different companies in my town to have it flahed. They cannot findout anything that is wrong with the phone and still cannot get it to properly flahsed.

So my options are Is there a way to get this thing flashed back to sprint. (stock data, mms, and voice) settings and re flash it to page plus or can i just take it back to a sprint store and they can do it for me?

thanks!

Chris
[Sprint Samsung Galaxy Note II] juggamonkey:
What's exactly wrong with it ? I've got mine flashed to Verizon prepaid but its basically the same as pageplus far as flashing
[Sprint Samsung Galaxy Note II] chris111690:
Thanks for the reply.

The company that flashed it was remotewirelesstech.com

They flashed it then about 2 months later it crapped out on me. I lost data then i lost voice/text a couple of weeks later.

I contacted them and they said that they will not reflash bc alot of ppl have hadthis happen to them in the past.

So I tried to flash to Boost. Got everything to work, then I got no data or voice.

I then tried to use wireless workshop to go to Pageplus but nothing would work.

Someone told me that Pageplus will not allow rooted phones, so I unrooted and went back to a stock rom 4.1.2.

I reflashed with wireless workshop and now when I try to call it askes to add money to the account.

But nothing works. I still have 2 dollars on my PP account.

I then took it to 2 different flashing companies around my area and they could not figure it out. (II think they both done just automated one click methods) but Ive even tried to get it to work with CDMA workshop and DFS to no avail.

If someone is up to it, I can donate paypal to get this thing flashed remotly. Im so desperate.

I paid almost 500 for this phone last march and now If I sell it, It will only get 300 out of it. But I love my Note II, and was thinkgin about buying the verizon model if I sell this one.

Any suggestions??:eek:
[Sprint Samsung Galaxy Note II] bogie03:
i can help

i can do a remote flash.... those 1 click methods dont work to well....i use dfs

pm me and we can set up something
[G2 Q&A, Help & Troubleshooting] shadehh:
Are they still that bad or have they improved? I would really love to get this phone, i really find the design amazing and the current software it seems to have on it wonderful. The battery life i've seen posts of seem to be great as well. The only thing stopping me is my concern for updates.
[G2 Q&A, Help & Troubleshooting] Intub8:
The last LG phone I owned was the thrill 3d phone. It was awful and I swore I would never get another. LG really stepped up their game and with this phone being across 4 major carriers I think they will try to stay on top of updates for a few months. Have no fear, the carriers will slow them down even more.
[G2 Q&A, Help & Troubleshooting] Geekybiker:
Since the international and US GSM version are supposedly the same hardware wise, maybe that means we'll just be able to flash international roms? Dodge the whole carrier bit.
[G2 Q&A, Help & Troubleshooting] Semantics:
Samsung and HTC were notorious for bad update policies. If you can't run with the dogs, stay on the porch. I have a feeling that LG will be fine in this area now.
[G2 Q&A, Help & Troubleshooting] WhiteZero:
I asked a similar question recently.
[G2 Q&A, Help & Troubleshooting] EniGmA1987:
Developer support for ROMs and kernels are way better than official updates from a manufacturer. After a week we already have root, a custom ROM, and a way to flash kernels once a kernel dev comes around. I would say this phone will most likely have plenty of dev support because not many phones have so much activity and success just within the first week.
[G2 Q&A, Help & Troubleshooting] deeznuts:
Exactly. Soonest possible update IMO from LG wouldn't even go into effect for another 6-8 months from now due to each carrier having their own way with releasing the updates. That's IF LG tried putting an update out 2 months from now, add another 6 months to that via carriers before release. Within 6 months i'm sure the dev community will be flying and already 5 steps ahead of LG's update, if any ;). Only thing Devs CAN'T do is update the firmware or OS to say 4.3, etc without LG officially doing this.
[Transformer TF300T Q&A, Help & Troubleshooting] arvo.bowen:
How can I tell if my bootloader is UNLOCKED? With older versions of the bootloader (at least I think) it was a white screen with all the text/data on it at the top telling you useful information. Now with the 10.6.1.27.5 update all I can see is the black screen with 3 icons in the middle. (RCK, Android, and Wipe Data).
[Transformer TF300T Q&A, Help & Troubleshooting] Lord Yurij:
It says so in the upper corner of the screen when Asus logo is displayed while starting the tablet

Swyped from my Nexus 4 using Tapatalk 4
[Transformer TF300T Q&A, Help & Troubleshooting] arvo.bowen:
I have "no certificate to inject" on the initial screen (not going into the bootloader mode). So I'm guessing that means it's locked. Best tutorial to unlock it?
[Transformer TF300T Q&A, Help & Troubleshooting] Lord Yurij:
I mean it says "the device is unlocked" of it's unlocked

Swyped from my Nexus 4 using Tapatalk 4
[Transformer TF300T Q&A, Help & Troubleshooting] fred99u:
unlocking is easy

1.just go to asus.com on your PC (search for your tablet) and download the bootloader unlock apk (JB or ICS, get the right one)

2.connect your tablet to your pc via USB and put the bootloader unlock apk somewhere in your tablet

3. unplug USB

4.install the bootloader unlock apk on your tablet

5.go to your list of apps and run the bootloader unlock tool (i think it's called "unlock tool" in your list of apps)

then just follow the onscreen instructions

but if you are having trouble unlocking it i wouldn't do it

i bricked my tablet and i unlocked it easily, ran NVflash fine, and put on TWRP on easily as well, but screwed things up changing the rom

during the whole process unlocking was the easiest
[Transformer TF300T Q&A, Help & Troubleshooting] arvo.bowen:
Got you! Thanks

I just hopped over to the Asus website and grabbed the "Unlock Device App: Unlock boot loader." utility.

located here
[Galaxy S I9000 Q&A, Help & Troubleshooting] am2013:
Hi all,

I'm using Cm10.2 nightly and my battery lasts for some 12-16 hours only. Using the same setup with CM9.1 the battery will last for some 3 days!

I checked the stats with wakelock detector and could identify what seems to be responsible for the drain.

It i caused by the Phone app. I have a VOIP account setup with following settings:

- receive incoming calls

- transporttype: UDP

- send keep-alive: always

Looking at the stats, the drain is caused by 'SipWakeLock'. I have noticed that when disabling WIFI-Optimization, the amount of SipWakeLocks was reduced a bit. SIP is running over WIFI.

Anyway, using the same configuration in ICS the amount of SipWakeLocks is much lower. Just to give you an impression of the stats:

CM10.2

Statistics for 4h

2h10m are used by Phone

SipWakeLock count is 1200 and 2h10m time.

Device is awake 95%

CM9.1

4h statistics

Sipwakelock count is 230!! only and 13s of time.

Device is awake 16%

So can anyone advise what can be done? I woul like to contact the devs, but don't have enough posts yet. Can/has this issue to be fixed in the code?

Thank you and best regards,

am
[Galaxy S I9000 Q&A, Help & Troubleshooting] freakymod2120:
Hi,

i will link it for you in the dev forum ...:good:

As needful information: What nightly of CM10.2 do you use acutally???

---------- Post added at 01:53 PM ---------- Previous post was at 01:52 PM ----------

Here you are:

http://xdaforums.com/showthread.php?p=45734132#post45734132
[Galaxy S I9000 Q&A, Help & Troubleshooting] pawitp:
I don't use SIP and don't really have any knowledge on it. I recommend you to post the bug on jira.cyanogenmod.org after a "M" build is released. The bug is more likely to get fixed that way.

It'll also be useful if you try CM10 and CM10.1 to see which version the bug really got introduced.
[Galaxy S I9000 Q&A, Help & Troubleshooting] am2013:
[MENTION=5326164]freakymod2120[/MENTION]: Thanx a lot for linking. I'm using always the current nightly. Sometimes I'm two days behind the current but I'm updating nearly every day.

[MENTION=3117667]pawitp[/MENTION]: Thanx for your info. I will do a downgrade and will do some testing with all stable releases after CM9.1. Will also try 10.1.3 RC2. I think that the battary drain started with some of the first CM10.2 nightlies. Will do some investigation and will provide the feedback.

Thanx again and best regards,

am2013
[Galaxy S I9000 Q&A, Help & Troubleshooting] freakymod2120:
[MENTION=3117667]pawitp[/MENTION]: Many many Thanks for looking in this thread !!!

---------- Post added at 06:21 PM ---------- Previous post was at 06:16 PM ----------

No prob therefore we are here in an community ...:good::highfive: Everyone begun with posts < 10 so it is no problem for me to help ...

And pawitp the dev of CM10.2 for our device ,is very committed like you have seen because of answering ...somebody else wouldn`t look here in it ,but pawitp does ...:good:

Okay test it and let us no with which nightly it begins ....
[Galaxy S I9000 Q&A, Help & Troubleshooting] am2013:
I did some testing. It looks like the issue was introduced before CM 10.2 already. I used CM 10.0.0 before so wasn't aware of the battery drain. I did upgrade to CM10.2 directly so wasnt' aware of the issue in previous versions.

I have uploaded some screenshots of the battery stats. Basically the battery drain was not present in CM 9.1 and CM 10.0.0. The issue with the SipWakeLock was introduced in CM 10.1.0.

Here are some screenshots for comparison:

http://imageshack.us/photo/my-images/826/56hq.png/ CM 10.0.0

http://imageshack.us/photo/my-images/163/4rzk.png/ CM 10.1.0

http://imageshack.us/photo/my-images/13/vppc.png/ CM 10.1.1

http://imageshack.us/photo/my-images/27/0ahp.png/ CM 10.1.2

http://imageshack.us/photo/my-images/27/0ahp.png/ CM 10.1.3

I hope that you can find out what was changed in the Phone.apk from CM 10.0.0 to CM 10.1.0. I'm using identical settings but as you see there is a lot of CPU consumed by the SipWakeLock. If you need any further info just tell me how to help. CM 10.2 has the same issue and I'm using it currently. It does not have any apparent bugs for me. With the battery drain solved it would be the perfect ROM.

Best regards,

am2013
[Galaxy S I9000 Q&A, Help & Troubleshooting] pawitp:
Like I've mentioned before, please submit the bug on jira when an M build is released so other developers can look at it.

If you know anyone else who use SIP, knowing if it happens on other devices or not will also be very useful.
[Galaxy S I9000 Q&A, Help & Troubleshooting] freakymod2120:
We have to wait until an M-Release of CM 10.2 is coming out, then we report it on Jira ,so that all developers have the aviblity to look at here ...
[Galaxy S I9000 Q&A, Help & Troubleshooting] am2013:
Battary drain caused by SipWakeLock fixed

Hi all,

I just want to inform you, that the battery drain, that I have described before has been fixed in some recent release. I think, that it was fixed some two or three weeks ago. So the issue is not existent anymore. My phone is running up to 3 days now without having to charge it.

Best regards,

am2013
[Nexus 4 Q&A, Help & Troubleshooting] BravoMotorola:
This has been an issue for me in 4.3 or any 4.3 ROM with the AOSP messaging app. I'm getting extremely tired of it freezing up my whole phone for 10 seconds at a time. Is there seriously no way to fix this awful issue?
[Nexus 4 Q&A, Help & Troubleshooting] VoiD_Dweller:
My recent cm 10.2 builds are doing this since last week.. Hopefully its something they are aware of .. getting annoying. At first I thought it was my Swype but it happens on other keyboards as well..
[Nexus 4 Q&A, Help & Troubleshooting] cenwesi:
Thank God i am not the only one that experience this. I have had that freeze three times already. Twice last week and once yesterday. This morning my phone rebooted by itself for the first time since running any CM10.X. I hope this is a bug that will be crushed in the next few builds.
[Nexus 4 Q&A, Help & Troubleshooting] BravoMotorola:
I've had it for so long, I'm not sure if anyones on it to fix the problem or not. I'm actually thinking its a general 4.3 bug not just a CM10.2 bug.
[Nexus 4 Q&A, Help & Troubleshooting] seriousneo:
You are right. It's a deadlock on all JSS builds used in cm 10.2
[Nexus 4 Q&A, Help & Troubleshooting] BravoMotorola:
So do you why this happens? Should it really be that hard of a fix?
[Nexus 4 Q&A, Help & Troubleshooting] abaaaabbbb63:
The problem is in the AOSP source. The fix has to come from Google. We won't see it soon, as Google is working on 4.4 now.

Until then, try JWR/JSS hybrids. They don't have deadlocks.
[Android Q&A, Help & Troubleshooting] Gilboss:
in the previous android versions, from the dialpad, you could:

Edit contact

Send SMS

Trigger any contact account (GMail, Whatsapp, Tango, Facebook, Address etc..)

i mean that popup window:

i.stack.imgur.com/aTGat.jpg

Where is it in the Android 4.3 dialpad?
[Android Q&A, Help & Troubleshooting] willyg00:
Same case

Same cuastion, it was really great con my Cianogenmod 10.1 the autocomplete dial, 'couse I was able to send SMS or view details from the contact or view all contact list matching the search.... but with 10.3 I cant do it. Any suggestion?