yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] badogg:
Ugh, nevermind. I guess he was confused and thought we were asking about HTCOne. Waiting for him to reply about DNA. So scratch what I said. Sorry.
[HTC Droid DNA] .torrented:
At least you get replies I've tried before and only gotten silence
[HTC Droid DNA] badogg:
From Jason Mackenzie? He's responded every single time I've tweeted to him. Granted it is about 4 times total, but still. :)
[HTC Droid DNA] .torrented:
yup Ive tweeted at him 2-3 times with no response
[HTC Droid DNA] Uzephi:
Lucky. I asked him why the DNA got pushed back to "integration" no response :(

Checking his feed for news or responses and Verizon was the second to approve the One update. Now for HTC to make the DNA 4.4 that can go through approval... Which by history, I'd say might never happen given the age of the device compared to the One.
[HTC Droid DNA] Lens Pirate:
Geez..... such a awesome phone... Still one of the best. Criminal that it is not updated already.
[General Questions and Answers] pianokeys:
Hi all, I tried posting this on the dedicated forum for the Elocity A7, but it's a pretty old device and it looks like that forum is closed down or archived. I'm super new to XDA, so please forgive me if this isn't the right place to post.

I have an old A7 kicking around that I'm trying to turn into a simple game and movie device for my daughter. I'm super new to rooting devices and I found a step-be-step guide on XDA for the "Evilocity" mod, which appears to be specifically designed for my device (link below).

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

I've followed the instructions step by step and after the entire process was complete, my device just white-screened and is now useless. I can't access any menus or even load the recovery menu in the boot cycle to try and "undo" this update.

Does anyone know of a way to wipe the device clean? Or get the root package to take? I'm not totally bummed out as this was an old device that nobody was using, but I'd prefer not to just chuck the thing in the garbage if I can salvage it.
[8125, K-JAM, P4300, MDA Vario General] DJMurtz:
I've read several topics about programs that have profiles for virbrate on/off, different call volumes, etc.

I've also read topics about phones switching to BT when picking up in your car.

What I haven't read, is a tool that gives me the possibility to switch between two profiles. One profile enables the handsfree function (speaker function) on pickup (I don't have a carkit, so this is the alternative) and the other switches back to normal functioning pickup key..

anyone?
[8125, K-JAM, P4300, MDA Vario General] DJMurtz:
anyone please? I could really use a function like this. Have to pick up the phone each time I get a call in the car right now, and that's not allowed here in the netherlands :shock:
[Samsung Galaxy Gear] verbaljeff:
Any suggested apps for using Gear to track sleep? Either using a side loaded app or with a custom ROM?
[Samsung Galaxy Gear] hurdlejade:
sleep as android comes to my mind, but i haven't tried sleep tracking mode on the gear.
[Samsung Galaxy Gear] 3vo3d:
+1 I use this on my note 3 and it is very good. I never thought of running it on the gear though.

Interested if you do!
[Samsung Galaxy Gear] ronfurro:
When are you ever going to find time to charge it! LOL
[Samsung Galaxy Gear] exactor_mortis:
Not the OP, but I get up a couple of hours before I have to work, so theoretically that's all I need.
[Samsung Galaxy Gear] zim_zimmer:
Is there such an app that can run on the Galaxy Gear then?

So much like the fitbit bands and the new Gear 2 range it will monitor your sleep??
[Samsung Galaxy Gear] fastmike:
Yes and no. The Gear 2 sleep monitorig is very poor and only limited to 'no movement detection'. So if you havea bad night and cannot sleep,but just keep your eyes opened it will just tell you that you had no movement for 100% of the nigt.

Not reallly a monitoring system that should be linked to heart beat and other valuable information.
[Samsung Galaxy Gear] zim_zimmer:
True but given that a FitBit or other fitness band would also not be able to tell if you have your eyes open or not, its never going to be the most reliable way of recording sleep anyway!

With regards to the Galaxy Gear then... you're saying that there is an app to use on the watch itself?
[Samsung Galaxy Gear] hackerseraph:
Sleep as Android

I used ADB to install Sleep as Android. I bought this app a few years back, and I've loved it ever since.

Used it on all my android phones

-HTC Aria

-Motorola Atrix

-Samsung Galaxy

-Samsung Galaxy Note

-Samsung Galaxy S4

