Develop Bugs

[ROM][AOSP][CDMA] gorilla_toro-AOSP-v1 4.0.3 UPDATE 1/2/11

JUST ANOTHER AOSP BUILD!
This is an AOSP Build of 4.0.3 I have made basically no changes as of right now. I have fixed tethering and market restore. I plan to add some useful modifications in the future.
Gapps-403_signed.zip
md5sum cf82c67056c31101cfed0f936cac29c1
Gorilla-toro_AOSP_v1.1.zip
md5sum 9ce8af2122bd743862c0aa6d49bed97d
Full wipe if coming from any other ROM. Especially if they have made framework changes.
Use my gapps if you want to make sure market restore works. These are the same as the latest that are floating around I just included google backup transport apk in mine.
Google Wallet - download the unmodified apk. Install as usual after full wipe. Seems to work, I haven't used it recently though.
Kernel - Stock for now.
Also I can't check any of the NFC stuff because I don't know anyone else with an NFC enabled phone.
Big thanks to everyone as usual, CM Team, RootzWiki, RootzBoat, Birdman, Pete of Bugless Beast fame, I looked at all of their vendor make files to figure out how to set those up.
Source Code: Google AOSP 4.0.3 Master Branch - my changes will uploaded tonight when I get off work to my github.
Post any issues that you notice. I don't expect many though since it is currently a pure AOSP build.

MD5 Sums are correct now.
Facebook Sync fixed, added reboot recovery menu.
Google wallet works. Do a fresh install of Google Wallet after wiping.
I am working on the camera panorama mode.

Reserved one more time

Post on Rootzwiki?

I shall later today. I want to get my source uploaded to my github. Otherwise I will get hear a lot of whining..as in source, source, source..... Just here for now. Upload there tonight or in the morning.

Thanks for this. I've been looking for a mostly-stock 4.0.3 ROM.

This is EXACTLY what I have been looking for! Thank you!
My only reservation is that I really don't want to wipe my device as I've only recently got everything sorted the way I wanted it on my phone. Is there a quick and dirty way to unlock the tethering capabilities with ADB or Root Explorer? Or is that part of the framework that would have to be properly flashed with the installation of a new ROM like this one?

It is part of the Frameworks. It is built into the system. There is no quick and dirty way. You could do a titanium back up and restore everything after the flash. The changes are minimal and should not affect anything from another build. I suppose there could be problems if you restore from 4.02 to 4.03 but you can always Nandroid and try it if you like.
Going to post an update today. It will have working FB sync and a file manager built in from CM otherwise no changes.

do i install this with CWM? can someone tell me how to install this?

I'll be checking this one out soon, been waiting for an all stock 4.0.3
A couple quick questions:
Is it rooted?
Does it have busybox?
Is it deodexed?
On a side note, the md5sums you have listed, are the same for both files

Does anyone else get a force close when using panorama mode in the camera?
Sent from my Galaxy Nexus using xda premium

jimmytinsnips said:
Does anyone else get a force close when using panorama mode in the camera?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I sure do. Tried to fix permissions to see if that would help to no avail.

Can you rent and watch movies from the market? Each rom I try, it seems either tethering is unlocked, or you can rent and watch movies. I would love a rom where I can do both.

I am now working on Panorama mode. Just found that it force closes, because I never use it. The current release has the Facebook fix, thanks to team kang, also I added in a reboot recovery menu. Otherwise it is stock with working tethering.
I will let you know when I see why panaorma isn't working.

Thanks. I don't use Panorama much, but it's nice to have the feature available.

I will post an update to fix the camera it is simply due to a couple of missing libs that I didn't add to the extract.sh script. I will also fix it and post the updated rom tonight. I am not sure about movies from the market. I think that has something to do with rooted devices and googles agreements with the copyright holders. Probably due to piracy concerns.
Let me know if you notice any other bugs. There really shouldn't be many since it is basically a pure AOSP build.

Gr8gorilla said:
I will post an update to fix the camera it is simply due to a couple of missing libs that I didn't add to the extract.sh script. I will also fix it and post the updated rom tonight. I am not sure about movies from the market. I think that has something to do with rooted devices and googles agreements with the copyright holders. Probably due to piracy concerns.
Let me know if you notice any other bugs. There really shouldn't be many since it is basically a pure AOSP build.
Click to expand...
Click to collapse
While you're fixing the panoramic camera, would you be able (and willing) to add back the original live wallpapers and ringtones? Or if not in the build itself, perhaps a separate flashable zip file that would add them back? I tried (and failed) to modify your ROM with these original files added back in and, of course, I only got a bootloop.
If you need the files, I can adb pull them for you and zip them up easily.
Thanks again for your awesome ROM.

