yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] derekdoom:
Ah I see, it just occurred to me that this starting happening after I installed Cerberus so I've uninstalled that and it appears - at least for the moment - to have done the trick.
[Nexus 7 Q&A, Help & Troubleshooting] edufur:
I am thinking about getting one of these. But I have 1 question. What is the benefit of rooting it? On a phone, it makes sense... since you can tether. But what features on a tablet does one get from ROOT that they otherwise wouldn't?
[Nexus 7 Q&A, Help & Troubleshooting] xxdmxx:
USB OTG support, new ROMs, debloat, being able to back up certain apps/data
[Nexus 7 Q&A, Help & Troubleshooting] jazzboyrules:
I felt I wouldn't need to root. But then I couldn't help installing Titanium Backup and restoring backups of almost all apps from my phone. That's one reason, and then there are a lot of other reasons too, as the poster mentioned above.
[Nexus 7 Q&A, Help & Troubleshooting] gflare:
I haven't rooted my Nexus 7 yet, but when I do it'll primarily be for backing up my device. I love titanium backup and ROM manager. Even if you don't flash custom Roms,it still comes in handy to easily create full backups.
[Nexus 7 Q&A, Help & Troubleshooting] pmgreen:
If you root, then have a hardware defect/issue, are you SOL?
[Nexus 7 Q&A, Help & Troubleshooting] AraDreamer:
I'm too new to post links, but there's one on this site that if you root your device, that doesn't void your warranty. I'd search and read that.

-Ara
[Nexus 7 Q&A, Help & Troubleshooting] Jordanooo:
Just unroot and relock bootloader

In development section, theres a toolkit by 'Wugfresh' that does everything for you. Check it out
[Nexus 7 Q&A, Help & Troubleshooting] pmgreen:
thanks you too.. I appreciate the help without the ding that happens in some threads.
[Nexus 7 Q&A, Help & Troubleshooting] S3Killer:
thanx
[Nexus 7 Q&A, Help & Troubleshooting] whatisreal7:
Appreciate it!
[Nexus 7 Q&A, Help & Troubleshooting] stevieraveon:
Rooted for the sole purpose of changing dpi to 160 to get true tablet mode.
[Nexus 7 Q&A, Help & Troubleshooting] mi7chy:
I'd highly suggest you don't don't root unless you absolutely positively have a dire need for it. And, even then you should run stock for at least a few weeks to establish a base line so that if issues arise you can determine if rooting/kerneling/etc. is causing it. Seen too many glitches caused with non-stock in the forums.
[Nexus 7 Q&A, Help & Troubleshooting] Eagle1337:
I'd root for tablet ui and stickmount.
[Miscellaneous Android Development] breakhans:
Hi, I bought a "goophone y5" in Pandawill but I cheated and sent me a Sophone v75. How do I make ROOT? I need a google play!

I could install apps on Facebook and Instagram but no charge "news, dashboard etc."

Sorry my English is very bad.

thanks for the answers.
[Miscellaneous Android Development] whitetigerdk:
Hi,

U can use SuperOneClick to get root - Use the "force mode" .. Google the program..
[Miscellaneous Android Development] chrisrock782003:
Hello please help me

I don´t unserstand waht to do?

I search for Super One Click and then?:confused:
[Galaxy S III Q&A, (US Carriers)] jjlean:
So yesterday I was driving and I had a triangle with an exclamation point pop up in my notification bar. I noticed my 4g connection was gone. I opened the notification and it said data access restricted. I could not get any data. I checked the network settings and even re-selected tmo... nothing. I shut my phone off and when it can back on everything was normal. Had been fine since. What happened? Think it was just a freak thing?

I haven't installed and new apps or firewall type apps. I still have my imei.

Sent from my SGS3
[Nexus 7 General] Mento:
What are the best settings to use in Handbrake for the Nexus 7?

I want to encode movies while keeping good quality but as the device has limited space I dont want to store any information that the device cant show.

