Related
Hi folks. Sorry to start a new thread but there's something bugging me around here. If by any chance you mods think this post is useless please close it and accept my apologies.
It's known to the most of you that the first version of drivers didn't worked on all roms. That issue forced the developers to do a workaround and slow down the process to get it working on those roms and created a new set of drivers that is not so fast as the first one.
So... i was thinking on this and decided to start a poll in order to give a hand to the developers in wich way they should follow. What do you prefer?
A Gold XDA based ROM with fastest drivers and less compatibility with all roms? (forcing all XDA members to flash their phones - not a big deal i presume)
Or a set of drivers compatible with most of the roms but with slower performance?
I know this is a controversial issue and the urge of the drivers working on our kaisers is huge but i think we would have more if we had a custom GOLD XDA rom
Just My 2 cents
Cheers,
Draco
kinda seems like a no-brainer honestly (unless you're petrified to flash or just despise 6.1). They will develop said drivers and you have a million chefs making a million roms from them...
Fared said:
kinda seems like a no-brainer honestly (unless you're petrified to flash or just despise 6.1). They will develop said drivers and you have a million chefs making a million roms from them...
Click to expand...
Click to collapse
I have no problems at all flashing my phone. I assume that there are some people who are not comfortable doing that but.... this is XDA. And if they are here that's because we all want to get the most out of our phones. And that is the tricky part of this poll. Developing the drivers based on one specific rom ( a ported one form Diamond or Raphael or an official kaiser one ) will be the more accurate and fastest way to get there.
Again... just my 2 cents
Draco
first:
flashing rom is a non-trivial task for a huge majority of users. leaving them out in the cold sounds like a very selfish position. If not for this reason, maybe avoiding a flood of "I bricked my tilt, help !!!!" threads may be a better one.
second:
Anyway, as i understood it what is slowing down FPS in the new version is the enabled VSync, which yields less tearing and improved smoothness (sounds like a shaver commercial, i'm afraid). I don't know what the refresh rate of a kaiser LCD is, but anything higher than 75fps (ie 15ms refresh rate) is a complete waste.
draxredd said:
second:
flashing rom is a non-trivial task for a huge majority of users. leaving them out in the cold sounds like a very selfish position.
Click to expand...
Click to collapse
Not at all draxredd. Although i'm a junior member this is the second time i'm on XDA. I'm here for almost 7 years. Believe me, this is not a selfish position. As i was able to get some help to start flashing all of the members here on XDA will get that help too. The first time i flashed my first phone i was scared to death but... it's all the same. It only hurts the first time.
As i stated before this is just my opinion. The more roms the developers must include in the drivers development process, the more difficult it will be and much more time will be wasted.
Draco
haste... makes waste.
And if only one rom was to be designated as a target for the driver, it has to be the official HTC one, for two reasons:
- enabling driver support for a huge majority of users
- sticking it to HTC, deep.
draxredd said:
And if only one rom was to be designated as a target for the driver, it has to be the official HTC one, for two reasons:
- enabling driver support for a huge majority of users
- sticking it to HTC, deep.
Click to expand...
Click to collapse
What about performance issues? Doesn't that count as well?
Anyway.... i've started the poll just to check your opinion against wide compatibility among all the roms versus one specific rom fully optimized. Let's not get far from the main question
By the way... my kaiser has the official 6.1 rom from HTC... for now
cheers,
Draco
I'm for Flashing myself, but the in the ideal world both sollutions would be best so no one comes off short. However the kind developers should be aiming at the most stable of the 2 first.
Looking at the driver progress it looks like theyre slowly getting there and getting the driver to work on the latest 6.1 roms
I voted for compatibility with the official ROM, simply because it's an identifiable standard that everyone recognises, and which everyone has on their phone by default. Cooked ROMs are great, but they're all individual, designed by individuals and used by individuals with the same tastes/needs - not one of them will suit everyone else, with or without drivers, whereas drivers released for the official ROM should work with pretty much everything else.
It's too early to say whether drivers developed for the standard ROM will always be slower than those for a cooked version, and I'm sure the very brilliant developer of those drivers will do their best to minimise any performance loss, assuming their is any in the longterm.
Vastly improved performance for the majority (and what that means for sales of the Touch Pro etc) has to take priority over a marginally improved performance in a niche ROM, aimed at an elite few, surely? At the end of the day it's entirely down to the developer what they do, irrespective of any poll here, but that's my take on it anyway.
Maybe i didn't expose correctly my idea.
There isn't any XDA Gold rom nor any kind of perfect ROM. The XDA Gold rom is just a concept and the first name that crossed my mind.
This is a big community and has some big brains around here. The exchange of knowledge bettween everyone is a plus and that opens a big wide world to explore.
So.... let's just imagine this scenario, ok?
The developers will pick a base rom. It really doesn't matter if it is a ported rom or a Official one. Preferably one that is fast and stable enough. The driver will be written over that rom. Users (those who want obviously) will test the rom for bugs and then chefs will try to cook out a 100% clean (note that by clean i mean a rom just as close as an official rom regarding to apps) fast and stable rom.
Of course this is just a crazy ideia but that i was thinking of. Create the first genuine XDA rom based on one device.
Note that there are many roms out there based on diferent releases. Make the drivers compatible with all of them will make the development process slow down and eventualy fail. That's the main reason i started this thread.
Now that the concept of the "XDA Gold rom" was properly explained (i hope) let's get on with the poll.
Draco
DracoLX said:
Now that the concept of the "XDA Gold rom" was properly explained (i hope) let's get on with the poll.
Click to expand...
Click to collapse
As long as "XDA Gold" = HTC Latest Official version I cant see a problem. It's when drivers are developed for anything other than the official ROM that we'll encounter problems. All the chefs can base their designs starting with official ROMs and work out from there. In the end it will depend on whether those developing the drivers want to satisfy the larger number using official ROMs or those using Custom ROMs where the chef has not saught to maintain driver compatibility. I've therefore not voted because it depends whether "XDA Gold" does in fact = HTC Latest Official version - we weren't told.
Are you even sure that theifference is that huge?
They might be able to provide two sets to cover all ends without much additional work.
DracoLX said:
Note that there are many roms out there based on diferent releases. Make the drivers compatible with all of them will make the development process slow down and eventualy fail. That's the main reason i started this thread.
Now that the concept of the "XDA Gold rom" was properly explained (i hope) let's get on with the poll.
Draco
Click to expand...
Click to collapse
IMO, The drivers only need to be compatible with an official based rom. It's up to the chefs to make the drivers work with their rom. Now, if the root of the compatibility issue can be resolved, I think things can progress forward at a faster rate.
DracoLX said:
It's known to the most of you that the first version of drivers didn't worked on all roms. That issue forced the developers to do a workaround and slow down the process to get it working on those roms and created a new set of drivers that is not so fast as the first one.
Click to expand...
Click to collapse
FALSE. Two separate issues.
First, is dlls load differently between stock or hacked/cooked roms due to memory mangling by G'realoc going into cooked roms. An attempt to fix that was in the updated release.
Two, the screen update style in the first release was really just a hack that hijacked DDI's screen refresh routines. The 2nd release finally got the 'official' way to work so the hack was removed.
I voted faster...there isn't any other reason I came to XDA other than customizing.
Anyone who doesn't want a faster cellphone won't appreciate the new D3D drivers anyway.
There are may reasons the XDA Gold Rom (HTC Original 6.1) may be slower. Cooks reduce the software on the rom and use newer software versions, these may be faster than the previous ones.
Also this software is not from the Kaiser sometimes these may be causing the incompatiblity problems with the drivers.
The HTC original rom is slower to start than most cooked roms anyway, so way wouldn't the 3d drivers also run slower.
I decided not to vote, I think speed is a non issue as long as the drivers work on the HTC original rom, and are stable. You will always get rom's that perform faster, that's what cooks do round here.
I also don't think you would get a big jump in performance writing for just one rom, the hardware is the same in all the HTC Kaiser's handsets. Software can only make small difference to the performance of hardware if the drivers are written correctly.
personally i would love the drivers in a rom like dutty's diamond v1, but i think building them into a standard(ish) htc rom is best for the comunity; it sticks it to htc best as it shows u guys can do what they couldn't(or wouldn't), and makes flashing a rom feel safer to noobs.
and anyway we all know within hours of a rom with the drivers being released there will be dozens of cooked versions for all tastes with the drivers included too.
is it me or is it the rom developments for incs has slowed down significantly?
i dont see any new roms popping up.. most of the recently active roms have slowed down too.. are we getting left behind?
think (hope) it will pickup after first official ICS Sense roms starts to leak. on the other hand, incredible S is starting to be a bit outdated (although it has some decent hardware), more focus seems to be on the dual core, more popular devices. we gotta admit, incredible s isn't that popular - we don't even officially have it on any carriers in my country.
I think the main cause is 'android fragmentation'. You may have heard of this term before. There's too many android devices, each further HTC device release caused all of us to separate into different development sections.
Back in the G1, Nexus one days it was much easier since there were relatively few devices..
Now all the new stuff's out, lots of people want to jump to Galaxy Nexus, so on.
---------- Post added at 11:42 AM ---------- Previous post was at 11:17 AM ----------
andrei.je said:
think (hope) it will pickup after first official ICS Sense roms starts to leak. on the other hand, incredible S is starting to be a bit outdated (although it has some decent hardware), more focus seems to be on the dual core, more popular devices. we gotta admit, incredible s isn't that popular - we don't even officially have it on any carriers in my country.
Click to expand...
Click to collapse
The funny thing is dual core doesn't offer much improvement over the single, it seems like a lot of hype going on over nothing. probably over 3/4th or I dare say 90+% of the market is still written for single core applications.
I have the asus transformer 1 and most times I feel like performance is on par if not the same with the IncS, but when compared to my HTC Flyer (View) it feels much speedier since it's got a 1.5Ghz clock speed, the extra 500mhz shows sometimes. It takes heavy games like Shadowgun to see the difference between all devices, which can't be seen much in general surfing and regular phone related app use.
This is one thing that Apple has the advantage to in their gameplay strategy for devs, since they keep the releases specific, once a year. Development of their devices can be pooled and properly 'coordinated' without them moving onto different branches due to hardware, SoC, camera issues and so on.
Agree, if the first ICS HTC ROMs are leaked, development will gain momentum.
Right now, lots of work is spent on getting the camera working in ICS AOSP.
also, we gotta look at this ROM development as a hobby of the devs, one that usually starts with enthusiasm but over time proves to be very time consuming and falls last on their list of priorities. and unfortunately not a lot of people are willing or have the knowledge to fill in for the devs that get out of the game. i'm still reading up on android basics and kernel development, trying to make my first mix. Custom ROM development won't pay the bills, its mostly charity work.
You got to be grateful and appreciate their work.
Just last week there was a developer inviting testers for his vivo port http://forum.xda-developers.com/showthread.php?t=1475459 and yet strangely, I don't see you contributing anything to the thread... in fact the response from the whole incredible s community was actually pretty unwelcoming. If I was a developer I would bypass this phone also, which seems to be pretty much what happened 6+ months ago.
Somehow, I missed that thread. I tend to not really read the index in general section often but I read the index of the dev section frequently.
I'm trying to jumpstart some action into the IncS, may not be much, but I have been building CM7.2 kangs and in the middle of testing building a CM9 kang, see how it goes.
Nonverbose said:
Just last week there was a developer inviting testers for his vivo port http://forum.xda-developers.com/showthread.php?t=1475459 and yet strangely, I don't see you contributing anything to the thread... in fact the response from the whole incredible s community was actually pretty unwelcoming. If I was a developer I would bypass this phone also, which seems to be pretty much what happened 6+ months ago.
Click to expand...
Click to collapse
i seemed to have missed his thread. will go over and take a look now
andrei.je said:
also, we gotta look at this ROM development as a hobby of the devs, one that usually starts with enthusiasm but over time proves to be very time consuming and falls last on their list of priorities. and unfortunately not a lot of people are willing or have the knowledge to fill in for the devs that get out of the game. i'm still reading up on android basics and kernel development, trying to make my first mix. Custom ROM development won't pay the bills, its mostly charity work.
You got to be grateful and appreciate their work.
Click to expand...
Click to collapse
i understand that, but the point that i want to point out here is that is our device getting left behind? im already thinking whether to sell my incs off and get a sensation instead but thinking back how hard nik and the guys worked so hard, it held me back for a moment
So you need to flash your phone 5 times or more per day to be satisfied? Why not use it instead? Heavy case of ORD .
hey bro,see this:http://forum.xda-developers.com/showthread.php?t=1490881
bigeyes0x0 said:
So you need to flash your phone 5 times or more per day to be satisfied? Why not use it instead? Heavy case of ORD .
Click to expand...
Click to collapse
lol ORD. not that man.. it's just that i see new roms popping out in the dhd section and the people there are always active and they never sleep. just wondering how can the dhd (old phone) be more popular than incs (newer) lol
Litestar said:
hey bro,see this:http://forum.xda-developers.com/showthread.php?t=1490881
Click to expand...
Click to collapse
i saw it bro. im pretty much worked up right now haha~ cant wait to try it!
There's a lot of things ppl can "masturbate" to with their phones. Like popularity with more ROMs like Desire HD, Sensation, Galaxy S2. I do it to longer battery life, better camera, radio reception, and it also fit better in my hands and palms ( at least compared to the DHD). More ROMs do not mean better quality ROMs, I'm fully satisfied right now with ARHD, and with the state of Quattro, I haven't even tried it. We're getting ICS officially that's good enough, I can wait for another stable custom ROM based on that. Be happy with what you know and have, ignorant is bliss. And I'm kinda gettings tired of ORD myself, maybe a case of cured one, until something remarkable new popped up .
bigeyes0x0 said:
There's a lot of things ppl can "masturbate" to with their phones. Like popularity with more ROMs like Desire HD, Sensation, Galaxy S2. I do it to longer battery life, better camera, radio reception, and it also fit better in my hands and palms ( at least compared to the DHD). More ROMs do not mean better quality ROMs, I'm fully satisfied right now with ARHD, and with the state of Quattro, I haven't even tried it. We're getting ICS officially that's good enough, I can wait for another stable custom ROM based on that. Be happy with what you know and have, ignorant is bliss. And I'm kinda gettings tired of ORD myself, maybe a case of cured one, until something remarkable new popped up .
Click to expand...
Click to collapse
Amen bro!
I'm with you in every word you said!
+1 for your post.
Sent from my HTC Incredible S
bigeyes0x0 said:
There's a lot of things ppl can "masturbate" to with their phones. Like popularity with more ROMs like Desire HD, Sensation, Galaxy S2. I do it to longer battery life, better camera, radio reception, and it also fit better in my hands and palms ( at least compared to the DHD). More ROMs do not mean better quality ROMs, I'm fully satisfied right now with ARHD, and with the state of Quattro, I haven't even tried it. We're getting ICS officially that's good enough, I can wait for another stable custom ROM based on that. Be happy with what you know and have, ignorant is bliss. And I'm kinda gettings tired of ORD myself, maybe a case of cured one, until something remarkable new popped up .
Click to expand...
Click to collapse
It's like you said =)
Sometimes you don't need a lot of things to have a great experience.
I remember back in the LG P500 days, there was only one rom and one kernel and the thing was fantastic.Even later new tweaks came,new roms,new kernels but the simpler ones were the best.
I like very much nikhil007mmus's work and Virtuous Team work, both very stable and fast.
I even suggested nikhil007mmus to talk with Francisco Franco to share some ideas to make even greater kernels for our device (kernel devs, don't get me wrong, I am not saying your work is bad, I don't even test it, but what I do know is that this man makes GREAT kernels, with great performance,great battery life and it keeps them simple.I tested his kernels in the P500 (Wich made the thing fast as hell (For a 600MHz device of course) and in the Nexus S (I got 2 full days of battery life with wifi,3g,lots of calls,etc etc and fast as hell).
Hope it get's even better here =)
Problem is the Incredible S was not a popular phone to begin among devs. Not like the Nexus One, Desire HD, Sensation and Galaxy S II.
Sent from my HTC Incredible S using xda premium
The bad and nice thing of HTC phones is, they have a bunch of devices with practically nearly identical internal HW. Thus you don't actually really need that many devs on one device in particular. The way I see it, quality is way more important, we already have Android fragmentation like some say, now we also have custom ROM fragmentation . All Sense 3.5 roms failed for me when toggling data. It would not be that much of a problem on Samsung as they don't disable data during call, but HTC do, and sometimes after call data doesn't come up which is a major problem for me as I need auto-sync for a bunch of services and it is the most annoying bug of all. I wish devs collaborated more for less ROMs but better quality. It also means less duplicated effort.
For now I'm using a ROM Cleaned ARHD 2.1.3 with Ultra Smooth Rosie, batt mod, odexed, and some tweaks in init.d. It's smooth like butter and I think that I can be happy until whenever ICS comes out, unless some Sense 3.5 custom ROM devs fixed the bug above. Just use your phone, the best is yet to come. And if you're too trigger happy buy Samsung GSII to flash around and chaotic development. My brother has one and I am actually the one modding it for him. It's insanely fast yet I do not want it (because of aesthetic, functional reasons and knowing what is enough) even though I can afford it.
Is it just me, or does the Sprint HTC One seem to be completely overlooked by ROM developers? TWRP for Sprint HTC One is still only 2.6.3.0 despite 2.6.3.3 and 2.6.3.4 being out for other phones for months. Nearly every ROM I have looked at seems to support every HTC One variant except for Sprint. If you want Sprint support, you have to use an older version. The latest CWM for m7spr does support KitKat, and I have been able to install CM11 nightly, but this is extremely buggy, and every nightly build seems to introduce as many new problems as it solves. Is there any stable KitKat ROM that doesn't suck and supports Sprint? Is there a reason developers hate Sprint users? Please someone tell me the answer to this.
Well I'm on the official cm11 from 1/3 and its running perfectly now for me except the browser once l toggled the data to CDMA/lte but that's it. Ecliptic seems to run as good as any other 5.5 on 4.4 Sense in my experience with it. I only use Sense a little because since the 4.3 ota the WiFi doesn't upload data at all and I use that way too much to tolerate that absence but the devs overlook it. Oh well cm it is until its fixed by Sprint.
Sent from my One using Tapatalk
No offense but if you bothered to do a simple Google search, you'd find that an official 4.4 OTA for sprint is not yet released which is why there is a lack of stable 4.4 roms...
vcumsk said:
No offense but if you bothered to do a simple Google search, you'd find that an official 4.4 OTA for sprint is not yet released which is why there is a lack of stable 4.4 roms...
Click to expand...
Click to collapse
Agree with the need to do a search before complaining about the devs sucking around here (which is effectively what was said, imho).
I have to dissent from the 'no stable kitkit' ROMs, though. For instance, EclipicONE [4.4] is quite stable -- it is, after all, based on InsertCoin and I can't imagine anyone suggesting @baadnewz creates anything other than extremely stable ROMs when he says they're good to go, and @hawknest is clearly no slouch either. I've used EclipticONE since the final test versions for my day to day -- no problems at all and fact it's outperforming my 4.3 ROMs (generally use ViperONE or InsertCoin) handily in battery, speed (I clocked it up to the 1.7 our processor is supposed to be, but even the default 1.1GHz top end runs totally smoothly) and general operations.
Not on a high horse here -- just saying ... I find we do in fact have stable kitkat based roms.
Eliptic is super stable. It can't get better than this. Plus it has s2w and s2s
Sent from my HTCONE using Tapatalk
TV4FUN said:
Is it just me, or does the Sprint HTC One seem to be completely overlooked by ROM developers? TWRP for Sprint HTC One is still only 2.6.3.0 despite 2.6.3.3 and 2.6.3.4 being out for other phones for months. Nearly every ROM I have looked at seems to support every HTC One variant except for Sprint. If you want Sprint support, you have to use an older version. The latest CWM for m7spr does support KitKat, and I have been able to install CM11 nightly, but this is extremely buggy, and every nightly build seems to introduce as many new problems as it solves. Is there any stable KitKat ROM that doesn't suck and supports Sprint? Is there a reason developers hate Sprint users? Please someone tell me the answer to this.
Click to expand...
Click to collapse
try Beanstalk 4.4, it's stable and everything works.
Aldo101t said:
try Beanstalk 4.4, it's stable and everything works.
Click to expand...
Click to collapse
Without tooting my own horn(cuz it ain't me who designs this ROM, I just build it), BS 4.4.205 is one of the best KK custom ROMs around, and I check. It does not have a completely bug-free experience, but for the scale of what is offered in options versus what doesn't work properly, you can't do much better anywhere. Most of the other custom ROMs are still implementing KK. As far as stock or stock-based, the earlier comments are all true. I do feel as though development here has stalled, and in general, Sprint is the ugly stepchild of the carrier system, based on how the phone is designed to run(totally different than any other carrier). Most of the truly gifted and knowledgeable devs have already moved on to the next big thing, which unfortunately, is the name of the game around here. But, I love my m7spr, and although I am not a coding guru, I plan to stick around for a while and try to get more cool ROM choices out there.
TV4FUN said:
Is it just me, or does the Sprint HTC One seem to be completely overlooked by ROM developers? TWRP for Sprint HTC One is still only 2.6.3.0 despite 2.6.3.3 and 2.6.3.4 being out for other phones for months. Nearly every ROM I have looked at seems to support every HTC One variant except for Sprint. If you want Sprint support, you have to use an older version. The latest CWM for m7spr does support KitKat, and I have been able to install CM11 nightly, but this is extremely buggy, and every nightly build seems to introduce as many new problems as it solves. Is there any stable KitKat ROM that doesn't suck and supports Sprint? Is there a reason developers hate Sprint users? Please someone tell me the answer to this.
Click to expand...
Click to collapse
Thanks for joining XDA nearly 4 years ago and only posting 7 times. Good thing you used one of those 7 for this stupid post to discourage the developers we do have for Sprint. Boo I say, Boo!
OT
I'm getting really annoyed with these 'did you search first, stupid?' posts. Get off yourself. Yeah, there's a lot of information out there, but most of it's junk/spam, obsolete or completely irrelevant. There's so much crap info out there. If someone is unsure enough about something to get to the point of asking a question to get an answer, and you know the answer, just answer it.
Google 'sprint kit kat htc one'. Kind of interesting sure, but absolutely none of that is useful information esp in helping TV4FUN get an answer. Blogspot opinions, link farms copying things over and over, unrelated sprint and Moto(?!) info and random HTC ad crap, etc.
Similar experience to TV4FUN.. IMO there are no daily drivers for KK yet, probably not until Sprint KK and source is released. Much thanks to the devs who are working hard to get there though.
[irony]everyone stop beings dicks to everyone[/obvious]
pbassjunk said:
OT
I'm getting really annoyed with these 'did you search first, stupid?' posts. Get off yourself. Yeah, there's a lot of information out there, but most of it's junk/spam, obsolete or completely irrelevant. There's so much crap info out there. If someone is unsure enough about something to get to the point of asking a question to get an answer, and you know the answer, just answer it.
Google 'sprint kit kat htc one'. Kind of interesting sure, but absolutely none of that is useful information esp in helping TV4FUN get an answer. Blogspot opinions, link farms copying things over and over, unrelated sprint and Moto(?!) info and random HTC ad crap, etc.
Similar experience to TV4FUN.. IMO there are no daily drivers for KK yet, probably not until Sprint KK and source is released. Much thanks to the devs who are working hard to get there though.
[irony]everyone stop beings dicks to everyone[/obvious]
Click to expand...
Click to collapse
It's just funny how I'm able to search and find 99% of the answers to questions I have. I don't think I'm special, it's just pretty east. That is why.
http://forum.xda-developers.com/showthread.php?p=48697103
Me, @buckmarble and @brymaster5000
Have made kitkat on Sprint quite stable
From My Dark EclipticONE
hawknest said:
http://forum.xda-developers.com/showthread.php?p=48697103
Me, @buckmarble and @brymaster5000
Have made kitkat on Sprint quite stable
From My Dark EclipticONE
Click to expand...
Click to collapse
Agreed! :good: :beer:
hawknest said:
http://forum.xda-developers.com/showthread.php?p=48697103
Me, @buckmarble and @brymaster5000
Have made kitkat on Sprint quite stable
From My Dark EclipticONE
Click to expand...
Click to collapse
Yes thank you. I am using EclipticONE now and it is quite stable. By the way, does vDM client do anything important?
Sent from my HTCONE using Tapatalk
I'm confused about this because little by little we are getting more and more roms for this phone more than when I first got here. A lot of the aosp issue we have the other variants of the m7 have as well and a lot are Google based issues, one reason the devs are having issues is that kit kat has changed a lot even cyanogen him self has said so.
Be patient and remember no one here gets paid for this, they do it out of love for Android and a little respect I believe is deserved.
Edit: Mods should have closed this a while ago because it kills moral.
Sent from my One using XDA Premium 4 mobile app
Ecliptic is good enough for a daily driver. In my opinion so are the nocturnal roms. I have never tried beanstalk so I cannot speak to that. But I think there are plenty of options out there. I guess it just boils down to how picky you are.
I would like to know what about ecliptic kk is not stable? just my 2 cents but most these issues people complain about are self induced due to lack of research or just nit picky! Come to think of it there isn't a single sense rom atleast that I have tried that isn't damn near perfect. I for one am feel very fortunate to be a part of the sprint m7 community
jblaze10 said:
I would like to know what about ecliptic kk is not stable? just my 2 cents but most these issues people complain about are self induced due to lack of research or just nit picky! Come to think of it there isn't a single sense rom atleast that I have tried that isn't damn near perfect. I for one am feel very fortunate to be a part of the sprint m7 community
Click to expand...
Click to collapse
Depends who you ask. For some people, 'stable' means completely bug free.
vcumsk said:
Depends who you ask. For some people, 'stable' means completely bug free.
Click to expand...
Click to collapse
Then "those" people should stick to stock software and not be installing custom ROMs.
raptoro07 said:
Then "those" people should stick to stock software and not be installing custom ROMs.
Click to expand...
Click to collapse
EXACTLY!! And actually I think that with all these batt drain and SIM card issues the ota has presented. One could argue that the custom software here is better than the official versions!
OP you can go to Tmo now they will pay your ETF, get a gsm One if you need kit kat so bad
Sent from my HTCONE using Tapatalk
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
Would any developer be willing to create an MIUI or IOS ROM for the HTC Desire 626 Metro PCs?
MIUI: Would they- No ; Could they- Yes, but there is not a single reason to do so.
iOS - Impossible
Also, wrong section. Please try to follow forum guidelines and post in the appropriate section (q&a)
Whoareyou said:
MIUI: Would they- No ; Could they- Yes, but there is not a single reason to do so.
iOS - Impossible
Also, wrong section. Please try to follow forum guidelines and post in the appropriate section (q&a)
Click to expand...
Click to collapse
Will repost in q&a. Thanks so much for your kind answer. Looks like you got it all figured out.
Whoareyou said:
iOS - Impossible
Click to expand...
Click to collapse
Probably a reference to JoyOS, an iOS cloned theme that was last seen around the time CM 7 was still the most popular ROM. To my knowledge the original Chinese forum which was doing the heavy lifting abandoned this quite some time ago. With the exception of the Goophone I don't think anyone is doing full conversion ROMs which resemble iOS anymore and their systems don't seem to have been dumped and translated yet, which by this time indicates there is no interest.
Sent from my 0PM92 using Tapatalk
EDIT: Links are hard
bornagainpenguin said:
Probably a reference to JoyOS, an iOS cloned theme that was last seen around the time CM 7 was still the most popular ROM. To my knowledge the original Chinese forum which was doing the heavy lifting abandoned this quite some time ago. With the exception of the Goophone I don't think anyone is doing full conversion ROMs which resemble iOS anymore and their systems don't seem to have been dumped and translated yet, which by this time indicates there is no interest.
Sent from my 0PM92 using Tapatalk
EDIT: Links are hard
Click to expand...
Click to collapse
That explains the reason why there's no more ios rom creation. But, what about MIUI? The os of MIUI has dramatically evolved over the past 4 years. Am I tripping, or is it that no one wants to take a crack at creating a rom for us little guys for devices such as the HTC Desire 626s?
s3llz said:
But, what about MIUI? The os of MIUI has dramatically evolved over the past 4 years. Am I tripping, or is it that no one wants to take a crack at creating a rom for us little guys for devices such as the HTC Desire 626s?
Click to expand...
Click to collapse
Believe it or not rom creation is hard and relies on having the sources available (which not all companies will do--HTC used to be better than most about this which is why I took a chance on this phone) and on having developers who have the phone and are capable\willing to do the hard work of making a complete AOSP or Cyangogenmod version of the base operating system. Only after that has been completed do you usually start to see more exotic systems like MIUI, Mokee, ParanoidAndroid, etc, get ported over. Even then there's a dirty little secret about Android roms:
Most of them never get 100% compatibility and hardware support. Ever. Despite the best efforts of the porters.
I had an HTC One V which did well for its time but the camera never quite made it to 100% hardware support. Same thing with bluetooth. My LG Optimus F3 never quite got anywhere with roms and eventually I gave up on it and moved on to the HTC Desire 626s which despite some solid efforts at producing the slimmed down version I am currently running also does not seem to have any real custom android roms.
This goes back to my first point: Rom creation is hard.
That's why even when people put up bounties and buy phones for well known rom hackers who have produced many ports, it still doesn't always result in new roms. Because it's a lot harder than it looks.
I was spoiled initially, I had an LG Optimus V which quickly had a custom rom built for it with very good hardware support which was lean and clean. There were custom kernels for it and it quickly had all sorts of ports of everything from CM7 to JoyOS to MIUI to Mokee and friends within a relatively short period of time. It was the little phone that could and I mistakenly believed that because lightening struck and all sorts of good things were happening this was how it always was. Not even close to the case.
I got lucky. The LG Optimus V was cheap enough that it attracted all sorts of interest from a variety of the right people at the right time. This kind of thing isn't even close to being normal. Some times you get lucky, sometimes you don't.
So why not MIUI? Well I'm sorry to say but for one thing MIUI is heavy. It's heavy like Touchwiz or Sense can be, and that sort of thing can only be helped with massive amounts of optimization. Sadly not every phone has a developer (or group of developers) who are willing to do that sort of thing for free.
So all I can say is appreciate the level of development we've got and be thankful for the work of the developers who have released a slimmer rom for us already. If you need a MIUI rom for your phone, you should probably track the releases here before buying. If you check the forums, you'll see you are not alone. There are lots of people who want MIUI ports.
bornagainpenguin said:
Believe it or not rom creation is hard and relies on having the sources available (which not all companies will do--HTC used to be better than most about this which is why I took a chance on this phone) and on having developers who have the phone and are capable\willing to do the hard work of making a complete AOSP or Cyangogenmod version of the base operating system. Only after that has been completed do you usually start to see more exotic systems like MIUI, Mokee, ParanoidAndroid, etc, get ported over. Even then there's a dirty little secret about Android roms:
Most of them never get 100% compatibility and hardware support. Ever. Despite the best efforts of the porters.
I had an HTC One V which did well for its time but the camera never quite made it to 100% hardware support. Same thing with bluetooth. My LG Optimus F3 never quite got anywhere with roms and eventually I gave up on it and moved on to the HTC Desire 626s which despite some solid efforts at producing the slimmed down version I am currently running also does not seem to have any real custom android roms.
This goes back to my first point: Rom creation is hard.
That's why even when people put up bounties and buy phones for well known rom hackers who have produced many ports, it still doesn't always result in new roms. Because it's a lot harder than it looks.
I was spoiled initially, I had an LG Optimus V which quickly had a custom rom built for it with very good hardware support which was lean and clean. There were custom kernels for it and it quickly had all sorts of ports of everything from CM7 to JoyOS to MIUI to Mokee and friends within a relatively short period of time. It was the little phone that could and I mistakenly believed that because lightening struck and all sorts of good things were happening this was how it always was. Not even close to the case.
I got lucky. The LG Optimus V was cheap enough that it attracted all sorts of interest from a variety of the right people at the right time. This kind of thing isn't even close to being normal. Some times you get lucky, sometimes you don't.
So why not MIUI? Well I'm sorry to say but for one thing MIUI is heavy. It's heavy like Touchwiz or Sense can be, and that sort of thing can only be helped with massive amounts of optimization. Sadly not every phone has a developer (or group of developers) who are willing to do that sort of thing for free.
So all I can say is appreciate the level of development we've got and be thankful for the work of the developers who have released a slimmer rom for us already. If you need a MIUI rom for your phone, you should probably track the releases here before buying. If you check the forums, you'll see you are not alone. There are lots of people who want MIUI ports.
Click to expand...
Click to collapse
Thank you. You have truly answered my questions, even ones I wondered about but didn't ask. I am greatly satisfied with what you have said. I understand that rom creation is hard and it can take a toll on the one creating the rom. It's not an easy task. I to had a Samsung galaxy epic 4g touch, which had all sorts of roms for it. But also knowing from experience, you are correct. It is a hit and miss sometimes with some devices you buy. Maybe as newer devices are created, the ability to create ROMs for them gets harder because of the upgraded technology and coding. I could be wrong. On the miui official site, they is a list of devices that they support. But most of them are old school and i surely wouldn't want to take a step down from this phone just to have miui. Then the newer phones in some cases cost more than this phone(referring to the HTC desire 626). I do appreciate the effort that has been put forth for a slimmed down version for this phone. But what I've asked in previous threads was whether or not there is root access yet for the mm update for the metro PCs version of the HTC desire 626s. No bites what so ever. I'm guessing either there isn't any or I'm just not coming across it yet. Any help on that would be highly appreciated. But all in all, I would really like to say thank you for taking the time to answer my question. I appreciate that. You have brought some clarity to the table. I wouldn't mind help supporting a developer who would be willing to create an miui rom for our device once a cyanogenmod version is acquired.
s3llz said:
Thank you. You have truly answered my questions, even ones I wondered about but didn't ask. I am greatly satisfied with what you have said. I understand that rom creation is hard and it can take a toll on the one creating the rom. It's not an easy task. I to had a Samsung galaxy epic 4g touch, which had all sorts of roms for it. But also knowing from experience, you are correct. It is a hit and miss sometimes with some devices you buy. Maybe as newer devices are created, the ability to create ROMs for them gets harder because of the upgraded technology and coding. I could be wrong. On the miui official site, they is a list of devices that they support. But most of them are old school and i surely wouldn't want to take a step down from this phone just to have miui. Then the newer phones in some cases cost more than this phone(referring to the HTC desire 626). I do appreciate the effort that has been put forth for a slimmed down version for this phone. But what I've asked in previous threads was whether or not there is root access yet for the mm update for the metro PCs version of the HTC desire 626s. No bites what so ever. I'm guessing either there isn't any or I'm just not coming across it yet. Any help on that would be highly appreciated. But all in all, I would really like to say thank you for taking the time to answer my question. I appreciate that. You have brought some clarity to the table. I wouldn't mind help supporting a developer who would be willing to create an miui rom for our device once a cyanogenmod version is acquired.
Click to expand...
Click to collapse
Metro pcs desire 626s can be rooted
IsaacGuti said:
Metro pcs desire 626s can be rooted
Click to expand...
Click to collapse
By any chance would you mind telling me how you rooted it? I know how to unlock the bootloader, but where do I get the custom recover from and su?
s3llz said:
By any chance would you mind telling me how you rooted it? I know how to unlock the bootloader, but where do I get the custom recover from and su?
Click to expand...
Click to collapse
The custom recovery is posted in this thread and used this> supersu.zip, fastboot flash the recovery and then flash the supersu.zip in recovery. After flashing supersu and booting up install busybox.
BUT don't forget to make a backup, just incase.
IsaacGuti said:
The custom recovery is posted in this thread and used this> supersu.zip, fastboot flash the recovery and then flash the supersu.zip in recovery. After flashing supersu and booting up install busybox.
BUT don't forget to make a backup, just incase.
Click to expand...
Click to collapse
Thank you sir for the info. I am unlocked and rooted again. Now, I'll sit back and wait for some debloated roms to pop up for 6.0.1 2.17.1550.1 Metro PCS.
Hey, if you're still interested in Miui, you could try installing the launcher app, see if that gives you enough of the miui experience to get by until someone eventually makes a port?
Sent from my 0PM92 using Tapatalk
bornagainpenguin said:
Hey, if you're still interested in Miui, you could try installing the launcher app, see if that gives you enough of the miui experience to get by until someone eventually makes a port?
Sent from my 0PM92 using Tapatalk
Click to expand...
Click to collapse
Wish I could, but it isn't compatible with mashmallow.
s3llz said:
Wish I could, but it isn't compatible with mashmallow.
Click to expand...
Click to collapse
My bad. Here I found the app in my Play Store history, (from before Google made it country specific?) and installed it. It immediately crashed but stayed open. From there I updated it from within the launcher settings and it crashed again. Just as I was about to give up I had a brainstorm and went back into settings and turned off the lockscreen. This made it stop crashing for me. I hunted around for Beautiful Widgets and replaced the clock and installed miui theme for it and everything looks good from here.
So I installed Titanium Backup and uploaded the app. Hopefully this helps you.
Sent from my 0PM92 using Tapatalk