yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] monil.verma:
So i own a Galaxy S3 with 16 GB internal storage and 64 GB external SD Card. The files i receive via Wifi Direct gets stored in the internal storage by default.

Can this be changed somehow to external SD Card ? :fingers-crossed:

And External SD Card to Internal Storage swapping using scripts is not the answer to my question. :p
[General Questions and Answers] sMiTTy0652:
Just wondering...Did you ever figure this out? Or anyone want to answer now? Cause I got the same prob that I need to fix..
[HTC Droid DNA] jdpalmer2k13:
I'm somewhat of a noob at this - this is my first HTC, so I had no idea what S-Off or unlocked bootloader meant. With my Samsung, rooting and installing a custom recovery involved a one-click method, so I never had to learn all the ins and outs of this stuff. With this DNA, I used the revone method (since the phone was purchased with 2.06 firmware already installed), so I still didn't need to learn much.

Anyway, I recently tried to go back to stock. I figured that would involve an RUU, going back to S-On, and locking the bootloader. So I first (yes, before performing the RUU like a dodo) used revone to go back to S-On, then found something saying I needed to execute "fastboot oem writesecureflag 3", so I did that, and now I am stuck at fastboot. I don't have access to CWM recovery, and if I try to boot beyond fastboot it hangs on the initial HTC screen.

Without being able to use ADB since it doesn't boot that far, I can't go back to S-Off via revone. I can't flash anything that I have been able to find so far via fastboot because it fails at signature verification. And I can't use the RUU that I found because it is firmware 1.15 and it won't allow me to install on top of 2.06.

Does anyone have any ideas on how to fix this? Is there a way to get to S-Off through fastboot? Is there an RUU for the 2.06 firmware? I have spent a few days searching and the answer to both seems to be no...

UPDATE: I grabbed the Rom.zip out of the 1.15 RUU and tried flashing that via fastboot (in RUU mode). I got the following message:

I assume this has something to do with the firmware version difference (1.15 vs. 2.06). But I was very excited to see a signature check be successful for once.
[HTC Droid DNA] jdpalmer2k13:
I should note that the ROM I was running when doing this was Newt's NOS m7 v 3.0.6
[HTC Droid DNA] Phaded:
When selecting recovery from the fastboot menu, it does nothing?

If that's a yes... You need s-off again.
[HTC Droid DNA] jdpalmer2k13:
It doesn't do nothing per se, it shows a screen that I'm not used to with a red triangle and exclamation point on top of a picture of a phone with a blue background. I assume this is the recovery screen from the factory, not the CWM recovery I had installed previously.

Is there a way to get s-off without ADB (only using fastboot)?
[HTC Droid DNA] Phaded:
Flash firmware zip located on the moonshine thread, then use moonshine
[HTC Droid DNA] jdpalmer2k13:
I successfully flashed the firmware zip from the moonshine thread, but the phone still will not boot past fastboot. I assume since the instructions for moonshine require the phone to be booted to android, this option will not work for me.
[HTC Droid DNA] jdpalmer2k13:
I've been thinking about this. Why did the firmware zip from Moonshine pass signature inspection? Was it signed? Could that same signature be placed on a rom or some other zip that installs a recovery or even somehow performs s-off? I know I am not very well experienced with android development, so I'm probably talking out of my ass.
[HTC Droid DNA] FynxSyndct:
I recently flashed the RUU from fastboot.

http://xdaforums.com/showthread.php?t=2115987 post#4
[HTC Droid DNA] bwhxeon:
I believe what you are looking for is in this thread.

To get back to stock on my phone I needed to flash the stock hboot first before I could use the stock RUU
[HTC Droid DNA] jdpalmer2k13:
I can't flash the stock hboot because I'm s-on and the file fails signature verification.
[HTC Droid DNA] bwhxeon:
Then your pretty much out of luck. Need to exchange it or possibly do a jtag. Does your phone say tampered/relocked? If so then I'd guess Jtag is the only solution.

Unfortunately the guide you used to go back to stock was pretty dumb in telling you make your phone s-on again. It isn't needed especially if it was just so you could do a clean install and flash other roms.

I was in your situation, but I was lucky enough to have unlocked my phone using htcdev when Jcase released his original unlock method. If the super cid method still works. I would unlock my bootloader the super cid method and not even bother with moonshine. That way you end up with a unlock token and wouldn't get stuck in this situation.
[HTC Droid DNA] Phaded:
Nothing was wrong with the guide. He didn't follow it correctly as he did s-on using revone.