Thanks,

Mento
[Nexus 7 General] dej2gp3:
I'm still a rookie on the forum so I can't post links, but do a Google search for "android video compatibility" and you will see the stock android video capabilities in the first link, address starts with "developer.android."

You'll see that it basically can handle good hi def in the form of mp4 and mkv. That being said, you can use less space by using avi files that are marginally smaller, but you will need a media player app like MX player, there are plenty of free ones that can get the hardware involved in the processing so you get great video.

Hope this helps.
[Nexus 7 General] reggie14:
I've been looking for the same information since the Nexus 7 was released. I haven't been able to find a good resource that says what options in the H.264 spec are supported. However, I was able to play back some movies which I encoded for an iPod Touch using Handbrake. These videos were encoded basically using the iPhone profile with some minor changes. So, H.264, high-profile, using b-frames (I think 3).

I've been using DicePlayer, mostly because I couldn't get stable playback using MxPlayer or the stock player on my Touchpad. It seems like the Nexus 7 stock player is capable of playing those files back, but I still use Dice.
[Nexus 7 General] bennor3814:
There are two presets in Handbrake under Devices, Android Mid and Android High.
[Nexus 7 General] haydonxda:
ffmpeg settings

It's a shame there's no standard. Each Android device supports different features. Using ffmpeg If you want maximum compatibility you have to encode with baseline slow. However, the Nexus 7 seems to have excellent H.264 support.

Here's what I've successfully used to downconvert 1920x1080i video - it does crop the edges a bit but I think it's probably within the overscan area anyway. (Yeah, I know, LCDs don't actually have overscan.)

High quality, remove a logo, 24fps 'film' source :

ffmpeg -y -i <INPUTVIDEONAME> -r 24000/1001 -crf 20 -filter:v yadif,removelogo=<LOGOFILENAME>,scale=-1:800,crop=1280:800 -sws_flags spline -preset placebo -profile:v high -aq 90 -ac 2 <OUTPUTVIDEONAME>.mp4

Lower quality (crf=20 vs 30), no logo removal:

ffmpeg -y -i <INPUTVIDEONAME> -r 24000/1001 -crf 30 -filter:v yadif,scale=-1:800,crop=1280:800 -sws_flags spline -preset placebo -profile:v high -aq 90 -ac 2 <OUTPUTVIDEONAME>.mp4

Lower quality, 29.97fps video source:

ffmpeg -y -i <INPUTVIDEONAME> -r 30000/1001 -crf 30 -filter:v yadif,scale=-1:800,crop=1280:800 -sws_flags spline -preset placebo -profile:v high -aq 90 -ac 2 <OUTPUTVIDEONAME>.mp4

