yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] rirawin:
Thanks, says cannot open volume for direct access
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] da.trute:
first try this again, make sure you open the command prompt as an administrator and try:

chkdsk /X /F /Z (Z is your drive letter)

You may also find some more help here:

http://xdaforums.com/showthread.php?t=367912&page=6

you can also test disk to get back any lost data before you try repair the card again.

http://www.cgsecurity.org/wiki/TestDisk

and then try reapir with this:

https://www.sdcard.org/downloads/formatter_3/
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] rirawin:
The SD card doesn't appear on my PC though, its simply not there.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] da.trute:
It wont appear until its repaired, how are you inserting it into your PC?, do you use a micro SD to standard SD converter and then put that card in a external USB reader or is your SD reader built into your PC.

I ask as even with the slots empty some readers will still show drive letters so you should be able to work out which drive letter your micro Sd will be in, lets say its drive "E".

from the command promprt type CHKDSK /X /F E - this should repair their card enough for you to get it online and then format it. If there is data on you want then do a quick format and then try to copy the data off. If no data appears on the card once fixed then you can try TESTDISK software, this is really good at dragging data of cards once they have been formatted.:
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] rirawin:
I use a micro sd to sd card inserted in my sd reader in my PC.

CHKDSK /X /F m: cannot read the volume.

I insert it but nothing shows or displays, if I use another micro sd its m: drive.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] HUYI:
What brand Is It and Where did you buy It From?, that ls the sure way to find out If It's a Fake or not.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] da.trute:
This isnt sounding good, have you tried some of the options in the thread I pointed you to, like SD formatted software and TESTDISK, TEST DISK can often repair SD card issues.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] Bulbous:
On your PC, have you tried right clicking "Computer" and then selecting "Manage"

Go to Disk Management

There should be something there for the physical device even if it doesn't have a drive letter.

Let us know what you find
[Android Software/Hacking General [Developers Only]] tojimori:
hi

i have a difficult problem with my chinese m98 google 4gs+ phone.

i have flashing the wrong rom on the phone with the SP-Flashtool.

The phone shows only this like the picture.

it is possible to flash the phone with the SP-Flashtool, but i have no rom for this.

i have the rom for flashing from SD-card. Can i modify this rom for the SP-Flashtool? Or it is possible to flashing clockworkmode on this phone and then can i flashing from the sd-card.

Many many thanks :)
[Galaxy Note 10.1 General] jjflemin:
http://www.engadget.com/2013/01/03/samsung-galaxy-note-10-1-verizon-lte-fcc/

Thought some of you might find this interesting! There was a similar one last month, but this LTE Note 10.1 has bands that will work in the US!
[Nexus 4 Q&A, Help & Troubleshooting] zdenoh1975:
Please permanently I have WIFI issue in deeps sleep. Wifi dont work - dont work any gtalk, gmail notification, or too late.. At the moment I turn on display - comes all notification - in the same second when display turn on, all nottification beeps!

When is display on, or is connected charger (-deep sleep is off), all about wifi is perfect and push servis is ok. But when goes to deep sleep, all is back. I trayd many roms, but still the same. Please, know someone any solution? Thank you very much!

Off course wifi deep slep setting is "allways" and router is ok..
[General Questions and Answers] Ron312123:
i deleted my ONE X OS by accident!

oh damn! i tryed to install some rom from my recovery (team win recovery project 2.3.1.0)

and i did wipe> wipe catch and then i want to do factory reset and i hit system.. and i didnt notice..

and the zip of the rom refuse to install! and i dont know what to do! please help me :(

i cant put another rom on my SD card.. im doomed!

and i got ONE X not XL
[General Questions and Answers] lowandbehold:
Use adb to push a rom or an RUU to the internal SD card..
[General Questions and Answers] romulofelix:
I've deleted my OS and I can't even turn tablet on anymore!

Hello everyone! PLEASE, I need someone's help!

I have a Sanei N10 dual core. Its original OS version was 4.0.4 and I was trying to install Jelly bean into it. I had tried many ways, and the last one was using LiveSuit. I did all procedures taught in the forum. My device was connected to PC in ADB mode, and with Livesuit Open, I got a formating box from windows (the same you get when you select "format" on a storage device), so I chose format and after that, nothing else succeeded. So I disconnected the device from USB and I had to reset it. And the worse part, it didn't even turn on anymore.

I'm kinda noob in this issue, but I think when I chose format, I've formatted the partition which had the OS.

Now the Tablet doesn't give any life sign... No led, no message error, no anything "/

PLEASE, I need my Tablet back!

Thank you SO MUCH for any help ;)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] jls95:
Hey guys.I really like the concept of instagram and fb when it comes to photos.Its like a photo journal of your life.I would like to ask if there is an app for offline use.I tried sony million moments but I m not quite happy with it.
[Android Q&A, Help & Troubleshooting] cheqolada:
Hello again :)

