yashsingh1/xdaforums huggingface dataset:
[Remix OS for PC] Vioner:
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 , [MENTION=7236200]RemixOS_Guannan[/MENTION] , [MENTION=7226752]RemixOS_Jason[/MENTION] , [MENTION=7233799]RemixOS_Josh[/MENTION] , [MENTION=7234746]RemixOS_Joshua[/MENTION] , [MENTION=7314333]RemixOS_Valentina[/MENTION] , @AmoraRei
[Remix OS for PC] RemixOS_Jason:
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
[Remix OS for PC] Vioner:
[MENTION=7226752]RemixOS_Jason[/MENTION] 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
[Remix OS for PC] Vioner:
[MENTION=7226752]RemixOS_Jason[/MENTION] I've just checked how feedback for Phoenix OS looks like and they're ahead of you! :D 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).
[Remix OS for PC] HypoTurtle:
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.
[Remix OS for PC] Vioner:
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.
[Remix OS for PC] RemixOS_Jason:
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
[Remix OS for PC] or29544:
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.
[Remix OS for PC] Vioner:
Still no improvement?

[MENTION=7253066]RemixOS_Cameron[/MENTION] , [MENTION=7236200]RemixOS_Guannan[/MENTION] , [MENTION=7226752]RemixOS_Jason[/MENTION] , [MENTION=7233799]RemixOS_Josh[/MENTION] , [MENTION=7234746]RemixOS_Joshua[/MENTION] , [MENTION=7314333]RemixOS_Valentina[/MENTION] , [MENTION=7270817]AmoraRei[/MENTION]

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.
[Remix OS for PC] AmoraRei:
dag u done tagged everybody ?. I see u and I forward ur message.
[Remix OS for PC] RemixOS_Jason:
[MENTION=4666322]Ventricle[/MENTION] - 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
[Remix OS for PC] Vioner:
Sure thing [MENTION=7226752]RemixOS_Jason[/MENTION] ,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 [MENTION=7226752]RemixOS_Jason[/MENTION] here:
[G4 Q&A, Help & Troubleshooting] CiroP33:
Hi everyone, I love modding but I'm worried to lose warranty. Can you tell me which are the real advantages to have warranty? Thank you so much for your time.
[G4 Q&A, Help & Troubleshooting] sergioreis:
transfer app to sd

The main reason I use to rot is to use program like Link2SD. The internal memory is never enough for everything.

I think the only advantage is about the warranty, and depending on the root can have malicious code behind.
[G4 Q&A, Help & Troubleshooting] joelalmeidaptg:
You can move apps to the external sd card by going to the Settings > Apps > Select an app > Storage and then hit Change. I don't think you need to use such kind of tools ;)
[G4 Q&A, Help & Troubleshooting] arvarobert:
But can't do it with every app.
[G4 Q&A, Help & Troubleshooting] sergioreis:
Yes, the biggest use to not accept change to SD
[G4 Q&A, Help & Troubleshooting] steadfasterX:
In MM you can use an external sdcard as internal storage! Android will move apps then auto magically to the sdcard. No need for root no need for tools like link2sd anymore. Correct me if i miss a point here. :eek:
[G4 Q&A, Help & Troubleshooting] mulperi:
I use Afwall+ firewall to control which apps may call home. Second usage is AdAway that modifies your hosts file to block most ads in all apps, not just browser. A minor goodie is ClockSync that keeps your clock spot on.
[G4 Q&A, Help & Troubleshooting] raptorddd:
you can root with locked bootloade and install xposed.. i have locked bootloader.. for warranty.. search google and youll find how to.
[G4 Q&A, Help & Troubleshooting] kabirjedi:
why opena again 123456577. root or not topic???Use the search options pls.

Moderator close this pls.Thanks!
[G4 Q&A, Help & Troubleshooting] OllieD:
you do know root still voids warranty don't you?

LG have a root checking tool RCT that logs if you have rooted your device.
[G4 Q&A, Help & Troubleshooting] raptorddd:
not if you flash stock firmware.. or in the case of bootloop disable main core and root will be deleted when you flash stock KDZ. but unlocking bootloader you must ask LG for unlock.bin key , so i guess they have record that you requested the unlock key.. some have requested key , and say they didnt use it , got bootloop sent for repair and warranty was void and phone wasnt unlocked..
[G4 Q&A, Help & Troubleshooting] mulperi:
You can always pay for service if you cannot get out of boot loop yourself.

