Database Users

Request to the devs, new version, new thread

Please start a new thread when you put out a new version of your rom.
By the time the second version comes out for the really good roms it's impossible to follow all the issues as there can be upwards of 1000 posts in the thread. Starting at the back doesn't help because of all the "how's your battery life?" posts. Then again, maybe that's the problem.
Anyway, I REALLY appreciate the work you guys do on these roms and kernels. I just wish it were easier to follow the flow of development.
Thanks for listening.
<flame retardant shield UP>

+1 .... i am with you !!!

+1 . Yeah it so annoying to go through thousands of old threads...

Moved to general

Moved? Do the people I'm talking to ever look in "general?"

I support this all the way people always tell everyone to use search but you barely ever get what your looking for..

michaelh99 said:
Please start a new thread when you put out a new version of your rom.
By the time the second version comes out for the really good roms it's impossible to follow all the issues as there can be upwards of 1000 posts in the thread. Starting at the back doesn't help because of all the "how's your battery life?" posts. Then again, maybe that's the problem.
Anyway, I REALLY appreciate the work you guys do on these roms and kernels. I just wish it were easier to follow the flow of development.
Thanks for listening.
<flame retardant shield UP>
Click to expand...
Click to collapse
+100000000

Great suggestion. totally agree.

michaelh99 said:
Moved? Do the people I'm talking to ever look in "general?"
Click to expand...
Click to collapse
Well it doesn't have anything to do with developing..
Although you do make a pretty good point, it is a LOT easier just to update the thread with a new download link & change log.
It would also cut down on a lot of clutter in that section.
If you are running an older version of what that dev posted, you shouldn't post bugs unless it didn't say it was fixed in the newest version of what they posted.

Master™ said:
Well it doesn't have anything to do with developing..
Although you do make a pretty good point, it is a LOT easier just to update the thread with a new download link & change log.
It would also cut down on a lot of clutter in that section.
If you are running an older version of what that dev posted, you shouldn't post bugs unless it didn't say it was fixed in the newest version of what they posted.
Click to expand...
Click to collapse
Master, your thread specifically is almost impossible to follow because of the almost 10,000 posts in it.
The easy fix to your update example above:
1) go to post for last release
2) hit edit
3) Ctrl-A to select all and Ctrl-C to copy
4) Hit Cancel
5) Open new thread and Ctrl-V to paste
6) edit pasted text and hit preview
7) review the post and make corrections as needed
8) hit submit and wait for the flood

T313C0mun1s7 said:
Master, your thread specifically is almost impossible to follow because of the almost 10,000 posts in it.
The easy fix to your update example above:
1) go to post for last release
2) hit edit
3) Ctrl-A to select all and Ctrl-C to copy
4) Hit Cancel
5) Open new thread and Ctrl-V to paste
6) edit pasted text and hit preview
7) review the post and make corrections as needed
8) hit submit and wait for the flood
Click to expand...
Click to collapse
9. Delete the old thread.
I think it's more of a "Let's see whose thread can get the mot posts" type of thing. Because it actually makes little to no sense to update a thread from months ago that is full of non-existent issues and then ask people to search through that thread as if the answer is supposed to jump out at them. Luckily I have given up on trying to read threads.

kangxi said:
9. Delete the old thread.
I think it's more of a "Let's see whose thread can get the mot posts" type of thing. Because it actually makes little to no sense to update a thread from months ago that is full of non-existent issues and then ask people to search through that thread as if the answer is supposed to jump out at them. Luckily I have given up on trying to read threads.
Click to expand...
Click to collapse
Well first, you cannot delete your own threads nor close them.
There is a search button in the threads for a reason also..
I guess it could be a thing to get people into saying what version they are on when they report a bug/ask a question..
Just a thought

I have to say I kinda agree with the OP, although obviously from your point of view its just making work.
I run your Axura 2.1 ROM Master, and was feeling a little lag from it here and there. I was looking for one piece of information... "can I use OCLF with this ROM"... had bad experiences with Voodoo in the past.
Man, it was no mean feat to find this out. Eventually, I put the new Voodoo kernel on my phone and its running flawlessly (utterly love this ROM by the way man. Seriously. Better than anything out there by a royal mile), but it was a hugely frustrating process to figure out whether I had any other options. To get a definitive answer. Just to find something simple.
I've often asked people direct questions in PM, and got no response, or at least an unhelpful one. As a technical guy, but not a developer, any questions I have are usually pretty specific, and not newbie in nature, and finding the answer is a massive problem. One of the biggest hurdles to this is 1000+ post threads.
Sent from my SGH-T959 using XDA App

