Database Develop

[ROM] Final Froyo Release for Obsidian by CCRoms V2.02 Next Up Gingerbread

Welcome to the final release of Froyo, by the CCRoms team, which means you guessed it, we're switching gears to Gingerbread after this release. With this release we managed to get the Evo/Emerald going as intended(sorry for the wait.) The Galaxy S style pulldown power widget has been implemented in this release as well. Gem settings have been completely re-written as well, to provide a more intuitive and easier to understand interface for everyone, and of course bug fixes abound.
downloads available at: http://www.ccroms.net
Note:
Droid X users, at this point there is nothign more we can find to do to improve battery life. When/If the battery starts to drain fast, gets sluggish, or gets hot, reboot the phone this will put the race condition causing all of these problems back to sleep, unfortunately there is no way to put the process back to sleep once it wakes up and if you kill the process kernel panics and the phone reboots anyway.

sniffle said:
Welcome to the final release of Froyo, by the CCRoms team, which means you guessed it, we're switching gears to Gingerbread after this release. With this release we managed to get the Evo/Emerald going as intended(sorry for the wait.) The Galaxy S style pulldown power widget has been implemented in this release as well. Gem settings have been completely re-written as well, to provide a more intuitive and easier to understand interface for everyone, and of course bug fixes abound.
downloads available at: http://www.ccroms.net
Note:
Droid X users, at this point there is nothign more we can find to do to improve battery life. When/If the battery starts to drain fast, gets sluggish, or gets hot, reboot the phone this will put the race condition causing all of these problems back to sleep, unfortunately there is no way to put the process back to sleep once it wakes up and if you kill the process kernel panics and the phone reboots anyway.
Click to expand...
Click to collapse
How do you plan on bringing gingerbread to the droid x when we won't have the proper kernel to take advantage of it?

Are the "known issues" (GPS, camera/camcorder, etc.) fixed in this release?

avlfive said:
Are the "known issues" (GPS, camera/camcorder, etc.) fixed in this release?
Click to expand...
Click to collapse
No they are not. It shows all the known issues from the dl link posted above

bravo1234 said:
How do you plan on bringing gingerbread to the droid x when we won't have the proper kernel to take advantage of it?
Click to expand...
Click to collapse
for the record, a kernel is nothing more than a core piece of low-level software that executes other programs and provides access to the hardware. nothing says that when you upgrade an android version you MUST upgrade the kernel as well, if anything you just might need to modify how android interfaces with the hardware to match the old kernel interfaces.

joebob296 said:
No they are not. It shows all the known issues from the dl link posted above
Click to expand...
Click to collapse
Saw that, just didn't know if it hadn't been updated quite yet. Too bad. I'm still waiting on these to be fixed before I can jump back in. LOVED the ROM though.

avlfive said:
Saw that, just didn't know if it hadn't been updated quite yet. Too bad. I'm still waiting on these to be fixed before I can jump back in. LOVED the ROM though.
Click to expand...
Click to collapse
Those are all a must for me at least
Sent from my DROIDX using XDA App

I don't understand the gps issue or the camera issue. If there was fine GPS and a camera i would love the fact it is AOSP however not that i use them all that often but if i loaded it i would inevitably need one or both. and its still beta if you can't get a totally stable and working froyo rom how will you ever get the GB stable. Will the kexec(?) be used to use custom kernels to make the gps and camera work?

I just booted this up seemed ok other than the problems known but for some reason it wouldn't let me download anything from the market said I didn't have enough room.... Idk y that happened
Sent from my DROIDX using XDA App

Funnyface19 said:
I just booted this up seemed ok other than the problems known but for some reason it wouldn't let me download anything from the market said I didn't have enough room.... Idk y that happened
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
same here. it's been reported in other obsidian forums too. i was able to get around it by using an older version of market. i installed cm gapps instead of obsidian gapps. The cm gapps had a version of market from 2 month ago. everything worked fine. then i updated my market to 2.2.11 and the "There's not enough room..." error message was right back again.
other than that, i really love how clean and fast this rom is. thanks a ton cvpcs and best of luck with the cyanogenmod team.