I think it is a risk worth taking considering benefits of rooting.
[G4 Q&A, Help & Troubleshooting] EPa:
Who says that? Can you provide links?

Even LG says your warranty is void if you *unlock*, not if you just download the unlock.bin..
[G4 Q&A, Help & Troubleshooting] kiddhern:
If anything happens and your phone has KDZ outs you can just use LGUP to go back to complete stock. I had a boot loader unlocked flag on boot and i used that to get rid of it when I had a bootloop and had to send my phone in for warranty repair.
[G4 Q&A, Help & Troubleshooting] EPa:
You're saying a bootloader unlock is reversible/concealable?
[G4 Q&A, Help & Troubleshooting] raptorddd:
its on the bootloop g4 thread... i can provide a link to a way to relock bootloader ... i have not try it..

well apparently thats what one guy said, since they might have record that you downloaded and requested unlock . bin cause i think they ask for something not sure if serial number or imei... so the guys said he assumes they have it on record and belive you unlock it...

link for relocking..

http://xdaforums.com/tmobile-g4/help/relock-bootloader-h811-t3372970
[G4 Q&A, Help & Troubleshooting] EPa:
I asked proof about what you wrote concerning:

LG denying service on the basis of their "who downloaded unlock.bin" database, *even though the device was NOT unlocked*.

Is there any? I would really like to know.. That guy you're referring to, can you find the post please?

Edit: ok, I just noticed the words "thinks" "assumes" and the like. I have read the posts, so don't bother looking. These are not personal experience posts, just assumptions.
[Nexus 7 (2013) Q&A] hekat0n:
My beloved N7 2013 fell victim to the eMMC-nuking 5.0 (unsure about exact version) OTA update last year. I put off replacing the motherboard, as I had already bought a new tablet. Lately, though, my N7 itch returned. I was able to successfully replace the motherboard, but the replacement I purchased was also Kingston...much to my chagrin.

Anyways, I updated the new motherboard to 4.4.4 via OTA, and forewent the next OTA (5.0 OTA update). Things are smooth, and my tablet has been resurrected.

My question, then, is two-fold. First, is the 6.0.1 stock update worth the hassle of running a clean install? And second, will I run into the same problem that killed my N7 the first time (update nukes eMMC)?

I tried to find a thread where this has been discussed, but I must not fully understand searching for things on this site. Thanks for your help!
[Nexus 7 (2013) Q&A] graphdarnell:
Amazing how you'd consider throwing good money after bad. If you insist on everything stock, you assume the risk, random though it might be with MM. There are plenty of custom roms that mirror stock almost totally, why the insistence? What's so sacred about it?
[Nexus 7 (2013) Q&A] quickdraw86:
There was a known write loop error in one of the 5.x OTA updates that baked boards, but the Kingston boards are generally known to be unreliable among the three common boards for razor. Long story short, you have nothing to lose by updating to the latest OTA, 6.x adds nice features, runs well, and has the latest security updates and compatibility with the latest popular apps. Bricks on 6.x OTAs seem random, and are most likely related to instances of hardware failure on individual devices that developed over long periods of device use, than from a single software update causing or contributing to a hardware failure.

The users here have been contributing to a thread regarding this issue, it can be found here.

It's worth mentioning that instances of eMMc failure on devices running custom ROMs are far fewer in number than instances of bricks on stock devices.
[HTC 10 Questions & Answers] MissPokita2006:
I just got my htc 10 today. I am trying to unlock the bootloader. I have the unlocked us model so i know it is not locked. every time i try to select my identifier token it always highlights extra parts. I tried copying and pasting the whole block of text and deleting the extra words but htc dev still wont give me my unlock code. Is it possible to have someone send me a unlock code file to unlock my bootloader or am i stuck with a locked bootloader for life. Any help would be great. I can provide my email if needed.
[HTC 10 Questions & Answers] schmeggy929:
there are extra spaces at the end too you have to delete. You can't use someone's unlock_token.
[HTC 10 Questions & Answers] Lancerz:
Are you using windows 10? I had the same issue. If you enable legacy options in the command window it will make it so only what you highlight will be selected. Right click the top bar in the cmd window to access the options. And you can just request a new token if that one doesn't work, since the code changes.
[HTC 10 Questions & Answers] MissPokita2006:
That worked perfectly thank you. I didnt know windows 10 had that issue
[HTC 10 Questions & Answers] jollywhitefoot:
nice tip. thanks
[HTC 10 Questions & Answers] Lancerz:
Trust me I was pulling my hair out too, it was driving me crazy. I was at the point where I just started messing around in options and when that worked I was jumping with joy lol.
[HTC 10 Questions & Answers] MissPokita2006:
i just tried to finish unlocking the bootloader however it falied and my phone is stuck in download mode it says flash image success and will not turn off or reboot is my phone bricked
[HTC 10 Questions & Answers] Lancerz:
Try typing fastboot reboot bootloader
[HTC 10 Questions & Answers] MissPokita2006:
i got it to reboot. Why wont the unlock bin flash. I have it in the folder where my adb files are on my desktop
[HTC 10 Questions & Answers] MissPokita2006:
C:\Users\darkh\Desktop\adb> fastboot flash unlocktoken Unlock_code.bin

