Request Sources for SM-P607T (T-Mobile) - Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl

Hi,
I noticed that the vast majority of people own the P605 and there are already numerous kernel mods out for it, with progress being made on rooting on 5.1.1. The P607T however does not seem to have that many users and so are forced to flash their devices with a custom kernel made for the P605. While this seems to be working, its not ideal and so I contacted Samsung Open Source and requested the sources for the P607T so that we can make our own kernel mods and what not. Turns out, this actually does work, and I just received a reply from them as below:
"Dear Customer,
Thank you for your interest in our product.
We are now in the process of reviewing your inquiry.
We will let you know a reply to this issue soon.
Sincerely yours,
"
I made the request from http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView . I imagine we will see the sources out much faster if more P607T users went and posted a request as well. And hey, maybe the enthusiasts of the P605 world want to help their brethren out Calling all xda Note 10.1 users to go and request Samsung for the sources to the 5.1.1 Lollipop ROM for the P607T.

Wow, they just released the sources! Got this from them:
Dear Customer,
We are pleased to provide you the source code of SM-P607T.
You can download the source code from the site below: http://opensource.samsung.com
Thank you.
Sincerely yours,
Samsung OSRC Team
You can now download the source from here!

Related

Zopo: Request to release the kernel source code

Dear Zopo fans ,
I start this new thread because I've read that the developers are angry with many Chinese manufacturers because thay not release the kernel source code for their phones.
With your help, perhaps, we could change that situation and help the developers to develop new Rom or fix any bugs.
How? Quite simply!
For anyone who has a Facebook account:
Click " Like" on the official page of Zopo :
https://www.facebook.com/officialzopo?fref=ts
Then copy this message (if anyone knows a better English of mine, I am ready to change it):
Dear Zopo with this message I ask you to release the source code of the kernel of your mobile phones.
This demand stems from the repute many developers would be Helped to develop new ROM or fix any bugs.
In addition, I am sure, that the release of the source code and therefore the support of the community of XDA Developers, greatly increase the volume of your sales.
With the hope that this request does not fall on deaf ears, I wish you a good day .
Click to expand...
Click to collapse
and paste it in the Zopo official page.
For those who did not have a facebook account, there are other methods.
Go to the official page of Zopo, in the section contact us : http://zopomobile.cn/contact-us/
Or write a reply message in this topic present in their official forum : http://zopomobile.cn/forum/viewtopic.php?f=4&t=372&p=1732#p1732
When in doubt, made ​​the request in all three ways
I hope that you will give your support to this project !
Hi guys!
There is a good news!!!
Zopo have reply to us!!!
And today...
Any news of Source code of zopo prodcts??? From Zp998 waiting....

petition for jiayu to publish repositories

Dear Jiayu S3 hardware/software development department,
First of all, thanks for making the marvelous Jiayu S3 device and
providing software updates.
There is an enthusiastic XDA community dedicated to the Jiayu S3 with
'tag' jiayu-s3 : http://forum.xda-developers.com/t/jiayu-s3
This thread named 'petition for jiayu to publish repositories' is
created to ask you if you can make an agreement with Jiayu
management to make source code repository for kernel source available,
and, to ask you if you can also make the necessary vendor and device
repositories available for building firmware (especially custom
firmware such as e.g. cyanogenmod and aosp).
Please, if these repositories can be made available, also include
necessary patches and instructions to build kernel and firmware
e.g. cyanogenmod and aosp.
Other vendors have contributed to better linux kernel and android
firmware that way and we would be proud if we can say Jiayu does the
same. Especially for the new 64 bit architecture starting with
Lollipop.
Looking forward to positive response.
It seems this thread has outlived its usefulness, as I just deleted 25 garbage posts by forum users that should know better than to spam a thread. Be glad I don't have the time or patience to dole out infractions to every person that posted here. On that note........
Thread closed

How to become Maintainer for Lineage OS?