Master™ said:
Well first, you cannot delete your own threads nor close them.
There is a search button in the threads for a reason also..
I guess it could be a thing to get people into saying what version they are on when they report a bug/ask a question..
Just a thought
Click to expand...
Click to collapse
Personally I think the old threads should remain anyhow. They help to keep the versions separate, not everyone upgrades right away. People should post in the correct thread for their version, but right not this is not possible.
Also, the old, dead thread clean up is not the responsibility of the OP, but of the forum admin. I have owned and run many forums. I have used ikonboard, vBulletin, Invision Power Board, MyBB, Phorum, phpBB, and my favorite Simple Machines Forum. All of them have in the administrative back end the option to cleanup old dead threads with no posts with a set time frame.

Problem is rom gets updated, 300 posts of "OMG Thank You, flashing soon!!!!"

They don't care.. The only thing they care about is getting donations. Higher post conts = more attention = more donations. In summary: they do not care
Sent from my SGH-T959 using XDA App

grennis said:
They don't care.. The only thing they care about is getting donations. Higher post conts = more attention = more donations. In summary: they do not care
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Sorry, gotta call BS on this one. Based on recent events I can guess that you are speaking at least generally if not specifically to Master, and he already addressed (IN THIS VERY THREAD) his thoughts both for and against. In fact so far he has been the ONLY developer to come forward and state he would be willing to do this.
Your statement does not contribute in any way to the discussion at hand, and I personally to not appreciate anyone that posts in running threads just to flamebait and be defamatory. Please check yourself.

I think an easier and better solution exists.
The problem for us the users is that we cannot find which posts relate to which rom version, correct?
The problem for developers if we choose to open a new thread for every release is to follow all 20 threads.
An easy solution would be to have one thread for the rom as it is now, BUT with every update of the rom (and the first page) the developer can add another post with update details at the end of his thread (basically a simple post reply) and put a link to it on the first page in the change log.
This way people viewing the change log will have links to the parts of the thread that discuss that update, while developers won't have 20 threads to maintain.
Sent from my Nexus One using XDA App

Whether you are following 20 threads or the same number of posts in 1 thread the work is the same because you have to reply either way. Also, all versions in 1 thread plus people still using old versions leads to confusion, and confusion equals having to clarify which ultimately means more posts. If you subscribe to the threads and use proper subjects for the thread you should get an e-mail that not only tells you there was a reply, but to which thread version and you can prioritize your replies, ie. Current version I will answer that now, 3 versions back and he can wait until I am done with what I am working on or else he can upgrade. Also since the older threads will get posted to less frequently the chance of multiple posts after the e-mail is less, so if the question is something that was fixed in a newer version you can decide it is not even worth your time to reply. As a developer you can not do that now because there may be many replies after the one that triggered your subscription e-mail that you will not see until you visit the forum.
Trust me, I have run a BUNCH of forums, and 1 thread per version is a better idea for many reasons you have not even thought of yet. If you fully think it out you will realize that it is actually easier to keep track of the 2 or 3 most resent threads people actually pay attention to then try to track the last 2 or 3 versions in 1 thread.

I've run a few big forums too so I do know what im talking about.
With 95% of users upgrade to a newer version of the rom there would be no need to keep the threads for the old roms because no one will write there. But you can't delete them. So instead of having 20 threads with 20 roms, we will have 400 threads for 20 versions of those 20 roms if we follow your idea
Sent from my Nexus One using XDA App

Unite to get answered! (VoLTE)

Straight to the point,
Oneplus is really stubborn answering our questions regarding VoLTE update for Oneplus devices. Let's ask them daily by asking them openly on twitter with #opvolte and do not forget to tag @oneplus_Support and @getpeid. Screenshot attached.
Unite and get answered.
A disappointed customer.
Used LTE to post it. Couldn't call my friends to recommend this phone to them, no VoLTE.\

MakDroid said:
Straight to the point,
Oneplus is really stubborn answering our questions regarding VoLTE update for Oneplus devices. Let's ask them daily by asking them openly on twitter with #opvolte and do not forget to tag @oneplus_Support and @getpeid. Screenshot attached.
Unite and get answered.
A disappointed customer.
Used LTE to post it. Couldn't call my friends to recommend this phone to them, no VoLTE.\
Click to expand...
Click to collapse
+1

Vjdv
---------- Post added at 03:36 AM ---------- Previous post was at 03:35 AM ----------
MakDroid said:
Straight to the point,
Oneplus is really stubborn answering our questions regarding VoLTE update for Oneplus devices. Let's ask them daily by asking them openly on twitter with #opvolte and do not forget to tag @oneplus_Support and @getpeid. Screenshot attached.
Unite and get answered.
A disappointed customer.
Used LTE to post it. Couldn't call my friends to recommend this phone to them, no VoLTE.\
Click to expand...
Click to collapse
Cardinal AOSP added volte support for the OnePlus X in their latest release... Can it be ported and added to this rom.?
Link: http://forum.xda-developers.com/oneplus-x/development/rom-cardinal-aosp-t3408349

whoisvignesh said:
Vjdv
---------- Post added at 03:36 AM ---------- Previous post was at 03:35 AM ----------
Cardinal AOSP added volte support for the OnePlus X in their latest release... Can it be ported and added to this rom.?
Link: http://forum.xda-developers.com/oneplus-x/development/rom-cardinal-aosp-t3408349
Click to expand...
Click to collapse
See the last page-
Adesh15 said:
It is a device specific changelog.
It means that the ROM supports VoLTE but since our device doesn't have VoLTE enabled there won't be any ROM having VoLTE support till the Oneplus devs do something.
BTW I have tested it with Jio and it doesn't work.
Click to expand...
Click to collapse
Looks like our only option is spamming OnePlus on social media till they do something about it, or atleast give us an ETA.
Considering the amount of time they took to release an official marshmallow update (that too, just a community build), it might be as late as May 2017 before we see VoLTE on our OPX.
If you read their statements regarding VoLTE support, they have only mentioned that they'll be working with Jio to provide support for older devices. They have nowhere mentioned which devices they'll be supporting.
For all we know, they might end up offering support to only the OP2 and leaving OPO and OPX users in the dust.
TL;DR The more people that spam them on social media, the better the chances we have of getting VoLTE support.
I'm with you @MakDroid! Let's get #opvolte trending!

+1

Is AOSPA 7.2.2 Something You Would Like?

I have finally built it after trying different things, I fixed the problem myself. After receiving a whole lot of flak on my thread (that I intended to have this build already uploaded to) I have decided to ask if anyone wants me to create a thread for my sub-weekly builds. I will be building them as quickly as I feel they should be made (if errors happen) or weekly. Hope you guys are a little kinder this time to me. Or I might just stop replying to those comments. Anyways, let me know soon. Otherwise I'll take it as a no and just build it for myself.:good:

I am looking forward to it

Pls Share the Build.

Techie Android said:
I have finally built it after trying different things, I fixed the problem myself. After receiving a whole lot of flak on my thread (that I intended to have this build already uploaded to) I have decided to ask if anyone wants me to create a thread for my sub-weekly builds. I will be building them as quickly as I feel they should be made (if errors happen) or weekly. Hope you guys are a little kinder this time to me. Or I might just stop replying to those comments. Anyways, let me know soon. Otherwise I'll take it as a no and just build it for myself.:good:
Click to expand...
Click to collapse
This community is for sharing.You're more than welcome to share stuff that you feel worthy.
Though what you did the other day was incorrect,you'll get to know that yourself if you have a look at XDA rules.Just follow the rules and remember what is appropriate and what is not appropriate.
BTW,did you fixed the proximity sensor and random app crashes issue?

Please share. I've no idea what mistake you made and I really don't care too.

Mr.Ak said:
This community is for sharing.You're more than welcome to share stuff that you feel worthy.
Though what you did the other day was incorrect,you'll get to know that yourself if you have a look at XDA rules.Just follow the rules and remember what is appropriate and what is not appropriate.
BTW,did you fixed the proximity sensor and random app crashes issue?
Click to expand...
Click to collapse
I understand that about the rules and respect that and I admit I did not look at the rules regarding that, and I apologize for that. But it only took about a day to fixed the compiling problems, so all that whining to the mods to remove my thread was just plain unnecessary IMO. I will be more careful though now that I know that there are sensitive people here.
I'm not having any of that. Can you elaborate and maybe I can look into that more, what instance was it happening in? Remember I'm not associated with AOSPA on GitHub so I cannot make changes to the master. I'm still new to compiling ROMs and could probably use some insight on how and what is safe to modify on my local copy of the source. I was thinking about replacing jack compiler with the default toolchain now that jack has been depreciated.

