yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Q&A, Help & Troubleshooting] Moomoomania:
When I first got my Nexus 9, I looked very carefully for the light bleeding as I heard it was really common on these devices. And to be quite fair, mine had a lot when you ramp up to max screens brightness (especially on the bottom left corner). But after several months of use, I hardly see it now as it's due to myself not always nitpicking at it. You will eventually grow accustomed to it so in the end, it'll definitely fade into the background of your device
[Nexus 9 Q&A, Help & Troubleshooting] ChristianJay:
The first one I got from Amazon, a early build white 16gb had really bad bleed and the buttons were flush. They sent a replacement with a later build date and it has MUCH less bleed and great buttons. I was fortunate I assume.
[Nexus 9 Q&A, Help & Troubleshooting] colts187:
I have one of the same models you have I bought from best buy yesterday. I'm really happy with mine. I have no perceivable bleed and the build quality is excellent. The back of the device has no flex. Its much better than the floor model in the store for sure.
[Verizon LG G3] bagsofcole:
Hey All,

I've tried about every LP AOSP Rom for the Verizon VS985 variant of the G3 and think I've narrowed down the culprit. First let me explain the issue. The Amazon Music App won't stream music, giving exception 181. I've chatted with amazon tech support and now here I am. It works fine with the stock ROM and Jasmine. It also works with Fusion 5.0 and Slim Alpha - I believe both of these to be Slip based. But for the life of me, I can't get it to work with any CM based ROM including but not limited to Illusion, Vanir, Fusion 5.1... more than I'd like to admit.

Anyone know how to fix this issue so I'm not so limited? I don't need many, just one good daily driver. After gong to AOSP, back to stock is so slow.

Thanks,

bagz
[General Topics] Menneisyys:
Available Emulators I - Recommended ones

1. MorphGear 2.4.0.9

MorphGear is a multi-purpose emulator for Windows Mobile. While, in general, it's a bit (or, as far as SmartGear is concerned, a lot) slower than the other, recommended emulators, it's pretty good in the following respects:

it supports Landscape

it has no known MAJOR bugs, unlike, say, PocketEngine (under WM2003+) and XPCE (sound desynchronization)

it is free.

Unfortunately, in addition to speed issues (which, again, ONLY affect slower devices - all games run flawlessly on my 624 MHz Dell Axim x51v under MorphGear), it's the only emulator NOT to support stereo sound with TurboGrafx-16 games (all the other games have stereo sound; most games are stereo and MUCH more fun with stereo enabled). This is another problem with the emulator. Hope it will be fixed some time - it can't be THAT complicated.

Getting and installing MorphGear is easy: download THIS (main program) and THIS (TurboGrafx-16 module) CAB files; unzip them, transfer them to your PDA and click them for installing. Then, click the new MorphGear icon in the Programs / Games group. Click the icon in order to select a ROM to load. After this, the game will start (if it’s compatible).

Note that, if you transfer your ROM images compressed with ZIP, you will explicitly need to switch to displaying ZIP files in the file dialog box.

2. SmartGear 0.12

SmartGear, introduced in the NES article, is a REALLY- REALLY fast emulator - WAY faster than any of its alternatives. Unfortunately, this comes at a price: it's incompatible with many titles the other emulators are compatible with. In addition, it's a commercial application - but, taken the speed and the number of systems it emulates into account, it's still a excellent tradeoff. Finally, it's useless on high-resolution ((W)VGA) devices.

However, if you have a slow(er) Windows Mobile device and / or you don't want to / can't overclock it, SmartGear will become a very nice alternative to anything else. Also, it’s the only alternative when you want to play all the available Bonk titles. The same stands for underclocking your otherwise very fast and responsive (say, 624 MHz Xscale-equipped) mobile to save (considerable) battery life. Sticking with current Xscale-equipped devices, at 208 MHz, the emulation still works flawlessly (unlike with any of the other titles).

Please read the NES roundup for more info on using and configuring both MorphGear and SmartGear. Note that, as far as the former is concerned, the module name is "HuGo (TurboGrafx-16)" - look for this one when you change its settings:
[General Topics] Menneisyys:
3. PocketEngine 1.0 beta 1

