yashsingh1/xdaforums huggingface dataset:
[Nexus 7 General] bftb0:
You mentioned "custom kernel".

As near as I can tell some kernel devs have been shipping just a bare kernel (zImage, etc), and others provide flashable boot images - that is, kernel + ramdisk.

If the "kernels" which include a ramdisk do something typical like set "ro.secure = 0" as a convenience for adb users (in /default.prop et cetera), and your app which "checks for root" inspects this property, then even though you removed SuperSU/Superuser and their corresponding "su" binaries this (as a single example) might cause the root check to still fail.

I guess the point is that you would need to know what exactly the app in question is checking for to know whether your efforts will succeed. It could be one or more of any of these things:

- bootloader lock state (only if it is detectable from the OS, not sure if this can be done)

- presence of a /system/xbin/su or /system/bin/su file

- presence of SuperSU.apk or Superuser.apk in /system/app

- ro.secure value (or others properties such as adb settings etc)

- relative timestamp checks on certain /system directories.

- TiBu installed as an app?

- other ?

I think that it is feasible to detect a non-stock recovery or boot kernel but not very easily with a non-root app - so you can probably get away with having a custom recovery and an unlocked bootloader too.

No way to know in advance though.
[Nexus 7 General] nthknd:
This maybe stupid but I had the same issue with my xoom and a few apps not working while rooted. The solution was to go into system then apps and rename the superuser to something else and that fooled the program and it didn't sect root. Maybe try that?
[Motorola Droid 4] Mike03:
I understand that this is probably the most commonly brought up question and all the veterans must cringe at coming across it yet again, but I've yet to find a real fix for this. On any current JB Rom, be it the unofficial AOKP build, official AOKP, unofficial CM10.1, or the newly released CM10.1 nightly build, I cannot send or receive MMS messages, even when trying to use a 3rd party app such as Chomp SMS. The only rom I've been able to do this on is Eclipse, and even that requires a wipe of cache every time I want to download a new one. I'd really like to use a JB rom, and it seems that others aren't having this issue, can anyone point me in the right direction?
[MDA, XDA, 1010 Accessories] trevorcompton:
Does anyone know of a fix for connecting the SX56 to an external projector like an "INFocus" projector? This would obviously be for giving Power Point presentations from the XDA device.

:?: I was given several options from Siemens but most or all of them required SDIO connection rather than the standard SD slot that the SX56 comes with. Whoever was the genius that didn't integrate the device with SDIO compatibility should have his n**s taken from him, but I need to find a solution.

Help????
[MDA, XDA, 1010 Accessories] edwardanton:
I've recently been contacted by Margi, which produces the 'Presenter to Go' accessory. They have projected mid Sept for release of a version compatible with the XDA. :)
[HTC Desire C] Ansanen:
This is port of CM9 settings.apk

This is beta1

BUGS

display settings does not work

***HOW TO INSTALL***

-make a backup of original settings.apk

-copy settings.apk to sd-card

-copy settings.apk to /system/app/

-reboot phone

boot can take a long time

Tested on Revolution De-Sense Rom v2.1

Please report bugs and visual defects.
[HTC Desire C] brnt:
This looks promising. :D

I just want to say that it's not for everyday use, but I hope it will be.
[HTC Desire C] barbrick:
No text in the apps section, icons still show up.
[HTC Desire C] brnt:
I've got text there, this is due something in your framework, I suppose.

And I'd like to ask, how did you port it? Maybe you can do the same with the Phone app, so that the lockscreen would function as it should?
[HTC Desire C] barbrick:
Likely caused by the sense 5 fonts, ill switch back and see if the issue persists.
[Sony Xperia P, U, Sola, Go] kasunpck:
I bought a sola about a week ago. But I did't got the ics update till date. Im in Sri Lanka. Is the update carrier depend or can i update it manually to new firmware
[Sony Xperia P, U, Sola, Go] CrazyXperiaA:
I'm in the UAE as of now and haven't received ICS update as of now. But, you can download a " *.ftf " file which is the firmware file and install it via flashtool. You can look up the tutorial on google or on the forums :)
[Nexus 4 Q&A, Help & Troubleshooting] msucoleman:
Pretty much what the title says. I have a friend looking at the Nexus 4 and they want only the 8 gig, but I find that to be not enough. I have that much on my S3, but I have a 32gig SD card so I'm fine. But, without the SD card option in the N4, I don't find the 8 gig model to be worth it.