Let me test this build out just to see what works/doesn't real quick and then I'll make another thread. I supposed it doesn't need to be flawless since I've seen worse ROMs pop up and they plain didn't half work. And sometimes they say to test it out yourself and report bugs... So I guess I'll upload it soon in a thread in the ROMs section.

Eagerly waiting for your build...

Techie Android said:
Let me test this build out just to see what works/doesn't real quick and then I'll make another thread. I supposed it doesn't need to be flawless since I've seen worse ROMs pop up and they plain didn't half work. And sometimes they say to test it out yourself and report bugs... So I guess I'll upload it soon in a thread in the ROMs section.
Click to expand...
Click to collapse
Yes,but devs only do that when they do blind builds aka builds for devices they don't have,since they can't test it themselves they release it to people having that device to test it out.
---------- Post added at 04:38 PM ---------- Previous post was at 04:31 PM ----------
Techie Android said:
I understand that about the rules and respect that and I admit I did not look at the rules regarding that, and I apologize for that. But it only took about a day to fixed the compiling problems, so all that whining to the mods to remove my thread was just plain unnecessary IMO. I will be more careful though now that I know that there are sensitive people here.
I'm not having any of that. Can you elaborate and maybe I can look into that more, what instance was it happening in? Remember I'm not associated with AOSPA on GitHub so I cannot make changes to the master. I'm still new to compiling ROMs and could probably use some insight on how and what is safe to modify on my local copy of the source. I was thinking about replacing jack compiler with the default toolchain now that jack has been depreciated.
Click to expand...
Click to collapse
Some apps and games which were supposed to work(since they work out fine on other ROMs) give force closes.
About proximity sensor, when you place your device during a call on your ear then the screen should turn off normally,but it doesn't(on official AOSPA) due to proximity sensor issues, although it can be fixed by using another firmware ,it should be fixed(ROM side changes) so that people can use other firmwares too if they want to.

It's up! https://forum.xda-developers.com/oneplus-one/development/rom-t3656901

Mr.Ak said:
Yes,but devs only do that when they do blind builds aka builds for devices they don't have,since they can't test it themselves they release it to people having that device to test it out.
---------- Post added at 04:38 PM ---------- Previous post was at 04:31 PM ----------
Some apps and games which were supposed to work(since they work out fine on other ROMs) give force closes.
About proximity sensor, when you place your device during a call on your ear then the screen should turn off normally,but it doesn't(on official AOSPA) due to proximity sensor issues, although it can be fixed by using another firmware ,it should be fixed(ROM side changes) so that people can use other firmwares too if they want to.
Click to expand...
Click to collapse
Yeah I had the proximity problem but never had my apps crash. But the proximity problem is fixed now.

can you build paranoid android with OOS blobs V3?
It uses 2.x right now, right?
also more video codec support?

Thread closed. Anything after this point I will not monitor. Go to https://forum.xda-developers.com/oneplus-one/development/rom-t3656901 to post.

so far aospa(just test it) in my OnePlus One has the following issues (official AOSPA from their website)
- The hardware keys light is broken(lights up whenever and for unknown time - also cannot be controller),
- The battery circle icon(my favorite) ...if you use the percentage, you can't see the percentage ...circle is having a thick layer(for some reason)
Didn't test it further as I can't have these obvious bugs, so back to LA-OS until it's better

[ROM][UNOFFICIAL] MIUI 10 with gapps

Can Any one port miui 10 for mi a1.
For What you all are developers.
No one can do this.
Anyone have dare to accept the challenge.
I think no one have.
If you feel. Then I am really sorry.

thenavin98 said:
Can Any one port miui 10 for mi a1.
For What you all are developers.
No one can do this.
Anyone have dare to accept the challenge.
I think no one have.
If you feel. Then I am really sorry.
Click to expand...
Click to collapse
People have already tried porting MIUI to Mi A1 with no success just yet. But don't worry, a lot of people are still working on it.
MOD EDIT by @gregbradley

Thread temporarily closed whilst i sort this out and move to correct section
Thread moved and re-opened.
In response to this questions remember rule 2
2.1 Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please don't direct profanity, sexually explicit language or other offensive content toward Members or their work. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.
2.2 Nudity: XDA is used by people of all ages, including minors. It is unacceptable to post nude or pornographic imagery, which includes the exposure of male or female genitalia and / or female breasts.
2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.
2.5 All members are expected to read and adhere to the XDA rules.
Click to expand...
Click to collapse

I'm working on an MIUI 9 GSI but nobody knows if this is even possible yet. It's all Experimental and nobody has ported a DSSI to GSI before.
Regardless, you can monitor progress and talk here - https://forum.xda-developers.com/pr...velopment/requesting-miui-10-treble-t3799025/