j.bruha said:
While you're fixing the panoramic camera, would you be able (and willing) to add back the original live wallpapers and ringtones? Or if not in the build itself, perhaps a separate flashable zip file that would add them back? I tried (and failed) to modify your ROM with these original files added back in and, of course, I only got a bootloop.
If you need the files, I can adb pull them for you and zip them up easily.
Thanks again for your awesome ROM.
Click to expand...
Click to collapse
Sure, no problem. Zip them up and upload them to dropbox or multiupload or something and I will fix it up over the weekend.
Also, Sorry for the delay on teh camera fix. I have just been extremely busy with a project that is a few days past deadline at work. Unfortunately, real life has to come first....

Flashed the update...lost my camera completely...
Sent from my Galaxy Nexus using xda premium

Wow, that's Crazy. Sorry I have not been maintaining the thread here. School has me so busy I just don't have the time right now. I am in a Physics Class, Electricity, Electromagnetism, and fiberoptics. And at the same time in an advanced Computer Science Class with 4 hours of Elective Classes....Kinda busy....

Working pdroid patches [currently AOKP(toro+maguro), stock AOSP, cm9]

I'm using this thread to share working pdroid patches I've got for various Galaxy Nexus roms. This was made using the patcher being developed here (patcher is in the 4th post). The patcher is currently linux-only, but will also work with cygwin in windows. I'm posting the finished flashable zip here as a convenience to anyone who can't use it themselves. Please note that I am not one of the people actively developing this patcher, just a willing tester who happens to own a toro Gnex.
If you don't know what Pdroid is, this is the thread for it on xda. Basically, it lets you deny permissions to apps on a per-permission basis, without risking apps crashing. Same basic idea as LBE privacy guard, but in my opinion executed better. Plus, open source is always a plus. Even though the official patcher there won't work for us yet, check the official thread. You'll need to download the app from the market and follow the same instructions, just using the zips I'll post here (or make your own).
I'll include a revert.zip for anything I post here, but please note that I take no responsibility for anything that happens to your phone. Make backups before flashing things. Try TWRP if you haven't, it's faster at backup/restore than CWR and does a bunch of other neat stuff like compressed backups and queued zip flashing. Also, in case of things breaking, please note that these revert zips are (1) only going to work if you are running the same rom used to create the zip and (2) just a slimmed down version of the rom's zip. What this means is that if you flash a pdroid zip and you need to revert, the surest thing to do is just re-flash your rom without wiping anything.
I'll try to update this thread as I get more patches working. Here's where my own experiments stand:
Link to my dropbox folder with files, notes below
Working patches:
-AOKP b39 (toro):
-AOKP b39 (maguro):
-CM9 Nightly: Patched build: 2012/06/19
--Note: Not sure if these will automatically fail with later nightlies or only when something relevant is updated in the rom. Feel free to try, just reflash your rom if it bootloops.
-Stock AOSP(+root, busybox): Patched build: 2012/06/02
-Paranoid Android v1.4a
Not Working (Yet):
-Liquidsmooth 1.5RC4:
-Slim ICS 4.0:
Unless otherwise noted, these are all for the toro (verizon) Galaxy Nexus. It's pretty quick and easy for me to make new patches so feel free to request something. But please be aware that sometimes it's a few days between when I can devote any time to this and don't be offended if I don't reply to you right away.
Just to reiterate, all you need to do for this is download the "Pdroid Patch Zip" file for your rom, flash it in recovery, and download Pdroid from Google Play.
Finally, be aware that the first boot after flashing can take a very long time, without any indication like the "Android is Upgrading..." screen. Don't assume it's bootlooping! Seriously, put the phone down and do something else for a bit. Anything in the tested section I've either personally flashed on my phone or someone else reported as working. If you're sure you're getting a bootloop on a clean install, my only advice is to do a full revert to stock and re-unlock/root/etc and see if it works then. Though rare, it is possible for something to be corrupt that persists across the usual "clean install" routine.

Isn't that what Permissions Denied does?
https://play.google.com/store/apps/details?id=com.stericson.permissions

Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?