Thoughts?
[Nexus 4 Q&A, Help & Troubleshooting] subxero123:
No
[Nexus 4 Q&A, Help & Troubleshooting] chrisrozon:
Total space 5.67gb

Available space 2.63gb

I'm completely satisfied with the 8gb model :)
[Nexus 4 Q&A, Help & Troubleshooting] Exodian:
All depends on what your phone use is like. I play games and watch movies on my tablet and have an iPod for music. All photos get synced to dropbox and deleted from the phone so 8gb model is more than fine for me. All depends on how you use the phone.
[Nexus 4 Q&A, Help & Troubleshooting] Ace42:
Do not buy. I got the 16 cause my music basically fills the 8gb alone. You don't want the feeling of having to constantly monitor your usage.
[Nexus 4 Q&A, Help & Troubleshooting] msucoleman:
They ended up with the 16gb model. I played with it a little. Wished I cld get 4.2.2. I miss it

Swiped from the S3
[Nexus 4 Q&A, Help & Troubleshooting] baraks:
well that depends on USER needs....

i have the 16GB ver. and have 7GB free... ithought the 16GB won't be enough cause i had 32GB on my Sensation 4G and used 28GB BUT somehow on the nexus 16GB is more than enough for me...

so it depends.....

best regards,

baraks.
[Nexus 4 Q&A, Help & Troubleshooting] lfbuccat:
It really depends on your workflow. I wanted a 16GB but it was so hard to get when the Nexus 4 was initially released so I settled with an 8GB. And so far I have been managing. I really don't play a lot of games or store movies on my phone, I use a tablet for that because of the screen real estate and the bigger battery. I use google music to store and stream my music and I have a dropbox and Box.net account where I store pictures and whatever files I may need. after about 4 months with this phone I still have about 1.5GB free memory which I think will be enough until the Nexus 5 comes out. :)
[Nexus 4 Q&A, Help & Troubleshooting] exb0:
Why won't it be enough? Sync everything online. All my music (90gbs of them) sync with google. I have unlimited Data so it's right there when I need it. Documents are stored on Google Drive and movies, well I'm sure the device would fit more than 5 DVDrips.
[Nexus 4 Q&A, Help & Troubleshooting] MarcPlusTwo:
For my usage (Surfing, Music, XDA, Youtube) 16 GB are enough. I have ROMs, at least one Nandroid Backup and such stuff on it.
[Ouya General] rushless:
Would be nice if could use a hub to run game controllers (USB arcade stick as example), thumbdrives and USB drives at same time.

Also nice if the device had built in support for NTFS.

Even better if the power line to the USB port could power the hub like a laptop, but that is probably being too greedy.

Update: I can find nothing that says it will or will not. I am leaning toward will, since makes not sense not to- in theory.
[Ouya General] eksasol:
It should support USB hub, you can buy a hub that accept wall adaptor for extra power. As for NTFS not likely official support due to being a Microsoft propriety format, but there can be apps or modules to install that enable it, same as Android phones (Stick Mount + NTFS Mounter).

Sent from XDA app
[Ouya General] lovekeiiy:
I think USB support is build into Android 4 and later. So if you have a power USB hub, you'll be fine. The rest, is just want does Android support or Ouya have build in. I think controllers, keyboards, and mouses will be fine. They may not support all keys or functions, but they'll work for the basic functions.

I just can't say about NTFS support. I think more than likely it may so that larger files can be stored and used for games. It'll possible we could have large and long games available.

The good news, we'll find out in about a month's time.
[Ouya General] Conjukt:
USB hub would be helpful, my only thought is for me the common user the only thing I might use it for would be an external HDD just for additional game storage space. I suppose though for the ability to also have a keyboard and mouse or other components connected we would then need a hub.
[Ouya General] RussianCode:
USB NTFS Support? Com on now, almost everything supports NTFS and has at least a USB. Not to mention this being a "Console" type.
[Ouya General] eksasol:
It will certainly not support NTFS out of the box, NTFS is a proprietary Microsoft format.

There might be kernel or use Stock Mount + NTFS Mounter.

Sent from XDA app
[Ouya General] m4soN:
what about controller from an usual computer? are they working too?
[Ouya General] eso259:
+1
[Ouya General] eksasol:
I think it should, I don't see why not, though it might not work fully with some controller, especially analog and touch buttons, but I can't be sure. Knowing Ouya designed this for gaming they will probably make sure it work worth variety of controllers.

-1

