• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CM 10.2 Nightlies Discussion

I'm just thankful for what we do have: JB4.3 and KitKat on Spectrum-- WOW !!! I'm not going to complain about what we don't have. Most of us are just waiting until our upgrade time to go to a bigger, faster, better phone. Who cares if the camera doesn't work on other apps. It works on AOSP camera/camcorder which is awesome already. Just be thankful to what we do have and stop complaining.
 
I'm just thankful for what we do have: JB4.3 and KitKat on Spectrum-- WOW !!! I'm not going to complain about what we don't have. Most of us are just waiting until our upgrade time to go to a bigger, faster, better phone. Who cares if the camera doesn't work on other apps. It works on AOSP camera/camcorder which is awesome already. Just be thankful to what we do have and stop complaining.

Like I said, I'm not complaining, I'm just pointing out an issue that everyone seems to overlook when they say "Great Rom! Everything works great!" It's not mentioned in the bugs and every time someone says something about it it's ignored. There's about 10 times more discussion about the LG logo which is really nothing more than a slight annoyance.
 
Like I said, I'm not complaining, I'm just pointing out an issue that everyone seems to overlook when they say "Great Rom! Everything works great!" It's not mentioned in the bugs and every time someone says something about it it's ignored. There's about 10 times more discussion about the LG logo which is really nothing more than a slight annoyance.

and Bluetooth... hahaha, it doesn't work either.
:D
 
Yea, it's good to just be patient. When something gets brought up I HIGHLY doubt it's being "ignored" per say. What the devs do is try to fix the problems that affect most people first. Is the LG logo less impactful as an issue than the camera issue? Certainly. However, it also affects EVERYONE. Many people are perfectly content with CM's camera abilities, so it doesn't affect as much of a user base. I'm an app dev, but I gotta say between family life and development at work, I do not do any of this stuff as a hobby. (I get sick of it at work. When I was a server admin however, I did tons of personal "hobby" programming) My ONLY problem, which is why i am not on one of the newer ROMs is bluetooth. Would I love for audio streaming to actually work properly, or even at all in most cases? Absolutely, and I have mentioned it before. I'm also however positive that the devs remember it being mentioned, it's just, not many people actual use it. I think besides me, only 1 or 2 others have mentioned it. And that is a TINY user base in reality, I expect it to be back burner, if not at all before devs lose interest in the device. What they've brought to this little device so far however is astounding. Basically, don't fret if you feel your feedback isn't being listened to. I'm willing to bet it's not only heard, but actually appreciated. I know when I'm deving software, the #1 thing I LOVE to hear is feedback. Makes me feel good about the things I do right, and gives me new challenges to fix the things that are wrong. Anyhow, I think without the work that's been done so far, I would have returned this device back to Verizon within 2 weeks of having it, because I got it way back on Gingerbread when it was crap for stock ROM. The devs made the phone not only useable, but great. In fact, I wonder if the custom ROMs that were created for it are what posed LG to actually step up their game. Publicly, it's likely humiliating as a company to be out-done by hobbyists. ;)
 
I was not aware we had a bluetooth streaming audio issue going on. I'll snag my wireless car adapter from work during Thanksgiving shutdown and see if it's a simple or complex fix. Can you be a bit more specific as to the issue you're seeing and what programs don't work?
 
FWIW, I am able to pair, connect, and use my Jawbone Era in both hands-free and audio/streaming modes. Let me know if I can check/test anything.
 
Yea, it's good to just be patient. When something gets brought up I HIGHLY doubt it's being "ignored" per say. What the devs do is try to fix the problems that affect most people first. Is the LG logo less impactful as an issue than the camera issue? Certainly. However, it also affects EVERYONE. Many people are perfectly content with CM's camera abilities, so it doesn't affect as much of a user base. I'm an app dev, but I gotta say between family life and development at work, I do not do any of this stuff as a hobby. (I get sick of it at work. When I was a server admin however, I did tons of personal "hobby" programming) My ONLY problem, which is why i am not on one of the newer ROMs is bluetooth. Would I love for audio streaming to actually work properly, or even at all in most cases? Absolutely, and I have mentioned it before. I'm also however positive that the devs remember it being mentioned, it's just, not many people actual use it. I think besides me, only 1 or 2 others have mentioned it. And that is a TINY user base in reality, I expect it to be back burner, if not at all before devs lose interest in the device. What they've brought to this little device so far however is astounding. Basically, don't fret if you feel your feedback isn't being listened to. I'm willing to bet it's not only heard, but actually appreciated. I know when I'm deving software, the #1 thing I LOVE to hear is feedback. Makes me feel good about the things I do right, and gives me new challenges to fix the things that are wrong. Anyhow, I think without the work that's been done so far, I would have returned this device back to Verizon within 2 weeks of having it, because I got it way back on Gingerbread when it was crap for stock ROM. The devs made the phone not only useable, but great. In fact, I wonder if the custom ROMs that were created for it are what posed LG to actually step up their game. Publicly, it's likely humiliating as a company to be out-done by hobbyists. ;)


TBH, The company doesnt really care about being outdone by hobbyists... as sad as that is. You paid them for the hardware, they moved on.

This sadly leads into some of the issues we have... The OEM can force the different equipment manufacturers to provide updated drivers and such, a hobbyist cant. Hell, half the time we can't even get their source without paying out of pocket... So its rough updating anything beyond what was last officially supported. What you have now is LARGELY because TDM re-worked things on his own. *claps*. That part isnt directed at you, but as a general comment. What you said about userbase is 100% true... If a handful of people complain about bluetooth.... and 90%+ dont. it tends to get back-burnered.... especially when the devs cant get the source for the drivers.

Down the rabbit hole I went, and I think I found a prize.

Gerrit Code Review

"- QC Proprietary parsers will be built and added only if
TARGET_ENABLE_QC_AV_ENHANCEMENTS is true."

Trying my first build of CM. Lets see how many errors I get.

Heads up... I cant build the latest 10.2 recovery image... you may have to build each target besides that individually.
 
I actually don't really have any real problems with Bluetooth either, which is actually important for me because I accidentally broke my headphone jack in a tragic elliptical accident. I use my car's Bluetooth as well as a Miccus Bluetooth receiver for headphones and the only issue I have is that the audio drops out occasionally (like I was receiving a notification) when I play music, but it's not a big deal.
 
Heads up... I cant build the latest 10.2 recovery image... you may have to build each target besides that individually.
Were you running into this error?
Code:
hardware/qcom/display-caf/liboverlay/overlayUtils.h: In function 'bool overlay::utils::isYuv(uint32_t)':
hardware/qcom/display-caf/liboverlay/overlayUtils.h:481:14: error: 'MDP_YCBYCR_H2V1' was not declared in this scope
It's where I kept being hung by the kernel build, until I added in the patch listed here (just not exactly on the same line # as their kernel):
https://github.com/MoKee/android_kernel_google_msm/commit/c53fb6d134fab3e3d7a022ba857d9cad4fcfa59a
 
Were you running into this error?
Code:
hardware/qcom/display-caf/liboverlay/overlayUtils.h: In function 'bool overlay::utils::isYuv(uint32_t)':
hardware/qcom/display-caf/liboverlay/overlayUtils.h:481:14: error: 'MDP_YCBYCR_H2V1' was not declared in this scope
It's where I kept being hung by the kernel build, until I added in the patch listed here (just not exactly on the same line # as their kernel):
https://github.com/MoKee/android_kernel_google_msm/commit/c53fb6d134fab3e3d7a022ba857d9cad4fcfa59a

I can't recall the error I was getting. I was only building the recoveryimage target though. My errors were all in bionic

Sent from my VS920 4G using Tapatalk 2
 
Man, I wish I would have known about that git before. Anywho, first ROM built and flashing now. If it boots properly, then start the next one with that Qcom AV switch enabled.
 
For the ones who asked, here's what I posted on Bluetooth a while back. I last tried a 11/12 nightly which continued to have the same issue.(Also, a note, when I first ran this ROM, it did pair properly as I describe. The inability to pair occurs after running for a while or pairing once or twice.)

As elaboration, sometimes it doesn't pair even on reboot. Also, when it is playing, I do get the audio dropout from time to time. Which really isn't the big deal for me, the fact that sometimes it doesn't pair is. The other strange thing, when it gets in this state of "unpairability??" if you try to turn Bluetooth off and then back on, it never can come back on until reboot.

...

