[Q] Lollipop ROM Timeframe - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Hello,
I have a question on what is needed by developers to make Lollipop ROMs for our S3.
I have been following the releases and know that the images for the Nexus devices are up and that OTAs have begun. Is that what developers need as a starting point?
As you can tell I'm fairly clueless about this so I appreciate any information because I like to follow along.
Thanks!

Devs need the actual sources to build, which have been released. Unfortunately they can't work with the factory images for Nexus devices.
If I remember correctly, it took 2 or 3 months to get a usable KitKat build from Slim. (the first ones to do it, I recall.) We'd be lucky to see it by the new year, in my opinion.

Thank you for the info.
So they take the Nexus sources and then build it for our devices and then figure out how to add drivers for our hardware, etc?
Thank you for the timeline. I'm hoping it will be sooner, but your estimate is more realistic

I saw this in the S3 international forum:
http://forum.xda-developers.com/galaxy-s3/orig-development/rom-namelessrom-t2939673
And
http://forum.xda-developers.com/galaxy-s3/development/wip-cyanogenmod-12-t2936990
Looks like they are hard at work on lollipop for their devices. I wonder if anyone is working on it for ours yet?

philhouse said:
I saw this in the S3 international forum:
http://forum.xda-developers.com/galaxy-s3/orig-development/rom-namelessrom-t2939673
And
http://forum.xda-developers.com/galaxy-s3/development/wip-cyanogenmod-12-t2936990
Looks like they are hard at work on lollipop for their devices. I wonder if anyone is working on it for ours yet?
Click to expand...
Click to collapse
Im wondering the same and if anybody has taken interest in building it for the d2lte variants like the att etc..

I haven't seen anything yet in the forums, but I'm still hopeful that someone will!

Found this today. Sweeeeet:
http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071

philhouse said:
Found this today. Sweeeeet:
http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Click to expand...
Click to collapse
Yeah I been on the ROM since it was provided.

Related

Official 4.0.4 From Google about to be released AOSP

https://groups.google.com/forum/?fromgroups#!topic/android-building/YoBlTfntDvo
I am hoping i see a good rom to push this 4.0.4
http://forum.xda-developers.com/showthread.php?t=1569496
Sent from my Galaxy Nexus using Tapatalk
I have been running 4.0.4 for a couple months already thanks to the leak. evryone that has been hesitant to try it will be very pleased with it.
About damn time.
jr313 said:
I have been running 4.0.4 for a couple months already thanks to the leak. evryone that has been hesitant to try it will be very pleased with it.
Click to expand...
Click to collapse
That's a much older build though that JBQ admitted had some bugs that were quite bad. Better to way a day or so for the official build.
Can't wait for this. Will the native tethering hack still work with it?
blunden said:
That's a much older build though that JBQ admitted had some bugs that were quite bad. Better to way a day or so for the official build.
Click to expand...
Click to collapse
It's not that much older. IMM74 is exactly 34 days newer than IMM30. The second M says they're both from the same quarter of the year. The two builds were made 30 days and 74 days into quarter M.
SOURCE: http://source.android.com/source/build-numbers.html
1/4 down the page
here is official link w/ 4.0.4 - Binaries for Nexus Phones and Flagship Devices - Google Support for Nexus Phones and Flagship Devices - Google Code
I will wait for miui version.
From mister JBQ himself via Twitter:
@XxSmokeeyxX toro source files and proprietary binaries are out (but untested). mysid factory images will follow the OTA (still untested).
Click to expand...
Click to collapse
We are getting source and blobs!
zeke1988 said:
I will wait for miui version.
Click to expand...
Click to collapse
Do you use a custom launcher or put everything in folders? Tried to get into MIUI, but not for me unless there is a better way to use it.
gchild320 said:
Do you use a custom launcher or put everything in folders? Tried to get into MIUI, but not for me unless there is a better way to use it.
Click to expand...
Click to collapse
Irrelevant to the thread, but when I used MIUI briefly, I used a custom launcher. I really don't like not having an app drawer. I like minimalist desktops
xVehemencityx said:
Irrelevant to the thread...
Click to expand...
Click to collapse
This thread is irrelevant to itself (if that's a thing). This is the development section so this should probably be in the general section. Believe me, the developers know this information a) because it's posted all over the interwebs today and b) they are developers and their new code beacons go off when ever El Goog releases new code.
blunden said:
That's a much older build though that JBQ admitted had some bugs that were quite bad. Better to way a day or so for the official build.
Click to expand...
Click to collapse
I personally highly doubt that there is a huge differ in performance increase from the already leaked build for CDMA version and the newly pushed out one. Some of the increased performances that are said it has I experience with the already leaked build. The camera is faster opening. The rotation is much faster. I don't experience any bugs.
When we actually get the official one you can bet I will put that on here and root it so I can benefit from overclocking and underclocking (good battery life)
Surely someone with over 400 posts would know that this has no business in the development forum.
TheBiles said:
Surely someone with over 400 posts would know that this has no business in the development forum.
Click to expand...
Click to collapse
+1 was wondering that myself.
GNEX
jr313 said:
I have been running 4.0.4 for a couple months already thanks to the leak. evryone that has been hesitant to try it will be very pleased with it.
Click to expand...
Click to collapse
You've been running an alpha build (basically) of the LTE version. It lacks updated kernels, drivers, and maybe even code. It was an accidental release.
So as awesome as it is, it's very possible it'll be even better when it comes out.

*** AT&T JB Leaks are out there *** NEED HELP

Ok .. we all know that XDA members and especially the Dev's are anxious to get there hands on an OFFICIAL AT&T release of JellyBean 4.1.x for our SGSIII's .. well, I can tell you this .. so far, AT&T (that I'm aware of) have already gone through 3 releases .. and NOT one of them have found there way up here on XDA.
The 4 builds so far are:
samsung/d2uc/d2att:4.1.1/JRO03L/I747UCDLI7:user/release-keys
samsung/d2uc/d2att:4.1.1/JRO03L/I747UCDLJ2:user/release-keys
samsung/d2uc/d2att:4.1.1/JRO03L/I747UCDLJ3:user/release-keys
samsung/d2uc/d2att:4.1.1/JRO03L/I747UCDLJ3c:user/release-keys
So .. if ANYONE knows, has access, secrets .. etc etc etc .. please release or leak so that our Dev's can have some real fun
I have searched high and low all over the internet .. I have been unable to find absolutely ZIP on all 3 releases.
And just how did you come across this information?
mrhaley30705 said:
And just how did you come across this information?
Click to expand...
Click to collapse
http://www.glbenchmark.com/phonedetails.jsp?benchmark=glpro25&D=Samsung+SGH-I747+(Samsung+Galaxy+S+III+AT+and+T)&testgroup=system
Ya seriously, we need someone on the inside to release these leaks.
I have been toying with installing a JB custom ROM from here, but all of them have things that just aren't working.
Sometimes I am tempted to just go back to the iPhone and get a 5.
I would love to install an official leak. Would make me feel better.
I am sure we will see something very soon in the form of a leak or info on official release. A Sprint document was just leaked stating the their official JB update pushes tomorrow. Unfortunately its always the case that AT&T takes longer on updates than others.
Ooo, watching this thread eagerly. Phandroid released an article today that Sprint is going to start JB updates for their GS3s starting tomorrow:
http://phandroid.com/2012/10/24/sprints-samsung-galaxy-s3-jelly-bean-rollout-starts-october-25th/
Would love to get my hands on one of these leaks until the official makes its way out.
jmacdonald19 said:
Ooo, watching this thread eagerly. Phandroid released an article today that Sprint is going to start JB updates for their GS3s starting tomorrow:
http://phandroid.com/2012/10/24/sprints-samsung-galaxy-s3-jelly-bean-rollout-starts-october-25th/
Would love to get my hands on one of these leaks until the official makes its way out.
Click to expand...
Click to collapse
Here's the article that specifically references the Sprint exclusion that I referenced on the other thread. As evidenced by today's development, the Examiner was correct.
http://www.examiner.com/article/samsung-galaxy-s-iii-may-not-get-jelly-bean-u-s-until-2013
kgbkny said:
Here's the article that specifically references the Sprint exclusion that I referenced on the other thread. As evidenced by today's development, the Examiner was correct.
http://www.examiner.com/article/samsung-galaxy-s-iii-may-not-get-jelly-bean-u-s-until-2013
Click to expand...
Click to collapse
Well nuts. I wonder why only Sprint is getting the love? Supposedly there are AT&T JB betas out there in the wild being tested, but none of them have leaked.
Can't come soon enough, if only because it'll eventually help our AOSP jelly roms wrt the proprietary bits.
There's no going back to a stock touchwiz rom, even if it is jellybean. )
(EDIT: Somebody gave this thread a 1-star rating, so I gave it a 5 to raise the current avg to 3)
zmore said:
Can't come soon enough, if only because it'll eventually help our AOSP jelly roms wrt the proprietary bits.
There's no going back to a stock touchwiz rom, even if it is jellybean. )
(EDIT: Somebody gave this thread a 1-star rating, so I gave it a 5 to raise the current avg to 3)
Click to expand...
Click to collapse
yeah, even if I won't use the stock JB rom, devs will to make our CM/AOKP much much better.
awaiting development.
joeyl said:
awaiting development.
Click to expand...
Click to collapse
And they are waiting for leakage.
By the looks of it .. there is now another release out there somewhere for AT&T :
samsung/d2uc/d2att:4.1.1/JRO03L/I747UCDLJ3c:user/release-keys
It doesn't matter if there are a million leaks, without the ability to dl, it doesn't do a lot of good.
Sent from my SGH-I897 using xda premium
mrhaley30705 said:
It doesn't matter if there are a million leaks, without the ability to dl, it doesn't do a lot of good.
Click to expand...
Click to collapse
I know .. it just sucks that all these are out there somewhere, and we can't get our hands on any of them !!!
Randomacts said:
yeah, even if I won't use the stock JB rom, devs will to make our CM/AOKP much much better.
Click to expand...
Click to collapse
Except that CM/AOKP are built almost entirely from source. Considering there isn't really a whole lot that's different between the Sprint, Bell, or whatever other carriers leaked/released their official JB builds for the GS3, i can't imagine having an AT&T specific ROM providing more aide than any of the others have already done.
elementaldragon said:
Except that CM/AOKP are built almost entirely from source. Considering there isn't really a whole lot that's different between the Sprint, Bell, or whatever other carriers leaked/released their official JB builds for the GS3, i can't imagine having an AT&T specific ROM providing more aide than any of the others have already done.
Click to expand...
Click to collapse
Regarding what leaks are already out there .. Sprint, Bell, Rogers, T-Mobile etc etc etc // There are still bugs with each one of them on our AT&T SGS3's .. and again, these are of cause leaks .. except the Sprint release which is now Official, and there are even still bugs with that when ported over to ours.
At least, if we can get our hands on a original AT&T leak .. we can see if these same bugs exist between the builds, or if AT&T has everything working as it should .. who knows !!!
That's why I've been posting that there are test builds out there for AT&T .. just cannot find them, or get our hands on them .. I know there is someone out there that has access to these builds .. problem is, that person is telling me that he does "not have permission to release" !!!
I couldn't even get the fella to verify the build numbers for me.
Some devs have serious connections when it's available out well be here
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
Some devs have serious connections when it's available out well be here
Click to expand...
Click to collapse
Ohh I'm fully aware of that .. alot of Devs do .. worse part of all this, I know someone on here that already has access to and has been using it .. I cannot persuade him to release/leak what he has, keeps telling me "I don't have permission" !!! SUCKS
His last response to me on Twitter was "I'm good, many people send drama my way for giving them free stuff. some people in the android community just ruin it for everyone." and I haven't heard from him since.

[Q] Build CM (CyanogenMod) for the hltetmo

Okay, so after no updates for a month and no sign of any sign of AOSP for the Note 3, I have decided to take things into my own hands. Or so I would like to believe. The problem? I have never built AOSP or Cyanogenmod before, let alone for a device that isn't even supported. So I was hoping the wonderful XDA community could help me out.
The only thing I really can't figure out is how to build CM/AOSP for an unsupported device using a device tree. Someone posted this tree on Github a month ago - https://github.com/OUDhs/android_device_samsung_hltetmo
Then there is a Cyanogenmod kernel for just regular hlte (not hltetmo), posted 10 days ago - https://github.com/CyanogenMod/android_kernel_samsung_hlte
And then there are blobs for mi5 (not mi7), posted 2 days ago - https://github.com/DoItForTheRatchets/vendor_hlte
So my questions are:
Are these any indication of progress on AOSP for the Note 3?
Can I/anyone build CM/AOSP from these for the hltetmo.
I know people have gotten CM on the Note 3; we have all seen the blurry pic one, but here is someone else on October 24th - https://plus.google.com/u/0/+TonyLayher/posts/A4J8eRH8Rht
gakio12 said:
Okay, so after no updates for a month and no sign of any sign of AOSP for the Note 3, I have decided to take things into my own hands. Or so I would like to believe. The problem? I have never built AOSP or Cyanogenmod before, let alone for a device that isn't even supported. So I was hoping the wonderful XDA community could help me out.
The only thing I really can't figure out is how to build CM/AOSP for an unsupported device using a device tree. Someone posted this tree on Github a month ago - https://github.com/OUDhs/android_device_samsung_hltetmo
Then there is a Cyanogenmod kernel for just regular hlte (not hltetmo), posted 10 days ago - https://github.com/CyanogenMod/android_kernel_samsung_hlte
And then there are blobs for mi5 (not mi7), posted 2 days ago - https://github.com/DoItForTheRatchets/vendor_hlte
So my questions are:
Are these any indication of progress on AOSP for the Note 3?
Can I/anyone build CM/AOSP from these for the hltetmo.
I know people have gotten CM on the Note 3; we have all seen the blurry pic one, but here is someone else on October 24th - https://plus.google.com/u/0/+TonyLayher/posts/A4J8eRH8Rht
Click to expand...
Click to collapse
It looks like it's progress or at least people are tinkering around with it. However, you would need a full tree for the device if you wanted to build it from source, know enough to get your own tree, or be able to fork from other device tree's to get something going. The new Nexus has the same chip so that may make things quicker with getting a full working device tree. I'm just quoting based on my own understanding of things, so please correct me if I'm wrong.
I've been wanting to know the same. I've built AOSP ROMs before (namely AOKP for my Note 1 pulling from CM's device tree) and would do the same if the files were available for the Note 3. A few devs have teased the community with screenshots, but until they post their code a tease and a cruel joke is all that it is. I really wish these devs would put their source code up even if it is incomplete and let the community at large get this thing in gear since obviously they can't do it fast enough single-handedly. Holding back code until it's "ready" defeats the entire purpose of open source development in the first place! We have the kernel but no one has a full device tree out yet, only a limited one for recovery purposes (mainly the TeamWin one from TWRP).
Any updates on cm10 or cm11 for the note 3
Sent from my SM-N900T
Within hours of any (usable) device tree updates you'll see an explosion of new CM-based firmwares in the Dev sections.
I'll be building BeanStalk for hltetmo, probably 100 ppl will upload unofficial CM 11, it'll be a giant party for all.
CrashTestDroid said:
Within hours of any device tree updates you'll see an explosion of new CM-based firmwares in the Dev sections.
I'll be building BeanStalk for hltetmo, probably 100 ppl will upload unofficial CM 11, it'll be a giant party for all.
Click to expand...
Click to collapse
Sooo... When's this party begin? :angel::fingers-crossed:
Can't wait for this
Sent from my SM-N900T using Tapatalk
Me neither even got rid of my note and went with n5 cause I couldn't wait but im back tk the beast just need cm
Sent from my SM-N900T
Ker~Man said:
Sooo... When's this party begin? :angel::fingers-crossed:
Click to expand...
Click to collapse
When a hlte device tree is buildable, looks like CM is making additions and others like nikkdotcom
gakio12 said:
Okay, so after no updates for a month and no sign of any sign of AOSP for the Note 3, I have decided to take things into my own hands. Or so I would like to believe. The problem? I have never built AOSP or Cyanogenmod before, let alone for a device that isn't even supported. So I was hoping the wonderful XDA community could help me out.
The only thing I really can't figure out is how to build CM/AOSP for an unsupported device using a device tree. Someone posted this tree on Github a month ago - https://github.com/OUDhs/android_device_samsung_hltetmo
Then there is a Cyanogenmod kernel for just regular hlte (not hltetmo), posted 10 days ago - https://github.com/CyanogenMod/android_kernel_samsung_hlte
And then there are blobs for mi5 (not mi7), posted 2 days ago - https://github.com/DoItForTheRatchets/vendor_hlte
So my questions are:
Are these any indication of progress on AOSP for the Note 3?
Can I/anyone build CM/AOSP from these for the hltetmo.
I know people have gotten CM on the Note 3; we have all seen the blurry pic one, but here is someone else on October 24th - https://plus.google.com/u/0/+TonyLayher/posts/A4J8eRH8Rht
Click to expand...
Click to collapse
Its getting real close. I imagine some other stuff is needed like qcom hardware updates and stuff. I'd give it another few weeks or so. BUT I imagine it'll be available soon.
I noticed nikkdotcom has a thread over in general for trying to get it running; he is asking for assistance in getting it to work.
CrashTestDroid said:
When a hlte device tree is buildable, looks like CM is making additions and others like nikkdotcom
Click to expand...
Click to collapse
That would be accurate.
Nikkdotcom GitHub here: https://github.com/nikkdotcom/android_device_samsung_hltetmo
---------- Post added at 01:18 AM ---------- Previous post was at 01:10 AM ----------
gakio12 said:
I noticed nikkdotcom has a thread over in general for trying to get it running; he is asking for assistance in getting it to work.
Click to expand...
Click to collapse
Im looking for someone who knows a little better than me about building without the proper blobs for the device. Once the right blobs are available, it will be custom ROMs galore!
What blobs do you need? I thought blobs had to be extracted from the TW stock ROM. GPU blobs should be able to come from any other S800 device right (like the Nexus 5)?
Sent from my SM-N900T using xda app-developers app
geekcentercreations said:
That would be accurate.
Nikkdotcom GitHub here: https://github.com/nikkdotcom/android_device_samsung_hltetmo
---------- Post added at 01:18 AM ---------- Previous post was at 01:10 AM ----------
Im looking for someone who knows a little better than me about building without the proper blobs for the device. Once the right blobs are available, it will be custom ROMs galore!
Click to expand...
Click to collapse
I'd be more than happy to lend a hand.
ProTekk said:
I'd be more than happy to lend a hand.
Click to expand...
Click to collapse
That is great news! We need someone with experience like you. I remember you from other devices, namely the s3.
Would you be able to reach out to the OP and try and get things rolling?
Have you found anything useful on github?
idtheftvictim said:
That is great news! We need someone with experience like you. I remember you from other devices, namely the s3.
Would you be able to reach out to the OP and try and get things rolling?
Have you found anything useful on github?
Click to expand...
Click to collapse
There's enough on GitHub right now for a starting point. I've just started to poke around this morning so I can't say much. Tbh, I've been fairly content with TouchWiz so that's been one reason I haven't had a strong interest in working on AOSP
idtheftvictim said:
That is great news! We need someone with experience like you. I remember you from other devices, namely the s3.
Would you be able to reach out to the OP and try and get things rolling?
Have you found anything useful on github?
Click to expand...
Click to collapse
Really? Content with touchwiz? Hmmm...I wish I knew more, I would be started trying to build cm awhile ago
Sent from my SM-N900T using xda app-developers app
Here is the most likely furthest along tree for anyone.
https://github.com/utkanos/android_device_samsung_hltetmo
It just seems like we might not see stuff on this device. Looking back on this thread people talked like it would be released in a week but I think it's going to be a lot longer than that.
idtheftvictim said:
Really? Content with touchwiz? Hmmm...I wish I knew more, I would be started trying to build cm awhile ago
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
That stuff is 2 months old. Nothing in two months? Man...no progress
Sent from my SM-N900T using xda app-developers app
I've never seen a device of this caliber take this long to receive an AOSP ROM! Wish I knew how guys, I'm tired of the TW ROMS, need some action in this forum already

LG Spectrum 2 ROM Development.

I am.willing to fund a dev for the creation of a custom Rom for the LGE VS930. We have root and a way to bypass the downloader. There is no reason a year and a half later that we can't have a custom Rom.
Sent from my VS930 4G using Tapatalk
Also waiting eagerly for its custom rom
Pleeeeeaaasssssse Devs work on it. Please
Sent from my GT-N7100 using Tapatalk 2
blah blah blah
After all this time, no one has even announced a development. I think wishing for it is a dead subject. I'm going to get a Samsung since it seems that developers aren't interested in LG's
bullriders said:
After all this time, no one has even announced a development. I think wishing for it is a dead subject. I'm going to get a Samsung since it seems that developers aren't interested in LG's
Click to expand...
Click to collapse
Yeah man i agree with you..
i dont want to raise a thread from the dead, but this is completely possible. lg made the source files completely downloadable for 4.1 jelly bean, and i'm going to see if i cant compile and get it running this week. we already have an unlocked kernel, so a custom rom shouldnt be that far fetched, especially considering the hardware is so similar to other cellphones with huge rom development.
if anyone could help me out, though, i would greatly appreciate it. i've never actually compile a rom from source, but i do have experience with code, and app development. I also have the actual hardware, which apparently was a huge problem for a while.
here's to hoping everything runs smoothly, and that we get a working, clean rom out soon!
here's a link to the ics and jb source code from lg. (cant i have too few posts, but basically go the the lg open source repository and search for vs930)
hannse12 said:
i dont want to raise a thread from the dead, but this is completely possible. lg made the source files completely downloadable for 4.1 jelly bean, and i'm going to see if i cant compile and get it running this week. we already have an unlocked kernel, so a custom rom shouldnt be that far fetched, especially considering the hardware is so similar to other cellphones with huge rom development.
if anyone could help me out, though, i would greatly appreciate it. i've never actually compile a rom from source, but i do have experience with code, and app development. I also have the actual hardware, which apparently was a huge problem for a while.
here's to hoping everything runs smoothly, and that we get a working, clean rom out soon!
here's a link to the ics and jb source code from lg. (cant i have too few posts, but basically go the the lg open source repository and search for vs930)
Click to expand...
Click to collapse
Having any luck?

[Q] Is no one sharing sources?

Hi, HAM devs!
You propably don't know me yet, as i am new to the HAM. I already built CM7, 10 and 11 on LG devices though, so i am not totally new to android development/building.
Well.. i just got this Ascend Mate, and thought it would be nice to have a custom rom on it, like i had on other devices.
But all i can find is closed source flashables. Seems like joe.stone is the only one who shared atleast something.
Don't you guys think we could achieve more, if we work together?
I really want to work on custom stuff for our HAM, but it would be easier if i don't have to start from scratch, while a bunch of people COULD share their experiences with me.
So please contact me, if you can provide some useful informations on how to build for the HAM. - Let's do something!
- MisjudgedTwat a.k.a. BangL
Dont hold your breath mate, in my opinion This is one of the worst forums on xda !
Well, maybe i just start instead of flaming.
Here we go: https://github.com/hwmt1-u06
If anybody is interested in participating to this, just let me know.
I think the main reason for that is that most of the stuff here was developed in Russia or China and those of us here just basically searched online and found ROMs and posted links here.
Joe Stone was the main Dev here and he's moved on. Gold Concert did some good work here too and moved on. Outside of these guys I think the rest of people in the group are like me. We know a little about developing but we're not Devs so as a result the forum has pretty much died.
I would welcome your developing skills here right now:beer:
sent from my MT1-U06 using Tapatalk 2
yeah, i kinda figured that out already, my first post was a little bit fast maybe.
well, let's see what i can do... so far i can boot, but sound and reboots arent working well (maybe more).
currently trying to contact mrAlmid, and looking into his roms for a hint to the right direction.
Just a thought. Since huawei mate and huawei p6 are essentially same hardware (same motherboard, same cpu/gpu) with main difference in display, maybe some of the sources for p6 will come in handy?
tileeq said:
Just a thought. Since huawei mate and huawei p6 are essentially same hardware (same motherboard, same cpu/gpu) with main difference in display, maybe some of the sources for p6 will come in handy?
Click to expand...
Click to collapse
absolutely, yes.
alright, i got my first pretty-much-useable build done, so let the bug-hunting begin...
http://forum.xda-developers.com/asc...-unofficial-cyanogenmod-11-0-beta-v0-t3229182
Once a Finnish developer tried porting sailfish to the P6, he (or someone he forked from) had managed to collect almost all the sources for the P6. You can try tinkering around, if you have time, you could figure out how to build the needed libraries for the graphics stack from source (all the other devs jumped the boat already), if you succeed then we may have a chance of compiling a working Lollipop rom. For the mate, dont forget to change the touchscreen drivers as it differs on the P6 and the Mate. Heres the repo: https://github.com/locusf/cm11-p6
tauio111 said:
Once a Finnish developer tried porting sailfish to the P6, he (or someone he forked from) had managed to collect almost all the sources for the P6. You can try tinkering around, if you have time, you could figure out how to build the needed libraries for the graphics stack from source (all the other devs jumped the boat already), if you succeed then we may have a chance of compiling a working Lollipop rom. For the mate, dont forget to change the touchscreen drivers as it differs on the P6 and the Mate. Heres the repo: https://github.com/locusf/cm11-p6
Click to expand...
Click to collapse
a working lollipop rom? i dont feel like beeing THAT professional, to be honest. but i will check if i can use something for more stability on kk. thanks for the information, though! maybe i can find something to fix "reboot to recovery"-freeze
I got my current rom (carbon rom 4.4.4) from this website:
http://mateone4you.blogspot.nl/2015/04/carbon-rom-444-for-huawei-ascend-mate.html
He has a few more too.
Edit: I guess you know, reading your CM thread, but some may not....
Would welcome some more development, especially bluetooth connecting to audio is horrible...
I tried his other roms too, only got carbon working nicely.
SvenHee said:
I got my current rom (carbon rom 4.4.4) from this website:
http://mateone4you.blogspot.nl/2015/04/carbon-rom-444-for-huawei-ascend-mate.html
He has a few more too.
Edit: I guess you know, reading your CM thread, but some may not....
Would welcome some more development, especially bluetooth connecting to audio is horrible...
I tried his other roms too, only got carbon working nicely.
Click to expand...
Click to collapse
yeah, that's Alex Midnight (mrAlmid), i used some huawei binaries off his roms already.
i will see what i can do about bluetooth a2dp, dont have to much hope though, that a2dp stuff was a hell on LG's p990 already.

Categories

Resources