[ROM][WIP][4.4.2] CyanogenMod 11 KitKat for Optimus S/V

[skinbark]

root@thunderc:/ # busybox ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1312 (1.2 KiB) TX bytes:1312 (1.2 KiB)

rmnet0 Link encap:Ethernet HWaddr CA:19:91:FC:8D: D5
inet6 addr: fe80::c819:91ff:fefc:8dd5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:2000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1636 (1.5 KiB)

wlan0 Link encap:Ethernet HWaddr 14:7D:C5:A1:3E:F3
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:98 errors:0 dropped:19 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7950 (7.7 KiB) TX bytes:4063 (3.9 KiB)

This command shows that the data interface (rmnet0) is active, so I think it's okay at the kernel level.
"Ifconfig is used to configure the kernel-resident network interfaces. It is used at boot time to set up interfaces as necessary. After that, it is usually only needed when debugging or when system tuning is needed."

 

[skinbark]

Here's part of a startup logcat for kitkat:

I/SystemServer( 487): NetworkStats Service
I/SystemServer( 487): NetworkPolicy Service
I/SystemServer( 487): Wi-Fi P2pService
I/SystemServer( 487): Wi-Fi Service
I/SystemServer( 487): Connectivity Service
D/ConnectivityService( 487): ConnectivityService starting up
D/ConnectivityService( 487): wifiOnly=false
E/ConnectivityService( 487): Ignoring protectedNetwork 10
E/ConnectivityService( 487): Ignoring protectedNetwork 11
E/ConnectivityService( 487): Ignoring protectedNetwork 12
E/ConnectivityService( 487): Ignoring protectedNetwork 14
E/MobileDataStateTracker( 487): default: Ignoring feature request because could not acquire PhoneService
E/MobileDataStateTracker( 487): default: Could not enable APN type "default"
D/WifiHW ( 487): Unable to unload driver module "wireless": No such file or directory
D/Tethering( 487): Exception adding default nw to upstreamIfaceTypes: java.lang.NullPointerException
I/WifiService( 487): WifiService starting up with Wi-Fi enabled
D/WifiService( 487): setWifiEnabled: true pid=487, uid=1000
D/WifiController( 487): WifiController msg { when=-3ms what=155656 target=com.android.internal.util.StateMachine$SmHandler } deferred for 272ms
I/SystemServer( 487): Network Service Discovery Service
D/NsdService( 487): Network service discovery enabled true
I/SystemServer( 487): UpdateLock Service
I/SystemServer( 487): Profile Manager
V/ProfileTriggerHelper( 487): Enabling
D/ProfileService( 487): Found active: 2f1d374b-a126-4063-868f-3de0fffa4df4
D/WifiController( 487): DEFERRED_TOGGLE handled
D/ProfileService( 487): Set active profile to: 2f1d374b-a126-4063-868f-3de0fffa4df4 - Default
D/ProfileService( 487): Saving profile data...
D/ProfileService( 487): Save completed.

 

[Shinkenred]

Never mind, I must have already deleted them from that rom.

Okay...here's what happened after following those instructions:
Back button works, got keyboard up and running to log into Google; Home & Menu are still switched, though.

Gapps STILL don't seem to work; this is after having tried both the version that came with the 12/25 rom and the new Skinny version. I have no idea why this isn't working. I don't normally use the stock browser anymore, but perhaps I'll try to go into Google that way.

This is probably because it's time for a new battery, nevertheless I'll make it known: it seems with JB roms and now this, reboots can be sheer hell on the battery. Sometimes it won't affect it much, other times it eats away a HUGE chunk of power. Just now, it dropped from 35% to a mere 4% after rebooting.

Also, if it's plugged in, it will NOT reboot to recovery; for some reason, it only reboots normally.

UPDATED (because I totally forgot to mention this): Themes STILL crashes. Trying to sideload the ThemesProvider.apk won't work, either...it doesn't install at all.

Can't get any more than the ONE page for apps on the home screen.

Posted via Android Central App

 

[bigsupersquid]

... I may upload a larger rom at some point for whoever wants to try this. ...

