hi
i just got a samsung dart from my girlfriend
it says that this phone also is galaxy mini so i have a question will ANY of these roms work on a rooted samsung dart?
Apparently yes, since Samsung Dart is a Galaxy Mini renamed by T-Mobile. But only testing can confirm...
hmmm.....im going to try one im running cm7.1 i found on a dart forum but ill report back
Some work done don't even boot
Sent from my Galaxy Mini (SGH-T499) using Tapatalk 2 Beta-2
squidbutt said:
Some work done don't even boot
Sent from my Galaxy Mini (SGH-T499) using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
Too bad... could you at least return to the original ROM (assuming you were using original stock ROM)?
If you could give us more details...
shame
i just purchased the t-499 myself and its a shame that such a new/great phone has so little support, ive looked all over google and only gotten mixed answers and dead end threads. icant even figure out if galaxy mini roms are cross compatible to the dart or not. its actually a good phone with a decent screen if u change the lcd_density to 100 the resolution is pretty decent.
if someone can help me a little it would be greatly appreciated, atleast point me in the right direction.
Not sure where else to post this, but can someone tell me if I can use a bootanimation.zip on the Samsung Dart? I've looked at a lot of threads on how to do this, used ROM toolbox to move files around, but haven't had any luck. I'd just like to know for sure so I don't drive myself crazy and waste more time!
D1358531 said:
Not sure where else to post this, but can someone tell me if I can use a bootanimation.zip on the Samsung Dart? I've looked at a lot of threads on how to do this, used ROM toolbox to move files around, but haven't had any luck. I'd just like to know for sure so I don't drive myself crazy and waste more time!
Click to expand...
Click to collapse
On he stock Dart rom, no.
Samsung apparently uses some weird proprietary bootanimation format.
I am running the CM7 port in my sig from the MadTeam Forums and it of course uses bootanimation.zip's and I even have enabled boot sounds on it.
It's a good rom, couple of really minor bugs like button lights don't work and slow to wake on incoming calls, but overall quite stable.
Bummer....I guess I'll have to wait til I can upgrade to a new phone
they have make new rom for dart
ShawnnKushh said:
i just purchased the t-499 myself and its a shame that such a new/great phone has so little support, ive looked all over google and only gotten mixed answers and dead end threads. icant even figure out if galaxy mini roms are cross compatible to the dart or not. its actually a good phone with a decent screen if u change the lcd_density to 100 the resolution is pretty decent.
if someone can help me a little it would be greatly appreciated, atleast point me in the right direction.
Click to expand...
Click to collapse
How do you change the lcd_density to 100 in the stock ROM?
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