any pics of the drop down toggles???

tttuning said:
any pics of the drop down toggles???
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=RbKJy6MPUz0

cvpcs said:
for the record, a kernel is nothing more than a core piece of low-level software that executes other programs and provides access to the hardware. nothing says that when you upgrade an android version you MUST upgrade the kernel as well, if anything you just might need to modify how android interfaces with the hardware to match the old kernel interfaces.
Click to expand...
Click to collapse
what...? What!? That is completely wrong... Nothing says you have to upgrade the kernel... unless Gingerbread uses modules not currently in the present kernel, which I can pretty much guarantee it will... Your statement could hold true for something such as minor update like 2.2 to 2.2.1 as we saw earlier, but would very like cause many things to not work come gingerbread. A good example is the previous hacked upgrades of 2.1 to 2.2 back before the proper kernels were released (specifically in memory of the HTC Incredible) sure, 2.2 could run without the proper kernel, of course your WiFi wouldn't work, GPS didn't work, if you tried to run the 720p camera it would crash, as well as several others that I cannot remember as of this moment. The kernel is not "just a low level piece of software" it is the backbone of your entire system, especially when it comes to the system talking with the hardware itself.

I think Taco that you should reread CVPS post. It stated this...
"nothing says that when you upgrade an android version you MUST upgrade the kernel as well"
Which is what you said was wrong, then said the same thing following it.

So how is the rom working for everyone? or it's pretty much dead..

ram130 said:
So how is the rom working for everyone? or it's pretty much dead..
Click to expand...
Click to collapse
I think it was pretty much dead on arrival when it said the camera & camcorder didn't work...that's kind of a mandatory feature of any smartphone.
If it's been fixed...then they're lame for not updating the page noting the bugs.

JagoX said:
I think it was pretty much dead on arrival when it said the camera & camcorder didn't work...that's kind of a mandatory feature of any smartphone.
If it's been fixed...then they're lame for not updating the page noting the bugs.
Click to expand...
Click to collapse
Well that sucks ..development on this phone is so slow..

The worst part is the x HAD so much potential, do to great things. I have watched this forum since the day the x launched and the sad thing is that the tbolt is only 6 days old right now and has a much larger devwlopment thread than the x has had at any point. Sad to say it but i think moto phones are done in the development community.
Sent from my ADR6400L using XDA App

ksizzle9 said:
The worst part is the x HAD so much potential, do to great things. I have watched this forum since the day the x launched and the sad thing is that the tbolt is only 6 days old right now and has a much larger devwlopment thread than the x has had at any point. Sad to say it but i think moto phones are done in the development community.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
The X development has all but ceased from what I can see. Such a bummer since I'm stuck with it for another year and a half. Hopefully we can see a few updates to some ROMs once gingerbread rolls around for the phone, but after that I don't see much reason for hope.

True...so what was the most annoying issue with this rom? Im thinking about flashing it. Im on 3.4.2 now.
Also you can sell your DX on swappa.com then pay the difference and get a htc.

[DEV][WIP] CyanogenMod 7 for the LG Revolution (working 2d/3d acceleration!)

No, it's not out yet-- but I do have it booting, and with working touchscreen support
Video Link: http://www.youtube.com/watch?v=hnRlyMZzdT0
New video:: http://www.youtube.com/watch?v=2d4pZXyayts
That's about it right now.
Things left:
Mobile Voice
3G Data
4G Data / Voice
Audio
Front Camera
Back Camera
GPS
Bluetooth
Wifi
DSP support for video encode/decode
Vibrate/Notification LED
As I get things working, I'll update this list.
My first priority is wifi, then mobile voice, then 3g data, then vibrate/notification LED.
After that, I'll get GPS working (not hard) then rear camera.
Things that'll probably not happen in CM7 for a while:
Front camera
4G Voice
4G Data
Anything to do with 4G will be VERY tough, since I don't have LG's kernel sources, and I'm no RIL reverse engineer... Any help in this matter is appreciated!

