Database Develop

[REQUESTS]Porting I9300 Roms to I9305

For all Porting discussions and requests hopefully they get answered. I think soon once a Dev knows what they are doing, this will be the case he will work with all the i9300 Rom Devs and work on porting them to I9305.
Hopefully. . Lol

I'm suspecting not that hard - in fact i am now porting ... seems to have good progress =]

it wont be long when devs start to play with I9305, we just need to keep this forum active and help people like Kazuni with their rom testing

_ray_ said:
it wont be long when devs start to play with I9305, we just need to keep this forum active and help people like Kazuni with their rom testing
Click to expand...
Click to collapse
I can't guarantee my promptly reply on debugging and feature requests, but they are welcome. After all I have a pretty hectic daytime job

kazuni said:
I can't guarantee my promptly reply on debugging and feature requests, but they are welcome. After all I have a pretty hectic daytime job
Click to expand...
Click to collapse
any chance of ASOP any time soon? in your opinion...

Hope so, will make rom development alot eaisier if they can just port them accross for us

had hypergalaxy ported to my device... now trying to get the FC out... and trying to figure out abt the signal lost...

with so much debate of whether the I9305 supports fm radio I wonder if anyone has ported the I9300 radio app/firmware to settle the argument. not that i really care about fm radio lol...

springah said:
any chance of ASOP any time soon? in your opinion...
Click to expand...
Click to collapse
AOSP would be a bit difficult for me, as I am not very good at working on AOSP materials however I will still investigate porting something like CM/MIUIv4 over when I got some time this weekend

cyborg24 said:
with so much debate of whether the I9305 supports fm radio I wonder if anyone has ported the I9300 radio app/firmware to settle the argument. not that i really care about fm radio lol...
Click to expand...
Click to collapse
ive tried few fm radio and is not working with our stock kernel..

kazuni said:
AOSP would be a bit difficult for me, as I am not very good at working on AOSP materials however I will still investigate porting something like CM/MIUIv4 over when I got some time this weekend
Click to expand...
Click to collapse
How about AOKP? Or is CM AOKP....?
Also, which part of the rom is it that is making things like the toggle switches big, green and ugly, and not a stock JB look of small and blue?
Like this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

singlecell83 said:
How about AOKP? Or is CM AOKP....?
Also, which part of the rom is it that is making things like the toggle switches big, green and ugly, and not a stock JB look of small and blue?
Like this :
Click to expand...
Click to collapse
AOKP is a complete new set of material to work with - it requires custom kernel building and additional proprietary drivers, and fortunately samsung has provided I9305 as open source already; however, i am not familiar with kernel building on android, so I probably won't be working on CM based builds unless I can gain some more knowledge :\ Sorry.

Fm radio will not work if the kernel does not support it, and if the kernel that came with firmware which didnt have FM radio pre-installed then it wont be programmed to support it, Basically meaning no drivers. Mick.Wheels was working on compiling a kernel to support FM but he is now on holidays so gotta wait. This guy caled Weeeo was reveiwing a I9305 for his sponsor SamsungUK apparently, But I saw his video on youtube and it was showing the FM radio app , so i asked him if he could test it which he did and was working fine. so I am in the middle of asking him to create a nandroid for us to play with. He is currently waiting for a replacement phone as his screen was scratched. So will see what happens then when it returns. Exciting timessssss

btemtd said:
Fm radio will not work if the kernel does not support it, and if the kernel that came with firmware which didnt have FM radio pre-installed then it wont be programmed to support it, Basically meaning no drivers. Mick.Wheels was working on compiling a kernel to support FM but he is now on holidays so gotta wait. This guy caled Weeeo was reveiwing a I9305 for his sponsor SamsungUK apparently, But I saw his video on youtube and it was showing the FM radio app , so i asked him if he could test it which he did and was working fine. so I am in the middle of asking him to create a nandroid for us to play with. He is currently waiting for a replacement phone as his screen was scratched. So will see what happens then when it returns. Exciting timessssss
Click to expand...
Click to collapse
That would be great. On one hand we have a dev that would try to compile the kernel from source - which means we could (in future) adding overclocking support, init.d support, amongst a few things.
On the unfortunate part is that, I've contacted gokhanmoral and confirmed that works on LTE model will not be done since there are not enough time nor the actual hardware. It would be great if someone can pickup the source from git and see if there are anything we can do to make a branch.

I was also looking into porting CM. But as of today I haven't found time to get a new build environment up and running. Maybe I'll look into it later today. As far as I saw it shouldn't be too hard to port CM from 9300... But on the other hand I have less experience with Samsung phones than with their TVs Anyway, if I get some progress you will be the first to know about it.
Gesendet von meinem GT-I9305 mit Tapatalk 2

I have an i9300, and just stumbled onto this thread. If someone can give me a system dump there is a good chance I can compare both of them and see the differences between the i9300 and i9305. It shouldn't be too different, probably requiring some minor changes to get this working (the main difference here is only the radio to support LTE and the extra RAM)
Sent from my Transformer Pad Infinity TF700T using xda app-developers app

I will give you what you need, I have just PM'd you ... You have the Brain I have the Game (I9305) looll Letz Do dizzzz braaa Team LIQUID indhouse lol

hiemanshu said:
I have an i9300, and just stumbled onto this thread. If someone can give me a system dump there is a good chance I can compare both of them and see the differences between the i9300 and i9305. It shouldn't be too different, probably requiring some minor changes to get this working (the main difference here is only the radio to support LTE and the extra RAM)
Sent from my Transformer Pad Infinity TF700T using xda app-developers app
Click to expand...
Click to collapse
If that is all the differences are, and the 9305 parts can be implemented into a 9300 rom, does that mean we could convert any custom 9300 rom into a 9305 rom? Or am I just dreaming?

singlecell83 said:
If that is all the differences are, and the 9305 parts can be implemented into a 9300 rom, does that mean we could convert any custom 9300 rom into a 9305 rom? Or am I just dreaming?
Click to expand...
Click to collapse
Most of the time yes, because we just have to be careful about integrating the drivers for the modem. I'm not so sure about CM/AOKP roms since they have their own built drivers. I'm unfortunately not familiar with driver building so perhaps someone else can shed some light on this topic hopefully.

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Thanks ✟
Moving to Q&A

[ROM][PORT] OptimusNexus ALPHA: 1 | 04032013

Hello friends!
Today I release a Optimus G rom for our Nexus 4! This is a very early alpha build/port so dont expect a lot of functionality!
I AM NOT RESPONSIBLE FOR ANY BRICKED DEVICES!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Whats working in Alpha 1:
- It boots
- Screen works
- Sound works
- Charging works
- Bluetooth works
- Connecting to PC works
- LED notification works
- Anything related to CPU/GPU is working
- Navigation buttons for Nexus 4 work
Whats not working:
- GSM + WiFi
- Camera
- GPS
- Notebook FC's
- Random reboots
DO NOT FLASH THE BOOT.IMG ON NEXUS 4 ROMS, IT WILL BREAK SOME THINGS LIKE WIFI.
Code:
[CENTER]Changelog:
Alpha 1: Initial release[/CENTER]
Flash with CWM or TWRP
Download link Alpha 1: https://mega.co.nz/#!fFEEWSQS!K_3LVHkhj9Av-KpYINuSWXPK5B4VmrykdXm4ijYNUn8
OPTIONAL
Download link boot.img for Alpha 1: http://d-h.st/SsP
Donations
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=8J4B5RXM7UZKQ​

Optimus G kernel or replaced with Nexus4 stock kernel? Flashing a Nexus4 specific kernel seems to be a greet idea.
We should only change the device specific parts of the rom to be fully working.
I'll try to help later today.
Tapatalk 2-vel küldve az én Nexus 4-ről

Not that I would revert back to manufacture based skinned ROMs, but +1 for the nexus dev community!

TaRsY said:
Optimus G kernel or replaced with Nexus4 stock kernel? Flashing a Nexus4 specific kernel seems to be a greet idea.
We should only change the device specific parts of the rom to be fully working.
I'll try to help later today.
Tapatalk 2-vel küldve az én Nexus 4-ről
Click to expand...
Click to collapse
Optimus G kernel.
Its pretty hard to use the Nexus 4 kernel and modules etc. since its for Android 4.2.x and this rom is Android 4.1.2 =]

Aerys said:
Optimus G kernel.
Its pretty hard to use the Nexus 4 kernel and modules etc. since its for Android 4.2.x and this rom is Android 4.1.2 =]
Click to expand...
Click to collapse
oops forgot about this..

Not trying to say this isn't awesome but I'm only interested in that damn lock screen! That unlock effect is what everyone is after! Hopefully this is the beginning of that work. Well done for this! :thumbup:
Sent from my Nexus4™

benrees21 said:
Not trying to say this isn't awesome but I'm only interested in that damn lock screen! That unlock effect is what everyone is after! Hopefully this is the beginning of that work. Well done for this! :thumbup:
Sent from my Nexus4™
Click to expand...
Click to collapse
Yea the lockscreen is really beautiful!
EDIT:
Download link Alpha 1:
https://mega.co.nz/#!fFEEWSQS!K_3LVHkhj9Av-KpYINuSWXPK5B4VmrykdXm4ijYNUn8
Have fun =]

Awesome!!! When I was deciding what my next phone would be, it was between a nexus 4, an xperia z, and an optimus g....now I can see what I missed out on!
Great work...can't wait for a stable build

Note; When you boot the device it will do a media scan. It will be VERY slow and laggy for like 10-20 seconds.

The things that i find interesting are the wonderful lockscreen and the colors on the screen looks amazing, hope the devs here can put the Optimus G RGB and gamma values into their kernels.

Can't wait. I wonder if this rom will provide better battery life. LG has some tweaks in their software that's not part of stock android.
Sent from my Nexus 4 using xda premium

NardVa said:
Can't wait. I wonder if this rom will provide better battery life. LG has some tweaks in their software that's not part of stock android.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
My generalization about lg's android experience in the past is they have no idea what they are doing with software(not that I do either) and battery life was horrific. Maybe they got better and more experienced dev teams together. We shall see. On the other hand the nexus 4 is a mighty fine experience:thumbup:

Does this rom have an optimus or a nexus kernel? If it's an Optimus one, maybe we can use some of the custom optimus kernels with it! Then we can really get some awesome stuff!
*edit*
I hadn't looked through their forums to see that they are still in development infancy stages Maybe our cooperation can be mutually beneficial!

I think we will need the Nexus 4 kernel for rild and Wifi but yeah lets experiment a little.

davwman said:
My generalization about lg's android experience in the past is they have no idea what they are doing with software(not that I do either) and battery life was horrific. Maybe they got better and more experienced dev teams together. We shall see. On the other hand the nexus 4 is a mighty fine experience:thumbup:
Click to expand...
Click to collapse
this is because (IMHO) LG are like Sony....they make some of the sexiest, best performing, highest quality hardware you can find for many different types of devices/electronics. However, they have absolutely no business making software & firmware.
Having said that, I do think they have a great deal of wonderful IDEAS that they implement into their electronics (especially android) but they are usually not polished well, and end up being unstable or just buggy as hell. I do love having those features pulled out and isolated, though, so I can have a monstrous selection of special features that were never intended to work together, though. And when they are, for example, android mods added on top of pure aosp, beautiful things happen, IMHO

Aerys said:
I think we will need the Nexus 4 kernel for rild and Wifi but yeah lets experiment a little.
Click to expand...
Click to collapse
Don't see why that wouldn't work. Same hardware

davwman said:
Don't see why that wouldn't work. Same hardware
Click to expand...
Click to collapse
that's my exact school of thought here, as well. I would think if the rom can be swapped out so easily, there's no reason why at least SOME of the kernels wouldn't work by default, as well.
I'm looking specifically at the aokp port for optimus...that's got to have a custom kernel, I would think...and it's most likely optimized for optimus (lol...say that 5 times fast )

Do you even think this will boot on a n4 kernel?
Would it be easier having a 4.2.2 ROM with the LG stuff added or what's your game plan? I'm very excited about this..
Sent from my Nexus 4

ChongoDroid said:
Do you even think this will boot on a n4 kernel?
Would it be easier having a 4.2.2 ROM with the LG stuff added or what's your game plan? I'm very excited about this..
Sent from my Nexus 4
Click to expand...
Click to collapse
My goal is to get a fully working Optimus G rom. The Nexus 4 kernel doesnt boot with this rom, so I have to look at other options.

In theory with the correct radio/kernel combo, would this rom be capable of using DC HSPA +42? I guess a better question would be is the Optimus G capable of it?
Sent from my Nexus 4 using xda app-developers app

For modders Only bug rooms STOP