I just got a Galaxy Gear 1st Gen, and figured it was worth a shot. It installed and ran without issue here at the office. When I get home in 3 hours, I'll do a quick charge of my Galaxy Gear (I love how fast this thing charges) and then I'll go to sleep and see how the battery holds up and how the tracking does.

[IMG="Sleep as Android Icon"]https://pbs.twimg.com/media/BrnCqznCQAAlqOT.jpg:large[/IMG]

[IMG="Motion Tracking Test"]https://pbs.twimg.com/media/BrnD1gNIEAAc5aE.jpg:large[/IMG]
[Samsung Galaxy Gear] hackerseraph:
well... that didnt work out as well as I hoped. I came home, curled up in bed. Set the app, the screen dimmed off, and I went to sleep. I woke up around 2pm, and went to check the app and its nowhere to be found under apps. I checked in the background apps, its running, but when I tap on it, it doesnt launch. I rebooted the watch, the app is missing from the apps section. Im going to install nova launcher and try again later :confused:
[Samsung Galaxy Gear] hackerseraph:
Graph Indeed Saved

So I got into the office tonight, and sideloaded NOVA Launcher, and found the "missing" sleep as android app

looks like it did properly exit and grab my sleep graph. Today when I get home I'll try setting Nova Launcher as my default (this scares me, as I'm worried about it interfering with watch functionality) as see if it works a bit smoother, than it did yesterday.

[IMG="Sleep as Android Graph"]https://pbs.twimg.com/media/BrrJlv3CYAISp4Y.jpg:large[/IMG]

---------- Post added 4th July 2014 at 12:25 AM ---------- Previous post was 3rd July 2014 at 11:57 PM ----------

side note, I engaged urbandroid.info@gmail.com (the developer) via email to see if the community can assist them in getting a version pushed for the galaxy gear. I am eager to see to a response :fingers-crossed:
[Samsung Galaxy Gear] navilon:
From the official demo video, the app seems to detect patterns as if it was the phone lying on your bed. having the app on your hand would (i think) give the accelerometer much different results. Does your method seem work well? I'm really interested in getting this watch if this works!
[Android Apps and Games] Disharmony:
Description

Explore the world of weaponry like

never before! Disassemble and

reassemble 89 highly-detailed

models with fully working

animated parts! View the gun in

complete 3D, and learn about the

inner workings of the guns.

Operate the weapons in

OPERATION mode and try out your

skills by disassembling the

weapons as fast as possible,

competing with players AROUND

THE WORLD!

With fast and responsive 3D

graphics, you can discover the

parts of the guns from the gears

and bullets to the barrel and

chamber! Attach scopes, silencers,

and various parts to enhance the

shooting experience!

Features:

- 88 highly detailed models, all in

FULL 3D and high-definition retina

graphics

- Explore more than 7200 parts,

each with complete sound effects

and dynamic lighting

- Interact with the guns in

OPERATE mode, with four levels of

X-Ray and two levels of slow

motion

- Enjoy five game modes: Demo,

Operation, Disassembly, Assembly,

and Game

- Extensive collection of models

available via in-app purchase

- Stay up-to-date with new

models released periodically,

Available models:

Pistols

- Glock 19

- CZ75

- Colt 1911

- SIG P228

- Beretta 92FS

- Desert Eagle .44

- S&W Sigma

- Springfield XDM

- Browning Hi-Power

- Makarov (PM)

- Jericho 941

- Welrod MKII

- Walther PP

Smith & Wesson M&P.40

SMG/Assault Pistols

- MP5

- Tec-9

- Uzi

- HK UMP 45

- Kel-Tec PLR-16

- FN P90

- Mac-10

- Scorpion vz.61

Launchers

- RPG 7

- M32

Revolvers

- Colt Python

- S&W Model 53

- Colt SAA

- Ruger New Vaquero

- Chiappa Rhino 200DS

- Ruger Super Redhawk

- Ruger Old Army

Historical

- Colt Hammer

- Mauser C96

- Borchard C93

- Maxim

- Harpers Ferry

- Lewis Gun

- Winchester 1873

- Mauser 1914

WWII

- Tokarev Pistol

- Luger P08

- MP40

- Sten MK II

- M1 Garand

- Thompson Gun

- Mauser 98K

- PPSH

- Boys Anti-Tank Rifle

- SKS rifle

- Mosin-Nagant

- DP 27 machinegun

- Walther P38

- Lee Enfield

- StG. 44

Assault rifles

- AK47

- SIG SG552 commando

- LR 300ML