This works with CURRENT builds of ffmpeg as of this post. Earlier releases may not work.
[Nexus 7 General] br0adband:
Best bet is just choose the iPhone 4 preset and up the width to 1280 (depending on what you're encoding). If the source material is < 1280 pixels wide (SD content, etc) then just accept the default resolution the preset chooses (DVD content will play back at the correct aspect ratio). If the source material is = or > 1280 pixels wide, the preset will default to 960 pixels - change that to 1280 (for > 1280 wide) and it'll look fantastic.

Most likely you'll need to drop the audio down to simple 2-channel stereo, the recommendation is to use the AAC ffmpeg encoder at 160 Kbps or 128 Kbps if you want to save a few bytes (the size difference between a 128 Kbps and 160 Kbps audio stream will be fairly minimal; the 160 Kbps will offer better response so might as well just use that).

Or, if the material you want to encode already has AAC audio streams, just pass the audio through - that saves HandBrake the time and trouble of re-encoding already lossy audio and you end up with the exact audio stream taken from the source material but this only works if the source material HAS an AAC audio stream to begin with. There's an option to pass-thru MP3 audio streams as well.

Since the Nexus 7 isn't really designed to provide AC3/DTS capability for audio (5.1 or 7.1 soundtracks), there's no reason to encode or pass-thru such huge streams: encode it down to 128 or 160 Kbps AAC 2-channel stereo audio streams with the ffmpeg encoder.

MP4 or M4V is fine for the extension, either one will allow embedded captions/subtitles, or use MKV, doesn't really matter.

And the recommended media player for the Nexus 7 (at least my recommendation) is MX Player, there's nothing that can touch it.

These tips should get you some great looking videos. You can even make some minor adjustments like increasing the Reference frames to 5 and get slightly smaller video files in the long run as well.

But the basic iPhone 4 preset and adjusting the resolution to 1280 wide will give great results - you can of course just leave the resolution at the default of 960 pixels wide and it'll upscale beautifully on the Nexus 7 and you'll save a big chunk of space on the resulting encodes, like 25-35% in the end file size.

Hope this helps...

NOTE: HandBrake just updated again the other day, they're at 0.9.8 now so, if you're using an older build, it's a good idea to update to the most current one (the 0.9.7 release had some bugs they quashed pretty fast).
[Nexus 7 General] reggie14:
Let me just add one general warning. The iPhone 4 preset, along with the Android-high profile, use b-frames and other optional features in the H.264 that aren't necessarily supported on all Android devices. The Nexus 7 appears to deal with them fine, but as a general rule the iPhone 4 preset is not going to work on all Android devices.
[Nexus 7 General] br0adband:
Correct, and I was about to launch a very long post earlier but decided it's not worth the time or trouble.

Android devices with high resolution screens and made in the last ~18 months or so can handle the iPhone 4 preset without issues. My alteration to the preset is to increase the overall compression (using 5 Reference frames instead of the default 3 for the iPhone 4 preset) and also to adjust the Adaptive B-Frames to Optimal, that's about it on the Advanced tab.

I don't use the Android High preset because it requires me to alter more of the possible options than the iPhone 4 preset does (easier to adjust 2-3 options than 12).

Rest assured, the quad core Nexus 7 with the latest hardware decoder can handle any x264/h.264 options at this point in time.

This thread and this subforum ain't about all Android devices, it's about the Nexus 7 and everything posted so far is relevant to that device.
[Nexus 7 General] Eagle1337:
Tegra 3 doesn't like hi10p.
[Nexus 7 General] br0adband:
Hi10p only proves beneficial for one specific thing: anime or cartoon-type video content, and in the big picture it's pretty much irrelevant. It has a small community behind it - again, specifically anime fans - and that's fine but, in reality it's not a big enough "draw" (no pun intended) to bother with.

8-bit encoding with x264 looks just fine on the Nexus 7 and has no issues at all.
[Nexus 7 General] Eagle1337:
As side from the benefits in anime, the file size savings is really nice.
[Nexus 7 General] Hemidroids:
Handbrake

Regular Normal profile

H.264 for video

1000 Video Bitrate kbps (If you're starting with HD this bitrate is sufficient. about a gig per 2 hour movie)

Audio AAC (faac)

Gain 10

DRC 2.0

You can either setup handbrake to name it an mp4 instead of m4v or manually rename it to mp4.

You will be able to play with stock player.
[Nexus 7 General] zolo111:
I have never bothered to encode video files since I always owned devices that support mSD. But ever since I recieved this Nexus 7 as a gift ( HATE the no msd slot!!!!!) I thought it'd be a good idea to start encoding video files. I used handbrake (latest version), converted a 720p 1 hour game of thrones tv show episode, and I'm not impressed! I changed the resolution to 960X720, bit rate 1000, AAC FAAC stereo 128, Refrence Frame 5, Adaptive B-frame optimal, and all I ended up with was a 10mb difference in size (442mb to 433mb) :confused:
[Nexus 7 General] redmonke255:
Pretty much this, though I recommend changing horizontal pixels to 1280 and scale vertical accordingly. You can even scale down video bit rate on this device decently (if you're tight on space) because the high dpi helps hide compression artifacts.

Sent from my paranoid Nexus 7.
[Nexus 7 General] Entropy512:
The original file was probably already H.264 video.

Primary reasons to encode/transcode:

1) Reduce bitrate and resolution of 1080p Blu-Ray content

2) Change format of source files encoded in a way the device doesn't like

3) Use a more efficient codec than the source format while preserving the resolution (DVD encodes - H.264 is vastly superior to MPEG-2 so achieves major size reductions. Typically a 4.7GB DVD can be reduced to around 1GB of AVC+AAC at very high quality settings.)

