[Project] OmniRom 4.4.4 bq Curie - General Omni Discussion

Hi all developers, I wish I could port OmniRom 4.4.4 to the "bq Curie" tablet (from bq, spanish brand), but between all bq tablets, the "Curie" is the most difficult to work with. We (EngelProjektDroid) have ported this wonderful rom to almost all bq tablets, and we want "Curie" users to enjoy it too.
We ask you developers or computer engineers to help us with this hard "fight". "Curie" users are almost the most abandoned users in development,
and because of that I request your knowledge, because as I have understood, we all are one.
We will give access to the main sources of our git concerning the Curie and give directions that are needed or that I can best offer to you.
Here you have the dmesg and the logcat: https: //docs.google . com/file/d/0BwyzeSh2fR-oc3BSWlNPeDY4S00/edit (Join the parts of the link, sorry :S)
My sincere gratitude to all who help out and I think in this case I can speak for the whole community of this humble tablet.
Here are some links of our web and our work, thanks! (I'll post them better when the forum allow me, sorry :S, only join the parts of the link )
Forum: https ://epdcenter . es/foro/
Main web: https ://epdcenter . es
However, if you want, you can contact me on this mail: [email protected]

DavidMarcosEPD said:
Hi all developers, I wish I could port OmniRom 4.4.4 to the "bq Curie" tablet (from bq, spanish brand), but between all bq tablets, the "Curie" is the most difficult to work with. We (EngelProjektDroid) have ported this wonderful rom to almost all bq tablets, and we want "Curie" users to enjoy it too.
We ask you developers or computer engineers to help us with this hard "fight". "Curie" users are almost the most abandoned users in development,
and because of that I request your knowledge, because as I have understood, we all are one.
We will give access to the main sources of our git concerning the Curie and give directions that are needed or that I can best offer to you.
Here you have the dmesg and the logcat: https: //docs.google . com/file/d/0BwyzeSh2fR-oc3BSWlNPeDY4S00/edit (Join the parts of the link, sorry :S)
My sincere gratitude to all who help out and I think in this case I can speak for the whole community of this humble tablet.
Here are some links of our web and our work, thanks! (I'll post them better when the forum allow me, sorry :S, only join the parts of the link )
Forum: https ://epdcenter . es/foro/
Main web: https ://epdcenter . es
However, if you want, you can contact me on this mail: [email protected]
Click to expand...
Click to collapse
Since it sounds like you MIGHT be a developer asking general bringup questions, I'll refrain from reporting this one. (However, per the FAQ, Omni support requests are supposed to go to the device-specific community for your device.)
Since you haven't even been able to provide critical information about your device (such as exactly which CPU it has), we can't help you. Just as a warning: If it has a MediaTek CPU, there is basically no hope of support. If it's Rockchip, it's highly unlikely. If it's Allwinner, it's slightly more likely but Allwinner's media codecs have made supporting even that chip difficult.

Entropy512 said:
Since it sounds like you MIGHT be a developer asking general bringup questions, I'll refrain from reporting this one. (However, per the FAQ, Omni support requests are supposed to go to the device-specific community for your device.)
Since you haven't even been able to provide critical information about your device (such as exactly which CPU it has), we can't help you. Just as a warning: If it has a MediaTek CPU, there is basically no hope of support. If it's Rockchip, it's highly unlikely. If it's Allwinner, it's slightly more likely but Allwinner's media codecs have made supporting even that chip difficult.
Click to expand...
Click to collapse
Yes, we're a developing team (EngelProjektDroid), but we aren't asking for support for this device.
We are looking for developers to help us to port the Omnirom (unnoficcially) to this RockChip tablet.
If it isn't the place where I have to put this thread, tell me where it has to be and I'll move it.
The tablet is RockChip rk3066,with Mali-400

Is it easy to install a rom? I have that tablet (BQ Curie). Mine has 2 memories to install apps (a primary one with 2GB) and a second with 12GB...

Related

Need the help for the main developer of CM for L90 (Quarx)

Hello our friends abroad.
Just sorry for my english.
Used Google translator.​
To confirm the veracity of this post, you can ask about this very Quarx​
To develop a new Сyanogenmod based on Android M it is necessary to collect a certain amount to the acquisition for LG L90 developer.
We consider the purchase of a new device, but in any case it is necessary to talk about the amount of not less than 10 000 rubles.
The development will be engaged Quarx, author CM 11-12.1. Continue to update the CM is also possible, but the conditions were not discussed.
The device will remain in Quarx as payment for development. Start developing - off the release date of a new version of the CM.
As the author would be pleased at the expense of financial support for his work and the constant support of 12.1
For more information about CM: https://ru.wikipedia.org/wiki/CyanogenMod​**** Purse out on the development of CM ****
Regarding http://vk.com/wall-67828971_73142
Payment can be made at:
Yandex money
- "410012810651169"
Qiwi
- "+380991580348"
At this time that was collected:
Total: 5 458.58 rub.
Left to collect: 4 541.42 rub.
Links to our developer "Quarx2k", which is engaged in the development and support of 11-12.1 cm at the moment.
Quarx
Quarx2k site where you can see his work.
http://quarx2k.ru/
Payment to:
Truhan Kirill Sergeyevich
In comments to the payment be sure to specify your login on 4pda or XDA and the comment "tax on the phone!" Also, please write me in private message the amount, that you transfered, and i will post it on 4pda and here. The country should know its heroes.
respkirya (4PDA)
respkirya (XDA)
If you do not find yourself in this list, but made the payment - please contact http://vk.com/ukrainian_drift
All reports will be kept here http://vk.com/topic-67828971_32404538
P.S. The author of this post respkirya, I'm just posted, because i have amount of posted messages to create thread.
How about you let Quarx handle his own affairs?
toastgodsupreme said:
How about you let Quarx handle his own affairs?
Click to expand...
Click to collapse
What are you talking about?
So, no reaction? This is the crowdfunding some of you were asking to create

..

..
Can you share only the front flash fix please and also the link that you share is not working thanks in advance
Delete
Download link not working enlace de descarga no funciona revisa por favor.
Delete
this fix was not you that did, and you were not allowed to use it. the real developer name is @Bode327
@MikeChannon
gabrielunm said:
Add IT in xlm file of camera.
system/cameradate/camera-feacture-v8.xml
Or use IT magisk module
https://drive.google.com/file/d/1YYGa2S2UlcQekO6JZSLq9XScBH4W1KDQ/view?usp=drivesdk
Click to expand...
Click to collapse
Man, you did not solve any problem, you are using third party material to gain advantage, In your YouTube video where you explain downgrade from oreo to nougat. the script and the rom that you are using are mine, because the error 11 I left on purpose. Be a man and take or give credit to devs.
[email protected] said:
this fix was not you that did, and you were not allowed to use it. the real developer name is @Bode327
@MikeChannon
Click to expand...
Click to collapse
It's true who did was Bode327.
First of all, the MAGISK module that you have published as your own was created by me, according to the rules, to be able to promote and use, you should have given credits and thanks to me!
Whois the Developer for Rom Optimized Oreo V6 for J7p?
Mod Edit
May I remind everyone of the XDA RULES
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 sykopompos) or to a Moderator. We are here to help!
Please read these carefully.
malybru
Senior Moderator
NiCaARRecho said:
Whois the Developer for Rom Optimized Oreo V6 for J7p?
Click to expand...
Click to collapse
Yes
Sent from my on7xelte using XDA Labs

[CLOSED] [Discussion] TheRagingBeast Kernel: A totally baised community

I joined trb telegram gp and was totally amazed with the charging speed 2000-2100ma consistent at any temp. Then after a while noticed temp rises to whoping 47-48C contantly. Then I compared trb to pbh in the group in this good manner
Trb= Fast charging with 47C temp
Any other kernal= Ok charge speed with temp 43C max(in pb*). The trade off are equivalent trb not so gr8 as I thought.. Then a member told bb is not good then i shared charging speed of pbh in response to an admin telling pbh is bad(yes an admin talked and continue chat about pbh after all he is admin) vai screenshot and got fban immediately yes just shared the pic and after that fban from the group no warning no rules at all. Once in PE I was using no username so the admin warned me twice and third time they gave me 5 min. See the difference totally baised community even trb is closed sourced that's why thier thread is closed. And their every download link has tons and tons of ads.
BTW my thanks meter is just 1 cuz never asked anyone
TRB CLOSED THREAD LINK go and see what moderate reason were for closer https://forum.xda-developers.com/asus-zenfone-max-pro-m1/development/kernel-theragingbeast-derpgang-t3862835/page6
They were redirecting to telegram gp so that they can monetize vai their ****ty download links
XDA is not a place to discuss about Telegram groups, whether the group is good, or bad.
Okay
1. Why dont u ask other kernel cookers to get such speed
2. So when u r noob lemme tell asus P blobs are also responsible for heat, so go and complain about it to asus
3. When u share ss of our group u may need to provide proof of other kernels too. Common sense
4. Our thread was closed by mods because we didn't provide source because it was reported by so called m1 devs. So when u r not aware of such things dont try to get involved.
5. You are not forced to use this or that kernel infact roms too. No need to post such useless **** like this on xda platform.
6. Urs concerns barely effect us because we work based on our satisfaction not yours.
7. Try to learn about kernel before placing such useless **** like battery performance. We gave freedom to users to set what they want
8. Finally u say above ton community biased ??? I left to ur wisdom this one.
Thanks
Don't bring outside matters into XDA.
1. This is not the right platform to discuss this.
2. Never compare any ROM/Kernel... Developers make things according to their liking and they do not get paid for this.
Dude xda is xda and telegram is telegram.
Don't ever refer other platforms for issues here.
Also did you pay the developer to build a specific piece of software for you? If you didn't then you can't complain what they give you for free. If you use their software then thank them for giving their services for free.
Also no two developers are same TRB Developers can make their kernel as they want they did not came to you, you used their product for free.
If you like Pbh then be happy and don't compare kernels and roms each have their own set of modifications and features.
If you face a issue with any software which is free to you, you can only suggest the developer hoping it gets fixed. You can not demand anything from them according to your likings.
If you want everything you want hire developers and then you can have whatever you want. But if you use free stuff be grateful and thankful.
You bought the device from Asus and paid them go and complain to their devs don't cry on xda and telegram.
Hope this clears things up and teaches you what android developers do for you.
See the attachment first.
z1_nile said:
Dude xda is xda and telegram is telegram.
Don't ever refer other platforms for issues here.
Also did you pay the developer to build a specific piece of software for you? If you didn't then you can't complain what they give you for free. If you use their software then thank them for giving their services for free.
Also no two developers are same TRB Developers can make their kernel as they want they did not came to you, you used their product for free.
If you like Pbh then be happy and don't compare kernels and roms each have their own set of modifications and features.
If you face a issue with any software which is free to you, you can only suggest the developer hoping it gets fixed. You can not demand anything from them according to your likings.
If you want everything you want hire developers and then you can have whatever you want. But if you use free stuff be grateful and thankful.
You bought the device from Asus and paid them go and complain to their devs don't cry on xda and telegram.
Hope this clears things up and teaches you what android developers do for you.
Click to expand...
Click to collapse
If you read correctly the whole thing is how they banned me and how they reacted when I asked for justification
Hello,
As per our rule 15, this thread topic is irrelevant to this section.
15. Keep threads / posts on-topic
15. Keep threads / posts on-topic
Whilst a minor amount of off-topic posting may be overlooked, the general rule is that your posts / threads must be relevant to the Forum / thread in which you are posting.
General Forums - For news and announcements relating to your device.
Q&A Help & Troubleshooting Forums - For all question / request threads and posts. If there is no Q&A Help & Troubleshooting forum, use the General Forum of the relevant device
Accessories Forum - For posts related to accessories relevant to the device
Development Forums (ones with the word development in the title) - For Developers to post release threads e.g. ROMs and Kernels including modifications to kernels, bootloaders, ROMs, etc., as well as R&D development discussion threads designed with an end goal
Themes and Apps Forums - For the posting of Themes and / or Apps as well as announcements & discussions including modifications made to Themes and Apps.
Thread closed.
Jerry
Forum Moderator

[CLOSED][LOS 18.1] Real System Optimization

Hello there,
It's me again ...
What's New ?
Well ... I have made a full package for LineageOS 18.1 to take you in the next level !
Features
- Full ramdisk optimization : reworked from scratch (of course)
=>
. improve CPU/GPU & Memory management
. no lags, no freeze & no random reboot
. super smooth UX
. thermal protection : no throttling & no more overheating ... unless if you are a heavy gamer !
. ultra powersaving mode in deep-sleep
- improve also :
. Wi-Fi connectvity (screen-off playback)
. Camera in low-light
. Sound/Video recording
- Faster FP scanner
- Stock offline charging animation
- SafetyNet Fix included
F.A.Q :
Q/ using this mod the first time ?
A/ you format /data partition ... unless if you have flashed the SafetyNet fix already !
Q/ do i have to reinstall everytime i update my LOS ?
A/ yes, because it's not a Magisk module, otherwise the build fingerprint in /data will have a conflict with your LOS one , and the system will crash !
THIS IS A MOD THREAD
A.K.A
SYSTEM MODIFICATION
THE MAIN GOAL
IS
PERFECTION
THIS IS AN ADVANCED MOD LIKE YOU HAVE NEVER SEEN BEFORE
DON'T TRY TO CHANGE SOMETHING BY YOURSELF :
EACH PARAMETER IS RELATED TO ANOTHER ONE
" TAKE IT OR LEAVE IT "
&
DON'T COPY WITHOUT PERMISSION
***
TROLLS & NOOBS
STAY AWAY PLEASE
{Mod edit}​
Reserved
2021-10-17 Highly Recommended
- let cleanup some trash = remove "XiaomiParts" :
. heavy battery eater in the background even if it is disabled [Proximity Sensor = always ON !!!]
. framework badly implemented by LineageOS : the handwave gesture was dropped a long time ago by many OEMs (Google included) ... and it's not working here after a deep-sleep ! (check by yourself)
- msm_irqbalance.conf : tiny update / huge effect
- disable scoped storage aka "fuse" = bring back sdcardfs alive !
Your phone will restart itself once, due to the virtualization switch from fuse to sdcardfs ... so don't worry ! Enjoy
2021-10-16
- initial release
gringo80 said:
Q/ using this mod the first time ?
A/ you format /data partition
Click to expand...
Click to collapse
Sorry for noob question, is this for new LOS installation only? Won't I loose my current apps if I format data with my current LOS?
sturges said:
Sorry for noob question, is this for new LOS installation only? Won't I loose my current apps if I format data with my current LOS?
Click to expand...
Click to collapse
Yes, but if you have already applied this SafetyNet Fix : No ! (This is the main reason)
Moderator Information | Thread Locked for Clean-up
MODERATOR NOTICE | THREAD RE-OPENED
I have cleaned the thread. Please take a moment to review the forum rules especially section 2 about language and respecting other forum members. Don't forget that you agreed to keep these rules when you signed up.
This back and forth between a couple of users in this thread is childish & this kind of conversation has no place on XDA. Some of the recent posts here are users blaming each other and some defending them. This is not a playground.
This is a Courtesy Warning !!
Please do not engage in this type of activity & keep the thread solely for the purpose of topic discussion, not for off-topic chit chat, or exchanging insults and personal jabs at other users. Should this disregard for the forum rules continue, further action against the involved will be taken which may lead to the account being reviewed for restriction or removal.
Let's keep the discussion clean on any issues moving forward.
Thank you for your consideration,
Funk Wizard
Forum Moderator
Soon change acc to paradox
gringo80 said:
2021-10-17
[...]
- disable scoped storage aka " fuse" = bring back sdcardfs alive !
Click to expand...
Click to collapse
Does this means full read/write access to externalSD/USB-OTG? Cause it doesn't fully work on a different Xiaomi device I own (also on LOS)...
pnin said:
Does this means full read/write access to externalSD/USB-OTG? Cause it doesn't fully work on a different Xiaomi device I own (also on LOS)...
Click to expand...
Click to collapse
Yes ... and i have made also a Magisk module for this, not limited to POCO X3 [NFC] but all devices with A11 !
Check the specific thread for more information !
gringo80 said:
Yes ... and i have made also a Magisk module for this, not limited to POCO X3 [NFC] but all devices with A11 !
Check the specific thread for more information !
Click to expand...
Click to collapse
I see, thanks; so it's only for A11. Bummer!
Was expecting it to finally solve a problem I am having with another device, which is running A10 (more info at your module thread).
** WARNING LONG POST **
I spent some time to review this.
There are two replaced executables:
- charger
- init
The charger binary is replaced for the offline charging animation, i believe. But i didn't diffed with official charger bin as author do not disclose which MIUI it comes from. So it might be original or it might be modified i don't know.
The init replacement is more critical, probably related to the safetynet fix, but i would be personally concerned to run such binary on my phone unless full source to it is released by author.
All the main props files have been modified and a few things come to my attention.
The build is still abused as "official lineageOS build" by buildkite and such, which it is not at this point, so this would be a concern, even if more an ethical one, since people could report issues as "official" build while it's not an official build anymore.
Also, quite a few graphical props are changed / enabled when they have been not enabled on purpose on official build for stability concerns. So YMMV, but you could get crashes.
All build fingerprints have been changed with respect to official, which is probably related to the safetynet fix. This might lead to problems when Google will change things again, and users of this mod will probably have troubles using magisk or any other safetynet fix unless clean flash again. This patch does also change your crypto keys and make your data lost. But this has been advertised by the author, so you know.
There are a lot of modified init rc files, going trough them all is difficult here, but a few things come to my attention.
In a few files security permissions have been relaxed. Some additional permissions have been granted to camera, audio and other subsystems, the reason for this should be explained.
Also quite some /sys and /dev nodes permissions have been changed to make them less secure.
Systemwide stats collection and tuning have been altered in various places, again i see no direct reason for this.
It is my overall impression that the author took some init file from a different device and/or BSP and kind of copied it on the official ones. Not clear to what purpose.
There are massive changes to the mount schema and procedures, probably linked to the removal of "scoped storage", which is there for a reason so YMMV to accepting this change, specially if it is so widespread in the system.
There are lots of small tuning to CPU and governor, there is messing up with the nice levels and file descriptors, something which should not taken lightly and probably would need deep testing on some benchmark to prove that they actually work beside the placebo effect.
Moving on.
The media profiles, audio codecs and settings, have been modified with at least a couple of changes that are known for having caused issues with various apps in the past.
This is more or less the most of it. I have spent way too much time on this analysis at this point, but i did it as this might impact directly the support i give to the community on official LineageOS 18.1 for surya if anybody flashes it and then report issues.
I can see some improvements which would be good for official build too like some cleanup of probably useless init stuff (leftovers from davinci or generic sm6150) and such.
Unfortunately, providing one mega-patch like this with no underlying github repository to track changes and meaningful commit history to justify each one of them make this entire work useless, which is a pity. I strongly suggest the author to read up how to contribute to the android development community so that the good in his work can actually be of benefit for everybody, as he benefitted from the work of many like we all have.
I have also seen various lines that are actually authorship by somebody else, i suggest the author to spend some time identifying them and, after creating a repository for the patch, repo-pick those patches with the correct metadata. This is a time consuming activity, but a necessary one, as you all can understand, so that a real community can function. Just to be clear: it's the duty of who publish stuff to ensure it does not infringe others authorship's, not the other way around.
I suggest the author (i mean the real person behind his many accounts) to understand how the open source android development community works so that the good in his work can be actually benefit the community. There is good in his doing, it's only the ways that make it difficult to be actually used.
(note: i crossposted this on the official LOS for surya thread as well, because this is also related to that thread and might cause issues for users there)
STAY AWAY FROM THIS MOD!! I just flashed it in my LOS install and my phone was instantly bricked! I couldn't reboot back into LOS after the official update today! All my data is lost, i have to do a full restore via miflash then install LOS again. I'll never use this mod again!
{Mod edit: Quoted post has been removed}
Read OP in RED COLOR !
I don't understand, people don't like this work and keep coming from everywhere.
WHAT'S WRONG WITH YOU ALL ... NOT WITH ME. I DIDN'T INVITE ANYONE.
THIS IS NOT A MANDATORY VACCINE !​
To any troll here,
Any fake issue ... your comment will be reported. So don't waste your time with me.
Thanks
gringo80 said:
Read OP in RED COLOR !
I don't understand, people don't like this work and keep coming from everywhere.
WHAT'S WRONG WITH YOU ALL ... NOT WITH ME. I DIDN'T INVITE ANYONE.
THIS IS NOT A MANDATORY VACCINE !​
To any troll here,
Any fake issue ... your comment will be reported. So don't waste your time with me.
Thanks
by gringo80,
THE GOD OF CREATION
All rights reserved © 2021
Click to expand...
Click to collapse
You made my day, ROTFL
And i am still waiting for a technical reply to my questions.
{Mod edit: Quoted post has been removed}
1. Can you share the source code for your modified init binary?
2. Can you detail the reason for the various relax of security and permissions in your patch?
3. Why are you forcing "official" build status in the props within the mod, if this will not be an "official" build after your mod is applied?
4. Why did you changed the build fingerprints?
5. To what end did you changed stats collection stuff in your patch?
6. Which is the source from you took the various init scripts modifications? Is it stock? BSP? A different device? Or they all your work?
7. Why did you removed the "scoped storage"?
8. Do you have benchmarks and/or screenshots proving actual improvements with your patch applied?
9. why don't you organize your work so that it can be of benefit to the community?
10. Have you checked if any of this work has previous authorship?
There you go, these are more or less all the questione for you.
Moderator Announcement
It's a pity that this thread required cleaning again after it was already conducted by a moderator just 3 days ago. And even an administrator engaged before I provisionally closed the thread above. First, at no point language and behaviour that violate the standards for member conduct as stipulated in rule no. 2 of the XDA Forum Rules is accepted and acceptable. Nobody is granted permission to violate the rules, doesn't matter if long time member or just joined, just user of the gratefully provided development or developer, doesn't matter if visitor to a thread or author of a thread.
While we love and encourage vivid discussions, exchange of arguments, knowledge, experience and technical information we can't and won't except if this derails into rants and fights. And certainly everybody is able to support us on this way. For example, if somebody believes or even knows for sure that other's work has been re-released don't post this "accusation" in the thread but follow our request from rule no. 12, contact the Developer Relation Team (DRT; refer to the team members here) with evidence and let the DRT do its job. Especially if it's obvious by moderator announcements in a thread that the thread has been or is under observation, please refrain from further posts that add fuel to the fire but simply report, contact a moderator of your desire or directly the DRT.
But back to the vivid discussions: We expect that especially development threads are professionally handled. And this not only means that the author of the thread provides support in the thread and doesn't point the XDA members to whatever social media but more important that brick reports are immediately taken very seriously, that every effort is shown to support restoration of a device and that future bricks are avoided to the maximum extend. And if a devlopment or development solution is questioned by reasonable information and questions, it can not only it must be expected that these information and questions are seriously and professionally discussed and answered with mutual respect. Why shouldn't we execute on XDA what we do in real life, in our businesses and professions?
@gringo80 I've removed the attachment from the OP and keep the thread closed. Please advise the moderators team to re-open the thread when you are ready to seriously deal with the asked questions, the reports of bricked devices and to discuss the information challenging your product. Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator

HI

I work as a publisher to post exclusive things for free​If I have an apple and you have an apple, we both have one apple, and if I give you my apple and you give me yours, we each have an apple and nothing changes But if I had an idea and you had an idea and I gave you my idea and I took your idea from you, then each of us has two ideas. This is the rule by which I live.​
Greetings and welcome to XDA. Please take a moment to review the Forum Rules. XDA thrives on the sharing of ideas; however, we must be respectful of each others' work. Therefore, I would like to point out some specific items:
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;
Click to expand...
Click to collapse
As a rule of thumb, it's always good form to ask permission before you use someone else's idea or work. If you take my idea without asking, I'm not going to be particularly happy about it, even if you gave me one of yours.
Additionally, please review the XDA GPL Policy. Compliance with all forum rules and policies is mandatory and non-negotiable.

Categories

Resources