gimme.
I want everything, including the kitchen sink, that will run on our hardware (or might,) all in one zip file.
Just leave out stuff like NFC and Torch that don't work.
//edit
hm, I see someone's github was very recently updated.
maybe I can actually build something functional now which hasn't happened in a bit. then I won't need an upload.
you find those lines in board-thunderc-input.c for your keys? just do a 'find' for 'ls670' in the editor. or grep it case insensitive.

and, no real surprise,

lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
dummy0 DOWN 0.0.0.0/0 0x00000082 d6:c3:29:c9:e4:70
rmnet0 DOWN 0.0.0.0/0 0x00001002 b6:70:12:11:c3:65
rmnet1 DOWN 0.0.0.0/0 0x00001002 7a:82:53:26:81:1a
rmnet2 DOWN 0.0.0.0/0 0x00001002 c6:f1:b5:5c:28:89
rmnet3 DOWN 0.0.0.0/0 0x00001002 3a:30:33:83:43:f9
rmnet4 DOWN 0.0.0.0/0 0x00001002 b6:64:d9:ea:b0:dd
rmnet5 DOWN 0.0.0.0/0 0x00001002 2e:6b:e3:6b:28:68
rmnet6 DOWN 0.0.0.0/0 0x00001002 1e:a0:83:4a:21:17
rmnet7 DOWN 0.0.0.0/0 0x00001002 0a:ed:a9:0c:4b:6d
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00

 

[skinbark]

I'm just about to start a new 'full' build. Should take an hour or two.

 

[bigsupersquid]

I'm just about to start a new 'full' build. Should take an hour or two.

I synced from your manifest and got a 134mb zip to play with. thanks.
//edit: duh, forgot make clean. be longer...

 

[skinbark]

Okay...here's what happened after following those instructions:
Back button works, got keyboard up and running to log into Google; Home & Menu are still switched, though.

Gapps STILL don't seem to work; this is after having tried both the version that came with the 12/25 rom and the new Skinny version. I have no idea why this isn't working. I don't normally use the stock browser anymore, but perhaps I'll try to go into Google that way.

This is probably because it's time for a new battery, nevertheless I'll make it known: it seems with JB roms and now this, reboots can be sheer hell on the battery. Sometimes it won't affect it much, other times it eats away a HUGE chunk of power. Just now, it dropped from 35% to a mere 4% after rebooting.

Also, if it's plugged in, it will NOT reboot to recovery; for some reason, it only reboots normally.

UPDATED (because I totally forgot to mention this): Themes STILL crashes. Trying to sideload the ThemesProvider.apk won't work, either...it doesn't install at all.

Can't get any more than the ONE page for apps on the home screen.

Posted via Android Central App

I took out Themes to save space and because I read that it was a battery drain. I'm using Nova Launcher now but I think if you drag an app icon from the app drawer off to the side of the screen it'll create a new page and place the icon there. I know I was able to get multiple screens. If it doesn't work check in Settings for an option to enable multiple pages.

 

[skinbark]

I synced from your manifest and got a 134mb zip to play with. thanks.
//edit: duh, forgot make clean. be longer...

I put a new eri.xml in device/lge/thunderc so check if it makes any difference with data.
My build ended up being ~128 megs. /system is about 189 megs, small enough for the p500. I think you can make a bigger one by using a different make file in cm.mk instead of mini.mk but I haven't tried it yet.
I found the lines in the kernel file, thanks!

 

[yaconsult]

Yeah, that's how the screens work in kitkat default launcher - it's not exactly obvious. Dragging an icon off the right edge of a page will create a new page after it and put the icon on it. How do you delete these extra pages? When you move the last icon off a page, it gets deleted.

 

[bigsupersquid]

here's a fun tidbit.
updated http://forums.androidcentral.com/lg...nmod-11-kitkat-optimus-s-v-5.html#post3357615
these two files, init.qcom.rc and fstab.thunderc, in the device folders, make a recovery and zip which work out of the box to install to the 3 ext partitions mmcblk0p2, p3, and p4. and it appears the zip installs on the regular skinbark recovery, too.
View attachment 98947
however, something's still borked in my build and I get everything FC'ing like crazy on startup.

 

[skinbark]

here's a fun tidbit.
updated http://forums.androidcentral.com/lg...nmod-11-kitkat-optimus-s-v-5.html#post3357615
these two files, init.qcom.rc and fstab.thunderc, in the device folders, make a recovery and zip which work out of the box to install to the 3 ext partitions mmcblk0p2, p3, and p4. and it appears the zip installs on the regular skinbark recovery, too.
View attachment 98947
however, something's still borked in my build and I get everything FC'ing like crazy on startup.

Hmm, that does sound like fun. I think I'll try it!

 

[bigsupersquid]

Hmm, that does sound like fun. I think I'll try it!

I was hoping you'd get in on it. make it easier to squash bugs and evaluate issues.

 

[skinbark]

I got a Status 7 error when I tried to flash the zip. The recovery was mounting and unmounting sd-ext partitions properly. Here's the updater script if it helps any:

 

[bigsupersquid]

I forgot, the 'format' line in there messes it up. Sets the size to 0.
remove or comment it out. It doesn't seem to help to get the partition size right.
your current recovery is working fine, by the way.
and it seems to install to the ext4 several times faster than to yaffs.
this may help too, it's a zip to wipe all files off of mmcblkp2-p4.
View attachment cm-11-wipe_mmcp2-p4.zip
testing fstab mods from hammerhead now.

 

[skinbark]

I was hoping you'd get in on it. make it easier to squash bugs and evaluate issues.

Oh for sure, especially when you make it so easy!
I'm sure I'm not the only one who's interested.

 

[brotherswing]

I will be following the progress of this project intently! I'm constantly amazed at how far the OS/OV can be pushed!

Explore! Rescue! Protect!

 

[skinbark]

I got it installed and it's working No fcs. I flashed the modified gapps and got the play store going. Only problems are 1) I have a 512mb /data and android thinks I have an 128mb /data 2) I don't think /cache is working because when I reboot it 'forgets' my settings for developer options etc. Also it's pretty laggy off of my class 4 sd card but I expected that.
Edit: every reboot takes a long time like it's the first startup, and I get the setup wizard. No settings are being remembered.
Edit: I don't see any need to mount /cache on sd-ext. I'm going to try it with /cache mounted normally.

 

[bigsupersquid]

I got it installed and it's working No fcs. I flashed the modified gapps and got the play store going. Only problems are 1) I have a 512mb /data and android thinks I have an 128mb /data 2) I don't think /cache is working because when I reboot it 'forgets' my settings for developer options etc. Also it's pretty laggy off of my class 4 sd card but I expected that.

the fc's are because I haven't gotten a complete sync in days and days without missing bits here and there, trying to patch things together and failing.
as far as data and cache, there's issues in the fstab.thunderc.

try this one, I messed around a while and took some stuff from the hammerhead fstab.
the one I put up had some issues. was just guessing how to syntax it.
there may need to be differences in the init.qcom.rc as well. the hammerhead uses a neat line instead of individually mounting system, data, cache, etc...

on fs
    mount_all ./fstab.hammerhead

 

[skinbark]

the fc's are because I haven't gotten a complete sync in days and days without missing bits here and there, trying to patch things together and failing.
as far as data and cache, there's issues in the fstab.thunderc.

try this one, I messed around a while and took some stuff from the hammerhead fstab.
the one I put up had some issues. was just guessing how to syntax it.
there may need to be differences in the init.qcom.rc as well. the hammerhead uses a neat line instead of individually mounting system, data, cache, etc...

on fs
    mount_all ./fstab.hammerhead

Can you see any reason not to just mount /cache on mtd?
It's less of a bottleneck reading and writing from 2 physical devices.

 

[bigsupersquid]

Can you see any reason not to just mount /cache on mtd?

only that I've filled it up before, while installing from market on other roms.
and I just reflash my boot.img and reboot my use phone into the internal rom; can do that from terminal, and don't want to format and rebuild cache each time.
try whatever variations you like, it's easy to change... just change the appropriate matching lines in init.qcom.rc and fstab.thunderc
//edit: well, if that init.hammerhead.rc mount_all line works, you'll only need to change the fstab.thunderc file. aosp is really working more like linux these days, and I for one certainly do appreciate that.