I know that build a rom it's not that easy, and make it stable and fully working it's even harder. I also know that drivers and blobs are closed-source, so it's hard to make a device fully working.
But I wanna give some advice, because who want to mod his phone finds about 30/40 roms all unstable and full of bugs.
In my opinion, it's useless to release a rom if it isn't finished, wifi or bluetooth doesn't work, apps force-close, phone reboots randomly or maybe drinks the battery in 2 hours.
Lags in games, the home screen lags with 3/4 widgets. Maybe after a clean install the rom performs well but then you discover that it's not so good.
Let's not forget also that despite the roms are not finished, many times they aren't update any more to solve the bugs, or they are updated but the bugs remain.
I don't mean that ALL the roms have ALL the bugs, but each rom has at least two of those problems.
Some people may say that there are hardware limits to justify the bugs. Or maybe that the battery has to be changed. But those are only excuses considering that on three pages of roms, ONLY one performs well.
I have always been told “you have to change the battery”, or “the phone has got few ram” to justify the bugs. But why with the FluidRom gType (an Italian rom) I manage 24 hours with a normal usage (mobile data always on, wifi, background apps, little playing with games, several calls, facebook and whatsapp)? No lags in games, home and browser. So I assume that “change the battery” and “we have few ram” are only excuses.
If you release a rom only to show that you are able to develop something but then it’s full of bugs, stop. Don’t release it. Or release it when it performs really well.
The 4X it’s a 2012 flagship phone, but the roms are badly developed. So let’s not blame the hardware.
Some people may say “who forces you to change rom?” People try new roms because modders promise improvements.
Maybe this topic will be closed to restrict freedom of speech. But mine are only suggestions.

Serial67 said:
I know that build a rom it's not that easy, and make it stable and fully working it's even harder. I also know that drivers and blobs are closed-source, so it's hard to make a device fully working.
But I wanna give some advice, because who want to mod his phone finds about 30/40 roms all unstable and full of bugs.
In my opinion, it's useless to release a rom if it isn't finished, wifi or bluetooth doesn't work, apps force-close, phone reboots randomly or maybe drinks the battery in 2 hours.
Lags in games, the home screen lags with 3/4 widgets. Maybe after a clean install the rom performs well but then you discover that it's not so good.
Let's not forget also that despite the roms are not finished, many times they aren't update any more to solve the bugs, or they are updated but the bugs remain.
I don't mean that ALL the roms have ALL the bugs, but each rom has at least two of those problems.
Some people may say that there are hardware limits to justify the bugs. Or maybe that the battery has to be changed. But those are only excuses considering that on three pages of roms, ONLY one performs well.
I have always been told “you have to change the battery”, or “the phone has got few ram” to justify the bugs. But why with the FluidRom gType (an Italian rom) I manage 24 hours with a normal usage (mobile data always on, wifi, background apps, little playing with games, several calls, facebook and whatsapp)? No lags in games, home and browser. So I assume that “change the battery” and “we have few ram” are only excuses.
If you release a rom only to show that you are able to develop something but then it’s full of bugs, stop. Don’t release it. Or release it when it performs really well.
The 4X it’s a 2012 flagship phone, but the roms are badly developed. So let’s not blame the hardware.
Some people may say “who forces you to change rom?” People try new roms because modders promise improvements.
Maybe this topic will be closed to restrict freedom of speech. But mine are only suggestions.
Click to expand...
Click to collapse
Haha, there are so many angles i can take on this.
I and the other 4x developers and users don't owe you ANYTHING, dont like our roms? dont use them, Simple. It amazes me some people are so entitled...

Go and make some Roms by yourself we'll see how good they would be .
For your information bringing roms to device in long chain of more people than just our devs
Sent from my LG-P880 using Tapatalk

Serial67 said:
I know that... TL;DR
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Wow ! Never thought I'd read something like this on the 4X forum !
You're so wrong. So so wrong !
Do you realize that when a dev releases a ROM he does this on his time and (most of the time) he doesn't expect anything in return.
Have you ever tried to build a ROM from source ? To compile ? To fix bugs ? To spend hours developing ? I really doubt since you don't realize what this is and the time it takes.
Moreover, our device is "special". The last official update we had was 4.1.2 and thanks to the dev you criticized we are now at 4.4.2 !!! I'm not sure you realized the work of these devs.
Also you say that we don't have any stable ROM but you're wrong ! For me, "stable" means that you can use the ROM daily and profit of all basic and important features of the ROM therefore there ARE stable ROMs ! Since I'm in charge of Beanstalk 4.4.2 I won't give any name but for having personally tried many customs ROMs I can say that we do have stable ROMs.
Everybody has its opinion but man... You're wrong and some devs may understand your post as an offence.
I hope you see what I'm trying to explain.
Sent from my LG-P880 using XDA Premium 4 mobile app

