yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] _Dennis_:
Change homescreen only. Can't have live wallpaper on lockscreen and have the light or ripples. Same thing on Note2 with ripple

I think it has to do with performance and possibly look. Samsung can't conttol what the interaction would look like between the live wallpaper and the ripple/light beam.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] MentalToast:
Kind of the opposite of what my isue is

it defaults TO the light effect and then locks it out from trying anything else. so I have live wallpaper and am forced into the light effect also
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] tanvir108115:
whille recompiling systemui.apk it gives this error...how to fix it?

[*] C:\AutoAPKTool\_INPUT_APK\SystemUI
recompiling C:\AutoAPKTool\_INPUT_APK\SystemUI...
I: Smaling...
I: Building resources...
I: Building apk file...
The system cannot find the drive specified.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] sandy7:
It has recompiled properly I dont see sany error in this
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] tanvir108115:
The system cannot find the drive specified. isn't this a error?? and when I decompiled an apk and recompiled it without editing it didn't work
[One (M7) Q&A, Help & Troubleshooting] arjunanand1:
I've been using MX player to watch my videos on the One, and I've got some issues with it. The video occassionally freezes (audio continues) and I have to either wait a couple of seconds for it to catch up, or I have to rewind/forward to get it moving again. This happens on every single video I've tried (at least ones that I've copied over via USB) and I can't seem to figure it out. Already tried using the custom ARM7 neon codec too as suggested from MXplayer but it didn't make a difference. HW+, or software renderer does not make a difference either. Anybody else having these problems ? If so, were you able to fix it, or find a workaround ?

Forgot to add that I'm still using the stock ROM.
[One (M7) Q&A, Help & Troubleshooting] ArmedandDangerous:
Try uninstalling the codec pack, you don't need it unless MX Player specifically asks for it. I can't say I've had video go out of sync before though.
[One (M7) Q&A, Help & Troubleshooting] arjunanand1:
Thanks! I installed it just yesterday to see if it makes any difference. Until then I was using the default codec that comes with the player. I'm using the free version of MX player if that makes any difference.
[One (M7) Q&A, Help & Troubleshooting] arjunanand1:
Bump
[One (M7) Q&A, Help & Troubleshooting] arjunanand1:
No one else having this problem ? :(
[One (M7) Q&A, Help & Troubleshooting] ArmedandDangerous:
Maybe try a factory rest and see if that fixes it? :)
[One (M7) Q&A, Help & Troubleshooting] dayze0:
Yep - also have this problem sometimes - not tried uninstalling the codecs yet so will give that a try.

You could try VLC Player for android - works great for me with no lag or O/S problems.

Im Rooted, Tampered and running Android Revolution 9.2, with custom 1.29 Audio files(tfa) and PureXaudio 4.0
[One (M7) Q&A, Help & Troubleshooting] arjunanand1:
Thanks!!!! I tried VLC and it plays videos just fine. :D
[One (M7) Q&A, Help & Troubleshooting] dayze0:
No probs buddy = glad to help
[Galaxy S II Q&A, Help & Troubleshooting] galaxys9:
Hi everyone,

So I just bought my first smartphone ever and it's samsung galaxy s2 4G from Virgin Mobile. This is also my first experience with Android. So I am just looking for tips from experienced users to get the most out of it.
[Galaxy S II Q&A, Help & Troubleshooting] sgtkeroro:
It always starts by rooting it and flashing with a custom rom :good:
[Galaxy S II Q&A, Help & Troubleshooting] Donnie Sins:
Tips... What do you want to know? Because this question isn't very specific at all and can't be answered...
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
Search/read/learn (the first two don't necessarily have to be done in that order). Asking people to regurgitate ten steps on how to do a specific thing will teach you nothing & won't be any help to you if/when the SHTF.

If you read/learn/understand 'why' for yourself & how things work, you're more likely to be able to handle anything that comes up.
[Galaxy S II Q&A, Help & Troubleshooting] galaxys9:
I am not looking for steps....I just want to know what can I do with a smartphone..
[Galaxy S II Q&A, Help & Troubleshooting] carranty:
+1
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
If you do what I suggested you'll learn what you can do with a smartphone.
[Galaxy S II Q&A, Help & Troubleshooting] TwitchyEye:
You can do almost everything you could with a computer, and a bunch of stuff your computer could never do.

The play store has apps for whatever you want to do. Poke around in there and see.

This place is for Modding your phone's firmware and changing it's look/feel/functionality. So it may be a little much.

If you're looking for basics this would be the last place to look. People will mock you. Nyah!
[Galaxy S II Q&A, Help & Troubleshooting] noim:
Good u got a smartphone!!!

If this is really ur 1st smartphone ever??

Then take things a bit slow.learn the basics of the software. Explore the app store. Surf ur way thru settings and options and see what each one does.start rummaging thru ur smart phone...

If u don't get a specific feature or cant understand something? Then use Google? Watch YouTube videos of how it works and happens.... Even then u can't understand, that's the point when u start posting ur Q/A threads in XDA..;)

And u asked what u can do with a Android device? Well let me tell u can do similarly the exact things you can do with a PC... Slowly you will understand the usefulness & the power of a smartphone.

This is my suggestion. I hope u consider doing those things..

sent from my Galaxy S II
[Galaxy S II Q&A, Help & Troubleshooting] immortalneo:
U can create memes on ur smartphone! ;)

