yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Gear] rjalths:
I hope it could be applied to all android devices!
[Samsung Galaxy Gear] Sepharite:
Not only that, hopefully it's a watch I'd feel comfortable wearing!
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] andrycarlons:
Hello.

I'm using the CM 10.2 on my LG e610. It worka very fine, bit I have a peoblem. The camera crash when I record video. Van anyone help me?

Thanks!! :thumbup:
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] TahaX:
Clear your cache and reboot your phone.
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] andrycarlons:
Already do, but don't fixbthe problem

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] TahaX:
Which ROM do you use?
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] andrycarlons:
CM 10.2

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] andrycarlons:
I resolved!!!

I have changed the video codifier from high to medium, and it works!!

(Sorry for my bad english):p
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] Webster666:
Never had any problems with video in 10.2. Have you thought about flashing rom again (it's harmless without wiping anything). Weird problem :)

Can you provide more details? This workaround isn't legit :)
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] andrycarlons:
Solved
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] Webster666:
Could you provide your solution? Or you used your workaround?
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] andrycarlons:
I simply changed the recording resolution from Hugh to medium.
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] andrycarlons:
*high
[Galaxy Note 3 Q&A, Help & Troubleshooting] ab1000uk:
Hi all

Let me start by saying what an awesome forum this is and there are some very talented people on here I have been looking at this forum for a little while now and have decided that it is time for me to bite the bullet and try and fit in and become an active part of this community.

I brought a note 3 for my wife for her birthday and must say I was so impressed I have now ordered one for myself and am currently waiting for it to arrive (be on bread and water for a few weeks now lol). The main reason I was so impressed was the features of the S-pen and do not want to lose any of its features. However, I really am not keen on the standard icons in the taskbar and the quicklaunch etc. I really prefer more colours and the hey look at me style :)

So my question: really not sure what to do and wondered what you guys thought and recommended should I root and install a theme or customise using something like wanam or I like quite the look of the BobCatRom should I go the whole hog and install this (if I do will the s-pen still function the same). and also I presume that the second I root I will trip the knox counter can you foresee this being a problem in the future.

Thanks in advance for any advice
[Galaxy Note 3 Q&A, Help & Troubleshooting] radicalisto:
Yeah it's a nice phone.. :good:

Well any ROM that is TW based and not AOSP based will still have SPen features, there's a few ROMS, Bobcat/xnote/alliance/civz/omega etc etc, it's pretty much personal choice as they vary by quite a lot - You can use a theme sure, or you can theme a custom launcher like Nova/Apex etc also.

You may need to read up on KNOX and other rooting issues, however since you are UK -- KNOX won't be an issue for you under the EU directive.
[Galaxy Note 3 Q&A, Help & Troubleshooting] ab1000uk:
thankyou for the quick reply thats really handy to know think i will probably go the custom rom route.

have used Omega rom before on s3 and s4 and found it to be very stable but am really tempted by BobCatRom but see a lot of people seem to like xnote.. decisions decisions lol

What i meant about knox by future problems can you envisage any must have apps coming out that wont install if the counter has been tripped.

Thanks again this forum really is awesome and its all down to the members
[Galaxy Note 3 Q&A, Help & Troubleshooting] Mustajab Is'haq:
Knox should not be an issue for you as you seem to not care about the warranty (right?).

Once Knox is tripped (0x1), you can't use it. Thats it. It will have no effect whatsoever on any apps or features and they will continue to work fine.

The only thing you lose after tripping Knox is your warranty and Sammy's "Business/Enterprise Security" model (aka Knox), you wont be able to set it up and create different profiles for Work and Play.

S-Pen will also work fine.
[Galaxy Note 3 Q&A, Help & Troubleshooting] ab1000uk:
Thankyou that has definitely cleared things up and help me to try and make a decision.

Just to be sure i take it rooting and putting on a TW based rom will not affect the use of the galaxy gear (I am thinking of putting Null on)
[Galaxy Note 3 Q&A, Help & Troubleshooting] radicalisto:
Won't affect the Gear no.
[Galaxy Note 3 Q&A, Help & Troubleshooting] pete4k:
I would wait with tripping knox for couple weeks and make sure the phone works good on stock first. For starters you would know then if something stops working is it because of factory issue or due to flashing, also it would make warranty repairs or exchange less of a hassle.