This free and, unfortunately, long abandoned emulator would be excellent because of the Landscape support and sufficiently large on-screen tap areas (in Landscape) - the two main advantages of this title.

Unfortunately, it's plain incompatible with all operating systems starting with WM2003 (including, therefore, WM2003, WM2003SE, WM5 and WM6 and only excluding PPC2k and PPC2k2). Pressing Button 1, which is used to pause the emulation of the current title and bring up the menu completely crashes all (more) recent operating systems. However, if you do learn to live with the bug (for example, you don't want to frequently change the game you play and resetting the device after finishing playing isn't a problem), you may find this title excellent because of the above-mentioned landscape and screen tap zone support. It's also compatible with VGA devices (unlike SmartGear) and has no sound problems (unlike XPCE ver0.22).

The other major problem with the title is the lack of save loading/saving support, as opposed to (almost) all the other titles.

The menus of this title are really simple, unlike most of the alternates (1 2 3 4).

Available Emulators II - Non-recommended ones

XPCE ver0.22

This title wouldn't be THAT bad - if it had decent sound support. Unfortunately, it doesn't have - it has awfully desynched sound makes this a bad choice – unless you are ready to play without sound.

To find out how bad the sound support in this emulator is, listen to the music of any game having a, say, rhythmical music (for example, the in-game music of Bomberman '94). You'll see the emulator completely messes up the rhythm of the track. Unfortunately, disabling auto frameskip (the trick that helps with many SNES emulators upon encountering the same problem) doesn't help either.

bfEngine v0.1b

This title is REALLY bad. It has a very low compatibility ratio. And, if is compatible with something, it’s way too fast - unless you enable Throttle in the settings (see the link for other settings capabilities). Finally, it has no sound support at all. Absolutely not recommended.

TGEmuCE

(the homepage of the developer doesn’t list it; neither does its Download section)

This is another title you'll want to avoid. It's VERY slow and the frameskip parameter (Option / Misc) doesn't help this at all (I bet it doesn't even try to read this value under Windows Mobile - the app is a native WindowsCE application). What is more, the settings you (manually and VERY awkwardly – examples: 1 2 3) enter in the configuration dialogs don't stick - they're all forgotten upon restating the emulator. All in all, it's in NO way recommended.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] goyal.vishal3:
hello all,

I am having a samsung galaxy tab 2 gt-p3100 and it is out of warranty now. It was working fine till the day when my cousin installed a game of almost 2 GB size (fifa, also i dont know whether the problem is due to game or not). after the game was launched tab showed restarting issues. It is restarting again and again by itself even when I am not using it. I decided to factory reset it but it didn't worked. I tried hard reset also and again it was not working. All apps data were present there even after reset, nothing was changed.

I did some research on android forums and XDA and found that installing custom ROM can solve this issue else I have to get my motherboard replaced.

I started with rooting and installing CWM recovery on my device. I did the process using a video tutorial and used the files mentioned in it from XDA. the files name is :

"P3100_CWM_RECOVERY-6.0.1.3_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5"

My odin message box displays below messages. :

............

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

<ID:0/007> Firmware update start..

<ID:0/007> cache.img

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

<ID:0/007> recovery.img

<ID:0/007> RQT_CLOSE !!

<ID:0/007> RES OK !!

<ID:0/007> Removed!!

<ID:0/007> Remain Port .... 0

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

(Before showing PASS messages. odin showed me RESET message and it was only when tab restarted it showed me PASS)

This shows that process is completed and my device should be rooted. But when I checked there was not Superuser installed and no custom recovery was seen when recovery mode was started.

Also, tab when started shows error messages like "gapps stopped working", "gmail stopped working". In short, all the google apps were displaying these kind of messages.

Please help!!! and suggest me how should I proceed to try custom ROM.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] shsagnik:
Have you checked root access using any app? If no then do check it.

---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------

And can you boot into recovery? Volume up+ power button?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] goyal.vishal3:
i tried booting the device into recovery mode using volume up and power button but itt shows android recovery mode.