Like this:

View attachment 1980325

:D

"To err is human, to forgive is divine"

Sent from my SGS II
[Android Q&A, Help & Troubleshooting] boyz99:
where the path line in the xml framework-res.apk to change the colour,,
[Ouya Android Development] tylerwhall:
I started looking into bootloader-level recovery tonight before messing with the file system too much and potentially getting into a bad state. I couldn't find this information anywhere else.

UART pinout

J3 - 4 pin unpopulated header on the front of the board near the LED

Pin 1: 3.3v

Pin 2: TX

Pin 3: RX

Pin 4: GND

Bootloader and kernel console output comes out this port, but android doesn't start a shell.

Bootloader strap

On the back of the board in the center, there is an unpopulated button (U33). When jumped while the power button is pressed, this appears to put the bootloader into USB recovery mode. It enumerates with an nvidia vendor id. Presumably nvflash or tegrarcm could be used to unbrick the device.

I haven't done anything with the bootloader recovery since I haven't yet made a backup. I'm not sure how much of the functionality is allowed given the state of the production fuse, but I would think we could use this to at least get back to a stock state.
[Ouya Android Development] embeem:
I had posted pretty much the same thing a few hours earlier over on the ouya forums - https://forums.ouya.tv/discussion/comment/11742/#Comment_11742

The good news about the bootloader is that none of the android partitions have any sort of signature, which means that the bootloader is effectively "unlocked", you can even do a "fastboot boot". The bad news is that there doesn't seem to be any sort of hotkey to enter the bootloader or recovery mode, although I did find that you could usually get into recovery with the sysrq, just press alt-sysrq-i a few times at bootup to crash the processes spawned by init and eventually it will reboot into recovery -- obviously this won't work if your ouya doesn't even boot that far, so be careful.

The button at u33 does get you into nvflash mode, but from what I can tell it's entirely useless since every command will return a 0x4; we'll need the secure boot key to actually get this working.

As far as backups, the OTA download contains an entire copy of the system and boot partitions, this can be flashed from recovery using adb sideload; rayman has posted a link to all the known OTA downloads over on this thread - http://xdaforums.com/showthread.php?t=2266629
[Ouya Android Development] rayman:
Sadly, no. The way nvidia does security means that you need to know the Secure Boot key (if set - but it is set on ouya) to even be able to communicate with the device through APX/nvflash.

As embeem mentions, it will return 0x4, which essentially means "go away, i don't know you" after which it goes into an almost turned off state where it refuses to do anything but restart. The SBK is an AES-128 key so it's essentially impossible (inpractical) to bruteforce it.
[Ouya Android Development] wolf849:
So what was the trick that you used/developed to bypass the encryption on TF101 B80+ / TF201 / TF701 ? As far as I know their bootloaders also required SBK, nevertheless you published tool that works with them even though SBK remain unknown, or am I wrong and misread something?

Cheers
[Ouya Android Development] rayman:
Black magic.
[Ouya Android Development] invisiblek:
Well, not much capable in nvflash mode, can't get anything to work properly.

UART lets me see it boot up, and fail miserably. Sadly, nothing doing there either. Nothing I send to it seems to affect it.

Back story: I broke init. The sysrq trick doesn't work unless you're getting to init.

Boot log via UART:

http://pastebin.com/ENQYQbTS

It still responds to sysrq, but nothing I'm doing seems to do much. I can dump the memory, crash the system, reboot it, shut it down, all kinds of things. Here's the HELP for sysrq:

[ 66.672046] SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) thaw-filesystems(J) show-backtrace-all-active-cpus(L) show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) Sync show-task-states(T) Unmount show-blocked-tasks(W) dump-ftrace-buffer(Z)

an easier list of sysrq commands:

