So i'm a bit confused. Which builds are better for fireball? The official cyanogen nightly or the unofficial mdm builds? I can't post in the offical dev post for cyanogen so i have to post here.
Right now i'm running the latest nightly. All seems to be be pretty stable. Just missing 16:9 for the camera, and once in a while while i'm running with my nikeplus app and the google music playing, if i hit the power button to turn off the screen it resets the entire device.
Anyways, i can't tell which builds are better / ahead of the others?
Sorry i know i posted this in another forum, but it was the wrong forum.
danjfoley said:
So i'm a bit confused. Which builds are better for fireball? The official cyanogen nightly or the unofficial mdm builds? I can't post in the offical dev post for cyanogen so i have to post here.
Right now i'm running the latest nightly. All seems to be be pretty stable. Just missing 16:9 for the camera, and once in a while while i'm running with my nikeplus app and the google music playing, if i hit the power button to turn off the screen it resets the entire device.
Anyways, i can't tell which builds are better / ahead of the others?
Sorry i know i posted this in another forum, but it was the wrong forum.
Click to expand...
Click to collapse
I use MDM builds because I have the flicker issue from the cynagen 3.4 kernel. I don't think I've had any random reboots on the MDM like I did with the cyanogen nightlies.
Why then are the mdm releases.. or the guy behind the mdm releases, not working on the official releases? I mean why is his hard work not going into the official releases?
I feel like if i switch to mdm i'm going to miss fixes in the official nightlys.. as it's just one guy working on it.
Just doesn't make sense. the official releases are open sourced at git hub right? So why isn't the mdm guy working on the official releases?
danjfoley said:
Why then are the mdm releases.. or the guy behind the mdm releases, not working on the official releases? I mean why is his hard work not going into the official releases?
I feel like if i switch to mdm i'm going to miss fixes in the official nightlys.. as it's just one guy working on it.
Just doesn't make sense. the official releases are open sourced at git hub right? So why isn't the mdm guy working on the official releases?
Click to expand...
Click to collapse
@mdmower is working on official releases. instead of merging patches that might cripple the officials he is doing "beta" test outside of it. hence why he's always asking for feed back.
once he gets enough feedback on the mdm builds he submits a patch to cm and it gets merged into source. ^_^
i would go with the mdm5 build because it has a working camera focus but once he merges the RIL commit i will be going back because i like the stability of the officials minus the RIL hickup i had. but everyone is different and will react differently.
where did you get the 3.4 kernel?
Sum Dumb Guy said:
I use MDM builds because I have the flicker issue from the cynagen 3.4 kernel. I don't think I've had any random reboots on the MDM like I did with the cyanogen nightlies.
Click to expand...
Click to collapse
where did you get the 3.4 kernel?
synisterwolf said:
@mdmower is working on official releases. instead of merging patches that might cripple the officials he is doing "beta" test outside of it. hence why he's always asking for feed back.
once he gets enough feedback on the mdm builds he submits a patch to cm and it gets merged into source. ^_^
i would go with the mdm5 build because it has a working camera focus but once he merges the RIL commit i will be going back because i like the stability of the officials minus the RIL hickup i had. but everyone is different and will react differently.
Click to expand...
Click to collapse
This is mostly right, just couple clarifications:
mdm releases exist because CyanogenMod cannot publish releases that include a certain proprietary camera file. They are based on the latest stable CyanogenMod release (10.1.2) with a few tweaks that improve stability. Typically, these changes are backports from nightlies. In my opinion, these are the most functional CyanogenMod releases to date. Unfortunately, the kernel in use by these releases had to be dropped in order to prevent legal repercussions to CyanogenMod from closed-minded manufacturers.
I am actively working on the official nightlies. Unfortunately, HTC has not released kernel source for this phone that is meant to work with jellybean. Furthermore, hardware support (for every phone out there) still relies on closed-source manufacturer drivers/blobs, and this phone hasn't seen a jellybean release yet. Long story short, there's stuff that just doesn't work because of lack of jellybean-compatible kernel/firmware/drivers from HTC.
mdmower said:
This is mostly right, just couple clarifications:
mdm releases exist because CyanogenMod cannot publish releases that include a certain proprietary camera file. They are based on the latest stable CyanogenMod release (10.1.2) with a few tweaks that improve stability. Typically, these changes are backports from nightlies. In my opinion, these are the most functional CyanogenMod releases to date. Unfortunately, the kernel in use by these releases had to be dropped in order to prevent legal repercussions to CyanogenMod from closed-minded manufacturers.
I am actively working on the official nightlies. Unfortunately, HTC has not released kernel source for this phone that is meant to work with jellybean. Furthermore, hardware support (for every phone out there) still relies on closed-source manufacturer drivers/blobs, and this phone hasn't seen a jellybean release yet. Long story short, there's stuff that just doesn't work because of lack of jellybean-compatible kernel/firmware/drivers from HTC.
Click to expand...
Click to collapse
and thats why i like the XDA page system. ^_^ straight from the source ladies and gentlemen. thank you for clearing that up.
bad_christian said:
where did you get the 3.4 kernel?
Click to expand...
Click to collapse
3.4 are part of the official nightly releases. MDM uses 3.0.xx Kernels that are more stable for my phone.
Related
anyone know that what is difference between Unofficial CM9 Nightly and alpha 0.6 ?
hki_peter said:
anyone know that what is difference between Unofficial CM9 Nightly and alpha 0.6 ?
Click to expand...
Click to collapse
Nightlies are probably going to be less stable.
Basically, when you get a nightly, it's not yet been released. It's what somebody was working on last night...when they quit working on it, whether successful in what they had been working on or not, it was uploaded - hence the name, nightly.
And now you know.
And knowing's half the battle.
sean is here. said:
Nightlies are probably going to be less stable.
Basically, when you get a nightly, it's not yet been released. It's what somebody was working on last night...when they quit working on it, whether successful in what they had been working on or not, it was uploaded - hence the name, nightly.
And now you know.
And knowing's half the battle.
Click to expand...
Click to collapse
Well its slightly more than just something someone happened to be working on and left it!
I'm using the KANG of 20120216 and finding it is far better than my experience with .06!
And I'm about to flash 20120217.
pa49 said:
Well its slightly more than just something someone happened to be working on and left it!
I'm using the KANG of 20120216 and finding it is far better than my experience with .06!
And I'm about to flash 20120217.
Click to expand...
Click to collapse
EDIT: I re-read this reply after posting my response, and the first sentence is just incorrect. A 'nightly' is nothing "more than just something someone happened to be working on and left it".
The rest is subjective opinion, but the definition of what a nightly is can be found clearly explained below.
I think you've misunderstood me, or something else somewhere along the line.
I'm not saying that they're better or worse than official releases.
I was merely pointing out that the way they come about, is that they aren't fully evaluated and tested for stability in order to be released publicly as a finished product.
Before a major release, devs will typically spent time testing their software themselves, in addition to sending it out to 'focus groups' (they aren't REALLY focus groups but serve the same function) where they are further tested...then upon completion of testing, or when a threshold of minimum functionality has been reached (often with a pre-specified maximum number of bugs or critical failures) they can be released publicly.
Nightlies don't go through that extensive testing. That's where the name comes from. The devs 'clock out' and the ROM is built, and posted as a 'nightly'.
From the CM Team:
... Lastly we have the Nightlies, which are as volatile as a firmware can get. These releases keep coming at an interval of a day or two and if you do end up trying one of these, do not be alarmed if the your device goes cuckoo on you. These ROMs are largely untested, and as advised by CyanogenMod, not meant for use for an average user. These releases, are meant to test untested waters with tweaked codes that may or may not break your phone.
Click to expand...
Click to collapse
My understanding was that the nightlies were being built automatically by a script that pulls the most recent source from the cm server. As new code is added daily by devs it is automatically put into nightly builds for testing.
joggerman said:
My understanding was that the nightlies were being built automatically by a script that pulls the most recent source from the cm server. As new code is added daily by devs it is automatically put into nightly builds for testing.
Click to expand...
Click to collapse
As far as I'm aware, you are correct.
Hey guys,
I just want to add, the one of the developers of the official CM9 alpha release is recommending users install the nightly as there may not be an official update pushed put anytime soon.
http://liliputing.com/2012/02/nightly-builds-of-cyanogenmod-9-for-the-hp-touchpad-now-available.html
Anyone know which nightly is pretty stable?
wonshikee said:
Anyone know which nightly is pretty stable?
Click to expand...
Click to collapse
go for alpha 1 as dalingrin said the nightlies won't be based on alpha 1 until a few days later.
As soon as the at&t 4.1.2 jelly bean update was available i had it flashed, and for the most part, im happy, not as snappy as the 4.2.2 rom releases but HDMI out works on it along with the other bells and whistles.... what i was wondering was when do we start seeing roms that are based on that att release...is it the source code that the devs are waiting on? Just curious......the devs do an amazing job, its unreal...i give them so much credit..
here's one...
So we're starting to see already.....
I'm hoping AOSP based roms actually start taking advantage of our 4.1.2 kernel soon. Granted, CM merged some stuff from it, but from what I read in the CM nightly thread, they'd have been better off with the blobs and bases they were using rather than trying to merge all the skyrocket stuff. Perhaps they think more longterm than I, though.
Hello,
I've been a fan of this site for a while, and I just created an account tonight.
I noticed that the ICS kernel source was released by HTC today. I am looking forward to having a nice ICS AOSP rom with working video. Thank you DEVS!
With the ICS kernel source, are we limited to ICS versions of android? Can the kernel source be modified to work with Jelly Bean? Maybe CM10.1?
From a verizon customer holding on to unlimited data,
thanks again to all of the DEVs and individuals that contribute to the Thunderbolt community.
blackshoes said:
Hello,
I've been a fan of this site for a while, and I just created an account tonight.
I noticed that the ICS kernel source was released by HTC today. I am looking forward to having a nice ICS AOSP rom with working video. Thank you DEVS!
With the ICS kernel source, are we limited to ICS versions of android? Can the kernel source be modified to work with Jelly Bean? Maybe CM10.1?
From a verizon customer holding on to unlimited data,
thanks again to all of the DEVs and individuals that contribute to the Thunderbolt community.
Click to expand...
Click to collapse
From what I understand it's being worked on, maybe not actively right now but it seems to be a strong possibility.
HTC released their kernel version 3.0.16. That will out-of-the-box support Ice Cream Sandwich. Jelly Bean needs 3.0.31 (or higher). I think what the kernel developers now need to do is back port the necessary bits and pieces to HTC's version to make it compatible.
hallstevenson said:
HTC released their kernel version 3.0.16. That will out-of-the-box support Ice Cream Sandwich. Jelly Bean needs 3.0.31 (or higher). I think what the kernel developers now need to do is back port the necessary bits and pieces to HTC's version to make it compatible.
Click to expand...
Click to collapse
Already have one patched up to around 3.0.80, just gotta finish adding in the new board files, LTE drivers and defconfig.
As we all know though, older kernels can also be made to run versions they aren't intended for as well.
Also already have CM10.1 running pretty darn well...
santod040 said:
Already have one patched up to around 3.0.80, just gotta finish adding in the new board files, LTE drivers and defconfig.
As we all know though, older kernels can also be made to run versions they aren't intended for as well.
Also already have CM10.1 running pretty darn well...
Click to expand...
Click to collapse
What a tease!
Sent from my Blissful Bolt using Tapatalk 2
santod040 said:
Already have one patched up to around 3.0.80, just gotta finish adding in the new board files, LTE drivers and defconfig.
As we all know though, older kernels can also be made to run versions they aren't intended for as well.
Also already have CM10.1 running pretty darn well...
Click to expand...
Click to collapse
That is great news Santod!
santod040 said:
Already have one patched up to around 3.0.80, just gotta finish adding in the new board files, LTE drivers and defconfig.
As we all know though, older kernels can also be made to run versions they aren't intended for as well.
Also already have CM10.1 running pretty darn well...
Click to expand...
Click to collapse
I think I just soiled myself. Oh the amazing things I miss while I'm at work.
santod040 said:
Already have one patched up to around 3.0.80, just gotta finish adding in the new board files, LTE drivers and defconfig.
As we all know though, older kernels can also be made to run versions they aren't intended for as well.
Also already have CM10.1 running pretty darn well...
Click to expand...
Click to collapse
Is the RIL working for you?
video of cm1.1 on the tbolt
blackshoes said:
Hello,
I've been a fan of this site for a while, and I just created an account tonight.
I noticed that the ICS kernel source was released by HTC today. I am looking forward to having a nice ICS AOSP rom with working video. Thank you DEVS!
With the ICS kernel source, are we limited to ICS versions of android? Can the kernel source be modified to work with Jelly Bean? Maybe CM10.1?
From a verizon customer holding on to unlimited data,
thanks again to all of the DEVs and individuals that contribute to the Thunderbolt community.
Click to expand...
Click to collapse
HTC Thunderbolt Runnig cm10.1 Video:good:
jacobmacek said:
HTC Thunderbolt Runnig cm10.1 Video:good:
Click to expand...
Click to collapse
loving this! :good:
Cyanogenmod 10.1 official support?
I'm curious. Once the devs are able to get the kernel ready for cyanogenmod 10.1, has anyone thought about submitting that kernel to cyanogenmod for official Thunderbolt cyanogenmod builds?
From the posting linked below, cyanogenmod requires a tested kernel and a developer or group of developers that will maintain the kernel for official support. Is cyanogenmod official support a possibility with the kernel the DEVs are working on?
forum.cyanogenmod.com/topic/72612-can-i-get-cyanogenmod-on-my-device/
Thanks for the info!
blackshoes said:
I'm curious. Once the devs are able to get the kernel ready for cyanogenmod 10.1, has anyone thought about submitting that kernel to cyanogenmod for official Thunderbolt cyanogenmod builds?
From the posting linked below, cyanogenmod requires a tested kernel and a developer or group of developers that will maintain the kernel for official support. Is cyanogenmod official support a possibility with the kernel the DEVs are working on?
forum.cyanogenmod.com/topic/72612-can-i-get-cyanogenmod-on-my-device/
Thanks for the info!
Click to expand...
Click to collapse
I can't speak for everyone, but let's get "that" kernel worked out first.
It's now possible, but still not exactly a simple task.
Having already knocked out a custom Sense ICS kernel from the source was done without much hassle already.
And Jelly Bean has come pretty far for the Bolt already, but making a fully functional Jelly Bean kernel from HTC's ICS source may take a bit more dilligence.
So I would just say let's take it one step at a time.
Official builds would require dedication on a dev or multiple devs parts to continue updating and supporting it.
There aren't a lot of candidates left, that may still have enough personal interest in doing so when that time comes.
Basically, that's just not something that can be predicted at this point, as there are still uncertainties surrounding such a thing, from several different aspects/angles.
It would of course be great to see the old Bolt be added to the list of devices which are officially supported.
Who knows what else the future may hold for this faithful beast that keeps getting surprises, even if long overdue.
jacobmacek said:
HTC Thunderbolt Runnig cm10.1 Video:good:
Click to expand...
Click to collapse
I want.
Sent from my Blissful Bolt using Tapatalk 2
I know this is yesterday's news but I felt compelled to post this and get other users input on this topic.
http://www.cyanogenmod.org/blog/releases-11-12-final
What I don't understand is Cyanogen's priorities when it comes to which devices get 11, 12 or 12.1. I completely understand about phasing out CM11/KitKat as that is now a rather "old" version of android. However what I don't understand is why a device as new/old as ours (Aug 2013 is not THAT old) is stuck on CM12 (and now a final Snapshot build as of 6/25)? I mean, the Galaxy S3 is even getting 12.1 builds. I'm wondering if its because that was a far more popular device than the G2 was?
Just wanted to put this out there and see what other people think and find out what they're running currently on their G2 variant. I own the US T-Mobile D801 variant and do NOT want to run stock (LG) Lollipop since my device tends to run extremely HOT on it. I know not everyone was complaining about their G2 overheating on stock LP but I notice a considerable difference running CM12.
So, how do you guys feel about this? Do you even care or what?
t3chn0s1s said:
I know this is yesterday's news but I felt compelled to post this and get other users input on this topic.
http://www.cyanogenmod.org/blog/releases-11-12-final
What I don't understand is Cyanogen's priorities when it comes to which devices get 11, 12 or 12.1. I completely understand about phasing out CM11/KitKat as that is now a rather "old" version of android. However what I don't understand is why a device as new/old as ours (Aug 2013 is not THAT old) is stuck on CM12 (and now a final Snapshot build as of 6/25)? I mean, the Galaxy S3 is even getting 12.1 builds. I'm wondering if its because that was a far more popular device than the G2 was?
Just wanted to put this out there and see what other people think and find out what they're running currently on their G2 variant. I own the US T-Mobile D801 variant and do NOT want to run stock (LG) Lollipop since my device tends to run extremely HOT on it. I know not everyone was complaining about their G2 overheating on stock LP but I notice a considerable difference running CM12.
So, how do you guys feel about this? Do you even care or what?
Click to expand...
Click to collapse
We haven't had nightlies for a while now. What you see as nightlies aren't really worthwhile builds, they didn't have any device or kernel fixes for the g2.
A new 11 build is coming probably because half the android userbase relies on kitkat at the moment.
As for the s3, it's not getting CM12 nor 12.1, not the international version at the least. Archi is maintaining an unofficial version, but it still carries the bugs from 10.0/10.1.
Lastly, this is the commit that requires to be merged in order for the builds to even be considered started:
http://review.cyanogenmod.org/#/c/93181/
Without it, nothing CAF related can be merged, and as such, no CM12.1 builds can be had for our device. I believe the reason it's not merged because not all of the variants have a lollipop release, if they ever will get one. Also the whole bootstack/amount of users who don't reed is astonishingly dangerous to handle, so rashed simply preferred to skip building for now.
Finally, it's not that popular of a device. It's a nexus without being a nexus with a locked bootloader, which is a pain in the ass and not too many maintainers have it left (they either went with G3 or skipped LG entirely, as did a whole bunch from the exynos team back in the day).
t3chn0s1s said:
I saw you responded to my post about CM12 nightlies not continuing for the G2. Wanted to ask you (since you didn't mention) what 5.1 (CAF source) ROM you're running? What would you suggest for a stable AOSP ROM that has device/kernel specific updates for our G2s?
Click to expand...
Click to collapse
Why not reply to me in this thread then?
I'm running official euphoria builds. Any caf roms run fine. They are all based on the same LG-devs CAF device source + kernel source. Some roms have specific tweaks, but as far as functionality, they all work the same way (ie: if bluetooth deep sleep is broken, it's most likely broken in every rom).
Choristav said:
Why not reply to me in this thread then?
I'm running official euphoria builds. Any caf roms run fine. They are all based on the same LG-devs CAF device source + kernel source. Some roms have specific tweaks, but as far as functionality, they all work the same way (ie: if bluetooth deep sleep is broken, it's most likely broken in every rom).
Click to expand...
Click to collapse
Sorry - was on my phone when I saw your replies and it was just easier for me to respond in the other thread.
Anyways.. thanks for the info. I've done some research and I'm a bit more informed about CAF and what it means to device specific sources, ROMs, etc. Are you just using the stock Euphoria kernel or something else?
On this forum @varund7726 builds his rather excellent ResurrectionRom from the latest CM code release. I suggest you use that. For the D803, @zr239 has beaten all odds including LG not releasing CAF code, to build a fully functional pure CM 12.1 ROM that closely tracks official CM repos.
Lg G2 has it pretty good !
@Choristav
I wanted to clarify something you said in your initial response to my OP. You said the S3 wasn't going to get CM12 or 12.1 but when I navigate to the CM downloads page for ANY S3 variant - they ALL have CM12.1 nightlies still being generated. What exactly did you mean?
t3chn0s1s said:
@Choristav
I wanted to clarify something you said in your initial response to my OP. You said the S3 wasn't going to get CM12 or 12.1 but when I navigate to the CM downloads page for ANY S3 variant - they ALL have CM12.1 nightlies still being generated. What exactly did you mean?
Click to expand...
Click to collapse
I checked, you are right, several of the qualcomm variants have cyanogenmod support. This means that they have active maintainers, but they also don't have to deal with locked bootloader crap, which is why the bump commit is so important for our device.
I only mentioned the international version, which support was dropped because it had a lot of issues thanks to its closed source exynos processor (it requires extra work, and some stuff doesn't end up working anyway).
Not really much to say, the commit is already in CM's gerrit, it's just waiting for review. Maybe it's a CTS-side issue?
Aside from that, being a maintainer doesn't really require much, just effort and presence. It's not an easy task, I'm just saying anyone can apply to be a maintainer and get nighties rolling for a device you might not even have heard of.
@Rashed97 is the man for our G2 when it comes to CM. Dont mind nightlies as long as Rashed is around
Note: he is currently busy with the One M9 but we will hopefully see some cool stuff from him in the future.
Not really a big deal, last I remember those nightlies were still using outdated jellybean components. I wouldn't use them, I would use something on the G2 forums like Rashed97 builds like someone else said.
I don't think that the availability of nightlies has to do with the device itself so much as it has to do with someone maintaining the g2 and building roms, so nightlies could come back at any time if someone steps up and does it.
Ploxorz said:
Not really a big deal, last I remember those nightlies were still using outdated jellybean components. I wouldn't use them, I would use something on the G2 forums like Rashed97 builds like someone else said.
I don't think that the availability of nightlies has to do with the device itself so much as it has to do with someone maintaining the g2 and building roms, so nightlies could come back at any time if someone steps up and does it.
Click to expand...
Click to collapse
And it appears you're correct as there is another nightly build up with today's date. I apparently posted this thread prematurely.
Guys I wouldnt worry to much about CM, its not like they are the only (or even best) option in the forums. If you guys want development then dig in and make some for it.
zelendel said:
Guys I wouldnt worry to much about CM, its not like they are the only (or even best) option in the forums. If you guys want development then dig in and make some for it.
Click to expand...
Click to collapse
You are absolutely right. I had no idea until I posted this thread that CM nightlies did not contain any device specific updates. I honestly NEVER used to like CM at all. I honestly hated it... until owning a OnePlus One. I originally had the G2 right when it came out in 2013 and sold it off long ago & moved on to better devices - but when my OPO got stolen about 2 months back or so - I had to find a relatively cheap, but decent device and the G2 was the best bang for the buck (5.2" display, quick charge 2.0, 3000 mAh battery) and no other phones in 2013 came close to the specs the G2 had at the time.
So, now that I know CM is basically a sh*t ROM for this device I'll be moving on to a ROM that is compiled using CAF sources. Thanks everyone for your input!
Somehow doesn't look too good so far:
https://jira.cyanogenmod.org/browse/CYAN-6556
But why oh why?
The LG G2 still is such a modern and powerful device. It might be almost two years "old", but it's way better than a lot of other current devices.
I am using AICP on my g2. It is based on CM(5.1.1).
What's the best place to follow updates / changes to the CAF stuff?
I know there's a handful of ROMs based on CAF sources, I'm not too interested in the changelogs of those ROMs, more following the progress of CAF before it eventually all gets merged into CM12.1.
Is this it? https://github.com/lg-devs/android_device_lge_g2-common/commits/cm-12.1-caf
seanp25 said:
What's the best place to follow updates / changes to the CAF stuff?
I know there's a handful of ROMs based on CAF sources, I'm not too interested in the changelogs of those ROMs, more following the progress of CAF before it eventually all gets merged into CM12.1.
Is this it? https://github.com/lg-devs/android_device_lge_g2-common/commits/cm-12.1-caf
Click to expand...
Click to collapse
I would watch the Code Aurora forums where CAF comes from.
zelendel said:
I would watch the Code Aurora forums where CAF comes from.
Click to expand...
Click to collapse
It's better to watch public activity on Rashed97's github. He is CM maintainer for LG G2 and he brought up CAF sources for our devices.
adamz667 said:
It's better to watch public activity on Rashed97's github. He is CM maintainer for LG G2 and he brought up CAF sources for our devices.
Click to expand...
Click to collapse
No. It's far better to watch the main code base. Cm messes too much up by not testing code before merging.
zelendel said:
No. It's far better to watch the main code base. Cm messes too much up by not testing code before merging.
Click to expand...
Click to collapse
Okay, but @seanp25 probably want to follow source changes for our device, not common CAF source.
Just saw this:
Çetin ÇÖNE wrote on Jul 26 11:18 AM:
Why there is no nighlies it's really stable. Merge it please
Seth Shelnutt wrote on Jul 26 1:26 PM:
There are no nightlies because SELinux is not enabled. Sensors break with it enabled and I don't have time to address it yet.
Click to expand...
Click to collapse
Source:
http://review.cyanogenmod.org/#/c/103673/
Some days after that there came this:
http://review.cyanogenmod.org/#/c/103674/
So maybe there soon will be 12.1 nightlies?
I would really like to see the latest PA ported to the original MiPad. Is anybody up to take up the mantel!?
No go. Some of PA's stuff is closed source, so I'm afraid unless someone in the PA team gets a Mi Pad, we'll probably never see a build.
drakonizer said:
No go. Some of PA's stuff is closed source, so I'm afraid unless someone in the PA team gets a Mi Pad, we'll probably never see a build.
Click to expand...
Click to collapse
Thanks for shading light on the topic.
drakonizer said:
No go. Some of PA's stuff is closed source, so I'm afraid unless someone in the PA team gets a Mi Pad, we'll probably never see a build.
Click to expand...
Click to collapse
Did you read this https://plus.google.com/+ParanoidAndroidCorner/posts/dcrz5JP1HLg - seems there's hope after all
"Device Maintainers
We are currently looking to expand our roster of supported devices and to do this we would like to recruit some more developers to our team. If you think you have what it takes and have a device (or two) that you’d like to see supported by us we’d like you to get in touch. "
Palm Trees said:
Did you read this https://plus.google.com/+ParanoidAndroidCorner/posts/dcrz5JP1HLg - seems there's hope after all
"Device Maintainers
We are currently looking to expand our roster of supported devices and to do this we would like to recruit some more developers to our team. If you think you have what it takes and have a device (or two) that you’d like to see supported by us we’d like you to get in touch. "
Click to expand...
Click to collapse
Not yet unfortunately. They're looking for official maintainers. Our device can't go official for any ROM because in order to get a stable build, the developers patch the Android source itself, which is not possible in official builds built by a server. In addition, if we were to use the new blobs (that don't require said patches), we wouldn't have a working camera, which a custom ROM community like AOSPA would never agree to.
Once camera starts to work with new blobs, we can expect something.
drakonizer said:
Not yet unfortunately. They're looking for official maintainers. Our device can't go official for any ROM because in order to get a stable build, the developers patch the Android source itself, which is not possible in official builds built by a server. In addition, if we were to use the new blobs (that don't require said patches), we wouldn't have a working camera, which a custom ROM community like AOSPA would never agree to.
Once camera starts to work with new blobs, we can expect something.
Click to expand...
Click to collapse
Thanks for clarifying that Let's hope for the best.