- HK G36E

- FN FAL

- FAMAS-F1

- M-16

-TAR-21

- M4 Carbine

Rifles

- SIG SG550S

- SVD

- HK SL9SD

- Barrett M107

- M14

- M200 CheyTac

- Steyr Scout

Machine gun

- M60

- M134D 'Minigun'

- Browning M1919

Compact Guns

- Ruger LCP

- Derringer

- COP 357

- AMT Backup

- Ruger LCR

Shotguns

- Remington 870

- Mossberg 500

Artillery

- ZiS divisional field gun

- 88 cm Flak 37

Sport

- Ruger .22 Charger

- Marlin 336

- Ruger MKII

- Marlin 336

- Ruger No.1

- Beretta CX4 Storm

TRY OUT THE MOST

COMPREHENSIVE MOBILE GUN APP

NOW! Go Ahead on Googlepaly and search for this awesome app.
[One (M7) Q&A, Help & Troubleshooting] fromtheaudible:
My AT&T HTC One (32 GB) that I bought day one keeps rebooting randomly.

From day one, I rooted, unlocked my bootloader, flashed CWM, and installed Android Revolution.

I've since updated up to AR 31.0 without any problem, and have been running that version for quite a few months.

I have never had any problems with Mike's roms on any of my other phones.

Recently, it reboots completely, even when I'm not touching it.

Once booted up, it will revert to a previous state. The same apps will begin to update, I will be notified of the same emails, voicemails, texts, etc.

If I touch it while all this happens, it will reboot again, and do all of the same things.

If I leave it alone until all of this occurs, I might have some luck using the phone in a stable state.

I've not installed anything new recently.

I run Seeder, a few Xposed tweaks, a couple of Sense Toolbox tweaks, and Tasker at root level, but all of these things have been running simultaneously without a problem for months.

This just started happening out of no where.

Again, running AR 31.0, Android 4.3, Sense 5.5. Random reboots.

Any ideas guys?
[One (M7) Q&A, Help & Troubleshooting] kamilmirza:
does this happens on any other ROM?
[One (M7) Q&A, Help & Troubleshooting] fromtheaudible:
Nope. Never had this happen before. I just wonder how something could have changed without me doing anything.
[One (M7) Q&A, Help & Troubleshooting] kamilmirza:
try any other ROM and see
[One (M7) Q&A, Help & Troubleshooting] fromtheaudible:
Been trying to.

I've tried to flash the rom cleanly, but it reaches 30% and reboots every time.

I'd flash another rom, but I'm running CWM, and all I seem to find is new roms that require TWRP.

When trying to install TWRP recovery, the phone still boots into CWM.

I have no idea what to do.
[One (M7) Q&A, Help & Troubleshooting] kamilmirza:
download TWRP from here

then place it in your adb folder

then reboot your phone into recovery and try any other ROM

---------- Post added at 12:07 AM ---------- Previous post was at 12:04 AM ----------

before all that paste the "fastboot getvar all" (without S/N and IMEI removed) from the bootloader
[One (M7) Q&A, Help & Troubleshooting] fromtheaudible:
Tried exactly that twice before you posted it, but still no luck.

Boots into CWM, won't allow full flashes, and still reboots randomly.

Here's the info though:

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4A.14.3250.13

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno:

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0712000

(bootloader) cidnum: CWS__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4237mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

ERROR: usb_read failed with status e00002e8

getvar:all FAILED (status read failed (No such file or directory))

finished. total time: 0.042s

I found the usb read status to be interesting. Maybe that's the issue.

Any idea how to fix that if that's the problem?
[One (M7) Q&A, Help & Troubleshooting] kamilmirza:
have you tried the latest CWM?
[One (M7) Q&A, Help & Troubleshooting] fromtheaudible:
I'm on CWM 6.0.3.1.

Just tried to flash two different versions of TWRP, and CWM, standard and touch.

None of them stuck when I tried to enter recovery from the bootloader, even though fastboot gave me successful flashes.

:(
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
Had something similar happen on a nexus ages ago. Internal SD died..
[One (M7) Q&A, Help & Troubleshooting] kamilmirza:
we need a professional here ;)

let's call [MENTION=2605798]nkk71[/MENTION] :fingers-crossed:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Didn't read much, but

1- CWM 6.0.3.1... r u kidding?

2- 31.0 was released (at first) with w/p kernel, so changes wont stick,

Use 31.6 instead