In Holiday I compile new kernel with oc for my Device. Before flash new kernel touch work great. After Flash Touch work not satisfactory ... My Question is - How I can change Touch Sensitibity? I Located File with 'touch drivers' but i don't have Idea what i can do? :silly:

Greets.
[Android Q&A, Help & Troubleshooting] cheqolada:
refresh:(
[Android Q&A, Help & Troubleshooting] _Zoom:
Are you talking about multi-touch>?

There is a kernel patch for it if that is it....

located in

drivers/input/touchscreen/atmel.c

this is mainly the patch

+ // credit to agrabren for this

+ if (!ts->finger_count)

+ {

+ // Force re-calibrate whenever we run out of fingers

+ atmel_unlock_store(NULL, NULL, "2\n" , 1);

+ }

This was created by Agrabren..........

Looks like only used for gsm evo 3d and cdma as well...But may work for your kernel as well......Need to find the patch tho

ahhh....here is the commit

https://github.com/TeamJB/android_kernel_htc_msm8660/commit/1b0b841d4d93ec9d4b4467ea8eafae729d820f03

im not positive ifthis is your issue but its worth giving it a shot...

}
[Android Q&A, Help & Troubleshooting] cheqolada:
Ok I Try your kode :)
[Galaxy S III Q&A, Help & Troubleshooting] mlapaglia:
Had to contact emergency response yesterday. When asked afterwards what time I called 911, my recent contacts list had nothing listed about the emergency call. Is this a possible bug? Seems like something you'd want to have on record.

I'm running cyanogenmod 10 stable.
[Galaxy S III Q&A, Help & Troubleshooting] Meraklis56:
on stock rom,the calls on 911 are being logged.
[Samsung Galaxy Nexus] simms22:
As we all know(or should know if you read around the forums) that there is an issue with "sod". Now these sods are not the same as the sod i was familiar with before 4.2. Before 4.2, the device(s) were for all intensive purposes not alive. Sure you could connect to adb, but the device was "dead" until you pulled the battery and rebooted. But with these 4.2 "sods", the device is alive, with the exception of the screen not being able to turn on. Phone calls and messages still come in. notification sounds still play, and you can use the volume buttons to raise/lower the volume. But you still have to pull the battery and reboot for the screen to come back on. Running logcats via adb doesnt seem to show anything related. Well, ive found a way to reproduce these 4.2.X "sods" while the device is awake with the screen on. I can reproduce it at will, and have had other users confirm this. What i do is this.. I go into the main settings, display, then brightness. Turn off automatic brightness if its on. Now adjust the brightness, up, then down, then up(back and forth, but take your finger off the slider when you go up then down). now press ok to set the brightness. Go back into the brightness setting and repeat. Eventually(sometimes seconds, sometimes minutes) the screen goes completely black, like its off, but the device is completely awake. same as these 4.2 sods, phone calls and messages come in, notifications sound, etc. Only difference is the device screen is on when it goes black instead of it being off. The symptoms are the same. This behavior leads me to believe that it most likely isnt a kernel issue like many believe. I believe that its related to some coding that controls the screen. As we know, every rom/kernel has shown this behavior, even stock and unrooted(some more, some less). Personally, i had 3 of these sods last month(trinity kernel/rasbean rom), but i know that some users have them many times a day unfortunately. What could it mean that i can replicate this behavior on an awake device? Any more thoughts about this?
[Samsung Galaxy Nexus] simms22:
maybe someone using another kernel/rom can try to reproduce this?
[Samsung Galaxy Nexus] peikojose:
I haven't tried your method yet. I'll and post my results here. I was able to replicate it using another program (check the links below)