Hello,
I want to become maintainer for Lineage OS for specific device (I will buy the device to maintain).
Could someone plz explain me the process of becoming the maintainer and pre-requisites for it?
I had a look at teamoctos/join-our-team/ but it will be helpful if someone explains all those steps in it.
--
Thanks
I'm not sure about this but however:
First of all you will have to build device tree for that device (I guess that device isn't supported at the moment, if is than you can contribute to that repo on github via pull requests and wait for them to approve change) and that device tree works without lethal bugs. Also you'll need kernel that won't make you much troubles because manufacturer probably published sources (they had to). And when you make it work than you can try to conntact them about joining team, if they accept new devs, because I read somwhere about how to make CM support device officialy they mention only they support devices they own, they not mention anything about joining team if I remember well. It's best that you conntact them and ask I'm sure there is way for that.
alpesh.valia said:
Hello,
I want to become maintainer for Lineage OS for specific device (I will buy the device to maintain).
Could someone plz explain me the process of becoming the maintainer and pre-requisites for it?
I had a look at teamoctos/join-our-team/ but it will be helpful if someone explains all those steps in it.
--
Thanks
Click to expand...
Click to collapse
Unless a specific thread states otherwise (which will provide you with the individual or location to do so), the XDA Forums isn't where you request this.
Regarding the Official LineageOS, though, the XDA Forums isn't where you request this either, here's the only location (at this time) to where you can find what you're looking for.
1) Go to the following link:
http://wiki.lineageos.org/faq.html
2) Scroll down to the following question (without quotes):
"My device is not officially supported, but I’d really like to give LineageOS a try. Can you support my device?"
3) It is there that you'll find the information you're looking for as well as the E-Mail address to where you can send them the information.
Good Luck!
Sent from my SCH-I535 using XDA Free mobile app

Android 10 or 11 for Samsung S5 mini

Dear Forum,
meanwhile is there a version (lineage or whatever)available which can be applied to a Samsung S5 mini?
I am always struggling, cause the posts are mostly for Samsung S5 and when reading there is no list included which type
of S5 it is working on. I think a better specification in the posts wpould help a lot.
Thank you very much
I'ts all there: https://forum.xda-developers.com/f/galaxy-s5-mini-android-development.3300/
The threads are marked with either g800f or g800h!
Reason for no Android 10: https://forum.xda-developers.com/t/...os-16-0-beta-10-02-2021.3868612/post-84460579
How did anyone get on A11?!
LineageOS Statistics
stats.lineageos.org
possibility 1:
people are trolling and just randomly changing versions
possibility 2:
trees for A10 and A11 exist and they are unknown to us
I have found these trees which seem to be Q, but they give me "ran out of inodes" error

TWRP Realme C15 ROOT user

How to install twrp from official TWRP App
after rebooting just wait for the black screen, don't panic, it's the boot process
The TWRP.img You gave is Compiled By me for realme C11/12, Since realme C11/12/15 ( mtk Edition ) are same it worked in C15 & I know About that, Please try to Give Credits to original Owner of the Compiled ROM/Recovery, I've verified md5 checksum too, its same, Edit The post with proper credits, Thanks
@bass_deso THREAD CLOSED and the formerly attached twrp.img removed.
It seems you haven't credited the original developer of the recovery that you posted. Even if it had been your development TWRP is licensed under GPLv3 i.e. you were required to provide a link to your source.
Please advise the moderaors team (best via the report function) to re-open the thread when ready to credit the devloper of the TWRP and to mention where you obtained it from. If the original location does not obtain a link to source you'd be required to provide that link.
XDA Forum Rules (excerpt):
...
12. Sharing
XDA-Developers is based on the principle of sharing to transmit knowledge. This is the cornerstone of our site. Our members and developers freely share their experience, knowledge, and finished works with the rest of the community to promote growth within the developer community, and to encourage those still learning to become better. There are those, however, who take advantage of this model and try to make personal gains from the hard work of others.
In order to preserve the delicate balance between sharing for the good of the community and blatant self-promotion, regular members and developers alike must understand (and agree) to the following:
12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
12.2. Courtesy - While most of the work released on our site falls under the umbrella of open source, that is not the only license model being used by developers on xda-developers. In order to prevent problems, we ask that if you decide to base your work on someone else's that you check the license model being used (as it might not be as permissive as one may think);
12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
12.4. Developers can issue take down requests (by contacting the Dev Relations team) under the following circumstances:
- in-process builds start showing up on forums when the developer is not yet ready to release the work;
- cases in which another developer is too aggressively soliciting donations or misrepresenting the work (kanging);
- unofficial builds where an official build is already available;
In summary, we want people to have access to work and knowledge alike. Sharing is good and courtesy and ethics go a long way.
Developers with questions, comments, complaints, or concerns about our rules (or anything!) should send a PM to our Dev Relations team (efrant or to a Moderator. We are here to help!
...
Click to expand...
Click to collapse

Categories

Resources