Develop Bugs

Scoot CyanogenMod 7.1.0 RLS3 (Gingerbread 2.3.5) [07/08/11]

Scoot CyanogenMod 7.1.0 RLS3
This is a build I have compiled from the official CyanogenMod source files and adapted for Kaiser/Vogue. Feel free to give it a go at your own risk!
Well, it still isn't quite as snappy as Froyo and the camera still doesn't work properly but it's probably about as fast as Gingerbread will get on our devices. I'm bound to have messed a few things up but i'll continue to work on it when I get time
All the usual things are working as far as i know, GPS works fine for me but the camera is as always not fully functional.
All of this is thanks to the guys working on the CyanogenMod roms and of course, none of this would work without all the hard work on the kernel so big thanks to dzo, vilord, l1q1d etc...
-------------------------------------------------------------------------------------
RLS 1:
Initial Release
Includes most of the Google Apps including Maps, Gmail etc..
Latest Market is included
RLS2:
Built from the latest 7.0.2 source
Optimised EGL for our devices
Updated Market
LDPI and PNG optimisations to save space & increase speed
ADW Launcher updated
Loads of tweaks and status bar changes
Updated RIL lib
Loads of fixes and optimisations
**I recommend leaving the phone for 5 minutes after installing to sort itself out and cache apps etc...**
RLS3:
I can't really be bothered to list all of the changes, there are quite a few but I just compile the thing, the changes are in the CyanogenMod repository. I have included the updated RIL and all of the Google Apps are up to date. The camera is still ****e but that's a driver issue. This release hasn't been heavily tested as I don't use my Kaiser as a main phone anymore So i'm sure you will find issues in which case we can sort them out as and when. Enjoy!
LINKS:
RLS1:
English: http://www.mediafire.com/?6708ud8kc9l9ex5
All Languages: http://www.mediafire.com/?amhd996w81xfldp
RLS2:
English: http://www.mediafire.com/?yhsc6jyl47wgpkv
All Languages: http://www.mediafire.com/?v3hhbh5tufoedfp
RLS3:
English: http://www.mediafire.com/?76vn9k0cx3debzd
All Languages: Coming soon!
Google Apps
28.04.11 : http://www.mediafire.com/?4yc9ubn2m513k3q
07.08.11 : http://www.mediafire.com/?c86rpae5kopdicc
I think that's it for now, have fun

OOOOOyyyyéééééé OOOOoyyyyyéééé !!!!
download'n !!!
thinx scooter & all android developers for our old kaiser
'll try your build this night & report any bugs...
keep working i realy apreciate your work sccooouut
xcuse my stupide bad english
cordialement esolks.

scooter1556 said:
Scoot CyanogenMod 7 alpha RLS1
This is a build i have compiled from the official CyanogenMod source files and adapted for Kaiser/Vogue. Feel free to give it a go at your own risk!
This is an alpha and still needs a fair bit of work to get it running to it's full potential but you can get an idea of what it will be like. Feel free to report any bugs that you find, by this i mean application crashes and things that don't work or look correct. I already know the system can hang and it isn't as fast a froyo
I have had to make a LOT of modifications for this to work, some of which may affect battery life but i haven't tested it for long enough to know so let me know how it goes. I'm bound to have messed a few things up but i'll continue to work on it when i get time
All the usual things are working as far as i know, i have not tested GPS fully and the camera is as always not fully functional.
All of this is thanks to the guys working on the CyanogenMod roms and of course, none of this would work without all the hard work on the kernel so big thanks to dzo, l1q1d etc...
-------------------------------------------------------------------------------------
RLS 1:
Initial Release
Includes most of the Google Apps including Maps, Gmail etc..
Latest Market is included
LINKS:
RLS1 :
English : http://www.mediafire.com/?6708ud8kc9l9ex5
All Languages : Coming soon hopefully.....
I will try and get some screen shots posted for those that like pretty pictures
I think that's it for now, have fun
Click to expand...
Click to collapse
This might be a stupid question but I need to ask anyway...is CM 7 based on gingerbread?

-Arturo- said:
This might be a stupid question but I need to ask anyway...is CM 7 based on gingerbread?
Click to expand...
Click to collapse
It is indeed

scooter1556 said:
It is indeed
Click to expand...
Click to collapse
Excellent, thanks Scooter.

downloading now keep up the good work man

woot...gonna give it shot ... hoping for not getting same data/wifi reboots

woow, million thanks to you scooter
finally a gingerbread based build for our kaiser
btw, which kernel do you suggest for this build?
thanks in advance