ectoplasma22 said:
Wow ! Never thought I'd read something like this on the 4X forum !
You're so wrong. So so wrong !
Do you realize that when a dev releases a ROM he does this on his time and (most of the time) he doesn't expect anything in return.
Have you ever tried to build a ROM from source ? To compile ? To fix bugs ? To spend hours developing ? I really doubt since you don't realize what this is and the time it takes.
Moreover, our device is "special". The last official update we had was 4.1.2 and thanks to the dev you criticized we are now at 4.4.2 !!! I'm not sure you realized the work of these devs.
Also you say that we don't have any stable ROM but you're wrong ! For me, "stable" means that you can use the ROM daily and profit of all basic and important features of the ROM therefore there ARE stable ROMs ! Since I'm in charge of Beanstalk 4.4.2 I won't give any name but for having personally tried many customs ROMs I can say that we do have stable ROMs.
Everybody has its opinion but man... You're wrong and some devs may understand your post as an offence.
I hope you see what I'm trying to explain.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Don't worry ecto, we are talking about it in the italian forum where this kind of discussion began.. And we are composing it saying exactly what you're saying right here..hope that it'll stop as a great mistake, and to go on..
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app

one word, ridiculous

We should change abit this letter and sent it to the LG dev-update department so they can ask @Demetris @laufer @adam @Ectoplasma @JoinTheRealms @SnXo (and many other talented and good people) for help next time they decide to push or even make any software for any LG phone.I know.this guyment to say official software not custom one so i am just correcting his type mistake.
Послато са LG-P880 уз помоћ Тапатока

whoa, easy there, mate...
First of all, I haven't seen an unstable ROM on our phones up till now. I am personally using CM (unofficial) and SlimKat as my daily drivers, and both are rock stable. The only bugs I have personally encountered are the camera (which is extremely hard to properly fix) and the broken reboot into recovery on Slim. And that's it.
All ROMs you find on xda are made for free, you don't need to pay anything, which means you also can't demand anything. Bringing a ROM to a device can take several hours (disregarding the time the pure download of the sourcecode takes), as every ROM needs its special treatment.
Furthermore, do you have any idea how long the pure compile process takes? On my new machine (which I upgraded for development only) needs ~75min for a clean build. Before that, my lappy was working over 8 hours for a clean build...
Saying we devs wouldn't maintain our ROMs isn't really nice, nor what XDA stands for. We do our best to provide you with the best/fully functional stuff, but there are things we can't fix/improve simply because we don't experience these issues. As an example, I am debugging my kernel ATM, and @FunkyRasta and I both run the kernel, however, FunkyRasta is experiencing lags, that I never experienced. So without his reports, I wouldn't even know about that until someone else might encounter it after the release.
@Serial67, nobody forces you to use "unstable" ROMs, but please don't just complain, but rather give some helpful feedback (logs) to help solve the issues. If you're not willing to provide such info (you don't have to), please don't complain.
Thread closed.

[ROM][4.4.4] moto_msm8960 OmniROM

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Overview
OmniROM is pretty close to AOSP, as the 4.4.4 era comes to a close I've decided to post it.
This build has nothing to do with Nobe1976.
It is not his build on Droidrzr forums and was built by me, from source. Although it is likely the same (assuming configs for our device haven't changed much the past year)
Download
Feb/27/2015: OmniROM 4.4.4
KKBL only for now folks!!!
Source
Device
https://github.com/CyanogenMod/android_device_motorola_moto_msm8960/tree/cm-11.0
Kernel
https://github.com/CyanogenMod/android_kernel_motorola_msm8960dt-common/tree/cm-11.0
Vendor
https://github.com/TheMuppets/proprietary_vendor_motorola/tree/cm-11.0

Yes JJBL people, I will build for you, but I need someone to test so OmniROM aside; IF JBBL people want these firmware I will need a tester :<

Just flashed this on my XT926 and the only issue ive had is when going into Settings>More>Mobile Networks>Carrier Settings The process com.android.phone force closes.

nice rom, works fairly well on my razr m. feels lighter than cyanogenmod and other 4.4.x roms.

lol
Do you know about Lollipop? lol

Working really great on my XT925.. I love OmniRom.. Thanks @Tqr

The fact that this base appeared here means MIUI v6 comes soon
Edit: I'm NOT heading MIUI v6 I am only working as an assistant this is not my era to shine; with that being said if I can't get a JBBL volunteer It's not likely JBBL people will get MIUI v6

kkruglov said:
nice rom, works fairly well on my razr m. feels lighter than cyanogenmod and other 4.4.x roms.
Click to expand...
Click to collapse
A lot of people use my MIUI or other fork builds but don't really have the chance to use my source-builds which are almost always nearly 'perfect' (I don't usually post them)
Some compatibility takes a huge hit after I start chopping stuff to pieces so I just wanted to throw this up for people who are the opposite of the MIUI/Lewa/Whatever crowd and just want something as close to 'stock' android as possible.

Tqr said:
but don't really have the chance to use my source-builds which are almost always nearly 'perfect' (I don't usually post them)
Click to expand...
Click to collapse
why?

