MOD EDIT:
So an update eh? How about a public beta? Sorry you all have been waiting so long, there has been much going on in the world of athena on our end and much more in testing. One thing we worked hard on is a true 6.1 NK.exe the ONLY rom anywhere that will have that, a work done by the hardworking cmonex herself. To download go here: http://eliteteam.htc-hackers.mobi/pub/AthenaProjectRedux/ Download the nbh and the wrapper. If you'd like to there is also the pagepool app that you can play with pagepool settings. Please all download play with it and see what you think. Thank you for your support and patience
Added by DaveShaw in LTxda's absence, take from a post by AstainHellbring here.
END MOD EDIT:
...more coming soon.
Project Goals
- New Build
- New Life
- New Features
- New Speed
- New Stability
- Updated Software
- Two Versions - Packed and Clean but nothing in between (wow that rhymed, pretty cool)
- More to come soon...
_--Reserved--_
__--Reserved--__
___--Reserved--___
no promises but if stuff in school calms down and i find the time i will make that come back tour i was talking about. going back to square one though and making a whole new kitchen if i do. lite and full rom. latest stuff from blackstone, raphael, and diamond. touchflo2d maybe. touchflo3d not in near future. also might be one rom only as im still looking into getting a blackstone.
Pawel062 said:
no promises but if stuff in school calms down and i find the time i will make that come back tour i was talking about. going back to square one though and making a whole new kitchen if i do. lite and full rom. latest stuff from blackstone, raphael, and diamond. touchflo2d maybe. touchflo3d not in near future. also might be one rom only as im still looking into getting a blackstone.
Click to expand...
Click to collapse
Bro, you're always welcome back. Meanwhile we'll keep the machine well greased and parts moving. Come back when you can, we'll all be here waiting on you.
We have some nice plans for this next ROM so check in from time to time and flash your Athena and provide feedback.
yeaahhh!
ltxda said:
Bro, you're always welcome back. Meanwhile we'll keep the machine well greased and parts moving. Come back when you can, we'll all be here waiting on you.
*
We have some nice plans for this next ROM so check in from time to time and flash your Athena and provide feedback.
Click to expand...
Click to collapse
Yo ltxda,ya giving me a hard on with these roms lol.Good to see the ap team on a comeback.I miss them days on irc waiting for ap4 and pre-testing,at the same time bashing on good ol' irus lol.Still trying to figure out building the cannon .God bless you ltxda,your daughters health,and the rest of ap team.
btw ,ya still on irc?
any help you need lemme kno.
looking foward! peace!
*
D1ab70 said:
Yo ltxda,ya giving me a hard on with these roms lol.Good to see the ap team on a comeback.I miss them days on irc waiting for ap4 and pre-testing,at the same time bashing on good ol' irus lol.Still trying to figure out building the cannon .God bless you ltxda,your daughters health,and the rest of ap team.
btw ,ya still on irc?
any help you need lemme kno.
looking foward! peace!
*
Click to expand...
Click to collapse
Hey!
Thanks for your kinds words bro. We sure are on IRC. There isn't much activity for this yet in the public. Today I flashed a alpha ROM to my Athena and it booted fine, all is looking good for this project so far....but i never thought it wouldn't
We should be active in IRC soon with some more testing once we port some nice things over to the ROM. I can't wait. These newer builds, I'm hoping will make the Athena snappier and a bit more pleasant to use.
For now, let everyone know about the project so we can get things going again. I can't wait to see how the thread will turn up again. LOL
Those were some crazy crazy times. I'm sure many people had to replace the F5 key on their keyboards from hitting refresh so much.
ltxda said:
Hey!
*
Thanks for your kinds words bro. We sure are on IRC. There isn't much activity for this yet in the public. Today I flashed a alpha ROM to my Athena and it booted fine, all is looking good for this project so far....but i never thought it wouldn't
*
We should be active in IRC soon with some more testing once we port some nice things over to the ROM. I can't wait. These newer builds, I'm hoping will make the Athena snappier and a bit more pleasant to use.
*
For now, let everyone know about the project so we can get things going again. I can't wait to see how the thread will turn up again. LOL
*
Those were some crazy crazy times. I'm sure many people had to replace the F5 key on their keyboards from hitting refresh so much.
Click to expand...
Click to collapse
Hellz yeah Bro!
Tha ap4 thread was wild!
its irc.freenode.net #xda-devs is the channel right?
Mods need 2 sticky this!
*
D1ab70 said:
Hellz yeah Bro!
Tha ap4 thread was wild!
its irc.freenode.net #xda-devs is the channel right?
Mods need 2 sticky this!
*
Click to expand...
Click to collapse
Yep and sticky on the way.
Thanks for all the hard work AP Elite Team. Hitting F5 and charging my Dopod U1000 .
Dusting, dusting away...
Hi Team I just dusted off my X7500 and will make sure it's all charged up for our next adventure!
Welcome back!!!!
greeeeeeeeeaaaaaat news, ole, ole, ole, the best team for the best rom.
could you please try to port the driver from kaiser or diamond to have all athena users manila 3d working?
thanks.
wellcome back dudes. dusted off my athena as well. ready 4 action
If you guys can come up with something better than MiChy, I will be seriously interested - I have been rock solid with MiChy 2.04D and not seen the need to upgrade further.
One small request - if you can build on Pawel 's work on BlueTooth improvements, that would be awesome. Its my only real gripe at present
MrSums
Liking the interest already. Spread the word and I hope there is as much interest in the project as there was "back in the day"
Nice, really looking forward to an new AP rom!
Mrsums said:
If you guys can come up with something better than MiChy, I will be seriously interested - I have been rock solid with MiChy 2.04D and not seen the need to upgrade further.
One small request - if you can build on Pawel 's work on BlueTooth improvements, that would be awesome. Its my only real gripe at present
MrSums
Click to expand...
Click to collapse
Thanks. Although we're not competing against anyone, I'm going to flash his ROM to see what it's about. Our goal is not to compete but to do the best job we can and hope that's enough.
We still have all our old tricks in the bag as well as a few new ones.
Still running AP4 and would be happy to move up if it looks good.
Prayer said for your daughter, BTW...
What about a x7510 version?
I'm glad to hear this news.
The problem is that I have updated my athena to a x7510.
Do you plan to make a versión for this model? Now that we have the HardSPL for the x7510 (thanks cmonex), we need good ROMs.
If you don plan to release a version for the x7510, would you give me authorization to port your new ROM to the x7510? (or at least to try it, because I'm quite new to ROM cooking )
Thanks.
Hi,
I'd like to get some very important info from Remix OS dev team.
Users unrelated to the dev team or with no android-x86 OS dev experience, please DO NOT attempt to answer these questions.
Could you please make a thorough guide on how to report bugs, suggestions, feature requests and hardware incompatibilites?
Which tools should we use to report bugs or hardware problems - be precise please. Current feedback form seems very modest and inefficient.
Except for bug description and device info should we provide a full logcat, dmesg, per-app logcat - please point out the most effective way to report this stuff.
Where should we post feature requests or suggestions?
I personally think, that e-mails or forum threads are really inefficient for this. I'd recommend using Uservoice service (https://uservoice.com) or something familiar . Example of uservoice usage in practice: https://touchpal.uservoice.com/ There are plenty of web services like these and they are very powerful and efficient.
Perhaps there is a web service that would help making an official list of supported hardware?
Remix OS, Android-x86 and Phoenix OS all base pretty much on the same ground here, so they could share same list, but none of these actually has a nice, neat tool to report supported hardware. Except for a list of officially supported devices, it's a total mess.
I know that ChromeOS with android apps support and upcoming Android releases may be groundbreaking for whole Android-x86 related projects, but if we mobilize ourselfs and use all resources efficiently, I'm pretty sure Remix OS can become very popular and liked. Devs - help us, users, help you achieve that.
Right now it seems like you don't really care about other devices compatibility or about what people may report. If you did, you would provide better tools for that in order to do your work more efficiently. Don't take it as offense, it's just cirtical point of view.
Please optimize that - this will help speed up the development process and community contact a ton.
Please reply Remix OS, Jide, @RemixOS_Cameron , @RemixOS_Guannan , @RemixOS_Jason , @RemixOS_Josh , @RemixOS_Joshua , @RemixOS_Valentina , @AmoraRei
Hey Ventricle,
Thanks for the message and the suggestions!
Currently:
We have the help center setup for general inquires as well as leaving technical feedback here: http://support.jide.com/hc/en-us/requests/new
We also have a google form specifically set up for Remix OS for PC users: https://docs.google.com/forms/d/1WMRbcwDqcoZ1vyUq68AJKCYvXBGvUIEvbgHhuySrUUc/viewform
On products like Remix Mini, clicking on the power options will allow you to "Report a problem" and then "Submit feedback". This will also send a user log along with the report.
We also actually read through almost every one of these threads for bug reports and feature requests. As for hardware incompatibilities, we accumulate a list based on the comments here as well as in our google group (https://groups.google.com/forum/#!forum/remix-os-for-pc). However, these incompatibilities are much trickier to tackle as the hardware configurations are so varied and diverse.
However, I will admit that the user feedback process can be better. We'll work on a more streamlined process, write up an easy to follow guide and then we'll post it here in XDA as well as other channels.
Thanks again for your comments. We clearly need the support of our user community as we grow. Sometimes, in the process of growing as a young company, processes need to keep getting better or else we fall behind. Appreciate the reminder and I'll drop you a note after we've created the guide.
Best,
Jason
@RemixOS_Jason that's great, thanks. I'm looking forward to your actions.
A little overhaul in this part of Remix development can have a powerful impact and spare so much time both for the devs and the users.
Wysłane z mojego Nexus 4 przy użyciu Tapatalka
@RemixOS_Jason I've just checked how feedback for Phoenix OS looks like and they're ahead of you! Anyway, this is what I think is better than just e-mails, forms and forums - http://www.phoenixos.com/feedback/page/1
Unfortunetly they don't have everything translated to English yet, but I hope this will change.
Just a suggestion from my side.
UPDATE:
Phoenix is definitely not ahead, so I take my words back. The feedback page is still a mess and all bushy (Chinese).
Ventricle said:
@RemixOS_Jason I've just checked how feedback for Phoenix OS looks like and they're ahead of you! Anyway, this is what I think is far better than just e-mails and forums - http://www.phoenixos.com/feedback/page/1
Unfortunetly they don't have everything translated to English yet, but I hope this will change.
Just a suggestion from my side.
Click to expand...
Click to collapse
I fail to see how that is any better that Jide's feedback forms form1/form2 or the submit a request
That page from PhoenixOS looks just like a nonsensical mess that there team would need a crystal ball to decipher what the posters 'issues' are.
HypoTurtle said:
I fail to see how that is any better that Jide's feedback forms form1/form2 or the submit a request
That page from PhoenixOS looks just like a nonsensical mess that there team would need a crystal ball to decipher what the posters 'issues' are.
Click to expand...
Click to collapse
It's true that the page looks a bit chaotic and as if people don't suggest anything useful (technical) to devs - but THATS BECAUSE THERE ARE NO GUIDELINES. And of course it looks like alpha state feedback page which isn't even translated to English yet. The description text area in Remix feedback form is like those suggestions on Phoenix feedback page - it's simply bad, because it doesn't hint people how they should describe things and what should be mentioned.
I didn't say Phoenix feedback is perfect, I'm only suggesting what direction is good in my opinion. TouchPal uservoice page looks awesome and you can see that devs read these reports and they let you know wheter they will add something or fix it. Also it lets community decide which things should be dealth with first - by upvoting them.
The forms you mentioned seem quite inefficient to me (except the booting problems one - it's great) - you can only describe a bug or a problem, you can't attach any error files and the forms don't ask what camera, audio, bluetooth devices you have. What's important - after you send it, you will never get a notification about anything coming to life - you can only hope that the next OS release will include fixes you need.
I've spoken to few devs and they usually need logcats dmesg files and as much HW info as possible. This form is just too poor to provide nice information and a gazzilion of people can report the same thing.
Instead, I'd rather visit f.e remixos.uservoice.com search if someone has the same problem as me and then if I find it, I'd upvote it and maybe add a comment. In other case, I'd post a new "ticket" following specially written guidelines on how to report/suggest stuff.
To sum up, feedback needs:
1. Guidelines on how to report (error files, which apps to reproduce etc.)
2. Anti-redundancy filter - upvoting existing feedback reports
3. More direct contact with devs - by them replying to feedback when it's a major or very popular issue (then it's not a waste of dev team's time, because it's like replying to hundreds or thousands of people) and ITS PUBLIC.
4. After a new version of system is released, the devs should also point volunteer testers to what they should focus on in testing.
Trust me, this may seem like devs will have to focus on community instead of real work, but actually if this is better designed and more efficient, they will eventually spend way less time on it then they might now.
Also using Google Groups to get to the community is a mediocre measure in my opinion. I get that it's free, has google class stability and requires almost no time to maintain or set up, but it's hugely inefficient, chaotic and inconvenient.
Remember, I only want to help improve Remix, so I suggest what may be better. I'm on Jide's side, specially now when they have Android-x86 founder working with them.
Ventricle said:
Hi,
I'd like to get some very important info from Remix OS dev team.
Users unrelated to the dev team or with no android-x86 OS dev experience, please DO NOT attempt to answer these questions.
Could you please make a thorough guide on how to report bugs, suggestions, feature requests and hardware incompatibilites?
Which tools should we use to report bugs or hardware problems - be precise please. Current feedback form seems very modest and inefficient.
Except for bug description and device info should we provide a full logcat, dmesg, per-app logcat - please point out the most effective way to report this stuff.
Where should we post feature requests or suggestions?
I personally think, that e-mails or forum threads are really inefficient for this. I'd recommend using Uservoice service (https://uservoice.com) or something familiar . Example of uservoice usage in practice: https://touchpal.uservoice.com/ There are plenty of web services like these and they are very powerful and efficient.
Perhaps there is a web service that would help making an official list of supported hardware?
Remix OS, Android-x86 and Phoenix OS all base pretty much on the same ground here, so they could share same list, but none of these actually has a nice, neat tool to report supported hardware. Except for a list of officially supported devices, it's a total mess.
I know that ChromeOS with android apps support and upcoming Android releases may be groundbreaking for whole Android-x86 related projects, but if we mobilize ourselfs and use all resources efficiently, I'm pretty sure Remix OS can become very popular and liked. Devs - help us, users, help you achieve that.
Right now it seems like you don't really care about other devices compatibility or about what people may report. If you did, you would provide better tools for that in order to do your work more efficiently. Don't take it as offense, it's just cirtical point of view.
Please optimize that - this will help speed up the development process and community contact a ton.
Please reply Remix OS, Jide, @RemixOS_Cameron , @RemixOS_Guannan , @RemixOS_Jason , @RemixOS_Josh , @RemixOS_Joshua , @RemixOS_Valentina , @AmoraRei
Click to expand...
Click to collapse
Hey Ventricle,
Again, thanks for your comments on our communication channels. I've consolidated our feedback channels into their core functions and how one can access them. In short, we're constantly trying to improve so we'll take a step back and evaluate how this can be done better. As of now, here is the short guide on how to communicate with us most effectively:
Feedback/bugs channels
Remix OS for PC: Google form: https://docs.google.com/forms/d/e/1FAIpQLSeqaTBTPzHgjwUKtn08zUDusKTYXQtG8mLczmo7D6bDgd_17A/viewform
Remix Mini: Go to power options, select â??Report a problemâ?
Remix Ultratablet: Go to power options, select â??Report a problemâ?
Feature requests/suggestions
Help Center: http://support.jide.com/hc/en-us/requests/new
Official list of supported hardware
Remix OS for PC
Google group: https://groups.google.com/forum/#!forum/remix-os-for-pc
Thanks and I hope this helps,
Jason
Could we have a development road map somewhere please? I would like to know what the devs are working on and where we are heading. I would like to know what to expect in a future release. At least what's the plan in general terms. I feel it's a bit too quiet when we talk about future releases/versions/patches.
Still no improvement?
@RemixOS_Cameron , @RemixOS_Guannan , @RemixOS_Jason , @RemixOS_Josh , @RemixOS_Joshua , @RemixOS_Valentina , @AmoraRei
Still no improvement in how you gather feedback and still no guidelines for reporting issues and giving the feedback. Why is that? This is as important as education is for a country - no education means slow or no development.
If you invest just a little more effort and time into what I suggest, I guarantee you huge improvement in feedback value and that will result in faster development. Also this will truly involve users in the development and make them want to support the idea even more.
If you don't like the Uservoice methods then I suggest you making a seprate repository on GitHub called f.e Remix OS feature requests, Remix OS problem reports, Remix OS hardware incompatibilities etc.
In these repositories, people could make Issues that your actual devs could assign to future builds or at least they would acknowledge them - people would actually feel like devs really read their feedback!
This way, people would also be able to sign under existing issues instead of duplicating them. Just like here:
https://github.com/FortAwesome/Font-Awesome/issues/878
Look just how awesome this can be:
https://github.com/FortAwesome/Font-Awesome/issues
I honestly can't understand why you neglect this part of Remix OS.
It's beyond my imagination how a company like this uses such inefficient feedback tools.
I know you use Zendesk for feature requests, but doesn't it have an option to make requests public? It'd avoid duplication of requests. Maybe it's possible to view all reports; both feature requests and problem reports? But users just don't know about it?
It could be so much better with the tools I mentioned. Come on... use them!
Please reply and let me know what you think of my suggestions.
dag u done tagged everybody ?. I see u and I forward ur message.
Ventricle said:
@RemixOS_Cameron , @RemixOS_Guannan , @RemixOS_Jason , @RemixOS_Josh , @RemixOS_Joshua , @RemixOS_Valentina , @AmoraRei
Still no improvement in how you gather feedback and still no guidelines for reporting issues and giving the feedback. Why is that? This is as important as education is for a country - no education means slow or no development.
If you invest just a little more effort and time into what I suggest, I guarantee you huge improvement in feedback value and that will result in faster development. Also this will truly involve users in the development and make them want to support the idea even more.
If you don't like the Uservoice methods then I suggest you making a seprate repository on GitHub called f.e Remix OS feature requests, Remix OS problem reports, Remix OS hardware incompatibilities etc.
In these repositories, people could make Issues that your actual devs could assign to future builds or at least they would acknowledge them - people would actually feel like devs really read their feedback!
This way, people would also be able to sign under existing issues instead of duplicating them. Just like here:
https://github.com/FortAwesome/Font-Awesome/issues/878
Look just how awesome this can be:
https://github.com/FortAwesome/Font-Awesome/issues
I honestly can't understand why you neglect this part of Remix OS.
It's beyond my imagination how a company like this uses such inefficient feedback tools.
I know you use Zendesk for feature requests, but doesn't it have an option to make requests public? It'd avoid duplication of requests. Maybe it's possible to view all reports; both feature requests and problem reports? But users just don't know about it?
It could be so much better with the tools I mentioned. Come on... use them!
Please reply and let me know what you think of my suggestions.
Click to expand...
Click to collapse
@Ventricle - After receiving your message, I shared your suggestions with our PMs, engineering team and customer support. Long story short is, they are trying to work out the feasibility, the timing and the execution of your suggestions. Although I cannot confirm at this time if and when these changes will be made, I can tell you that it's not something they haven't thought of. It does come down to the internal planning, human resource allocation and execution. Thus, please give me a few days to reply to you about your suggestions. Thanks again for pushing us to improve!
Jason
Sure thing @RemixOS_Jason ,I understand it completely. Just you saying that gives the community the sense that improvements are coming.
I'm looking forward to your follow up on this issue.
Some high hopes there!
Cheers,
Karol
UPDATE:
Got a very informative and valuable quote from @RemixOS_Jason here:
RemixOS_Jason said:
@alz_uk - Wow! It's pretty clear you have it in your mind that we are quite an evil, greedy company! Not sure if I can make a dent in your opinion, but I thought it prudent to give you a transparent answer:
As @Vioner and other users have pointed out to us, they'd like to see a different user feedback system. However, we designed it because we in the International (meaning outside of China) PR, marketing and customer support team is two full time staff and 2 part time interns. This means that our resources are limited.
Thus, the way the system is currently designed is for us to:
1) gather feedback - this is what this form is for: https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
2) organize the feedback regularly - once a week, my colleague organizes all the feedback into topics and sections and prioritizes them based on volume of reported bugs, issues, and compatibility with specific devices. This includes issues like the audio over HDMI, black screen, Wi-Fi, Bluetooth, gaming, app specific, etc. Device specific is numerous, but consider this: currently we support roughly 65% of the PCs out in the wild. This means that there will be 35% of the PCs that just don't work for one reason or another yet. That also means that for every person with a PC that doesn't work, there are around 2 people whose PC does work. With a small dedicated engineering staff as well, we try to tackle these issues from a platform point of view. Thus, you've seen in some updates the fact that we worked on GPUs that were vendor or brand specific, rather than only tackle one specific set of hardware components in a reported device. This is where the feedback form helps us to gather data so that we focus on fixing the issues that affect the widest range of users first.
3) send the feedback to the engineers - when it reaches the devs, they tweak our prioritization order based on what's feasible and what's not in the short and long term. Thus, you can be certain that we know about outstanding audio issues (we all dogfood our prodcuts and so, there are colleagues who's Remix OS for PC machines also don't have audio coming out). However, if we haven't update with this fix, you can be certain that whatever we've tried haven't passed testing, or is in the process of testing. Thus, there are two layers of what we do with feedback: count them, and then see which ones we can actually fix.
4) The fixes we do come up with must pass internal and external testing.
5) If they do pass, they are put into updates.
The installer issue was pretty simple. Most 3rd party installer do work, but as we gathered feedback from back in Remix OS for PC based Lollipop, our product manager noticed a trend where some of the OTA issues were due to 3rd Party installers. Thus, we put out the message that we couldn't promise that 3rd party installers would work 100% to support future OTAs.
Releasing fixes take time because they need to be tested. If a fix worked for some, but might cause issues for others, we don't release that fix for a stable release. Let's take the black screen issue during installation as a case example. We gathered around 65 users' emails who had this issue during installation. When we had a fix, we sent out emails and a testing ROM just for these folks with the potential fix. After around a week, most reported that their issue was fixed and that they didn't experience any other significant issues after being able to boot Remix OS (outside of some minor app compatibility issues). Thus, after a few more days of testing internally in parallel with this tester group, we rolled into that update. If you didn't see the fix applied in an update yet, it's probably because it didn't pass testing internally, or with their related testers, meaning though some folks' issues got fixed, many did not, or it caused other significant issues.
With limited resources, we do tackle issues from a platform (CPU, GPU, broadcom wireless chip, etc.) and not focus on your device, or his device or her device specific. We also work with the patches that are given out by the Android-x86 team (of which their founder, Chih-Wei Huang actually is our tech lead on Remix OS for PC) as can be evident by the update that integrated their latest release (rc2). In fact, we are small enough as a startup that we welcome our user developers assistance. So much so that I'm trying to work on making GitHub a place where interested developers can work on projects with us (where applicable since most of Remix OS is closed source). This is how much we actually need your development help!
In the end, I beg you to consider that people in general post 4-7 times more likely if they have outstanding issues, and not because we fixed any of their issues. Thus (and I know this all too well as the manager of our forums here) it can seem like everything is terrible, that Remix OS for PC just doesn't work for anyone and that no improvement has ever been made, ever. However, I just need to remember that for every 1 person with an issue that we're still trying to resolve, there are many more where the fixes we've implemented have made a difference.
As a startup, having the amount of users we have is a blessing. As a startup, having the amount of users we have with the limited resources, I mean engineers and folks like myself who communicate with the community, has been challenging. But, I ask that instead of giving up on us or spiting us for being a "mind game" playing, evil, greedy company, that you work with us to make a difference.
It wasn't that long ago that we had users who called us out on forums and tell we needed to improve our feedback system, and they're right. I'm working on improving it to offer more transparency into the process without increasing our workload to the point where it's not sustainable. Those same users who called us out are now working with us to improve through our Ambassador program. So, the challenge is, can you help us rather than just spite us? Running a startup in the industry we're in isn't easy, but it's something we're passionate about. Clearly we can still get better. Please help us.
Thanks,
Jason Zheng
Head of International PR, and Community Management at Jide Technology
I'm also frequently on our Facebook page and Twitter page
Click to expand...
Click to collapse