On many devices, H.264 had better hardware acceleration than MPEG-4 ASP (aka DivX/Xvid) and most Android devices have far better support for the MPEG-4 container format than AVI - so it would be beneficial to transcode torrents that were ASP+MP3 AVIs.

However, many HD torrents are now AVC+AC3 MKVs. AC3 can be a problem, so can MKV, so usually when I do these transcodes I just transcode the audio using ffmpeg. Something like:

ffmpeg -i <infile.mkv> -acodec libfaac -ab 160k -ac 2 -vcodec copy <outfile.mp4>

Replaces AC-3 surround audio with 2-channel 160 kilobit AAC audio, and remuxes into an MPEG-4 stream.

Traditionally, 1 hour torrent releases were 700MB (1 CD) ASP+MP3 in an AVI container - However the scene seems to be moving from constant-size AVI encoding to constant-quality H.264+AAC MPEG-4 releases for standard definition content. 443MB for 1 hour sounds like one of these releases, which likely don't need any transcoding at all.
[Nexus 7 General] e.mote:
>ffmpeg -i <infile.mkv> -acodec libfaac -ab 160k -ac 2 -vcodec copy <outfile.mp4>

Has ffmpeg updated its AAC codec to be anything decent? I'm still using NeroAACenc.

Another ffmpeg issue is that last I checked (a year ago), it can mangle channel mapping for 5.1 audio, assuming you want 6ch AAC rather than stereo. I use ffmpeg for (some) demux, and straight x264 for video. There are better audio enc tools.

MPEG4-ASP isn't relevant any more, except to the few still stuck on obsolete playback hardware.

>the scene seems to be moving from constant-size AVI encoding to constant-quality H.264+AAC MPEG-4 releases for standard definition content.

I don't see that. Yes, peeps are moving to smaller-sized AVC encodes, but they're all still using 2-pass/fixed bitrate rather than 1-pass/fixed CRF.

BTW, for those with Win32 box and are interested in recoding/shrinking their vids, do try my x264 script below. Its forte is commandline efficiency with menu simplicity. It uses one-pass constant quality (CRF). You can vary the CRF.

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

---------- Post added at 05:01 PM ---------- Previous post was at 04:35 PM ----------

>I used handbrake (latest version), converted a 720p 1 hour game of thrones tv show episode, and I'm not impressed! I changed the resolution to 960X720, bit rate 1000, AAC FAAC stereo 128, Refrence Frame 5, Adaptive B-frame optimal, and all I ended up with was a 10mb difference in size (442mb to 433mb)

The 720p 1-hr vid is already using a low bitrate to achieve the 442MB size. By using an arbitrary bitrate--why 1000, because it's an even number?--you're both increasing the bitrate and decreasing the quality, by re-encoding it again and at lower resolution.

BTW, most HDTV vids are 16:9, which at 960 is 960x540.

Videos can have wildly varying bitrate requirements, so it's advisable to use constant quality, and let the encoder determine the bitrate. HB uses a default of CRF 20, which is overly generous. Low-bitrate encodes such as the above has a CRF-equivalent of 24-27 (higher CRF = softer detail = lower bitrate), so don't bother recoding those. For biggies, suggest the x264 default of CRF 23 to start out.
[Nexus 7 General] Entropy512:
AAC codec: Might be why if you use -acodec aac you get all sorts of warnings that you should really use libfaac instead - seems fine to me. That said my ears aren't particularly picky. NeroAACenc isn't really an option for me on a Linux box, and the above works fine for my use case.