You are the man!

Anxiously awaiting!
Sent from my VS910 4G using XDA Premium App

Uh oh....deciding between 4G and CM7 is going to be rough.
Good work dasgewürfelte (thecubed in German haha)...thanks for everything

Anytime you need a tester Cubed, just let me know. My city is scheduled to get 4G this Thursday so I should be able to test that for you too, soon.

thecubed said:
No, it's not out yet-- but I do have it booting, and with working touchscreen support
That's about it right now.
Things left:
Mobile Voice
3G Data
4G Data / Voice
Audio
Front Camera
Back Camera
GPS
Bluetooth
Wifi
DSP support for video encode/decode
Vibrate/Notification LED
As I get things working, I'll update this list.
My first priority is wifi, then mobile voice, then 3g data, then vibrate/notification LED.
After that, I'll get GPS working (not hard) then rear camera.
Things that'll probably not happen in CM7 for a while:
Front camera
4G Voice
4G Data
Anything to do with 4G will be VERY tough, since I don't have LG's kernel sources, and I'm no RIL reverse engineer... Any help in this matter is appreciated!
Click to expand...
Click to collapse
So, does the release of the kernel change your thoughts on 4G? What about the issues with 3G data lag? Not pressing, just curious. I know with the release of the kernel you aren't going to have a lot of time on your hands to get sidetracked

majorpay said:
So, does the release of the kernel change your thoughts on 4G? What about the issues with 3G data lag? Not pressing, just curious. I know with the release of the kernel you aren't going to have a lot of time on your hands to get sidetracked
Click to expand...
Click to collapse
We were on IRC before when I posted that link. He said 4G data/voice shouldn't be a problem now.
The kernel gives the information on how to communicate with the radio
Pretty much, from what I understand, all of those "not for a while" items. Are now going to be in the first build of CM7 for the REVOLUTIOnnnnn-tionn-tion-tion

nick99wj said:
We were on IRC before when I posted that link. He said 4G data/voice shouldn't be a problem now.
The kernel gives the information on how to communicate with the radio
Pretty much, from what I understand, all of those "not for a while" items. Are now going to be in the first build of CM7 for the REVOLUTIOnnnnn-tionn-tion-tion
Click to expand...
Click to collapse
so did I miss LG releasing the kernal source.. or did we get it another way..?
**edit**
so just a few more clicks and I wouldn't have asked that question.. I am game try whatever you have available!

holy crap i just nutted.

mursepaolo said:
holy crap i just nutted.
Click to expand...
Click to collapse
This.
Awesome!

Hey Thecubed, is there a particular reason you went with ADW Launcher as the... er... Launcher? What would keep you from using HeLauncher as the default? Any chance of getting a Samsung style launcher and icons?
And I think its almost been a week, and the phone is still running smooth. I did the stat bar cleaner, thanks MT. And the battery life is stellar.\
Thanks again. I am working overtime so I can get you a sizeable dony.

nick99wj said:
We were on IRC before when I posted that link. He said 4G data/voice shouldn't be a problem now.
The kernel gives the information on how to communicate with the radio
Pretty much, from what I understand, all of those "not for a while" items. Are now going to be in the first build of CM7 for the REVOLUTIOnnnnn-tionn-tion-tion
Click to expand...
Click to collapse
Very good to hear
Fixing 3G lag will be sooo nice.

