Develop Bugs

[WIP] 3.4 Kernel for d2 (qcom sgs3)

Hello.
I have a kernel based on CAF's jb_2.5 branch booting on d2spr.
Source is here.
Status currently is: userland comes up (working panel) and seems to be functioning properly, with the caveat that pretty much all peripherals are broken. USB also works - so this project really is a developer's dream: plethora of mini problems to work on and a wealth of debugging information readily available.
Up until this point, I could focus on specific problems with the boot process and tackle them one by one. However now, there are dozens of directions one could go in, so I am posting this with the hopes of soliciting some help from like-minded individuals with experience in kernel porting. Work is also picking up for me, and I really need to offload some of this kernel work. Plus, I am burning a hole through my boot partition flashing/re-flashing, and it really is no fun doing this alone.
A bit of background: I used CAF's jb_2.5 branch because it is closest to being compatible with the userland HAL (display-caf in particular) currently used in cm10.1. I also have CAF's msm-3.4 branch booting, but the panel headers in userland are too far apart.
I tried to be surgical with the alterations: rather than mass merges, I tried to insert drivers individually (with the exception of media/video where samsung seems to have done an amazing job of crapping all over qcom's already non-upstreamed v4l2/camera/media code). The upshot of this is, we get rid of all the extraneous samsung crap. The downside is things are harder to fix.
The priorities as I see them:
1. Get d2vzw, d2tmo, d2att (etc) off the ground. Currently I only have board files for d2spr since this is the device I own, but someone with the right device and skill set should be able to invest couple of hours to follow my commits and get their version up.
2. Sound.
3. WiFi/Bluetooth. (invisiblek)
4. Camera
So let's get this going.

I wish we could put an effort to make this happen on Midas...
But really this is the wrong forum, the Qualcomm devices are truly on a completely different platform, there is little to no shared code here. Anyway good luck with it...

This honestly belongs in one of three places.
I am very interested in this work though.
http://forum.xda-developers.com/forumdisplay.php?f=1672
http://forum.xda-developers.com/forumdisplay.php?f=1692
http://forum.xda-developers.com/forumdisplay.php?f=1712

It's not really in the wrong section (currently): the US variants of the SGS3 share this "development discussion" section with the exynos versions. If a different dev discussion is created for the qualcomm devices, this thread will probably be moved there.
Take care
Gary

Audio is up and going.
You know you want in on this.

moving along well
wifi and bluetooth now too (bluetooth is just as ****ty as it was before)
as far as i can tell, the two big things left are:
-shutdown/reboot sequence is borked
-data
EDIT: oh, camera too

Can you please discuss development, as opposed to just give status updates on a project? (Otherwise, I'll have to delete the thread.)
Some suggestions: Discuss HOW you got audio, bluetooth, wifi, etc working - perhaps with some code snippets or actual examples.
Thank you
Gary

garyd9 said:
Can you please discuss development, as opposed to just give status updates on a project? (Otherwise, I'll have to delete the thread.)
Some suggestions: Discuss HOW you got audio, bluetooth, wifi, etc working - perhaps with some code snippets or actual examples.
Thank you
Gary
Click to expand...
Click to collapse
Gary, I appreciate what you are trying to do here, but the commit log is readily available. It's not like folks are asking specific questions and they are left unanswered.
If someone wants to spur discussion on a particular part of any code that's been committed then I am game, but rehashing past efforts for the sake of generating content is wasting everyone's time.
You have the last word so do what you gotta do.
In the meantime we have all sensors going (prox/light/g-sensor), gps also works, device reboots properly, and now actually enters power collapse in suspend. Thanks to invisiblek, our wifi and BT drivers have been ported over from 3.0, + he's got d2_vzw up to speed.
Other than some (minor and not so minor) tweaks here and there, the major project that needs a champion is camera.

detule said:
Gary, I appreciate what you are trying to do here, but the commit log is readily available. It's not like folks are asking specific questions and they are left unanswered.
Click to expand...
Click to collapse
The issue is that this section is for development discussion. Currently, this thread is using it as a "status updates for a specific product" thread (and not discussing the process whatsoever.)
Perhaps "Sprint samsung galaxy S III -> General" would be a better place for this thread?
Take care
Gary

How's the progress on the camera coming along? Its pretty impressive that you got the 3.4 kernel this far already.
Sent from my SGH-T999 using Tapatalk 2

Oh wait, never mind I'll just check the progress on github.
Sent from my SGH-T999 using Tapatalk 2

Moved to sprint sgs3 general.
Take care
Gary
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Just an fyi, I saw Chad Goodman post a pure Google aosp jb Rom with a 3.4 kernel a couple of weeks ago where everything including camera worked, even html5
Obviously it wasn't here.

klin1344 said:
How's the progress on the camera coming along? Its pretty impressive that you got the 3.4 kernel this far already.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I had an aosp rom with 3.4 kernel and the camera working, plus audio, wifi, and bluetooth. This was almost 3 weeks ago. Sorry to burst the bubble. Thanks
Yes I approve bigwillyg

bigwillyg said:
Just an fyi, I saw Chad Goodman post a pure Google aosp jb Rom with a 3.4 kernel a couple of weeks ago where everything including camera worked, even html5
Obviously it wasn't here.
Click to expand...
Click to collapse
Get out of here dude! Hahah jk.
Sent from my SPH-L710 using Tapatalk 2

bigwillyg said:
Just an fyi, I saw Chad Goodman post a pure Google aosp jb Rom with a 3.4 kernel a couple of weeks ago where everything including camera worked, even html5
Obviously it wasn't here.
Click to expand...
Click to collapse
Isn't his beta ROM 3.4. I've ran that since he dropped it. Best aosp ROM out there.
Sent from my SPH-L710 using Xparent Blue Tapatalk 2

bigwillyg said:
Just an fyi, I saw Chad Goodman post a pure Google aosp jb Rom with a 3.4 kernel a couple of weeks ago where everything including camera worked, even html5
Obviously it wasn't here.
Click to expand...
Click to collapse
You should know better than to post things like the above without offering a source tree.
Mod please close this thread, it obviously does not belong here.
As a side note: Pretty disappointed with XDA here - this thread gets bounced from development (into general nonetheless), in favour of threads "how to compile CM10.1"? Close it, posts like the ones above are exactly what I was trying to avoid.

detule said:
You should know better than to post things like the above without offering a source tree.
Mod please close this thread, it obviously does not belong here.
As a side note: Pretty disappointed with XDA here - this thread gets bounced from development (into general nonetheless), in favour of threads "how to compile CM10.1"? Close it, posts like the ones above are exactly what I was trying to avoid.
Click to expand...
Click to collapse
Why are you getting upset ? Because someone else has already accomplished what the OP is trying to do. I've ran the Rom before so I can say that it ran great.
Sent from my SPH-L710 using Tapatalk 2

daniel4653 said:
Why are you getting upset ? Because someone else has already accomplished what the OP is trying to do. I've ran the Rom before so I can say that it ran great.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Then where's the kernel source?
Sent from my SGH-T999 using Tapatalk 2

daniel4653 said:
Why are you getting upset ? Because someone else has already accomplished what the OP is trying to do. I've ran the Rom before so I can say that it ran great.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
+1 I ran it also wish I still had it
Sent from my SPH-L710 using Tapatalk 2
---------- Post added at 07:51 PM ---------- Previous post was at 07:49 PM ----------
klin1344 said:
Then where's the kernel source?
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Since kernel is not on XDA there's no need to show the kernel source.
Sent from my SPH-L710 using Tapatalk 2

[Q] Chameleon OS

grabbed this and put it on the note1 for my girlfriend, she really likes it
have to admit it looks pretty slick runs well too
I wish I could get it running for us. there looking for people to run it
http://forums.chameleonos.org/threads/device-maintainers-wanted.66/
any takers ?

The tablet UI looks awesome....
not really diggin the phone look from what i saw.

This looks HOT...I'm a fiend for the status bar

Yup can't wait for it to show up for us
Sent from my GT-N7105 using xda app-developers app

It's out for Verizon note 2 and beans said he will port for us soon.
Sent from my GT-N7105 using Tapatalk 2

yes !!!
I saw it for Verizon, was hoping it was a matter of time till it got here WOOT !

anyone sniff this around yet ?

well im going to give it a go and try to port it for our rom.
first time for everything

stuck on boot will play around with it more

Where is this? In Verizon? Do you need someone to just make a quick port for us? I can do it
---------- Post added at 01:59 AM ---------- Previous post was at 01:58 AM ----------
wuelfman said:
well im going to give it a go and try to port it for our rom.
first time for everything
Click to expand...
Click to collapse
Hey bro..if you need any help let me know..

www.chameleonos.org/downloads.php
Got it from here
They dont support porting I was gonna trying building from source. Might be to much for me though
Sent from my SGH-T889 using xda app-developers app

wuelfman said:
www.chameleonos.org/downloads.php
Got it from here
They dont support porting I was gonna trying building from source. Might be to much for me though
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Yeh am trying to contact someone from there and there not responding back to my mail even mailed beans ? Im trying to see if anyone has started this or get permission, or see if beans is gonna port?

wish777 said:
Yeh am trying to contact someone from there and there not responding back to my mail even mailed beans ? Im trying to see if anyone has started this or get permission, or see if beans is gonna port?
Click to expand...
Click to collapse
this is from there site
"We want ChameleonOS to run on as many devices as possible and to do this we need help from the community. We're looking for those of you interested in being a device maintainer for devices we will support officially. For us to consider a device to be officially supported it must be able to be built using all of our projects found in the ChameleonOS repo manifest. Devices that require one or more stock projects to be removed and replaced by a modified version that allows the device to function correctly will interfere with our current build system. If this is the case, you are more than welcome to maintain your own unofficial builds
Since we originally based ChameleonOS off of CyanogenMod, any device that has official support for CM 10.1 will be easy to convert so that it builds for ChameleonOS. We'll be putting together an easy to follow guide on how to create the necessary projects to be merged into ChameleonOS in order to get your device into our system. In the mean time let me go over some of the requirements we have for individuals interested in being a device maintainer.
1.Familiarity with repo and git
2.Familiarity with the android build system and building a ROM from source code.
3.Know how to use gerrit code review and be able to submit patches to http://review.chameleonos.org
4.Able to debug, troubleshoot, and fix build issues.
5.Willing to keep all projects related to your device up to date and test new changes to verify everything is working as intended.
If you have a device that meets our requirements and you are willing and able to be a maintainer for a device please contact me 0xd34d(at)chameleonos[dot]org. Make sure to provide a couple of references to projects or work you have done that relates to android development. Some gerrit commits are always nice as well as links to threads for ROMs you have worked on. Please don't include any references to ROMs you may have ported. I've worked on ports myself but I don't consider the work done on a port comparable to working on a ROM from source.
Thanks in advance to all those that contact me!
"

I think this is what you might be looking for:
http://forums.chameleonos.org/threads/4-2-2-chameleonos-chaos-unofficialy-offical-4-8.157/

actually looks pretty cool. Any word on how well it runs? Battery life, etc.?

Traqic said:
actually looks pretty cool. Any word on how well it runs? Battery life, etc.?
Click to expand...
Click to collapse
Faustous said:
I think this is what you might be looking for:
http://forums.chameleonos.org/threads/4-2-2-chameleonos-chaos-unofficialy-offical-4-8.157/
Click to expand...
Click to collapse
yes it is for note 2 but for Verizon not sure how it would run ( not taking any chances of ruining my note lol

I got that but I mean if anyone tried it. Perfectly capable of doing a search

asp roms

When will we see a aosp rom for our note 3

Tomorrow when the clock strikes 12. I promise
Sent from my magic spaceship

When people stop asking for ETA's.
sent from my sm-9005.

Yerv Melkonian said:
When will we see a aosp rom for our note 3
Click to expand...
Click to collapse
When will we see people stop asking for aosp roms? Thats the real question, this phones barely a month old smh.
Sent from my note 2 ya bish!

d12unk13astard said:
When will we see people stop asking for aosp roms? Thats the real question, this phones barely a month old smh.
Sent from my note 2 ya bish!
Click to expand...
Click to collapse
We're just excited. Let us wag our tails and scratch at the door until our owner opens the door for us. So to speak. LOL!

Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium

dragonstalker said:
Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
I would love to see that
Sent from my SM-N900T

Is there a Google edition or developer edition coming? Has that been confirmed anywhere? I too am really missing cm, aokp, pa, and especially pac man. Man, what I'd give for pac man on this beast! I REALLY hope we get some aosp love.
Sent from my SM-N900T using Tapatalk

dragonstalker said:
Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.

CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
You sir have just explained the reason I fell in love with android, aosp, the rooting community. A lot of people don't get and are unappreciative of the works of ROM devs. So much greed and selfishness I've seen on xda since after the g1 days. Its always *****ing and bickering and this and that and demanding. Thank you to all the devs out there. Without you guys, android will be a Disney Land that never opened its gates
Sent from my SM-N900T using xda app-developers app

pathtologos said:
Is there a Google edition or developer edition coming? Has that been confirmed anywhere? I too am really missing cm, aokp, pa, and especially pac man. Man, what I'd give for pac man on this beast! I REALLY hope we get some aosp love.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
+24

CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
Why would you quote me and say exactly what i said in a long drawn out explanation. I'm guessing you missed the punctuation in my response. I mean you said everything i said, down to how the CM is a work in progress. Sheesh.

CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
DUDE I couldn't have said it better myself. You devs are wizards.

[ROM][SGH-I317 / T0LTEATT][4.4.4][UNOFFICIAL] CyanogenMod 11 - Builds of opportunity

As many of you know the GSM Note 2 is supported by CyanogenMod in a unified build format. This work is simply monumental with a beautiful product. Many in the US Note 2 community are reluctant to use the unified build for a variety of reasons.
Nicktastique and rmanne picked up the mantle and provided the SGH-T889 community with device specific unofficial CM11 builds. As rmanne has transitioned to a new device, I saw that I would be able to give back to the T889 community and pick up the yoke and keep us moving forward. The SGH-I317 is very similar to the T889 and use nearly all the same build configuration.
My product is no more than a straight source built t0lteatt build as the CM11 spec is drawn up for the t0lteatt on the CM github. All source is available at the CM git. I make no changes unless noted (in the remote chance that changes occur they will be documented/git referrenced).
I make no promises or warranty of any kind, all flashing is done at your own risk and should not be thought to be the responsibility of anyone other than the person deciding to flash the ROM. While I will attempt to help you work through issues, I do not plan on integrating non-CM commits or "fixes" with very few exceptions (carrier network labeling is one such exception).
I plan on putting up new builds weekly if not a bit more frequently if I am inspired. If I see a change in CM commits that looks promising I expect that I would post a new build. I will not promise a timeline, I simply plan on weekly builds.
Let me know if anything is goofy.
Flashing instructions:
Using the most current TWRP, ClockworkMod, or PhilzTouch recovery; wipe data, system, cache, and dalvik (especially if coming from a different ROM).
Flash the unofficial CM .zip file from the link below
Flash the gapps of your choice (CM or PA are good)
Boot phone and let sit on a stationary flat surface.
Do not touch the device for 10 minutes to allow the caches to build.
Reboot the device and set up to your liking
DOWNLOADS
cm-11-20150322-COUGMADE-t0lteatt.zip
cm-11-20150313-COUGMADE-t0lteatt.zip
cm-11-20150222-COUGMADE-t0lteatt.zip
cm-11-20150206-COUGMADE-t0lteatt.zip
cm-11-20150130-COUGMADE-t0lteatt.zip
cm-11-20150116-COUGMADE-t0lteatt.zip
cm-11-20150107-COUGMADE-t0lteatt.zip
cm-11-20150101-COUGMADE-t0lteatt.zip
cm-11-20141220-COUGMADE-t0lteatt.zip
cm-11-20141212-COUGMADE-t0lteatt.zip
cm-11-20141209-COUGMADE-t0lteatt.zip
cm-11-20141206-COUGMADE-t0lteatt.zip
cm-11-20141201-COUGMADE-t0lteatt.zip
cm-11-20141126-COUGMADE-t0lteatt.zip
cm-11-20141027-COUGMADE-t0lteatt.zip
cm-11-20141020-COUGMADE-t0lteatt.zip
cm-11-20141011-UNOFFICIAL-t0lteatt.zip
cm-11-20141002-UNOFFICIAL-t0lteatt.zip
cm-11-20140921-UNOFFICIAL-t0lteatt.zip
cm-11-20140914-UNOFFICIAL-t0lteatt.zip
cm-11-20140906-UNOFFICIAL-t0lteatt.zip
cm-11-20140902-UNOFFICIAL-t0lteatt.zip
cm-11-20140826-UNOFFICIAL-t0lteatt.zip
cm-11-20140818-UNOFFICIAL-t0lteatt.zip
cm-11-20140810-UNOFFICIAL-t0lteatt.zip
CyanogenMod Gapps
PA Gapps (good variety of options)
All source code for CyanogenMod is available in the CyanogenMod Github.
CM t0lte git
CM t0lteatt git
DonkeyCoyote Samsung Vendor git
Props and credit to:
CyanogenMod team (especially t0lte maintainers codeworkx and madmack for their hardwork toward insuring that the Note 2 is kept in the loop).
UtkarshGupta for providing advice in working through build issues on compiling Omni that translated to quick work on CM.
Rmanne for assistance in getting running by help with troubleshooting the build process.
And certainly not least mattlowry for being solid from his first posts in the doubleshot community, evolving along with weekendsR2short to porting for the doubleshot, and elevating his game on the Note 2. His advice and example made the unfathomable become doable.
Hastily spouted for your befuddlement

Mine

Gimme

Will you be adding support for gear manager and Samsung apps store for people such as myself who has a galaxy gear (2 neo). I ask because it can be pre-built into the ROM and well I can't personally get it working otherwise lol. Thanks for taking the time :thumbup:

fatjoejr2001 said:
Will you be adding support for gear manager and Samsung apps store for people such as myself who has a galaxy gear (2 neo). I ask because it can be pre-built into the ROM and well I can't personally get it working otherwise lol. Thanks for taking the time [emoji106]
Click to expand...
Click to collapse
Not immediately. I have some stuff to focus on and figure out first. I'll look at it down the road.

Does it comes with the CM Themer?
Sent from my SHIELD Tablet using XDA Free mobile app

ShrekOpher said:
Does it comes with the CM Themer?
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Based on OP it sounds like it is in ever way shape and form the same.
Trying to figure out why I should prefer this over official.. No added bells and whistles...
Great to see the Note 2 is continuing. Leaving for one plus one. Best of luck!!

frewys said:
Based on OP it sounds like it is in ever way shape and form the same.
Trying to figure out why I should prefer this over official.. No added bells and whistles...
Great to see the Note 2 is continuing. Leaving for one plus one. Best of luck!!
Click to expand...
Click to collapse
Some folks really want to have a build that doesn't show some other phones build ID. Those folks may not be numerous but they are around.
I may play with it after I figure another project I'm working on. If I feel I'm wasting my time building it, I'll stop. I thought the AT&T community might want something like this as I was putting a similar build together for the T-Mobile community.

Coug76 said:
Some folks really want to have a build that doesn't show some other phones build ID. Those folks may not be numerous but they are around.
I may play with it after I figure another project I'm working on. If I feel I'm wasting my time building it, I'll stop. I thought the AT&T community might want something like this as I was putting a similar build together for the T-Mobile community.
Click to expand...
Click to collapse
the builds are functionally the same(right?)

xda1zero said:
the builds are functionally the same(right?)
Click to expand...
Click to collapse
Yup. They are purely CM source home builds.
Eventually I will start doing subtle things to try learn more. Any changes to the I317 ROM will be tested on the T889 ROM first and documented in the OP.
If anyone out there has flashed this, how is your network being reported? Does it show AT&T?
New build is up.

Thanks for bringing this over to ATT, 6/18 running rock solid so far.
EDIT: Found a bug this morning, while the headphones are plugged in and play music is going the music will stop once the screen shuts off

Does this ROM have the camera blobs or whatever the correct term in it? I'm running OmniROM right now because they do and my photos have been significantly better.

edfuhr1 said:
Thanks for bringing this over to ATT, 6/18 running rock solid so far.
EDIT: Found a bug this morning, while the headphones are plugged in and play music is going the music will stop once the screen shuts off
Click to expand...
Click to collapse
I can't duplicate your bug on my T889. Both play music and Apollo work fine for me when the screen shuts off or times out. Are you running any battery saving settings?

New build posted in OP. Nothing changed other than the CM nightly changes and those from source. In what spare time I have I am digging through what I can find for ways to address the little things that bug me.

New build posted.
Hastily spouted for your befuddlement

Does this have the camera blobs and all that junk? I'm not sure on the specifics.. I was going to try and roll my own rom to learn, but then I saw this thread!
Thanks for your work, going to give this a test shortly.
EDIT: You might wanna fix that spelling error in the thread title too!

tetrahedonism said:
Does this have the camera blobs and all that junk? I'm not sure on the specifics.. I was going to try and roll my own rom to learn, but then I saw this thread!
Thanks for your work, going to give this a test shortly.
EDIT: You might wanna fix that spelling error in the thread title too!
Click to expand...
Click to collapse
This build is strictly CM without edit. If there is a compelling reason to change something I might, the only thing I am spending time on presently is the carrier labeling bit.

Coug76 said:
This build is strictly CM without edit. If there is a compelling reason to change something I might, the only thing I am spending time on presently is the carrier labeling bit.
Click to expand...
Click to collapse
The camera blobs (the ones Samsung released that are included in OmniROM these days) significantly improve camera performance and clarity. You might wanna take a look. Thanks for the reply too!

tetrahedonism said:
The camera blobs (the ones Samsung released that are included in OmniROM these days) significantly improve camera performance and clarity. You might wanna take a look. Thanks for the reply too!
Click to expand...
Click to collapse
IIRC they broke my OmniRom home builds camera. I might mess with them on my Omni home builds. It will take a while and I doubt I'll add them unless it makes a huge difference and documenting the change is easy.

Coug76 said:
IIRC they broke my OmniRom home builds camera. I might mess with them on my Omni home builds. It will take a while and I doubt I'll add them unless it makes a huge difference and documenting the change is easy.
Click to expand...
Click to collapse
Understandable! Good luck!

CyanogenMod 12/Android L Discussion

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.