[ROM+Kernel][CM-11.0][4.4.4][OS2SD/internal][f2fs]bigsuperROM-thunderc-4.4.4

[bigsupersquid]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

...
bigsupersquid: I really think all your efforts should be concentrated on the OS2SD version. I'll try to help where possible.
Posted via Android Central App

ah, yes. I am looking at firerat's custom mtd partition mod for a speedup like skinbark was talking about early on with the OS2SD.
Trying to use the kernel mtd swap functions fail with errors both with mkswap and swapon. And I don't imagine that /cache speed has a lot of effect on run speeds.
So, I was thinking to combine the /system and /data partition space for just /system on mtd. Then card p2 becomes sd-ext, p3 data, and p4 still cache. CM wants sd-ext. Recovery and other things bork up p2 if not expecting it like the new twrp.
With /system apps on one media and /data apps on another run times may improve like skinbark was thinking.
I need someone with this running to post the dmesg from just after booting an optimus S... or optimus V with S firmware.
Actually I only need these two bits:

<6>[ 0.000000] Partition (from atag) boot -- Offset:141 Size:38
<6>[ 0.000000] Partition (from atag) cache -- Offset:179 Size:371
<6>[ 0.000000] Partition (from atag) recovery -- Offset:4ea Size:38
<6>[ 0.000000] Partition (from atag) splash -- Offset:522 Size:a
<6>[ 0.000000] Partition (from atag) FOTA_STO -- Offset:52c Size:8
<6>[ 0.000000] Partition (from atag) system -- Offset:534 Size:524
<6>[ 0.000000] Partition (from atag) userdata -- Offset:a58 Size:597
<6>[ 0.000000] Partition (from atag) misc -- Offset:fef Size:4
<6>[ 0.000000] Partition (from atag) persist -- Offset:ff3 Size:c

<6>[ 1.402146] msm_nand_probe: phys addr 0xa0a00000
<6>[ 1.402169] msm_nand_probe: dmac 0x7
<6>[ 1.402228] msm_nand_probe: allocated dma buffer at ffde4000, dma_addr 2c432000
<6>[ 1.402761] status: c00020
<6>[ 1.402778] nandid: 5590bc2c maker 2c device bc
<6>[ 1.402804] ONFI probe : Found an ONFI compliant device MT29F4G16ABBDA3W ,
<6>[ 1.402844] Found a supported NAND device
<6>[ 1.402859] NAND Id : 0x5590bc2c
<6>[ 1.402873] Buswidth : 16 Bits
<6>[ 1.402884] Density : 512 MByte
<6>[ 1.402896] Pagesize : 2048 Bytes
<6>[ 1.402909] Erasesize: 131072 Bytes
<6>[ 1.402921] Oobsize : 64 Bytes
<6>[ 1.402934] CFG0 Init : 0xa85408c0
<6>[ 1.402948] CFG1 Init : 0x0004745e
<6>[ 1.402961] ECCBUFCFG : 0x00000203
<5>[ 1.402979] Creating 9 MTD partitions on "msm_nand":
<5>[ 1.403008] 0x000002820000-0x000002f20000 : "boot"
<5>[ 1.407849] 0x000002f20000-0x000009d40000 : "cache"
<5>[ 1.464499] 0x000009d40000-0x00000a440000 : "recovery"
<5>[ 1.469191] 0x00000a440000-0x00000a580000 : "splash"
<5>[ 1.470971] 0x00000a580000-0x00000a680000 : "FOTA_STO"
<5>[ 1.472586] 0x00000a680000-0x000014b00000 : "system"
<5>[ 1.556716] 0x000014b00000-0x00001fde0000 : "userdata"
<5>[ 1.648236] 0x00001fde0000-0x00001fe60000 : "misc"
<5>[ 1.649569] 0x00001fe60000-0x00001ffe0000 : "persist"

just to make sure that nobody with S firmware bootloops if they try it after the mod is in place.

 

[TrikkJames]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

No dice, does not install for me.

Dang. I was afraid of that. Well I tried.

 

[AndyOpie150]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Yea, pretty much. Although when it dies, i usually let it be dead for a few hours throughout the day.