target reported max download size of 800000000 bytes

sending 'unlocktoken' (0 KB)...

OKAY [ 1.007s]

writing 'unlocktoken'...

(bootloader) flash unlocktoken

(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp

(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock

FAILED (remote: UnlockToken Verify Fail!!)

finished. total time: 1.079s

C:\Users\darkh\Desktop\adb>
[HTC 10 Questions & Answers] Lancerz:
I had that same issue too, I think I just got another unlock.bin and the second one worked
[HTC 10 Questions & Answers] MissPokita2006:
That did the trick. I am gonna try to root and s off now. Ill post if i have any more questions
[HTC 10 Questions & Answers] Lancerz:
Cool, good luck. What rom you plan on running?
[HTC 10 Questions & Answers] MissPokita2006:
i really want to run viper rom. i love the customation features and ota updates. I just have to check and see what superuser app to use because i know the htc 10 has that issue where if you dont do everything right you lose your cell signal.
[HTC 10 Questions & Answers] Lancerz:
Once you install twrp you can just flash viper and it will already be rooted so no need to root it on it's own. I'm running Viper also and it has all the customizations that I love!
[HTC 10 Questions & Answers] MissPokita2006:
after I s offed my phone sayes s off locked im assuming that is what jcase was saying when sunshine gives you the option to soff and with the new version s off locked is the same as s off unlocked correct? since i am s off locked i should have all s off and unlocked privilages like normal even with the s off locked status if so i can take a break for a while lol
[HTC 10 Questions & Answers] Lancerz:
I can't help you with that since I didn't see a need to S-off for me.
[HTC 10 Questions & Answers] Android The Greek:
Are you in FL mode or bootloader mode. Should be in DL mode

---------- Post added at 06:26 PM ---------- Previous post was at 06:23 PM ----------

I don't think it matters unless you want to flash TWRP again. If you are running the RUU.exe it doesn't matter.
[Paranoid Android Q&A] asolo157:
Hi, I am using the new Paranoid Android on the Nexus 6p on AT&T. It's great. However, the tethering option in settings is grayed out. I have tethering in my plan, and tethering worked fine on other ROMS. Does anyone have any idea why this would be happening and how to fix it? Thanks.
[Paranoid Android Q&A] LHCCollider:
running same on Sprint, my tethering is grayed out as well.
[Paranoid Android Q&A] snipinu:
You will have to edit your build prop to get tethering to work, do a search on XDA and the thread should show up
[Off-topic] PoseidonKing:
Hello there, guys! Ever wanted a cool signature for your XDA profile? Well, you found out the correct thread! All kinds of requests will be accepted and I'll fulfill them ASAP. Just pm me your ideas about your signature, I'll make it as per your request, guaranteed! ;)

For instance, you can look at my own signature.

I'm gonna upload some samples of my signatures.. Hope you like it!

Regards,

PoseidonKing
[Off-topic] PoseidonKing:
Sample signatures
[Off-topic] Trafalgar Square:
In Off Topic section, there is no thanks button :D
[Off-topic] PoseidonKing:
Yep, I figured!
[Off-topic] PoseidonKing:
New templates and designs coming soon...

Stay Tuned!!!

Regards,

PoseidonKing
[Off-topic] PoseidonKing:
Man, I ain't uploading the templates on the thread. If you want a signature, pm me your ideas and all. I can make game signatures too, I mean, game templates for your signatures..

Regards,

PoseidonKing
[Off-topic] adityaupreti:
[MENTION=6515701]PoseidonKing[/MENTION], i need some banner and graphics logos for my rom

https://github.com/Toxic-OS
[Off-topic] PoseidonKing:
Sure! I'll make some and pm you..

Regards,

PoseidonKing
[Off-topic] adityaupreti:
THank You
[Off-topic] uts58:
just my nickname with master yi backgroud!

Thanks a lot!!!