Samsung and HTC pay a royalty fee of about $10-$15 to Microsoft for every Android phone they sell, yet they still don't support NTFS out of the box.
[Ouya General] rushless:
I am wondering if any controller will work besides their own. They are already apparently locking out the Play store and will lock out the Ouya store for rooted devices. Seems logical they would find a way to allow only their $50 controllers to work, since more expensive than most other options. If not, most people will buy cheaper options.

Perhaps they will allow keyboard map type devices and only analog control with their controllers. Kind of hard to lock all controllers out, unless they also do not allow keyboards.
[Ouya General] Harfainx:
Bluetooth controllers should work just fine. They just won't have all of the features that the OUYA controller will have.

Controller Specs:

Two analog joysticks, each with their own “button” (i.e. L3 + R3)

A D-Pad

Four face buttons (labeled O, U, Y, and A)

Two digital shoulder buttons (L1 + R1)

Two analog triggers (L2 + R2)

A menu button (to open the OUYA menu at any time during a game)

A touchpad (to mimic mouse/touch controls or to be used in games)

Player LED indicators (so you know which player a connected controller is set to)

Don't expect the two in red to be on aftermarket controllers for quite some time (and even if they do have a "menu" button, it likely won't work until someone makes an app for mapping).

The touchpad will make a functional difference if you're playing a game that requires touch input if you're using an aftermarket controller. You'll likely become rather stuck if it requires touch input.
[Ouya General] raptir:
The PS3 does not support NTFS. Even Microsoft's own Xbox 360 does not support NTFS. If the Ouya supported NTFS it would be the first console to do so.
[Ouya General] supremekizzle:
So would a USB hub allow me to connect multiple N64 USB or multiple SNES USB controllers to the console? If not, what would I need to do this? Thanks
[Ouya General] eksasol:
It should as long as there are modules that allow those controllers to work correctly.

Sent from XDA app
[Ouya General] AiyoX:
Well that's what we have the wonderful people of XDA for! :victory: :laugh:
[Ouya General] SGTChilidog:
Just my two cents... I have several droids that I've rooted and used Stick Mount with, and they all play very nicely with NTFS formatted USB drives. I also use a nifty little USB hub that has a plain jane USB plug on one side of it and a micro-USB plug on the other end... it works with either end (OTG adapter for USB A) and I haven't had any trouble with it on any of my devices. One other item of possible interest is the variety of common devices that Android will support with little or no extra effort from the folks at OUYA; I have a G-Box Midnight, which has a very crude firmware, based on ICS, and I keep a USB Mouse, USB Keyboard and Microsoft USB WebCam plugged in at all times, and they all worked with zero configuration on my part (the webcam captures 1080p video and even has a microphone built-in and that works too). Before I bought the webcam, I did some reading to make sure that my idea for it would bear fruit, and what I gathered was that a "universal" webcam standard had been developed and that most big manufacturers now conform to it for driverless functionality, along with Windows, MAC and Linux. My experience has been consistent with that explanation, so I am anticipating that my OUYA will be equally kind to these USB devices.

---------- Post added at 12:16 PM ---------- Previous post was at 11:56 AM ----------

One other thought that just struck me... an NTFS file system (at one point in its development) was the only FS that supported persistent data for an Android x86 system installation. At the time, you were stuck operating as a LiveCD if you formatted ext3 or ext4. It's been a while since I fooled around with that, so I have no idea where they're at with that now, but it struck me as odd that I would have to format NTFS for a Linux-based OS installation, instead of ext(x), although I've also used Linux on NTFS partitions in other situations in the past. At any rate, I'm more surprised now when NTFS ISN'T supported than when it is. I could be completely wrong this time. ;)
[Ouya General] supremekizzle:
Are modules on the software side? Do you mean modules that allow the controllers to work with an emulator, or is the module for telling the ouya that multiple devices are connected to the one USB port? Thanks again
[Ouya General] mromutt:
see i find this weird since i have used ntfs formatted hard drives on the 360 and they worked just fine, just plugged in and was good to go. the console did say it wasnt supported but still let me use it. so i dont really understand why it says it and they claim it is unsupported when it clearly has for me on more than one console :/

---------- Post added at 07:39 PM ---------- Previous post was at 07:31 PM ----------