Sent from my LG-VM670 using Xparent Red Tapatalk 2

Try not to let it die. Charge it up when it gets below 20%.

Posted via Android Central App

 

[AndyOpie150]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Hey Andy, did the GB Google+ work on KK? Thought maybe since you thanked my post that you tried it.

Haven't had chance till now, but looks like it won't work. Will try some other ideas though.

Posted via Android Central App

 

[AndyOpie150]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

ah, yes. I am looking at firerat's custom mtd partition mod for a speedup like skinbark was talking about early on with the OS2SD.
Trying to use the kernel mtd swap functions fail with errors both with mkswap and swapon. And I don't imagine that /cache speed has a lot of effect on run speeds.
So, I was thinking to combine the /system and /data partition space for just /system on mtd. Then card p2 becomes sd-ext, p3 data, and p4 still cache. CM wants sd-ext. Recovery and other things bork up p2 if not expecting it like the new twrp.
With /system apps on one media and /data apps on another run times may improve like skinbark was thinking.
I need someone with this running to post the dmesg from just after booting an optimus S... or optimus V.

Are you saying you need a dmesg of OS2SD ROM right after bootup or OS2SD with the mod you mentioned?

Posted via Android Central App

 

[bigsupersquid]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Are you saying you need a dmesg of OS2SD ROM right after bootup or OS2SD with the mod you mentioned?

Posted via Android Central App

The first. Actually from any 3.08 kernel install on s firmware.

 

[Lpen21]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Currently using an app called lag free by Grilled Monkey. Seems to,really work to reduce clock lag but the free version does not have a scheduler so you have to reapply it from time to time. Wondering if anyone else has tried, specially the paid version with built in scheduler.

 

[bigsupersquid]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Currently using an app called lag free by Grilled Monkey. Seems to,really work to reduce clock lag but the free version does not have a scheduler so you have to reapply it from time to time. Wondering if anyone else has tried, specially the paid version with built in scheduler.

the clock lag bugs me.
I have seen lockscreen clock one wrong time, cLock widget on home screen another wrong time, statusbar clock yet another incorrect time, all while device info live wallpaper shows the correct time. it reads the time from the kernel rather than the android system, I think.

 

[Lpen21]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

the clock lag bugs me.
I have seen lockscreen clock one wrong time, cLock widget on home screen another wrong time, statusbar clock yet another incorrect time, all while device info live wallpaper shows the correct time. it reads the time from the kernel rather than the android system, I think.

Yeah it doesn't eliminate but Thought it helped some, maybe more placebo effect.

 

[Lpen21]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Yeah it doesn't eliminate but Thought it helped some, maybe more placebo effect.

Ok I think there may be something to this app. I have noticed that clocks do not always match but they seem to refresh within 5-10 seconds. Have had this app x 4 hours now and it seems to be off by no more than one minute when it's not synced. Just for giggles I also turned the cpu to 748/245 and installed a different theme( this combination really exacerbated lag before) and still running like a champ. So far I have not had the clock freeze to the point of needing to click screen off. I have the os2sd build with reg Gapps. I have the paid version .99 that adds daily scheduler. Can anyone else reproduce these findings?

 

[TrikkJames]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Haven't had chance till now, but looks like it won't work. Will try some other ideas though.

Posted via Android Central App

Mk cool.

 

[bigsupersquid]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

yay, upstream fixed 3g data again.
and mms works now out of the box without any nasty hackery like I had in DcTracker to initialize the apn. as a plus for me, Team-Hydra pulled my Virgin Mobile MMS patch upstream so now I don't have to add anything funny to the build for working mms.
Still things all wanky from cm, and I am trying to settle it all down.

 

[bigsupersquid]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

For grins and your elucidation, (based on ibcoder's partition layouts referred to by firerat's mtd partition mod)
here is the default optimus v mtd layout in kernel command line form.

BOARD_KERNEL_CMDLINE := mem=471M console=ttyMSM2,115200n8 androidboot.hardware=thunderc lge.rev=10 mtdparts=msm_nand:112k@2f20000(boot),1762k@2f20000(cache),112k@9d40000(recovery),20k@a440000(splash),16k@a580000(FOTA_STO),2632k@a680000(system),2862k@14b0000(userdata),8k@1fde0000(misc),24k@1fe60000(persist)

