yashsingh1/xdaforums huggingface dataset:
[Galaxy Grand Prime Original Android Development] Perseus:
Just wanted to clarify what the differences are between android and original development. Here are some KEY points by our very own pulser_g2.

The following are most likely “Original Development”:

*Official releases of highly original and upstream custom ROMs (built from the ground up with significant original development within them

*Official releases/development of such original ROMs, perhaps posted by the maintainer or their nominated person.

*A significant “first” in development for a device. Significant is subjective, but it is likely something which took considerable time/effort, and is generally accepted by developers to be significant and non-trivial.

*Kernels which are built with beneficial changes that are not simply pulled from other kernels already available. Some element of original work is expected.

*ROMs where the developer has made a custom kernel for it.

*Tools and utilities with a clear purpose, and which are well-made, and useful to users. They should have an element of originality, either in purpose or through significant improvement in the means of operation.

*Significant port of a ROM from one device to another, giving enhanced features or functionality to users of the target device. The port should be beneficial (a port from two virtually identical devices isn’t original development, it’s winzipping, and nobody really benefits from this, as it’s not development)

The following are most likely not “Original Development”, and should be posted in the “Android Development” subforum:

*Your own “unofficial” stock build of your favorite original, source-built (or otherwise) ROM, particularly where an official or maintainer-endorsed thread exists already.

*Minor derivatives of other ROMs with little or no changes, or ROMs consisting of “placebo” features as a main constituent or claim.

*Renames or rebadges of others’ work – these don’t belong on XDA at all! Refer to rule 12 for more information.

*Reposts of existing ROMs with small changes (i.e. kitchen work, such as adding a couple of apps). If you could realistically distribute your changes as an “addon pack” above and beyond a ROM, you should do so. In addition, your “ROM” would not be original development as it would be substantially identical to the original ROM.

*A thread created with unrealistic goals that are clearly unachievable by those starting the thread. This is not intended to discourage high aspirations, rather to prevent threads porting Windows Phone 8 to the HTC Wallaby. This is pretty much common sense.

*A ROM where a main or significant claim/feature is graphical changes to the user interface (ie. Themed ROM)

You can find all the info for it here. Threads will be moved if they do not meet the "Original" development requirements. Thank you and have fun! :highfive:
[Galaxy S 5 Q&A, Help & Troubleshooting] gordyt77:
Hello all, first off apologies if this has been answered... If it has I can't find it...so here goes..the wife's galasxy s5 had the lollipop update...as we all know Samsung jumped the gun....the phone over a few days got worse for screen freezing and random off and on...until eventually it got caught in a bootloop...

I tried to data/factory reset but the menu list wasn't there just a blue message saying booting recovery..

So after taking the battery out for 5,10 then 30 min for the same thing to happen.

I then decided (stupidly) to use Odin (I've used it a lot over the years) and flash the original ROM from sammobile...(yes I can get to the download screen).Odin says reset after flashing, phone resets and again it bootloops....not sure if the Knox was tripped at this point however after a bit more research and other tutorials I realised I tried to install an unlocked version not one tied to 02...so o found the o2 one from sammobile...went through it all again and still nothing... Bootloop.....so I tried again but this time i tried to root it using Odin...again it said it worked...I assume it did because I received another menu lines at the booting recover one in red and one in yellow...however it still boot loops....I then try flashing ROM again and still boot loops....boot loops.....boot loops.....I put custom ROM back on and go to Samsung repair shop as the devices is less than a year old...to be told the knox is tripped sorry....please can someone point me in the right direction as to what I can do with this phone now....
[Galaxy S 5 Q&A, Help & Troubleshooting] qubbus:
Something is wrong with your keyboard, dot key is stuck or something? :laugh::laugh::laugh:

Did you even try to do Factory Reset after flashing firmware dedicated to your phone?

To do this - flash STOCK firmware via ODIN again. It phone get into bootloop again - pull out battery.

Then wait 30 seconds and enter to STOCK recovery - VOL+ + HOME + POWER (Almost the same like download mode but instead vol- is vol+) and do format data and format cache few times.
[Galaxy S 5 Q&A, Help & Troubleshooting] gordyt77:
Thanks for the reply, unfortunately there is no menu at the stock recovery just a blue message saying booting recovery...it then goes into bootloop again.

And removing batt for 30 sec...
[8525, TyTN, MDA Vario II, JasJam General] power2rule:
i am total novice so pardon me if i ask some stupid question =s

I am using Vodafone V1605 with standard rom 1.20.161.6

i have been trying since ages to pair my bluetooth stereo headset (SAMSUNG SBH-100) with my V1605 but phone doesnt find the headset when i search for bluetooth devices.

do i need to upgrade rom or something or what is the actual problem, can anyone help me Please!
[8525, TyTN, MDA Vario II, JasJam General] AnyMal:
I hate to ask the obvious, but did you put your headset into discovery mode? :D
[8525, TyTN, MDA Vario II, JasJam General] stukes:
No. First make sure your headset is in Pairing MODE. Usually the led will be ON solid or BLINKING very fast. Some have a different color to show if they are in PAIRING MODE. Then turn on the phones bluetooth and add a new paired device. If it does not show up then either the headset is not in pairing MODE or it is not working properly. Hope this helps you.:)
[Shield Android Development] Steel01:
DISCONTINUED

Do not use this recovery anymore. It breaks with update 103. Instead, use the TWRP provide in the MultiROM thread. It's newer, works with update 103, and shouldn't have any trouble with the older versions either.

~------------------------------------------------------------------------------------------------------------------------------------------------------------------~

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

Tablet look:

INSTRUCTIONS:

Boot into fastboot by holding back and home when powering on the Shield.

Connect Shield to a computer via USB.

Execute 'fastboot flash recovery recovery.img' from a command line.

DOWNLOAD:

Android File Host

BUGS:

Ask in this thread. It's probably my fault and not upstreams.

KNOWN PROBLEMS:

This is build from Tassadars multirom branch. This is because he has code to rotate the display that isn't upstream.

However, I disabled multirom because I haven't quite got it to work yet. The button is still there, but it does nothing.

SOURCE CODE:

https://github.com/Tegra4/android_device_nvidia_roth/tree/cm-12.0-mrom

SPECIAL MENTION:

Bogdacutu for rm-wrapper. Originally created to get touch working for the Shield Tablet and Ubuntu, it was also able to be used for TWRP. And the setup for the Portable is so similar that the program was able to be used here as well.

XDA:DevDB Information

TWRP Roth, Tool/Utility for the Nvidia Shield

Contributors

Steel01, Unjustified Dev

Version Information

Status: Testing

Created 2015-02-28

Last Updated 2015-07-25
[Shield Android Development] Spleeno:
finally, I could never stand cwm on my shield...

first thing I noticed though, I cant change timezone in settings -> timezone (the liste is just empty)

also, the buttons seem to only use like 3/4 of the screen - but only in the main menu/ button dominated view - the moment I pick a option that displays filelists its fullscreen.

besides those bugs it seems to run just fine, thx a bunch ;)
[Shield Android Development] r3pwn:
A while ago [MENTION=4911249]Unjustified Dev[/MENTION] said that this would be impossible. I'm glad that it was eventually figured out. :)
[Shield Android Development] stab244:
Can anyone apply themes? I'm trying to use the material twrp theme but it doesn't seem to work.

