Related
I been obsessed lately, trying to find something that works with our new D4's. I flashed Arctic's VZW rom after rooting my phone and....it works! I have tested SMS/MMS, GPS and phone calls with no issue. The only think that i have noticed right off the bat is that the keyboard does not light up, which I am assuming is because the necessary drivers obviously were not in place for the Razr. With this being said, I would thikn CM7 as well as other Razr roms WILL work with our phones. I'm glad we have at least something now.....
His link on XDA is here
**Bluetooth causes a reboot***
But hey, we're getting closer!!!
I also flashed the Eclipse ROM for the Razr and that is working well also. Just follow the directions on skipping the Android initial setup.
reigndropz said:
I been obsessed lately, trying to find something that works with our new D4's. I flashed Arctic's VZW rom after rooting my phone and....it works! I have tested SMS/MMS, GPS and phone calls with no issue. The only think that i have noticed right off the bat is that the keyboard does not light up, which I am assuming is because the necessary drivers obviously were not in place for the Razr. With this being said, I would thikn CM7 as well as other Razr roms WILL work with our phones. I'm glad we have at least something now.....
His link on XDA is here
Click to expand...
Click to collapse
If its anything like using the VZW 6.11.748 Razr Roms on 6.12.173 Razr then I believe enabling bluetooth will cause a reboot. Could you try that?
Also I am working with someone to bring Arctic to 2.3.6... it sounds like it would probably work better on D4 too.
You are 100% correct. Bluetooth causes a reboot. Seems to be a common problem. I am looking into it still and I edited my OP
reigndropz said:
You are 100% correct. Bluetooth causes a reboot. Seems to be a common problem. I am looking into it still and I edited my OP
Click to expand...
Click to collapse
This is because 2.3.6 introduced a new bluetooth, but the Rom is based on 2.3.5 that's why it won't work.
I am very interested in how this works out. The new EclipseRom and IC3Razr may work on it too... I will be trying them when I get my Droid 4 tomorrow (I hope)
mattlgroff said:
This is because 2.3.6 introduced a new bluetooth, but the Rom is based on 2.3.5 that's why it won't work.
I am very interested in how this works out. The new EclipseRom and IC3Razr may work on it too... I will be trying them when I get my Droid 4 tomorrow (I hope)
Click to expand...
Click to collapse
Great man....thanks for trying. I been racking my brain doin this. I have extracted the orginal bluetooth apk from our devices and am trying to reimplement it but im running into issues. I believe that will solve the issue.
have any pics of your phone running this ROM? i dont want to do any major modding of my phone until the sbfs have been released/leaked
If you're that worried I would wait unti something comes along more comfortable for you. For screenshots click the link in post 1. Its the same...
Could you post a video of ypur phone running the rom
Sent Via My Shiny New Droid4!
CreepyE said:
Could you post a video of ypur phone running the rom
Sent Via My Shiny New Droid4!
Click to expand...
Click to collapse
No I can't because thats the only device I have to take video
I understand people being hesitant in trying this out but I would not waste anyone's time making up a lie that it works just to have people mess up their phone. I'm not an official dev but I am telling you it works. Whether anyone tries it, is on them. I'm only trying to help get our development for the D4 working. I am using Eclipse right now also, without issue.
reigndropz said:
No I can't because thats the only device I have to take video
I understand people being hesitant in trying this out but I would not waste anyone's time making up a lie that it works just to have people mess up their phone. I'm not an official dev but I am telling you it works. Whether anyone tries it, is on them. I'm only trying to help get our development for the D4 working. I am using Eclipse right now also, without issue.
Click to expand...
Click to collapse
Backlit keyboard working?
now for an ICS ROM to start working on the Droid 4
mattlgroff said:
Backlit keyboard working?
Click to expand...
Click to collapse
No sir...I dont think until we get one specifically for our D4 are we gonna see that. It should just be a matter of a system file from our dump and throwin it in whatever rom we're using. The reason the Razr roms are working is because the hardware is identical with the exception of the display. The issues we are having with Bluetooth, Market and some other apps has nothing to do with the hardware of our devices. It's because most of the Razr roms were not created with the latest OS update , which all of the D4 owners have. My knowledge is limited with dev'ing but if anyone else wants to chime in on this, please feel fee....
reigndropz said:
No sir...I dont think until we get one specifically for our D4 are we gonna see that. It should just be a matter of a system file from our dump and throwin it in whatever rom we're using. The reason the Razr roms are working is because the hardware is identical with the exception of the display. The issues we are having with Bluetooth, Market and some other apps has nothing to do with the hardware of our devices. It's because most of the Razr roms were not created with the latest OS update , which all of the D4 owners have. My knowledge is limited with dev'ing but if anyone else wants to chime in on this, please feel fee....
Click to expand...
Click to collapse
I believe I found the file. I am going to try implementing it into the beta-build of Arctic for Droid 4. "lights.spyder.co" to "lights.maserati.co" sounds legit lol.
I fixed bluetooth today. Market will think you are on a Razr until I get the build.prop out for ya too.
mattlgroff said:
I believe I found the file. I am going to try implementing it into the beta-build of Arctic for Droid 4. "lights.spyder.co" to "lights.maserati.co" sounds legit lol.
I fixed bluetooth today. Market will think you are on a Razr until I get the build.prop out for ya too.
Click to expand...
Click to collapse
That sounds right....awesome bro!
I think its really important when you are working without the safety net of a full XML.zip restore file, that you make it very clear with extremely dire warnings that nobody should use these ROMs until there is a way to recover properly. Average users should NOT attempt this under any circumstances and by posting about it here, you need to be responsible because you will create a wave of bricked devices. This has already started, if you note the post in the main forum briteyes has bricked her phone loading this ROM.
I know this is a very unpopular opinion, but somebody has to come out and say it, sorry.
cellzealot said:
I think its really important when you are working without the safety net of a full XML.zip restore file, that you make it very clear with extremely dire warnings that nobody should use these ROMs until there is a way to recover properly. Average users should NOT attempt this under any circumstances and by posting about it here, you need to be responsible because you will create a wave of bricked devices. This has already started, if you note the post in the main forum briteyes has bricked her phone loading this ROM.
I know this is a very unpopular opinion, but somebody has to come out and say it, sorry.
Click to expand...
Click to collapse
Very wise words cellzealot. I've seen to many people messing up their phones right now and not all of them were rom related, removed to much while getting rid of bloatware.
I'm holding off even rooting mine until there is rsd recovery files as a backup before I take the plunge. I know the rooting part is safe, just don't feel like unlocking the gates of trouble without a backup plan.
If it wasn't for people testing the limits, development would be a much slower process. I was one of the first to use the root, toy with freezing bloatware and test a bunch of the root-required apps. It is obvious that ROM flashing is a risky process, even with a restore, but that doesn't mean that it shouldn't be done.
I am also amused by how many people have said "I don't want to root until..." since the root has been entirely stable since day 1. If you can't trust yourself to be responsible with the root abilities, why even bother posting right now when everything is in the alpha stages for this phone since it came out less than 2 weeks ago.
This is the DEVELOPMENT forum... testing and risk are implied for anything that gets posted here.
zombie673 said:
If it wasn't for people testing the limits, development would be a much slower process. I was one of the first to use the root, toy with freezing bloatware and test a bunch of the root-required apps. It is obvious that ROM flashing is a risky process, even with a restore, but that doesn't mean that it shouldn't be done.
I am also amused by how many people have said "I don't want to root until..." since the root has been entirely stable since day 1. If you can't trust yourself to be responsible with the root abilities, why even bother posting right now when everything is in the alpha stages for this phone since it came out less than 2 weeks ago.
This is the DEVELOPMENT forum... testing and risk are implied for anything that gets posted here.
Click to expand...
Click to collapse
The root is stable, but the people rooting are NOT.
You see the posts of people deleting their own /system/apps/ folder?
CellZealot is very right in what he saying and it did have to be said. Without fastboot files and heck even without a factory-style cable it is not safe to be a crack flasher on this device.
zombie673 said:
If it wasn't for people testing the limits, development would be a much slower process. I was one of the first to use the root, toy with freezing bloatware and test a bunch of the root-required apps. It is obvious that ROM flashing is a risky process, even with a restore, but that doesn't mean that it shouldn't be done.
I am also amused by how many people have said "I don't want to root until..." since the root has been entirely stable since day 1. If you can't trust yourself to be responsible with the root abilities, why even bother posting right now when everything is in the alpha stages for this phone since it came out less than 2 weeks ago.
This is the DEVELOPMENT forum... testing and risk are implied for anything that gets posted here.
Click to expand...
Click to collapse
People are never happy..... like you said it's a developmental forum. If they aren't somewhat knowledgeable with flashing roms or how the process works, they should read up before saying anything at all. This is all free and people put hard work into developing things. If you want a disclaimer, go to Best Buy.
now that we have safe strap i am getting bold.. about to flash over eclipse 1.3 and see what happens... hoping for the best!
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
Hey all I'm curious and wanting to learn how to port roms for this device and could use some guidance. My goal if possible would be a fully stock rooted , no bells and whistles and odex GPE port for this device. If anyone could help me get started or give some feedback it would be appreciated. I've built roms from source in the past but never have I attempted a port.
@Captain_Throwback @digitalhigh
tuxattack80 said:
Hey all I'm curious and wanting to learn how to port roms for this device and could use some guidance. My goal if possible would be a fully stock rooted , no bells and whistles and odex GPE port for this device. If anyone could help me get started or give some feedback it would be appreciated. I've built roms from source in the past but never have I attempted a port.
Click to expand...
Click to collapse
I'm not sure what you mean by odex, since Lollipop isn't structured the same as previous Android versions. I don't think you'll be doing any odexing, lol.
I could probably port it in the time it'll take me to explain this, it's literally that simple (except I understand you want to learn this, though I'm really in a more of a didactic mood). So I apologize ahead of time if I'm not very thorough here.
If you look at my GPE port, it's basically exactly what you're trying to do. The most basic things that need to be changed are framework-res.apk and build.prop. I think it may be as simple as dragging and dropping pre-compiled, working APNs and eri.xml from a working framework into the Lollipop framework with 7-zip (or Archive Manager, in Ubuntu) and changing the default telephony mode in build.prop to 8 so the modes show up properly. I think that's literally all you need for it to function.
I added some other lines from the stock build.prop but I'm 90% sure they're not even needed.
Captain_Throwback said:
I'm not sure what you mean by odex, since Lollipop isn't structured the same as previous Android versions. I don't think you'll be doing any odexing, lol.
I could probably port it in the time it'll take me to explain this, it's literally that simple (except I understand you want to learn this, though I'm really in a more of a didactic mood). So I apologize ahead of time if I'm not very thorough here.
If you look at my GPE port, it's basically exactly what you're trying to do. The most basic things that need to be changed are framework-res.apk and build.prop. I think it may be as simple as dragging and dropping pre-compiled, working APNs and eri.xml from a working framework into the Lollipop framework with 7-zip (or Archive Manager, in Ubuntu) and changing the default telephony mode in build.prop to 8 so the modes show up properly. I think that's literally all you need for it to function.
I added some other lines from the stock build.prop but I'm 90% sure they're not even needed.
Click to expand...
Click to collapse
I appreciate the info and help. I'm always up for learning when it comes to dev work, in all honesty I feel that it should be a requirement at times. I know when I was building and piecing together roms for my LG optimus G I gained a better sense of what's involved and how much time is invented. It's not just something you build in a second and you're done. Although some end-users feel that it's as easy as flipping a switch. I'll look into this more when I get home tonight. Thanks again for the helping hand.
tuxattack80 said:
I appreciate the info and help. I'm always up for learning when it comes to dev work, in all honesty I feel that it should be a requirement at times. I know when I was building and piecing together roms for my LG optimus G I gained a better sense of what's involved and how much time is invented. It's not just something you build in a second and you're done. Although some end-users feel that it's as easy as flipping a switch. I'll look into this more when I get home tonight. Thanks again for the helping hand.
Click to expand...
Click to collapse
I realize I missed some stuff, actually. There are two lines in build.prop. And then there's /system/etc/gps.conf which shou;d come from stock as well.
Finally, you need a boot.img that'll actually boot on the Sprint variant, which I built from source, but you could just as easily just use the one from 4.4.4 and it would work too.
Since I said it would only take a few minutes, I downloaded @graffixnyc's stock rooted and quick-ported it using the changes I just mentioned. I'll shoot it over to you and you can diff it from his original release to see what changes were made.
Captain_Throwback said:
I realize I missed some stuff, actually. There are two lines in build.prop. And then there's /system/etc/gps.conf which shou;d come from stock as well.
Finally, you need a boot.img that'll actually boot on the Sprint variant, which I built from source, but you could just as easily just use the one from 4.4.4 and it would work too.
Since I said it would only take a few minutes, I downloaded @graffixnyc's stock rooted and quick-ported it using the changes I just mentioned. I'll shoot it over to you and you can diff it from his original release to see what changes were made.
Click to expand...
Click to collapse
Awesome!! I'd greatly appreciate that, be a little easier to break down and see that way and may also keep me from buying a new device right before Christmas lol!!
tuxattack80 said:
Awesome!! I'd greatly appreciate that, be a little easier to break down and see that way and may also keep me from buying a new device right before Christmas lol!!
Click to expand...
Click to collapse
You do know there's a GPE ROM that's Sprint compatible already available, though, right?
Captain_Throwback said:
You do know there's a GPE ROM that's Sprint compatible already available, though, right?
Click to expand...
Click to collapse
Yeah I've been trying out DH's build and your 4.4.4 beyond stock build a lot lately but still wanting to get my hands dirty and figured a pure vanilla build would be a good place to start(far from a programmer and some of the init.d's confuse me lol). Nothing against his build or yours at all just curious on how things work.
tuxattack80 said:
Yeah I've been trying out DH's build and your 4.4.4 beyond stock build a lot lately but still wanting to get my hands dirty and figured a pure vanilla build would be a good place to start(far from a programmer and some of the init.d's confuse me lol). Nothing against his build or yours at all just curious on how things work.
Click to expand...
Click to collapse
I wouldn't even really call the GPE ROM a port because it'll boot up just by swapping out the dtb. Getting data just requires having it set to the right network mode and to use the CDMA Network Settings, and add in the proper APN entry. Then to fix the Carrier name that displays, swapping in a proper ERI file. Any other tweaks are just bonus.
A real port is from one device to another. Since the hardware on all the M8 variants is the same, there isn't much work to really do. It's actually harder to port an International-based Sense ROM to Sprint than it is to port GPE.
I'll PM you the link when the upload is complete. I was able to successfully boot my port and get data, so I know it's working as it is now. The only thing I always have an issue with is Sprint Voicemail. It never works properly on non-Sense ROMs.
I'm not sure if it's just a D415/410/405 thing or if it's a KitKat to Lollipop thing. I'm not new to rooting, flashing, and customizing, but I'm in no way a dev either, so I was wondering why so many ROMs for our phone need a KK baseband? Alternatively, if I'm already on a debloated but otherwise stock LP ROM do I need to downgrade to the KK baseband first or can I flash over?
Note: the last time I was playing around with flashing ROMs was on a Galaxy Exhibit II 4G and I bumped it up from 2.3.6 to 4.4.2 without having to play with basebands. This is why the confusion.
Thanks in advance for any advice and answers.
I guess because no one really is maintaining LG L90 device sources.
For a log time there was Quarx but his device got broken so he's not really developing it anymore. He's only compiling CM12.1 from sources but I'm pretty sure it's all done by computer, fully automatically. After Quarx there was BigMajster who if I'm not wrong was the first one to introduced L90 owners to Lollipop. He was a great bug-hunter and he published a lot of great fixes for different L90 variants. If I'm not mistaken he was the one who fixed Double-tap-to-wake feature and storage 190MB bug for D415. He was a great developer until he disappeared somewhere in January I think. One day he was gone without saying anything. For some time I thought that something happened to him but after a little research I found out his real name and that he's pretty much alive and well. I didn't contact him though. I thought that if he left the way he did there was no point.
Other developers (I will not mention any names) are no really maintaining device sources. Most of them are just busy with their ROMs they are developing. The same bugs are present in all customROMs and no one is working to fix them. After months there is still no stable kernel for custom Lollipop, even though almost all of the current developing projects are based on Lollipop. Getting developers to work together, also didn't worked out. I probably forgot about some others important developers that are not with us anymore so sorry if I skipped anyone.
To be exactly clear. I don't make any accusations nor complaining. I just share my opinion with you, saying how I see things around here. I tried to state only facts, without my personal opinions but you should consider this whole statement as one.
A well thought out and thorough answer. Thank you for that. Any input on if I can flash from a stock LP base band or would I have to downgrade? That's about the only thing that makes me nervous and preventing me from trying 5.1.1 despite the random FCs
If you're on stock Lollipop and want to try CustomROM. Then you will have to downgrade to KitKat using KDZ or install bootstack.
Sent from my LG-D405 using XDA Free mobile app
@Xemidra
Keep in mind that NOONE of you pays us. You have no idea what we're doing on the source.
Quarx started with the device tree, kernel and vendor, so we don't know all what he did and how he did. We are working all or going to school(?), so we don't have so much time to rebase everything.
Also porting a Lollipop kernel from LGE source needs plenty much time.
In addition there is no "General source" to work on and maintain. All in all it's pretty cheeky to say something like we're doing nothing.
GrinningFerret said:
@Xemidra
Keep in mind that NOONE of you pays us. You have no idea what we're doing on the source.
Quarx started with the device tree, kernel and vendor, so we don't know all what he did and how he did. We are working all or going to school(?), so we don't have so much time to rebase everything.
Also porting a Lollipop kernel from LGE source needs plenty much time.
In addition there is no "General source" to work on and maintain. All in all it's pretty cheeky to say something like we're doing nothing.
Click to expand...
Click to collapse
Well, like I said it's was my opinion. That's how I see things around here.
I didn't mean any disrespect. I know that you don't get paid for your work so I don't have any right demanding anything from you and I don't but you also can't say that the current situation is a result of devs not getting paid.
I also put some work time into L90. I did made available all KDZ for Lollipop and some for KitKat. I made different versions of BOOTSTACKs and I made FlashableSTOCK. All that take a lot of my time, energy and also my internet connection, power supply etc. No one paid me for it. I basically paid for it from my own pocket. I'm not complaining. It's just how it is.
You can't get mad because someone did something not the way you wanted him to do while he did it for free.
At the same time you can't be mad at the current situation and say it's because someone didn't pay you to make it better.
That's my opinion.
@Xemidra
The problem isn't that we don't get paid for it - its' our hobby. But the point is that you're telling around that we do nothing on the device source, which is just wrong.
GrinningFerret said:
@Xemidra
The problem isn't that we don't get paid for it - its' our hobby. But the point is that you're telling around that we do nothing on the device source, which is just wrong.
Click to expand...
Click to collapse
I might have been wrong about the input in device sources.
Good you've stepped up and corrected me.
Sorry for the misunderstanding.
@Xemidra
Nevermind.
Sorry if this ruffled any feathers, guys. This was meant more to be an end user wanting to understand the dev and background process to be able to contribute and help more than a spirited discussion about who does what.
In any case, I thank you both for the information and the input. In the end I do understand a bit more.
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