Hello XDA people,
Since I9500 launched, developers were little afraid to pick it up for development because of Samsung Exynos' isolated documentation. (I hate Samsung for that)
Then, Ethan Chen (@intervigilium) decided to accept the challenge and port CM for I9500.. He did well. He ported almost everything (except camera and some Bluetooth related content). InSignal released partial SoC documentation at the right time and yesterday they released gralloc header. That made development easier.. I hope we will see bug free CM build in upcoming weeks.
Ok, enough CM.
I always have been quite interested in MIUI. The way they built their own framework on the top of barebone android framework was impressive. MIUI is one of the best and buttery smooth ROM ever I have used.
I bought I9500 on the very first day of it's launch in India.. The very next day, I asked one question in MIUI forums, will it ever be launched for this device? Being Exynos powered device, I knew developers would hardly build it for this device.
Then again, unexpected things happened. Official team have decided to port it for this device.. But I know it will take long. Voting is still going on. But before that, I want to use my experience and skills to port MIUI on our beloved device.
I have started working on it. I will not publish anything on github yet. I will have to make sure that the experiment I am working on will work. But I will update you all with the progress here.
Some facts :
1. No, it will not be dependent on CM source as of now. I will port it on top of Samsung stock ROM (result, better stability and fully working features).
2. I will remove the TouchWiz layer. Not only the UI part but almost every library, classes (smali) and libs based on TouchWiz.
3. Add compiled MIUI classes and resources.
I will be tweeting (and later blogging after I set up my domain and workspace) updates and progress on my twitter account..
@rahulzeven
@Moderators : I hope I am allowed to open thread for Port discussions..
Thanks for your initiative.
All the best.
I think this is good for exynos, and using samsung base have less bugs.
Sent from my GT-I9500 using xda app-developers app
Great
Subscribed
Sent From my i9500 With ☆★Crash Rom★☆
yeap. That's Great.
you said asked in MIUI forums. Do you know Chinese?
I heard that the most experienced engineer in Xiaomi will take over the job porting MIUI v5 for S4.
Great Work Rahul!
I would love to have MIUI on S4 Octa
jiant.li said:
yeap. That's Great.
you said asked in MIUI forums. Do you know Chinese?
I heard that the most experienced engineer in Xiaomi will take over the job porting MIUI v5 for S4.
Click to expand...
Click to collapse
Nope, they have English forum too
Subacribed...
Thanks for tye devs who support i9500 and bringing goodnews to us!
Sent from my Nokia 3210 LTE
How many of you really want specific SGS4 features? Like Air View, Smart Pause, Smart Stay blah blah?
Rahulrulez said:
How many of you really want specific SGS4 features? Like Air View, Smart Pause, Smart Stay blah blah?
Click to expand...
Click to collapse
First of all I would like to thank you for this.
I do not want any Specific SGS4 feature. Keep it as true to MIUI as you can
Rahulrulez said:
How many of you really want specific SGS4 features? Like Air View, Smart Pause, Smart Stay blah blah?
Click to expand...
Click to collapse
I don't use any of Samsung Features
I only try them once
Only IR Blaster Important For Me
Sent From my i9500 With ☆★Crash Rom★☆
AL_IRAQI said:
I don't use any of Samsung Features
I only try them once
Only IR Blaster Important For Me
Sent From my i9500 With ☆★Crash Rom★☆
Click to expand...
Click to collapse
IR Blaster is what I use a lot probably the only useful feature I've found.
THANX!!!
Will be great!
What a man!:good::good:
Rahulrulez said:
How many of you really want specific SGS4 features? Like Air View, Smart Pause, Smart Stay blah blah?
Click to expand...
Click to collapse
Air View and Smart stay would be great
Cool. Follow me up with requests on my Twitter I am more active there Handle in my signature.. Can't access XDA more at my workplace
Rahulrulez said:
How many of you really want specific SGS4 features? Like Air View, Smart Pause, Smart Stay blah blah?
Click to expand...
Click to collapse
Miui + s4 features = superb miui rom..
To those who dont like these features you can turn it off
Great to see those features on MIUI rom
Sent from my Nokia 3210 LTE
None of that is important. I guess I speak for about 95% of users!
@Rahulrulez how was it ? any updates ? just want to know and read
ChampMEon said:
None of that is important. I guess I speak for about 95% of users!
Click to expand...
Click to collapse
Lol.. too exagerated for 95%...
Sent from my Nokia 3210 LTE
Let's see... I will focus on Samsung Feature less base first.. Then will port Samsung stuff on top of that..
http://www.androidauthority.com/android-5-0-lollipop-source-code-563560/
Well what do we have here, Android Lollipop being uploaded to AOSP as we speak! As you can imagine, a code dump like this takes a great deal of time, and it could be hours before everything is completed. At the moment, the branch is being referred to as “lollipop-release” and it carries a build number of LRX21M, though its official release tag should be android-5.0_r1 when it ‘fully hits’.
Even more exciting, it’s also only a matter of time before device-specific repositories for all Nexus hardware shows up, and at least a few have already surfaced including the Nexus 7 (2013) LTE ‘deb’ and Nexus 7 (2013) Wifi ‘flo’. It is worth noting that a new repository for Android TV is also available now, though it is hard to say whether or not the full code will be uploaded.
Once everything is uploaded, it’ll only be a matter of time before developers and many others begin playing around, bringing us hidden goodies and so much more. And before you ask, no the Nexus factory images are not up yet. Patience my friends, all in good time.
Click to expand...
Click to collapse
Its been published.
Sent from my Xperia L using XDA Free mobile app
The last time i checked, Lollipop source was still pushed but still it hadn't had key files to compile it for any device like manifest etc. It was giving an error. These files usually take few hours.
And the source code being published is for Nexus 7 , 5, 6 and 9.
There still wasn't anything for Nexus 4 or 10 or any other device.
However few sites cited that the manufacturers were handed the source to Lollipop and they were working on it as well.
I'm not sure how much time it would take to make their sources public.
As for Xperia L, I can't say when exactly but I'd say roughly about one to two months before any development is to be seen. The nexus 7 and 5 still haven't got OTA or Nexus Factory Images yet as I'm watching it closely.
Sony is surely not releasing lollipop for L so we would just have to wait for Aosp and Cyanogen to combine few lollipop sources to current device tree to give you somewhat of Android L which our device is capable of.
I hope this information be enough for now
Update
Source code is now complete. You can compile it for the above mentioned nexus devices. Still No official OTA or nexus factory images.
Little update :
Nexus Media Player and Nexus 9 Factory Images have been pushed. Still nothing for Nexus 7 or 5. Neither for Nexus 6.
Although source code have been pushed but I don't see any binaries yet for any Nexus devices which means that custom ROMs are still not possible. Although if you try to compile a custom ROM, you'd have glitches/problems due to missing binaries.
What this means is that unless Qualcomm doesn't release binaries for it's Snapdragon processors, we won't be able to get a ROM fully stable.
We can get some features to be merged in our device tree but I am not sure how lollipop would work perfectly without binaries/blobs.
Last time, I remember the graphics glitch was sorted partially by using Xperia Z blobs but still it didn't was as affective as it could be if it was for Xperia L itself.
What Xperia L need is binaries from Qualcomm and source code from Sony for Lollipop.
Let's hope for the best
Update 2
It is now rumored that update for the remainder of Nexus devices would come on 12th Nov as Google found some last minute bugs and wants to send of more polished and refined bug free android L.
For Xperia L, you can only wait for binaries from Qualcomm and source code from Sony.
source code published
source code published
So currently I am on Cyanogen Mod 12.1 AOSP. I have recenlty come across the CAF version. After some research I found it is better optimised? Can you explain what it means by that and how is it better optimised? Aprrenlty there are also more features? So should II change from AOSP to CAF?
dec1153 said:
So currently I am on Cyanogen Mod 12.1 AOSP. I have recenlty come across the CAF version. After some research I found it is better optimised? Can you explain what it means by that and how is it better optimised? Aprrenlty there are also more features? So should II change from AOSP to CAF?
Click to expand...
Click to collapse
OK so CAF stands for Code Aurora Forrums,
These are Qualcomm's reference sources for their platform. This is what they provide to OEMs, and what nearly all OEMs base their software off of. As a result - nearly all non-Nexus devices are running kernels/display HALs/etc. that are derived from a CAF baseline.
Google's software baseline, or AOSP - Usually when Google starts working on a new Android version, they'll fork from CAF at the beginning. Very often Google will be adding "new" features specific to the new Android version, while Qualcomm will continue with performance enhancements and bugfixes against the "old" baseline.
So when a new Android revision comes out, you have two baselines: CAF which is usually "ahead" in performance but "behind" in features, and AOSP which is the opposite.
Starting with 4.3, CM started mixing code between CAF and AOSP. They put some CAF features/capabilities into their baselines for AOSP-supported devices (Nexus devices), and started putting AOSP patches into their baselines for CAF device
Sent from my Nexus 6 using Tapatalk
Thank you. I heard there are features like live display on the CAF version. Is that true?
Hello,
I have been a nexus device user, but since google only produces pixel devices I am thinking about other smartphones.
The Samsung Galaxy S7 seems pretty nice, but I would like to get the new android version pretty fast .
Android is open source, so how difficult is it to make out of the stock android source code a rom for the S7.
I don't need all the Cyanogenmod Features.
To myself: I think I am quite good in java, but I am not a professional. It is just a hobby
How difficult and how much time would I need to make such a rom.
Supporting device specific features like the curved screen from the S7 Egde or a pen from a samsung galaxy note would be much more difficult or can I use source code from Samsung/XDA-Developers.
When I would use the Stock Android, how difficult would it be to install the monthly security updates?
Thanks a lot
p4
``
Samsung software is too hard to bypass, so even Google experience-based ROMs still run on top of Samsung software. Also, Samsung's hardware relays on the software optimisations. This way, no custom ROM can take profit of the hardware features
Sorry for late reply heres the link
https://forum.xda-developers.com/ga...ce-plus-s8-t4001385/post80857251#post80857251