alt + sysrq + [0-9] - set log level (doesn't seem to work)
alt + sysrq + B - reboot
alt + sysrq + C - crash
alt + sysrq + E - terminate-all-tasks
alt + sysrq + F - memory-full-oom
alt + sysrq + I - kill-all-tasks
alt + sysrq + J - thaw-filesystems
alt + sysrq + L - show-backtrace-all-active-cpus
alt + sysrq + M - show-memory-usage
alt + sysrq + N - nice-all-RT-tasks
alt + sysrq + O - poweroff
alt + sysrq + P - show-registers
alt + sysrq + Q - show-all-timers
alt + sysrq + S - sync
alt + sysrq + T - show-task-states
alt + sysrq + U - unmount
alt + sysrq + W - show-blocked-tasks
alt + sysrq + Z - dump-ftrace-buffer

Some more detailed information on what these are: http://en.wikipedia.org/wiki/Magic_SysRq_key

Open to ideas!
[Ouya Android Development] DivinityCycle:
This reminds me of the old Droid X I had years back, which had a locked bootloader.

Because of this, there had to be a special "boot to recovery" boot strapper installed onto the system.

We have full RW access to the Ouya's filesystem and software, so it would seem like the first thing the community should do is develop some sort of "successfully booted" flagging to make the system try to automatically drop into CWM in the event that it looks like the OS is broken.

Couldn't such a thing live in the boot.img, and thus be available even if some silly person formats their /system partition? (This has happened already, and so the guy pretty much bricked his Ouya)
[Ouya Android Development] invisiblek:
My plan is to develop a sysrq key to write the appropriate bit(s) to SCRATCH0 and reboot. This would allow us to get into recovery via a simple keystroke. I've actually got it written but need to test it. Testing it would not be dangerous as it would normally boot the stock kernel/init.

Next week when I'm home I'll try to find a tester since I cannot test it (can't write anything to my mmcblk0)

This shouldn't be dangerous to test.
[Ouya Android Development] nchantmnt:
Any news on uart? I guess I bricked my ouya.

I was testing my custom kernel, did forget to use fastboot boot instead of flash and now have nothing but a black screen. My linux machine doesn't recognize my ouya and I can't go to recovery. So at least knowing what is causing the issue would be helpful.

Do you mind giving me a short intro on uart?

I guess I need a usb/uart adapter? If yes, which one should I get?

Thanks in advance

Gesendet von meinem HTC One X+ mit Tapatalk 2
[Ouya Android Development] nchantmnt:
anyone already saw this: http://xdaforums.com/showthread.php?t=2071626

did only have time to skimm it but might be useful to people with still working devices

aim is to get the sbk which should be - if i have understood it the right way - unique for each device as long as the company didn't burn in a fix sbk.

so maybe this will help us to save people from further bricks...as long as nvflash is usable via usb
[Ouya Android Development] dexter84:
Has anyone tested in on ouya ?
[Ouya Android Development] cronikman84:
Not yet i think...i know i won't be testing it on my OUYA no time soon, i don't feel like having my box BRICKED like nchantmnt does, screw this, it's too early to test this :rolleyes: , i wont even risk it, i dont feel like buying another OUYA for testing this...
[Ouya Android Development] nchantmnt:
Hey... no pain no gain :cool:

Gesendet von meinem HTC One X+ mit Tapatalk 2
[Ouya Android Development] zondajag:
I have an idea for a small usb device that could force the ouya into recovery mode using the keyboard combination mentioned below:

http://ouyabrew.com/how-to-put-ouya-in-recovery-mode/

Essentially my idea is to have a little usb circuit board with a micro controller that is smart enough to simulate a keyboard periodically sending the specified keypresses. When the ouya goes into recovery you would just yank out the dongle. I don't have any background technical knowledge in this stuff but this sounds like something Ben Heck could whip up (he is a legend).

Update: Looks like these are already a thing! this looks promising:

http://www.irongeek.com/i.php?page=...ke-dongle#So,_why_would_a_pen-tester_want_one
[Ouya Android Development] cronikman84:
this is a sweet idea, i wasn't aware of a programmable HID USB keystroke dongle...This would make things easier...i hope someone makes something out of this, this will solve the booting into recovery bigtime!!! :cool:
[Ouya Android Development] hecksagon:
This would only work if the stock kernal is installed and the recovery partition is intact. If you lose you recovery partition you won't be able to boot recovery and get adb working, and if the kernel isn't the stock kernel the keyboard combo won't work.
[Ouya Android Development] nchantmnt:
Also no use for broken init

Gesendet von meinem HTC One X+ mit Tapatalk 2
[Ouya Android Development] dexter84:
I don't think that this necessarily means bricking your device.

You could always try fastboot boot patched kernel and then try reading fuse values.

I was playing with this method to run Debian:

http://tuomas.kulve.fi/blog/2013/09/12/debian-on-ouya-all-systems-go/

It is an easy procedure and I've got it running. Unfortunately my USB hub is not working correctly with ouya (it's passive so voltage on USB can be low), so I didnt login into it, but you could use this method to try to extract sbk keys.
[Ouya Android Development] suruceanu.nick:
nvflash

How About this : http://xdaforums.com/showthread.php?t=2455927 ????
[Ouya Android Development] nchantmnt:
we first need to know if we do have a "masker sbk" or a device specific sbk.

for device-specific sbk this methode should work but only with a wheelie-enabled recovery for our device

don't try to flash any other recovery to your device or you're in danger of bricking it.

if you have access to the source and can add the required option for generating blob files to a working recovery image, then this should work for device specific sbks.

then you can use any uart-adapter/raspberry pi/etc. to connect to your device and make backup and flash partitions.

(NOTE: DO NOT USE YOUR PCS SERIAL OUTPUT - IT MIGHT DAMAGE YOUR DEVICE AND YOUR PC AS WELL... OH AND IT WILL NOT WORK)

if we do have any kind of masker-sbk i can only talk in theory:

you normally should be able to read out sbk from running system but this is of course prevented (in most cases by some kerner config).

i don't know exactly by what methode and what files exactly to change but I have read somewhere that you could make a custom kernel which doens't prevent read out of sbk. then fastboot boot boot.img, read out sbk and sould be good to go.

but praxis might be a good bit harde ;)