Bluetooth:
I use BT for my car stereo ALL THE TIME. I stream from my phone to it every car ride. How my stereo works is it never tells the phone it's a stereo device until you try playing on the Bluetooth section of the stereo. Otherwise, it only reads as a headset for phone calls. I tried pairing from the Bluetooth music portion of the stereo, it wouldn't pair and I had the same BT issues as 10.1. I rebooted. I paired it from just the phone section on the stereo, it paired just fine. I then went to play from the music side of the stereo. Stereo speaker appeared as a function in the pairing options and I got iHeartRadio playing. I shut off the car, waited 5 minutes, turned it back on, and it auto-paired. I then hit play, and it played in the car. Unfortunately, on lunch, I got in my car and the stereo wouldn't pair. I had to reboot the phone for it to pair.
So in a nutshell, it appears bluetooth is plagued with the same problems we've had the last few versions of Android. This is sadface because it's a necessity for me.

...

If other people's headsets truly do work without any issues even after running the ROM for a while, I'm curious why my car stereo does not. Perhaps it's the fact the same device (MAC) powers 2 separate functions? Maybe because it's a Bluetooth headset and stereo device at the same time?
 
i got frustrated with the bluetooth flakiness so i went back to stock using the LG tool. i can now pair bluetooth headset first time, every time.
if i was going to keep this phone, i would have to make a tough decision - keep it stock and mostly unusable (lag, lag, and more lag) but with a rock solid bluetooth or put in a nice ROM and have a bluetooth that might pair the first time and never again until reboot or whatever shenanigans it requires "that" time.

oh yeah, before i forget - my phone is now super slow to lock onto GPS (stock ZV8 & ZV9). it always locked on instantly before. stupid lg... hahaha.

is this phone worth more with cyangenmod installed or bone stock?
 
i got frustrated with the bluetooth flakiness so i went back to stock using the LG tool. i can now pair bluetooth headset first time, every time.
if i was going to keep this phone, i would have to make a tough decision - keep it stock and mostly unusable (lag, lag, and more lag) but with a rock solid bluetooth or put in a nice ROM and have a bluetooth that might pair the first time and never again until reboot or whatever shenanigans it requires "that" time.

oh yeah, before i forget - my phone is now super slow to lock onto GPS (stock ZV8 & ZV9). it always locked on instantly before. stupid lg... hahaha.

is this phone worth more with cyangenmod installed or bone stock?
Sadly bone stock is the best way right now, have been waiting for a ROM that was not so problematic in the Bluetooth department. Came from the OG Droid 1 got spoiled on Bugless Beast ROMs, they would work 99.9% of all functions right off.
This LG Spectrum has left a bad taste in my mouth, not use to clunky phone and buggy ROMs.
It is my fault for letting my wife talk me into this phone, never again, heck I would still be happy with my old OG Droid 1.
This phone really bites big time. [end rant]
 
Sadly bone stock is the best way right now, have been waiting for a ROM that was not so problematic in the Bluetooth department. Came from the OG Droid 1 got spoiled on Bugless Beast ROMs, they would work 99.9% of all functions right off.
This LG Spectrum has left a bad taste in my mouth, not use to clunky phone and buggy ROMs.
It is my fault for letting my wife talk me into this phone, never again, heck I would still be happy with my old OG Droid 1.
This phone really bites big time. [end rant]

i am in the same boat.. i jumped from the fascinate(very solid stable roms) to.this only because i could get 2 for $100 and upgrade my line 3 months early keeping unlimited data...
 
i am in the same boat.. i jumped from the fascinate(very solid stable roms) to.this only because i could get 2 for $100 and upgrade my line 3 months early keeping unlimited data...

Did the same here. What a mess.

Still have two fascinates working as alarm clocks and such. Running kit Kat. Go figure, right? (Thanks again jt1334!)

Just got my son a new BT headset... No go on the spec. Going to have to go back to stock it seems... Or get him a new device.
 
Did the same here. What a mess.

Still have two fascinates working as alarm clocks and such. Running kit Kat. Go figure, right? (Thanks again jt1334!)

Just got my son a new BT headset... No go on the spec. Going to have to go back to stock it seems... Or get him a new device.

Lucky. I'm stuck with 2.3 or geewiz 4.2. the fascinate won't convert to mtd with any of my sd cards. I get stuck in a recovery loop "waiting for sd to mount"
 
Did the same here. What a mess.

Still have two fascinates working as alarm clocks and such. Running kit Kat. Go figure, right? (Thanks again jt1334!)

Just got my son a new BT headset... No go on the spec. Going to have to go back to stock it seems... Or get him a new device.
Have you tried the CM11 official nightlies? Works with two diff BT headsets and my car's built-in BT for me
 
Back
Top Bottom