Database Info

BugTracker Now Online!

[06 July] XdaBugs - A Formal Introduction
Does your ROM play up?
Annoyed that those lazy developers are doing nothing?
Your complaints getting lost in all the n00b questions?
Well look no further - XdaBugs is your answer!!
What is XdaBugs?
XdaBugs is a Bug Tracking system that is designed for the multiple devices, roms and problems that mobile devices suffer. Using our unpatented technology, you can place a bug report using a structured form that allows developers to quickly decipher the problems and users to add comments and additional info
But, doesn't that replace these forums?
No.
XdaBugs is designed to compliment the Xda-Developers forums. XdaBugs is made with being clear and concise in mind, hence all comments\bugs are moderated and anything posted to the site needs to stay on topic.
So, how do I get started?
First goto: http://xdabugs.vidmes.com
Then, have a look around the site - you can even see bugs and comments without logging in!
A good place to start is the Help\FAQ page. Alternatively, clicking on every link in the sidebar also works...
Once your used to the layout and the site, goto the Register page and sign up
Now start spreading the bugs!! (That sounds like a good slogan... then again...)
Side Note: I'm a Developer, and my ROM is currently on the site, what should I do?
Sign up to the site then PM me on Xda-Developers requesting developer privileges
From there, remember to check on all of your bugs for your ROM, and edit the rom and bugs as you see neccesary
Side Note: I want to help out by being an Admin!
Great! Now go away!
But seriously, if you really want to help, then PM me requesting admin privileges and argue your case. If its decent, I'll grant you privileges.
[?? June] Original Post
The new Xda Bugtracker I have been working on has now been finalised (or at least in a Beta) - so its ready for use!
Just goto http://xdabugs.vidmes.com and check it out
NOTE:
It is still a little buggy, but I'm working on that
It IS NOT a forum - so bugs\comments will be heavily moderated
If you need developer\admin privleges, then PM me
Also PM or email me any bugs that you find
Enjoy!
(Also, all data from the Alpha version's database has been wiped - so you may need to re-register...)

Bugtracker
Hi D,
So now it's official
Great work thanks, I will ad my rom again for start
Cheers,
Leo

Bugtracker
Hi again,
I see my rom is still there, also Lt.Cmdr.Ivan has added his rom version's.
Cool!
Let the bugs begin
Leo

Laurentius26 said:
Hi again,
I see my rom is still there, also Lt.Cmdr.Ivan has added his rom version's.
Cool!
Let the bugs begin
Leo
Click to expand...
Click to collapse
Actually, I added most of the ROMs that are currently there - just to show some examples\get things started
Either way - Enjoy!

A Note to Developers:
You do actually need to edit your bugs and add\remove comments - thats the whole point of a bug tracking system, however I'm still seeing a lot of "unverified" bugs...

There isn't a big contribution to bug tracker.... i don't understand why guys don't participate to that !

is it still on?
TehPenguin said:
A Note to Developers:
You do actually need to edit your bugs and add\remove comments - thats the whole point of a bug tracking system, however I'm still seeing a lot of "unverified" bugs...
Click to expand...
Click to collapse
hey tehpenguin
wats wrong with the site, its not there anymore???

bushako said:
hey tehpenguin
wats wrong with the site, its not there anymore???
Click to expand...
Click to collapse
The site has been down for a while, but should be back up shortly.
Cheers,
Beast

New Version! (0.02.7b)
Includes
Minor bug fixes
Bugs now show the date of their latest comment
Date of latest comment is highlighted if it is new (compared to your lst logout)
A reminder for Developers
Please ensure that only your latest version is on the Xda Bugs site
Deprecate old versions (you can do this by editing them)
The site is supposed to be heavily moderated, so remove\edit comments as needed
Remember to update the status of bug (you can do this by editing them)
PM me if you need Developer permissions!

I like the idea of a bug tracker, but i believe i can say why it's not so much used.
1) UI is not intuitive. Bugs must be listed in table format with Title, Rom version, severity, reproducability etc etc in one list, searchable between roms and more.
2) The first thing you're faced with when you go to the site is a login prompt. First page must be the bug list, and you're not asked for login until you want to submit a new bug.
Not trying to all-knowing or anything, just giving constructive suggestions, i can even help out if nobody are up to it.
Bheam

I Mate Jas Jar
I upgraded my jas jar to the 2.09.01 and now it does not work or reboot any suggestions or idea how to recover or make it work with this rom
I mate are the worst with support or taking care of customers for $1300+ this is not good. Never again. None the less I own the jas jar and want to make the best out of it. Any help is appreciated.
thanks

aljasjar said:
I upgraded my jas jar to the 2.09.01 and now it does not work or reboot any suggestions or idea how to recover or make it work with this rom
I mate are the worst with support or taking care of customers for $1300+ this is not good. Never again. None the less I own the jas jar and want to make the best out of it. Any help is appreciated.
thanks
Click to expand...
Click to collapse
Was it official release or took rom from this forum? Can you describe clearly meaning of "it does not work or reboot" - are you stuck on any screen, splash? Try to reflash again, first

http://xdabugs.vidmes.com
Is it still down ? I am unable to open it.

sarah113 said:
http://xdabugs.vidmes.com
Is it still down ? I am unable to open it.
Click to expand...
Click to collapse
Fixed.
It was a DNS issue, so it may take a day or two to propogate. Alternatively, you can bring up the "Run" box in windows (Start->Run...) and type in "ipconfig /flushdns" then hit "Ok" - this should clear your DNS Cache

Xda Uploads - The new way to share ROMs

I've noticed that many developer use Rapidshare, Megaupload, etc to share their ROMs, however these sites are very annoying in that they throttle bandwidth, force you to wait, force one download at a time, etc - unless of course you are willing to pay.
I have attempted to help a number of ROM developers by granting them FTP access to my hosting - but I have realised that this is only a temporary measure - and that a better way must exist.
So the solution it here - Xda Uploads - http://xdauploads.vidmes.com
Developers can upload their ROMs to a temporary location on my site via FTP then, using Xda Uploads, they can move the file into their own folder in the http://vidmes.com/xda/ folders.
At the moment it is still in beta, and a number of features are missing - but, depending on the feedback from developers, features will be added and bugs fixed.
So, Xda Upload!
NOTE: All those who already have FTP accounts from me are welcome to keep them and assist in moderating\maintaining the xda folders

Excellent!!!

How about adding some of the originial roms like the WM5 OEM/Operator ROMS as well ...or is there a legal issue there?

