Database Info

[Q] JB MIUI For Galaxy S 4G

Hey guys, I have been looking for a jb miui ROM for this device and i cant find one, i know there are some ics miui ROMs, but i would really like a jb miui ROM.
There is one for the vibrant, can I use it for my Galaxy s 4G or can anyone port it to our device?
Vibrant MIUI JB ROM:
http://forum.xda-developers.com/showthread.php?t=2289234
Thanks

i'll build it when miui comes out with miui 4.2

airfluip1 said:
i'll build it when miui comes out with miui 4.2
Click to expand...
Click to collapse
Thank you i will be looking forward to it.

Beast said he would do it.
sent from me

that's been in my queue for a while along with aokp aries and paranoid android.

airfluip1 said:
i'll build it when miui comes out with miui 4.2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2313073

Just because there are some homebrew ports doesn't mean that MIUI is 4.2 yet.
http://en.miui.com/download.html
Official Downloads
Author : MIUI Developer Team
Kernel : Android 4.1
Latest update : 3.6.21
Download : http://www.miui.com/download.html
Language : Chinese and English
Click to expand...
Click to collapse

Why does it matter ? We use unofficial ROMs anyway...
sent from me

That's like saying that since a car, airplane, and weed-whacker all run on gas, you should just put the same stuff in each. Actually, the unofficial ROMS is a more tenuous connection than my gas connection. It's more like saying that since a bullet train, horse, and diesel bus all run on fuel, the fuel which goes into each shouldn't matter. It's all fuel.
Hey, you could (please don't) use an unofficial Vibrant ROM too. That's unofficial. What's the difference? The difference is that it won't work. And might brick your phone. That's bad.
Our only current Aries kernel is 4.2.2 and still has issues. MIUI is still 4.1.2 and would introduce an entirely new set of issues tied into GPS, Bluetooth, and so forth if/when a 4.1.2 Aries kernel was compiled. Does that make it impossible? No. But it means that as the build impetus - when MIUI is 4.2 - has not happened yet... it's not a great use of time yet. Unless one of the devs wants it. In which case, MIUI being not-updated is something they don't need to be hammered over the head with.

http://forum.xda-developers.com/showthread.php?t=2313073
4.2.2?

Port. If YOU see source linked from that page so our devs could actually do something useful to build that...

Hi Theraze
I have to disagree with you.
Port is not a dirty word and most of our ROMs are actually ports and not built from source. Furthermore, MIUI ROM is usually ported and not built from source and only recently did Xiaomi open their sources for the public. Even more than that, both MIUI versions brought to us by Beast were ports from Nexus and not built from source.
Now, regarding the incompatibility between kernel & OS - if it works on Nexus, I assume the adjustments were made, so one can enjoy both 4.2.2 & MIUI benefits. There is no logical reason why it couldn't be ported to our beloved device.
sent from me

I'm not saying it can't be done. I'm saying that our build-from-source dev who asked you to let him know when it hit 4.2 hasn't had his request met.
Does that mean that someone (him or another dev) CAN'T port it? Nope. But it makes it a lot less likely that air can just pull the source in and compile it using the Aries bits if the buildable MIUI is still only 4.1.2 and our Aries is 4.2.2 instead.
Again, I think we're agreeing on the general bits... yes, this is possible. But airfluip1 asked to be notified when buildable MIUI was 4.2.2 and that's when he said he'd build it. Not port it.

I don't care if a ROM is ported or built from source.
I will try to play with porting it myself.

[Q] Obstruction in 4.3, 4.4 and 4.x development

Hi,
Without having any (ROM) development skills I have tried to copy/port/compile a Android 4.4 ROM myself. I did not succeed but in the process I have learned a lot in general about ROM development. I'm not aspiring to be a ROM developer, but at this moment I am eager to know what exactly are the bottlenecks in creating a 4.3 or 4.4 ROM.
I have copied, dissected and altered the work of the guys who have 4.4 (partially) running on HTC Desire HD and HTC Incredible S. To my knowledge these devices have a lot in common (for the most part) and, in my mind, should work on SAGA with some tweaks (ACE -> SAGA / VIVO -> SAGA). Replacing text is off course a simplification, but hey, besides the camera, it is almost the same hardware. I guess there is more to it, because I tried several times, but did not get it to work.
I do not expect to solve these issues, but I wonder what holds the (stable) development of a 4.3 or 4.4 ROM. Outdated source code of drivers or kernel or ....
I was thinking of contacting some of the DEVS who are working on the 4.4 ACE and VIVO ports, but I hope someone on this forum can enlighten me.
Regards,
Michael

Ace and Vivo are indeed closest models to saga and very similar,..when ported to saga,
the roms seems ussualy faster,lighter,cleaner, much less bugy than those, ported (especially directly) from other devices,
.. What- most possibly holds the development for this device is the kernel (or its absence)-as often,..
very likely,-when there was a possibility to boot the port, without jumping also, to self porting/modding its kernel,
we would have seen yet quite a few stable KitKat ports,..
Kernel devs for desire s were briliant- but never many,
now, only @kylon remains active- pardon me if i`m not correct ,,

Request for Collaborators: Merging the CM11 ROMs into one "official" one

Hi,
I see at least 3 different CM11 roms based on kitkat:
* http://forum.xda-developers.com/showthread.php?t=2524961 [ROM] CyanogenMod 11.0 | Android 4.4.2 KitKat [KANG] [May-6]+[NIGHTLIES]
* http://forum.xda-developers.com/showthread.php?t=2530073 [ROM][STABLE][Android 4.4.4] CyanogenMod 11 with 3.0.16 kernel [July 25, 2014]
* http://forum.xda-developers.com/showthread.php?t=2692278 [UnORom][3.4Kernel] CM-11 Android 4.4.4 [Stable v2.0][29 July][Final]
All more or less unmaintained as far as I can see - please correct me if I'm wrong!
What are the remaining difficulties to get a official CM11 ROM out of these? Then a lot more infrastructure from CM could be used - e.g. development tools, build machines & downloads. If the problem is to get a build machine on which 3-5 persons could would together over the Internet - I'll spend a vserver on my own dedicated server if there is a serious effort to bring up an official CM11 ROM.
If there are rather tiny things I could try(!) to help - I have almost no experience with android system development, but with Linux and development (C, Java, embedded devices,...) in general.
Two links for the rough procedure:
* http://wiki.cyanogenmod.org/w/Doc:_porting_intro - the hard part, but luckily almost done (isn't it?)
* http://wiki.cyanogenmod.org/w/Doc:_Submitting_A_Port - the final
Wiki-entry: http://wiki.cyanogenmod.org/w/Pyramid_Info

+1 for uptodate pure CM11 rom for sensation. I hope someone will join to you.

I think Flemmard's variant of CM is ready to be official!

official CM11 to Sensation!!!! We need it

+1

+1 It would be great thing for senny to so see official CM11 because many developers left us.

I don't think it's possible to make an official CM11 for our phone. IIRC, to be official it can't use legacy drivers and for the CM11 to work on our phone, I think we are using drivers from ICS because that's until where our drivers are updated, I'm not sure.
And "official" one in other hand would be amazing, I tried PA and etc but I always return to CM.

scanferr said:
I don't think it's possible to make an official CM11 for our phone. IIRC, to be official it can't use legacy drivers and for the CM11 to work on our phone, I think we are using drivers from ICS because that's until where our drivers are updated, I'm not sure.
And "official" one in other hand would be amazing, I tried PA and etc but I always return to CM.
Click to expand...
Click to collapse
Flemmards CM use KK drivers.

+1 for me too.

It's good to take a question - how many developers are developing at this moment?
Albinoman moved to Galaxy S5
SultanXDA has forced to developing Nexus 5 device
Shantur give up his work and we can flash new builds only if Sajito will up new version (contains upstream changes)
Ivanich has decided to close his storage, so we cannot download anything...
...Ideas?

Inf1n1te said:
It's good to take a question - how many developers are developing at this moment?
Albinoman moved to Galaxy S5
SultanXDA has forced to developing Nexus 5 device
Shantur give up his work and we can flash new builds only if Sajito will up new version (contains upstream changes)
Ivanich has decided to close his storage, so we cannot download anything...
...Ideas?
Click to expand...
Click to collapse
That's not true... Team Venom also left us
For now we have official slimkat builds and maybe bilal liberty still develops for senny.
That's sad. We had many great developers and suddenly many of them left us. It will be great to see official CM builds.

Thats very sad, why they all leaving, i dont understand that. How's Ivanich latest 08/27 rom? Better than Sultan 07/25?
greetz

macicgangsta said:
That's not true... Team Venom also left us
For now we have official slimkat builds and maybe bilal liberty still develops for senny.
That's sad. We had many great developers and suddenly many of them left us. It will be great to see official CM builds.
Click to expand...
Click to collapse
bilal don't support our device anymore.

Inf1n1te said:
...Ideas?
Click to expand...
Click to collapse
The good thing is that all the great developers left us with good ROMs.
I think it is difficult to replace the devs. I can't fix the bugs they didn't fix until now, but I would like to try to keep at least one of the Cyanogenmod ROMs updated with upstream. I think in a month or two I will have time to start with that (if no one else is doing it until then).
@mifritscher: I think the lack of a build (or at least download-) server was a problem for devs here and then. So yes, your offer could be very helpful! Thanks for that!

Inf1n1te said:
It's good to take a question - how many developers are developing at this moment?
Albinoman moved to Galaxy S5
SultanXDA has forced to developing Nexus 5 device
Shantur give up his work and we can flash new builds only if Sajito will up new version (contains upstream changes)
Ivanich has decided to close his storage, so we cannot download anything...
...Ideas?
Click to expand...
Click to collapse
Sensation is a 3 year old device. i think as the devs have moved on to other devices, so should we. though our sensation has a lot of potential, i dont think devs will work on an android L port or making CM11 official. though there is hope with ivanich & bilal_liberty

Inf1n1te said:
It's good to take a question - how many developers are developing at this moment?
[....]
Ivanich has decided to close his storage, so we cannot download anything...
...Ideas?
Click to expand...
Click to collapse
I can give storage space and bandwidth if it's useful, please contact me to discuss the details.

I can build but i dont know how to make a device tree so if someone can do the device trees i can do the builds

I don't know if we have everything working as on stock, also I don't know if the rom would pass cts.
But even if everything works, I don't think there's anyone around who has enough time to maintain an official build.
But at this point there's only one cm which is still updated and that's ivanich's one. Where's the difference in having an official build?

Where to go from here?
I'm just a casual user looking for a ROM. Going through these threads is confusing and so many links are dead.
What available for the sensation right now?

cynamun said:
I'm just a casual user looking for a ROM. Going through these threads is confusing and so many links are dead.
What available for the sensation right now?
Click to expand...
Click to collapse
Except for official slimkat all available and maintained roms are part of DevB so just click here in forum in the dev:db bar on roms.

[Q] Cm 11 Question

Hey all! I'm looking for a CM rom that works with PAD (Puzzle and Dragons). On a lot of the CM roms, PAD has an infinite download loop, which is a deal breaker for me. If you could give me the name of the rom and the kernel you're using, that would be greatly appreciated! Thank you all for your time!

If it doesn't work on cm, or a bunch of cm based roms....seems pretty clear it's just not compatible with cm....And likely that will be the same for all cm based roms.

P&D stopped working after the M10 snapshot which was released back in September (16). There were some notable major framework changes, and I believe these are what lead the app to stop working/cause the infinite download loop.
http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m10-arrives
The only workaround known at this time is to install a version older than that date.

What stops the developer of a ROM like LiquidSmooth from basing the ROM off GPE ?

I know LiquidSmooth is based on Slim, which I believe is based on AOSP source. Either Slim is ported to our phone and Liquid is built on top of it, or Liquid, based on Slim, is ported to our phone (or they're both the same thing). Well, what stops someone who can take Slim and make it into LiquidSmooth, from basing it off of GPE instead?
Come to think of it, I've only seen ROMs based on GPE offer a couple tweaks. Nothing as extensive as something like LiquidSmooth. Can a GPE not be modified as extensively? Isn't it required to have its source posted due to the GPL or something?

dragontology said:
I know LiquidSmooth is based on Slim, which I believe is based on AOSP source. Either Slim is ported to our phone and Liquid is built on top of it, or Liquid, based on Slim, is ported to our phone (or they're both the same thing). Well, what stops someone who can take Slim and make it into LiquidSmooth, from basing it off of GPE instead?
Come to think of it, I've only seen ROMs based on GPE offer a couple tweaks. Nothing as extensive as something like LiquidSmooth. Can a GPE not be modified as extensively? Isn't it required to have its source posted due to the GPL or something?
Click to expand...
Click to collapse
GPE isn't aosp, it's Google play edition software. It isn't open sourced to be built off of. Think of it as more of a Sense or touchwiz interface than AOSP build. A GPE rom is built specific for each device it's operating on.
A GPE rom written for an HTC m8 will not work on a samsung galaxy s5, simply because the kernels are different. AOSP roms have the same kernel for all devices. That's mainly what would keep a developer from basing a rom off of a GPE code.
Slim is built AOSP source code, along with many other roms. Liquid chooses to use slimroms as a base, but it could choose to use CM, AOKP, or another AOSP base of their choosing. This doesn't apply to GPE.
GPE roms can be modified to do whatever the developer wants them to do. However, the whole point of GPE roms is to have a very fast, debloated close to stock experience. People looking for GPE roms aren't really looking for all the bells and whistles that go with highly modified stock or aosp roms.

Whoa... There is no such thing as a ROM that will run on both an HTC One M8 and a Samsung Galaxy S5. That isn't a valid limitation of GPE. Kernels are always device specific, too. You might get a universal kernel that works across variants of one phone, but I've never heard of a kernel, an aftermarket one anyway, that will run on devices across manufacturer lines. Then again, I don't follow kernels as closely as I have ROMs.
GPE isn't open source? That's news to me. I mean, I thought all Android builds had to provide source. I mean, rule #1 of XDA is don't ask for ETAs, but I saw a moderator demand source on a ROM "sooner than later." Not naming names because I'm sure the moderator was within rights, but it seemed to at least partially contradict the spirit of the famous rule.

dragontology said:
Whoa... There is no such thing as a ROM that will run on both an HTC One M8 and a Samsung Galaxy S5. That isn't a valid limitation of GPE. Kernels are always device specific, too. You might get a universal kernel that works across variants of one phone, but I've never heard of a kernel, an aftermarket one anyway, that will run on devices across manufacturer lines. Then again, I don't follow kernels as closely as I have ROMs.
GPE isn't open source? That's news to me. I mean, I thought all Android builds had to provide source. I mean, rule #1 of XDA is don't ask for ETAs, but I saw a moderator demand source on a ROM "sooner than later." Not naming names because I'm sure the moderator was within rights, but it seemed to at least partially contradict the spirit of the famous rule.
Click to expand...
Click to collapse
Ehh, GPE may be open sourced. I think Google has to release the information for it.
AOSP though definitely isn't as specific, the kernel has to be signed for each device but it's overall much easier to port the kernel over to another device.

kernels
The Linux kernel is a monolithic kernel and all device specific drivers are compiled in the binary unless they are stand alone modules. Android itself is open source, but it does NOT use the GPL v2 licence. The code for many of the drivers and other device-specific software is closed source and only available as binaries. XDA strictly enforces providing source code for kernels because that is a strict stipulation of GPL v2. A custom ROM generally doesn't require source code since many stock-derived ROMs don't begin with source code. Sense and GPE would be varieties that don't originate from source code.