3- 'random reboots' -> how's your power button?

Go to bootloader, any reboots ->

no -> go to custom recovery -> any reboots?

If yes to any of above, then ur power button is stuck.

Good night...
[One (M7) Q&A, Help & Troubleshooting] nkk71:
okay, just reread, so a couple of questions:

1- So you had this problem from day 1? and didnt think of exchanging it?

2- what OS you running (Win7, mac, etc)

(bootloader) version-main:

3- what did you try to flash (any firmware)??

(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001

4- have you tried restoring to stock using RUU_1.26.502.12_PN0712000_CWS__001_4A.14.3250.13

5- The random reboots, could indicate a hardware problem and/or corrupted partition(s), you could check those by opening a shell while in custom recovery (CWM or TWRP), and check the output:

C:\...> [B]adb devices[/B]
List of devices attached
H*********** recovery <- yep it's in recovery

C:\...> [B]adb shell
umount /system
umount /data
umount /sdcard
umount /cache[/B]

[B]e2fsck -n -v -f /dev/block/mmcblk0p35[/B] <- this checks /system
[B]e2fsck -n -v -f /dev/block/mmcblk0p36[/B] <- this checks /cache
[B]e2fsck -n -v -f /dev/block/mmcblk0p37[/B] <- this checks /data

if there are no major errors then output will look something like this:
[HIDE]~ # e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

39356 inodes used (2.31%)
350 non-contiguous files (0.9%)
31 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 38933/54
4696398 blocks used (68.91%)
0 bad blocks
1 large file

36560 regular files
2426 directories
0 character device files
0 block device files
0 fifos
0 links
357 symbolic links (357 fast symbolic links)
4 sockets
--------
39347 files[/HIDE]
if there [B]are [/B]major error, then output will look something like this:
[HIDE]~# e2fsck -v -f /dev/block/mmcblk0p37
e2fsck -v -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p37

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>[/HIDE]
[One (M7) Q&A, Help & Troubleshooting] LibertyMarine:
Maybe too low voltage?

Or http://android-revolution-hd.blogspot.ch/2013/10/fix-data-htc-one.html ?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
ah, ok my bad, i misunderstood.

Windows 7 should do nicely.

I think above refers to your ROM, cause your "(bootloader) version-main: " (ie firwmare) is blank, and since you're on hboot 1.44 + radio 4A.14.3250.13 should equal the RUU I posted earlier.

but nevermind for now

it won't unmount if it's already umounted, so that was not really an error

and there we go :( , the plot thickens, both /system and /data have some corruptions, not completely unmountable but also not completely clean, which would be a good reason you're experiencing problems.

the one thing i'm concerned about it that the problem is with both /system and /data, which may indicate a hardware fault.

we can go ahead and perform a "real" format (as opposed to wipe) of these partitions, if the formatting sticks (ie without filesystem errors coming up again), then it could just be a software issue.

Let me know if you want to proceed? (if you are going to format /system and /data), you need to be comfy with adb shell, adb push and/or adb sideload)

PS: I may need to offline in about 20mins, and could be back in a few (probably like 3+) hours or so
[One (M7) Q&A, Help & Troubleshooting] fromtheaudible:
That's what I gathered I'd have to do once LibertyMarine linked that forum post from Mike1986.

I'm all for it.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
i've done it with other users 3 or 4 times successfully, and 1 failure because of the filesystem errors kept coming back and back and back = hardware problem.

so have you read [MENTION=1631739]mike1986.[/MENTION] thread? you comfy with it?

here goes:

1- download this: http://goo.gl/pmZ9Mt and place it in your adb/fastboot folder

2- in recovery:

[B]adb push mkfs.ext4 /tmp/

adb shell
chmod 777 /tmp/mkfs.ext4

umount /data
umount /sdcard
umount /system

/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p35

/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
[/B]

you can see the expected output in mike's blog: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html

mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1703936 inodes, 6815744 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
208 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768,98304,163840,229376,294912,819200,884736,1605632,2654208,4096000
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 25 mounts or 180 days, whichever comes first.
Use tune2fs -c or -i to override.

if that goes all well, continue in the shell:

[B]mount /data
mkdir -p /data/media/0
exit[/B]

then push your rom:

adb push rom.zip /data/media/0/ <- this will take 5 mins or so with no progress showing until finished

then install your rom in recovery, and hope for the best, stay away from 4.4 (KitKat) ROMs for now, because of recovery version (BTW: which one and version do you have?)
[One (M7) Q&A, Help & Troubleshooting] fromtheaudible:
No working mirror for mkfs.ext4 file. :/
[One (M7) Q&A, Help & Troubleshooting] nkk71:
working here: http://www.androidrevolution.nl/downloader/download.php?file=mkfs.ext4

otherwise i'll upload it to my dropbox.
[One (M7) Q&A, Help & Troubleshooting] fromtheaudible:
Got it. Attempting now. Wish me luck!

I'll report back with results once I've finished.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Good luck, fingers-crossed :fingers-crossed::fingers-crossed:
[One (M7) Q&A, Help & Troubleshooting] fromtheaudible:
Alright, so I just ran through everything.

Despite trying twice, my data directory still exists as it was.

It doesn't seem to want to format even though I get proper feedback that I am in adb.

So when I push the rom successfully to what would be a new /data/media/0 directory, it still shows my old stuff, unformatted.

It's like no matter what, nothing will stick.

The phone always reboots/remains in this state.

Interesting side note, because the phone still boots up, I'm able to connect it to my PC or Mac and transfer files to it (it's still recognized as mass storage).