Hmm for some reason I cannot boot to android the phone has been stuck in boot loop for the last 15 minutes. I have an app.img file with about 80 applications so this might be a problem I'll try to boot it without the app.img. Both data and system on sd card imgs + latest '25 kernel.
Edit.
Ok I have removed the apps.img and it still doesn't boot.
I have noticed that there have only been modules for '32 kernel included in the build. Should it work with '25 kernel with proper modules added?

I'll wait for All Languages version to test it with the new kernel.

1. this was my first attempt to instal android on nand.. noob here ;P
downloaded kernel VOGUIMG-320-FROYO-01-16-11.NBH, then changed with editor to kaiser and painel 2. Install occured ok.... but phone isn't working.. "no service".
2. I do i see my batery status? can only see that bar on the top but don't no accurate bat status in %.
3. after this install can i install another another version overwrithing this one? for example now the phone isn't working so i want to change to another version of android can i simply put another "androidinstal.tar" in andboot folder and install?
Thanks and sorry for this noob questions...

chinomoreno said:
1. this was my first attempt to instal android on nand.. noob here ;P
downloaded kernel VOGUIMG-320-FROYO-01-16-11.NBH, then changed with editor to kaiser and painel 2. Install occured ok.... but phone isn't working.. "no service".
2. I do i see my batery status? can only see that bar on the top but don't no accurate bat status in %.
3. after this install can i install another another version overwrithing this one? for example now the phone isn't working so i want to change to another version of android can i simply put another "androidinstal.tar" in andboot folder and install?
Thanks and sorry for this noob questions...
Click to expand...
Click to collapse
YES! you can
To view Battery percentage, you need to set that in Cyanogenmod Settings (correct me if I'm wrong here since its been ages when I used CM build)

Yes, you can do that it's actually very simple. Just remember to edit your .nbh before every install if you are changing versions (donut, froyo, eclair).
Cheers. Welcome to Android world

-Arturo- said:
Hmm for some reason I cannot boot to android the phone has been stuck in boot loop for the last 15 minutes. I have an app.img file with about 80 applications so this might be a problem I'll try to boot it without the app.img. Both data and system on sd card imgs + latest '25 kernel.
Edit.
Ok I have removed the apps.img and it still doesn't boot.
Click to expand...
Click to collapse
Try a .32 kernel, also i have only tested it on NAND so it may be an issue with Haret. To be honest we're lucky it works with the .32 kernel so i expect problems with the .25 kernel. Sorry

scooter1556 said:
Try a .32 kernel, also i have only tested it on NAND so it may be an issue with Haret. To be honest we're lucky it works with the .32 kernel so i expect problems with the .25 kernel. Sorry
Click to expand...
Click to collapse
Yes I have noticed that there have only been '32 modules included in the build.
I think I'm going to skip the '32 kernel as It was acting up on me in the past. I'll try nand install in the evening hopefully it will work. Thanks Scooter.

-Rif- said:
woow, million thanks to you scooter
finally a gingerbread based build for our kaiser
btw, which kernel do you suggest for this build?
thanks in advance
Click to expand...
Click to collapse
I recommend using the latest .32 kernel you can find, either one that L1q1d has compiled or one from Clemsyn's thread You can find the latest kernel here: http://androidhtc.git.sourceforge.n...7c0bf5edc4f5c6d64ce4df29254e8332ce26b;hb=HEAD

Well have installed 6.1 and phone now works... =)
Will wait until a new version of this one to come out and then try again...
- Already found how to show percentage in bar status thanks dark_prince.
- Thanks for advice slimas, to edit .nbh do i need to reinstall kernel? and can i reinstall without mess up with previous android install or do i need to install again android?
- Some bugs that occurred to me .. sometimes bar on the bottom disappear can't access apps... ; some freezing sometimes, do you guys recommend to overlock? if so how to do it? Weather widget can't find info too lol not a serious prob...
I'm reading forum and these are some questions i couldn't find answer, for now i think that's all.. i'm enjoying android on kaiser think this is the time i will change forever...
thanks for fast feedback any good tips are welcome ;P