thenavin98 said:
Can Any one port miui 10 for mi a1.
For What you all are developers.
No one can do this.
Anyone have dare to accept the challenge.
I think no one have.
If you feel. Then I am really sorry.
Click to expand...
Click to collapse
The developers are not your slaves.
I request the MOD to delete this thread

wmfanboy25 said:
The developers are not your slaves.
I request the MOD to delete this thread
Click to expand...
Click to collapse
A mod has already judged the thread dude, look two posts above.

CosmicDan said:
A mod has already judged the thread dude, look two posts above.
Click to expand...
Click to collapse
My bad, didn't see that

Porting MIUI 10 would be really cool and my daily driver, but I guess this is impossible task. But still, fingers crossed.

TrueMS said:
Porting MIUI 10 would be really cool and my daily driver, but I guess this is impossible task. But still, fingers crossed.
Click to expand...
Click to collapse
It's not impossible lol. Nobody just wants to take responsibility with the release because it could be buggy and it's hard to maintain. A few of us have it booting and working fine. My reason for not releasing it though is because I want to make a GSI instead to help stimulate Treble development.

CosmicDan said:
It's not impossible lol. Nobody just wants to take responsibility with the release because it could be buggy and it's hard to maintain. A few of us have it booting and working fine. My reason for not releasing it though is because I want to make a GSI instead to help stimulate Treble development.
Click to expand...
Click to collapse
Maybe i can try your non gsi build? ;D

CosmicDan said:
It's not impossible lol. Nobody just wants to take responsibility with the release because it could be buggy and it's hard to maintain. A few of us have it booting and working fine. My reason for not releasing it though is because I want to make a GSI instead to help stimulate Treble development.
Click to expand...
Click to collapse
You have booted into MIUI ? That's great, are the MIUI services working ? Since i read in an another post for MIUI 9 that the services were not working since the device couln't be verified from mi servers

Thank you for your work.
Waiting to be able to prove miui in mi-a1

I've given up on MIUI GSI so now I'm reviewing whether to release MIUI just as a normal A1 ROM.
I still have work to do on it - the ROM I have right now is handcrafted. I will ONLY release it IF I can finish scripts to completely automate the build process (i.e. open source the work). Please don't bug me about it.
I will post updates here as they come in. Exams are on at the moment so it could be a while.

CosmicDan said:
I've given up on MIUI GSI so now I'm reviewing whether to release MIUI just as a normal A1 ROM.
I still have work to do on it - the ROM I have right now is handcrafted. I will ONLY release it IF I can finish scripts to completely automate the build process (i.e. open source the work). Please don't bug me about it.
I will post updates here as they come in. Exams are on at the moment so it could be a while.
Click to expand...
Click to collapse
thank you bro your my heroo broo <3

For those wondering, the main reason I will not release existing MIUI is because it's a straight port of nougat base from 5x. It doesn't work on my TWRP and I cannot dual boot, so I will never use it and thus cannot support it. I will not be an irresponsible dev who releases things that he won't use or test.
New work is based on Redmi S2, which is 8.1 based and will get MIUI 10 quicker. Since it's different hardware and based on China ROM, there is extra work to do.

CosmicDan said:
For those wondering, the main reason I will not release existing MIUI is because it's a straight port of nougat base from 5x. It doesn't work on my TWRP and I cannot dual boot, so I will never use it and thus cannot support it. I will not be an irresponsible dev who releases things that he won't use or test.
New work is based on Redmi S2, which is 8.1 based and will get MIUI 10 quicker. Since it's different hardware and based on China ROM, there is extra work to do.
Click to expand...
Click to collapse
Thank you so much. Why don't you take redmi Y2 ROM as it is the same rebranded version of S2 with global ROM?

Uvneshkumar said:
Thank you so much. Why don't you take redmi Y2 ROM as it is the same rebranded version of S2 with global ROM?
Click to expand...
Click to collapse
Oh really? Ha I had no idea, wasn't on GSMArena when I checked. If there's a global stable fastboot firmware for it then I'll switch to it's base. Cheers.

You can use Redmi note 5 miui 10 beta tester ROM for Xiaomi mi a1
---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------
And if you see paid theme in miui you can use xposed free theme module for mi a1 he bypass account verification too