kkruglov said:
why?
Click to expand...
Click to collapse
It would annoy me if someone ported a ROM I had planned to work on using a base I built.

Tqr said:
The fact that this base appeared here means MIUI v6 comes soon
Edit: I'm NOT heading MIUI v6 I am only working as an assistant this is not my era to shine; with that being said if I can't get a JBBL volunteer It's not likely JBBL people will get MIUI v6
Click to expand...
Click to collapse
Looking forward to see MIUI v6! Loved MIUI even since my evo 3d. Hope it comes soon
Sent from my DROID RAZR HD using XDA Free mobile app

dulexetina said:
Looking forward to see MIUI v6! Loved MIUI even since my evo 3d. Hope it comes soon
Sent from my DROID RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
Me too but my build configs are currently not working correctly for some devices.
It's kind of problematic on my end at this point because the past two builds of (pretty much) AOSP have resulted in failure for some unknown reason; even with supported configs.
At the same time to bring a close-to-AOSP ROM to this firmware I had to make a lot of changes in source; changes which may have caused breakage upon building for some devices so I've had to revert everything for this specific build which will probably set the process back a day or two.
But I don't want to sound over-important; the person heading v6 could have(and has) done this fully on their own power without issue and I am really contributing nothing except for build related stuff which isn't even essential It's just to save them time because a lot of time was saved in my life during v5.
It's like they say, someone does something for you and you do something for them if you can; a capacity I'm kind of failing in right now because a lot of the devices I'd like to see get hit with v6 do not have proper source bases

Thanks, very smooth... can you add HDR feature?

ikromy said:
Thanks, very smooth... can you add HDR feature?
Click to expand...
Click to collapse
Maybe, I have to address JBBL right after I finished with the device I'm building for right now.
Like a true piece of scum I neglected the JBBL folks during v5 because I wasn't aware of the exacts surrounding it and frankly was too lazy/busy to produce it.
But from here out all of my builds will also accomodate JBBL now that I know how to deal with it.
I mean it's really like a friend of mine said; that it's better to release broken things at first because If you release something right the first time your topic won't have as many views and as much attention but I've always kind of been a black sheep with my preference for (nearly fully) functional first releases
Edit: I can do MIUIv5 for JBBL if people really still care about it but I'd rather focus on getting things ready for V6, and other projects I'm working on
It's really important that ANY errors with this code-base are brought to my attention , I really do not want to find out there is some inherent error in this when V6 is released It's really important that I do this right so I don't have to bother the developer of it to do yet another build on a rebase.
I feel like I've really annoyed people because I've had multiple peers/friends/co-workers/whatever download firmware that somehow 'wasn't right' this week

Do it. It's been awhile. And that miui phone overseas is killing em softly. I'm on jbbl now to start fresh but if you decide to put out v5 I'll try it. I am ecstatic about v6 to try out.. I will be trying the omni for now. I need a real stable ROM at the moment.

Get lolly miui for mb886.

manuski said:
Do it. It's been awhile. And that miui phone overseas is killing em softly. I'm on jbbl now to start fresh but if you decide to put out v5 I'll try it. I am ecstatic about v6 to try out.. I will be trying the omni for now. I need a real stable ROM at the moment.
Click to expand...
Click to collapse
MIUI v6 is now nearly fully functioning on moto_msm8960 JBBL & KKBL, including V6 camera, scanner and all the other stuff you'd expect.
Unlike being a PatchROM build this is a direct adaptation from a Xiaomi device so there is a level of exclusivity here.
I really don't have the right to release this, It will be part of a friends multi-base thread; It'll show up at some point next month, hopefully.
I wanted to let people who are really anticipating being able to use V6 know that the codebase is finished; it does have all the features you'd expect on true stock MIUI that have never been ported (In this era):
- MIUI camera (Everything, including filters, panorama, fast&slow-motion recording mode...)
- MIUI Scanner (Everything)
- Nearly full native Xiaomi drivers (!)
- Everything, all features