xternal said:
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
Click to expand...
Click to collapse
For gsm you'd need a new patch. There are instructions in the first thread I linked to if you'd like to try it out. I might make one in a bit since I expect that to be a popular request and I expect it to work.
danger-rat said:
Isn't that what Permissions Denied does?
https://play.google.com/store/apps/details?id=com.stericson.permissions
Click to expand...
Click to collapse
Same idea, different approach. Permissions denied generally causes apps to crash if they need info that they are denied. I also had a major issue with it a while back that I ended up doing a factory reset for, but I think that's been fixed since then.
Not sure how pdroid gets around apps fc'ing (maybe it spoofs data so apps go on running normally? It has an option to set your own values I haven't played with much), but it works very smoothly.

xternal said:
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
Click to expand...
Click to collapse
Quick update, I put up a maguro for AOKP, and I also updated the OP quite a bit since I last posted. Finally got around to testing the patches I made; getting better at reading the patching process as well to tell when a patch will work before flashing it, too.
At far as updates go, I don't really intend to follow the cm9 nightlies as I don't run them myself. I'll probably continue to try new versions of AOKP and paranoid android as they come out. I'll continue to try the roms that don't patch yet with new versions of the patcher as they are released.

Thank you. The maguro patch works for me.
Edit: not sure, but this likely breaks 2 apps: Listen, Drive.

I've been using LBE Privacy to control permissions and this app doesn't crash apps that have permissions blocked. It's one of their selling points, doesn't crash apps.

deaffob said:
I've been using LBE Privacy to control permissions and this app doesn't crash apps that have permissions blocked. It's one of their selling points, doesn't crash apps.
Click to expand...
Click to collapse
PDroid source has been released, whilst LBE created by a 'suspect' chinese company. I put the suspect in inverted comma's because nothing has actually been proven.
The patch works a treat on GSM aokp, many thanks
edit: looking at it though, it seems it doesn't find all the permissions correctly. I am assuming this is a limitation of the current pdroid as it is not designed for ics.
For instance it does not find hardware controls. Google Drive has access to hardware controls to take photos/videos.

Thanks for the confirmations on the maguro zip, I edited the post to reflect that it's definitely working.
I hadn't heard of LBE before making these threads but from what I've read it seems like people generally prefer pdroid. I'll check it out at some point but it looks like it does a bit more than I'd want it to, and pdroid being open source is definitely a plus.

IIRC, there's certain instances where apps can bypass LBE but not PDroid. I think reboot is one of those times due to when LBE loads.

I've been running LBE but lately the service keeps stopping because it doesn't get root soon enough after boot. Trying this now on Paranoid. Thanks!

i have used this patch for CM9 but after the Bootscreen have i a Blackscreen -.- what can i do?

SGDynamite said:
i have used this patch for CM9 but after the Bootscreen have i a Blackscreen -.- what can i do?
Click to expand...
Click to collapse
I'm guessing you are running a different build/more recent nightly? I might take that link down as it was meant as more of a proof of concept if the cm9 patcher was working and it's unlikely anyone is going to be flashing that particular build just to test pdroid.
The most effective thing would be to just re-flash the original rom's zip, you don't need to wipe anything. The revert zip file is basically just four files copied from a given rom's original zip, services.jar, core.jar and framework.jar in /system/framework, and build.prop in /system.

xternal said:
LBE created by a 'suspect' chinese company. I put the suspect in inverted comma's because nothing has actually been proven.
Click to expand...
Click to collapse
I hadn't heard of pdroid until I was on the Nexus, so I'm not familiar with it to compare, but I'm currently using LBE and blocking its data connections with Droidwall. Perhaps a bit overkill... but works great as far as I can tell.
Sent from my Galaxy Nexus using xda premium

JoeSyr said:
I'm guessing you are running a different build/more recent nightly? I might take that link down as it was meant as more of a proof of concept if the cm9 patcher was working and it's unlikely anyone is going to be flashing that particular build just to test pdroid.
The most effective thing would be to just re-flash the original rom's zip, you don't need to wipe anything. The revert zip file is basically just four files copied from a given rom's original zip, services.jar, core.jar and framework.jar in /system/framework, and build.prop in /system.
Click to expand...
Click to collapse
I think I flashed it to a nightly a day or two after 5-18 and it worked, but it definitely did not work on 5-27 or 5-29.
If the patch doesn't work for you, pull the battery, then hold volume up and down while you hold power, then use volume up and down to get to recovery option--press power to select. Either flash the revert or the old from there on top of the non-working one. Don't clear data partition and you won't lose anything.
@Joesyr, I think there is some interest in CM9 nightly patches...would you mind making a CM9 patch maybe once a week? I haven't had any luck making the patch on my own.