Flashing the firmware zip should allow you to boot up and run moonshine. Are you sure it flashed correctly.
[HTC Droid DNA] jdpalmer2k13:
Correct, the guide was not at fault here, I am just an idiot. Here are the results of flashing the dna2.06firmware.zip file from the moonshine thread: http://pastebin.com/GkgdGt19

Following what is shown at this link, I executed "fastboot reboot-bootloader", selected "Power Down", and then tried to turn the phone on again. I got the same result as always (stuck on the initial HTC quietly brilliant screen - not the bootanimation screen).
[HTC Droid DNA] jdpalmer2k13:
Spoke with beaups on IRC. I was running a 4.2 rom that will not run on the stock kernel. Since the only thing I can flash is the signed stock kernel because I am s-on, the only remaining option is to run a 2.06 RUU. However, the 2.06 RUU has not been leaked to anyone's knowledge. So I will have to send off for jtag in order to get s-off, then flash whatever - RUU, custom ROM, what-have-you.

Thanks all for trying to help. I will hang on to it for a while if anyone has any other thoughts or suggestions.
[HTC Droid DNA] PiperBen85:
I talked to beaups last night about the same thing... Hes a good guy. I'm in the exact same boat. I hope there is a break through on this but if not I guess JTAG is our only option. Let me know if you figure anything out jdpalmer, i'd really appreciate it.
[HTC Droid DNA] Phaded:
Try this please

fastboot oem readcid

What's it say?
[HTC Droid DNA] PiperBen85:
VZW_001 for me. Not trying to jack your thread jd, it just seems we have screwed up in the exact same manner.
[HTC Droid DNA] jdpalmer2k13:
Yep same here
[HTC Droid DNA] Phaded:
You are s-on... Are you also locked?

---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------

It's possible you might have supercid, although I doubt it

You could try

Fastboot oem writecid 22222222

Reboot

Fastboot oem readcid

Did it change?
[HTC Droid DNA] jdpalmer2k13:
Yes, I am locked. Here is the result of trying to writecid:

C:\Android>fastboot oem writecid 22222222
...
(bootloader) [SD_ERR] The project does not support SD card
(bootloader) E0902910 E0902E20
FAILED (status read failed (Too many links))
finished. total time: 0.005s
[HTC Droid DNA] Phaded:
Meh... I'm at a loss. If beaups wasn't able to help either then you may need to jtag
[HTC Droid DNA] jdpalmer2k13:
Thank you for trying.
[MDA III, XDA III, PDA2k, 9090 General] joey jojo:
hi, i just wanted to say that my findings after yesting wm5.0 this week that after using my device the same way i used it on wm2003se, that at 12.00pm my battery is usually on about 20% , using wm5 i now have 65% left doing the same thing. i do have backlite on low, and im not sure if it has anything to do with patches, but its better than wm2003se, an its only a beta copy. lol.

anyone else having bettery battery life using wm5.0?

p.s, i am still waiting for someone to explain the difference between rom and ram that wm5.0 uses.
[MDA III, XDA III, PDA2k, 9090 General] far182:
I am seeing better battery life, but nothing I can put a number too.

Also, GPRS works everytime. No resets required.

If only bluetooth worked right! :(
[MDA III, XDA III, PDA2k, 9090 General] joey jojo:
even by Bluetooth works perfect, i havent got bt headset, so havent tried, but i dont need one so even if it didnt work, i wouldnt care, lol.

if u have that mamiach patch, for backlight and stuff, u will see the old icon for battery and at gives u the % of battery. and today plugins for battery meters also work, i have tried a few, and they seem to work.

but i use o2 plus, and that runs perfect, hell, i might even be Brave enough to try o2 active, lol, i can always reflash if it fooks up!
[MDA III, XDA III, PDA2k, 9090 General] mwheeler2:
WM5 RAM and ROM... (for joey jojo)

The difference between RAM and ROM (for any computer) is that the ROM (Read Only Memory) must be flashed to change state. This means that data stored/flashed to the ROM is persistent and is not affected by a loss of power. It can only be altered by a flash operation, but can be read at any time. RAM (Random Access Memory) can be written, read, stored only with power applied. This means that RAM is cleared whenever power is lost.

What this means in terms of WM5 is that your personal data and programs are written (flashed) to ROM, which is not affected by battery (or backup battery) failure. Since this information does not require any changes to be used (a program is loaded into RAM when it is run, so it occupies ROM until called by the user), it is not necessary for it to occupy RAM space for storage. This means that RAM is used to run the OS and programs, not to store your PIM data or programs.

This explanation is in layman's terms and is not applicable to all operating systems, but does describe in general terms how RAM/ROM work in PDA's.

Hope this offers some insight into memory function...

Mick...
[MDA III, XDA III, PDA2k, 9090 General] Twiglet:
Mine installed like a dream and seemed to last about the same but now its bein cained big time bcause iv overclocked it to make it run smoothly. just ordered a better battery :-)
[MDA III, XDA III, PDA2k, 9090 General] Mastiff:
And battery life matters a lot less now! I can run it to the ground without fear of loosing any data!
[MDA III, XDA III, PDA2k, 9090 General] remixme:
In addition to what mwheeler2 said, under 2003SE there was what was known as the 72 hour rule, meaning that manufacturers were obliged to make sure that even when the battery reads 0% and the device shuts off there is still enough power to keep the ram contents stored for a period of 72 hours, so in other words a large proportion of the battery capacity was used just to store the data in RAM, although dont ask me if that includes the backup battery as well!