Channel mapping: It seems to be downmixing fine, and as you see in my example, I told it to downmix to two channels. I haven't tested this in thorough detail, I need to find a good example of something with only rear channel audio to make sure the rear channels are getting mixed in. I don't encode to more than stereo AAC as I have nothing at all that can do anything useful with surround AAC - And there is no point in sending surround AAC to a Nexus 7 currently.

The "scene" using CBR 2-pass - I don't think they are any more for some newer releases - I'm seeing too much file size variance. It's not like the old days where files would be exactly 350MB or 700MB within a few kilobytes - I'm seeing up to 100MB of variation or more between releases even of the same show from the same group. That kinda screams CRF to me. Note that this is primarily TV shows from eztv - the movie "scene" may still be doing it oldskool.

Edit: Also, I find it highly unlikely that the person above actually had a 720p 1-hour episode. I've never seen a 720p TV release that small. Typically if it's around 440MB for a one hour video, that's a sign that it's a standard definition release.
[Nexus 7 General] e.mote:
NeroAACEnc is available for linux: ftp://ftp6.nero.com/tools/NeroDigitalAudio.zip

Re: Channel mapping - Yes, downmix works fine. The problem occurs when encoding to 6ch AAC, since AAC and AC3 (and DTS) all use different channel mapping, and ffmpeg doesn't remap them properly. You can try encoding the 5.1 AC3 test clip attached below. Each channel is verbalized out loud so you will know if it's correctly mapped.

Yes, it doesn't normally matter for tablets. But it would if you plug said tablet into a HDTV w/ hi-fi setup. OK, not the N7.

>The "scene" using CBR 2-pass

Admittedly I don't watch many vids nowaday, so you may be right. I usually do a mediainfo scan on stuff I watch to check their encoding params, and all the vids I see use 2-pass.

>unlikely that the person above actually had a 720p 1-hour episode. I've never seen a 720p TV release that small.

I've seen the Avengers 720p at 1.2GB, which is really low BR considering it's 2:22min long with lots of action scenes. Even at CRF 23 and just stereo AAC, my own 720p rip comes out to 1.8GB. It's typical for noobs to aim for a small fixed size and yet keeping the res high.

The result looks poor at close examination, but for casual viewing, it's actually fairly passable. At really low bitrates, the details are just softer rather than being pixellated as with ASP. For fast-motion scenes, it's hard to discern the detail loss. It's a testament to x264 encode quality.
[Nexus 7 General] zolo111:
Thanks Entropy512. You're right, I thought it'd be possible to further reduce the size since I wouldn't notice the picture quality difference on the 7" screen while I reduce the size by 20-25%. The scene already release a fantastic copy, size wise.
[Nexus 7 General] GizmoTheGreen:
anyone had any luck encoding a video at 1080p 60fps for the nexus 7, and in that case what codecs/settings?
[Nexus 7 General] e.mote:
>anyone had any luck encoding a video at 1080p 60fps for the nexus 7, and in that case what codecs/settings?

There's no difference for 60fps. Make sure the fps isn't set. The encoder should use the source's fps.

60fps is usually TV material, and can be frame-decimated (removing dupe frames) down to 30 or 24 for better compression efficiency. This is beyond the capabilities of most transcoders, however. You can simply keep it at 60fps. Just be aware that N7 won't be able to handle 60fps 1080p smoothly, and even 60fps 720p may be problematic.

A quick-and-dirty way to reduce 60 to 30 w/o smart frame-decimation is simply to drop every other frame. x264 has a "select_every" parameter for this, for those who use it. For HB users, you can set it as a custom parameter (since HB uses x264 as its encoding engine). For specifics, http://mewiki.project357.com/wiki/X264_Settings#select_every

