Develop Bugs

Please contribute. Android 2.0+ will not be released for General Mobile DSTL1.

Friends,
Rumour has it that Android 2.0+ will not be released for General Mobile DSTL1. If you are an owner of a DSTL1 or Sciphone N21, this means your device will not benefit from the upcoming version of Android.
However there are many people who work individually for incredible ROMs to make these devices better, like AmonRa, Andferno, Crzyruski etc. These people will need the source codes for the new ROMs so that they can continue developing.
Please take a minute and help them by posting your wish at the General Mobile dot com's contact page.
Remember; Android is a very extendable OS and can be made better by continued efforts.
Thanks and peace.

Questions to Devs in general

How come the devs around here use fire distribution sites instead of open source trackers? i mean android is open source, there are open source trackers, and on top of the 99% of the stuff available for rooted android phones is legal and you freely share. i figured it would help with the distribution of files for both the devs and the users.

RULES for posting in Development

I know we all have busy lives and don't have time to go through a list of long winded rules, so here's a shortened version to make your life easier
Only the following topics are allowed in DEVELOPMENT area:
[DEV] - Development for any special projects or Apps
[ROM] - Custom ROMs
[KERNEL] - Custom Kernels (usually found in Original Development)
[MOD] - Hack & Modifications for the phone with code only, zips go in themes and apps
[FIX] - Fixes for known issues & bugs
[R&D] - Research & Development for Devs only, when gathering data for a new projects
[HOWTO] / [GUIDE] - How to instructions and Guides (Most of the time should be in General)
Note: If you are unsure where your new topic should go, then please post it to General
Please Include Screen Shots for ROM / MOD / THEME / Apps & Games, when possible as it's expected by our members
DEV Support for ROM / KERNEL / MOD / THEME must be provided within the XDA thread. You MUST use the thread to provide support; directing users to off-site platforms and media is NOT permitted. See our Telegram Policy.
A ROM thread without support will be considered [INFO]rmation / [REF]erence and moved to General.
Unmodified Stock ROM and Source Codes does not count as a DEVELOPMENT project unless it's part of an active project you have already started
YOU MUST POST YOUR SOURCE for kernels or ROMs with bundled kernels, per the XDA GPL Policy. THIS IS MANDATORY.
Password must be provided for all password protected files
Direct download links preferred, due to stipulations stated in Forum Rule 11
Spoiler: Rule 11
Don’t use XDA to advertise your product or service. Proprietors of for-pay products or services, may use XDA to get feedback, provide beta access, or a free version of their product for XDA users and to offer support, but not to post with the intention of selling. This includes promoting sites similar / substantially similar to XDA-Developers.com.
Do not post press releases, announcements, links to trial software or commercial services, unless you’re posting an exclusive release for XDA-Developers.com.
Encouraging members to participate in forum activities on other phone related sites is prohibited.
Off-site downloads are permitted if the site is non-commercial and does not require registration.
Off-site downloads from sites requiring registration are NOT encouraged but may be permitted if both of the following conditions are met:
A) The site belongs to a member of XDA-Developers with at least 1500 posts and 2 years membership, who actively maintains an XDA-Developers support thread(s) / posts, related to the download.
B) The site is a relatively small, personal website without commercial advertising / links (i.e. not a competitor forum-based site with purposes and aims similar to those of XDA-Developers.com.)
Placeholder threads are NOT permitted! A development thread MUST include a download link for the development project at the time the thread is posted.
Extra emphasis on Forum Rule #12
Spoiler: Rule 12
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 Developer Relations Team (DRT) 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 or a Moderator (see here). We are here to help!
All ROM / MOD / DEV / etc... found in the DEV section not created by the DEV themselves does not qualify as a development and will be moved to General. It should be properly tagged as [INFO] or [REF], with links to the source website were it was found
Please keep all non Development relevant chatter off the DEV project topics, feel free to create a new topic in General for non Development comments about specific ROM / MOD / THEME / etc... valid replies within a DEV project are: BUG Reports, Problem, Troubleshooting Steps & Logs.
... and Please! keep all your personal bickering via PMs, do not pollute the forum with your personal indifferences.
If you have a problem with a specific member please contact the Moderators for help, that's what we're here for, but we are not babysitters, we are here to gather, organize and provide useful information for our over priced phones.