markapowell said:
Hey Thecubed, is there a particular reason you went with ADW Launcher as the... er... Launcher? What would keep you from using HeLauncher as the default? Any chance of getting a Samsung style launcher and icons?
And I think its almost been a week, and the phone is still running smooth. I did the stat bar cleaner, thanks MT. And the battery life is stellar.\
Thanks again. I am working overtime so I can get you a sizeable dony.
Click to expand...
Click to collapse
The kingpins of CM7 decided to use ADW.Launcher since its dev open-sourced the launcher. It makes customizations very easy to make. You can always pull it out with TB once you've got your launcher of choice up and running.
Cubed - I was so excited when I saw this thread pop up the other day. I have my Revolution coming in the mail hopefully sometime this afternoon, and I will definitely be on the IRC once it gets in. I won it in a contest, so I won't feel bad if I end up bricking it, especially because I have an upgrade in September.
And as soon as my finances allow, I will most certainly be submitting a donation. Thank you for your support!
I will say though, I just switched to this Fascinate I'm using currently a month ago, and our CM7 code finally got merged upstream, so I'm definitely gonna miss fully-functional GB, but I'm sure you'll have it running smoothly in no time!

Totally double-posting here, but I have my phone activated and running. 4G is friggin' SWEET!
Anywho, if you need any logcats or anything at all that's within my practical ability (I'm willing to flash just about anything since I didn't pay a dime for this phone, and can do any number of logcats/dmesg you need), just let me know. I'll pop onto the IRC from time to time just to check, but if you ever need someone in a hot moment, direct message me and I'll be glad help!

any chance we will see a alpha release to test out for you? would be ballin!

RegnierD said:
The kingpins of CM7 decided to use ADW.Launcher since its dev open-sourced the launcher. It makes customizations very easy to make. You can always pull it out with TB once you've got your launcher of choice up and running.
Cubed - I was so excited when I saw this thread pop up the other day. I have my Revolution coming in the mail hopefully sometime this afternoon, and I will definitely be on the IRC once it gets in. I won it in a contest, so I won't feel bad if I end up bricking it, especially because I have an upgrade in September.
And as soon as my finances allow, I will most certainly be submitting a donation. Thank you for your support!
I will say though, I just switched to this Fascinate I'm using currently a month ago, and our CM7 code finally got merged upstream, so I'm definitely gonna miss fully-functional GB, but I'm sure you'll have it running smoothly in no time!
Click to expand...
Click to collapse
I suspect another reason ADW was incorporated is because it's one of the only open source launchers. That comes without the possible legal ramifications of packaging someone elses work in your creation.

I also wouldn't mind being a testcase, if there is a use for another one.

Right now I'm reworking all the init scripts that LG has written and consolidating them into the cyanogenmod style of a single "init.bryce.rc" initscript.
As I'm doing that, I'm looking for referenced binaries and crossreferencing that list with the list of binaries that cyanogenmod builds (to see what binaries are LG-specific and what are stock Android). After I find the binaries, I am hexdumping each one to find out which libraries they import, and adding those to the cyanogenmod build directory also.
LG really really really needs to write better scripts. Their init process is all over the map, and half of the stuff in the init script isn't even for our device! It references dev platforms and other stuff that really should be trimmed before releasing to the public.
Anyway, in regards to testers, I actually have a device now (my very own device! but no service haha) so I'm able to do testing on my own for intermediate builds. When I release a milestone build (I'd consider wifi and 3d accelerator a milestone build) I'll release it via PM.
I don't want to make the test builds public because I worry that it'd cause problems with people not reading the "WARNING! THIS DOESNT WORK RIGHT!" and coming back saying they bricked their phones.
However, as soon as I have something to show, I'll make a video

Woohoo! That's exciting. I miss stable CM7 so much. It was flawlesson my trusty Incredible, just getting to stable on the Fascinate, and now being started from scratch here.
If you ever need any help, Cubed, I'm game. I would have no qualms with it. I'm available at nearly any moment and always have a computer nearby for logcats and d/kmesg dumps. Plus, I have full services 3/4G and wifi all around me at almost all times.
I'd love to be able to help the community out, even if it's only by flashing and giving error logs.
I noticed when peeking around in the system that things were a little messy too. The build.prop is kinda iffy and their lack of an organized boot animation is annoying. It's like being neat wasn't a concern at all. Seems like they were in a hurry.