Speaking of higher fps, I'm looking forward to see the Hobbit at 48fps. Videos are progressing to ever-higher spatial resolution. About time we get better temporal resolution as well.

For Handbrake users, know that HB has a nasty habit of converting CFR (constant framerate) sources to VFR. There's nothing you can do if you use HB. Just don't re-encode from a HB-coded source, or you may get audio async.
[Nexus 7 General] McMackson:
You can chose constant frame rate in Handbrake as well. It's just that they usually have variable frame rate as default option. And it should be no problem to re-encode from HB-coded source, just chose 'same as source' to preserve original time stamp information to avoid sync issues.

However, going from a truly VFR to CFR might be problematic. Typically one must preserve the original time stamp information to avoid sync issues, but given how variable they are, it might not be possible to fill in frames at a constant delta time without re-adjusting them. Would be interesting to know details how they implement such an algorithm.
[TouchPad Themes and Apps] BuffMcBigHuge:
Sixaxis is an app in the Google Play Store that allows you to use your PS3 Bluetooth controller as a controller for your Android Device.

Difficulty: EASY

Time: Approximately 5 minutes

The process:

Initial setup:

1) Download Sixaxis Controller - Google Play Store

2) Open the app, and in the bottom left corner, take note of the Local Bluetooth Address.

3) Use the Sixaxis Pair Tool to make the Master address of your controller as the Local Bluetooth Address mentioned above (Windows).

To use the app:

1) Open Sixaxis Controller

2) Click on Start

3) Wait until the app says "Listening for Controllers"

4) Press the PS button on the controller

5) Wait for "Client Connected: 1" to appear.

Notes:

To reconnect your controller to your PS3, simply plug it into the PS3 via USB and the Master MAC address will return to that of the PS3.

To turn off your controller, simply select "stop" in the Sixaxis App.

To set up touch profiles:

1) The touch profiles are located in the following folder on the SD Card.

SD Card\data\com.dancingpixelstudios.sixaxiscontroller\profiles

2) Download the following .map files and place them in the above mentioned folder (If you are browsing this website on your tablet, simply download the .map, and use RootExplorer to copy and paste them from "/SD Card/downloads" to the folder above.

3) Set the Active Touch Profile as the game you are playing!

I have created some Sixaxis Touch Profiles for certain games I play often on the Touchpad.

Note that I have made the following Touch Profiles the way I like to play the games. If you want to modify the sensitivity or button layout, simply click on the settings button in Sixaxis at the top right, >> Preferences >> Touch Emulation >> Edit Touch Profiles >>, then double tap, >> Load Profile, and dive right in!

Download the Touch Profiles below:

Dead Trigger

N.O.V.A. 3

N64oid

Max Payne

Amazing Spider Man

Sonic (ep 1 or 2)

I will try and add more in the near future. Please hit 'Thanks' if I have helped you out. Cheers! :cool:
[TouchPad Themes and Apps] Ghosteri7:
Say What? OMG you are the best. thanks a lot.

Can you maybe do: The dark night rises and dead space?

THANKS!
[TouchPad Themes and Apps] mafu6:
I was looking for something like this.. i searched the forums and many other devices have threads like this... great work... i will share some of mine when i manage to get hold of a cable that charges my controller... currently in a remote loaction!
[TouchPad Themes and Apps] BuffMcBigHuge:
I cannot get the Dark Knight Rises to work, and I have yet to try Deadspace on Android. Maybe you guys can put some profiles together?

When it comes to the Right Analog, make sure to change the button properties to "relative" and "wrap mode". Play around with it, you'll see why.
[TouchPad Themes and Apps] cf3esbestia:
Awesome thread. However, Dead trigger and Max Payne already have native gamepad support. I love using my DS3 with Dead trigger.