But don't just take my word for it, read for yourself:

http://buzzdev.net/index.php?option=com_newsfeeds&task=view&feedid=12&Itemid=64
[MDA III, XDA III, PDA2k, 9090 General] dilipc:
Can you tell me how you overclocked it? or refer me to the right post? :D
[MDA III, XDA III, PDA2k, 9090 General] imablackhat:
i dont seem to have any different battery life with my 1490 mAh. But I just put an order in for a 2400 mAh, can't wait to see how this baby runs :)
[MDA III, XDA III, PDA2k, 9090 General] Toche:
@Dilipc: might be what you're looking for: http://xdaforums.com/viewtopic.php?t=27976
[Galaxy S 4 Q&A, Help & Troubleshooting] lup3x:
Hey,

I have following problem:

Few days ago I bought a Samsung Galaxy S4 Lte (I9505 jfltexx). I wanted to root it and then flash CM onto it.

Rooting went fine but when I flashed CM it aborted with Error 7. After that it was soft bricked but i managed to flash the Stock Rom back and everything was fine again.

But today I tried it again but got following problem. CWM was gone and i had to reflash it. But then everytime I tried to get into recovery mode the phone freezed at the "Samsung Galaxy S4 I9505" Logo with the little blue "recovery booting" in the left upper corner. I tried to flash CWM and also twr but it did not help.

SO my final thought was flashing the stock rom again to at least have a working phone. But when I tried to flash the Stock Rom ODIN failed and my phone gave this error "SW REV. CHECK FAIL : fused:2, Binary: 1".

Then every time it started it booted into download mode and said "firmware upgrade encountered an issue. please select recovery mode in kies & try again". I googled how I can solve this and someone said that it has something to do with root. So again I flashed the CF auto root and thank god it booted up normally.

But now my problem: I have no root on my phone(superSu says that there are no SU-binarys), I can't update my stock-firmware because the software update says that my phone has been changed. What can I do to 1. gain root access again 2. flash a custom rom(best would be SlimBean)?