However, when I try to push files to it, they will copy over and then fail once complete.

The phone will then reboot.

Because of this, I'm thinking it must be a storage issue.

Possible that the internal SD died, as [MENTION=3525160]SaHiLzZ[/MENTION] suggested.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
that sounds quite strange, can you copy/paste your command prompt output please, and also, do this:

C:\ADB2>adb shell

~ # cat /proc/emmc

cat /proc/emmc

dev: size erasesize name

mmcblk0p19: 000ffa00 00000200 "misc"

mmcblk0p34: 00fffe00 00000200 "recovery"

mmcblk0p33: 01000000 00000200 "boot"

mmcblk0p35: 73fffc00 00000200 "system"

mmcblk0p26: 00140200 00000200 "local"

mmcblk0p36: 27fffe00 00000200 "cache"

mmcblk0p37: 680000000 00000200 "userdata" <-- confirm it's mmcblk0p37

mmcblk0p22: 01400000 00000200 "devlog"

mmcblk0p24: 00040000 00000200 "pdata"

mmcblk0p27: 00010000 00000200 "extra"

mmcblk0p31: 04b00200 00000200 "radio"

mmcblk0p16: 03c00400 00000200 "adsp"

mmcblk0p15: 00100000 00000200 "dsps"

mmcblk0p17: 007ffa00 00000200 "radio_config"

mmcblk0p20: 00400000 00000200 "modem_st1"

mmcblk0p21: 00400000 00000200 "modem_st2"

mmcblk0p28: 00100000 00000200 "cdma_record"

mmcblk0p18: 02000000 00000200 "reserve_1"

mmcblk0p30: 034ffa00 00000200 "reserve_2"

mmcblk0p32: 05fffc00 00000200 "reserve_3"

mmcblk0p29: 06069e00 00000200 "reserve"

~ # mount

mount

rootfs on / type rootfs (rw)

tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)

devpts on /dev/pts type devpts (rw,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,relatime)

/dev/block/mmcblk0p36 on /cache type ext4 (rw,nodev,noatime,nodiratime,data=ordered)

/dev/block/mmcblk0p37 on /data type ext4 (rw,nodev,noatime,nodiratime,data=ordered)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
unfortunately it looks that way :crying:, as mentioned before both /system and /data keep getting corrupted = hardware fault

if after format and reboot "e2fsck -n -v -f /dev/block/mmcblk0p37" still shows errors, then i can't think of anything more to do on a software level.

you can still try the ruu i posted earlier, no reason it shouldnt go through, but since you're S-On you will need to relock bootloader "fastboot oem lock" -> it will show as relocked on bootloader

here's what you can and can't do with (re)locked/unlocked and s-on/s-off: http://xdaforums.com/showpost.php?p=49832723&postcount=388
[One (M7) Q&A, Help & Troubleshooting] fromtheaudible:
Would it be wise to go S-Off and try the RUU?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
how are you gonna get s-off without a ROM?
[One (M7) Q&A, Help & Troubleshooting] fromtheaudible:
I tried using this guide here, but got hung up at ./revone -P with an error, and couldn't resolve it via the directions.

What do you mean by "without a rom?"
[One (M7) Q&A, Help & Troubleshooting] nkk71:
i thought you don't have a working ROM, did i misunderstand?