But reading your post, I'm sure now that SOD has to do with autobrightness or brightness control (knowing that, maybe it is easy to solve?)

Check my posts:

http://xdaforums.com/showthread.php?p=35205418#post35205418

http://xdaforums.com/showthread.php?p=35496824#post35496824
[Samsung Galaxy Nexus] pietropizzi:
Check my post here:

[URL="http://xdaforums.com/showpost.php?p=35899150&postcount=26638"]http://xdaforums.com/showpost.php?p=35899150&postcount=26638[/URL]

whre I answered to that phenomen. I was on RBJ + franco r348 that time

I can't reproduce (force) it now with RBJ + franco r360, I tried about 100 times.

Just wanted to post my results, maybe it's too early to tell as r360 is too young.
[Samsung Galaxy Nexus] Ashtrix:
Why does this not happen on N4, N7 and N10 :confused:

+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
[Samsung Galaxy Nexus] OtavioMalzone:
Maybe because OMAP is abandoned at 3.0.
[Samsung Galaxy Nexus] simms22:
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
[Samsung Galaxy Nexus] BinaryXeroMedia:
Sometimes I have my screen say go off but I will click the lock button The screen don't come on but it is still responding. Meaning I can still unlock the device as vibration tells me if I click the ring or not. So this is all down to the SOD? WoW. Learn something new everyday. I am on Xenon-HD 11-12-12 but also had it on stock too. With me though to fix this it just required to to press the power button a few time then the screen returned. Honestly I don't find it annoying at all UNLESS I need to say make a call to my local emergency services. (999 in UK). That is the only time. My nexus S does the same too with the screen but only after I had the NAND chip replaced by Samsung. Hope you guys can find something and my bit of info helps a little.

Regards

Jessie-James
[Samsung Galaxy Nexus] simms22:
if your device wakes, even after a few presses, its not sod.
[Samsung Galaxy Nexus] Ashtrix:
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
[Samsung Galaxy Nexus] simms22:
pressing and holding the power button for 10-20 seconds will force reboot those devices.
[Samsung Galaxy Nexus] MondoMor:
A battery pull isn't necessary; you can shut down the phone with a little practice (depending on your lockscreen).

1. Press the power button (or wait) to lock the phone

2. Press the power button again and unlock

3. [optional] Press the home button (center of screen near bottom edge)

4. Press and hold the power button until a short vibration is felt.

5. Touch the Power Off button (center of the screen just below a horizontal line from the midpoint of the volume rocker). This puts you in the Power Off confirmation dialog.

6. Touch the screen in the approximate location of the "OK" button. I start at the middle on the right side and work my way down. Soon I get the long vibration telling me the phone has powered off. This is the hardest to master since feedback isn't immediate; the long vibration happens several seconds after I successfully hit the OK button.

7. If nothing happens, press the power button to re-lock and start again.

8. Practice when the phone is functioning normally, and you'll be prepared for your next SOD.

My observations (bone stock GSM phone):

This happened once in a pitch-black room. The screen does not go perfectly dark, but it is extremely dim and uniformly grey. I could not make out any details, so the contrast is completely gone.

SOD happens all the time playing Ingress, or other apps where the screen is active for a long time. It seems to happen most often when the display partly dims before going to sleep. My phone is set to sleep at 30 seconds, and the "pre-dim" happens at about 25 seconds. That's usually where I get my SODs.

SOD happens to me less often with auto-brightness set to OFF. It's extremely rare in normal use (but happened just now as I replied to a text!)
[Samsung Galaxy Nexus] simms22:
wouldnt it be easier to just pull the battery? thank you for your observations btw.
[Samsung Galaxy Nexus] e34v8:
simms22, I actually think it is a kernel issue. I only experience SOD problems when i use a custom kernel. Also yesterday I flashed stock 4.2.1 and tried for 10 min to replicate SOD using your method - I could not. Today I tried again - nothing.
[Samsung Galaxy Nexus] MondoMor:
My phone is in an Incipio case, and it's more of a pain to separate the case, especially if I'm in my car or out hiking or whatever. I've gotten pretty good at doing it blind. Also, years of running Windows have made me anal about doing orderly shutdowns. :laugh:

Forgot to add earlier: I was unable to replicate with the technique described in the OP. But as long as someone can get this to happen on demand, it ought to be solvable.