RegnierD said:
Woohoo! That's exciting. I miss stable CM7 so much. It was flawlesson my trusty Incredible, just getting to stable on the Fascinate, and now being started from scratch here.
If you ever need any help, Cubed, I'm game. I would have no qualms with it. I'm available at nearly any moment and always have a computer nearby for logcats and d/kmesg dumps. Plus, I have full services 3/4G and wifi all around me at almost all times.
I'd love to be able to help the community out, even if it's only by flashing and giving error logs.
I noticed when peeking around in the system that things were a little messy too. The build.prop is kinda iffy and their lack of an organized boot animation is annoying. It's like being neat wasn't a concern at all. Seems like they were in a hurry.
Click to expand...
Click to collapse
I will need people to test the 3G/4G service once I get the radios initialized, since I only have the phone and no service
Right now I'm still sorting through the binaries and libraries trying to get at a bare minimum wifi and 3d acceleration working.

Ubuntu on D3

Anyone knows if someone take the initiative to develop something for our unlucky device?
Is that possible at least?

Im no real dev but I was bored last night and started messing around with it, got the android part to compile, havent flashed it or anything though
But in its current state, ubuntu phone doesnt seem like anything more then, 'hey this is cool, now back to a rom that has some actual support'
Its a dev preview with little to nothing working heh
To answer your question though, on paper, yes, it looks like it would work, just with all the same problems as current cm10.1 that are caused by kexec

That was exaustive man thanks!
Damn kexec is both a great good and a great bad for this device!
Hashcode, you're our only hope!

Looks like Hashcode is planning to port it eventually:
https://wiki.ubuntu.com/Touch/Devices#Work_in_progress
I wasn't really expecting anyone to port this for our Droid 3 considering the low amount of RAM we have when compared to newer devices.