Hope you can help me :(
[Galaxy S 4 Q&A, Help & Troubleshooting] joecool666:
mate mine says the same as yours. so might just be because it failed not sure tho we will just have to wait and see if someone can come up with a answer. regards
[Galaxy S 4 Q&A, Help & Troubleshooting] lup3x:
thank god somebody with the same problem! Is your device rooted? because whenever i try to root it odin says pass and SuperSu is installed but the phone is not rooted
[Galaxy S 4 Q&A, Help & Troubleshooting] joecool666:
not now its not. going to wait for c-f for fix until then i am staying where i am stock unrooted lol just to be safe.
[Galaxy S 4 Q&A, Help & Troubleshooting] lup3x:
GOTCHA! I used the auto root from here https://plus.google.com/+Chainfire/posts/5ggu7naWtaW and it finally worked! I don't know if it will work for u but i tried it out and i finally got it. Now to the ROM Part :P
[Galaxy S 4 Q&A, Help & Troubleshooting] YIKES1412:
What is this great advantage that rooting and installing cf brings, that makes you run the risk of destroying your brand new, very expensive phone?
[Galaxy S 4 Q&A, Help & Troubleshooting] lup3x:
The fact that i really don't like this mess which samsung calls a firmware. When i buy a pc i want to do anything i want with it. Same goes for smartphones.
[Galaxy S 4 Q&A, Help & Troubleshooting] YIKES1412:
Ok, I'm just wandering what big difference it makes. What extra does it enable your phone to do? I mean it must be really good to run this risk.
[Galaxy S 4 Q&A, Help & Troubleshooting] lup3x:
First of all it's the principle that I don't want to have a phone where Samsung tells me what to do and what not. Then there are things like root which are necessary for me because I'm also using it to test my apps which require root access. And also of course apps from the play store which need it. I'm currently using Slimbean because there's no AOKP build for the I9505. It requires less space on the phone, it's heavily customizable and it has the look of vanilla android. And a huge portion of why I am doing this is just me being curious about such things. :p

In the end it worked and I learned very much new stuff.

Sry 4 bad english :p
[Galaxy S 4 Q&A, Help & Troubleshooting] YIKES1412:
Hey your English is very good mate. And I was just curious as to why you run the risk, thanks for explaining it to me. I rooted and put a new rom onto an orange san francisco (zte blade) once. But that was not an expensive phone. My wife would kill me if I messed up this s4 with almost 2 years of contract to go lol
[Galaxy S 4 Q&A, Help & Troubleshooting] Ratata82:
Hi all

My I9505, has turned quite weird today... I tried flashing it with latest NEE firmware, but it failed:

<ID:0/005> NAND Write Start!!

<ID:0/005> sbl3.mbn

<ID:0/005> rpm.mbn

<ID:0/005> aboot.mbn

<ID:0/005> FAIL! (Auth)

<OSM> All threads completed. (succeed 0 / failed 1)

And on the handset I get in red writing:

STAT: [224, 1440]

SW REV. CHECK FAIL : fused : 2 , Binary : 1

I can only flash it with:

I9505XXUAMDE_I9505OXXAMD8_NEE

When entering recovery I sometimes get:

"No command" instead of the windows where it sets CSC, sometimes it sets CSC normally

When I try to reset flash counter I get

could not find triangle and counter data

I have also tried flashing with PIT, but that didn't help either...

Any help??

Kind regards
[Galaxy S 4 Q&A, Help & Troubleshooting] Ratata82:
I have already tried all the steps, many times... This is just driving me insane
[Galaxy S 4 Q&A, Help & Troubleshooting] samersh72:
it is something to do with bootloader

read this http://teamuscellular.com/Forum/topic/4963-★☞-support-touchwizstock-deodexed-jflteuscr970vxuamf5-☜★/?p=77401 post #51

and this http://xdaforums.com/showpost.php?p=43619724&postcount=479
[Galaxy S 4 Q&A, Help & Troubleshooting] Ratata82:
But then I should be able to upgrade it, it fails with every single rom except the oldest. But looks like you are right
[Galaxy S 4 Q&A, Help & Troubleshooting] Ratata82:
Fixed:

The problem was infact the new KNOX secure bootloader. I just upgradet it to I9505XXUDMH8_I9505OXXDMHA_BTU, and that fixed it.

Hopefully we will soon see a bootloader downgrade for new KNOX security Samsung handsets, nothing is unbreakable

Best regards
[Galaxy S 4 Q&A, Help & Troubleshooting] hrazanaqvi:
Please Explain

can you please explain, how did you fix it. I am facing the same problem :crying:
[Galaxy S 4 Q&A, Help & Troubleshooting] waterdaan:
You can't downgrade which means flash a previous android version

So just flash the newest android version and you'll be ok
[Nexus 7 (2013) General] hollisterryann:
This was taken with my Nexus 7 2nd generation . Front camera is clear and this is my back camera on 5mp.is is completely blurry. Is there a sticker on camera or something giving me quality this bad. It's also makes a clicking noise when switching to camera is that normal
[Nexus 7 (2013) General] DeDanMU:
The clicking noise is normal. But the blurry pictures not. Maybe reset the device. And try again.
[Nexus 7 (2013) General] pmr5019:
I don't remember having to remove a sticker from the lense at all. That clicking sound,does it come from the speakers or does it sound like its coming from N7's internals? That doesn't sound normal to me, def. not happening on mine.

I would download a replacement camera app and test that out. If the same thing happens I would guess you have a malfunctioning camera, specifiaclly the focus feature. If the replacement camera app doesnt produce the same issue and it doesn't fix it on the stock camera app then I would guess that the stock camera app isn't communicating with the lense correctly.

Best of luck!
[Nexus 7 (2013) General] Username invalid:
Try flashing a different kernel as that is what bridges hardware and software.
[Nexus 7 (2013) General] hollisterryann:
When I take pictures close up. Like inches away the quality is better but from a few feet it's bad. I'll try it once I leave work. Sucks if I need to send it back to Google
[Nexus 7 (2013) General] player911:
Sounds like it isn't focusing properly. The clicking sound IS normal, it's the shutter or whatever, but it shouldn't be that loud. It should sound more like a light rattle when tapping near the camera.

In this case, it sounds like the camera's focus lens is broken. When you tap on different parts of the screen, in the camera app, it should focus where you are pointing. Unfortunately I think you should exchange it. This is the first one I've heard with this issue so it isn't common. Perhaps it was dropped and knocked the focus gear out of whack.
[Nexus 7 (2013) General] hollisterryann:
No never dropped it. Thing is babied. I'll have to call Google becaus it was bought from play store. This should be a fun experience
[Nexus 7 (2013) General] Kookas:
Shouldn't be too bad, Google customer support is pretty good IME, though it's an odd experience speaking to Americans as a Brit.
[Nexus 7 (2013) General] Richieboy67:
I think I have tried one of the cameras one. They are junk. Love the device but definitely would not use it for taking pictures. I just use my vacate or even my nex 4. These cams on this device are worthless.
[Nexus 7 (2013) General] cowisland:
Your picture looks as if it's totally out of focus. Try touching the image on the screen of the object you are photographing to make sure you focus on it. Alternatively, just take a picture of a wall so that everything in your picture is equal distance from the camera.
[Nexus 7 (2013) General] Gorgtech:
The camera is just a nice toy, not more or less. It´s good enough if you want to shoot some quick pictures of the stuff you´re about to sell at ebay :D

Btw, every cellphone camera offers a better quality, check this out : http://thebestpageintheuniverse.net/c.cgi?u=padhole :eek:
[Nexus 7 (2013) General] kevin619:
One of the more significant updates to the Nexus 7 (2013) is the inclusion of a 5-megapixel camera where previously there was none. Even though camera usage isn’t very optimal on a tablet, it is a nice addition when you just need a simple shot and nothing too fancy.

The camera app brings all the usual capabilities you get in a stock Android camera app, and that includes Photo Sphere, an improved Photo Sphere, in fact. Picture quality is decent enough, but honestly, it’s nothing to get too excited about.
[Nexus 7 (2013) General] hollisterryann:
I'm never gonna use the camera. I usually sell all my olf stuff once a new one comes out and this would be a bad thing when it comes to sell it. Something wrong with focus. Working on a return through Google customer service
[Nexus 7 (2013) General] stanglifemike:
There is definitely something out of whack with the camera on your N7 FHD! While the camera on this tablet is anything but good, the photo you posted is worse than normal. I agree that using a camera on a tablet is far from idea, my Asus Infinity takes excellent photos!! I'll rarely ever use either camera in the N7 FHD, but if mine was defective then I'd definitely want a replacement device!

SwiftKey'ed from my '13 Nexus 7 FHD using XDA Premium HD
[Nexus 7 (2013) General] swisstourist:
uh. u can upload Dropbox picture taken with your phone...

just need to activate your wifi when at home. 2 minutes later all your pictures will be on Dropbox.

tablet is good for documents to send immediately. scan fax... whatever.
[Nexus 7 (2013) General] NigPod:
i think its a problem with all the nexus 7s, both mine and my freinds nexus needs to be focused twice to produce focused shots. hope its software, im going to try a new rom or camera app soon
[Nexus 7 (2013) General] robdroyd:
My N7's rear cam also needs to focus twice (or more) before it snaps a good focused photo.

I'm running a custom kernel and ROM- but they both originate from Google source-code, so it may well be a software issue?

Once it gets focus lock- it seems to drift off very quickly, almost like it's too sensitive to very small movements of the tablet.

Would be nice to have a manual focus override...
[Nexus 7 (2013) General] Pfeffernuss:
Didn't even try the camera prior to reading this thread :p

But indeed, the images are grainy. They are "okay" when being watched in a smaller size but at 100% you can surely see blocky stuff.

Made two test shots (here and here). Am never going to use the camera anyway so no biggie for me :cool:
[Nexus 7 (2013) General] hollisterryann:
Looks better then mine did. I got a replacement and this one is better. Not gonna use it just h Los for resell value that Everything works
[Java for Android App Development] st0neski:
Hi all, I am trying to develop a widget that works similar to the App Folder that comes standard with android. The functionality is that you can drag and drop apps into a folder so that your homescreen is a bit more organized. Is it possible to create a widget that can accept a drop of another application?

I have done a lot of searching on google and have come up short. Any help is appreciated.
[Java for Android App Development] SimplicityApks:
AFAIK, there's no way of doing this except with building your own home screen launcher since (most) Android launchers move widgets out of the way if you drag a shortcut on them (JB+) and do not pass any event or call to the widget (all versions).

You can, however, create that Widget and in the setup screen show a check list with all apps so the user can choose there which apps they want in the folder.
[Java for Android App Development] nikwen:
That's a good idea. :good:

Yeah, as far as I know there is no way to do this, too. :(