... or maybe blob mehtode might work.

got important exams tomorrow but if anyone could send me link to wheelie-enabled n7 recovery i might take a look the next days.

maybe recovery-devs could make something out of it even earlier ;)
[General Questions and Answers] Dexptchang:
Hi Guys,

I have an S Duos. It's stuck on the logo & has the warning triangle at startup. Sofar I have had no luck with Odin. It wont go into recovery mode for me to load ROM of the SD card.

But I really just need someone to direct me to the proper forum.

Dex
[General Questions and Answers] thrgk:
Hey guys on my note 2 im getting texts from 6250 and its very annoying. Im on clean rom 4.9 ace and dont even have backup plus in settings so no idea why its doibg it. I never got them on jelly brans rom though. I tried going to my vzw accoubt to remove emails but wasnt sure how. If there is a step by step guide on where to go in my vzw accoubt or another way please let me know. Should I call vzw and tell them to remove backup on my line only?

Thanks
[MDA II, XDA II, 2060 ROM Development] sosiska:
Hi there,

I tried to update my device rom from 1.60.00 to 1.60.50,

my device is not responding after the update, on the screen it displays the word "Serial" on the upper side of the screeen and "v 1.06" on the bottom.

please help me :cry:
[MDA II, XDA II, 2060 ROM Development] edsub:
No worries, youre in the bootloader.

Just disconnect (take out of cradle)

Go into bootloader (if not allready there: power / reset / d-pad)

Re-connect (cradle)

Restart upgrade

Wait
[MDA II, XDA II, 2060 ROM Development] sosiska:
Thanks!

I accept the ERROR 100
[RAZR HD Q&A, Help & Troubleshooting] Nero's:
When trying to flash I keep getting this message attatched. Not sure what I am doing and can't seem to Google my way out of it. Any help is much appreciated
[RAZR HD Q&A, Help & Troubleshooting] Nero's:
solution

http://xdaforums.com/showthread.php?t=1515361&page=2

post # 13 worked for this flasher
[Sprint HTC One (M7)] treIII:
How can I remove the GPS icon? I know I can with omj mod pack. But I would like to remove just the GPS icon without any of the other mods. Thanks to anyone who can possibly help

Sent from my HTCONE using Xparent Blue Tapatalk 2
[Sprint HTC One (M7)] jazz995756:
If you are rooted you can decompile your systemui.apk and delete the GPS icon from within but I think that will leave a space there when its on
[Sprint HTC One (M7)] BrianBaker:
It does leave a space.. I'm also looking for the icon to be removed along with the headphones icon.. I believe is a smali edit.
[T-Mobile Samsung Galaxy S II SGH-T989] Phateless:
I had an ODIN flash go awry and now I'm pretty bricked, can't get into download mode. I downloaded and installed qpst but I clearly have no freaking idea how to use it.

Can someone help me recover?

Thanks!
[T-Mobile Samsung Galaxy S II SGH-T989] Phateless:
Bumpy wumpy.
[T-Mobile Samsung Galaxy S II SGH-T989] thakrew317:
Ur pretty much bricked and ready for jtag if ur drivers are reading that
[HTC EVO 3D] boxchild23:
I was using a jellybean rom (liquidsmooth rom) on my htc evo 3d gsm s-off unlocked. Now when I try to revert to a sense 4.1 rom i can't. I tried to flash viper3d and sensai and i get the same message when trying to flash via aroma installer. "Checking /system partition" and it hangs there. I also tried to flash butteredtoast kernel and I got this message when I rebooted into recovery after the flash "there was a problem with the update, your previous boot partition will remain untouched". I can flash sense 3.6 roms though. Does anyone know whats going on or how to fix it?
[HTC EVO 3D] Taimou:
Just wait. It could take 30 minutes to check all partitions before install.
[HTC EVO 3D] boxchild23:
yep it worked

Ya it took a really long time but worked in the end. thanks for the help!
[T-Mobile, Samsung Galaxy SIII] nicefella:
Hey guys,

I have a problem with all AOSP ROMs. I simply install the ROM and with no internet/no apps/no nothing and I lose like 30% overnight :/ On the otherhand, any TW based ROM and I lose like ~11% IF THAT...

I was running CM10 on my S3 and I didn't see any problems but all 10.1 based roms are killing me. I despise TW lol and I much rather stay on AOSP

I mean, I didn't post BBS since I don't even have anything installed or nothing

Any solutions? I was fine on CM10 based roms but ...:rolleyes:
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
BetterBatteryStats. Let us see them.
[T-Mobile, Samsung Galaxy SIII] chrisram88:
I second this
[T-Mobile, Samsung Galaxy SIII] wardoc22:
Or install nova launcher :o
[Galaxy Note II Q&A, Help & Troubleshooting] boodies:
I read on a couple of different blogs that movie mode is suppose to be the most accurate. Does anyone else feel that that mode is waaaaaaaaay desaturated compared to standard? I've been using standard but wow.. what is your take on it guys. Is that really how other screens lcd screens look like?
[Galaxy Note II Q&A, Help & Troubleshooting] tuxonhtc:
Standard is terribly over saturated. Movie is a tad under saturated. Natural is much closer IMO.

If you want perfect calibration - use Perseus kernel :)
[Galaxy Note II Q&A, Help & Troubleshooting] outrun86:
Honestly I prefer a bit of saturation instead of the washed-out-like colours of the natural profile, even if the latter it's closer to reality...

However, I like to change it sometimes.
[Galaxy Note II Q&A, Help & Troubleshooting] tuxonhtc:
The only time when it's useful is while watching some videos. And still I hate it - since oversaturation means significant loss of detail. Icons look blurry and make me want to gouge my eyes out. Ugh.
[Galaxy Note II Q&A, Help & Troubleshooting] Simone:
Psychological. Use what suites your interest. Period. :angel:
[Galaxy Note II Q&A, Help & Troubleshooting] dazza7111:
I use natural. Used to it now lol
[Galaxy Note II Q&A, Help & Troubleshooting] Zanr Zij:
I need another mode a bit higher saturate than Natural but overall I'm ok with Natural mode.

Sent from my GT-N7100
[Galaxy Note II Q&A, Help & Troubleshooting] boodies:
Yeah, i've been using natural now. Normal is definitely over saturated. I wonder what the pro mode for the GS4 is close to.
[Galaxy Note II Q&A, Help & Troubleshooting] tuxonhtc:
Try Perseus, again. Can't recommend it enough if you, like me, prefer accurate color calibration.
[Galaxy Note II Q&A, Help & Troubleshooting] Elsydeon:
Using Natural myself, I think it's the most realistic, but it's still slightly undersaturated compared to a good LCD. I agree that Movie is too desaturated and washed out, while Standard leans way too much towards typical AMOLED cartoony oversaturation. I literally don't think I would've kept my Note 2 if it were locked at the Standard or Dynamic settings, they both look ridiculous.
[Galaxy Note II Q&A, Help & Troubleshooting] treszerotres:
a

its very interesting
[Galaxy Note II Q&A, Help & Troubleshooting] Zanr Zij:
I tried but could not find the best setting as expect.
[Galaxy Note II Q&A, Help & Troubleshooting] tuxonhtc:
Huh? What do you mean by that? The color calibration is as accurate as it could get to real life - what do you mean you didn't get the "best setting"? Probably you could slightly adjust the whites if it's absolutely necessary, other than that it's perfect. Give it 2-3 days and let your eyes adjust to the calibration, though.