Also some things are impossible to undo, like knox flag or updating to KitKat.
[Galaxy Note 3 Q&A, Help & Troubleshooting] sephkateno:
Also you should really consider whether going for the latest android 4.4.2 which is by far the best version regarding performance but has some thing missing for my taste like lockscreen effects still is in it's early stages which means no heavy development has been made so far and on top of that you have to flash the rom without flashing the new bootloader if you don't wanna be stuck on 4.4.2 and the kernels available for 4.4.2. don't have over clocking capabilities...going back to 4.3 is impossible at this time learnd it the hard way also if you have second thoughts regarding the warranty I have heard rumors that people who need their phone getting fixed just damage it on purpose so it won't boot not even download mode so Samsung can't detect whether it has been tempered with or not so they change your phone's board how they do that is still unclear to me.
[Galaxy Note 3 Themes and Apps] meawww:
Simple and easy open the file build.prop inside /system then add a new line of code and put this.

#Nexus Navigation

qemu.hw.mainkeys=0

Reboot and enjoy..
[Galaxy Note 3 Themes and Apps] antt00:
How does it look at the samsung contacts and message screen? Is there still an additional row on top.
[Galaxy Note 3 Themes and Apps] meawww:
This thngy needs alot of fix for sammy device some are not in place or covering somethin
[Galaxy Note 3 Themes and Apps] antt00:
Yeah i tried this before on tw rom on different samsung device and end up hating it especially contacts, messages and the camera. :(
[JASJAR, XDA Exec, MDA Pro General] alfredtv:
I think the Universal is bigger but am not sure as to how much.

I live in the states so the Universal is not sold in stores here and I wanted to know if any of you Universal owners had the Blue Angel still and would be willing to post a few side by side comparisons.

THanks
[HTC Butterfly S] FYL21:
After the 4.3 update, the HTC Butterfly s also the real-time audio of a slow-motion video so you can hear it when the video is played at real-time speed on the phone. Does anybody know how I can access this audio file?

When I import the slow-mo video file into Sony Vegas there is nothing else other than the video in slow motion. (From what I recall, you need to download some Quicktime codecs to import the videos into Vegas, they aren't very good and lag on my old computer with the HD video)
[Verizon Samsung Galaxy S III] Gibscreen:
Anyone know of any AOSP-type roms that support USB OTG?

I've been running Cyanogen roms for a while and it doesn't support USB OTG (currently running cm11 nightlies). I've heard it has something to do with the usb connector on the phone not providing power on the cm rom or kernel. Wife's phone is still on TW and otg works every time. I've tried a couple of different kernels with cm11 but no joy.

Anyone have any luck on any AOSP roms? Thanks!
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] subrban:
My rom is slimbean, and i need to restsrt the device every time i add tones to notification folser to be visible in the ring tone selecter, is ther any way beter than this ?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
May be media is not being scanned added. Check if this app named Rescan Media ROOT if of any use to you. It will do as its name says.. :)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] subrban:
I already installed it, but it seems useless , I operate as it says , did this app worked with you before ?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
Yes.. it has worked for me in the past when new photos added were not shown in the gallery and after running this, it used to get displayed.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] subrban:
It could be working on photos only, really I am suffering with this issue
[Verizon HTC Droid Incredible 4G LTE] kimba99:
yesterday when i tried to update the radio on my dinc4g (including rcdata=radio_data and rpm=radio-powermanagement, but somehow i thought it should be okay to also include boot.img (as this is reversible by TWRP recovery and tz=trusted_zone!!) ... before i compared to similar (but supposedly reversible!! partial firmware updates with their matching firmware downgrades ... all only suggested to remove at least hboot.img and stock-recovery if included) ... there was no new hboot in the new 2014 OTA firmware and stock-recovery (along with the 2ndary bootloaders) i had removed

everything also flashed just fine, no write failed, just all "OK / OKAY" and done, BUT ... after fastboot reboot ... the phone didn't come up anymore and is now STUCK on "QHSUSB_DLOAD" mode => bricked! damn ...

unfortunately the "regular" HTC unbrick tools do not support the Dinc4G ... now i'm hunting for solutions to recover my daily driver >.> already searched xda and elsewhere: tried at least brick-detect from HTC unbrick tools, but they are mainly looking if linux registers the "qhsusb_dload" _and_ adds the partitions of the phone to the running linux ... but mine only registers the serial-usb terminal from qhsusb_dload, but _not_ the phones partition(s) >_>

only thing i found is that the qualcomm QPST (oem preprogramming!) tool sees this device (albeit as said in download-mode only) and offers to flash certain things, but i do not have a QPST backup-file for the Dinc4G to compare to and/or use that to revive my phone.

i'm therefore looking for someone with a working (and at best similarly S-OFF'ed dinc4g phone to create such a QPST backup. :confused:

any help is highly welcome :(:rolleyes:
[Verizon HTC Droid Incredible 4G LTE] kimba99:
further hunting the web and lots of reading here on XDA (for similarly bricked mobiles ... from almost every manufacturer!) ... the easiest (albeit not always working) idea comes down to the following:

getting a direct dump from the eMMC memory of a running/working system in a known good state:

Is anyone willing to dump the partition table/bootloader part from their working Dinc4G with FW 2.17.605.2 (the regular ICS4.0.4 without the most current 2014 OTA) for me?... best would be from an S-OFF device like mine i assume, just to make sure it matches my situation, but S-ON should also work, as it's just for recovery-boot via microSD (if it work's on a Dinc4G)

in a busybox or other terminal as root (aka: su mode)

dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1048576 count=256

this will dump the first 128MB of your own eMMC (internal memory) including your current and working partition table and some of the boot partitions

then just zip that "backup.bin" (which should greatly reduce its size!) ... uploaded it somewhere and forward me the link ...

thanks for your help!!! :fingers-crossed:
[Verizon HTC Droid Incredible 4G LTE] kimba99:
thanks to j13smiley, who provided me with a eMMC dump from his Dinc4G ... i couldn't get my bricked fireball so far to failsafe-boot from the microSD with the dump he send me:

but I was able to reconstruct the filesystem-structure quite somewhat further than mdmower here http://xdaforums.com/showthread.php?t=2077608&page=7 with the descriptive help from this thread http://xdaforums.com/showthread.php?t=1959445 using the HOXL as a template for partition types on HTC devices

here is what i've come up with so far (analysing the /dev/mmcblk0 dump from j13smiley:

omitting empty partition (33)
Partition 33 is deleted

Disk /dev/mmcblk0: 15.9 GB, 15931539456 bytes =!size is wrong, due to using a 16GB uSD to dump the backup!=
1 heads, 16 sectors/track, 1944768 cylinders, total 31116288 sectors =!same as above!=
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System	QCname
/dev/mmcblk0p1 * 1 256 128 4d QNX4.x	SBL1(cfg_data)
/dev/mmcblk0p2 257 768 256 51 OnTrack DM6 Aux1	SBL2
/dev/mmcblk0p3 769 262110 130671 5d Unknown
/dev/mmcblk0p4 262111 15269886 7503888 5 Extended	EXT
/dev/mmcblk0p5 262112 262143 16 5a Unknown	(CID+IMEI)
/dev/mmcblk0p6 262145 262656 256 73 Unknown
/dev/mmcblk0p7 262658 293812 15577+ 5b Unknown
/dev/mmcblk0p8 293814 294325 256 5c Priam Edisk
/dev/mmcblk0p9 294327 296374 1024 45 Unknown	SBL3(qscbl)
/dev/mmcblk0p10 296376 296887 256 47 Unknown	RPM(appsbl)
/dev/mmcblk0p11 296889 300984 2048 46 Unknown	TZ(oemsbl)
/dev/mmcblk0p12 300986 303033 1024 4c Unknown	HBOOT(aboot/fota)
/dev/mmcblk0p13 303035 303098 32 0 Empty
/dev/mmcblk0p14 303100 315387 6144 34 Unknown	SPLASH
/dev/mmcblk0p15 315389 317436 1024 36 Unknown
/dev/mmcblk0p16 317438 319485 1024 0 Empty	(dsps)
/dev/mmcblk0p17 319487 411646 46080 77 Unknown	(radio)
/dev/mmcblk0p18 411648 432127 10240 7a Unknown	(adsp/q6)
/dev/mmcblk0p19 432129 442368 5120 0 Empty	(wcnss)
/dev/mmcblk0p20 442370 458750 8190+ 74 Unknown	(radio_config)
/dev/mmcblk0p21 458752 491519 16384 48 Unknown	BOOT(apps)
/dev/mmcblk0p22 491521 524287 16383+ 71 Unknown	(recovery)
/dev/mmcblk0p23 524289 526333 1022+ 76 Unknown	(misc)
/dev/mmcblk0p24 526335 534526 4096 4a Unknown	MODEMST1
/dev/mmcblk0p25 534528 542719 4096 4b Unknown	MODEMST2
/dev/mmcblk0p26 542721 583680 20480 19 Unknown	(devlog)
/dev/mmcblk0p27 583682 583689 4 0 Empty
/dev/mmcblk0p28 583691 584202 256 23 Unknown	(pdata)
/dev/mmcblk0p29 584204 584235 16 0 Empty
/dev/mmcblk0p30 584237 586797 1280+ 0 Empty	(local)
/dev/mmcblk0p31 586799 586926 64 0 Empty
/dev/mmcblk0p32 586928 786431 99752 0 Empty	=!possibly wrong start/end&blocks!=
/dev/mmcblk0p33 83 EXT4	(system)
/dev/mmcblk0p34 83 EXT4	(cache)
/dev/mmcblk0p35 83 EXT4	(userdata)
/dev/mmcblk0p36 c FAT32(LBA)	(fat)

not fully complete yet, but still much further improved over the previous partition layout details
[Verizon HTC Droid Incredible 4G LTE] mutterc:
Anything I can do to help?

I have qdload.pl, a MPRG8960.hex and 8960_msimage.mbn from some XDA thread or other (they don't seem to work though). My fireball is functional, rooted but S-ON (I got it early and htcdev still allowed me to unlock the bootloader). It does have the OTA update though.

I'm interested because my wife's fireball is stuck in QDL mode. She's migrated to a Rezound so it's not urgent.

I suspect it got that way because I used DirtyRacun S-OFF, then went to flash the OTA update. I suspect DR modifies hboot or one of the sbl's, and when I flashed the OTA it might have put me back S-ON.

(Got motivated to try to root her phone because even though it wasn't rooted, it kept trying and failing to download the OTA, killing the battery).

The DR website has an RUU.zip that has images of all the sbl's and an hboot, so working images isn't a problem, but getting them on there is.
[Verizon HTC Droid Incredible 4G LTE] kimba99:
if you don't mind: plz attach your MPRG8960.hex and 8960_msimage.mbn files here ... so i could compare against those i have.

and well, if you are still S-ON _and_ the OTA-2014 is already applied then you are "out of luck" ... at least for the next couple of weeks or even months. no S-OFF method known for OTA-2014 applied fireballs!

afaik: DR "only" uses security holes in the firmware from 2.17.605.2 (from regular ICS4.0.4 RUU) to remove S-ON/write S-OFF flag ... and then add the engineering hboot of fireball (albeit modified) ... in the general section, several users with S-OFF (before the OTA-2014!) applied now the firmware from the OTA-2014 separately and confirmed that S-OFF stayed even after the OTA and since it doesn't include any new hboot, they still have their previous one

likewise, there are different qhsusb_dload modes, depending on WHEN they kicked in... in the sense of which stage fails (attaching your qdload-fireball to a linux system, there are at least 2 distinct possibilities: a) only qdload-mode or b) qdload-mode AND enumerating partitions ... the latter one is fairly easy to cure whereas the former (like mine) is much harder to come by unfortunately >_<

they have a RUU.zip (for 2.17.605.2) and it has the firmware bit isolated and included, but that _won't help you at all_ with a bricked phone as you need a predefined partition-layout and -structure files _and_ then manage to get your brick to accept and all load those start-up settings at once. the RUU has only the files, but _not_ their structure!

i managed to already recreate most of the partition-structure of a fireball with the help from some other xda-members, but _still_ that wasn't enough for those software-tools i tried!! maybe my MPRG8960.hex isn't correct (193.692byte / md5sum: 2534fd61ebc7c8bdd9fe0dbb90c77fb0) ... i decided to buy another 2nd-hand fireball (hopefully it should still come W/O the OTA-2014 ;)) ... to create/dump what is on there to resurrect my bricked fireball, yet even that is still unclear if it will work. (need to wait a few more weeks until the other fireball arrives here: intl shipping & customs take quite a while unfortunately)
[Verizon HTC Droid Incredible 4G LTE] dcooterfrog:
kimba.

first thanks for your help with the ota foirmare in theother tread. second HOW CAN I HELP YOU.

although I am on cm11 and have the firmware updated I think that is where you want to get to.

i am reasonable good with unix and adb with directions I am sure I can get anything you need off of my phone. let me know.
[Verizon HTC Droid Incredible 4G LTE] mutterc:
Attached as tar.gz, looks like from your size/md5sums that my MPRG8960.hex is the same.

Mine has only one device (qcserial) showing up in lsusb, which means it's not enumerating partitions, right? Which if I'm still S-OFF means one of the SBLs is scrod, right?
[Verizon HTC Droid Incredible 4G LTE] kimba99:
don't just check lsusb ;) ... try the output of

dmesg | tail

BEFORE ... you attach the bricked fireball to your linux system & then right after attaching (about 10sec later or so should be enough) check again with the SAME

dmesg | tail

if it only attaches a "qualcomm usb-2-serial device on tty*" then you're in bad luck (as me) currently ... but if dmesg shows and lists some new "/dev/sdb1 /dev/sdb2 /dev/sdb3" devices and so on ... you can fairly easy fix it (at least as _now_ we/i had extracted or better said reconstructed the partition-layout and thereby we could flash any borked or unmatching partition directly).

as for S-OFF, that _should_ have nothing to do with the reason for the brick as there are already fellows here with properly updated OTA2014 firmware _working_ with properly retained S-OFF ... and secondly, it doesn't have to be one of your SBL2*'s as it could also be TZ or RPM not matching one another (as far as I understood the SecureBoot3.0-chain) ... so it depends WHICH file you (tried to) flash (and how) that leaded to your brick.

EDIT: as for your attached MSM8960-files ... identical to mine and thereby unfortunately NOT working (afaik) for recovery of a fireball T_T
[Verizon HTC Droid Incredible 4G LTE] Ngaihte04.16:
any improvements on this problem? I'm having the same problem with my phone so please let me know if you find a way to fix this problem....
[Verizon HTC Droid Incredible 4G LTE] kimba99:
bought another Dinc4G ... in replacement for my bricked one. in my trail to revive my bricked one (and/or having another Dinc4g at least to use regularly with a ROM of my choice again)

after requested, the seller _confirmed_ that the 2014-OTA has __not__ yet been applied and the phone still runs fine on 2.17.605.2 ... and "guess what" i received yesterday in my mail:

his Dinc4G _WITH_ the 2014-OTA applied & of course it's stock/locked/s-on!!! DAMN IT!!!
[Verizon HTC Droid Incredible 4G LTE] therreid:
That sucks. Having this phone unrooted with the 2014 update is a little like being Sandra Bullock in the film Gravity. I sure hope there's someone smarter than me working on root for this thing with the 2014 update.
[Verizon HTC Droid Incredible 4G LTE] kimba99:
not many users (or even devs!) left on our Dinc4G .... pretty unfortunate

i mean temp-root still work's (apparently) on the 2014-OTA ... and the hboot didn't change at all (it's still 1.15) ... i assume one needs to find a way to perm-root the new 2.19.605.2 stock-rom first & from there try the same (or at least similar) "s-off" attack to the 1.15-hboot as previously. it's just that the devs of the prev s-off methods don't tell WHERE or HOW they obtained write-permission to set the s-off flag

still: i managed to trigger the "tampered"-flag above my "*locked*"-flag ... *lol*
[Verizon HTC Droid Incredible 4G LTE] junkmail9:
With the news of the new s-off method for the latest OTA, I was wondering if you were able to fix your phone. Looks like the answer is no, buuuut, you now have s-off with the latest OTA! :good: !
[Verizon HTC Droid Incredible 4G LTE] kimba99:
unfortunately not (yet?) ... but at least, i'm near exactly where i was left on the new phone! real incredible that i could restore my nandroid from the borked phone directly to the new one (okay, after i figured out i need to rename the TWRP-backup folder to match ne new ADB-ID of the phone :p ... only missing a bunch of photos, that i didn't backup prior to the brick.

i'll try again later, but the brick still doesn't accept to be flashed either way by QPST as it says it is missing "its magical token" (whatever that means, but there are several posts about that specific QPST issue with qhsusb_dload bricked phones here on xda) :mad:
[Verizon HTC Droid Incredible 4G LTE] kimba99:
finally solved ... but that SURE wasn't for the faint hearted => poor fireball had to strip completely (disassambled) ... JTAG pins are ___under___ the IMEI-battery sticker even (so that had to be removed as well) ... before the "solder party" could begin.

and then thanks to _huzein_ from "gsm-europe" (who provided the RIFF-box and soldering for some smaller money) ... and the famous _legija_ ... the developer of the RIFF-box himself! (who guided us and reflashed my brick via a remote RIFF-session) ... flashing a bricked "HTC fireball" via JTAG for the very FIRST time!! we used the dump from jsmiley13 (so thanks to him again for providing me with the dump) ... after that we needed to reflash the ENG-HBOOT (via RIFF JTAG interface again) though as it had the 1.15.1111 but showed S-OFF _locked_ ?!

now it's back alive ... after 2hrs of remote debugging, remote-flashing etc ... hopefully now, legija can implement a NEW ressurrector.dll for fireball (for the 1ST TIME) and add it as a by now newly supported device on his RIFF-box!

attached below is a small "photo-story" ... for those who are interested *lol* ... and NO it's not an optical illusion, the panels definitely appear to have some slightly different color-hue (esp the green looks not the same)
[Verizon HTC Droid Incredible 4G LTE] dmbtech:
Looks like I am also having the same issue. Did an exchange remote wipe and came back to my phone completely bricked, Q Download mode. I am guessing the only way is to JTAG the device? Is there any other possibilities? I have qpst, and hpst etc. What is the hex and mbn image used for?