robjective said:
I think I flashed it to a nightly a day or two after 5-18 and it worked, but it definitely did not work on 5-27 or 5-29.
If the patch doesn't work for you, pull the battery, then hold volume up and down while you hold power, then use volume up and down to get to recovery option--press power to select. Either flash the revert or the old from there on top of the non-working one. Don't clear data partition and you won't lose anything.
@Joesyr, I think there is some interest in CM9 nightly patches...would you mind making a CM9 patch maybe once a week? I haven't had any luck making the patch on my own.
Click to expand...
Click to collapse
Well the last cm9 nightly I tried didn't patch at all (I believe it was a 5/29 build). I will try tinkering with things as I get the time but I'm not really at the level of fully understanding these kinds of failures yet.
Next time there's an updated cm9 patch I will try to get a working pdroid zip and I'll consider weekly updates. I'm also generally willing to make these on request as it's a pretty quick process. Fiddling with dropbox links is probably the longest part of any of this.
Any particular issue you're having with the patcher? I've been thinking I could write a little tutorial for getting cygwin up and running since I imagine that for most people the limiting factor is just that they don't have a linux environment to work in. But until I get the time to do that I can help troubleshoot.

Can you make a patch for stock root.
Thx

Has anybody experienced random rebooting? All was fine until I opened a non system app. Then it just started rebooting randomly after opening any app. I ran it on Maguro with AOKP b37.

soloxp said:
Can you make a patch for stock root.
Thx
Click to expand...
Click to collapse
Yup, not sure if the rom I just put up is the same you were looking for but it's the first one I've been able to get to patch correctly with the aosp patch.

Just flashed the Toro AOKP b37 patch, tested and working great here. Thank so much! Awesome work!!

What I would like is a simple ICS rom, but there are none!

Yep.
I just wish there was stock ICS for the HOV. Vanilla ics rom is close but it still has sense left over.
cm9 is far too unstable, and all my attempts at flashing various roms of JB are instable/not daily driver ready.
There don't seem to be any truly usable roms for this device. Stock sense is the only build in which everything works.
It's either one thing or another. If the camcorder works, the build might not work with simple apps like voxer. If voxer works, then mms won't work. If JB runs perfectly stable, then maybe the camcorder doesn't work. Does a rom that works without bugs like this exist? Here are a list of things I would need in a daily driver rom:
1. Camcorder- I'm a skater and I like to film fun edits of me and my hoodrat friends doing hoodrat things on our skates.
2. MMS - Such a simple necessity.
3. App compatibility -It drives me crazy when my important apps like voxer, instagram, facebook, and launchers lag badly or crash every time I open them
4. LAG - this is why I can't upgrade to JB, I thought provision Rom was AMAZING until I started using my apps (see #3)
5. Simple Multitasking
6. Random reboots - doesn't bother me too much but I could see it happening in some situation where I would need the phone immediately and have to try and explain to someone that "Herp, muh super custom droid phone likes to reboot so you'll just have to wait."
So far the only thing I can think of doing is building a stock ics rom (which I have no idea how to do). Any tips, first timer here.
Right now I just flashed back to stock and am going to run the de-sense tool. Why must OEMs ruin everything we love?
I hate to complain like this and I'm very glad there are devs working on the problems I describe. I guess I'm just venting my frustration. I love this phone but I have spent so much time trying to get a stock android experience that works. I would just buy galaxy nexus or an S3 but I'm a college and pre-paid cheap phones are the only way to fly right now, man. Sorry to sound so negative throughout the post but these are simply my observations in contrast with my needs and wants.
BTW first post on here. Don't hate me plz.

What do you mean CM9 is unstable?
Sent from an awesome phone

ryanlow134 said:
What do you mean CM9 is unstable?
Sent from an awesome phone
Click to expand...
Click to collapse
Exactly cm9 is 100% stable. Do a fill wipe before you flash
Sent from my One V using xda app-developers app