TecknoFreak said:
Get lolly miui for mb886.
Click to expand...
Click to collapse
It's being worked on as well, but 4.4 takes priority because it is literally almost finished.

Tqr said:
MIUI v6 is now nearly fully functioning on moto_msm8960 JBBL & KKBL, including V6 camera, scanner and all the other stuff you'd expect.
Unlike being a PatchROM build this is a direct adaptation from a Xiaomi device so there is a level of exclusivity here.
I really don't have the right to release this, It will be part of a friends multi-base thread; It'll show up at some point next month, hopefully.
I wanted to let people who are really anticipating being able to use V6 know that the codebase is finished; it does have all the features you'd expect on true stock MIUI that have never been ported (In this era):
- MIUI camera (Everything, including filters, panorama, fast&slow-motion recording mode...)
- MIUI Scanner (Everything)
- Nearly full native Xiaomi drivers (!)
- Everything, all features
Click to expand...
Click to collapse
This is great to hear man! Now I want to try it even more.Can't wait till next month...release it tomorrow MIUI 5 was great,simple and smart,just hope that v6 is gonna be same or even better.
Sent from my DROID RAZR HD using XDA Free mobile app

Honestly I straight up lied.
MIUI v6 boots with full function except RIL- Because of the nature of this work all builds have been kept closed. I will check with the head of development and ask if beta may begin.
If anyone here feels strong in development and can address RIL both the KKBL and JBBL can have this firmware in the very forseeable future. It's because we use some kind of fked up Generic RIL and I'm not sure where to play Xiaomis invasive code because It's so different.
I do not even know how this device handles RIL in the 4.4 era, if anyone has an understanding of this please be in touch.

Nexus 6 - Stock, AOSP, CM and Blends

OK so I know everybody had different experiences but I thought I'd share mine and see what others are experiencing .....
Currently running Multirom
Primary -- Android N
Secondaries Tried -- Pure Nexus, Stock Lite, UberStock, and couple others
The N ROM is just a bit buggy and although there are apparently work arounds I can't get many apps to work. Fairly fluid but not "snappy".
Stock Lite has interestingly been the most steady but requires Cat mod to get the bare minimum Moss that I like.
Weirdly enough despite Pure Nexus being so popular, it and a few other AOSP builds have just not been as reliable. I just got a phone call on PN and the screen wouldn't come on until several power button pushes.
UberStock was snappy but it just irritates me to not have a text percentage battery.
The CM builds of various authors usually have their bugs.
Any thoughts? Or share experiences ..... Not necessarily of a specific ROM but more of thoughts Stock, vs AOSP, vs CM etc
Certainly don't want to insult any developers .... Their shared work is appreciated

jcrompton said:
OK so I know everybody had different experiences but I thought I'd share mine and see what others are experiencing .....
Currently running Multirom
Primary -- Android N
Secondaries Tried -- Pure Nexus, Stock Lite, UberStock, and couple others
The N ROM is just a bit buggy and although there are apparently work arounds I can't get many apps to work. Fairly fluid but not "snappy".
Stock Lite has interestingly been the most steady but requires Cat mod to get the bare minimum Moss that I like.
Weirdly enough despite Pure Nexus being so popular, it and a few other AOSP builds have just not been as reliable. I just got a phone call on PN and the screen wouldn't come on until several power button pushes.
UberStock was snappy but it just irritates me to not have a text percentage battery.
The CM builds of various authors usually have their bugs.
Any thoughts? Or share experiences ..... Not necessarily of a specific ROM but more of thoughts Stock, vs AOSP, vs CM etc
Certainly don't want to insult any developers .... Their shared work is appreciated
Click to expand...
Click to collapse
running pure nexus myself. generally, I like staying with aosp builds. but, user experience can be heavily effected by whatever the user installs or mods. like your power button issue, that can happen because of an app, a theme, or a mod. not because the ROM doesn't like it, but becauseany apps, themes, or mods are not made by professionals, but by amateurs.
stock, I usually am on for the first hour to a max of a couple days after getting a nexus. then its usually an aosp build. CM, or CM based ROMs I stay very far away from. I used to be the biggest CM fanboy years ago, but CM is not the CM that used to be. now they are different, as are their goals.