rdosti said:
How about adding some of the originial roms like the WM5 OEM/Operator ROMS as well ...or is there a legal issue there?
Click to expand...
Click to collapse
Go for it
If there is a legal issue, then I'll get an email from my hosting company and I'll pull the offending material down. Worst case, my site goes down for a couple of days (and this has happened before...).
btw. I haven't seen anyone sign up yet :'( (but that isn't an excuse for anyone to register - I'd rather keep this as a Dev\Cook\Senior Member service...)

Rom OP Format...DEVS READ PLEASE

Below is a format that should be used as an example of how a rom thread should look. It doesnt have to be exact. I suggest that you stay creative and use all the features in the advanced panel when creating a thread.
1. Name of rom, team, etc
2. Introduction
3. Changelog in code or php tags
4. What's included in the rom in the (apps, tweaks, scripts, addons, mods) in code of php tags
5. What works/what doesn't work in code or php tags
6. Credits (Users name-with link to (profile/github/or thread u got tweak from embedded), and what they did to help you)
7. Screenshots (2-10 different screenshots of different aspects of rom)
8. Kernel with either link to thread you got it from or github (if stock sense or cm please state that and that is enough)
9. Instructions on how to install the rom (also if special instruction for a2sd or beats audio...etc)
10. Do's and Don'ts of the rom
11. Questions & Answers section (I find this helpful to write out asked questions with solutions at the bottom of the op. I find that it cuts down on the question being asked a million times)
12. Finally the dl link
13. Additional add-ons (this can go into first post or reserved posts after)
I find the embedded link looks and feels better throughout the op if possible.
All sections should have a header with enlarged text and spaced out so people can read it easily.
I am hoping that this helps to make this section a little cleaner and easier. enjoy
The way I look at this is that it takes US weeks/days/hours to make these roms....we can take the time out to make sure that the op looks professional and clean
Also Make sure the op is fully ready before posting. I know we all get excited to release a rom but stating that half the stuff will be updated as time permits just shows that you are lazy and in a hurry which doesnt look good cause if thats the case then how does your rom run....
No posting a a rom thread without a DL link either

Thanks Papa Smurf151 i think everyone who is getting ready to post a rom should be redirected here!
sorry if im not allowed to post here, so please delete my comment if needed

i left this open for feedback

How about how stable it is like in the old days?
I remember last year everyone would label them as beta, RC, final etc.

bennyboy78 said:
How about how stable it is like in the old days?
I remember last year everyone would label them as beta, RC, final etc.
Click to expand...
Click to collapse
I think what Papa Smurf outlined in the OP is more then enough and it covers the basics while keeping the majority of the threads uniformed or at least try to
I also don't think we should start being over critical here and require individuals that start threads in the development section to add labels like Alpha, Beta, MC, RC or whatever.
I understand that having labels would make things a whole lot easier for the user BUT it also doesn't encourage the user to read about what he or she flashes onto their phone.
I don't know how many times I've seen a user complain and harass developers over something that was clearly their (the user) fault because they didn't read the OP. They saw fancy screenshots and saw the download link and either ended up bricking their phone or causing their phone to turn into a hot pocket...lol
Not trying to tell people how to do their job BUT I think we should encourage users to read/search more not shortcut things for users.

Mazda said:
I think what Papa Smurf outlined in the OP is more then enough and it covers the basics while keeping the majority of the threads uniformed or at least try to
I also don't think we should start being over critical here and require individuals that start threads in the development section to add labels like Alpha, Beta, MC, RC or whatever.
I understand that having labels would make things a whole lot easier for the user BUT it also doesn't encourage the user to read about what he or she flashes onto their phone.
I don't know how many times I've seen a user complain and harass developers over something that was clearly their (the user) fault because they didn't read the OP. They saw fancy screenshots and saw the download link and either ended up bricking their phone or causing their phone to turn into a hot pocket...lol
Not trying to tell people how to do their job BUT I think we should encourage users to read/search more not shortcut things for users.
Click to expand...
Click to collapse
Well said, couldn't agree any more.

MBQsniper said:
Well said, couldn't agree any more.
Click to expand...
Click to collapse
See I assumed this was common sense and ROMs that are missing a lot of these details, I don't give the time of day too so those ROMs don't matter to me. Because in my mind all the good ROM's out there already follow this in some way shape or form.
I appreciate what you did but I don't see why we need it is all.

As long as these are only guidelines and not enforceable rules, I agree with them. But I wouldn't agree with deleting/locking threads that fail to follow these guidelines; that would send the wrong message to developers.

v5HMeca said:
As long as these are only guidelines and not enforceable rules, I agree with them. But I wouldn't agree with deleting/locking threads that fail to follow these guidelines; that would send the wrong message to developers.
Click to expand...
Click to collapse
Rom threads will never be locked or deleted for not following these guidelines. I would hope devs would embrace them and if a fellow dev isn't then I would hope someone would point them here and try to help them. Most rom devs want to have a nice looking op. But some of them are new and don't know better or are very young and don't know better. This just helps to give structure that they can refer to and say oh yeah maybe I should have that or this.
XDA Moderator

Cherokee4Life said:
See I assumed this was common sense and ROMs that are missing a lot of these details, I don't give the time of day too so those ROMs don't matter to me. Because in my mind all the good ROM's out there already follow this in some way shape or form.
I appreciate what you did but I don't see why we need it is all.
Click to expand...
Click to collapse
What?

Kangers

So I have a question, one Rom Developer said that if he Kangs (copies) another ROM developer's work, as long as he puts his name in the credits then it is all good. He can copy any rom with little effort and then putting that person's name in the credits gets him out of the issue of copying another person's work. I hope this isn't someone taking advantage of a loophole in XDA's policies....

It depends on the developer,
if he does not mind then kang can do it.
If the developer minds and asks kang to stop and he does not, he could be banned if the developer complains to XDA.
Kang should get permission from the developer and give him credit where it is due.

Would Kanging apply if the work in question is not in the domain of XDA?
I KNOW of one Dev who doesn't post his work on XDA but has his muppets attack people on XDA for work not posted on the platform?
Sent from my SM-G935F using XDA-Developers mobile app

From the Forum Rules;
12. Using the work of others.
If you are developing something that is based on the work of another Member, you MUST first seek their permission and you must give credit to the member whose work you used. If a dispute occurs about who developed / created a piece of work, first try to settle the matter by private message and NOT in open forum. If this fails, you may then contact a Moderator and provide clear evidence that the work was created by you.
Convincing evidence will result in the copied work being removed. If there is no clear evidence that it was you who created the work, then in the spirit of sharing, all work will remain posted on the forums.
As an addition, developers have the right to hold exclusivity over their work for as long as it is deemed necessary by that developer. However, if the work is claimed as exclusive, it must remain as such. No selective sharing will be allowed (ie, allowing certain people to use it and not others). If the developer decides to start sharing the work with others, the work automatically becomes available for all to use, albeit with the relevant credit displayed.
When permission has already been given, unless there is a very valid reason, it cannot be revoked (same applies to major updates on the work). Under that same premise, permissions cannot be denied unless the work is exclusive or under extreme circumstances.
In plain English: If you want to keep your work exclusive, go for it. However, if you are going to share your work, do it fairly.
Reposted content, derivative or maintained works based on that of former or banned members may be removed at our discretion.
These rules apply to all software posted on XDA (including but not limited to ROMs, RUUs, apps, games, kernels, themes, icons, etc) unless that software comes with a license that waives these rules.

Unbrick your OP6

Hi guys,
This is NOT something new, simply you will find everything you need in one place with the steps. Yesterday I had an issue restoring my system using twrp and got a crash dump error everytime I start my one plus 6. So, simply I collected everything you need to unbrick your OP6 and restore it to version 9.0.4 in one folder. If you want to restore your system to another version, visit this link
to download everything you need, I uploaded the folder on mega,
https://mega.nz/#F!PewjxYrJ!hVJ50jcE1vdctOUc9JyX7Q
The files I added in this folder were shared by @Some_Random_Username and @Fivegates
Again this is just so you be ready to go with one downloading link.
I hope it helps.
edit:
There is also twrp and magisk in that folder but the steps to how to root the device aren't included neither how to unlock oem

where did you get the tool from?

This is msm?
Tapatalk - OnePlus6

This is duplicate work of following thread:
[OP6][LATEST 9.0.4] Collection of unbrick tools
Also, notice some files in the folder was not got permission from original developers to mirror.
12. Using the work of others.
If you are developing something that is based on the work of another Member, you MUST first seek their permission and you must give credit to the member whose work you used. If a dispute occurs about who developed / created a piece of work, first try to settle the matter by private message and NOT in open forum. If this fails, you may then contact a Moderator and provide clear evidence that the work was created by you.
Convincing evidence will result in the copied work being removed. If there is no clear evidence that it was you who created the work, then in the spirit of sharing, all work will remain posted on the forums.
As an addition, developers have the right to hold exclusivity over their work for as long as it is deemed necessary by that developer. However, if the work is claimed as exclusive, it must remain as such. No selective sharing will be allowed (ie, allowing certain people to use it and not others). Should the developer decide to start sharing the work with others, the work automatically becomes fair game for all to use, albeit with the relative credit displayed.
In regard to permissions, the same rules apply for this but if permission was already given and unless there is a very valid reason, it cannot be revoked (same applies to major updates on the work). Under that same premise, permissions cannot be denied unless the work is exclusive or under extreme circumstances.
In plain English: If you want to keep your work exclusive, go for it. However, if you are going to share your work, do it fairly.
These rules apply to all software posted on XDA (including but not limited to ROMs, RUUs, apps, games, kernels, themes, icons, etc) unless that software comes with a license that waives these rules.
Therefore, this thread is closed. Please continue discussion in the thread aforementioned. Thanks.
Regards
Jerry
Forum Moderator