CosmicDan said:
Oh really? Ha I had no idea, wasn't on GSMArena when I checked. If there's a global stable fastboot firmware for it then I'll switch to it's base. Cheers.
Click to expand...
Click to collapse
Yeah it was launched a few days back here in India and infact the first sale went yesterday. So wait for a little bit for its firmware to appear on the website..! It's Redmi Y2..! All the best..!

ajay9804 said:
You can use Redmi note 5 miui 10 beta tester ROM for Xiaomi mi a1
---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------
And if you see paid theme in miui you can use xposed free theme module for mi a1 he bypass account verification too
Click to expand...
Click to collapse
It's only Nougat, so no I cannot use it.
I will never port beta ROM anyway, only stable releases. Otherwise I can't be sure if it's a bug with port or the ROM itself.
Uvneshkumar said:
Yeah it was launched a few days back here in India and infact the first sale went yesterday. So wait for a little bit for its firmware to appear on the website..! It's Redmi Y2..! All the best..!
Click to expand...
Click to collapse
No problem, I have exams for the next week so hopefully it's out soon.

X

Instead of this ill try to post MY LineageOS rom for Mi Max 3 sooner than I expected
Please close this thread

To be deleted

To be deleted

To be deleted

Really!? Because it boots on another Xiaomi device you decide to post it here...!?
The XDA Mi Max 3 forum gets worst and worst every day... It's neck to neck with Xiaomi official forum already... What a shame...

nijel8 said:
Really!? Because it boots on another Xiaomi device you decide to post it here...!?
The XDA Mi Max 3 forum gets worst and worst every day... It's neck to neck with Xiaomi official forum already... What a shame...
Click to expand...
Click to collapse
I think such reply is uncalled for @nijel8. However true your reply may appear to you, It neither inspire people here to do better nor yield better understanding.
I would suggest that you start your own thread and exemplify what XDA should be. If people here find your way to be better, then hopefully they will follow suit.
---------- Post added at 09:17 AM ---------- Previous post was at 09:16 AM ----------
omer919 said:
I will update the thread with every patch / fix or new working installation process that you guys are going to post
Click to expand...
Click to collapse
Will be waiting for it. I've heard that OxygenOS really is a good ROM.

xgneilx said:
I think such reply is uncalled for @nijel8. However true your reply may appear to you, It neither inspire people here to do better nor yield better understanding.
I would suggest that you start your own thread and exemplify what XDA should be. If people here find your way to be better, then hopefully they will follow suit.
Click to expand...
Click to collapse
Have you red the flashing instructions? Ridiculous... I can't waste 1GB of my mobile data to take a look but I am pretty sure this is a TWRP backup from mido device and the fact that it boots straight to fastboot after restore it even includes mido boot partition with mido kernel!!! Now tell me how ridiculous this thread is... Oh, and this is not the first time this OP posts guides and stuff of this nature...
Users comes to XDA for help from knowledgeable people and they trust the information they read here. When misinformation, misguides and alike from people who don't have basic knowledge about Android development and how things works in general then how are we better from anything else out there...
We used to have those people who misrepresented themselves as advanced users throwing "advices" and roms and stuff from all over the Internet back in the Max 1 days but they disappeared very fast after publicly exposed from guys who knows better. I hate it when people gets advantage of the poor user!
BTW not to give any hopes but you will see soon what XDA is really about... Like this weekend soon(I hope...)

nijel8 said:
Have you red the flashing instructions? Ridiculous... I can't waste 1GB of my mobile data to take a look but I am pretty sure this is a TWRP backup from mido device and the fact that it boots straight to fastboot after restore it even includes mido boot partition with mido kernel!!! Now tell me how ridiculous this thread is... Oh, and this is not the first time this OP posts guides and stuff of this nature...
Users comes to XDA for help from knowledgeable people and they trust the information they read here. When misinformation, misguides and alike from people who don't have basic knowledge about Android development and how things works in general then how are we better from anything else out there...
We used to have those people who misrepresented themselves as advanced users throwing "advices" and roms and stuff from all over the Internet back in the Max 1 days but they disappeared very fast after publicly exposed from guys who knows better. I hate it when people gets advantage of the poor user!
BTW not to give any hopes but you will see soon what XDA is really about... Like this weekend soon(I hope...)
Click to expand...
Click to collapse
I agree that misinformation and misguides are not really helping, and may even cause confusion to most people. However, the OP was actually honest with his observation and goal for this thread. And isn't that part of learning experience?
Anyways, I'm hopeful that you'll also be able to come up with a reliable custom rom just like on mi max. Till then, I believe encouraging others to experiment will yield better results in the long run, not just for the community but for the person him/herself.

To be deleted