General /e/OS Websites and Support Links

In this thread, we share some links for users interested in /e/OS
Website
Official website
Documentation Site
Community Forum
GitLab - Bugs and Features
/e/OS Source Code
Murena Smartphones
Telegram Channels
Announcements
Community Support - English
Public Channel - French
Community Support - French
Community Support - German
Community Support - Italian
Community Support - Turkish
/e/ mail ID
Support

@ManojNairOnline
I've removed the links to telegram from your post above!
As an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads and if thorough support is provided in the thread. These conditions obviously don't apply to this thread. Additional information is also available here:
WhatsApp / Telegram Chat Channels - Way Forward
Why was your Telegram/WhatsApp group/channel thread closed? Well, it's just becoming too much. Going forward, we will only allow only one Telegram/WhatsApp link in a development thread by the ROM developer provided thorough support is still...
forum.xda-developers.com
Please refrain from sharing social media links in future unless done in your own development thread.
Regards
Oswald Boelcke
Senior Moderator

Thanks for the review, Oswald. Will take care.

Is there somewhere or a way I can get the individual eOS Murena app's instead of using the web-based one's?
I'm asking cause I'm using Bliss OS x86 Pie on a Lenovo Helix ThinkPad and would kinda like to crossover with those app's.
It uses microG but as you probably know a lot Google app's don't like that won't run at all with that.
Not only that but I see eOS/Murena app's as an exactly migration merger for being in-between Linux Phones and Android. Which I eventually plan on getting a PinePhone Pro and tinkering around with it, just tired of Android after using it since around 2009/2010 and eOS/Murena looks like a good median service.

DorkyDev said:
Is there somewhere or a way I can get the individual eOS Murena app's instead of using the web-based one's?
Click to expand...
Click to collapse
Apart from Bliss launcher, /e/ don't make their apps publicly available via F-Droid. You can find prebuilt versions in /e/'s gitlab repos. If you were to use those, then you would need to check regularly for updated versions, as you won't be informed of updates automatically.
Better (in my opinion) to use the original, upstream versions of the apps that /e have forked , most of which are available in F-Droid . That way, F-Droid will inform you of updates, and you will get bug fixes and new features quicker, as you won't have to wait for /e/ to merge the fixes into their forked apps. All of them are pretty much -de-googled already, so all you miss out on are a: /e/'s UI changes and b: the bugs they have introduced when forking the apps
Calendar / ETAR
Messaging / QKSMS
Notes / NextCloud Notes
Email / K-9 Mail
eDrive / NextCloud sync client
/e/'s Browser app is a fork of Bromite (based on Chromium), which isn't available directly in F-Droid , but can be installed and updated using FFUpdater from F-Droid. A good alternative browser is Fennec F-Droid, which is based on Firefox.
For installing apps, use F-Droid and - if you need non-FOSS apps - Aurora Store
Good luck!

Recognized Developer Code of Conduct & Minimum Requirements.