Also, i tried installing the application to test for root but tab won't allow the installation to finish. It restarts in between so cant check using apps.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] shsagnik:
Try flashing recovery through odin
[Galaxy Tab 2 Q&A, Help & Troubleshooting] goyal.vishal3:
File which i mentioned in above description is for rooting as well as cwm recovery (it was shown in the video as such) so it should complete both processes. But for me it seems none is completed.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] shsagnik:
Have you tried restoring the stock rom through Odin?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] goyal.vishal3:
Yes i tried that option too but the installatiin was failing in between.

For once, i took my tab to samsung service centers too, they too tried to flash rom using odin (i was able to see there working on pc) but there process was also giving the same result - fail.

I am having a doubt, should my device be rooted to install cwm recovery or this recovery is required to root the device as i am planning to again perform these processes individually using other tutorials individual for both.

I hope this helps.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] shsagnik:
Maybe you have got the famous trim bug,I think you should use the superuser zip method to root your device,the one without recovery included,

Then try flashing the recovery,
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Yayan.F:
Try to flash with stock rom from www.sammobile.com.flash with odin.if failed try again 2times or 3times,because Yesterday I have got some problem like you,my device also P3100.fhirst time failed until 3times succses to flash,but I have stuck on boot logo samsung I waitting until 20minutes-30minutes not to enter menu.and I open back cover and remove the battery from device until 30 minute I put again the battery.and boot into recovery system.and do factory reset,wipe chace,davlik chace,and reebot device and my device now get life again until here...

Try do it my be can help your device.....
[Galaxy Tab 2 Q&A, Help & Troubleshooting] shsagnik:
Midst of the people have there battery fixed inside their tab, and as I have seen in YouTube it's easy to crack the screen while doing it.?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] goyal.vishal3:
I have already tried to flash stock rom from sammobile and as i have already mentioned, same process was also tried by engineer at samsung service center and the process failed. In all, that process is almost tried on this tab for 5-6 times but with same result.

I also noticed one thing that this tab is stuck at one particular state. No mattwr what i do with it, it comes back to same home screen and without any changes. For example, if i start my tab and uninstall some application and change the view of home screen and then if the tab restarts, it will be back to previous state i.e. no apps unonstalled and home sceen will also b back to previous state. All changes are reverted back.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Yayan.F:
I think this problem is EMMC.

Try ask to Samsung Service Centre.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] baptenda:
Same here

I have the same problem as yours. Tried to flash the stock rom, wiped the device thru the android recovery, every thing fails. If there is anyone with the solution, let me know.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] andreavanzini:
I have the same problem with a Samsung Galaxy Tab 2 10.1 P5100.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] cx5:
I have the exact same problem to P5100. No solution yet, still reading everywhere.
[Nexus 6 Q&A, Help & Troubleshooting] marsdiamond:
I am on my second OTA and my phone gets encrypted during the process. Is there a to update without forced encryption being reactivated on my device? I want to disable encryption so that my N6 runs faster but I don't want to have to wipe my device every time there's a new OTA.
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
How are you OTA-ing? OTA checks for modified kernel and should fail... You need edited kernel to have forced encryption disabled.

The best way to update would be to fastboot flash the system.img and then flash a matching boot.img wit forced encryption disabled.
[Nexus 6 Q&A, Help & Troubleshooting] marsdiamond:
I am using the Wug Fresh Toolkit...

But when I flash an image with encryption disabled, won't that wipe my device?
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
No idea. I suggested using fastboot. If you're using s toolkit, you're on your own. At least from me.

Here is my generic toolkit statement

There's nothing wrong with toolkits themselves.* They can be great, useful tools.* We're not even saying they cause bricks either - though users not understanding things *could* cause one...Toolkits are necessary on many devices, but on Nexuses, the manual steps are very easy.