yeah its been years since i have had issues with ntfs and linux playing well, infact it seems standard to have it out of the box on most flavors. even our cable boxes support it now without a second thought
[Ouya General] josenightbreed:
i remember the days when i need it 2 or 3 libraries in linux to be able to read ntfs, writing was a whole other issue :) Thank god those days are gone :)
[Ouya General] raptir:
Well, you're the only person I've seen saying that it works. Googling "xbox360 ntfs" will get you about fifty people saying that NTFS does not work just on the first page.
[Ouya General] mromutt:
i literally just plugged in the drive and it let me listen to the music on it
[Verizon Samsung Galaxy Note II] ITGuru48051:
I just switched to Carbon 1.5 and I would like the default Samsung camera and keyboard app. Is there a place I can download them from?
[Verizon Samsung Galaxy Note II] kintwofan:
No because it wILL only work on aTW based ROM.
[Verizon Samsung Galaxy Note II] ITGuru48051:
Ahh ok. Thanks for the response.
[Verizon Samsung Galaxy Note II] ufkal:
and that's the reason I can't switch over to CM10.1 or PacRom. I really like the keyboard and the camera with all its features. But dang, I want my CM roms.
[Verizon Samsung Galaxy Note II] ITGuru48051:
After a few hours on the Carbon ROM, I forgot about most of the TW features I liked. Seems you can get all the functionality you want from apps from the store. I say try an AOSP ROM for a few days, worst case you have to flash back, but I don't think I am going back to a TW based ROM again.
[Verizon Samsung Galaxy Note II] ufkal:
Coming from the GNEX and Killrom and Eclipse and all the other goodies over there, I truly do like the ASOP/AKOP roms. I just like that keyboard. And while swiftkey is right in front with keyboards, it just seems to be missing that little something. I don't know. I'm getting all the ones I want to try, and will probably blow through several different ones before I decide. It just takes so long to restore and get everything set up. :silly:
[Verizon Samsung Galaxy S III] HypostaticOnion:
Haven't seen anyone post about this (even after doing a Google search), but Verizon has started sending out the OTA today. My question is this: since my bootloader in unlocked, and I'm rooted, can I restore back to my stock ROM and take the update? Is there a possibility that I'd completely lose root? Obviously I'd lose superuser and such, but would it replace my bootloader and custom recovery?

Thanks in advance for any helpful replies. I've been around android for a while now, but I'm new to Samsung phones, and how the bootloaders work. (I'm used to HTC where you S-OFF and you're good to go)
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Yup, you can restore back to stock (via nandroid or Odin) and take the update. You should switch back your recovery if you restore a stock nandroid though.

You answered your question, if you lose SU, you lose root. Verizon OTA's will replace your bootloader and custom recovery if you force the install to take through your custom recovery. It should fail initially but I've read around that folks installed the OTA in recovery.
[Verizon Samsung Galaxy S III] stkiswr:
I'll check my wife's phone tonight. If she gets the ota I will pull it from the cache and extract the boot loader and recovery and rezip it and see if it will flash via twrp
[Verizon Samsung Galaxy S III] HypostaticOnion:
Ok thanks for the reply. What do you mean by switch back my recovery? I'm currently on TWRP which is what I rooted with, and I've been using it since. I just want a completely untampered stock OTA of the latest OTA.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I mean, the OTA will fail if you just try to accept it right now. It would also fail if you switched back to your stock nandroid because you still have TWRP installed too. That's how its always been. Switching to the stock recovery, you could use EZ Recovery to do so, would resolve that.

I've read that you can still have a custom recovery installed and successfully take the OTA with a custom recovery installed but idk the exact steps to take to make this happen. Since I have no need for accepting OTA's I try to learn from what people post here.