ok thanks! The only cm9 I could find was on the cdma dev forum and it said a number of things including the camcorder didn't work.
...and then I googled it and found exactly what I needed. Flashing now. We'll see how this works. Was there something I'm missing? I looked at this one [CDMA/PRIMOC][ROM] Unofficial CM9 for PrimoC Beta
480p video recording kind of suck but it'll have to do I guess.

Before u go knocking on peoples stuff how about u make a effort to fix it ur self and u can't say well I don't know how. Well sir u know that little company that bought android os yea sell they Also have a easy to use search bar and so does this little site u are on
And last how about u try and talk to the developers by posting in threads and asking if thus is a problem or even try p.m the developers the problem and I know that for sure u never messeaged me about a application messing up on our provisions rom
Thanks for using provisions ROM and do remember have a nice day.
Sent from my PK7630000 using xda app-developers app

Please check user's face. We are not responsible for your 'horrific' experiences while trying custom roms build by us if you are too noob enought to not do a full wipe before you flash a rom.
Thank you and see you in the other side!

1ceb0x said:
you are too noob enought to not do a full wipe before you flash a rom.
Click to expand...
Click to collapse
No. Just because this is my 3rd post doesn't mean I haven't done my homework.
sbkjuggalo said:
And last how about u try and talk to the developers by posting in threads and asking if thus is a problem or even try p.m the developers the problem and I know that for sure u never messeaged me about a application messing up on our provisions rom
Click to expand...
Click to collapse
I did for the Vanilla ICS rom. Sorry about yours but I was going through a series of JB on my device and they all had the same problems with app compatibility/stability.

DrZaiusIsAlive said:
No.
I did for the Vanilla ICS rom. Sorry about yours but I was going through a series of JB on my device and they all had the same problems with app compatibility/stability.
Click to expand...
Click to collapse
Dude before flashing you must wipe your device properly.
Sent from my One V using xda app-developers app

DrZaiusIsAlive said:
No. Just because this is my 3rd post doesn't mean I haven't done my homework.
I did for the Vanilla ICS rom. Sorry about yours but I was going through a series of JB on my device and they all had the same problems with app compatibility/stability.
Click to expand...
Click to collapse
Don't know about comatibility/stability. Using CM10 from Lloir and works flawless for me, and yes, I'm using mms, camcorder, apps of a wide range, and yes, this is my primer and only phone, so I can say that it is stable too. Only camcorder problem I found that autofocus is somehow misbehaving in video recording.
Full wipe is essential for stability if you flash a rom that is based on something else, than the last one you used. I even erase sometimes the sdcards android and secure partitions if must. I tried Lloir's slimbean just this morning and seems promising enough, really thinking about to change to that rom permanently.

Full wipe means:
Factory reset (this will delete cache and dalvik cache - this will also remove the .android_secure folder)
Wipe system
Flash rom
Flash the correct kernel in bootloader
Reboot your phone
Voila, rom without any issues at all!
Don't tell me you did all these and you still have problems with JB and other custom roms. I just don't buy it. Everyone here that uses a custom rom are so enthusiastic about them, they don't even wanna get back on sense. I am having Paranoid Android on my One V from the moment I started making the rom for us, since August. From then onwards, I've only used this rom. I don't think that there are any kind of instability with it, because I test my roms before releasing them so if it was unstable, why should've I used it for more than 4 months now?

1ceb0x said:
Full wipe means:
Factory reset (this will delete cache and dalvik cache - this will also remove the .android_secure folder)
Wipe system
Flash rom
Flash the correct kernel in bootloader
Reboot your phone
why should've I used it for more than 4 months now?
Click to expand...
Click to collapse
1. I do all those. This is is my third android device. I used to have a galaxy tab 2 rom'd with cm10 and it was awesome. But even it had some problems with app compatibility. I got my learning in on that device. I nearly bricked it 3-4 times haha.
2. We use our phones differently. There are probably a ton of apps I use and a ton you don't. I know for sure that draw something is incompatible with JB itself.
I'll probably flash PA soon if some issues pop up with the cm9 build I'm using now.

Draw something is compatible with jellybean no doubt since I installed it on my HOV and it works.

[WIP][ROM][Verizon] CM10.1 for LG G2 (Verizon) looking for help!!

Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: kernel, device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_kernel_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
10/17/13:
http://forum.xda-developers.com/showpost.php?p=46554268&postcount=271
10/12/13: alpha
http://forum.xda-developers.com/showpost.php?p=46407049&postcount=138
10/3/13: Super alpha
http://forum.xda-developers.com/showpost.php?p=46147336&postcount=74