Recognized Developer Code of Conduct​As an XDA Developers member with special standing as part of our developer program, we obviously have some expectations of your conduct. We try to be friendly here, and while we understand that not everyone is going to get along, we would ask that you try to avoid getting into big arguments in threads. If you have an issue with another forum member, take it up with them politely in a private message. It’s the mature way to deal with things.
As a titled member on XDA, you are a representative of XDA’s ethos – “by developers, for developers.” As such your activity offsite in other public venues should be in the same vein. Any negative, derogatory, abusive talk or actions may be taken into account as to your status as a titled member. This would include any behavior which violates our site rules. This does not change your responsibility to be subject to the requirements for acceptance into the Recognized Developer program, both in their current and future states.
While all users should follow the site rules, we would ask that you take a quick look at them again, as they are occasionally updated. If you have any questions, please don’t hesitate to get in touch with any moderator.
In addition to the rules, we would highlight the importance of acknowledging the work of others. It’s not nice to see your work get ripped off—whether it’s a ROM, part of a ROM, an app, a theme, images, guide text, etc. If you’re familiar with the regulations in academic institutions, you should know the score. Just seek permission and acknowledge those whose work you use, and generally be reasonable about things.
We would also ask that if you have a dispute, you first try to resolve it in a reasonable and private way, such as through private message. It is in no one’s interest to see your dirty laundry aired in public, and it looks much better for you to avoid conflicts on the site.
Senior Recognized Developers of XDA, in additional to the above, are expected to be active on XDA regularly. While we all go away for vacation, exams, and other everyday life events; we would ask that if a Senior Recognized Developer intends to take a significant break from development, he or she stand down temporarily. You’re more than welcome back if and when you return, and we’d love to have you back, if a space becomes available. The reason for requesting this level of activity is because as a Senior Recognized Developer, you will be able to vote on the appointment of other Senior Recognized Developers in the future. If many Senior Developers disappeared, it would be troublesome gathering a sensible turnout. In addition, from time to time we will invite discussions on matters pertaining to the site, and it’s only fair that we try to ensure that the people most familiar with development and XDA have a chance at helping out.
Recognized Developer Minimum Requirements​To be able to provide some transparency on how the reviews for RD are rated we’ve set up these minimum requirements. Please understand that the RD program is not just a reward for people that try hard on XDA, it is more than that. Accordingly, not just any project meets the standard of development. We will use these minimum requirements with enough room to budge if the circumstances require this, but please use a somewhat critical view of your projects, and only apply if you have at least met these requirements.
Make sure you uphold the RD code of conduct and the regular XDA rules. Should you have infractions on your account, contact the Developer Committee if you want to know if you are eligible to apply. As a general rule of thumb, wait one month per infraction point before applying, and can’t accept members with more than 10 points to their account. Of course, exceptions may be made but contact us if you have a question about this.
All Projects
Members must be actively involved in the community
Team accounts can’t receive the RD title. It’s a program that rewards developers for their individual work and team accounts don’t fit that idea.
A minimum of two full-fledged, markedly different projects are needed to apply for RD, only very special projects are considered otherwise
Any project needs to have at least three months of active development before it will be taken into account for the application
No history of bans and/or serious infractions
Changelogs must be readily available inside the thread, with updated information for each version
Feature lists and changelogs need to be free of blurry expressions like “tweaked ext4 performance” and other meaningless terms. Instead, it should be explained what was done in detail and why it was done
ROM
They started from an official manufacturer or source base (stock ROM or AOSP-like source).
Threads show a clear overview of changes made, in a way that DC can clearly see what has been developed by the user
The ROM isn’t the product of an online kitchen or otherwise derivative development (i.e. themed stock ROM)
ROMs need to identify what kernel they are using
If 100% stock then they must state that
If custom they must provide a link to the kernel on XDA (if available) or a link to the kernel source. To accomplish this there are two options:
Option 1: They provide links to suggested kernels but do not include them in the ROM
Option 2: They include the kernel but must provide a full, buildable source with all GPLv2 requirements met
Apps
Very simple applications may be excluded (very basic UI or functioning)
A free version of the application is available on XDA (no trials)
The developers are either active on XDA or really helpful in their support thread
Kernels
Sources must be posted and downloadable with build comments, toolchain used, and must compile
Sources must be released via forking + commits rather than “lump releases”
Link to the source must include which branch is in use
Guidelines:
In order to make sure the DC is able to find the information we need to make sure your threads hold all the information necessary. Here’s a list of things we like to see.
Threads should include:
Clear introduction
An overview of what the project does (i.e. its purpose) and what is included
2-8 screenshots that are posted alongside each other
A clear changelog in a
Code:
or tag, that shows the non-trivial updates to the project
Installation instructions and links to download and github (or like services) for source code, as applicable
Credits with links to the projects that have been built upon, or have been included, in this project
Provide a checksum if you can (md5, sha1 etc.)
The DC set up a template thread that highlights the important parts of a project. Try to follow this template to have an organized and clean thread. You can find the template thread here.