Related
Can someone building this app from github? It looks pretty cool, but I don't know how to build nor do I think I have the equipment to.
Thanks!
Link: http://onskreen.com/cornerstone/index.php
Sent from my GT-P7510
I think I can f*p to this
Developers, please help! , this could help take multitasking on android tablets to a whole new level!
Would like to see this myself!
Thats really really cool, hope the developers here will do a build with ICS with that fantastic experiment!
CyanogenMod team is working in building it into CM9.
Think it's only compatible with ics and gingerbread when ics is more common on devices I think more cooks will add it. I can't believe their is not more interest from dev on this. Cm9 and Thor, are building this into their rom.
Not an APP. This has to be built into the ROM itself. I have been searching for the "user built ROMS" on Onskreen's website but with no luck. CMteam is adding it to CM9 but a flashable zip to drop the right files into the right places would be increadible. This would give most people the option to use what ROM they want and then flash the "Cornerstone into said ROM. I am excited about this.
Including this into the ROMs might make Google decide to pull ROMs out of access to the Android Market I've read.
Not sure if and how this would all pan out.
edit: if CM would include this as an optional package that would remove the risk of excluding ROMs to the market, nice find mtjnkee
work in progress? or already an app ready?
I thunk it'll still a work in progress.
Sent from my GT-P7510
http://forum.aokp.co/topic/38-build-23-special-onskreen-edition-wifi-only/
Roman from the aokp rom has a special edition of his rom with cornerstone built in. It is buggy (onskreen needs to fix it up a bit), but if you want to test it out here it is. For the wifi 10.1
Sent from my GT-P7510 using Tapatalk
task650 said:
CyanogenMod team is working in building it into CM9.
Click to expand...
Click to collapse
It's in an overnight build of AOKP--a one-time thing, I believe. It has a long way to go to be generally useable.
Skilover said:
It's in an overnight build of AOKP--a one-time thing, I believe. It has a long way to go to be generally useable.
Click to expand...
Click to collapse
Yes but when I made the original post he hadn't included it yet.
Any roms for the a500 with this built in yet. Available now?
I think that once more devices start to implement ICS then we will see a much faster development time for these sort of OS enhancements
task650 said:
CyanogenMod team is working in building it into CM9.
Click to expand...
Click to collapse
For interested readers: plus(dot)google(dot)com/117962666888533781522/posts/bPKE7qtvwC9 CyanogenMod - The Cornerstone Breakup
So IMHO they're more on building an own solution to this, taking Cornerstone as an origin.
If anyone has a Touchpad laying around there is an CM9 Kang ROM with Cornerstone baked in over in the Touchpad development section.
http://forum.xda-developers.com/showthread.php?t=1501637
Any progress?
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 know this is going to be a somewhat complicated process, but I'm willing to stick with it.
I'm willing to upgrade to any ROM, really, I'm not picky. If nobody suggests anything different, I'll just go with Cyanogenmod. What I really want is Android M running on the device as soon as possible. Which ROM gets that update out the quickest? I'm a complete beginner at everything you can think of, but I can read and I have a computer, so I can follow tutorials just fine.
Any ideas which ROM I should upgrade to when the time comes? (I mean, if any developers have announced the update to M and their support for the Mate2). If not, my main question is when will Cyanogenmod developers start building on Android M? And when do you think it will get over to the Mate2?
EDIT: I know it hasn't come out yet, but sometimes developers announce that their ROM will be based on some new version of android before it even comes out.
Both PAC and CM are nice. I run CM because I prefer the stick android experience . PAC has more bells and whistles. Personal preference really. SuperBass has made videos on both of them. As well as installing each one.
M will probably never make it to the HAM2. CM works great and is easy to install. Just jump in there with both feet.
kimtyson said:
M will probably never make it to the HAM2. CM works great and is easy to install. Just jump in there with both feet.
Click to expand...
Click to collapse
Well, to get there, I'd have to downgrade to Jellybean, upgrade to Lollipop, and then start the CM install, which I'm likely to **** up. It's gonna be more like a couple of slow hops in different directions.
kimtyson said:
M will probably never make it to the HAM2. CM works great and is easy to install. Just jump in there with both feet.
Click to expand...
Click to collapse
Yeah, I was wondering about M. So the official Huawei devs won't update to Android M, but won't CM be updated to be based on it? Is that how it works, or am I mistaken?
I am under the impression that CM has official developers who actually work on the ROM. Then other developers use that and make it available for different devices. Therefore, Android M will be coming to the Mate2 as long as CM is updated by the official developers and it gets support for the device, right?
Mackks said:
Yeah, I was wondering about M. So the official Huawei devs won't update to Android M, but won't CM be updated to be based on it? Is that how it works, or am I mistaken?
I am under the impression that CM has official developers who actually work on the ROM. Then other developers use that and make it available for different devices. Therefore, Android M will be coming to the Mate2 as long as CM is updated by the official developers and it gets support for the device, right?
Click to expand...
Click to collapse
No, that's not how it works, actually. Huawei would have to release the HAM2 specific M code for other ROMs to use it. I am about 99.9 percent sure that Huawei will not build M for the HAM2 so it dies on the vine, so to speak.
kimtyson said:
No, that's not how it works, actually. Huawei would have to release the HAM2 specific M code for other ROMs to use it. I am about 99.9 percent sure that Huawei will not build M for the HAM2 so it dies on the vine, so to speak.
Click to expand...
Click to collapse
So CM isn't a base that device developers tweak to work with specific devices? Do you mean that CM is developed over what the phone manufacturers release?
Mackks said:
So CM isn't a base that device developers tweak to work with specific devices? Do you mean that CM is developed over what the phone manufacturers release?
Click to expand...
Click to collapse
Devs need manufacturer kernel source to build off of. Someone can PORT M to this phone. But I seriously doubt that happens. Huawei will surely NOT release M. They barely managed L. And that was only due to so many complaining about no support.
Mackks said:
So CM isn't a base that device developers tweak to work with specific devices? Do you mean that CM is developed over what the phone manufacturers release?
Click to expand...
Click to collapse
Yes, CM is often used as a base that other devs use to add their stuff on top of. But, if the manufacturer doesn't release their code (which includes drivers and such), then there will be no CM. Yes, CM is developed over what the phone manufacturers release.
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.