Related
So... i know that there aren't any devs working on modifying the kernels from the 2.3 Sense Leak, but this is something I dont really understand.
Netarchy and crew (among many others) had kernels pushed out for the EVO WAAAAYYY before they released any source info. and even when we moved to 2.2, there were kernels ready soon after.
Obviously, the brightness fix is in a ton of working 2.2 kernels. Why cant we pull that out and put it in another kernel? Maybe add SBC and/or some battery tweaks?
I know that devs dont want to have to start over if there is a major difference in the Kernels from beta to release, but what would be the major change? Wouldnt the 2.3 be a good place to start messing around, and then make small adjustments when the full kernel is released? You could easily get a leg up on other devs and incorporate it into the TONS of 2.3 Roms that are out there now.
Im ignorant as hell when it comes to kernels and compiling, but speaking on a tiny modicum of common sense, there should be a way to prod and poke this kernel into submission.
ignore me if in being dumb. I just felt like i had to ask this.
EDIT:
Id like to keep this a conversation between people who want this and people who know. Please dont add your 2cnts in to say the same things we have all heard (we need source, cant do it, no reverse engineering, blah blah)
If you are a dev and can give some REAL PROPER insight, we would love to hear it. even if its to tell us to stuff it LOL.
rawdikrik said:
So... i know that there aren't any devs working on modifying the kernels from the 2.3 Sense Leak, but this is something I dont really understand.
Netarchy and crew (among many others) had kernels pushed out for the EVO WAAAAYYY before they released any source info. and even when we moved to 2.2, there were kernels ready soon after.
Obviously, the brightness fix is in a ton of working 2.2 kernels. Why cant we pull that out and put it in another kernel? Maybe add SBC and/or some battery tweaks?
I know that devs dont want to have to start over if there is a major difference in the Kernels from beta to release, but what would be the major change? Wouldnt the 2.3 be a good place to start messing around, and then make small adjustments when the full kernel is released? You could easily get a leg up on other devs and incorporate it into the TONS of 2.3 Roms that are out there now.
Im ignorant as hell when it comes to kernels and compiling, but speaking on a tiny modicum of common sense, there should be a way to prod and poke this kernel into submission.
ignore me if in being dumb. I just felt like i had to ask this.
Click to expand...
Click to collapse
Unfortunately, there is nothing that can be done until HTC releases source code for the kernel, or until HTC releases a new, working kernel. The kernel that is out now, that causes the brightness issue, is basically an incomplete kernel, from a leaked rom. Something that is fully working, and more stable is needed.
k2buckley said:
Unfortunately, there is nothing that can be done until HTC releases source code for the kernel, or until HTC releases a new, working kernel. The kernel that is out now, that causes the brightness issue, is basically an incomplete kernel, from a leaked rom. Something that is fully working, and more stable is needed.
Click to expand...
Click to collapse
I appreciate you saying that... but it doesnt explain why we had kernels for 2.1 and 2.2 before any source was released. I would like to hear from the devs directly.
Thanks for chiming in though.
From the little and probably wrong information I'm making up, you can't decompile kernels from a Rom, you need source to download from, then apply your mods and then can compile a fixed kernel
Edit: complete speculation, if it is in fact true i will modify post to reflect my all knowing powers
NewZJ said:
From the little and probably wrong information I'm making up, you can't decompile kernels from a Rom, you need source to download from, then apply your mods and then can compile a fixed kernel
Click to expand...
Click to collapse
Thank you... but this is what I am trying to avoid. Id like to remove the misinformation and get a real set of reasons and information. We can all speculate. I want a real answer... and im sure im not the only one.
rawdikrik said:
Thank you... but this is what I am trying to avoid. Id like to remove the misinformation and get a real set of reasons and information. We can all speculate. I want a real answer... and im sure im not the only one.
Click to expand...
Click to collapse
Can't make kernels unless they are 1.) reverse-engineered 2.) or HTC releases the source code for a specific device.
Too time consuming. And by the time, it goes through a psuedo-SDLC, HTC would have probably already released the newest one and devs here already working on a custom kernel.
Hope that answers your question
I believe net said he would work on one as soon as the source is released....I think I read it in his thread
Sent from my PC36100 using XDA App
pinky059 said:
Can't make kernels unless they are 1.) reverse-engineered 2.) or HTC releases the source code for a specific device.
Too time consuming. And by the time, it goes through a psuedo-SDLC, HTC would have probably already released the newest one and devs here already working on a custom kernel.
Hope that answers your question
Click to expand...
Click to collapse
So in other words the reasons that they arent bothering is because they dont want to invest the time when it could become obsolete before it is even released?
mutant13 said:
I believe net said he would work on one as soon as the source is released....I think I read it in his thread
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I dont see that happening any time soon.
Not only that, but i think i remember NET working on one before any source came out for 2.2 and 2.1, especially to fix the FPS cap.
I think that he didnt want to touch it because it is beta and can change between now and an official 2.3 release, like most devs have stated.
rawdikrik said:
I appreciate you saying that... but it doesnt explain why we had kernels for 2.1 and 2.2 before any source was released. I would like to hear from the devs directly.
Thanks for chiming in though.
Click to expand...
Click to collapse
Not a problem. I don't have an answer for you about kernels being released for 2.1 and 2.2 before source was released, other than that you're most likely mistaken about that. Based on what I've been told by devs, and what I've seen devs say (netarchy said he'd work on this kernel as soon as source was released, and that there was nothing that could be done prior to source being released....he said it in his kernel thread), it is nearly impossible to mod/tweak a kernel without the source code. Without source code, it would need to be reverse engineered. By the time that was to happen, a new kernel would already be released most likely.
That's all I got on that issue. So basically, no custom kernels without kernel source.
k2buckley said:
Not a problem. I don't have an answer for you about kernels being released for 2.1 and 2.2 before source was released, other than that you're most likely mistaken about that. Based on what I've been told by devs, and what I've seen devs say (netarchy said he'd work on this kernel as soon as source was released, and that there was nothing that could be done prior to source being released....he said it in his kernel thread), it is nearly impossible to mod/tweak a kernel without the source code. Without source code, it would need to be reverse engineered. By the time that was to happen, a new kernel would already be released most likely.
That's all I got on that issue. So basically, no custom kernels without kernel source.
Click to expand...
Click to collapse
I may very well be COMPLETELY WRONG. LOL. Im not against that. I am right now doing my homework to confirm what ive been thinking.
EDIT: After doing some homework, it looks like Net and Toast were making changes to the stock 2.1 kernel before any source was released. This i remember because the 2.2 Kernels that they first made broke the camera, which wasnt fixed until the source was released. I remember waiting with my hand over f5 til HTC released the source.
They we working hard on using Kernels from other devices and tryign to get the FPS cap removed along with getting the HDMI working.
All i did was go over this ANCIENT thread
http://forum.xda-developers.com/showthread.php?t=719763&highlight=source
rawdikrik said:
I may very well be COMPLETELY WRONG. LOL. Im not against that. I am right now doing my homework to confirm what ive been thinking.
EDIT: After doing some homework, it looks like Net and Toast were making changes to the stock 2.1 kernel before any source was released. This i remember because the 2.2 Kernels that they first made broke the camera, which wasnt fixed until the source was released. I remember waiting with my hand over f5 til HTC released the source.
They we working hard on using Kernels from other devices and tryign to get the FPS cap removed along with getting the HDMI working.
All i did was go over this ANCIENT thread
http://forum.xda-developers.com/showthread.php?t=719763&highlight=source
Click to expand...
Click to collapse
Well, maybe there are certain things that can be worked on without source, but I believe for this type of problem (brightness issue), source is needed. Probably similar to how you said that the 2.2 kerneles broke the camera at first, and couldn't be fixed until source was released. This is the same type of deal. Hopefully Sprint will release an OTA within 30-60 days. I wouldn't get my hopes up for anything before that, unfortunately.
k2buckley said:
Well, maybe there are certain things that can be worked on without source, but I believe for this type of problem (brightness issue), source is needed. Probably similar to how you said that the 2.2 kerneles broke the camera at first, and couldn't be fixed until source was released. This is the same type of deal. Hopefully Sprint will release an OTA within 30-60 days. I wouldn't get my hopes up for anything before that, unfortunately.
Click to expand...
Click to collapse
The word around the grapevine is that sprint isn't releasing the OTA until after the release of the evo 3d (marketing scheme, you know how it is).
AbsolutZeroGI said:
The word around the grapevine is that sprint isn't releasing the OTA until after the release of the evo 3d (marketing scheme, you know how it is).
Click to expand...
Click to collapse
I heard that too. That wont be til June/July and then they have another 60days of waiting time they usually take to release source.
and that is IF They do the upgrade, since usually they only want a single upgrade in the life cycle of a product. They will most likely REALLY think about it, to not risk stealing sales from the newer phones coming out over the summer.
AbsolutZeroGI said:
The word around the grapevine is that sprint isn't releasing the OTA until after the release of the evo 3d (marketing scheme, you know how it is).
Click to expand...
Click to collapse
Correct. I predict the 3D to drop within 30-60 days from now though. Then shortly after that, the OTA will probably roll out. As rawdikrik said, source will probably come a month or two after the OTA. The good thing though, is that if/when an OTA is released, it will have a working kernel in it. So even without source being released, a working kernel will be in circulation at that point, which will most likely resolve the brightness issue.
Evo 3D is supposedly hitting June so I'm going to say July just to give it some breathing room. If OTA hits around August maybe September, then its another 30-45 days to release source. So were talking around September-October ish for complete source. This is all speculation but sprint/HTC operate that way. My guess is september for a fully working kernel for GB based on the source code. Stupid marketing scheme to get us to buy the evo 3D.
Sent from my PC36100 using XDA Premium App
I'm so going to buy the EVO 3d
not sure how i feel about the 3d gimmick...
Can we keep this on topic though? THanks guys... Im just waiting to hear something from the big dogs.
Keep in mind it's entirely possible that we will see another leaked kernal long before the OTA is out, this one fully functional. This is especially true if(as many of you seem to suspect) this "leak" was actually no leak at all but an intentional way to let the Chefs and Power Users test their new ROM for them and get feedback on it.
Not sure if you (the Op) have ever tried programming... But (in perspective of the difficulty), basically this would be like me writing a "Hello World" app in Java or C++, and it having an extra space in between the words that bothered you. You would have to cipher through hundreds of lines of code in a hexidecimal editor trying to find the "call" to the display API, and then find which variable or constant it was using for the text output, and change it.
Then you would have to re-compile, and hope it worked without breaking anything else already in place. If you broke something, it's INCREDIBLY hard to debug without real source code.
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.
Hi guys,
So for the past week I think I have at least wiped/flashed/Odin'd different ROMs for my new Captivate Glide at least a hundred times. I've finally settled on thegreatergood's LiteROM 0.9.0 and it's working great for me. Not only the one ROM though as I've had to find many workarounds for different things. Flashables/kernels/apks you name it. Although I have no regrets and I'm really proud of how It's like a beast in my pocket, I am quite bothered by one thing which is that the whole thing feels like a big piece of patchwork..
Coming from a HTC Desire Z running CM7 serving me loyally for many years, I miss that officiality (<-- oops, red snakes.. not sure that's a word. Whatever. Shakespeare made his own words too right? ) and the stability that CM7 offered.
I'm a humble man, and possibly carry the apologetic traits of a typical Canadian. Instead of whining and/or nagging some senior developer to hurry up on their ICS or JB development I've decided to build my own CM instead.
However some thought, I think the reason why the JB based experimental CM 10.1s for the Captivate Glide have been a difficult task is because it's probably quite a challenge to build something from something that's not currently very well understood, namely the JB. So I thought, why not just build I nice and stable ROM based off of GB and if it does well it could probably officiated as a CM7 port for the Captivate Glide.
I have a feeling that this is a very plausible task. But I have no way to do it alone.. I have zilch experience in development in anything, had to drop out of my C++ course and have been doing nothing but lurking and leeching since I started modding when I was eleven. All I have is a vision. If someone could point me in the right direction or even form a development team with me, I would be very grateful.
And if this goes well, I will have gained some long overdue experience
So.. Anyone?
P.S. I guess this goes in this forum too. But my phone gets real angry when I flash certain things onto it. The biggest issue currently is that it will freeze and crash (more specifically the screen will freeze and fade into white lines..) whenever I try to use ClockWorkMod Recovery.. I dunno if the crappy 1500 mAh China battery I got ripped off with is an issue but I'm waiting on an OEM one in the mail..
Post in general not development bub...
And were on cm 10. Why fall back?
Sent from my SGH-I927 using xda app-developers app
I intend to turn it into development thread. But will have a better audience over General?
And maybe see it more like an educational project with a usuable product?
Sent from my SGH-I927 using xda app-developers app
hey bud im with you ... though I think CM9 would be better as ICS has been released, stable, and has a few more tweaks and features that CM7 didn't ... things like in JB where we have a transparent notification pull down, control over the dpi of certain apps etc.
First thing you should do is readup on the compile cm10 from source thread, get your feet wet there it'll get you all setup with a development system .. Linux is a must so I hope that you're savvy in the *nix shell or things will be antagonistic right off the start ...
I installed the CM9 recently and radio etc didn't work .. Guaranteed there is tonnes of information across all devices on xda-developers and even in general development threads.
Scroll through these forums, find the github links and learn how to setup your own, download the sources for the kernels from the other devs (theres a couple CM10.1s out there).
CM7 .. while I appreciate where you're coming from as i LOVED having CM7 on my Galaxy ACE - everything just worked... battery was great, it looked cool, and it was just off the stock enough to be unique and rub in iPhone users' faces
If I had the time I'd take it on with you .. chart your work and links that have helped you as you go along.
maybe he say that, because the glide have GB and ics officialy and not JB, so, if i understand what he say, maybe a romCM based y that version can be more stable, and less bugs, i was thinking about a CM9 too. But, if i remember correctly, it must create a device tree and a lot of thing, but i am not sure becausea never do a rom.
lorddavid said:
maybe he say that, because the glide have GB and ics officialy and not JB, so, if i understand what he say, maybe a romCM based y that version can be more stable, and less bugs, i was thinking about a CM9 too. But, if i remember correctly, it must create a device tree and a lot of thing, but i am not sure becausea never do a rom.
Click to expand...
Click to collapse
CM9 is based on ICS 4.0.4 ...
Check this link, not for our device but it offers some good insight to CM7 : http://forum.xda-developers.com/showthread.php?t=1273718
Another one for CM9 : http://forum.xda-developers.com/showthread.php?p=20844007
.... maybe I should just build a linux VM and give it a go in my spare time .... we're so starved for developers for our glides even amateur contributions can't hurt .... in the 2nd link the guy said it took him 11 months to learn how to mod for ICS from no experience so ..... depends on how much you want to commit to it ..
yohan4ws said:
CM9 is based on ICS 4.0.4 ...
Check this link, not for our device but it offers some good insight : http://forum.xda-developers.com/showthread.php?t=1273718
Click to expand...
Click to collapse
yes, i know that, and i was thinking that a cm9 (because there is a ics fully working in the glide) can be a good option, but not sure
This doesn't belong here, please, some mod, move this to General. Thanks
chrisyjwai said:
I intend to turn it into development thread. But will have a better audience over General?
And maybe see it more like an educational project with a usuable product?
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Flagged to be moved to general. If this turns into a dev thread, then you can flag to move it to the dev section, but you only post in the dev sections if you actually have a product or are actively working on something.
Your intentions seem great, but never wait for someone else to help you, otherwise it will never get done. No one is going to carry you through learning this.
There's a ton of guides out there on how to build, port, cherry pick CM commits, etc. etc. Go find them and start learning. Ask SPECIFIC questions if you have any.
No one shows up to college on day 1 and says I'd like to learn how to be a doctor, engineer, pharmacist, journalist, etc. There's a lot of steps in between. So go and get started.
gtmaster303 said:
No one shows up to college on day 1 and says I'd like to learn how to be a doctor, engineer, pharmacist, journalist, etc.
Click to expand...
Click to collapse
That doesn't make any sense.... lots of people show up to college and say that, and then enroll in the courses to do that ..
What is with the lack of custom roms for our phone? Is it the lack of devs who own the device, or is it the lack of open source resources for our device? Thanks for your responses.
We have more roms than the international version. What are you crying about?
helikido said:
We have more roms than the international version. What are you crying about?
Click to expand...
Click to collapse
I think we have what, two roms right now? And they're both stock (one is deodexed), so really not a whole lot to choose from right? (And I mean absolutely no disrespect to Devs. I know this process, I've been around a while now. It takes time to get up and running.)
But I know, and feel what the op is saying. Normally by now, we'd at least have some more things going on as far as roms, and especially kernels. What I'm most excited for is aosp or cm. I really miss stock android, and I think this phone would benefit a whole lot from it as far as battery life and fluidity.
But I can be patient... I think
Sent from my LG-D851 using XDA Free mobile app
nory82688 said:
I think we have what, two roms right now? And they're both stock (one is deodexed), so really not a whole lot to choose from right? (And I mean absolutely no disrespect to Devs. I know this process, I've been around a while now. It takes time to get up and running.)
But I know, and feel what the op is saying. Normally by now, we'd at least have some more things going on as far as roms, and especially kernels. What I'm most excited for is aosp or cm. I really miss stock android, and I think this phone would benefit a whole lot from it as far as battery life and fluidity.
But I can be patient... I think
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
Dont worry bro the devs probably barely got their devices rightnow. We dont know what they are planning. But they will be coming and you will be first to enjoy a fully custom phone and quench the thirst. I have it too. The fact that the bootloader is unlocked for tmbile make me relieved[emoji27]
nory82688 said:
I think we have what, two roms right now? And they're both stock (one is deodexed), so really not a whole lot to choose from right? (And I mean absolutely no disrespect to Devs. I know this process, I've been around a while now. It takes time to get up and running.)
But I know, and feel what the op is saying. Normally by now, we'd at least have some more things going on as far as roms, and especially kernels. What I'm most excited for is aosp or cm. I really miss stock android, and I think this phone would benefit a whole lot from it as far as battery life and fluidity.
But I can be patient... I think
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
I could be way off here but if you want aosp you better start compiling it. For some reason I doubt we will see official aosp or aokp until one of us gets the ball rolling on github. I would but the idea of being a guinea pig for the kernel scares me off. If anyone knows of it officially being worked on please correct me.
I wish i could help unfortunately I cant code very much.. Anyways I cant wait for some LG G3 custom ROM love. :good:
It took almost 2 months for the first AOSP rom to start showing up for the G2, and that had less exposure. It just takes time.
Sent from my LG-D851 using XDA Free mobile app
Be patient. Device just recently came out. The fact we even have a full root and 2 flavors of stock is nice already given the time
I like LG's take on Android. I'd be happy with a properly debloated rom and custom kernel.
ThePagel said:
I could be way off here but if you want aosp you better start compiling it. For some reason I doubt we will see official aosp or aokp until one of us gets the ball rolling on github. I would but the idea of being a guinea pig for the kernel scares me off. If anyone knows of it officially being worked on please correct me.
Click to expand...
Click to collapse
Trust me, If I could code, I wouldve started by now lol, but as far as I've seen , there is a guy messing with a 4.4.4 aosp build or Android L build in the general section of the T-Mobile threads. From what I've read he's responsible for the Android L port to the Nexus 4, so at least we have someone digging at it.
Other than that I haven't seen anything else.
This is my first non nexus LG smartphone , so forgive me if Im not privy to how long development normally takes. All I can say is I'm definitely excited to see something
Sent from my LG-D851 using XDA Free mobile app
I dont know how develpoment is now on the the G2 but when i had it there wasnt much going on there, I think i flashed international roms on that device, would that be possible with the G3?
unciviilized said:
I dont know how develpoment is now on the the G2 but when i had it there wasnt much going on there, I think i flashed international roms on that device, would that be possible with the G3?
Click to expand...
Click to collapse
With the G2 you could do that as long as you had a D801 kernel to flash on top of it. Might be the same here.
I wanted to compile AOSPA (paranoid android for those who don't know), but couldn't find the device tree for this device. Someone answered me on here and said that they needed to be built and none were available at this time.
That's what we're waiting for to get any type of AOSP rom on this device. I looked into building it myself, but it's a bit over my head.
Hello everybody.
So I was wondering, when CyanogenMod 12 comes out, will they still support all of the devices they have been supporting? Or at least, in specific, our device? I can't imagine why'd they drop support.
Also, I hear in the new Android version, the Linux 3.10 kernel is being used. As opposed to the current 3.4 kernel we are using. Does anybody know about any significant changes between the two?
This is very exciting if/when we get this on our device I personally will just wait on a CM or AOSP version of Android as stock never really does it for me.
I don't know, but the more I think about it, the more excited I get (also the more apprehensive I get since I'll have to upgrade my kernel sources).
I know I probably shouldn't bring this up, but I also can't wait to blow my friend's new iOS 8 update out of the water with CM12/L (Not like CM11 doesn't already do that )
Snepsts said:
Hello everybody.
So I was wondering, when CyanogenMod 12 comes out, will they still support all of the devices they have been supporting? Or at least, in specific, our device? I can't imagine why'd they drop support.
Also, I hear in the new Android version, the Linux 3.10 kernel is being used. As opposed to the current 3.4 kernel we are using. Does anybody know about any significant changes between the two?
This is very exciting if/when we get this on our device I personally will just wait on a CM or AOSP version of Android as stock never really does it for me.
I don't know, but the more I think about it, the more excited I get (also the more apprehensive I get since I'll have to upgrade my kernel sources).
I know I probably shouldn't bring this up, but I also can't wait to blow my friend's new iOS 8 update out of the water with CM12/L (Not like CM11 doesn't already do that )
Click to expand...
Click to collapse
I'm so excited about this. It will be sooooooo cool. I need to learn to develop ROMs and stuff, because if developer support dies for this phone I would want to keep the development going.
Well then start now rjm....... Better now then never
2SHAYNEZ
rjmxtech said:
I'm so excited about this. It will be sooooooo cool. I need to learn to develop ROMs and stuff, because if developer support dies for this phone I would want to keep the development going.
Click to expand...
Click to collapse
You'll have me doing the little bit I can for this device for the next 8-9 months I'm stuck with this thing
Don't worry about developing ROMs, all you really need to know is how to compile and maintain. I plan to attempt at some unofficial builds of a ROM or two once I can deem my kernel as done. But don't worry, the LG OGP is definitely booming with activity right now, and will probably only get better with the following months to come.
We already have:
Gummy
PAC
Beanstalk
CM11
AOKP
AICP
Vanir
and a pretty good range of stock ROMs.
Soon (and I mean within a month or so) I hope to add Carbon and Paranoid Android to this list, but we will have to see. I do not know how to compile unofficially or much about it, but it doesn't look extremely difficult. So my hopes are high.
Plus, as this device drops in price, we may get some more people to keep development for this device relevant. Although I did not see our device in the local AT&T store last time I was there...
We have a beautiful phone with the processing power to last as a quality device for another year at least. LG makes some pretty nice stuff.
Unfortunately, we will be seeing more and more of our users leave as the months drag on as this phone gains age
We'll have to see who lasts the longest with this phone as their primary device... lol.
I suspect we will reach our peek in ROMs soon a few months after Android L is up and running. Just my guess though.
Shayne has a good point though, now is definitely the time to start. So better hit the tutorials!
Snepsts said:
You'll have me doing the little bit I can for this device for the next 8-9 months I'm stuck with this thing
Don't worry about developing ROMs, all you really need to know is how to compile and maintain. I plan to attempt at some unofficial builds of a ROM or two once I can deem my kernel as done. But don't worry, the LG OGP is definitely booming with activity right now, and will probably only get better with the following months to come.
We already have:
Gummy
PAC
Beanstalk
CM11
AOKP
AICP
Vanir
and a pretty good range of stock ROMs.
Soon (and I mean within a month or so) I hope to add Carbon and Paranoid Android to this list, but we will have to see. I do not know how to compile unofficially or much about it, but it doesn't look extremely difficult. So my hopes are high.
Plus, as this device drops in price, we may get some more people to keep development for this device relevant. Although I did not see our device in the local AT&T store last time I was there...
We have a beautiful phone with the processing power to last as a quality device for another year at least. LG makes some pretty nice stuff.
Unfortunately, we will be seeing more and more of our users leave as the months drag on as this phone gains age
We'll have to see who lasts the longest with this phone as their primary device... lol.
I suspect we will reach our peek in ROMs soon a few months after Android L is up and running. Just my guess though.
Shayne has a good point though, now is definitely the time to start. So better hit the tutorials!
Click to expand...
Click to collapse
If you could keep Beanstalk going for our device if development stops I would greatly appreciate it. I'll try and help out too when I learn how in case development does stop.
rjmxtech said:
If you could keep Beanstalk going for our device if development stops I would greatly appreciate it. I'll try and help out too when I learn how in case development does stop.
Click to expand...
Click to collapse
I have a feeling that we don't have to worry about Beanstalk
No it won't stop..... Aicp has seemed to come to a hault .. Maybe you should jump on that rmj..... Read read read and then read .... Then compile yo stuff
2SHAYNEZ
shayneflashindaily said:
No it won't stop..... Aicp has seemed to come to a hault .. Maybe you should jump on that rmj..... Read read read and then read .... Then compile yo stuff
2SHAYNEZ
Click to expand...
Click to collapse
It seems as though a lot of ROMs by that particular dev get abandoned eventually... but that's none of my business.
Yes AICP would be a great one to start on, first thing is first though, rjm, get yourself on a Linux VM or a Linux computer. Also, I hope you have some decent specs or it'll be hell trying to do it.
For example, I have an AMD FX-6350, so I have 6 cores in my system. I can allocate 4 to my VM
And you'll want some RAM, too. Like 8 GB so if you're using a VM you can allocate 4 as well.
For the distro I suggest using Linux Mint 64-bit (has to be 64-bit).
And I really hope your host OS is 64-bit, because otherwise you are probably incapable of compiling ROMs.
Best of luck!
P.S: I downloaded Carbon sources today. We'll see how that goes.
Oh also be sure you have PLENTY of free space, those sources love hogging space. I just cleaned out my old VM and set up a new one with 200 GB of space allocated. Thank God for Terabyte HDDs
Staying on topic, the L/5.0 SDK was released today. Approx. two weeks until the official Nexus release, and hopefully not too long until we get a taste of that afterwards.
KitKat was great (it felt like the smoothest Android experience ever when I flashed my first KK ROM) but I'm ready for Lollipop!
Material design looks interesting, although I gotta say... the circle triangle square virtual buttons aren't the best design choice imo. Maybe it's to make switching from an iPhone to an Android easier for the iUsers that find the current system to difficult to understand :laugh: They sure like their shapes of rounded edge squares and circles.
I'm not kidding, actually. A friend of mine steals my phone all the time and she cannot figure out PIE to save her life...
shayneflashindaily said:
No it won't stop..... Aicp has seemed to come to a hault .. Maybe you should jump on that rmj..... Read read read and then read .... Then compile yo stuff
2SHAYNEZ
Click to expand...
Click to collapse
I don't think I want to compile AICP. Beanstalk is the only ROM IMO that really would be a loss if development stopped. The features of Beanstalk outnumber those of other ROMs
rjmxtech said:
I don't think I want to compile AICP. Beanstalk is the only ROM IMO that really would be a loss if development stopped. The features of Beanstalk outnumber those of other ROMs
Click to expand...
Click to collapse
What about compiling it for the sake of learning how to compile...?
Snepsts said:
What about compiling it for the sake of learning how to compile...?
Click to expand...
Click to collapse
Maybe
rjmxtech said:
I don't think I want to compile AICP. Beanstalk is the only ROM IMO that really would be a loss if development stopped. The features of Beanstalk outnumber those of other ROMs
Click to expand...
Click to collapse
Is Beanstalk as stable as cm11. Does it have a RC or something similar to PAC or M11?
dpalmer76 said:
Is Beanstalk as stable as cm11. Does it have a RC or something similar to PAC or M11?
Click to expand...
Click to collapse
I'm pretty sure Beanstalk only releases stable updates. From what I remember there aren't any nightlies, as it sometimes is months before a new update is released. That is another reason why I like Beanstalk better than other ROMs.
I will be happy to see official LG update for Android Lollipop 5.x Waiting for updates!
rahib172 said:
I will be happy to see official LG update for Android Lollipop 5.x Waiting for updates!
Click to expand...
Click to collapse
Not much news from lg on updates yet:
http://www.androidauthority.com/which-phones-android-lollipop-540232/
---------- Post added at 05:11 PM ---------- Previous post was at 05:05 PM ----------
rjmxtech said:
I don't think I want to compile AICP. Beanstalk is the only ROM IMO that really would be a loss if development stopped. The features of Beanstalk outnumber those of other ROMs
Click to expand...
Click to collapse
Probably a sort of noobish question, but anyway many roms are cm-based (including beanstalk), and even aokp is cm enabled. How dependent are these roms on cm, basically meaning could they sustain themselves without cm continuing support too?
abumy said:
Not much news from lg on updates yet:
http://www.androidauthority.com/which-phones-android-lollipop-540232/
---------- Post added at 05:11 PM ---------- Previous post was at 05:05 PM ----------
Probably a sort of noobish question, but anyway many roms are cm-based (including beanstalk), and even aokp is cm enabled. How dependent are these roms on cm, basically meaning could they sustain themselves without cm continuing support too?
Click to expand...
Click to collapse
I think CM official support is close to vital for these ROMs, mainly for the kernel, but also because they update the device thingy you use to build ROMs I do believe.
I am 90% sure we will receive updates from CM though. They sure know how to take care of their devices.
Any custom ROM will do, if we are talking about testing the new Android L. What's bothering me is the support for F240x devices. If CM, Beanstalk, VANIR/COMMOTIO or AICP (the one I am using for a long period of time), will release an update, will there be a KERNEL or ROM that will work for the F240x?
MitoTakatori said:
Any custom ROM will do, if we are talking about testing the new Android L. What's bothering me is the support for F240x devices. If CM, Beanstalk, VANIR/COMMOTIO or AICP (the one I am using for a long period of time), will release an update, will there be a KERNEL or ROM that will work for the F240x?
Click to expand...
Click to collapse
I really hope it is for your sake. Luckily the dev that makes F240 ROMs for you guys seems to know what he's doing, and I'm sure he'll keep working for you. As long as e980 has support he can use that kernel and use it for F240.
Snepsts said:
I really hope it is for your sake. Luckily the dev that makes F240 ROMs for you guys seems to know what he's doing, and I'm sure he'll keep working for you. As long as e980 has support he can use that kernel and use it for F240.
Click to expand...
Click to collapse
Hopefully.