chinomoreno said:
- Some bugs that occurred to me .. sometimes bar on the bottom disappear can't access apps... ; some freezing sometimes, do you guys recommend to overlock? if so how to do it? Weather widget can't find info too lol not a serious prob...
Click to expand...
Click to collapse
The bar at the bottom of the scrren can disappear if you swipe down on the screen, it is a bit random but is a flaw in ADW launcher. To get it back you need to press the 'menu' button and go to 'settings' then go to 'ADW Settings, UI Settings and untick 'Dockbar'. Re-select 'Dockbar' and exit settings and it should be back I expect some freezing, it is still under heavy development and our devices are quite limited hardware wise so there won't be any miracles yet I overclock my Kaiser to 500Hz using ATools, a lot of people don't recommend it but it is what i have always done and i have never had any problems, it speeds the phone up a fair amount. Just tick the option when editing your NBH. The phone obviously needs to be connected to data or wifi for weather widget to get location information, i just tried it with wifi and it worked ok, there may be an issue with data though, i'll look into it Thanks for testing.

CAMERA
camera is not working properly but it looks awesome i will try to apply the update from previous cm to see if this will work

camera
after applying the update android can`t start so i am going reinstall it

[ROM][AOSP 2.3.7] OMFGB compiled and ported

Hy all,
inspired by this thread I spend some spare time in compiling OMFGB sources for use with the hero gsm.
Because of the fact, that I did not manage to successfully compile the OMFGB sources directly for the hero gsm (compiling was OK but could not get rom to boot) I did it the other way.
I compiled the sources for the hero cdma (heroc) and afterwards ported it to hero gsm.
I integrated Erasmux fly-kernel 13 since I used it with all other hero roms before.
After testing the rom for ~1 week (also my son is quite satisfied with it) I decided to share it.
I took out some apps that were not usable (for example God Mode) and put in minimal gapps so that it's possible to sign in on google account and run market.
Also I replaced the LatinIME.apk with the CMs one to get other keyboard layouts than querty.
I'd recommend to install morelocale2 to be able to dial 123456 instead of 123-456.
What I have to say is that I'm by far no developer (at least not on android platform).
Download
OMFGB-Hero -www.2shared.com
OMFGB-Hero - www.mediafire.com
Thanks and credits go to
OMFGB Team for their sources
Erasmux for the kernel
stritfajt and bharat_goku for their patients and giving me directions

i'll take a look at this when i've got some spare time

Thanks for the ROM but OMFGB without God mode? its like CM7 without CM settings lol D

cartman333 said:
Thanks for the ROM but OMFGB without God mode? its like CM7 without CM settings lol D
Click to expand...
Click to collapse
God mode seems not to be compatible with hero, all menu entries were grayed out, so I decided to delete it from package.
Maybe someone has a clue how to get it run

Can you upload it to some other site? I can't seem to download from 2shared.

aca89 said:
Can you upload it to some other site? I can't seem to download from 2shared.
Click to expand...
Click to collapse
Uploaded to mediafire

Just checked the zip,replace the heroc files in use/keylayout,keychars wit similar files from a hero rom,basically key functionality
Sent from my Hero using xda premium

bharat_goku said:
Just checked the zip,replace the heroc files in use/keylayout,keychars wit similar files from a hero rom,basically key functionality
Sent from my Hero using xda premium
Click to expand...
Click to collapse
I ported and tested the rom step by step.
Since all keys work as they should, I skipped this step.

I gave it a go. Not bad, for some reason I had extremely good wifi reception using this ROM, so that's good. Really missed some kind of advanced settings 'cause I use a lot of options from there and that was a dealbreaker . Also a2ext didn't work, so I had to flash darktremor script which caused i few random reboots. All in all, a solid ROM which could be much improved.
Cheers

aca89 said:
I gave it a go. Not bad, for some reason I had extremely good wifi reception using this ROM, so that's good. Really missed some kind of advanced settings 'cause I use a lot of options from there and that was a dealbreaker . Also a2ext didn't work, so I had to flash darktremor script which caused i few random reboots. All in all, a solid ROM which could be much improved.
Cheers
Click to expand...
Click to collapse
For the advanced settings, I could not get the God_Mode fully working so far.
For a2ext, I don't use it since I don't need it.
My son, which has a hero too, uses a lot of games.
For him I did custom mtd layout, much faster than a2ext cause it's kept all internal.

Please add the Russian.

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.

[AOSP Tamien 8.1 with OpenGapps]

I was able to use https://github.com/anestisb/android-prepare-vendor to prepare the vendor images to correctly build AOSP.
I submitted some changes to make it work with Pixel2-XL and they have been merged into main branch.
You have to wipe everything.
I dont know how to make proper zip images for TWRP so use fastboot
I use the fastboot script included in the zip after a full wipe and im all good
Thanks:
anestisb on Github
opengapps
not working:
pixel squeeze
AOSP 8.1 with google apps:
V3:
https://www.androidfilehost.com/?fid=889964283620776051
AOSP 8.1 stock (no gapps):
https://www.androidfilehost.com/?fid=817906626617955840
changelog:
v3:
Jan security update
v2:
updated camera
pixel launcher
updated wallpaper that was causing errors
fixed google setup errors during startup and boot
archive:
v2: https://www.androidfilehost.com/?fid=817906626617955877
V1:
https://www.androidfilehost.com/?fid=745849072291697825
During first boot google setup crashes a bit and I just skip it ...then on reboot I get complaints about stuff. but everything works. so......

deeproot said:
I built AOSP with OpenGapps and all I got was this forum thread
You have to wipe everything.
I dont know how to make proper images so use fastboot
I use the fastboot script included after a full wipe and im all good
Click to expand...
Click to collapse
Link?
Sent from my Pixel 2 XL using Tapatalk

yea, link?

?????

Don't tease us like this, lol. I'll flash anything at this point!
Sent from my Pixel 2 XL using Tapatalk

uplodz complete.

Interesting :good:

I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!

prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
I thought the whole point of gapps is Google *****es if you build a Rom with google apps installed already...

prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
u did add in the propietary drivers i assume before u started making ur build?
this build is running smooth! i almost wanna say u couldve left gapps out n let ppl choose which they want to use but of cpurse this is only the beginning.. first thing i did was remove all those google hotword apks that fc, not had any issues yet and u already stated squeeze isnt on here but i nvr used that anyways
I was building from source today but my env has a ways to go before its useable.. it literally took all day to make aosp arm64 eng lol.. started gettin low mem stops towards the end so gonna look at it tom... i actually need to change it up and tweak settings cuz i only got 6gb ram
my set up tho is ur aosp, flash kernel 2.05 and magisk 15.1.. butter.. or shall i say vanilla??

prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
aosp i dont think includes automatocally.. its runnin android web view n all lol instead of chrome that is

Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.

jgreen077 said:
Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.
Click to expand...
Click to collapse
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself

jgreen077 said:
Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.
Click to expand...
Click to collapse
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself

elliwigy said:
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself
Click to expand...
Click to collapse
Honestly, I'd normally listen and hold off. But since I have a day off I think I'm gonna attempt it just for the sake of learning!
As long as it has the Play Store so I can download the apps I want, I'm good. If I can get all the apps I need to than I'll be a happy camper.
Say later on it's decided I want to go to another AOSP rom, am I going to have to wipe again? If I can get all my apps, won't have to wipe my device every other week, and can get my modules installed I should be good to do some good old fashioned experimentation.
I am not a smart man, at times. I'm gonna try it out. I have a few hours before anyone else is awake. Might as well use that time (un)wisely.
Plus I believe these "vanilla" ROMs, being what they are, can be modded to an even greater extent than the already pretty modifiable "stock" Pixel ones. Please correct me if I'm wrong.

prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
I found this:
https://github.com/anestisb/android-prepare-vendor
I submitted my changes and they will update in a few days to the add tamien support.

I am going to hold off on this for now, as it's just a shell of what custom Android can be but just wanted to say thank you very much for getting the ball rolling. For giving us hope haha. I check the thread at least 4 times a day and my heart jumped when I saw this post! Good work!

Nice can we flash the Kernels that have been around here for a while on this rom?

patt2k said:
Nice can we flash the Kernels that have been around here for a while on this rom?
Click to expand...
Click to collapse
I flashed Elemental X and finger print stopped working.

deeproot said:
I found this:
https://github.com/anestisb/android-prepare-vendor
I submitted my changes and they will update in a few days to the add tamien support.
Click to expand...
Click to collapse
@deeproot
have you uploaded your WIP android_prepare_vendor anywhere? I would like to clone your changed repo and run this script if possible.
I attempted to manually add your changes in the pull request, but the script is breaking with a debugfs error
Thanks,
Edit: Found it, still getting same debugfs error.
Code:
[*] Extracting '/tmp/android_prepare_vendor.jlQiR6/taimen/opm1.171019.011/taimen-opm1.171019.011-factory-2df1c1cb.zip'
[*] Unzipping 'image-taimen-opm1.171019.011.zip'
[-] Symlinks have not been properly processed from /tmp/android_img_extract.FRWAOM/taimen-opm1.171019.011-factory-2df1c1cb/images/vendor.img.raw
[!] If you don't have a compatible debugfs version, modify 'execute-all.sh' to disable 'USE_DEBUGFS' flag
[-] Factory images data extract failed
[email protected] ~/Desktop/android-prepare-vendor $