Edit: Seems my OTA/custom recovery inquiry has been answered pretty thoroughly here (post #10). You could try those steps if you desire too.
[Verizon Samsung Galaxy S III] HypostaticOnion:
Hmmm sounds interesting. I doubt I'd be able to use EZ unlock like I did on ICS... I guess I'll wait for a recovery flashable file.
[Verizon Samsung Galaxy S III] cammykool:
What OTA?
[Verizon Samsung Galaxy S III] stkiswr:
4.1.2 ota being pushed starting today. According to Google+
[Verizon Samsung Galaxy S III] pettigrew95:
Is this basically the same thing as the VRBMA2 leak?
[Verizon Samsung Galaxy S III] buhohitr:
Yes, it's a final version of VRBMA2 leak which is VRBMB1
[Verizon Samsung Galaxy S III] cammykool:
Damn.... on the day i root... oh well glad i did!

vzw probably blocked our current methods.
[Verizon Samsung Galaxy S III] pettigrew95:
The OTA de-odexed is already posted courtesy of beanstown over here:

http://xdaforums.com/showthread.php?t=2177798
[Verizon Samsung Galaxy S III] lexluthor:
I'm rooted, unlocked and custom recovery w/stock ROM (odex).

How do I get this update installed and keep root/unlocked/custom recovery in place?

Also want to keep Google Wallet working correctly.
[Verizon Samsung Galaxy S III] pettigrew95:
Download this and flash it through recovery once beanstown posts the links:

http://xdaforums.com/showthread.php?t=2177798
[Verizon Samsung Galaxy S III] lexluthor:
I'd rather have the odex version though. You think someone will post that?
[Verizon Samsung Galaxy S III] stkiswr:
OK I took it from cache. Does anyone remember what all I need to delete after I extract it so it doesn't update boot loader. Recovery for sure...here's where I am before i rezip
[Xperia Z Q&A, Help & Troubleshooting] samxool:
As the thread title suggests, How easy is it to root the Xperia Z?

i'm thinking of rooting, but I've never done it before and don't know where to start looking.

thanks
[Xperia Z Q&A, Help & Troubleshooting] xXxG0dzRAgexXx:
How hard is it to post in the Xperia Z Forum? :p

I wouldn't know how hard it is, I advise asking it again in the Xperia Z forum, or google it. We don't know much about Xperia Z rooting over here in the HTC One forum. :p
[Xperia Z Q&A, Help & Troubleshooting] daleski75:
Sorry but this is a HTC One section you will find the correct section by searching for Sony Xperia Z!
[Xperia Z Q&A, Help & Troubleshooting] metalfan78:
This is getting amusing. I keep coming here to see how many incorrect posts there are more than I come here for info about the new phone!
[Xperia Z Q&A, Help & Troubleshooting] craftycarper1:
Piece of piss Quite easy really, plant it in the ground, give it a good watering (it won't get damaged, it is waterproof after all), then leave it buried for 6 months and it should be rooted by then.:laugh:
[Kindle Fire Q&A, Help & Troubleshooting] ben08112:
Well I've searched the forums and I can't find anything similar, which leads me to think I'm just missing something really obvious, but this is really frustrating me so I need help.

I'm trying to use the Kindle Fire Utility v0.9.6 to install TWRP and FireFireFire bootloader to my first-gen Kindle, so I can install Hashcode's Jelly Bean. I think I've got the normal drivers working as it shows up as ADB: online, although Boot mode: unknown is also reported. When enter "Install TWRP" it says it's putting the kindle into fastboot mode, but my Kindle seems to have other ideas. It just reboots normally and the utility is stuck on "waiting for device".

I've read one of your fastboot guides, which said that inserting the factory cable then inserting into a computer should activate fastboot mode. Well I tried that with what I think was the original cable, and it just booted normally.

I some small experience with rooting, but basically I'm a noob. I do have some Linux systems handy if they're required.

Any help would be appreciated!
[Kindle Fire Q&A, Help & Troubleshooting] mindmajick:
Can't help much since i don't have a kf1..

But i CAN tell you that the ORIGINAL cable is not the same as a factory cable.

--

Sent from my Kindle Fire 2, CM 10.1
[Kindle Fire Q&A, Help & Troubleshooting] ben08112:
OK thank you, I didn't know that.

However I think even if I did get hold of one of these factory cables, it wouldn't help much as I need to get this program to work primarily...

any ideas what might be causing adb to be online but boot status unknown?
[Kindle Fire Q&A, Help & Troubleshooting] BrooklynNY:
Personally, KFU v0.9.5 worked better for me.
[Kindle Fire Q&A, Help & Troubleshooting] ben08112:
Exactly the same result with that version, I'm afraid. :crying:
[Kindle Fire Q&A, Help & Troubleshooting] Vlasp:
Are you using a USB 3.0 port? Maybe that's why. USB 3.0 is high speed, so maybe the connection got messed up...

How old is your computer?

Sent from a bird... No, a plane... Wait, It's a Kindle Fire!
[Kindle Fire Q&A, Help & Troubleshooting] ben08112:
I'm afraid that's not it... It's a 4 year old mid-range Win7 64 bit laptop. I did root my phone using this computer... I think I'll try using one of the XPs that I have on hand to see if that makes a difference.
[Kindle Fire Q&A, Help & Troubleshooting] ben08112:
Well I've tried on two XP computers and I can't even get the drivers to install.
[Kindle Fire Q&A, Help & Troubleshooting] ben08112:
Oops...

OK thanks for your input guys, you've been really helpful.

I feel really stupid now - my kindle is actually a kindle fire 2. That makes sense. For some reason I thought that a second-gen kindle fire was the kindle fire HD, and therefore mine was a kindle fire.

Sorry for wasting your time.