Edit: Figured it out. The theme only works in portrait. Guess I'll ask the theme dev to see if he can fix.

Sent from my bacon
[Shield Android Development] Steel01:
Yeah, that would have been my first guess. On the topic of themes, I picked the closest one TWRP had which was 1280x800. As mentioned above, that has the main screen icons really small. If someone can make or find a theme that is 1280x720 with larger buttons, it would help a lot.
[Shield Android Development] YamazakiRobert:
i have a question , i previous have a n8000 with have native support twrp team and the device is 720p and the icons on screen are better sized and use portrait orientation

if possible take a look on p4noterf (n80xx) or on p31xx maybe they have some useful stuff for us.

sorry im no dev but if you tell me what do i have to seaarch im happy too help
[Shield Android Development] Steel01:
The difference is portrait vs. landscape. There is a portrait 720x1280 skin, but not a landscape 1280x720. This device is practically unusable in portrait layout, so the theme needs to be landscape. Which it seems there isn't a lot of. As for how to make or modify a theme, someone else will have to answer. I haven't ever looked into it.
[Shield Android Development] AltCtrl701:
Thanks for the work. Will multirom eventually be ported also?
[Shield Android Development] Steel01:
I'm trying, but it isn't going so well. Main problem is that the kernel patch doesn't work right. It reboot to the right kernel, but the wrong initrd. Which means it's unusable. Secondary problems are the touch input not lining up and the gamepad buttons not working. The latter should be simple to fix, though.

Another problem I'm having with twrp in general is size. The portable only has a 8 MB recovery partition. Recent compiles weight in around 10 MB, 8.3 MB with lzma compression. I have to remove all the optional twrp bits and back out ntfs-3g from Tasssadars fork to make 2.8.6.0 barely fit. I expect this to get worse as time goes on.
[Shield Android Development] brianakapple@gmail.com:
What's it do for development of android users
[Fire TV Q&A, Help & Troubleshooting] jashang87:
I saw so many ads online for live channels and movies (including indian channels) but they sell for a lot and doesn't provide any replacement warranty if something happens to the device and they can access this remotely (which I am not comfortable with as they will get access to my home network). So I decided to get the fire tv by myself. I got the version which can be rooted (I didn't open it yet).

Can someone guide me how can I add those indian live channels or should I return it and get the one selling online (already set-up)?

Here's the links for online ones:

https://www.youtube.com/watch?v=xu_Nvt7ccSM#t=44

http://www.ebay.com/itm/Amazon-Fire...EATURES-NOT-AVAILABLE-ON-OTHERS-/121575225981

Any help is appreciated.
[Fire TV Q&A, Help & Troubleshooting] navigates:
you could subscribe to Dishworld and use that login with slingtv app. It works very well and they give it for $14.95 for the first three months. you can also go back and you will get hd. If you are not based in the US, you could use unlocator which works very well.
[Fire TV Q&A, Help & Troubleshooting] jashang87:
Thanks for pointing that out, thats $44.99+$24.99 per month (after first 3 months) for the channels I am looking for. I am trying to cut the costs thats why I want to set up xbmc on fire tv.
[Fire TV Q&A, Help & Troubleshooting] navigates:
After 3 months its $44.99. Whats the 24.99? Are those for english sling? you don't have to get that. And after three call and cancel and they will probably match the 14.99 again. Good luck with xbmc on firetv. I've tried those in the past and those are nothing more than a pain. if even they work.
[Fire TV Q&A, Help & Troubleshooting] imtiaz78:
This is great.

I did not realize the sling TV apps works for Dish world.

I have tried side loading the dishworld app but the remote did not work well on that.

Thanks navigates..repped u
[Fire TV Q&A, Help & Troubleshooting] navigates:
That's cool. I too tried it out and was glad to see it work.
[Shield Android Development] Steel01:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.

/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for CyanogenMod is available in the CyanogenMod Github Repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.

Instructions:

1. First time flashing CyanogenMod 13.0 your device, or coming from another ROM?

2. Download the zip(s).

3. Install a compatible Recovery

4. Perform a NANDroid backup of your current ROM (Optional)

5. Wipe data & cache partitions of your device

6. Flash CyanogenMod.

7. Optional: Install the Google Apps addon package.

Firmware Update:

If you have not installed the latest stock ota, then some firmware files need updated. The following flashable zips will update the bootloader and the dtb corresponding with the listed stock version. Only the latest one listed here will be supported by recent CM builds.

106

Official Nightly Downloads:

get.cm

GAPPS

Unofficial Downloads with Nvidia App Support (CM 12.1):

20151003

Bugreport:

Report in this thread. CM's JIRA is only for stable builds, which I have not released.

Known Problems:

Only the power button seems to wake the device.

Wireless controller doesn't work.

Source Code:

https://github.com/CM-Shield/android_device_nvidia_roth

https://github.com/CM-Shield/android_kernel_nvidia_roth

XDA:DevDB Information

CM13.0 Unofficial Roth, ROM for the Nvidia Shield

Contributors

Steel01, Unjustified Dev

ROM OS Version: 6.0.x Marshmallow

ROM Kernel: Linux 3.4.x

Based On: CyanogenMod

Version Information

Status: Nightly

Created 2015-02-28

Last Updated 2016-03-15
[Shield Android Development] Spleeno:
sweet - since I'm not using most of the quicksettings on the stock shield I can finally get rid of most of them without installing xposed and gravity box...

but right now its missing the buttons-menu in the settings - so you cant configure the power menu or any of that stuff.

still, the bootup time is amazing on this thing compared to stock...
[Shield Android Development] r3pwn:
Sweet! Does this have the stuff I sent to [MENTION=4911249]Unjustified Dev[/MENTION]? (Setting volume button as volume down)
[Shield Android Development] Steel01:
No, this build does nothing with the volume button. What I'd like to see it do is bring up the volume widget without changing the volume which would be as similar to stock as I can figure, but I don't see a way to do that. You can change that pretty easily locally, if you want that on your install.

[MENTION=4853574]Spleeno[/MENTION]: I expect that has to do with upstream cm. I didn't turn off any settins and I don't think Unjustified Dev did either. I know upstream was still working on forward porting all of 11's features last I looked. I don't know where they're at on that now.
[Shield Android Development] r3pwn:
Also, if it helps at all, it's possible to disable the LED by running (as root) "echo 0 > /sys/class/leds/roth-led/brightness". (This was a setting on stock, not sure if you guys want to re-add it in.)

I had mine set to Volume down for a couple reasons:

1. When tapped once, it would pull up the volume menu (and lower volume by one step, but not a huge issue)

2. When held with the power button, it takes a screenshot (that's what happened on stock, too)

3. Holding it down mutes it, if for some reason you needed to quickly mute the device.
[Shield Android Development] Steel01:
For the first, I'd want to leave that to user choice. Wonder how hard it would be to add that to the settings section. Can you even add setting pages from the device tree without modifying upstream?

On the second, you might have me convinced there. I'll change it on mine next time I'm poking at it. And will probably change it in the tree unless something weird pops out.

There's several more things I want to look at porting over. Console mode looks to be really easy. At least in basic form. There's a couple props to force hdmi only and resolution. Only problem is if the cable is unplugged, it wont automatically switch back over. The wireless controller is another, but more difficult. I got the apps to run, but they errored out. I have a couple more ideas to try, but haven't got there yet. Took a break over the weekend, but should be back at it tomorrow night.
[Shield Android Development] r3pwn:
I'm not sure. I'll have to take a look. Anything is possible with overlays, though, right? :P

Absolute worst case scenario, I'll make an app with a few misc. things like this to gain some functionality back from stock.

And while we're in the spirit of discussing rom-related components, I have a bug report: Attempting to use Nvidia's GRID Streaming service results in only the audio going through. (Not sure if that affects PC streaming, as my PC is nowhere near powerful enough to test)

And also,

There seems to be some weird issue with storage. Either apps aren't getting moved to the sdcard when told or the system is factoring them into the internal storage space calculation anyways. (I'll get back to you on this one, it isn't too hard to test to figure it out.)

Alright. No rush, take as long of a break as you need!
[Shield Android Development] Spleeno:
Hm, I'm running the 20150223 cm12 nightly on my z3 compact and it already has the button menu - I wouldnt have expected/noticed with some of the early january builds ofc :p
[Shield Android Development] Steel01:
So I started a proper post with quotes and all, but the android keyboard or textbox edit thing in Firefox did something weird and ate my post. And there's no undo... So this is my shorter and more miffed second attempt.

[MENTION=4853574]Spleeno[/MENTION]: My bad, I see that on my Nexus 5 now. I'll compare my dev tree with the N5's and see what the difference in that area is.

[MENTION=4732871]r3pwn[/MENTION]: On the Grid issue: I confirmed that this morning, but didn't have much time to look at the logs. I saw something about missing codecs, but that was at the top and maybe not related. I'll look more into it tonight. It could well be a worse underlying problem.
[Shield Android Development] YamazakiRobert:
[MENTION=1416222]Steel01[/MENTION] man thanks so much for your initiative, i'm happy to see a custom rom o my shield and its working great, i have tested with retroarch nightly and ppsspp nightly and its working awesome.

if its possible until you define the function to volume button i think you can change from program_red to button_select to at least we can use on the emulators

another thing i have noticed the volume button on original shield rom is 109 on you rom is 183

thanks for your time and thanks so much for the custom rom!

update:

other things i have noticed

when we make a fresh installation the shield don't have the mtp option checked

we have a vibration option on sound menu (i dont know if this make some erros on system if enable/disable)

if the kernel have the option Prism from nvidia its possible to put on display using the adaptive brightness ( /sys/class/graphics/fb0/device/smartdimmer/enable)

thanks again
[Shield Android Development] r3pwn:
I looked at the sdcard issue. It appears that only the app is getting transferred over,not any obbs that belong to the app. You can move those manually, but that's not very user-friendly. :P
[Shield Android Development] Steel01:
Okay, I've been chasing this grid problem around most of the night... Finally got a lead when I gave up and started trying to mess with the controller stuff again. Apparently the Grid service want to use stuff from the main Nvidia control service. Which is embedded in the stock build and not open source. I was able to pull the apks (NvCPLSvc and the controller related NvBlakeManager and BlakePairing) from my Shield Tablet (already on lollipop), resign them with CM's keys and get them to run. Once NvCPLSvc was happy, the logs related to Grid stuff look a lot more similar to what I get on my stock tablet, but still no dice. It's getting stuck in the queue. Dunno if I'll make any more progress on that tonight or not, but I'm a lot closer.

On the controller front, at least it's more obvious what the problem is. Nvidia modified the wireless p2p stuff in the android framework. Some functions that blake calls don't exist in CM and causes the service to bomb. I'm playing with a diff between the aosp tree and CM. Should be able to get get a sane one tonight and run off a build to see how much further I can get. Then the question will be if I can magically add the changes to the device tree or if they would have to be submitted to upstream CM or Google which isn't likely to get merged.

[MENTION=751788]YamazakiRobert[/MENTION]:

The mtp part could be due to some testing we were doing and trying to get adb up when cm wasn't booting. I'll check when I'm working on the device tree again.

I doubt turning on vibrate would damage anything since there isn't any hardware for it. But I agree the option shouldn't be there. More things to add to the device tree list.

That smartdimmer path is there on this build and is enabled by default. Though, I haven't seen any effects like adaptive brightness. That feature drives me nuts and is one of the first things I turn off on a phone reinstall... But, I'll look into enabling auto brightness in CM. Should be able to find that in the N5 tree as well.

[MENTION=4732871]r3pwn[/MENTION]:

Creating a open source control app would probably be the easiest way to go. Control things like the leds, console mode, etc. If someone could figure out what blake is actually doing under the hood, it would be nice to get away from those stock programs as well. But I didn't have a whole lot of luck with deciphering that a few weeks ago. But it's looking like NvCPLSvc will have to stick around if people want Grid access, which is unfortunate.

The transfer problem sounds like an upstream issue or even on-purpose decision. Does this work on other CM ports?

Edit: Ugh. The wifi framework stuff appears to have been refactored between 4.4 and 5.0. Got the patch cleaned up and applied and stuff overlaps and isn't found and all kinds of fun. I probably should have pulled all this from the tablet aosp. Guess I'll try that angle tomorrow.
[Shield Android Development] -woczarder-:
Thank you for this majestic piece of work.

I'm going to build a shrine with your username when you'll make a working CM12 with GRID.

:D