I would love to help, but I admit I don't know much about Android development. I've got an AT&T G2 and I know C# and a bit of C++, so I'm sure I can figure out C. I think it's awesome that you're working on CM, if I can help out somehow I'd love to!

Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?

bose301s said:
Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?
Click to expand...
Click to collapse
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.

fonix232 said:
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.
Click to expand...
Click to collapse
Ok, that is what I was thinking but I have never done any dev work or anything so I figured I would ask.

I cant help but I sure want to thank you folks for trying to get this up and running. This phone is an absolute BEAST! Coming from the gnex I'm excited about the G2's potential.
Sent from my VS980 4G using Tapatalk 4

Thanks!
I just wanted to thank you very very much for working on this! I knew this was going to be a well developed phone and I bet before 4 months we will have a good amount of choice as far as roms go. Thanks again!

I've been trying to port beanstalk to the G2 but I need the same information you are trying for. I need device trees to sync with. I can PM you with what info I've came up with So far if you are interested.?
Edit: tress are up! Great work
Sent from my LG-D800 using xda app-developers app

If you lived in my town I'd probably help by cleaning the gutters for you hehe. Thanks for your work!
Sent from my EVO using xda app-developers app

I am definitely willing to help in any way I can.

I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...

grandmasterlarry said:
I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...
Click to expand...
Click to collapse
same goes for me, I have the Korean version.

Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?

mrbig012 said:
Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?
Click to expand...
Click to collapse
LG UI feature. I'm fairly sure it will be ported to an AOSP/CM10/LGUI hybrid ROM at some point. I believe part of the issue that devs are running into is that a lot of the custom LG software appears to be tied together.

Can you guys keep us updated on your progress, this is a make or break thing for me with this phone, CM is just so much better than any stock ROM that I don't know if I can deal with a phone that has no prospect of official support.

JackpotClavin said:
Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
Click to expand...
Click to collapse
Are we going to try getting mobile network and wifi working first? Is adb working?

droid_<3er said:
Are we going to try getting mobile network and wifi working first? Is adb working?
Click to expand...
Click to collapse
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source

JackpotClavin said:
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source
Click to expand...
Click to collapse
I am NOT a developer, but this could help perhaps?
http://opensource.wolfsonmicro.com/content/wm5110-linux-driver-released
Not sure if it really is open source or only available as binaries, but the WM5110 is the audio SoC in this phone... I am probably not helping.
Additionally, I think the S4 uses this SoC as well. It's a pretty new part but is gaining a lot of momentum.
Edit: My god that WM5110 is a hell of a part... quad-core, 600 MIPS... dayum!

Glad to hear an update, even if it's about issues. Seeing that there are people actively working on this to make it happen makes me much happier and less worried about keeping this phone vs. returning it tomorrow or Friday to see how the Nexus 5 plays out etc.

Have any of you tried talking to Ricardo Cerqueira? He is in fact the primary maintainer for all LG Devices with regards to Cyanogenmod. I am sure he is planning on supporting this device in the near future, I just don't know when. It will probably be when the device is more readily available since it was pretty much just released.

[ROM] [Unofficial] [LOS15.1] Lilly's LineageOS CookieJar