Ultimately it's fine to use a toolkit but *only* if you already know how to do all these steps manually.* If you do not know how to do that then you should do it manually so that you do know. * The reason for this is if something goes wrong further down the line, we don't want to have to teach you the basics AND tell you what you need to do to fix whatever issue you have.* We just want to do the latter - because teaching someone the basics that they should already know when they are frustrated and panicking is not a good set of circumstances to be teaching under and it is frustrating to us more than you and putting us in that situation is a little bit selfish
[Nexus 6 Q&A, Help & Troubleshooting] GuestK0087:
Do you keep this statement somewhere so you can copy and paste or do you type it out every time? ;)
[Nexus 6 Q&A, Help & Troubleshooting] GuestK0087:
Touché.
[Nexus 6 Q&A, Help & Troubleshooting] marsdiamond:
rootSU...Thank you for you candid response. I do agree with you. I should know how to manually control my device. I bricked (no OS found) my N6 with my first lollipop OTA update using the toolkit. I looked up some manual instructions to flash the OS back to my device. I would have, but my third attempt/configuration with the toolkit I got it back. I plan on learning how to manually maintain my N6. Do you have a link to a thread that you suggest to get me started?

Also, if I manually flash OTA updates, is there a way that I can keep my encryption disabled? That is currently my biggest problem. Each time I update with the toolkit it re-encrypts my phone during the process.
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
Just go to General > Sticky Roll-up thread.

All "important" threads are there.

You cannot flash OTA if you have any customisations in the ROM or kernel and if you're unencrypted, you have a custom kernel.