boo. the kernel has to get the command line internally for the whole length to stick and then it just ignores the mtdparts. even using firerat's optimus s mtd partition values.
notice the partition sizes are in decimal but the addresses are in hex.
I plan to tweak this if it works by removing /data and adding it to /system. /cache and /system will reside on mtd and /data will operate from the card ext partition 3. but it's not looking good. the mtdparts is enabled in kernel config, has been the whole time.

 

[TrikkJames]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Haven't had chance till now, but looks like it won't work. Will try some other ideas though.

Posted via Android Central App

Got another idea. Might be the VM heap size forcing the newer Google+ to FC. I downloaded a couple apps, one called Simple Root Swap that allowed me to create a swap file on SD. The other is VM Heap Tool and it allowed me to bump up the heap to 64m.

Do that and see if it works. I'm on GB right now, can't test myself. Oh yeah, test the 33.50mb version of Google+ not the GB version of course.

 

[badblue1__]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Got another idea. Might be the VM heap size forcing the newer Google+ to FC. I downloaded a couple apps, one called Simple Root Swap that allowed me to create a swap file on SD. The other is VM Heap Tool and it allowed me to bump up the heap to 64m.

Do that and see if it works. I'm on GB right now, can't test myself. Oh yeah, test the 33.50mb version of Google+ not the GB version of course.

Just F.Y.I. you can change the vmheap size in the build.prop.

 

[TrikkJames]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Just F.Y.I. you can change the vmheap size in the build.prop.

I know but I'm always weary of changing things directly on Android. In this case, I have no idea what the good values of VM Heap are but the app does so I don't mess anything up. I'm paranoid lol.

Probably why I've never built a ROM yet. If I just wasn't paranoid, I'd probably obsess over development and create amazing things.

 

[mjs2011]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Holy crap. I can't believe you guys have KitKat working on this phone! I haven't had the Optimus in almost 2 years and I'm amazed that this little guy is still kicking.

I remember three days if Jerry Script pumping out IHO updates!

Sent from my SM-N900P using Tapatalk

 

[thewraith420]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Holy crap. I can't believe you guys have KitKat working on this phone! I haven't had the Optimus in almost 2 years and I'm amazed that this little guy is still kicking.

I remember three days if Jerry Script pumping out IHO updates!

Sent from my SM-N900P using Tapatalk

I too remember those days. This place has slowed down quite a lot but the development continues. I still keep my ov as my backup phone and have it active on page plus. Been having some fun playing with the os2sd build lately. It's funny though because my newer phone is still waiting on an official update before I can have kitkat with my locked bootloader. It's amazing how far the Optimus can be pushed

Sent from my XT907 using Tapatalk

 

[AndyOpie150]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

Andy, I also installed crossbreeder and have no noticeable lag even at cpu settings below 729/480. I cranked it back up there per everyone's advice to do so , so maybe crossbreeder really helps. Also also I find that the skinny gaps zip seems a bit more stable to me the the other gaps package.

Thanks. CrossBreeder does seem to help with the lag in opening apps. Apps are still a little laggy opening, but once opened, they seem to work fine.
Page scrolling is much better.
Entropy level is maxed out at 4096.

Still not able to multitask. If I try to do more than one thing at a time I get freezes and reboots.
WiFi sometimes doesn't want to turn on till a reboot.

bigsupersquid: Great work so far. I don't seem to have any clock lag. I've had this ROM on the spare V for a few days and it's keeping time just fine.

Posted via Android Central App

 

[daffy_duck_nj]

Re: [ROM+Kernel][CM-11.0][4.4.2][OS2SD/internal]OV-KitKat (JBC based)

I must be one of the few that still prefers the internal version! Anyway, I haven't encountered too many things out of the ordinary. Works well as is, including the accelerometer. I link all apps with link2sd; link2sd and superuser are the only apps in internal memory. Have about 40 apps installed. Took out a few preinstalled apps like file manager and replaced them with their user equivalents. Time lag disappears a few hours after installing ROM.