stock+xposed+gravity box and other modules? you don't really need custom roms anymore, having said that I prefer aosp, cm not even once

sgloki77 said:
stock+xposed+gravity box and other modules? you don't really need custom roms anymore, having said that I prefer aosp, cm not even once
Click to expand...
Click to collapse
Do you ever have or feel like xposed slows things down .....? It's been a while since I've tried
simms22 said:
running pure nexus myself. generally, I like staying with aosp builds. but, user experience can be heavily effected by whatever the user installs or mods. like your power button issue, that can happen because of an app, a theme, or a mod. not because the ROM doesn't like it, but becauseany apps, themes, or mods are not made by professionals, but by amateurs.
stock, I usually am on for the first hour to a max of a couple days after getting a nexus. then its usually an aosp build. CM, or CM based ROMs I stay very far away from. I used to be the biggest CM fanboy years ago, but CM is not the CM that used to be. now they are different, as are their goals.
Click to expand...
Click to collapse
Thanks

have all these modules working on pure nexus, snappy as usual
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6 using Tapatalk

Since the introduction of Lollipop, I really haven't felt the need to flash a custom ROM.
Stock ROM has always worked great for me, I use root for a few things like Greenify and Xposed, but I stopped using those as well.
On my N6:
Stock ROM - Best so far. Sometimes I don't even use root. Excellent battery life, no bugs and great performance.
PureNexus - Great ROM, however the CMTE version was a bit buggy when I used it. No disrespect to the devs, they're doing an excellent job.
CyanogenMod - My second choice, always. Nightly builds are stable in most ways, I'm using one right now and it's working great with a custom theme and a few mods installed.
---------- Post added at 11:42 AM ---------- Previous post was at 11:41 AM ----------
simms22 said:
I used to be the biggest CM fanboy years ago, but CM is not the CM that used to be. now they are different, as are their goals.
Click to expand...
Click to collapse
Can you elaborate a bit on this?
Everything seems the same to me.

I got my Nexus last year. I ran several kind of custom roms. Most of them dont last longer then a few hours. The one i am using the most and always go back to is Lite Rom. It has everything that i need and is stable, good battery life and just works. Sometimes i feel like the builders just try to put too many things into the rom and it can be confusing. I like to keep it simple and clean.

@murtaza02: I'm not @simms22, but I can provide some insight here. Back before Android hit version 4, Cyanogenmod was "king of custom ROMs". They were on the cutting edge, with lots of features that simply weren't available in Google's stock Android. This was done not for money, but out of love of Android. A few years ago they incorporated and now offer a commercial alternative to Android. Afterward they pretty much stopped innovating, especially after the Focal fiasco.
Cyanogenmod strayed from its roots, looking to get paid money rather than respect.

Strephon Alkhalikoi said:
@murtaza02: I'm not @simms22, but I can provide some insight here. Back before Android hit version 4, Cyanogenmod was "king of custom ROMs". They were on the cutting edge, with lots of features that simply weren't available in Google's stock Android. This was done not for money, but out of love of Android. A few years ago they incorporated and now offer a commercial alternative to Android. Afterward they pretty much stopped innovating, especially after the Focal fiasco.
Cyanogenmod strayed from its roots, looking to get paid money rather than respect.
Click to expand...
Click to collapse
Yes I recall during the time that this was going on there were several very heated discussions that took place here on XDA. The bottom line though 4 those of us not in the know basically I just noticed that cm ROMs definitely changed

Once they incorporated is when the innovation stopped, as that is when they changed focus away from what brought them to the attention of everyone in the Android community. Instead of making a "better" Android, they settled for simply making Android. The Focal fiasco cost them, in that they lost many of their freelance developers, and lost a lot of respect from the community at large.
To this day I don't put Cyanogenmod on my devices, because Cyanogenmod left the building a long time ago.

To be honest I stopped using CM and CM based roms years ago. While it has a little o do with their business model it was mostly due to the fact that there are bugs that have been around for years that were never fixed. Then they merge in code without testing it which has been known to cause huge issues.
I prefer roms built from AOSP which there are very few. I also never go for what is popular. To be honest to many people are sheep and follow the crowd. (yes even in android) I prefer to try some out and make up my own mind. And then I stick with it.

Honestly, I ditched Cyanogenmod because they stopped being innovative. It goes hand in hand with them incorporating, because the profit motive overrides everything else. Profit first, last, and always.