If you're wishing to stay rooted or unencypted, you should either install a rom.zip, custom kernel and SuperSU from custom recovery or download the factory image and fastboot flash the system.img, a custom kernel (recovery or fastboot) and SuperSU (recovery)
[Xperia Tablet Z Q&A, Help & Troubleshooting] elchingon:
I just purchased my Tablet from amazon and now having problem with the touch screen responding from time to time. it won`t unlock lockscreen sometimes it work after i reset but only for a while. has someone had this issue and knows of any fix?:confused:
[Xperia Tablet Z Q&A, Help & Troubleshooting] vlakarados:
This happened to my Xperia Z phone a while ago. Sometimes touch screen stops working entirely, have to reboot or do some voodoo with power button/lock screen. Have you done something that helped resolving this? I'm quite tired of rebooting when I need to make a call...
[HTC One SV] tnfsmith:
I own a One SV. I'm on Jelly Bean. I successfully rooted it via the newest superuser apk and twrp. But when I try to remove ANY file under /system (including apps) using Titanium Backup it require reboot device, after a reboot or battery run out it is mystically restored and apps installed removed either. But if I restart without mentions above it ok!!! Where the hell do the files come from? I've searched the entire phone memory but couldn't find anything. Have I missed something? :o
[HTC One SV] old.splatterhand:
Search this forum for my posts and keywords system write protection

I have answerd this question 20 times and more.
[HTC One SV] tnfsmith:
Thanks appreciate, I really unknown which cause come from and how to solve this issue because it's my friend device so I must post an question. I also have had some quick search but still out even through your reply with keyword suggestion :D
[HTC One SV] Xceeder:
The reason the apps are returning when you've rebooted your phone is because your not s-off I would recommend using rumrunner.....

Sent from my *super modded* HTC one SV ......
[HTC One SV] SHM:
If you flash a boot.img which has a modified kernel for write protection being removed then that too will also resolve the issue and thus S-Off wouldn't be necessary, but of course, going S-Off only makes it better and more convenient.
[HTC One SV] Xceeder:
Hhhmm you learn something new everyday , and just want to say I think you are very clever I've seen the posts you've done on XDA and I'm a big fan just one little question is the modified boot.img file available on XDA for the one sv or would it have to be created , I don't need it I'm just curious I'm already s-off ......

Sent from my Nexus 7
[HTC One SV] SHM:
Hard to say. Back when this device was a bit more active I would tell you, yes, but as of now that is a different story. Links could be bad but if you check old.splatterhands thread where everything needed to know about this forum is compiled then you may find that answer you are looking for.

With that said, it also depends on which K2 device you have. It's important that the correct kernel be used since they have their differences internally.

However, it is very easy to take the kernel source, remove write protection from it's source, then compile the kernel into a binary and apply it to your device. This is usually the approach I take for my own personal development and gain.

https://github.com/ModdingMyMind/an...mmit/c34ea02e20b758e78cae9f8b8bc975d268accd84

If you take a look at that link I just shared you will see the changes I made to the kernel source regarding the K2_CL (Boost Mobile) variant. Everything in green is what was added so the kernel would have Selinux support and everything in red is what I deleted to remove write protection from the kernel.

https://github.com/ModdingMyMind/an...mmit/86a317157a741ef12042426696e3c84eeed3e263

This next commit shows the changes I made to the kernel source for disabling Module Support so that when I make a new build with a new version number the kernel binary will work with the devices old modules thus saving me the hassle of building new modules and replacing the old with the new. More of a convenience in my opinion. Not many people disable module support for some reason which is why you will hear a lot about people flashing a new boot.img/kernel binary and then their WiFi breaking. It's usually the result of the kernel version not matching the old modules which prevents them from working properly or at all.
[HTC One SV] Xceeder:
That is very informative , thank you for your time and knowledge.....

Sent from my Nexus 7
[HTC One SV] SHM:
No problem. I still own the K2_CL. Wanting to get a new phone but until Boost offers something worth my interest I will continue to use this device as my primary. The phone has been out a long time now and is falling behind in the Android World but nevertheless, it is still a great phone and I use it for most of my Android Development projects since I don't always have time to sit in front of a computer. :)
[HTC One SV] Xceeder:
I have the European version and yeah they are good phones they don't sell them anymore here in the UK , I'm trying to get into android development myself but I think its a bit too hard , I read once on the internet that the best way to learn to code is to first find a fault or something you'd like to change in an app and look at the code so I'm going to keep researching and obviously looking at posts from professionals such as yourself ......

Sent from my Nexus 7
[Moto G 2014 LTE Q&A, Help & Troubleshooting] drumond1995:
I tried root my xt1078 with "kingoroot" and "one click root" but i failed =( the main fact of having a recent phone model is why there are not many ROM's or modifications :(
[Moto G 2014 LTE Q&A, Help & Troubleshooting] kieranc88:
​

On my xt1072 UK 4g model I flashed the 3g moto g twrp titan in fastboot and flashed SuperSU in twrp recovery and it worked fine, no problem at all. Assuming your boot loader unlocked.
[Moto G 2014 LTE Q&A, Help & Troubleshooting] drumond1995:
Could you send some pictures of your ROM here? Could you provide as which SuperSU file used to "root"? I blocked my phone and forgot the unlock password, I had to format the "hard reset" and I ended up realizing that the phone comes with a type of CWM, or am I wrong? For there where I used the restoration had "wipe cache, wipe factory, from SD card update" There are various options like CWM ...
[Moto G 2014 LTE Q&A, Help & Troubleshooting] sighted:
http://xdaforums.com/moto-g-2015/general/rooting-moto-g-2015-lte-xt1078-t3086069
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] chuckdart93:
Hello,

Recently, I've been trying to root my Kindle Fire so I could acess the larger Google Play market. However, I have not been able to do that. Through Towelroot, I always receive an error of "This phone is not currently supported." I have tried using the KFHDX toolkit and the instructions on this thread, and TR seperatly. The current version is 4.5.3.

If anyone could help, I would really appreciate it.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
You can't root 4.5.3. If you have a Gen 3 HDX (7" or older 8.9") you can roll back to 3.2.8, roll up to 4.5.2, root, block OTA (automatic updates from Amazon) and then install Google components including the Play Store. However, there are no hand holding tutorials and each step involves risk including permanently bricking your device. Also understand Google apps don't always play nice on Amazon devices. Many people have got them to work; others struggle.

If still interested you are going to have to do some reading. Everything is here in the HDX forums, albeit somewhat disorganized and often terse. Start here but do take the time to skim the entire thread (and others) before making the plunge. Good luck.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] chuckdart93:
Ok, thanks for the help!
[Nexus 6 Q&A, Help & Troubleshooting] scott0:
i googled and also checked a couple other threads re: icons and didn't come up with anything.......

screengrab: