LG Optimus S: 4.4 KitKat?

Toggle sidebar Toggle sidebar
Re: 4.4 KitKat?

Good idea. I just ordered a 500gb hd for my laptop, I pretty much maxed out my storage capacity on my 160gb. You want to leave the intermediate files on disk if possible, especially if you have a slow machine because you can recompile the system about 10 times as fast (but sometimes you have to delete the object files). I sent a pm about the recovery, thanks.
 
Re: 4.4 KitKat?

I'm a little slow today. Watching tv and checking on repo sync (had to run command again because my network failed at some point). Will check pm.
 
Re: 4.4 KitKat?

Shoot me a link and I'll test as well. Also no my way around adb and have everything I need to unbrick but I doubt I'd get in deep enough to need that

Sent from my LG-VM670 using Tapatalk 2
 
Re: 4.4 KitKat?

Had to do a repo sync this morning due to same network failure last night (really slow network). This is what the end results was:
Code: 
Fetching projects: 100% (437/437), done.  
Checking out files: 100% (26967/26967), done. files:   6% (1860/26967)   
Checking out files: 100% (5713/5713), done.ut files:  10% (628/5713)   
Checking out files: 100% (2438/2438), done.out files:  16% (412/2438)   
Checking out files: 100% (9389/9389), done.out files:  36% (3445/9389)   
Checking out files: 100% (45876/45876), done.
Checking out files: 100% (9597/9597), done.out files:   9% (939/9597)   
Checking out files: 100% (4301/4301), done.out files:   1% (73/4301)   
Checking out files: 100% (4082/4082), done.out files:  29% (1211/4082)   
Checking out files: 100% (3349/3349), done.out files:  18% (603/3349)   
Checking out files: 100% (7954/7954), done.
Checking out files: 100% (5580/5580), done. out files:  22% (1233/5580)   
Checking out files: 100% (3573/3573), done. out files:   8% (317/3573)   
Checking out files: 100% (11685/11685), done.ut files:  17% (2057/11685)   
Checking out files: 100% (4093/4093), done. out files:  47% (1928/4093)   
Checking out files: 100% (730/730), done.ng out files:  20% (146/730)   
Checking out files: 100% (871/871), done.ng out files:  15% (136/871)   
Checking out files: 100% (1654/1654), done. out files:  23% (396/1654)   
Checking out files: 100% (3924/3924), done.
Checking out files: 100% (2927/2927), done. out files:  33% (970/2927)   
Checking out files: 100% (22241/22241), done.
Checking out files: 100% (113/113), done.ng out files:  46% (53/113)   
Checking out files: 100% (1553/1553), done. out files:   0% (8/1553)   
Checking out files: 100% (376/376), done.ng out files:   7% (27/376)   
Checking out files: 100% (431/431), done.ng out files:   3% (13/431)   
Checking out files: 100% (171/171), done.
Checking out files: 100% (175/175), done.ng out files:  12% (22/175)   
Checking out files: 100% (181/181), done.
Checking out files: 100% (135/135), done.
Checking out files: 100% (192/192), done.
Checking out files: 100% (378/378), done.ng out files:  39% (149/378)   
Checking out files: 100% (109/109), done.
Checking out files: 100% (433/433), done.
Checking out files: 100% (181/181), done.
Checking out files: 100% (2407/2407), done. out files:  32% (792/2407)   
Checking out files: 100% (2482/2482), done.
Checking out files: 100% (2484/2484), done.
Checking out files: 100% (177/177), done.
Checking out files: 100% (182/182), done.ng out files:  43% (80/182)   
Checking out files: 100% (137/137), done.
Checking out files: 100% (193/193), done.
Checking out files: 100% (128/128), done.
Checking out files: 100% (50299/50299), done.ut files:   6% (3023/50299)   
Checking out files: 100% (4864/4864), done.
Checking out files: 100% (4383/4383), done.
Checking out files: 100% (28/28), done.
Checking out files: 100% (182/182), done.ng out files:   1% (2/182)   
Checking out files: 100% (1256/1256), done.
Checking out files: 100% (2951/2951), done.
Checking out files: 100% (89/89), done.king out files:  49% (44/89)   
Syncing work tree: 100% (437/437), done.  

andyopie150@Dell-OptiPlex-GX620DT:~/android/kitkat$
Is the % figures normal, or should I try to sync repo again?
 
Re: 4.4 KitKat?

AndyOpie150 said:
Had to do a repo sync this morning due to same network failure last night (really slow network). This is what the end results was:
Code: 
Fetching projects: 100% (437/437), done.  
Checking out files: 100% (26967/26967), done. files:   6% (1860/26967)   
Checking out files: 100% (5713/5713), done.ut files:  10% (628/5713)   
Checking out files: 100% (2438/2438), done.out files:  16% (412/2438)   
Checking out files: 100% (9389/9389), done.out files:  36% (3445/9389)   
Checking out files: 100% (45876/45876), done.
Checking out files: 100% (9597/9597), done.out files:   9% (939/9597)   
Checking out files: 100% (4301/4301), done.out files:   1% (73/4301)   
Checking out files: 100% (4082/4082), done.out files:  29% (1211/4082)   
Checking out files: 100% (3349/3349), done.out files:  18% (603/3349)   
Checking out files: 100% (7954/7954), done.
Checking out files: 100% (5580/5580), done. out files:  22% (1233/5580)   
Checking out files: 100% (3573/3573), done. out files:   8% (317/3573)   
Checking out files: 100% (11685/11685), done.ut files:  17% (2057/11685)   
Checking out files: 100% (4093/4093), done. out files:  47% (1928/4093)   
Checking out files: 100% (730/730), done.ng out files:  20% (146/730)   
Checking out files: 100% (871/871), done.ng out files:  15% (136/871)   
Checking out files: 100% (1654/1654), done. out files:  23% (396/1654)   
Checking out files: 100% (3924/3924), done.
Checking out files: 100% (2927/2927), done. out files:  33% (970/2927)   
Checking out files: 100% (22241/22241), done.
Checking out files: 100% (113/113), done.ng out files:  46% (53/113)   
Checking out files: 100% (1553/1553), done. out files:   0% (8/1553)   
Checking out files: 100% (376/376), done.ng out files:   7% (27/376)   
Checking out files: 100% (431/431), done.ng out files:   3% (13/431)   
Checking out files: 100% (171/171), done.
Checking out files: 100% (175/175), done.ng out files:  12% (22/175)   
Checking out files: 100% (181/181), done.
Checking out files: 100% (135/135), done.
Checking out files: 100% (192/192), done.
Checking out files: 100% (378/378), done.ng out files:  39% (149/378)   
Checking out files: 100% (109/109), done.
Checking out files: 100% (433/433), done.
Checking out files: 100% (181/181), done.
Checking out files: 100% (2407/2407), done. out files:  32% (792/2407)   
Checking out files: 100% (2482/2482), done.
Checking out files: 100% (2484/2484), done.
Checking out files: 100% (177/177), done.
Checking out files: 100% (182/182), done.ng out files:  43% (80/182)   
Checking out files: 100% (137/137), done.
Checking out files: 100% (193/193), done.
Checking out files: 100% (128/128), done.
Checking out files: 100% (50299/50299), done.ut files:   6% (3023/50299)   
Checking out files: 100% (4864/4864), done.
Checking out files: 100% (4383/4383), done.
Checking out files: 100% (28/28), done.
Checking out files: 100% (182/182), done.ng out files:   1% (2/182)   
Checking out files: 100% (1256/1256), done.
Checking out files: 100% (2951/2951), done.
Checking out files: 100% (89/89), done.king out files:  49% (44/89)   
Syncing work tree: 100% (437/437), done.  

andyopie150@Dell-OptiPlex-GX620DT:~/android/kitkat$
Is the % figures normal, or should I try to sync repo again?
Click to expand...

Looks like a good sync to me ;)

Sent from my LG-VM670 using Tapatalk 2
 
Re: 4.4 KitKat?

Nope, looks good! When you're ready to build, here's the commands:
(execute in base directory)

source build/envsetup.sh # this sets up the environment variables like PATH and LIB

lunch cm_thunderc-userdebug # this sets it up to build for our device in the userdebug configuration, which has limited debugging support

make -j3 bacon # this builds everything and creates a 'flashable' zip in the out directory (our zip won't be flashable without removing a lot of stuff)
# the -j flag tells how many threads to use, use # of cores + 1 i.e. 3 threads for a dual core cpu

You're going to get a number of build errors, be patient and post your error messages and we'll get you through it. Look at this as a learning experience, start poking around the source tree, the idea is to gain a big picture understanding of the build system and all the packages that go into it. The find and grep commands are your friends. The error messages aren't that informative so you need to search for files and search inside files to pinpoint the source of the problem. It's like detective work, you're looking for clues in the output. Here's an example that uses find plus grep to search inside all files that end with the .mk extension for the string TARGET_KERNEL_CONFIGURATION:

find . -name \*.mk -exec grep -H TARGET_KERNEL_CONFIGURATION {} \; # go ahead and try this command

Also try running a web search on the error output to see if anyone has encountered similar errors and gotten answers. I'm happy to help but the more you can figure out yourself the better, also I don't really know what I'm doing either ;)
 
Re: 4.4 KitKat?

Will have to wait till tonight, and after I enlarge my swap to 6GB, to start the build process.
Will post errors after first build attempt (I think I will pull side cover off tower and have fan blowing cool air onto hard drives and processor as well).
 
Re: 4.4 KitKat?

Almost forgot.
I signed up to Github last year. Checked and I'm still good. I might need a few pointers on how to use it properly. Any links or direct help would be appreciated.
 
Re: 4.4 KitKat?

Which should I use?
Search results found for Optimus
TWRP for LG Optimus 2x P990 [P990]
TWRP for LG Optimus Black [P970]
TWRP for LG Optimus G AT&T [geebus]
TWRP for LG Optimus G Sprint [geehrc4g]
TWRP for LG Optimus G2 [g2]
TWRP for LG Optimus LTE [su640]
TWRP for LG Optimus One [thunderg]
TWRP for LG Optimus Slider [gelato]

Optimus S, I'm running COT latest version now with SlimBean latest version. Do you have to have adb or is there a recovery flashable version? I can do either, I'd just rather recovery flash it.
 
Re: 4.4 KitKat?

skinbark said:
Use the info on this page: How To Build CyanogenMod Android for LG Optimus One ("p500") - CyanogenMod
but initialize your repo to this: git://github.com/androidarmv6/android.git -b cm-11.0
In the base directory there'll be a hidden directory called .repo, make a directory in .repo called local_manifests. Any xml manifest file in this directory will be used to sync along with the main source. This is the 'new' way. The old way was to use a single file in .repo called local_manifest.xml. I made a file in this directory called thunderc.xml that tells repo where to sync the device specific folders for thunderc from. I used the cm10.2 branch from TheJBC. Then when you run "repo sync" the device specific folders will be synced along with the cm11 source code. They say you need about 35 gb of disk space to build android, I think the source is around 10 gigs and the build generates a ton of intermediate object files etc. in the BASE_DIR/out directories. The full source includes extra stuff like the android sdk, you end up building stuff that's not really necessary to make a rom, I don't know how to weed that stuff out yet. There's good instructions for porting TWRP in a thread on xda, I'm thinking about trying to port that. A couple of guys in the p500 thread that thewraith420 mentioned were able to get cm11 flashed and booted using twrp. Unfortunately I bricked my OV the other night so I'm waiting on a new (used) one from ebay right now. I was messing around inside the broken recovery and managed to trash the system partition while attempting to mount it from the recovery. Luckily I got another one for $1.50(!) + shipping so it wasn't too bad a loss. I'd say hacking recoveries is risky though. The "build TWRP" thread tells how to build for the sdk emulator so you can experiment more safely. You're probably going to want to max out your ram and have plenty of disk space. You should add extra swap space as well, maybe 6 or 8 gigs?
Click to expand...
Follow this.
For clarification go here: http://forums.androidcentral.com/lg...ms-hacks/331332-4-4-kitkat-4.html#post3296313
 
Re: 4.4 KitKat?

Downloaded it.

Moving on to the build. Didn't take long to get an error.
Code: 
andyopie150@Dell-OptiPlex-GX620DT:~/android/kitkat$ source build/envsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/goldfish/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/bash_completion/git.bash
including vendor/cm/bash_completion/repo.bash
andyopie150@Dell-OptiPlex-GX620DT:~/android/kitkat$ lunch cm_thunderc-userdebug
ls: cannot access device/*/thunderc/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_thunderc".  Stop.
Device thunderc not found. Attempting to retrieve device repository from androidarmv6 Github (http://github.com/androidarmv6).
Repository for thunderc not found in the androidarmv6 Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
ls: cannot access device/*/thunderc/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_thunderc".  Stop.

** Don't have a product spec for: 'cm_thunderc'
** Do you have the right repo manifest?
 
Re: 4.4 KitKat?

Did you add the roomservice.xml file in the local_manifests directory? If not do that and then run 'repo sync' again to download the device files. The command I gave should work.
 
Re: 4.4 KitKat?

I did, but maybe too soon. I seem to have two local_manifests directory's now (I made one, as I thought I should). Transfered roomservice.xml file to the one that was generated by?, but not by me. Then deleted the directory I created.
Will run repo sync again.

Well, one good thing. I make all the mistakes so those that come behind me don't have to. Lol. At least if they read this thread.
 
Re: 4.4 KitKat?

You know lol I've built from sources several times but never messed with the manifest I've brought everything besides the Rom source in manually or via git clone. So I'm learning something here too :D

Sent from my LG-VM670 using Tapatalk 2
 
Re: 4.4 KitKat?

Hi,
I'm using Windows XP on my netbook wich support will be ended on 8th april 2014... I think it can't run Win 7, so I want to install Android 4.4 (or newer in the future) to it, but I've got a big problem.
Now I'm using Auto Power ON&Shut Down to automaticly wake my netbook up from total standby and after a time shut it down (hibernate). I've been searching for a similar Android app for 3 months and yesterday I found that Android 4.x versions can do it as default setting (without any apps). Is it true?
Or if not, does anyone have such an app? (The netbook need to be totally turned off.)
 
Last edited:
Re: 4.4 KitKat?

hbarnabas said:
Hi,
I'm using Windows XP on my netbook wich support will be ended on 8th april 2014... I think it can't run Win 7, so I want to install Android 4.4 (or newer in the future) to it, but I've got a big problem.
Now I'm using Auto Power ON&Shut Down to automaticly wake my netbook up from total standby and after a time shut it down (hibernate). I've been searching for a similar Android app for 3 months and yesterday I found that Android 4.x versions can do it as default setting (without any apps). Is it true?
Or if not, does anyone have such an app? (The netbook need to be totally turned off.)
Click to expand...

This forum is for the Optimus S your question should really be in the general Android section

Sent from my LG-VM670 using Tapatalk 2
 
Re: 4.4 KitKat?

thewraith420 said:
You know lol I've built from sources several times but never messed with the manifest I've brought everything besides the Rom source in manually or via git clone. So I'm learning something here too :D

Sent from my LG-VM670 using Tapatalk 2
Click to expand...
Any tips on using Github? Total newb to it as well. Need to create a new repository for this KitKat project I would assume. Unless there is already one out there.

EDIt: When I go to actually start the build, what is the proper command? Is it:
Code: 
croot
brunch thunderc
??
 
Last edited:
Re: 4.4 KitKat?

Before you build, check the device folder and see if you have the lge thunderc, qcom, msm7x27, and one other I think. In the boardconfig, you might have to change the kernel defconfig back to what bssquid uses. I rename it because I like it at the top of the file list.

Brunch should work fine but is a shortcut, I still use:
lunch
#to make sure thunderc is on the menu
# Choose cm_thunderc userdebug
make -j5 bacon
 
You must log in or register to reply here.

Similar threads

K
  • Question Question
Question Used phone with 1 TB storage purely to use as music player.
Replies
1
Views
900
Ask a Question
VidJunky
VidJunky
gray2018
S23 Ultra in 2025
Replies
17
Views
9K
Samsung Galaxy S23 Series
gray2018
gray2018
gray2018
S24+ from S21 Ultra?
Replies
5
Views
4K
Samsung Galaxy S24 Series
gray2018
gray2018
Joshua Luther1
S25 Ultra radios and signal strength
Replies
1
Views
6K
Samsung Galaxy S25 Series
bearone2
bearone2
T
  • Question Question
Question Samsung Galaxy S 22 Ultra Battery dies at %5
Replies
14
Views
11K
Ask a Question
SyCoREAPER
SyCoREAPER

Latest posts

Trending Posts

Members online

Total: 4,153 (members: 8, guests: 4,145)

Forum statistics

Threads
958,880
Messages
6,977,925
Members
3,164,144
Latest member
mindsetnovice

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom