yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Themes and Apps] guitmz:
new version coming soon with ringtone/alarm/notification support!
[Nexus 5 Themes and Apps] guitmz:
You can now set any sound as notification/alarm/ringtone! Get it from Play Store :)
[Motorola Droid Android Development] laufersteppenwolf:
Dear Developers

I'm sure you already heard about the GPL around the forums. In case you did not, the GPL ("GNU General Public License") is the most common license that affects many projects, like the Linux Kernel (the Linux Kernel is licensed under the GPLv2). This affects us, XDA and its members, as we are often working with the Linux Kernel (every Android platform runs on top of the Linux Kernel).

You may ask yourself now "Well, that's nice, but how does this affect me and what does the GPL do?" The answer is pretty simple actually: The GPL guarantees users to examine, modify and share their and others code by enforcing open-sourceness. This means you are free to use any GPL'ed sourcecode for your project, but you must make your used code publically available again.

Now, as many advantages this has, it also means quite some work for us developers. All used sources must be completely public by the time the compiled binary (like a Kernel) goes online. Another requirement is, that the OP must include all information to compile the exact same binary as uploaded by the developer. This means you need to specify:

The used toolchain including its version (linking to your toolchain source is always a good idea)

The used defconfig

The link to your sourcecode (including the used branch, tags,...)

If used, also upload your scripts used for the compilation

If you upload a kernel, publish the source, but the source is not compilable, it means you are breaking the GPL as you did not release the used source. Breaking the GPL actually means breaking the law, which means the sanctions on XDA could possibly be the least of your problems...

Example:

@ROM devs, using a precompiled kernel

As you are not compiling the kernel yourself, you do not have to give the above information. However, you have to link to the source of your kernel binary (for example: link to the OP of the used kernel). If you use the stock kernel, you must state this. Linking to the stock sources is not a requirement, but it is not the worst idea.

Keep in mind; if the kernel used is not GPL compliant, your ROM is not GPL compliant either. This may cause your thread to be closed and/or further action on your account may be taken.

Example:

If you need/want further information, you might want to take a look at THIS news article written by our Developer Admin pulser_g2
[Motorola Milestone Android Development] laufersteppenwolf:
Dear Developers

I'm sure you already heard about the GPL around the forums. In case you did not, the GPL ("GNU General Public License") is the most common license that affects many projects, like the Linux Kernel (the Linux Kernel is licensed under the GPLv2). This affects us, XDA and its members, as we are often working with the Linux Kernel (every Android platform runs on top of the Linux Kernel).

You may ask yourself now "Well, that's nice, but how does this affect me and what does the GPL do?" The answer is pretty simple actually: The GPL guarantees users to examine, modify and share their and others code by enforcing open-sourceness. This means you are free to use any GPL'ed sourcecode for your project, but you must make your used code publically available again.

Now, as many advantages this has, it also means quite some work for us developers. All used sources must be completely public by the time the compiled binary (like a Kernel) goes online. Another requirement is, that the OP must include all information to compile the exact same binary as uploaded by the developer. This means you need to specify:

The used toolchain including its version (linking to your toolchain source is always a good idea)

The used defconfig

The link to your sourcecode (including the used branch, tags,...)

If used, also upload your scripts used for the compilation

If you upload a kernel, publish the source, but the source is not compilable, it means you are breaking the GPL as you did not release the used source. Breaking the GPL actually means breaking the law, which means the sanctions on XDA could possibly be the least of your problems...

Example:

@ROM devs, using a precompiled kernel

As you are not compiling the kernel yourself, you do not have to give the above information. However, you have to link to the source of your kernel binary (for example: link to the OP of the used kernel). If you use the stock kernel, you must state this. Linking to the stock sources is not a requirement, but it is not the worst idea.

Keep in mind; if the kernel used is not GPL compliant, your ROM is not GPL compliant either. This may cause your thread to be closed and/or further action on your account may be taken.

Example:

If you need/want further information, you might want to take a look at THIS news article written by our Developer Admin pulser_g2
[Droid Pro Android Development] laufersteppenwolf:
Dear Developers

I'm sure you already heard about the GPL around the forums. In case you did not, the GPL ("GNU General Public License") is the most common license that affects many projects, like the Linux Kernel (the Linux Kernel is licensed under the GPLv2). This affects us, XDA and its members, as we are often working with the Linux Kernel (every Android platform runs on top of the Linux Kernel).

You may ask yourself now "Well, that's nice, but how does this affect me and what does the GPL do?" The answer is pretty simple actually: The GPL guarantees users to examine, modify and share their and others code by enforcing open-sourceness. This means you are free to use any GPL'ed sourcecode for your project, but you must make your used code publically available again.

Now, as many advantages this has, it also means quite some work for us developers. All used sources must be completely public by the time the compiled binary (like a Kernel) goes online. Another requirement is, that the OP must include all information to compile the exact same binary as uploaded by the developer. This means you need to specify:

The used toolchain including its version (linking to your toolchain source is always a good idea)

The used defconfig

The link to your sourcecode (including the used branch, tags,...)

If used, also upload your scripts used for the compilation

If you upload a kernel, publish the source, but the source is not compilable, it means you are breaking the GPL as you did not release the used source. Breaking the GPL actually means breaking the law, which means the sanctions on XDA could possibly be the least of your problems...

Example:

@ROM devs, using a precompiled kernel

As you are not compiling the kernel yourself, you do not have to give the above information. However, you have to link to the source of your kernel binary (for example: link to the OP of the used kernel). If you use the stock kernel, you must state this. Linking to the stock sources is not a requirement, but it is not the worst idea.

Keep in mind; if the kernel used is not GPL compliant, your ROM is not GPL compliant either. This may cause your thread to be closed and/or further action on your account may be taken.

Example:

If you need/want further information, you might want to take a look at THIS news article written by our Developer Admin pulser_g2
[Droid X Android Development] laufersteppenwolf:
Dear Developers

I'm sure you already heard about the GPL around the forums. In case you did not, the GPL ("GNU General Public License") is the most common license that affects many projects, like the Linux Kernel (the Linux Kernel is licensed under the GPLv2). This affects us, XDA and its members, as we are often working with the Linux Kernel (every Android platform runs on top of the Linux Kernel).

You may ask yourself now "Well, that's nice, but how does this affect me and what does the GPL do?" The answer is pretty simple actually: The GPL guarantees users to examine, modify and share their and others code by enforcing open-sourceness. This means you are free to use any GPL'ed sourcecode for your project, but you must make your used code publically available again.

Now, as many advantages this has, it also means quite some work for us developers. All used sources must be completely public by the time the compiled binary (like a Kernel) goes online. Another requirement is, that the OP must include all information to compile the exact same binary as uploaded by the developer. This means you need to specify:

The used toolchain including its version (linking to your toolchain source is always a good idea)

The used defconfig

The link to your sourcecode (including the used branch, tags,...)

If used, also upload your scripts used for the compilation

If you upload a kernel, publish the source, but the source is not compilable, it means you are breaking the GPL as you did not release the used source. Breaking the GPL actually means breaking the law, which means the sanctions on XDA could possibly be the least of your problems...

Example:

@ROM devs, using a precompiled kernel

As you are not compiling the kernel yourself, you do not have to give the above information. However, you have to link to the source of your kernel binary (for example: link to the OP of the used kernel). If you use the stock kernel, you must state this. Linking to the stock sources is not a requirement, but it is not the worst idea.

Keep in mind; if the kernel used is not GPL compliant, your ROM is not GPL compliant either. This may cause your thread to be closed and/or further action on your account may be taken.

Example:

If you need/want further information, you might want to take a look at THIS news article written by our Developer Admin pulser_g2
[Galaxy S 5 Q&A, Help & Troubleshooting] Kelter:
Good afternoon all!

I'm well-aware of the "search before you post" mentality of this forum, and I apologize if these questions have been answered correctly elsewhere - I'm seeing conflicting information :(

I'm new to the Galaxy S5 (SM-G900V), moving from the Galaxy S3 (running Hyperdrive V16), and I'm hoping to root my phone to gain some of the features that I had previously (with the most important being unlocked tethering). However, I'm reading in different sources that it's safe to root/not safe to root, safe to unlock/not safe to unlock (and that there isn't even an unlocked bootloader for the Verizon variant), etc. I'm hoping to put these rumors to rest by asking the following questions simply:

Is it currently safe to root the SM-G900V variant of the Galaxy S5?

Is it currently safe (or possible) to unlock the bootloader for the SM-G900V variant of the Galaxy S5?

If the above are true, what is your favorite recommendation for a person who is interested in a stock, rooted, deodexed experience?

Thanks to all of you for your hard work developing, and for the information! :good:
[Galaxy S 5 Q&A, Help & Troubleshooting] gridflash:
This is the thread you want to search: http://xdaforums.com/showthread.php?t=2783157&highlight=sm-g900v

Towel root will work on the SM G900V but the bootloader is still locked, so no custom recovery but SU and Titanium work fine
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] Gaijin42:
When looking at my Titanium settings, the backup location is set to /storage/emulated/legacy/TitaniumBackup

This seems to match instructions from various sites (can't post links yet, otherwise I would link them!) and other places.

However, I believe this location is on my internal storage, and not the SD card.

When attached via USB, I see the files at \\This PC\SAMSUNG-SM-G900V\Phone\TitaniumBackup and not in \\This PC\SAMSUNG-SM-G900V\Card

It seems like the location should be somewhere under /storage/extSdCard/Android but everywhere says "this folder is not writable"

It also seems like this is being subtracted from my 16BG, as in Settings/Storage I have 9gb of "miscellaneous files" of which 2.98gb is "TitaniumBackup"

Help?
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] Mansquared:
Kitkat is made that you cannot write to your sdcard so if you are rooted you can just download an app from playstore...I used one called nextapp sdfix...hope thay helped
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] nmarietta:
You must enable the system to write to your sdcard. Check out this thread located in Android Development

http://xdaforums.com/showthread.php?t=2784011
[Motorola Photon Q 4G LTE] laufersteppenwolf:
Dear Developers

I'm sure you already heard about the GPL around the forums. In case you did not, the GPL ("GNU General Public License") is the most common license that affects many projects, like the Linux Kernel (the Linux Kernel is licensed under the GPLv2). This affects us, XDA and its members, as we are often working with the Linux Kernel (every Android platform runs on top of the Linux Kernel).

You may ask yourself now "Well, that's nice, but how does this affect me and what does the GPL do?" The answer is pretty simple actually: The GPL guarantees users to examine, modify and share their and others code by enforcing open-sourceness. This means you are free to use any GPL'ed sourcecode for your project, but you must make your used code publically available again.

Now, as many advantages this has, it also means quite some work for us developers. All used sources must be completely public by the time the compiled binary (like a Kernel) goes online. Another requirement is, that the OP must include all information to compile the exact same binary as uploaded by the developer. This means you need to specify:

The used toolchain including its version (linking to your toolchain source is always a good idea)

The used defconfig

The link to your sourcecode (including the used branch, tags,...)

If used, also upload your scripts used for the compilation

If you upload a kernel, publish the source, but the source is not compilable, it means you are breaking the GPL as you did not release the used source. Breaking the GPL actually means breaking the law, which means the sanctions on XDA could possibly be the least of your problems...

Example:

@ROM devs, using a precompiled kernel

As you are not compiling the kernel yourself, you do not have to give the above information. However, you have to link to the source of your kernel binary (for example: link to the OP of the used kernel). If you use the stock kernel, you must state this. Linking to the stock sources is not a requirement, but it is not the worst idea.

Keep in mind; if the kernel used is not GPL compliant, your ROM is not GPL compliant either. This may cause your thread to be closed and/or further action on your account may be taken.

Example:

If you need/want further information, you might want to take a look at THIS news article written by our Developer Admin pulser_g2
[Optimus L3, L5, L7 Android Development] laufersteppenwolf:
Dear Developers

I'm sure you already heard about the GPL around the forums. In case you did not, the GPL ("GNU General Public License") is the most common license that affects many projects, like the Linux Kernel (the Linux Kernel is licensed under the GPLv2). This affects us, XDA and its members, as we are often working with the Linux Kernel (every Android platform runs on top of the Linux Kernel).

You may ask yourself now "Well, that's nice, but how does this affect me and what does the GPL do?" The answer is pretty simple actually: The GPL guarantees users to examine, modify and share their and others code by enforcing open-sourceness. This means you are free to use any GPL'ed sourcecode for your project, but you must make your used code publically available again.

Now, as many advantages this has, it also means quite some work for us developers. All used sources must be completely public by the time the compiled binary (like a Kernel) goes online. Another requirement is, that the OP must include all information to compile the exact same binary as uploaded by the developer. This means you need to specify:

The used toolchain including its version (linking to your toolchain source is always a good idea)

The used defconfig

The link to your sourcecode (including the used branch, tags,...)

If used, also upload your scripts used for the compilation

If you upload a kernel, publish the source, but the source is not compilable, it means you are breaking the GPL as you did not release the used source. Breaking the GPL actually means breaking the law, which means the sanctions on XDA could possibly be the least of your problems...

Example:

@ROM devs, using a precompiled kernel

As you are not compiling the kernel yourself, you do not have to give the above information. However, you have to link to the source of your kernel binary (for example: link to the OP of the used kernel). If you use the stock kernel, you must state this. Linking to the stock sources is not a requirement, but it is not the worst idea.

Keep in mind; if the kernel used is not GPL compliant, your ROM is not GPL compliant either. This may cause your thread to be closed and/or further action on your account may be taken.

Example:

If you need/want further information, you might want to take a look at THIS news article written by our Developer Admin pulser_g2
[Galaxy Tab 4 Q&A, Help & Troubleshooting] macbroom:
Does anyone with a Tab 4 have HDMI out working and if so which cable/adapter are you using?

I have ordered a cheap ebay cable for a Tab 3 8.0/10.1 that is supposed to have the Samsung 11 pin MLH usb plug. Does the Tab 4 use the same 11 pin jack as the Tab 3? I also saw a post here about screen mirroring for the 7.0 but nobody answered....the specs for both the Tab 3 7 and Tab 4 7 on the Samsung site show NO screen mirroring, only 8.0 and 10.1. That fact alone leads me to believe the Tab 3 cable will work.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] raitchison:
I tried it with a monoprice adapter and it did not work, I did not spend too much time messing with it though,

I think the screen mirroring built in is via DLNA to a Smart TV or other DLNA receiver.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] macbroom:
The specs say wired HDMI also so I am hoping the Tab 3 cable works. Is your adaper 5 pin or 11 pin, powered or unpowered. From what I have been reading the cable MUST be plugged in to USB power in addition to the tab for it to work. This is the one I have on order.

http://www.ebay.ca/itm/151312595134?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649
[Galaxy Tab 4 Q&A, Help & Troubleshooting] raitchison:
Yeah my adapter is powered but I did not have it plugged into USB. I'll try it again.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] imeem:
So does the Tab 4 (specificly the 8.0) support HDMI out? I notice that the US website and Best Buy mentions HDMI, but the canadian samsung website doesn't mention it.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] macbroom:
The MLH cable I got from China does NOT work. I do have hope for the future. There are no HDMI adapters available from Samsung at this time even though they say wired HDMI is supported with an adapter that they have not made available yet! I believe the hardware support is there but it is not implemented in the TouchWiz software.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] mjay3000:
Hi I tried several adapters ordered by Amazon including this one Samsung ET-H10FAUWEGWW but no chance of getting HDMI a signal out.

Therefore I contacted Samsung using the Smart Tutor app of samsung and unfortunately after remote examining the device, they confirmed that

MHL is NO

T supported by this device. However this might apply only to the European versions.

So what, now I am so disappointed?! Does anybody know if Samsung maybe deactivated this feature in their ROMs, if so maybe we could get

HDMI out with a custom ROM in the future.

kind regards

Mjay
[Galaxy Tab 4 Q&A, Help & Troubleshooting] ke7vng:
My first post!

I had this chat with a Samsung specialist a few weeks ago:

info: Please wait for a Samsung Agent to respond.

info: You are now chatting with 'Shawn'. There will be a brief survey at the end of our chat to share feedback on my performance today.

info: Your Issue ID for this chat is LTK1125601075630X

Shawn: Hi, thanks for reaching out to Samsung pre sales support. We appreciate your interest in Samsung products. How may I assist you today?

Visitor: I am wondering which of the tablets support HDMI output

Shawn: I understand that you are looking for the TVs that support HDMI output. Certainly, I will help you with the information.

Visitor: Not tvs that support HDMI, but Tables, such as the galaxy tab 4 10.1

Visitor: i mean tablets

Shawn: Sorry for the mis-communication.

Visitor: no problem

Shawn: You could use the HDMI adapter with Tab 4 10.1.

Visitor: Which adapter? None of the adapters that i have found say they specifically support that model. Plus, as I I trying to decide twich model (7, 8, or 10 inch, I am not able to find out which models support HDMI, and the adapter that is required

Shawn: Please check the below link for compatible devices that support the HDMI adapter which is used to connect the Tab to the TV.

Shawn: go to Samsung dot com /us/mobile/galaxy-tab-accessories/ET-H10FAUWEGUJ-compatible

Shawn: Are you able to access the above link?

Visitor: Yes. If it states that it is compatible with the tab 3, does that mean it is also compatible with the tab 4? The tab 4 is not listed.

Shawn: Tab 4 has been recently released. Hence, it isn't listed under the compatible devices. It should also support the adapter.

Visitor: ok, thanks

Shawn: You're welcome. Is there anything else that I can assist you with?

Visitor: No, that is all, thanks again

Shawn: Thanks for chatting with Samsung Support. If you have a minute, please click on the blue ?X close? button to receive the transcript of your chat and fill out a brief survey to help us serve you better.

Follow Samsung Service on Facebook, Twitter and YouTube.

info: Chat session has been terminated by the Samsung Agent.

You have to be careful in choosing an adapter for these. The following one did NOT work for my tab 4 10.1:

Go to amazon dot com/gp/product/B00ESM3Q7K/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1

But this one specifically says it does, and comments seem to confirm it:

Go to amazon com/gp/product/B00KGP5SEC/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1

I have one on order, and I will post my results when I get it and try it.

Eric
[Galaxy Tab 4 Q&A, Help & Troubleshooting] macbroom:
I wish you luck with the second cable you mentioned, but I read all 24 pages of reviews for it and the Tab 4 is not mentioned as working in any review. Half the reviews say it doesn't even work with the devices listed!

Most CS staff have very little technical knowledge. I would not put one bit of faith in a CS rep saying, oh it's not listed in the adapter specs but it should work...lol.

I would lay odds that wired HDMI out is not implemented in the kernel we have now. There are a few reports here that people lost wired HDMI out on Tab 3 after the Kit Kat update.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] ke7vng:
Well, I would think that the tab 4 would be supported as the tab 3 was, but that is why I am getting the cheap adapter rather than the official Samsung one (that one is around $75 on Amazon, but $35-$39 elsewhere). Having been in IT, I have found that most of the problems that people have are self induced, i.e. they did not read the instructions, or took shortcuts. It is worth noting that there seems to be two Samsung MHL adapters, one for the phones and one for the tablets. I do not know why they would do that, it does not make sense to me, as it causes too much confusion.

Eric