Edit: although I got the SOD in normal usage a few minutes after trying the technique in the OP. Maybe the display SODs on some specific number of brightness changes? That would explain it happening more often with autobrightness, also.
[Samsung Galaxy Nexus] OtavioMalzone:
Just hold down the power button for several seconds. Continue to hold down the power button until the screen blinks off and the boot logo appears.

We are flooding here.. lets discusse this other place and leave the devs alone here :)
[Samsung Galaxy Nexus] andQlimax:
i dont know how replicate this 4.2 SOD, but there is a simple way to avoid it, put all animations inside developers option to 1.0

it doesnt happen anymore to me, stock rom and kernel (i have automatic brightess on if this can matter)

if i put all animations to off or to 0.5, when the screen time out and became black, sometimes it doesnt wake anymore..4.2 sod
[Samsung Galaxy Nexus] biscuitownz:
When I was running the first few nightlies of CM10.1 it still did the "sod" on me. By default the animation settings are at 1.0. Not sure if it's different on stock.
[Samsung Galaxy Nexus] spacemanr:
I've had several sod's daily for last few day's and today finally flashed RBJ from the beginning plus dax's modified kernel and now i'm in watching phase. So far so good.
[Samsung Galaxy Nexus] peikojose:
I have time without any sod... Maybe because I'm trying not to use auto brightness or because of the lastest versions of Francos kernel... Stock ROM
[General Questions and Answers] jippybeale:
I have developed an app which uses SoundPool to play sounds when various areas of the screen are touched. I've also now added a "Record" button so whatever sounds the user plays can be recorded to an audio file. However, I can't find anywhere that explains how to capture the sounds being played via SoundPool. Can anyone help please? Otherwise is the only way to do it using the device mic?
[Samsung Galaxy SL i9003] hider7:
Plz.. I'm using cm10 and I want to send message to a number without I write any thing .. for etisalat .. but I can't ..

Any heeeelp ..
[Samsung Galaxy SL i9003] hider7:
Its so important .. plz solution ..
[Samsung Galaxy SL i9003] hider7:
Ok.. solved .. thanks ..
[Kindle Fire Q&A, Help & Troubleshooting] soukron:
Hi all.

I have seen this in another kind of devices but haven't found thread related about Kindle Fire (1st gen).

A little introduction:

- My kindle was in CM10 and I noticed it started to be detected as Unknown Device in Windows, so

- I used TWRP to flash 6.3.1 stock ROM BUT forgot to wipe before flashing and rebooting. In that moment my situation was an endless loop wih the Kindle being rebooted after 15 seconds aproximately.

- I modified a cable to make it "factory cable" but even in fastboot (plain kindle fire logo) the Unknown Device was there.

- After many tries I managed to make a Reset to factory defaults in Android in the 15 seconds

- Currently the kindle is in stock ROM but still is not correctly detected.

Of course, I have re-installed the drivers in my computer and even tried in a fresh windows installation with no previous drivers without luck. Also, booted an Ubuntu USB with SoupKit and no lsusb changes after plugin the device (just a few dmesg messages about being unable to enumerate USB device on port).

So, if some of you have any idea to try, please tell me. I have the factory cable and the back cover of the kindle removed... ready for anything!

Thank you for your time!
[Kindle Fire Q&A, Help & Troubleshooting] soukron:
This is the part I mentioned before about dmesg messages:

[ 234.956030] usb 2-5: >new full-speed USB device number 4 using ohci_hcd
[ 235.136035] usb 2-5: >device descriptor read/64, error -62
[ 235.420038] usb 2-5: >device descriptor read/64, error -62
[ 235.700026] usb 2-5: >new full-speed USB device number 5 using ohci_hcd
[ 235.880055] usb 2-5: >device descriptor read/64, error -62
[ 236.164040] usb 2-5: >device descriptor read/64, error -62
[ 236.444025] usb 2-5: >new full-speed USB device number 6 using ohci_hcd
[ 236.852030] usb 2-5: >device not accepting address 6, error -62
[ 237.028025] usb 2-5: >new full-speed USB device number 7 using ohci_hcd
[ 237.436025] usb 2-5: >device not accepting address 7, error -62
[ 237.436037] hub 2-0:1.0: >unable to enumerate USB device on port 5