Yeah, Hash is currently working on it (check his Twitter, there are links to the XDA thread. I'd link, but stupid 10 post limit here...), but it's as good as it's gonna get for a little bit.
As he says:
WHAT WORKS:
Display
Touch screen
Wifi
Audio
Click to expand...
Click to collapse
I'm running a D3 on Verizon with SafeStrap 3.05 and the 03-01 Phablet patch, and it CAN make phone calls (so CDMA and GSM both apparently work).
He isn't kidding about needing more swap space, or it being a power drain; a lot of issues with Ubuntu Touch boil down to how much of a WIP it is by the Ubuntu devs.
As soon as I have this 10 post criteria met, I'll post a bit more of an updated "how to install" on his dev thread.

I'm a noob but I finally got something flashed to my D3. I loaded the Nightly CM10.1 Solana from 03-10 and the 03-01 Gapps using TWRP Safestrap 3.05. The phone largely works, the biggest issue I have is that my Bluetooth keyboard doesn't work with it. It pairs but it doesn't send any keystrokes. I know the camera doesn't work, but my D3 pictures never turned out anyway. Operation seems smooth but a little bit on the slow side (which doesn't surprise me).
I haven't done any customizing or optimizing, so perhaps it could be made to run faster by tweaking on it.
I just wanted to try out the phone with larger font size so I don't have to hold the phone so far away. That's why I loaded Jelly Bean on it. The ICS version I installed couldn't make and receive calls, and same thing on the CM10.1 nightly from 03-09. I'm not saying I installed those right or anything. My point is, in my opinion, the March 10 Solana Nightly has left me with a phone that I'm having fun with, and I'm happy to leave it this way for awhile maybe. Perhaps it is not a good idea to load the nightly builds on your machine when you're a noob like me, but hey it looks to me like I picked a good day.

I've had it - going back to ICS

Well I'm fed up with this Jelly bean garbage! For you that say certain ones (Liquid smooth seems common) are 'fast', you're only kidding yourself.
JB on the bionic is terrible. It lags and is buggy (on after market's at least). I give props to the developers who have spent time making it usable for the most part.
I'm going back to ICS roms.

I had the same problem for a while. It wasn't until after I flashed Blurry JB after the third time did it work lag free. I had no idea what was going on but I just followed the advice of the developers and deleted the slot 1, wiped everything and reinstalled it.

delete

You seem to think all bionic users share your experience. Not true. My bionic running JB stock rom & kernel, rooted gives great performance and a better user experience than ICS. Mine is fast and stable with no lag. Your blanket criticisms miss the mark for most.

I thought you can't go back to ics once you have jb. No?
Sent from my DROID BIONIC using xda app-developers app

Groid said:
You seem to think all bionic users share your experience. Not true. My bionic running JB stock rom & kernel, rooted gives great performance and a better user experience than ICS. Mine is fast and stable with no lag. Your blanket criticisms miss the mark for most.
Click to expand...
Click to collapse
Have you even looked at the threads in the development section? It's pretty clear the lag issue is common and I am not alone. There are always a few exceptions to a blanket statement, thanks for pointing it out though.

No problems here.
If you're still running ICS as stock with JB in a safestrap slot, that's your problem

LucasMN said:
Have you even looked at the threads in the development section? It's pretty clear the lag issue is common and I am not alone. There are always a few exceptions to a blanket statement, thanks for pointing it out though.
Click to expand...
Click to collapse
I certainly agree that some percentage of users experience lag or other problems and I don't doubt that you are one of them. Not sure what that percentage is though. I did an FDR after the JB update and clear cache once in a while. I sync manually and turned off Google Now, but use Voice Search extensively. Various settings, sync options, location services and some apps can cause problems that have little to do with the rom.

Mr. HQ said:
No problems here.
If you're still running ICS as stock with JB in a safestrap slot, that's your problem
Click to expand...
Click to collapse
I'll try and update it to JB then I suppose. Thanks for the tip.
I get 2-10 second lags when doing a lot of tasks.

I have been reluctant to go from my extremely functional ICS based bionic running Icarus HD Remix to JB. I have not seen any post that convinces me to make the jump.
I have JB on my tablet, my wife has it on her Samsung S3, and my phone as it is kicks butt.
Why should I upgrade from stable to JB??
Thanks anyone with constructive responses.

Mr. HQ said:
No problems here.
If you're still running ICS as stock with JB in a safestrap slot, that's your problem
Click to expand...
Click to collapse
I deleted all my partitions (slots), uninstalled safestrap, did a Full data reset/cache wipe. Downloaded and installed JB stock (OTA). Then installed safestrap and Liquid Smooth and it is still super laggy.
It'll be fine for a few swipes/screens then all of the sudden you go to open an app or go to the homescreen and it takes forever (5+ seconds). I've also had it reboot once randomly tonight as well as freeze with nothing on the screen but the 4 lights on the bottom lit up.
I dunno what else to do. Maybe it's time to start looking at new phone.

Well good news. One of the guys at work broke his phone last night and wants to upgrade to an S4. Since we have insurance on it, all I have to do is pay $100 and I get brand new S3...should be in tomorrow. :good:

I reformatted my phone twice, and i got heavy lag after a long while. Something was definitely up with JB. GB was fine, ICS got a bit worse, JB is just completely unusable with lag.
A emergency phone call will lag for 60 seconds (absolutely unacceptable), as well as sending messages. Keyboard pops up after 10 seconds, typing a simple sentence takes over a minute, and sending just barely responds. Although chrome is known to be pretty slow compared to browsers, it was also completely unusable for 90 seconds of lag from opening the app to retrieving search results.
I killed off a lot of apps, as well as clear out images/messages, and other cache/data things. But still, it crawled like a slug.
I gave up yesterday, and just installed CM10.1 . Already, I feel relieved that I don't feel restricted by anything. Bionic is in the RC stage for cm10.1. It does all of the necessary things flawlessly so far. I suggest everyone hwo's having slowdown issues with this stock bloatware to move over to CM or some custom rom. Keep FAR FAR away from it.
For now, i feel like I have a completely new phone since GB, and it is keeping up with the responsiveness of my Nexus 7.
But, if you are very inclined on staying on stock: I'm not sure what will help you speed it up again, other than completely wiping it again and reformatting.

Mine was still laggy even on aftermarket roms (JB).
I have it listed on craigslist now since I'm rocking an S3 since last Friday.
No lag on this bad boy.:victory:

I've been using FlyingJelly and it's great! My wife is stock JB and she has no complaints either.

Lag caused by the Overclocking?
In another thread, someone suggested that the lag many bionic users experienced could be fixed by clocking the CPU back down from 1.2 to 1 GHz. I tried this using the CPU Control under ROM Toolbox and I have found this worked for my phone, although I haven't found a way to make it permanent (it seems to change back to the 1.2 GHz setting, most of the time when trying to download something over a bad wifi or 4G connection). But it has helped with the frustration to know that when it lags, I will find the setting just needs to be changed back.

I am on ICS, running Icarus remixed or whatever it is called, and everything works.
My phone is tweaked and customized and runs great.
I have not seen any posts that answer my prior question: what is the benefit of switching to Jellybean when my phone works great right now?

idivorceyou said:
I am on ICS, running Icarus remixed or whatever it is called, and everything works.
My phone is tweaked and customized and runs great.
I have not seen any posts that answer my prior question: what is the benefit of switching to Jellybean when my phone works great right now?
Click to expand...
Click to collapse
There isn't unless you want there to be one; as has been beaten to death on this forum, any updates are completely 100% personal preferences. If you're happy with what you have, then more power to ya!

thanks. I've always been on the edge with this phone, loading leaked upgrades, roms, etc. but now that it works nicely, I'm sticking with ICS & Icarus remixed. overclocked...

I wish I could go back to ICS. JB hasn't been able to keep my underclock at 600 and keeps resetting it back to 300.
Sent from my DROID BIONIC using Tapatalk 2

Blisspop/CM Rom now in Beta

Head over to the main G4 development page if you are interested in this for the H811/H815.
http://forum.xda-developers.com/g4/development/h811-h815-blisspop-cyanogenmod-12-1-t3185593

There's still a long way to go. Most things are still broken and new builds will generally break things on a regular basis. Just be aware before heading over. The post doesn't need more Posts saying goodbye this/that isn't working, it's still very much a WIP.
Sent from my LG-H815 using Tapatalk

IIIIkoolaidIIII said:
There's still a long way to go. Most things are still broken and new builds will generally break things on a regular basis. Just be aware before heading over. The post doesn't need more Posts saying goodbye this/that isn't working, it's still very much a WIP.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
True, and the OP doesn't have the most recent build where most stuff is actually working. I'm running the 10/15 build (page 76-78...somewhere in there, posted by codeworkx) and most of my audio is working. Haven't tried bluetooth, but I rarely use it, apparently voice calls have an echo, but I never call anyone, either. The only thing I really use that has an issue is the camera that delays on opening, but I'm sure that'll be worked out shortly. As soon as codeworkx got to work on it, it's honestly been pretty stable for a WIP, but I think I have a higher tolerance for broken builds and features, having been a crackflasher for 7 years now. I'm just happy to be back on AOSP/CM at this point with this phone.

schreckles said:
True, and the OP doesn't have the most recent build where most stuff is actually working. I'm running the 10/15 build (page 76-78...somewhere in there, posted by codeworkx) and most of my audio is working. Haven't tried bluetooth, but I rarely use it, apparently voice calls have an echo, but I never call anyone, either. The only thing I really use that has an issue is the camera that delays on opening, but I'm sure that'll be worked out shortly. As soon as codeworkx got to work on it, it's honestly been pretty stable for a WIP, but I think I have a higher tolerance for broken builds and features, having been a crackflasher for 7 years now. I'm just happy to be back on AOSP/CM at this point with this phone.
Click to expand...
Click to collapse
I hope nobody thought I was saying it is ready for prime time! Just a heads up. I have not installed it yet as I will wait for a more highly functioning build, but I also know there is a thirst for development here, so I wanted to share the good news!!

Honestly, if you were to try the 10/15 build, you'd be surprised at how "ready from prime time" it actually is. I've been using it as my DD for the last 2 days and it's actually been pretty nice. Couple small things here and there, but the only thing that's affected me at all so far was the camera delay. Now that there's at least a dev or two that seems like they know what they're doing, I'm hoping development for AOSP/CM stuff starts picking up. The little time that codeworkx has put in so far has been looking extremely promising. (Not to take away from the OP on that, but code made it so that I can actually use it as a DD with sound.)

schreckles said:
Honestly, if you were to try the 10/15 build, you'd be surprised at how "ready from prime time" it actually is. I've been using it as my DD for the last 2 days and it's actually been pretty nice. Couple small things here and there, but the only thing that's affected me at all so far was the camera delay. Now that there's at least a dev or two that seems like they know what they're doing, I'm hoping development for AOSP/CM stuff starts picking up. The little time that codeworkx has put in so far has been looking extremely promising. (Not to take away from the OP on that, but code made it so that I can actually use it as a DD with sound.)
Click to expand...
Click to collapse
Hmmm, I didn't realize it was that far along. Between the 815 talk there, it has become tough to follow. I may give it a go. I assumed you did a complete wipe before installing? Thanks, @schreckles
EDIT: You don't use bluetooth I see, and I do quite a bit. From what I understand, that doesn't work, so that's a non-starter for me. Guess I'll wait.

ShermCraig said:
Hmmm, I didn't realize it was that far along. Between the 815 talk there, it has become tough to follow. I may give it a go. I assumed you did a complete wipe before installing? Thanks, @schreckles
Click to expand...
Click to collapse
Yup, sure did. Full wipe (especially when switching back and forth between CM/AOSP and stock roms) and then flashed the 10/15 H811 build that codeworkx posted the other day, along with the nano gapps he'd suggested.
Small issues: Your LED will stay lit up blue until you plug the phone in and unplug again. No biggie. No "OK Google" or anything that requires the phone mic for me thus far (ie Google Sound Search.) Camera takes approximately 4 years to open, but it does open, and the shots it produces aren't bad. They aren't as good as stock, but that's typically been the trade-off even since back in my OG Droid days when going from stock to non-stock base. Call audio, bluetooth, and NFC apparently have some issues still, but I rarely use any of those, so meh. Oh, and I get a popup stating "Settings has closed" every so often, but it doesn't affect anything. I'm sure I could find the cause if I was motivated, but I'm sure it'll get worked out soon enough.
...Mostly just stuff I can live without for now that's broken. I've even been using Xposed and some of my favorite modules without any ill effects.

So is it more or less a theme now or what? I know what CM is, but as far as functionality, is it quite a bit faster than stock or what?
Thanks!

I am assuming that this is the only public aosp build for the G4?

maximus20895 said:
So is it more or less a theme now or what? I know what CM is, but as far as functionality, is it quite a bit faster than stock or what?
Thanks!
Click to expand...
Click to collapse
It's a completely different build of Android using different frameworks and whatnot. It's built upon AOSP and tweaked framework to make it CyanogenMod. I'm not sure if the one I am using currently is the one in this thread but so far it's been pretty smooth. There are definitely some issues but it's a lot further along than I though it would be. Kudos to those guys!
EDIT: That is the same build I am using (in case anyone is wondering).