Hey,
I just installed LineageOS 16.0 on my OnePlus 3 and I'm seeing some minor, but annoying bugs. Could we please make a new forum dedicated to bugs and issues with the system? We could easly share not only screenshots, but also videos of the bugs by uploading them to YouTube and sharing with a link. I personally would love to post some of the bugs that I found in my system, so that developers can visually see what is the problem.
And yes, I saw that there is a "Report Bug" in dev options, but it's crap.
Related
With so many roms and software being developed and so many questions being asked over and over again, it occured to me that there is not (correct me if i am wrong) a public bug tracker for XDA.
Ideally integration with the user database and even possibly the threads (more than just a url link) would be great.
If we had a way of tracking and submitting bugs then i think each dev or cook could better manage the bugs in thier software and i think it will help reduce the duplicate requests and bug reports going on in each thread.
The bug tracker could split between software types, platform, then also have device sections with each rom under that, much like XDA is structured at the moment, in fact probably identical to reduce the confusion and help with the linking and integration.
What bug trackers could possibly be used that would integrate with XDA? Bugzilla?
I am more than willing to setup an instance for testing etc, who would be keen to see and help with this? Integration will be the biggest task.
Interesting Idea, I guess that would have to involve developer consent that they want their work to be tracked. Having people discuss in threads isnt bad as that is what the forum is for but a tracker type online utility may be good for huge projects which would cut down on posts saying "Hey whats the status of Bug X and Y?"
Good idea
I used my own tracker for a while, but for xda we would have the issue of how to assign users to what role.
Every time I made a rom, I would need to request a new category and get ten pepper added as project authors ...
Trouble with the tracker that I found was that it just got messed up like the forums. Trust me that nobody searched it.
I reverted to a dedicated subforum, eventually, as it was less work in managing. I had appointed a second bug system admin, yet still got heaps of stuff to do...
A tracker is a great idea, but would be misused, and there stupid "why is camera no work kthxbai" posts would continue by those not checking the tracker.
Integrating a attacker is pretty easy on a username perspective, but harder on a people perspective
Still, I like the idea, but can envisage huge amounts of work for svetius, making new categories every time a new rom appears etc ...
pulser_g2 said:
I used my own tracker for a while, but for xda we would have the issue of how to assign users to what role.
Every time I made a rom, I would need to request a new category and get ten pepper added as project authors ...
Trouble with the tracker that I found was that it just got messed up like the forums. Trust me that nobody searched it.
I reverted to a dedicated subforum, eventually, as it was less work in managing. I had appointed a second bug system admin, yet still got heaps of stuff to do...
A tracker is a great idea, but would be misused, and there stupid "why is camera no work kthxbai" posts would continue by those not checking the tracker.
Integrating a attacker is pretty easy on a username perspective, but harder on a people perspective
Still, I like the idea, but can envisage huge amounts of work for svetius, making new categories every time a new rom appears etc ...
Click to expand...
Click to collapse
yeah i agree with all of your points, i guess i was thinking that if it were somehow integrated into the forums then it'd be used more. as far as roles, a simple request to establish a project that would then be assigned to the dev in question. they could then choose to add extra people.
i just have no idea what tracker could and how fully integrated it would be with the forums.
it seems to me that if some of the noob "why is x not working" could be at least reduced by a bug tracker, hell we could even weed out the noobs by saying that unless you check and submit bugs no questions will be answered in the forum.
anyway, thought it was worth mentioning and getting the ball rolling. We could do some basic pilots of different trackers based on any known integration benefits.
hello i just read a post on the portal talking about a bug list thread related to WP7. It would be a good idea for this site, users and developers if there was a section dedicated to bug list based on OS and phone type.
a sample of how the list should look like
Title (OS Name)
Type (Phone type)
Bug (description of bug) - Link/fix (a link to the fix for the bug)
This might make things simpler for everyone as it is a pain in the rear to hunt down bug issues as sometimes the bugs are only in certain model phones.
Thank you,
hackmimic
It is possible to add a "thread wiki" post below the original post?
Eg in slickdeals, you have a common wiki below the OP that people can add stuff
I feel like threads should have things like that...
OP might not have time to update his/her post with relevant info that an another user can add
It might be difficult trying to look through 100 pages of posts to figure out if someone has a similar problem(or through search), while it is easy for multiple people to maintain a common wiki that they can all edit
EG: http://slickdeals.net/f/4803408-Thi...ted-by-users-like-you?p=51265310#edit51265310
paperWastage said:
It is possible to add a "thread wiki" post below the original post?
Eg in slickdeals, you have a common wiki below the OP that people can add stuff
I feel like threads should have things like that...
OP might not have time to update his/her post with relevant info that an another user can add
It might be difficult trying to look through 100 pages of posts to figure out if someone has a similar problem(or through search), while it is easy for multiple people to maintain a common wiki that they can all edit
EG: http://slickdeals.net/f/4803408-Thi...ted-by-users-like-you?p=51265310#edit51265310
Click to expand...
Click to collapse
Interesting idea, not sure how adaptable it would be with the VBulletin software though. It might also be similar in effect to something I hear is going to be rolled out sometime soon, a post rating system so posts with more positive ratings will move to the top, and posts with enough negative ratings will be hidden.
I think though that the OP should either ask the mods to close the thread or hand it over to another user by contacting the forum admin if they don't have time to maintain their thread with important new information.
mf2112 said:
Interesting idea, not sure how adaptable it would be with the VBulletin software though. It might also be similar in effect to something I hear is going to be rolled out sometime soon, a post rating system so posts with more positive ratings will move to the top, and posts with enough negative ratings will be hidden.
I think though that the OP should either ask the mods to close the thread or hand it over to another user by contacting the forum admin if they don't have time to maintain their thread with important new information.
Click to expand...
Click to collapse
I mean small details: like "most commonly encountered problems and solutions", that the OP might have time to add or not
For a dev thread, I rather have the dev (most likely the OP) focus on developing and other people helping out in figuring out problems by common users... users can update the wiki on the un-resolved problems so that the dev can see, without having the dev to read the last 3 pages that were newly posted
you can see in the Slickdeals thread... 179 pages of posts... some of them are "useless" in saying "thanks for the deal", while some people have legitimate questions (like "is this phone quad band") that other users answered 10 pages after their post... having a wiki means common info will be presented clearly without having to dig through the thread, and anyone can update that, not just the OP <--- most important point
EDIT: Slickdeals uses vBulletin too, but customized plugins... there are probably open source plugins out there, just trying to dig through
EDIT2: i guess SD doesn't use pure vBulletin plugins for that... maybe some CMS system
paperWastage said:
I mean small details: like "most commonly encountered problems and solutions", that the OP might have time to add or not
For a dev thread, I rather have the dev (most likely the OP) focus on developing and other people helping out in figuring out problems by common users... users can update the wiki on the un-resolved problems so that the dev can see, without having the dev to read the last 3 pages that were newly posted
you can see in the Slickdeals thread... 179 pages of posts... some of them are "useless" in saying "thanks for the deal", while some people have legitimate questions (like "is this phone quad band") that other users answered 10 pages after their post... having a wiki means common info will be presented clearly without having to dig through the thread, and anyone can update that, not just the OP <--- most important point
EDIT: Slickdeals uses vBulletin too, but customized plugins... there are probably open source plugins out there, just trying to dig through
EDIT2: i guess SD doesn't use pure vBulletin plugins for that... maybe some CMS system
Click to expand...
Click to collapse
I guess the problem really is that the dev thread should not be used for support, but people insist on treating them that way. I think that there should be a "ROM XXXXX Support Thread" in the device Q&A forums and that is where such questions should go instead. Then there would be no problems with the restrictions since user support questions or bug reports without proper logging, details, attempted fixes, etc. would be moved from the dev thread into the support thread if they were able to post them there.
mf2112 said:
I guess the problem really is that the dev thread should not be used for support, but people insist on treating them that way. I think that there should be a "ROM XXXXX Support Thread" in the device Q&A forums and that is where such questions should go instead. Then there would be no problems with the restrictions since user support questions or bug reports without proper logging, details, attempted fixes, etc. would be moved from the dev thread into the support thread if they were able to post them there.
Click to expand...
Click to collapse
even in support threads... who would maintain the massive throve of info that many people would ask? the OP(most likely the dev himself who made the thread), or every user who wants to?
example.... if a lot of people post below us, makes it go into 5 pages... someone on page 3 found a plugin that does what it works.... does it make sense for that info to be posted just below my first post by anyone, or is it on me(the OP) to edit my first post "someone on page 3 found this info"?
This is actually an interesting idea. We are busy adding other new features but definitely will keep this in mind. Right now, we do already have a wiki and there is nothing stopping someone from creating a wiki page while adding their thread, and linking to it, but it would be nice to integrate that directly into the page.
bitpushr said:
This is actually an interesting idea. We are busy adding other new features but definitely will keep this in mind. Right now, we do already have a wiki and there is nothing stopping someone from creating a wiki page while adding their thread, and linking to it, but it would be nice to integrate that directly into the page.
Click to expand...
Click to collapse
yeah, but it's definitely not as seamless as having it right below the original post
lemme see if there are any plugins to "stream" that wiki page into a post...
Came here to request this too. And precisely for the same reasons as the OP.
This would be immediately embraced.
I don't understand the "I'm not sure this would be adaptable with vBulletin" comment since slickdeals uses vBulletin.
http://www.qapla.com/mods/showthread.php/309-Wiki-Posts-for-VB4-by-BOP5-BETA
another vote for this.
i have been following a thread about about the development of 4.4 for the hisense sero 7 pro (randomblame, davepmer and others are awesome)
anyway it has a post count of nearly 1,000 and people come in and try the latest build, or just wanting to ask a question about the latest builds. the same questions get asked over and over. i don't really think its the fault of the person asking since who is going to read 1,000 posts just to see if his/her problem has been discussed.
I've noticed that whenever someone asks, "What ROM should I use?" the responses are either brusque (e.g. "Just install whatever and find what you like,") or unverifiable ("I've had okay luck with XYZ").
When I choose a ROM, the first thing I care about are the bugs. And yet, there is no single thread in the development forum that has a list of all the current ROMs, and a list of bugs. Some developers are very good with updating the first page of their thread, clearly listing the bugs, and yet for other ROMs, you have to dig until you get to post 1579 on page 157 to find that such-and-such functionality doesn't work.
Why doesn't anybody do this? Why isn't there a sticky at the top of the development forum that clearly lists the major ROMs in development, and keeps track of the main bugs? This makes selecting a ROM much, much easier.
TSGM said:
I've noticed that whenever someone asks, "What ROM should I use?" the responses are either brusque (e.g. "Just install whatever and find what you like,") or unverifiable ("I've had okay luck with XYZ").
When I choose a ROM, the first thing I care about are the bugs. And yet, there is no single thread in the development forum that has a list of all the current ROMs, and a list of bugs. Some developers are very good with updating the first page of their thread, clearly listing the bugs, and yet for other ROMs, you have to dig until you get to post 1579 on page 157 to find that such-and-such functionality doesn't work.
Why doesn't anybody do this? Why isn't there a sticky at the top of the development forum that clearly lists the major ROMs in development, and keeps track of the main bugs? This makes selecting a ROM much, much easier.
Click to expand...
Click to collapse
I can do it. But it may annoy the developers. So we need at least few people working together for it. Because personal opinions may go biased.
So, if anybody wants to collaborate, join me, PM me, I alone won't do it.
One of the problems is that there are 'known bugs', that the developers admit to, and then there are the issues that individuals have because not all devices are the same...
Oneplus had been teasing the release of their latest Android 11 build of Oxygen OS. It is named as Oxygen OS 11 (Hydrogen OS 11 for china). They have offically made it availble for users to triy out these build. They are relaeased as a part of Develeoper preview and it might be buggy. Open Beta and stable release are planned for comming months. For OnePlus 7T/7/6 series the stable release would be planned by december.
New feature comming to Oxygen OS 11:
1. New visual design (including Weather app, Launcher, Gallery, Notes)
2. New layout for more comfortable and convenient one-handed operation
3. Always-on display function, including 11 new clock styles
4. Live wallpaper that changes according to the time of day
5. New OnePlus Sans font that improves readability
6. Optimized Dark Mode, including the ability to automatically turn on and off and a shortcut in Quick Settings
7. 3 new Zen Mode themes, more timing options, and new Group feature to let you experience Zen Mode with your friends
8. New Gallery function that automatically creates a weekly story based on your photos and videos
If you can't wait for stable release and want to try the build now then you can refer : {Mod edit}
Can someoneplease confirm if banking apps work with this DP3. Thanks
@x2wolf THREAD CLOSED as another subject matter related thread already exists, in which you also posted here a few minutes before you created this thread: https://forum.xda-developers.com/oneplus-8-pro/how-to/android-11-beta-t4113817
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse