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.
with the release of froyostone rom for the hd2 which is sense + 2.2 officially from htc, I believe it would be much easier to port sense to the captivate and completely remove touchwiz.
First your posting in the wrong captivate forum section...second the Android os isn't something that can be magically ported to XX device just because XXX device has it or its working on it, for starters the hd2 is a non native android device, which means its running an android port, with the help of a half working linux kernel, loaded with haret bootloader, android 2.2 is coming in September so just sit tight and be patient, or you can download CM6 vibrant source and port it over to the captivate(you would have to make the captivates kernel compatible with 2.2, meaning backporting/patching etc) which ever you like.
Rafyvitto
Yeah it ought to be about as easy as loading OS X on a Commodore 64.
gunnyman said:
Yeah it ought to be about as easy as loading OS X on a Commodore 64.
Click to expand...
Click to collapse
Well, maybe Steve can call Xerox for some help with that...
dressanderc said:
Well, maybe Steve can call Xerox for some help with that...
Click to expand...
Click to collapse
I LOL'ed +tenchars
gunnyman said:
Yeah it ought to be about as easy as loading OS X on a Commodore 64.
Click to expand...
Click to collapse
dressanderc said:
Well, maybe Steve can call Xerox for some help with that...
Click to expand...
Click to collapse
ROFL thats some good stuff guys.
who wants sense anyways, it's just a big shiney TURD!
designgears said:
who wants sense anyways, it's just a big shiney TURD!
Click to expand...
Click to collapse
+1
where's some good ol' fashioned AOSP when you need it?
*hint hint* DG *hint*
Personally, I cant wait till all manufacturers realize we don't want to be forced into sense, touch wiz etc.
Make it default if you have to, but provide an option to enjoy raw, unadulterated android!!!
I guess we wait and see what Gingerbread does about that.
To the OP, why don't YOU port Android 2.2 to the Captivate AND also port Sense??
Joking aside I am going to be cooking for the Captivate soon. I'm just waiting for Froyo so I can get my hands dirty with Android .
Maybe even a Sense port??
I've been working on porting sense to our the device for some weeks now but roms fail to boot, changing libs etc, got no clue of what else to try.
Sense is so deeply entangled into Android, kinda like trying to remove Internet Explorer from Windows 95, It is virtually impossible to get it working without all the kernel extensions HTC added to the OS.
gunnyman said:
Sense is so deeply entangled into Android, kinda like trying to remove Internet Explorer from Windows 95, It is virtually impossible to get it working without all the kernel extensions HTC added to the OS.
Click to expand...
Click to collapse
Just a historical footnote. Internet explorer was very easy to remove from windows 95. The original release of win95 didn't even include internet explorer. It was only available as part of the plus! Pack of addons. The SR1 release had IE v2 included but it could be easily deleted. It wasn't until IE 4 that active desktop became a part of the package and began making it difficult to seperate from the OS. IE 4 came sr2.5 but was an optional upgrade for most win95 instalations.
But i knew what you meant.
Sent from my SAMSUNG-SGH-I897 using XDA App
jaredc74 said:
Just a historical footnote. Internet explorer was very easy to remove from windows 95. The original release of win95 didn't even include internet explorer. It was only available as part of the plus! Pack of addons. The SR1 release had IE v2 included but it could be easily deleted. It wasn't until IE 4 that active desktop became a part of the package and began making it difficult to seperate from the OS. IE 4 came sr2.5 but was an optional upgrade for most win95 instalations.
But i knew what you meant.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
haha, I was literally going to add almost exactly this.
Sense seems only to be portable to devices that can run off of HTC-based ROMs. It seems to be much easier to remove it than to try and bring it over (I haven't heard of it being brought to a device that wasn't HTC based). The widgets haven't even been ported to the best of my knowledge to work on non-Sense launchers. And, as proven by our phones, they could have made Sense even MORE integrated considering removing touchwiz launcher causes massive force closes. Also, Sense is proprietary and cosed source, so we don't have any low-level access to remove the HTC restrictions (short of binary hacking, which I know nothing about and could indeed be wrong about)
Kaik541 said:
haha, I was literally going to add almost exactly this.
Sense seems only to be portable to devices that can run off of HTC-based ROMs. It seems to be much easier to remove it than to try and bring it over (I haven't heard of it being brought to a device that wasn't HTC based). The widgets haven't even been ported to the best of my knowledge to work on non-Sense launchers. And, as proven by our phones, they could have made Sense even MORE integrated considering removing touchwiz launcher causes massive force closes. Also, Sense is proprietary and cosed source, so we don't have any low-level access to remove the HTC restrictions (short of binary hacking, which I know nothing about and could indeed be wrong about)
Click to expand...
Click to collapse
Well how the huck did they get Sense on the HD2?? It doesn't even come with android from factory! We need someone to shed a little more light in this. Maybe its because they use some Qualcomm specific images or something.
rafyvitto said:
I've been working on porting sense to our the device for some weeks now but roms fail to boot, changing libs etc, got no clue of what else to try.
Click to expand...
Click to collapse
You got a PM
DJGonzo said:
Well how the huck did they get Sense on the HD2?? It doesn't even come with android from factory! We need someone to shed a little more light in this. Maybe its because they use some Qualcomm specific images or something.
Click to expand...
Click to collapse
notice how I said I can't see it being ported to a non-HTC device. The HD2 is indeed an HTC device and I believe the ROM that has Sense is one built off of an HTC ROM for another device. Much like how the Legend ROMs were able to be fairly easily/quickly ported to the Aria. In fact, many of the internals of the HD2 resemble a lot of the Android hardware produced by HTC (qualcomm snapdragon and all that good stuff I believe)... the difficulty of getting android on that device had nothing to do with the ROMs, but actually getting haret to boot a linux kernel properly.
Kaik541 said:
notice how I said I can't see it being ported to a non-HTC device. The HD2 is indeed an HTC device and I believe the ROM that has Sense is one built off of an HTC ROM for another device. Much like how the Legend ROMs were able to be fairly easily/quickly ported to the Aria. In fact, many of the internals of the HD2 resemble a lot of the Android hardware produced by HTC (qualcomm snapdragon and all that good stuff I believe)... the difficulty of getting android on that device had nothing to do with the ROMs, but actually getting haret to boot a linux kernel properly.
Click to expand...
Click to collapse
Unless they ported the whole ROM and re used drivers, I don't quite understand how they got it to work.
They got Sense 2.5 working from The HD2 onto the Omnia II (winmo), so its quite possible. We just need a team of developers willing to do the work. I can offer hosting and testing and little technical help since I am new at Android but I think we can get it to work if we start to tinker with it.
Maybe a ROM port is in order?
Maybe we should wait for a Froyo kernel though.
DJGonzo said:
Unless they ported the whole ROM and re used drivers, I don't quite understand how they got it to work.
They got Sense 2.5 working from The HD2 onto the Omnia II (winmo), so its quite possible. We just need a team of developers willing to do the work. I can offer hosting and testing and little technical help since I am new at Android but I think we can get it to work if we start to tinker with it.
Maybe a ROM port is in order?
Maybe we should wait for a Froyo kernel though.
Click to expand...
Click to collapse
I'm not saying it's impossible, I'm saying it hasn't been done. There are (correct me if I'm wrong) absolutely no non-HTC android devices with the Sense UI. I know nothing about the HD2/Omnia II Sense port, but that's WinMo... not even remotely close to Android in terms of interoperability. I also feel like any ROMs designed to bring Sense UI to non-HTC android devices would be hit with C&D's since it's their proprietary software (hence why both Fancy Widget and Beautiful Widgets got in trouble originally when they launched on the market).
Don't get me wrong, good luck in porting it, hell even I like the look of it and would love the option, but considering how long Sense has been out for android (and numerous devices) and we don't see it on any non-HTC android devices, I have to believe it's been tried and just doesn't work (which is why you also don't see MotoBLUR/NinjaBLUR anywhere else either... or even TouchWiz on the EVO)
Also I think the HD2 and the Desire are the same hardware. If not the Desire it's another phone. That also makes porting Android pretty painless.
Before any of you say anything negative this isnt to bug other devs this is a thread for people to request/ ask for things me and the other devs to do after they have finished their other projects.
-Firefox OS
-LG UI(fix lockscreen)
-CM7
-Sense 4.1
-cm10.1 WiFi and Bluetooth
-cm10 WiFi authentication issue
-S-OFF
-Roms for cdma version
-Sense 4.1.2
Just pop requests underneath and ill update reguarly.
Shad0wPanda said:
Before any of you say anything negative this isnt to bug other devs this is a thread for people to request/ ask for things me and the other devs to do after they have finished their other projects.
-Firefox OS
-LG UI
-CM7
Just pop requests underneath and ill update reguarly.
Click to expand...
Click to collapse
Sense 4.1 (If possible)
Shad0wPanda said:
Before any of you say anything negative this isnt to bug other devs this is a thread for people to request/ ask for things me and the other devs to do after they have finished their other projects.
-Firefox OS
-LG UI
-CM7
Just pop requests underneath and ill update reguarly.
Click to expand...
Click to collapse
Hahaha, heres an LG UI Rom, iv'e had it for a while, just lockscreen doesnt work at all! so slide down NC and hit settings to unlock, then install a custom locker such as holo locker! I'll post in the dev threads when i can be bothered, but test that out..
http://d-h.st/2V2
Click to expand...
Click to collapse
i think gettin bt and wifi implemented in cm 10.1 should be a good place to begin
lead3r1 said:
i think gettin bt and wifi implemented in cm 10.1 should be a good place to begin
Click to expand...
Click to collapse
+1
but we really need the devs to go back to work
CM7 FTW
CM7 first ... it would be super buttery smooth for us ...
How are you so certain it'd be "buttery smooth"? Cuz I'm not sure, if not totally negative on that matter.
How are you so certain it'd be "buttery smooth"? Cuz I'm not sure, if not totally negative on that matter.
Click to expand...
Click to collapse
Brnt you don't have to flash cm7... What's with all the gingerbread hate??
Sent from my HTC Desire C using xda app-developers app
I suggest we go back to XP then. It's going to run so much better on our new PCs!
It's not hate, you just get overexcited over nothing without even putting some though into it. Go on, prove me gingerbread will run smoother than JB/ICS, but without these facts your words are nothing.
brnt said:
I suggest we go back to XP then. It's going to run so much better on our new PCs!
It's not hate, you just get overexcited over nothing without even putting some though into it. Go on, prove me gingerbread will run smoother than JB/ICS, but without these facts your words are nothing.
Click to expand...
Click to collapse
I think you have your analogy wrong. Going from a newer version of Windows to an older version of Windows is pointless because...well...it's still Windows.
However, if you were to go from Ubuntu to, say, Slackware, you would definitely see a boost in performance because Slackware is far less taxing on the available resources. The same could be said about going from JB to GB. GB requires less resources and can therefore run smoother/faster on hardware designed for a higher version of Android. This is a well known fact throughout the Android community because nearly every JB or ICS based device has GB ROM development in some form or another.
It's still Android. Roughly 90% of the differences between JB/ICS and GB lie in the overall appearence, not the functionality.
IDEA
Or lets make CM10 even better
Like eliminate WiFi problems and hotspot problems etc :fingers-crossed:
What do you think?
S off would be good.
Not first priority though
sent from CM10'd Desire C
Phenziox said:
S off would be good.
Not first priority though
sent from CM10'd Desire C
Click to expand...
Click to collapse
It would be very useful though but it's more HTCs job
Sent from my HTC Desire C using xda premium
@soupmagnet, i agree entirely with that statement, however, where is the desire coming from for having GingerBread Roms? if it was desired so much, then why not buy a gingerbread phone in the first place? Would've been cheaper and there are still devices on the market, some with faster processors then the Desire C, if you wanted GingerBread, should've bought a GB Device, you don't go buy a brand new Windows 8 PC to deliberately downgrade it to a legacy OS like vista and limit the features you have access to. It lacks all logic in all honesty.. You don't go to sell a phone after use being all like, Yeah it has 2.3.5 GB on it, or brag to your mates, yeah my device is android 2.3.5, fact is 4.2.2 is the best android so far, Android has only improved over time, GB on our device is like an i7 with vista, you just don't do that kind of thing..
penguin449 said:
@soupmagnet, i agree entirely with that statement, however, where is the desire coming from for having GingerBread Roms? if it was desired so much, then why not buy a gingerbread phone in the first place? Would've been cheaper and there are still devices on the market, some with faster processors then the Desire C, if you wanted GingerBread, should've bought a GB Device, you don't go buy a brand new Windows 8 PC to deliberately downgrade it to a legacy OS like vista and limit the features you have access to. It lacks all logic in all honesty.. You don't go to sell a phone after use being all like, Yeah it has 2.3.5 GB on it, or brag to your mates, yeah my device is android 2.3.5, fact is 4.2.2 is the best android so far, Android has only improved over time, GB on our device is like an i7 with vista, you just don't do that kind of thing..
Click to expand...
Click to collapse
The problem with your logic is that Gingerbread based devices (with a few exceptions) only have hardware that is capable of meeting the low demands of Gingerbread.
For many people, the worth of their device is in its functionality, not its "bragging rights". I will never have Windows on my computer simply because of the features it provides. I use Linux, because of it's speed, stability and and overall functionality. ICS and JB do have some nice additional features, but at a noticeable cost of available resources and stability, and the overall functionality is still nearly the same. While higher versions of Android do provide some "improvements", they are mostly linked to the user interface (which many people don't necessarily like) and there are very few performance improvements. So for you to say that it "lacks all logic" is, well, illogical in itself.
While you may like what JB and ICS have to offer and prefer that for your daily driver, I don't think it's fair to ridicule others' personal preference in Android versions, considering the majority of changes between these versions are exclusive to the UI and not Android itself.
Off-topic... naughty naughty
Sent from my HTC Desire C using xda premium
Getting back on topic...
It would be nice to see more CDMA support though. I have a shell script, based on bin4ry's exploit, to root the CDMA variants, but it needs to be converted over to Windows' batch scripting language. If anyone wants to have a go at it, just let me know.
As far as ROMs are concerned, we can use the existing GSM ROMs, but a patch will need to be made. It wouldn't be that difficult to implement and would be much easier than creating all new CDMA ROMs.
The biggest problem would be getting a working recovery. I tried unpacking the existing (GSM) recovery and replaced the kernel with the phone's stock kernel but it didn't work out very well. I think a new recovery would need to be built from source, but I'm running into strange compile errors when compiling the stock kernel from source. I don't have experience building custom recovery so it's going to be challenging trying to figure everything out, but I think I can handle it.
Clearly, the need for CDMA support is low, but it's far from non-existent. I'm more than willing to take the reigns on this project, but I may have to take advantage of some of the experience around here, assuming there are those willing to lend a hand.
soupmagnet said:
The problem with your logic is that Gingerbread based devices (with a few exceptions) only have hardware that is capable of meeting the low demands of Gingerbread.
For many people, the worth of their device is in its functionality, not its "bragging rights". I will never have Windows on my computer simply because of the features it provides. I use Linux, because of it's speed, stability and and overall functionality. ICS and JB do have some nice additional features, but at a noticeable cost of available resources and stability, and the overall functionality is still nearly the same. While higher versions of Android do provide some "improvements", they are mostly linked to the user interface (which many people don't necessarily like) and there are very few performance improvements. So for you to say that it "lacks all logic" is, well, illogical in itself.
While you may like what JB and ICS have to offer and prefer that for your daily driver, I don't think it's fair to ridicule others' personal preference in Android versions, considering the majority of changes between these versions are exclusive to the UI and not Android itself.
Click to expand...
Click to collapse
I stand corrected, thankyou for clearing that up for me, i never thought to look at it in this way, however, when you do get a working recovering, i do so believe i added cdma support in SHTD, the rom was both configured for cdma and for gsm, as it is in the build.prop also!, however a cdma aosp kernel would be needed
cm10.1 wifi bluetooth fixed would be a cool rom... Devs plz fix it... We noobs will be greatfull to you......:laugh::laugh::good:
akashgartia said:
cm10.1 wifi bluetooth fixed would be a cool rom... Devs plz fix it... We noobs will be greatfull to you......:laugh::laugh::good:
Click to expand...
Click to collapse
Don't rush them. They have other stuff to do. If you want it done, you could learn and try it yourself.
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