And there's no reference in lsusb:

ubuntu@ubuntu:~$ lsusb
Bus 001 Device 004: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB Flash Drive
Bus 001 Device 005: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 002 Device 002: ID 04ca:0022 Lite-On Technology Corp.
Bus 002 Device 003: ID 046d:0a0b Logitech, Inc. ClearChat Pro USB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
ubuntu@ubuntu:~$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/10p, 12M
|__ Port 3: Dev 2, If 0, Class=HID, Driver=usbhid, 1.5M
|__ Port 4: Dev 3, If 0, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 1, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 2, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 3, Class=HID, Driver=usbhid, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/10p, 480M
|__ Port 9: Dev 5, If 0, Class=>ifc, Driver=rtl8187, 480M
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
From what I've seen, this is usually a problem with the bootloader. How or why, I don't know. That being said, Firekit w/shorting trick seems to be the most successful at resolving this issue.
[Kindle Fire Q&A, Help & Troubleshooting] soukron:
I'm trying to follow this thread http://xdaforums.com/showthread.php?t=1636883 but I don't know how to check if the "short trick" is well performed or not. Is there anything I should notice? At this moment if I make the short trick and plug in the usb connector, nothing seems to be working in the kindle but dmesg is continuously showing errors like previous ones.

Regards,
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Are you using Firekit? What command?

"That's a special kind of stupid. The kind that makes me laugh"
[Kindle Fire Q&A, Help & Troubleshooting] soukron:
I'm still in the step of the process when I make the short trick, plug the usb and the kindle should be detected. Should I try the usbboot commands even when there's no kindle entry in lsusb output?
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
YES absolutely! And hold the power button for 15 seconds to make sure the CPU isn't running before attempting the short.

"That's a special kind of stupid. The kind that makes me laugh."
[Kindle Fire Q&A, Help & Troubleshooting] soukron:
The command is ./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img but it keeps stopped in waiting for OMAP44xx device....

I'm going to try a few times more. Thank you!

BTW, what are the next steps? Because this unit is working properly but the USB port to transfer data between computer and device: it boots, it loads stock firmware, and works properly.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Are you using a 32bit or 64bit machine? If you have SoupKit installed, option 2 should have installed 32bit libs, but sometimes it fails...mostly due to Ubuntu servers and them trying to make 32bit libs obsolete. If you're running a 64bit machine, try installing 32bit libs again and see if you get any errors.

sudo apt-get install ia32-libs

Also since you have SoupKit installed, run it and select option 4 to launch the Firekit. There's really no difference in using Firekit and manually entering the commands for Rekindle but it makes things a little easier. Select "usb_install_fff_twrp". The important thing to know about the "usb_fix_parts..." and "usb_install..." commands in Firekit is that they both use "fastboot boot ..." instead of "fastboot flash ..." to install TWRP and FFF. Meaning, if you reboot or shut the device down before actually installing a bootloader, the device won't turn back on and you'll have to do the shorting trick again.

That being said,

from the moment you make the short, you only have about 2 seconds to plug the device in and have Linux detect it

before the CPU resets and you have to start all over again.

Hold the power button for 10-15 seconds to make sure the CPU is off before attempting the short.

Launch Firekit and select "usb_install_fff_twrp". When the command is run, you will get the "Waiting for OMAP4 device..." prompt. Let it wait.

To do the shorting trick...

Something I have found to be most useful in this situation is to use a sharp pair of tweezers or safety pin to make the short.

Keep the device flat on a desk or table with the USB connection pointed away from you. Use one hand to hold the short, one hand to plug the device in, and use your body against the other end of the device as leverage as you plug it in.

Using a safety pin, stick the sharp end of the safety pin into the short point and press it in a little to keep it from sliding off when you plug the device in. Squeeze the other end of the safety pin or tweezers to make contact with the metal frame and immediately plug the device in while holding the short.

If the tweezers slip or make contact with the frame before you are ready, hold the power button for 10-15 seconds to make sure the device is completely shut down and try again.

You should see something going on in the terminal to let you know it's working...let it finish.

It might take a few attempts to get the timing right but persistence (and practice) is key...don't give up.

Follow these instructions and I'm positive you'll get it working again. Good luck.