Related
What I miss at this forum, is a ROM with a honest, complete list of known bugs/non-working stuff.
Would like to see some quality-control, and know what I install - before I do.
Everybody is cooking ROM's (and that's nice) but there's no way to know how they will work before trying.
-its impossible to read thru >200 posts and figure out which of those are about the current version.
-recent posts are sometimes about earlier versions too...
Please: I hope some of you that des this nice job will focus on information about quality, and keep a "buglist" for each version..
AlCapone said:
What I miss at this forum, is a ROM with a honest, complete list of known bugs/non-working stuff.
Would like to see some quality-control, and know what I install - before I do.
Everybody is cooking ROM's (and that's nice) but there's no way to know how they will work before trying.
-its impossible to read thru >200 posts and figure out which of those are about the current version.
-recent posts are sometimes about earlier versions too...
Please: I hope some of you that des this nice job will focus on information about quality, and keep a "buglist" for each version..
Click to expand...
Click to collapse
I agree 100% Buglists are a must. Roms shouldn't be released with alot of bugs unless stated by the op.
husker91 said:
I agree 100% Buglists are a must. Roms shouldn't be released with alot of bugs unless stated by the op.
Click to expand...
Click to collapse
I think the point you're missing is that the bugs only become apparent after others flash the ROMs and do some testing.....
cr1960 said:
apparent after others flash the ROMs and do some testing.....
Click to expand...
Click to collapse
nope - the author/or a helper is in the ultimate position to read the feedback, verify, and make a list in the first article containing these bugs.
i did not say that the cook should know about every bug before releasing.
maintain a list, and verify it against next version.
-the only way to have some quality control...
I agree with the sentiment - for those of us who only flash their phones maybe once a month, it would be nice to know a ROM is ultra stable and all known bugs / oddities have been sorted. (or if not, then a comprehensive list of things that are broken, with any workarounds etc) Reading through thousands of posts takes hours and not everybody has the time or inclination for that.
For instance both WM and Manila (and others) are under very active development, there are always new versions coming out. While it would be unreasonable to expect the beta WM builds (23xxx, 28xxx) to be 100% stable, it would be nice for a cook or two to say "right, this combination of components is stable, I'm going to stick with these for a while" instead of always following the very latest cutting edge "LOOK, SHINY TOYS!" at the risk of stability.
As for stability I am currently on JoshKoss's latest (1.7) and have yet to experience a single error, crash or hang. And Josh's seem to be the fastest ROMs, definitely of the ones I have experienced anyway. There are a few minor inconsistencies but these are in no way critical. If you want stable I would not even consider Manila 2.5 or any of the "start menu at the bottom" ROMs.
Have you tried AthineOS ROMS? Very fast, very stable. The current Leo 2.02 based ROM is the fastest Sense 2.5 ROM I've tried (and I've tried them all) and stable enough for hassle-free day to day use.
Guyz As far as my experience goes no cook likes to hide the bug list, rather they work to bring more in the light. Users like us are expected to give our submissions. Thats how it works. Things like quality control is not what we have seen here since its not GM factory but a place to share & experiment & success & failure is part of that place.
AlCapone said:
nope - the author/or a helper is in the ultimate position to read the feedback, verify, and make a list in the first article containing these bugs.
i did not say that the cook should know about every bug before releasing.
maintain a list, and verify it against next version.
-the only way to have some quality control...
Click to expand...
Click to collapse
I completely disagree. At the rate new builds are released, and with so many new tweaks and items going into ROMs, I think it would take forever for the chef and a select few beta testers to try and figure out all or most bugs in a ROM. I use Arrups ROMs, and he discloses everything that he can, but ultimately its not the chefs responsibility to create a "perfect" rom for Al Capone is it? Everyone uses different applications which can affect the stability of a ROM completely-for example Opera beta 10. I think its much more efficient to have them release the ROMs and let lots of people try and break them, then come back and fix it. And when bugs arise the are put on a "bug list" to be fixed.
We would never see new ROM releases for months if we waited for chefs to perfect stuff. So the people who just flash and leach ROMs cant help out a little?
Since you are so anxious about having a perfect ROM, why dont you have a go at it? Or is *****ing easier?
MadBeef said:
As for stability I am currently on JoshKoss's latest (1.7) and have yet to experience a single error, crash or hang. And Josh's seem to be the fastest ROMs, definitely of the ones I have experienced anyway. There are a few minor inconsistencies but these are in no way critical. If you want stable I would not even consider Manila 2.5 or any of the "start menu at the bottom" ROMs.
Click to expand...
Click to collapse
X2, This is a very stable ROM. I have been running it close to 2 weeks with no real issues & haven't had to soft reset because of a glitch or hang up.
I have to chime in here and agree with the sentiment of this thread. The application of it is much more difficult that it seems. I have been down this road before, trying to get the chefs to post a comprehensive bug list for their ROMs and while they are willing to do it, it is VERY difficult to tell what is a real bug and what is OE (operator error), confusion caused by loading some application, etc that really isn't a bug or a real bug.
For example, I have been running Sergio76's EVO 3 ROM for sometime now, and have absolutely nothing bad to say about it. Stable as hell, fast, good memory, good battery etc. But some of the other users of the same ROM find 'bugs' mostly caused by putting different shells on, or trying to icon sets.
So, my point is BRAVO! this needs to be done, but let's have a good discussion of how to categorize what is a bug, what is an incompatibility, etc. Because, if we simply list all these things as bugs then we run the risk of scaring folks off of flashing a potentially GREAT ROM all because one or two guys muck it up by hacking the registry and it gets put on a bug list.
I would also like to see a 'standard' way all the chefs list bugs, etc.
Russ
iceman4357 said:
why dont you have a go at it? Or is *****ing easier?
Click to expand...
Click to collapse
bit harsh tbh
MadBeef said:
bit harsh tbh
Click to expand...
Click to collapse
I was actually holding back a lot. Unfortunately 90% of people on here dont contribute anything and just expect stuff to happen perfectly. If its so easy, then instead of creating an entire thread to talk about problems, why not make a "perfect" Rom and contribute.
iceman4357 said:
Since you are so anxious about having a perfect ROM, why dont you have a go at it? Or is *****ing easier?
Click to expand...
Click to collapse
your own *****ing certainly does not help.
read my lips:
-I do NOT ask for a "perfect" ROM
-I just ask for the cook/helper to browse thru the reply-posts, and add known bugs they can confirm, to the first post - the one that contains the ROM
-So any ROM can have a list of known errors, (the the author confirms)
AlCapone said:
your own *****ing certainly does not help.
read my lips:
-I do NOT ask for a "perfect" ROM
-I just ask for the cook/helper to browse thru the reply-posts, and add known bugs they can confirm, to the first post - the one that contains the ROM
-So any ROM can have a list of known errors, (the the author confirms)
Click to expand...
Click to collapse
So the chef should worry about reading the 200 posts that you were worried about reading instead of working on ROMs? I am sure that chef mailboxes are full of people reporting bugs on a daily basis.
There are people other than the chefs that have a good deal of experience that help within the thread posts, that free up the chef to continue experimenting and cooking ROMs.
A lot of "common" bugs are specific to builds, such as the landscape issues vs touchflow(sense), or GPS lag which take a lot of time and programming to figure out. These are commonly known across ROMs and builds.
A lot of smaller bugs are from individual customization errors like with S2U2, Opera Beta, lack of knowledge, or custom tweaking.
Chefs, in my opinion, are here to provide a decent platform ROM for us to costimize individually; not to help each individual person with each custom problem they have.
x2
Montea said:
X2, This is a very stable ROM. I have been running it close to 2 weeks with no real issues & haven't had to soft reset because of a glitch or hang up.
Click to expand...
Click to collapse
can u link me up with the x2 rom u speak about?thanks
oyebee said:
can u link me up with the x2 rom u speak about?thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=572938
We were on about JoshKoss's ROMs.
I've said this for years, something like bugzilla would be good. Not that I have ever used it but something with a bit of structure you know? Flag bugs by component (ie. Manila footprints tab, lock screen, or whatever) then by ROM so the system will know already if it is ROM specific or not. But it still relies on people adding good data, as the saying goes, "Garbage In Garbage Out". An automated config dump tool would be a good step towards that. (an end-to-end "report bug" app would be awesome) After all I don't know what point release of Manila I'm running (1921? 1922??) because I don't really care unless it breaks, or a newer version has more shiny.
Anyway I said this a while ago and we are still "*****ing" about ROMs at a fairly disorganised level, and yet the cooks continue to work their magic, so it can't be all that bad
From another guy who comes on here with not very much to offer yet continues to leech a new ROM once a month or so
Stop the Madness...
Oh Geez....
Yes, I am one of the lurkers here at XDA, having been flashing my phones for years and not really contributing much to the community.
I have made a New Year's resolution to change that, so I am posting more now.
But look at some of the most popular ROMS....
Within hours of a Chef releasing a new version, there are hundreds of posts about it.
From what I gather, 95% if not more of these guys/gals cook up these ROMs in their spare time. They do it because they like to do it. I don't think anyone here is getting rich cooking up a ROM for my TP2. They all have lives and when there can be 40+ pages of posts within a couple days after they release a new version, I don't expect them to read every single one. Especially where a vast majority are people asking how to flash the ROM, how to change the theme or other posts that a simple search would provide the answer.
Most Chefs do post what was fixed, what was improved and a lot of them post issues in their ROMS.
I have spent hours reading page after page trying to figure out an answer to a issue I have had...knowing I was probably not the only one having it.
Do some Chef's not post as much info as I would like? Yes.
Am I going to berate those Chefs for not doing so? No.
Some of the responsibility has to be on the users. Period.
For example, I was and am a fan of the Energy ROMs. But I SMS an insane amount and the newest Leo interface with the HTC messaging client sucked, period. Not to say NRGZ28's ROMs sucked, quite the contrary, they are great. But did those ROMs fill every need that I specifically had? No.
So, I did some research, and I found in a thread where Agent_47 suggested his ROM because he didn't even cook in the HTC SMS messaging client. So, I looked at his thread, flashed the ROM, and realized that I have had no issues with it and am very happy. Stable, works and I don't have to wait 7 minutes sometimes to send a text to someone!
We are all very lucky to have XDA. We are all very lucky to have the Chefs that spend their own time, and a lot of it, to cook up these excellent ROMs for us to flash.
Instead of complaining about the lack of 'bug lists'...perhaps you could create a tool or set something up to help the Chefs better manage those said lists?
That is the spirit that has and continues to make XDA great, if there is something you want, something that you see lacking, then create a tool to fill that void.
If you don't want to do that, then I suggest getting an iPhone, where you are locked into your OS and a slave to Apple and their constant updates and static interface. Cool device, granted, but I prefer the freedom of flashing, the excitement of trying new interfaces, experimenting with new features and lastly, the great folks here at XDA.
\.end rant
Spankmeister said:
I suggest getting an iPhone
Click to expand...
Click to collapse
Let's not get silly
Rom Port Team Effort
Hello P880 community.
This post has the purpose to put together a group of users / developers, who are willing to participate into bringing a different set of roms into our community.
These set of roms that I'm thinking, can range from complete Sense ports to more customized and maybe less popular roms (like ColorOS, LiGux, FlymeOS, FluidUI, etc..).
What's valid on this thread:
- CM / AOSP (any base we already have) themed (like Samsung TouchUI, Optimus, Blur, etc..). So you can grab any rom (with author authorization), theme it (i mean, not just shove an apk as default theme, I mean neat theming ).
- Ports from other devices (evert port needs to have clear authors permission to port it).
- All users are very welcome, everyone can participate, users with porting / developing skills are needed as well.
The idea is simple, we're not going to use this thread to post the work, this is just a thread to talk about possible projects.
We can start by listing which devices are hardware compatible and the port is "easily" possible.
Roms that can be used as a base for eventual future ports.
CM10.2 - thanks to laufersteppenwolf for compiling this build promptly for this purpose
http://goo.im/devs/laufersteppenwolf/CM10.2//cm-10.2-20140305-UNOFFICIAL-p880.zip
- - - - -
I strongly recommend the use of MultiRom for testing ports and other roms. That way you can maintain your working rom and whenver feeling adventurous you can without going through the hassle of backup / restore / yada yada yada that we are all too familiar with.
http://forum.xda-developers.com/showthread.php?t=2655988
- - List of Devices with hardware similar / close / identical to the 4X - -
- HTC One X
- HTC One X +
- More ??
- Possible roms to port:
Right now would be nice to see a OEM rom, such a touchwiz or Sense
Work in Progress
N/A available
(awaiting sugestions
So, what do you guys think? ? Any users with good porting skills ? I know we have good developers! Ideas? Sugestions?
Write away
A few guides from XDA - They may not be all you need to get the job done, but a LOT of important information is written here. Don't forget to thanks their authors
Guides / Tutorials
How to Port Roms by @saywhatt
How to Port Manufacturer Rom. by @GalaxyUser
How to port Stock/GB/CM7/CM9/ICS/CM10/JB Based ROMs by @Peteragent5
PS - Every work that is possible to port and if someone decides to invest time in it, it needs explicit authors permission.
Sure if a few people want a particular rom i can bring it to our device, but i would much prefer helping first time rom builders do this own their own then they can maintain it also
JoinTheRealms said:
Sure if a few people want a particular rom i can bring it to our device, but i would much prefer helping first time rom builders do this own their own then they can maintain it also
Click to expand...
Click to collapse
Well, I though about some sort of "voting" to bring a "specific" rom.
Personally, I'd love to have Sense on our device. I had two HTC's before and I miss that Sense interface :b
But far as I'm aware, isn't an easy thing to port.
About your offer, this thread stands mostly with learning. The idea is everyone being able to contribute and more users start bringing roms as their first times. So, thank you so much for lending your help and know how, I'm sure we'll have a fine list of possible ports and then we can talk about how to port them over
Everyone can ask for help and the idea is to everyone who is able to - help.
I like the idea of this thread, but what would also be quite usefull is a list of available ROMs and their maintainer(s).
Also the list should include ROMs someone is working on ATM, so it cannot happpen that 2 devs are working on the same ROM
However, your idea is good, but porting a ROM not from sorce is quite hard, and might need some smali "hacking" in order to resolve bugs.
But well, we're a community, and I guess we can help each other if needed, right
laufersteppenwolf said:
I like the idea of this thread, but what would also be quite usefull is a list of available ROMs and their maintainer(s).
Also the list should include ROMs someone is working on ATM, so it cannot happpen that 2 devs are working on the same ROM
However, your idea is good, but porting a ROM not from sorce is quite hard, and might need some smali "hacking" in order to resolve bugs.
But well, we're a community, and I guess we can help each other if needed, right
Click to expand...
Click to collapse
That's correct! :good:
The main point is to learn helping each other who knows in a month or so, today's whiners are tomorrow's contributors
Jokes aside, the first post will be edited in order to structure and add information.
I'm gonna start with compatible devices (the ones that allow porting in a easy way). Ideas? Besides the HTC One X ? I'm guessing the grouper (N7 2012) besides having the same soc, doesn't have the same screen...
PS - (this would be better with an experienced porter) - Maybe we could start with a easy one, and go on from there
I know we have "how to port" threads all around xda ,but each port is different so we can't use "one hat to fit them all" ... or a ring to rule them all, so we should treat each port differently.
However.. I'm gonna put some xda links about porting to bring some light into the matter for who is "new" on this subject... or for whom's feeling adventurous and can't wait to have "their" rom on "our" device
Oh yes finally, have been waiting for a thread like this for a long time me as well would love to see a sense rom on this phone
cm/aosp roms are not that hard to port most of the time u only need the same screen resolution for it to work. (ported a nexus s touchwiz rom over to my old lg optimus 2x) but would have loved to see some oem roms ported over as well, even though it would be a lot harder to port over. but as a wonderful community as this is we might be able to pull it off
MidnightDevil said:
That's correct! :good:
The main point is to learn helping each other who knows in a month or so, today's whiners are tomorrow's contributors
Jokes aside, the first post will be edited in order to structure and add information.
I'm gonna start with compatible devices (the ones that allow porting in a easy way). Ideas? Besides the HTC One X ? I'm guessing the grouper (N7 2012) besides having the same soc, doesn't have the same screen...
PS - (this would be better with an experienced porter) - Maybe we could start with a easy one, and go on from there
I know we have "how to port" threads all around xda ,but each port is different so we can't use "one hat to fit them all" ... or a ring to rule them all, so we should treat each port differently.
However.. I'm gonna put some xda links about porting to bring some light into the matter for who is "new" on this subject... or for whom's feeling adventurous and can't wait to have "their" rom on "our" device
Click to expand...
Click to collapse
You can add the HOX+ to the list as well
About porting, you need to seperate it in two halfs, porting from source, and "winzipping". TBH, I'm no fas of winzipping at all, but some stuff (like sense or TW) can only be winzipped...
BTW, if you need a 2nd/3rd post, just let me know
Personally, I'd like to see a GFlex or even better, a G2 (/mini) ROM for our phone (KitKat, of course )
This thread has potential
I'm new to this forum,so i dont know whats going on about roms,i see there are few devs working full time.
I think this is the best way to go: Port ALL open source roms,such as we have already,but we need them all.
Second,make a badass kernel,with all features and customizations,possibly 3.4.
Third,and just a suggestion,Make a community ROM?
I really like this thread,and i even more like this OX4 community,you all get along,and i've missed that,i was on a forum that has no frendly people whatsoever.
And,about the roms,the idea is awesome,but i always think of the clash of clans rule,max everything out before going on a higher level.
Sent from my LG-P880 using XDA Premium 4 mobile app
Regarding stock roms, it's an interesting thing, but I'm guessing stock roms are more trouble to port comparing to AOSP or CM.
I remember on the HTC Sensation forums the headaches sense brought to many developers and porters, the bunch of files that needed to be edited, kernel changes (aosp kernel is different from stock / sense kernel in that case).. so Stock roms are maybe harder to port fully.
Right now we have some apks from the G2 (lock screen, messaging, etc..), maybe someone will port some things from the Flex, but the whole base.. hum
@DeHuMaNiZeD , thanks for your reply
The other roms based of AOSP and CM, in my opinion, unless they're different (modded, themed, customized - etc..) but if not, if they are "clean" roms with no changes, then - we have them already I believe you'll agree. (Unless the idea is to test something).
A 3.4 kernel would be something, but perhaps a developer can shed some light here - what benefits would we have from a 3.4 kernel ?
A community rom is indeed long due. This thread is a different subject because it's about *several* roms, ports and tutorials, maybe you would like to create a thread here on General about that? You can start with votes (i believe it's a proper way to do it) with which base should we use (Cm, AOSP, Stock, etc..), included apps (or not), possibly aroma maybe and so on
DeHuMaNiZeD said:
This thread has potential
I'm new to this forum,so i dont know whats going on about roms,i see there are few devs working full time.
I think this is the best way to go: Port ALL open source roms,such as we have already,but we need them all.
Second,make a badass kernel,with all features and customizations,possibly 3.4.
Third,and just a suggestion,Make a community ROM?
I really like this thread,and i even more like this OX4 community,you all get along,and i've missed that,i was on a forum that has no frendly people whatsoever.
And,about the roms,the idea is awesome,but i always think of the clash of clans rule,max everything out before going on a higher level.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, this sounds quite good, but the real problem is: this is a hell lot of work. Also, it needs resources. The sourcecode of a ROM is ~25-30GB. When it's compiled it's about double the size, and takes my PC (8 cores @ 4GHz) about 75Min to compile. Not to mention the time 'til the sources are Downloaded. My 500GB HDD is near to its limit very soon, so sooner or later I will need a new HDD, then I might be able to get another ROM ported, but right now, hard...
Also, why do you need a 3.4 kernel?
MidnightDevil said:
Regarding stock roms, it's an interesting thing, but I'm guessing stock roms are more trouble to port comparing to AOSP or CM.
I remember on the HTC Sensation forums the headaches sense brought to many developers and porters, the bunch of files that needed to be edited, kernel changes (aosp kernel is different from stock / sense kernel in that case).. so Stock roms are maybe harder to port fully.
Right now we have some apks from the G2 (lock screen, messaging, etc..), maybe someone will port some things from the Flex, but the whole base.. hum
@DeHuMaNiZeD , thanks for your reply
The other roms based of AOSP and CM, in my opinion, unless they're different (modded, themed, customized - etc..) but if not, if they are "clean" roms with no changes, then - we have them already I believe you'll agree. (Unless the idea is to test something).
A 3.4 kernel would be something, but perhaps a developer can shed some light here - what benefits would we have from a 3.4 kernel ?
A community rom is indeed long due. This thread is a different subject because it's about *several* roms, ports and tutorials, maybe you would like to create a thread here on General about that? You can start with votes (i believe it's a proper way to do it) with which base should we use (Cm, AOSP, Stock, etc..), included apps (or not), possibly aroma maybe and so on
Click to expand...
Click to collapse
For stock ROMs to work, it's your best bet to use AOSP as your base, and then look for what's missing/broken. This, however, means you need an AOSP base first to work with. And AOSP is not always the easiest thing to get properly running.
About the benefits of an 3.4 kernel: None IMO. All you get is a higher version-number, and that's it. We actually already have some 3.4 features backported, and also tweaked the 3.1 kernel quite a lot. So the actual benefits are all in your head (well, except you count bugs as benefits )
Community ROM? Meh, what for? We have so many ROMs already, so everyone should find the one that suits him/her best
BTW: Thread stuck
laufersteppenwolf said:
Well, this sounds quite good, but the real problem is: this is a hell lot of work. Also, it needs resources. The sourcecode of a ROM is ~25-30GB. When it's compiled it's about double the size, and takes my PC (8 cores @ 4GHz) about 75Min to compile. Not to mention the time 'til the sources are Downloaded. My 500GB HDD is near to its limit very soon, so sooner or later I will need a new HDD, then I might be able to get another ROM ported, but right now, hard...
Also, why do you need a 3.4 kernel?
For stock ROMs to work, it's your best bet to use AOSP as your base, and then look for what's missing/broken. This, however, means you need an AOSP base first to work with. And AOSP is not always the easiest thing to get properly running.
About the benefits of an 3.4 kernel: None IMO. All you get is a higher version-number, and that's it. We actually already have some 3.4 features backported, and also tweaked the 3.1 kernel quite a lot. So the actual benefits are all in your head (well, except you count bugs as benefits )
Community ROM? Meh, what for? We have so many ROMs already, so everyone should find the one that suits him/her best
BTW: Thread stuck
Click to expand...
Click to collapse
Why dont you set up that build server,i think they're cheap atm,or someone could borrow you? It would take a lot less time and effort. that's why i think offical rom support is important,once it's merged to the build bot,its their responsibility.
Sent from my LG-P880 using XDA Premium 4 mobile app
DeHuMaNiZeD said:
Why dont you set up that build server,i think they're cheap atm,or someone could borrow you? It would take a lot less time and effort. that's why i think offical rom support is important,once it's merged to the build bot,its their responsibility.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's not as easy as you might think
I do have access to a buildserver, however I only have 100GB as it's a shared one, so this is genious for official builds, or quick tests/ports. But it isn't ideal for the long terms.
Also, having it official doesn't mean you're done you need to update it, and also fix it when it's broken. 'cause when it's broken, it can mess up the whole build process of the buildbot
But in general, you're right, having it official does help a lot
{fd}ware said:
Does anyone of you have a link to the latest CM10.2 (Android 4.3) for our device?
It seems like it's not anymore on get.cm and I wanted to start porting a TouchWiz (Note 3) ROM to our phone when I have free time
Click to expand...
Click to collapse
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
MidnightDevil said:
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
Click to expand...
Click to collapse
LOL, no, I do not, but gimme a few hours and I'll have one
Syncing right now
laufersteppenwolf said:
LOL, no, I do not, but gimme a few hours and I'll have one
Syncing right now
Click to expand...
Click to collapse
Thank you
{fd}ware said:
BTW, did anyone tried to port a ROM this way? http://forum.xda-developers.com/showthread.php?t=2245786
Click to expand...
Click to collapse
Nope, I actually never "winzipped" a ROM
Lot of things to comment on here. Very good initiative I have to admit. I'm sure I'll have more ideas as the discussion evolves.
Similar hardware: You can add HOX+ as laufer said. Very minor differences are there only.
What I would personally prefer is TouchWiz, at least Nature UX 2.0, but new S5 UI is also really awesome. I liked Sense till 4.5, but 5.0+ versions are now out of my 'inner circles'. Especially what I don't like is the UI.
Few suggestions:
FlymeOS (from Meizu MX) - I got 2.0 booting last summer, but had touchkey issues (they were freezing the device lol) and never released it. Nobody ever booted 2.0+ on other Android devices yet.
Porting LG roms might be the best start, I think porting full Optimus G system wouldn't be that hard. Just a pain in the *ss merging process.
What we mainly need is same screen size (unless you wanna resizing 100+ apps ). Similar SoC is a good extra, but that's very limited. Also, it's better to avoid Qualcomm SoCs to port from, it's extremely hard, there are a lot of code changes in low-level code which just make the device get into deep segfault cycles. :cyclops: Even Exynos is easier to port from, trust me. I got SGS3 leaked 4.2 booting on the O4X last autumn.
Big issue we have to note: In 4.2, Google radically changed graphics libraries code. We have old, 4.1.2 blobs and those need hacks in libgui.so and libsurfaceflinger.so to function properly (in 4.4+ libEGL.so, libGLES_v1_CM.so and libGLES_v2.so also need a change). Here comes the problem: Manufacturers do change these libraries, mainly adding Wi-Fi display and HDMI support code which other blobs rely on. Of course we can't just replace these libs, graphics wouldn't function that way. Either we have to guess those function signatures and reimplement some stub in the code, or use new blobs, i.e. what I did in Omni. But y'all now those are not perfect _yet_.
Regarding newer kernels: If, I emphasize, IF it's properly ported, it would cause a noticeable effect on overall performance, battery life, etc. What do I mean by proper porting: All machine-specific code must be updated to Nvidia/Google upstream, no excuses! I don't say anything for sure, I didn't check it much, but kholk didn't do this merge. His kernel still uses 3.1 files with slight modifications to be 3.4-compatible. What I mean would be a very long and painful process, but would surely benefit after all. 3.4 has no Android branch, mainline Nvidia Tegra kernel does only have Linux support, it might be even harder. 3.10 is maintained by Google for Android, issues I have found so far: No graphics driver support for T2 and T3, have to forward-port it and I didn't find core Android components like wakelocks, earlysuspend, etc. Weird.
A little related story: I initially started working on MultiROM so I can test and port different roms while I can keep a stable rom for myself and there'd be no need for reflash then. That's what I can suggest. Use MultiROM, it has so many capabilities! Maybe it's better with kernel sharing so you don't have to wait for hardboot on every reboot (which one needs a lot if porting). @MidnightDevil you could add this to the OP maybe.
MidnightDevil said:
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
Click to expand...
Click to collapse
Here you are! Compiled this because wanted to start porting from Note 2, but finally worked on Omni more and abandoned it.
{fd}ware said:
BTW, did anyone tried to port a ROM this way? http://forum.xda-developers.com/showthread.php?t=2245786
Click to expand...
Click to collapse
That's way too generic unfortunately.
Quick suggestion for you port: Use Note 2 base with Note 3 features. Note 2 has the same resolution and you won't need to resize.
Adam77Root said:
Lot of things to comment on here. Very good initiative I have to admit. I'm sure I'll have more ideas as the discussion evolves.
Similar hardware: You can add HOX+ as laufer said. Very minor differences are there only.
What I would personally prefer is TouchWiz, at least Nature UX 2.0, but new S5 UI is also really awesome. I liked Sense till 4.5, but 5.0+ versions are now out of my 'inner circles'. Especially what I don't like is the UI.
Few suggestions:
FlymeOS (from Meizu MX) - I got 2.0 booting last summer, but had touchkey issues (they were freezing the device lol) and never released it. Nobody ever booted 2.0+ on other Android devices yet.
Porting LG roms might be the best start, I think porting full Optimus G system wouldn't be that hard. Just a pain in the *ss merging process.
What we mainly need is same screen size (unless you wanna resizing 100+ apps ). Similar SoC is a good extra, but that's very limited. Also, it's better to avoid Qualcomm SoCs to port from, it's extremely hard, there are a lot of code changes in low-level code which just make the device get into deep segfault cycles. :cyclops: Even Exynos is easier to port from, trust me. I got SGS3 leaked 4.2 booting on the O4X last autumn.
Big issue we have to note: In 4.2, Google radically changed graphics libraries code. We have old, 4.1.2 blobs and those need hacks in libgui.so and libsurfaceflinger.so to function properly (in 4.4+ libEGL.so, libGLES_v1_CM.so and libGLES_v2.so also need a change). Here comes the problem: Manufacturers do change these libraries, mainly adding Wi-Fi display and HDMI support code which other blobs rely on. Of course we can't just replace these libs, graphics wouldn't function that way. Either we have to guess those function signatures and reimplement some stub in the code, or use new blobs, i.e. what I did in Omni. But y'all now those are not perfect _yet_.
Regarding newer kernels: If, I emphasize, IF it's properly ported, it would cause a noticeable effect on overall performance, battery life, etc. What do I mean by proper porting: All machine-specific code must be updated to Nvidia/Google upstream, no excuses! I don't say anything for sure, I didn't check it much, but kholk didn't do this merge. His kernel still uses 3.1 files with slight modifications to be 3.4-compatible. What I mean would be a very long and painful process, but would surely benefit after all. 3.4 has no Android branch, mainline Nvidia Tegra kernel does only have Linux support, it might be even harder. 3.10 is maintained by Google for Android, issues I have found so far: No graphics driver support for T2 and T3, have to forward-port it and I didn't find core Android components like wakelocks, earlysuspend, etc. Weird.
A little related story: I initially started working on MultiROM so I can test and port different roms while I can keep a stable rom for myself and there'd be no need for reflash then. That's what I can suggest. Use MultiROM, it has so many capabilities! Maybe it's better with kernel sharing so you don't have to wait for hardboot on every reboot (which one needs a lot if porting). @MidnightDevil you could add this to the OP maybe.
Here you are! Compiled this because wanted to start porting from Note 2, but finally worked on Omni more and abandoned it.
That's way too generic unfortunately.
Quick suggestion for you port: Use Note 2 base with Note 3 features. Note 2 has the same resolution and you won't need to resize.
Click to expand...
Click to collapse
Dang, you've beaten me but mine's as fresh as it could be
HERE you guys go, for all who need the newest CM10.2
laufersteppenwolf said:
Dang, you've beaten me but mine's as fresh as it could be
HERE you guys go, for all who need the newest CM10.2
Click to expand...
Click to collapse
Just don't delete the sources, you might need them in the close future.
I think we should create a schedule about what to do. As you all know, good buildings all have good grounding. So let's get started from the very beginning I say. First fix remaining bugs in MultiROM, then create a unified kernel so users don't have to choose. Very likely this is not possible as people think different so just make all kernels hardboot compatible. After these we have a solid base for starting all the work. Of course this cannot be done if not everybody is involved. Both devs and users should share a part in this magnificent journey.
(High expectations, I know. )
Sent from my OmniROM-powered LG Optimus 4X HD
Since people say on every rom released with OpenKirin source codes that there are same bugs on every rom, I joined forces with some of my friends and in result=> KirinMixTeam Development, name's not fully decided, so it may change, but that's not important.
The important thing is that we already started working on a new P8 Lite source code: https://github.com/KirinMixTeam/device_huawei_hi6210sft/tree/AOKP-7.1.2 ,there are much more bugs to fix, I'm sure ril will not work on first hand, at least hopefully wifi works.
Our team goal is to develop for as much as we can, and now that I've finnaly repaired my computer I have 2TB of free space to develop on.
Reminder: Do not take our team as a rival to OpenKirin or haky86, or any other developers, we do not want to do that, take this as some good news that P8 Lite will get even more developers to work on its platform and others!
Also, since for now we're just 3 members in the team, maybe one of you want to get in. PM me or @AymenDe7 for further information, but if you think you are not ready for this please do not fill our inbox worthless.
P.S. Do not overhype already, wait until at least a bootable rom to be sure that our source code works. Tommorow I'm already testing first build of AOKP 7.1.2, so we'll keep you updated!
Thank you.:good:
Wow so P8Lite isn't dead
Nice news !!
I just want to get a stable rom that consists no bugs, and as stable as huawei's stock firmware. I've tried all of the custom roms and there are lots of annoying bugs such as,
slow and laggy interface,
poor app performance
720p 60fps playback issue
headset issue,
low download speeds on my mobile network etc. etc.
I've now converted back to stock and unrooted firmware, I will be waiting and checking for a %100 stable custom rom. good to see you're determined to make a good rom, good luck and thank you.
tayfuntb1393 said:
I just want to get a stable rom that consists no bugs, and as stable as huawei's stock firmware. I've tried all of the custom roms and there are lots of annoying bugs such as,
slow and laggy interface,
poor app performance
720p 60fps playback issue
headset issue,
low download speeds on my mobile network etc. etc.
I've now converted back to stock and unrooted firmware, I will be waiting and checking for a %100 stable custom rom. good to see you're determined to make a good rom, good luck and thank you.
Click to expand...
Click to collapse
Nor OpenKirin roms nor haky86's are slow, they get almost all of them 30K in antutu. Problem with 720p 60fps is related to codecs, but I don't know what causes the headset issue.
XTutorials said:
Since people say on every rom released with OpenKirin source codes that there are same bugs on every rom, I joined forces with some of my friends and in result=> KirinMixTeam Development, name's not fully decided, so it may change, but that's not important.
The important thing is that we already started working on a new P8 Lite source code: https://github.com/KirinMixTeam/device_huawei_hi6210sft/tree/AOKP-7.1.2 ,there are much more bugs to fix, I'm sure ril will not work on first hand, at least hopefully wifi works.
Our team goal is to develop for as much as we can, and now that I've finnaly repaired my computer I have 2TB of free space to develop on.
Reminder: Do not take our team as a rival to OpenKirin or haky86, or any other developers, we do not want to do that, take this as some good news that P8 Lite will get even more developers to work on its platform and others!
Also, since for now we're just 3 members in the team, maybe one of you want to get in. PM me or @AymenDe7 for further information, but if you think you are not ready for this please do not fill our inbox worthless.
P.S. Do not overhype already, wait until at least a bootable rom to be sure that our source code works. Tommorow I'm already testing first build of AOKP 7.1.2, so we'll keep you updated!
Thank you.:good:
Click to expand...
Click to collapse
Super!
If i can help in something, just ask!
PS: Maybe i can learn something from you guys!
:good:
.
persona78 said:
Super!
If i can help in something, just ask!
PS: Maybe i can learn something from you guys!
:good:
.
Click to expand...
Click to collapse
How you can help if you only work on stock rom Don't take it bad! or maybe I missing something
persona78 said:
Super!
If i can help in something, just ask!
PS: Maybe i can learn something from you guys!
:good:
.
Click to expand...
Click to collapse
Thank you! We'll count on you!
I, actually... want you in the team, please send me a PM, so we can talk more.
Thank you.
I would be interested to learn more about android. I'm not excepting you to hold my hand through android basics. But if there is anything i can do. Feel free to pm me. I have some kinda google skills
Good news, best wishes!! ✌
I learn how to upstream kernels, not helpful for you, but eh maybe i will question some things in the future.
Thank you so much for your support!
For your interest, but not interesting, I'm already compiling AOKP 7.1.2 for Nexus 6P. After that will get back to P8 Lite.
wait wait best ROMs kkk
Guys dont take me wrong if any of you are willing to try ROM building but cant do it due to various reasons like Computing power or HDD space or slow Internet speeds etc.., . Here is the best alternative even a small mobile is enough to build the ROM.
https://forum.xda-developers.com/chef-central/android/guide-how-to-build-rom-google-cloud-t3360430
I have compiled aokp 7.1.2 yesterday but it's stuck on boot logo and i don't know why
redknight65 said:
I have compiled aokp 7.1.2 yesterday but it's stuck on boot logo and i don't know why
Click to expand...
Click to collapse
For P8 Lite?
@XTutorials
I wish you luck but in my opinion you (and we as community) should focus on fixing bugs in OpenKrirn's source rather than making a new ROM from scratch
Actually on their nougat we just need video recording, 60fps videos (here emui 4.1 kernel and blobs can fix this I think), GPS and deepsleep to have a fully functional ROM (I don't count dual SIM).
HWC is unfortunately a different story...
That's the best option, we don't want other roms, we want fixes for current ones, like thst cpu fix... Maybe GPS, deepsleep, wifi fix etc
dominj97 said:
@XTutorials
I wish you luck but in my opinion you (and we as community) should focus on fixing bugs in OpenKrirn's source rather than making a new ROM from scratch
Actually on their nougat we just need video recording, 60fps videos (here emui 4.1 kernel and blobs can fix this I think), GPS and deepsleep to have a fully functional ROM (I don't count dual SIM).
HWC is unfortunately a different story...
Click to expand...
Click to collapse
Unfortunately, in my opinion I don't think is right to just continue OK source code and post it as yours.
How it is said, better do it slowly than doing it fast and bad.
I know you really want asap a fully-stable ROM, and we put a lot of effort in doing that. Expect a booting ROM in 1-2 weeks from now.
Thank you for understanding!
XTutorials said:
Unfortunately, in my opinion I don't think is right to just continue OK source code and post it as yours.
How it is said, better do it slowly than doing it fast and bad.
I know you really want asap a fully-stable ROM, and we put a lot of effort in doing that. Expect a booting ROM in 1-2 weeks from now.
Thank you for understanding!
Click to expand...
Click to collapse
I'm not talking about posting it as yours I'm talking about contributing to their project.
Pls don't get me wrong I know it's hard to develop on this phone (and we don't pay you for it) but you will probably also have problems with your project (maybe even the same as OpenKirin and XePeleato when there was no OpenKirin yet). What's the reason of doing the same job again?
dominj97 said:
I'm not talking about posting it as yours I'm talking about contributing to their project.
Pls don't get me wrong I know it's hard to develop on this phone (and we don't pay you for it) but you will probably also have problems with your project (maybe even the same as OpenKirin and XePeleato when there was no OpenKirin yet). What's the reason of doing the same job again?
Click to expand...
Click to collapse
Well, I'm working for the first time source codes ( working seriously, not just edit BoardConfig and other .mk's) and I need some practicing and learning, so first ROM will come out harder, if you let me practice and learn then I will fix bugs and build roms faster.
Thank you.
I don't mean to be that guy, but i was wondering if anyone was going to bring plain old lineage 15.1 to the Mix. I see all these new oreo roms, with both aosp and los bases, and while they are intriguing, I'd prefer to stick with the tried and true, the most well supported, and thus the most stable custom rom for android.
Ah... I haven't any right to be impatient. I appreciate the work thus far. Just a wish.
I moved away from Lineage since AICP is basically LOS + their extras, and frankly I was building it for myself to begin with. I assumed the AICP/LOS maintainers would already have put out Oreo builds by now. I always found AICP and RR (although it's mostly AOSP-based) to be every bit as stable as LOS, and any bugs they had would almost always be inherited from it. The only app that isn't working in AICP/RR that I'm aware of is the default Music app. There aren't any apps crashing or random reboots or anything else that you'd normally associate with beta ROMs (aside from the TWRP issues that some have reported).
It doesn't look like RR is going to have an official maintainer for the Mix so I might have that one for the foreseeable future. The AICP guy said that they will be bring Oreo builds soon. If/when they do I suppose I could swap AICP out for LOS, but juggling 3 ROMs is a bit much. Even if I built it, it'd almost certainly have the same TWRP issues with decryption/mounting data that my last AICP/RR builds had. Hopefully Hen Ry will migrate to Oreo ASAP.
msn100dc said:
I don't mean to be that guy, but i was wondering if anyone was going to bring plain old lineage 15.1 to the Mix. I see all these new oreo roms, with both aosp and los bases, and while they are intriguing, I'd prefer to stick with the tried and true, the most well supported, and thus the most stable custom rom for android.
Ah... I haven't any right to be impatient. I appreciate the work thus far. Just a wish.
Click to expand...
Click to collapse
I´ll build it for you tomorrow. stay tuned!!!
Didn't necessarily expect the outpouring, but it is appreciated. Ive heard alot about aicp, and its rock solid composition. In theory id like to switch, but i perhaps have an irrational attachment to LOS. Been running custom roms for 7 years now and I'm not long for much experimenting, though i should probably do a bit more.
Ha, no pressure at all, but it would be cool to see LOS 15.1 in official or unofficial capacity. Gavin especially, you've put in alot of work, so dont take it too seriously. Just voicing a thought. Thanks guys.
msn100dc said:
Didn't necessarily expect the outpouring, but it is appreciated. Ive heard alot about aicp, and its rock solid composition. In theory id like to switch, but i perhaps have an irrational attachment to LOS. Been running custom roms for 7 years now and I'm not long for much experimenting, though i should probably do a bit more.
Ha, no pressure at all, but it would be cool to see LOS 15.1 in official or unofficial capacity. Gavin especially, you've put in alot of work, so dont take it too seriously. Just voicing a thought. Thanks guys.
Click to expand...
Click to collapse
Here you have ( as im new user I don't have rights to make a thread so if someone wants to make a post with my build , please feel free to do it. As I promised here you have your build made with love!!!!
https://mega.nz/#!hDYCwBAb!mJRa6jySLzuStzSXaGDdkKZIa62pRhIJkm2u1M6oNVE
ArwenArtful said:
Here you have ( as im new user I don't have rights to make a thread so if someone wants to make a post with my build , please feel free to do it. As I promised here you have your build made with love!!!!
https://mega.nz/#!hDYCwBAb!mJRa6jySLzuStzSXaGDdkKZIa62pRhIJkm2u1M6oNVE
Click to expand...
Click to collapse
Thanks bro!
I don't have time to test tonight, but I'll let you know how things turn out tomorrow. Perhaps someone else can chime in before that too.
Also, you may want to consider opening an unofficial thread for 15.1 in the development section if all is well. I can't be the only holdout for LOS 15.
Once again, thank you
Haha... Ha...
Tried it, works like a charm.
HOWEVER, the twrp issue, encryption, 0mb data even though the settings in 15.1 state that the rom is not encrypted, that's been plaguing all oreo roms reared its ugly head. Typing this on my trusty oneplus one because i utterly botched my mix. Whew. I know better. Still, it hurts.
Until the twrp and encryption issues are figured out, i think this'll be a major stumbling block. Even so,thank you for your work.
Man am i dumb...
msn100dc said:
Haha... Ha...
Tried it, works like a charm.
HOWEVER, the twrp issue, encryption, 0mb data even though the settings in 15.1 state that the rom is not encrypted, that's been plaguing all oreo roms reared its ugly head. Typing this on my trusty oneplus one because i utterly botched my mix. Whew. I know better. Still, it hurts.
Until the twrp and encryption issues are figured out, i think this'll be a major stumbling block. Even so,thank you for your work.
Man am i dumb...
Click to expand...
Click to collapse
Hey, the question is; proximity working as it supposed to be?
Konstantine34 said:
Hey, the question is the proximity working as it supposed to be?
Click to expand...
Click to collapse
Im about to ask the same thing lol
---------- Post added at 03:51 PM ---------- Previous post was at 03:48 PM ----------
msn100dc said:
Haha... Ha...
Tried it, works like a charm.
HOWEVER, the twrp issue, encryption, 0mb data even though the settings in 15.1 state that the rom is not encrypted, that's been plaguing all oreo roms reared its ugly head. Typing this on my trusty oneplus one because i utterly botched my mix. Whew. I know better. Still, it hurts.
Until the twrp and encryption issues are figured out, i think this'll be a major stumbling block. Even so,thank you for your work.
Man am i dumb...
Click to expand...
Click to collapse
Re: twrp issue, what version are you using ? Same problem with RR oreo? Is proximity working on this rom?
Sorry, didn't test long enough to find out. Chickened out at the first sign of trouble. I really cant have my phone down for too long.
As for the twrp, its an older version, smarty twrp based on 3.0.2.? I believe it is the only other version of twrp beyond raines that doesn't have the touch screen issues if not matched perfectly with the rom. It flashed oreo, but it wouldn't mount any partitions after flashing oreo. Had to format everything. Should've anticipated that, but id been drinking.
Oh well.
From whay ive seen, i have no reason and had no expectation of proximity working here,as this is the base for other roms with non-working proximity. Those that have downtime to spare can confirm.
msn100dc said:
Sorry, didn't test long enough to find out. Chickened out at the first sign of trouble. I really cant have my phone down for too long.
As for the twrp, its an older version, smarty twrp based on 3.0.2.? I believe it is the only other version of twrp beyond raines that doesn't have the touch screen issues if not matched perfectly with the rom. It flashed oreo, but it wouldn't mount any partitions after flashing oreo. Had to format everything. Should've anticipated that, but id been drinking.
Oh well.
From whay ive seen, i have no reason and had no expectation of proximity working here,as this is the base for other roms with non-working proximity. Those that have downtime to spare can confirm.
Click to expand...
Click to collapse
The MultiROM and raupe builds are both newer and have working touch. I've been using this one for ~6 months (unencrypted) and never had any issue with the Oreo ROMS (PE/RR/AICP and Cardinal).
The proximity mention was because they stated that they had fixed the issue.
msn100dc said:
Sorry, didn't test long enough to find out. Chickened out at the first sign of trouble. I really cant have my phone down for too long.
As for the twrp, its an older version, smarty twrp based on 3.0.2.? I believe it is the only other version of twrp beyond raines that doesn't have the touch screen issues if not matched perfectly with the rom. It flashed oreo, but it wouldn't mount any partitions after flashing oreo. Had to format everything. Should've anticipated that, but id been drinking.
Oh well.
From whay ive seen, i have no reason and had no expectation of proximity working here,as this is the base for other roms with non-working proximity. Those that have downtime to spare can confirm.
Click to expand...
Click to collapse
Cheers man..next time dont drink and flash roms lol..kidding aside..well i asked about proximity since the dev mentioned that he found the solution to the proximity issue on other oreo roms....
What good is it if everyone creates a ROM and they all have the same sources?
I have already created a LOS build, but no proxi and partition is
"Encrypted".
Hen Ry said:
What good is it if everyone creates a ROM and they all have the same sources?
I have already created a LOS build, but no proxi and partiotion is
"Encrypted".
Click to expand...
Click to collapse
Well if built from same sources possible no difference at all..anyway, may i know if what twrp you are using? Thanks hen ry and eagerly waiting for your official oreo los based rom.
I know im not a pro dev , im starting to it but hey...we all have started from zero so..ill try my best to keep Mi Mix updated (the proximity sensor fix is not mine , the user that fixed it don't want to share with me so sorry for that) , as I don't know which sources are the best I just use the ones that the other devs used .
Hen Ry said:
What good is it if everyone creates a ROM and they all have the same sources?
I have already created a LOS build, but no proxi and partition is
"Encrypted".
Click to expand...
Click to collapse
The average user doesn't care or know about sources. Sure, PE/Cardinal and AICP/RR could be twins, but more choice is better than less.
The whole reason that myself and albertoduqe started building Oreo ROMs is because no one else was doing it. Sure, some of them might be very similar, but to the end users most ROMs are 95% identical anyway. All it takes is for one ROM to have some minor config option or theme or whatever and that's enough to make someone choose it over the next one that's 99% the same under the hood. Also, if one or two of us move on to another device, like papps did, then there will still be one or two around to keep putting builds out.
Correct me if I'm wrong, but aren't almost all ROMs out there based on either LOS or AOSP anyway?
ArwenArtful said:
I know im not a pro dev , im starting to it but hey...we all have started from zero so..ill try my best to keep Mi Mix updated (the proximity sensor fix is not mine , the user that fixed it don't want to share with me so sorry for that) , as I don't know which sources are the best I just use the ones that the other devs used .
Click to expand...
Click to collapse
Just LoL. No other words.
Don't drink and flash, truer words never been spoken.
On the TWRP, I was aware when i was forced to reformat, but i didn't want to go down that rabbit hole again,not in that condition. Now that its down and im sane again, i suppose i could really mess with it. Ive reached the acceptance phase of loss.
Ill try those newer versions of twrp when i have some time, its a bridge ive needed ti cross, now more than ever.
gavin19 said:
The average user doesn't care or know about sources. Sure, PE/Cardinal and AICP/RR could be twins, but more choice is better than less.
The whole reason that myself and albertoduqe started building Oreo ROMs is because no one else was doing it. Sure, some of them might be very similar, but to the end users most ROMs are 95% identical anyway. All it takes is for one ROM to have some minor config option or theme or whatever and that's enough to make someone choose it over the next one that's 99% the same under the hood. Also, if one or two of us move on to another device, like papps did, then there will still be one or two around to keep putting builds out.
Correct me if I'm wrong, but aren't almost all ROMs out there based on either LOS or AOSP anyway?
Click to expand...
Click to collapse
100% Agree to your point Gavin. Being a flashaholic user, the more ROM to try the merrier.!!! Its regardless of the sources. To devs who are devoting their time trying to build a new ROM i salute you all. You all know who you are. We are all glad that you keep the flame burning for Mi Mix! Keep it up Devs.....
The major issue I ran into when flashing the build posted here is that I cannot flash magisk. An issue with mounting the vendor partion arises in that part of the workflow, ending in Error 1.
Beyond that, the temporary solution to the 0mb issue is to reformat your data to f2fs in recovery, specifically the one Gavin posted here. I no longer have any issues after first boot. A little more on my experience here. But this confirms it working on two oreo roms for me now, and I expect the rest will run too.
In my expanded testing, I couldn't get proximity to work..., but everything else ran fine for the most part. Ill have to wait until the vendor partition mounting works to continue on as root is a requirement for me, and magisk is the best supported at this time.
Who is with me? I am committing to donating as long as the ROM is a proper port/build and is stable and reliable enough to be a daily driver.
Let's see who else can commit to donate!
Can't stand MIUI!!!!
tdot.loco said:
Who is with me? I am committing to donating as long as the ROM is a proper port/build and is stable and reliable enough to be a daily driver.
Let's see who else can commit to donate!
Can't stand MIUI!!!!
Click to expand...
Click to collapse
this is not how it works... devs on xda are no professionnals, they build roms on their spare time, after school or work hours.
The main problem is not to build any rom, but is to make sure it is usable and stable.
Patience is a vertue
Forgive me, but I don't understand why people are waiting for custom ROMs to show up when a GSI is working perfectly fine (in a better state than the current build of LOS)
OP, what is stopping you from using a GSI. You can continue to use the vendor image from your stock MIUI build while swapping out top-level GSIs
hmm for me i cannot use GSI roms. it says 'wrong pin' whenever i set pin/pattern.
tdot.loco said:
Who is with me? I am committing to donating as long as the ROM is a proper port/build and is stable and reliable enough to be a daily driver.
Let's see who else can commit to donate!
Can't stand MIUI!!!!
Click to expand...
Click to collapse
xD i wont take 10$ but i can build PE
letsmakecakes said:
xD i wont take 10$ but i can build PE
Click to expand...
Click to collapse
$10 is actually nothing in comparison to the hard work that is required to build any ROM whatsoever, and that's why we must be grateful to have you building lOS for us for FREE!
i will pay $100
Guys I have tremendous respect for all devs, of any device. I've owned myself from LG G2, G3, G4, Samsung S2, HTC M7 all the way to Samsung Note 8. I appreciate it all the hard work they put in. The reason why I took the initiative to incentive the very few ones that are following/owning our devices right now is because of that very same reason, there is little attention to this device.
I know most of them do this because it's a hobby or a side thing or to get some exposure/experience, but I know money is not the greatest motivator to them at all.
satadi said:
Forgive me, but I don't understand why people are waiting for custom ROMs to show up when a GSI is working perfectly fine (in a better state than the current build of LOS)
OP, what is stopping you from using a GSI. You can continue to use the vendor image from your stock MIUI build while swapping out top-level GSIs
Click to expand...
Click to collapse
I heard someone say there is still lots of bugs with LOS GSI on our device.
Can you confirm it is bug free on RN7 China version?
Still waiting for this
Pixie dust is out for treble.
Load it that way.
Edit:
https://forum.xda-developers.com/pr...evice-development/9-0-pixel-dust-pie-t3862484
Lots of other GSI images as well!
I am waiting three hundred hours to unlock bootloader, or I would give you more specific instructions.
Basically flash GSI image to your system partition, threads will include more information .
Hi OP, no offense, but offering $10 for personal rom request like this really cheapen out the dev's work. Porting a custom ROM isn't an easy work, and offering them this small amount of money is offensive.
Either wait until someone ported PE then donate to the dev, or join some lavender development group on telegram and throw some hundred bucks until someone's agreed to built you a rom.
why don't you want to use the pe already built for our device? this rom has been around for months yet you lot all appear to have never seen the thread.
https://forum.xda-developers.com/redmi-note-7/development/rom-pixel-experience-t3930709
official status means absolutely *nothing*. if it works, it works. official status doesn't automagically make it 100% stable either.
NightRaven49 said:
why don't you want to use the pe already built for our device?
https://forum.xda-developers.com/redmi-note-7/development/rom-pixel-experience-t3930709
Click to expand...
Click to collapse
Was about to make the same observation, I have just installed this Rom on my note 7 and seems to be bug free so far and even with small differences works just as well as the excellent Pixel expierence by jhenrique09 on my note 5. Give it a go!!
eh my bad, just realised this thread was started a couple of weeks before the initial pe rom thread was started. doesn't really seem to get much updates though.