Hi everyone!
This is just my corner where I drop the builds of Lineage-15.1 that I personally use. They do contain a few smaller customisations, like a custom kernel and other goodies that I personally need. I'm posting this here in case somebody finds them to be useful.
Nooby Disclaimer:
I'm not a developer and just because I've got a thread here, doesn't mean I fully know what I'm doing when modding or building ROMs. What I publish is used by myself personally and thereby tested as daily driver. If something still breaks and your phone doesn't survive the smoke test, that's your problem and not mine.
Builds will mostly cater towards my needs if I have any special wishes with the hopes that the changes are useful or interesting for someone else as well (won't be too deep changes I think).
Some info/bugs specific to this build:
SELinux defaults to permissive
Make sure you tell OpenGapps to keep LineageOS Snap installed, Google Camera crashes.
Fails SafetyNet Test, don't use if you need that to verify.
OTA Support (Can somebody confirm that it works?.). The Updater should notify you of a new version.
Other than that, there's not much to say about it. It's LineageOS 15.1, what more could you wish for?
Download link:
http://tf2glados.dynv6.net:8080/
(It's in the LineageOTA folder)
Sources:
http://github.com/LineageOS
http://github.com/LineageOS/android_device_nextbit_ether
http://github.com/LineageOS/android_kernel_nextbit_msm8992
https://github.com/linckandrea/Pop-kernel-ether-LOS14.1-15.1
http://review.lineageos.org/

Mine mineminemineminemineminemine

Another one

It's kind of impressive you managed to miss that I post 15.1 unofficials in the 14.1 thread.

javelinanddart said:
It's kind of impressive you managed to miss that I post 15.1 unofficials in the 14.1 thread.
Click to expand...
Click to collapse
I'm going to ignore the passive-aggressiveness and just go ahead and argue that with time that my builds will deviate a tiny bit from vanilla Lineage here and there, be it only tiny tweaks and goodies like Pixel Navbar, kernel with Kali Nethunter support and OTA support. Besides, I wouldn't expect a 14.1 thread to contain Lineage15.1, now would I? Fss.

Alexandroid99 said:
I'm going to ignore the passive-aggressiveness and just go ahead and argue that with time that my builds will deviate a tiny bit from vanilla Lineage here and there, be it only tiny tweaks and goodies like Pixel Navbar, kernel with Kali Nethunter support and OTA support. Besides, I wouldn't expect a 14.1 thread to contain Lineage15.1, now would I? Fss.
Click to expand...
Click to collapse
No need to get snippy. Just commenting that I've been running builds for weeks now bringing up 15.1, and there's 40+ people in the hangouts group I made. I can't stop you from releasing builds or building from my sources (and nor do I care to), just letting you know that it's incorrect to say nobody's been building unofficials.

Sorry, I do apologise, but your comment did sound passive-aggressive even after reading over it multiple times. My point still stands though.

working like a champ but having issue with the figer print

karthikpl said:
working like a champ but having issue with the figer print
Click to expand...
Click to collapse
Working for me just fine. Just a tiny bit inaccurate as always.

http://tf2glados.dynv6.net:8080/LineageOTA/builds/full/lineage-15.1-20180401-NIGHTLY-ether.zip

Hello. I installed the UNOFFICIAL version. But the Nighly version is not. How do I install the Night version?

kinhkinhls said:
Hello. I installed the UNOFFICIAL version. But the Nighly version is not. How do I install the Night version?
Click to expand...
Click to collapse
Not sure what you are asking, but I had to override the build type branding to NIGHTLY in order to have the OTA server working. Just flash it over the old version. If you're using twrp and it doesn't want to flash, I'll have a Lineage recovery here, flashing that and then flashing the update using the lineage recovery always worked for me. http://tf2glados.dynv6net:8080/LineageRecovery/
Otherwise, just update TWRP. I tried it with the latest TWRP version just now and it works.

Download link is not working
Link is not working bro. Send me link

Quick note:-
OP is away at the moment and shall update the links upon return. :good:
Edit :- Download links are up an running.

Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.

batp said:
Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.
Click to expand...
Click to collapse
I haven't had any issues with that and I wouldn't consider it a build-specific bug, but I might be able to help you anyway. Plug in the phone, go to developer options and tap on "Select USB Configuration" and set it to MTP. That mostly fixes hiccups with USB modes for me. Otherwise, try replacing the cable if you're using the original Nextbit one that came with it. Mine became really unreliable soon after buying the phone, so I replaced it with a better (USB 3.1, even) cable and now it just works.

batp said:
Hello, thank you for working on this.
I flashed it yesterday and had an issue with mounting USB to my windows computer.
It worked on the first boot, and I was able to pull down the notification bar and tell it to transfer files. However on subsequent boots it did not give me such an option, although rebooting to recovery with the cable plugged in the same way mounted the device in my computer.
Click to expand...
Click to collapse
I might have found the technical reason behind it.
https://github.com/LineageOS/androi...mmit/99a8ea97e55cc7f9e28a2b7009325647110dc638
I'll rebuild when I get home, so that will include this fix.

Short note here, my Raspi server died on me again, so sorry for the dead links again. Buuut I'll be home soon, so I can get around fixing the Pi and the downloads will be up again just in time for a new build.

Enjoying the new build so far! Pretty good for me.

http://tf2glados.dynv6.net:8080/LineageOTA/builds/full/lineage-15.1-20180605-NIGHTLY-ether.zip