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

[QuinnSF]

Google Maps is very laggy for me, the phone runs hot a lot, and yelp doesn't work for me. Widgets seem to make the phone laggy, but I could be wrong about this. Do you guys experience any of this or did I turn on some settings I shouldn't have? Also, I loaded a different theme and then deleted it a day later, I can't access Performance and Developer Settings in the Settings now.

 

[bigsupersquid]

Google Maps is very laggy for me, the phone runs hot a lot, and yelp doesn't work for me. Widgets seem to make the phone laggy, but I could be wrong about this. Do you guys experience any of this or did I turn on some settings I shouldn't have? Also, I loaded a different theme and then deleted it a day later, I can't access Performance and Developer Settings in the Settings now.

you should be able to open the dev settings back up with about phone>tap build number until it says it's activated.

there's a 'last version' of maps that runs clean because of our gpu
it's buried in this thread somewhere.

gapps make the phone laggier, and any apps that run on boot will too.
use widgets>settings>app ops to turn off start on boot and any 'wake up' 'prevent sleep' perms for downloaded apps.

 

[Shinkenred]

Update on the ROM situation:

...nope. Tried the 10/30 os2sd by itself, NO Sprint fix, gapps, or facilitator. Bloody thing STILL installs absolutely perfectly, and yet it STILL refuses to boot. At this point, I'm about ready to give up...I dunno what to do anymore.

 

[bigsupersquid]

Update on the ROM situation:

...nope. Tried the 10/30 os2sd by itself, NO Sprint fix, gapps, or facilitator. Bloody thing STILL installs absolutely perfectly, and yet it STILL refuses to boot. At this point, I'm about ready to give up...I dunno what to do anymore.

ok, last-ditch effort to see what's going on.

in recovery, mount /system, open advanced>file manager
see if /system has a bunch of subdirectories.

if it does, that's a good start, it means something is going wrong with the boot.img

You can try to flash one in recovery with a zip. For the 10/30 only.
This uses flash_image where the recovery updater_script uses write_raw_image, and I don't know if it handles those differently or not.
A bad boot.img flash would cause the wifi and some other problems I've seen as well as some of yours.
View attachment boottest.zip

 

[Shinkenred]

ok, last-ditch effort to see what's going on.

in recovery, mount /system, open advanced>file manager
see if /system has a bunch of subdirectories.

if it does, that's a good start, it means something is going wrong with the boot.img

You can try to flash one in recovery with a zip. For the 10/30 only.
This uses flash_image where the recovery updater_script uses write_raw_image, and I don't know if it handles those differently or not.
A bad boot.img flash would cause the wifi and some other problems I've seen as well as some of yours.
View attachment 146072

Okay, so where in the order of flashing would this go? I tried it after the ROM, and it didn't work.

New odd thing: with this thing connected to the computer earlier (at library), I tried to delete one file from the Download section of my SD card...only for it to mysteriously nuke the ENTIRE FOLDER...and "cancel" COULDN'T STOP IT. All those apks downloaded (and a video and a couple songs), GONE. How that happened, I have no clue, but I am NOT a happy camper...

 

[bigsupersquid]

I meant flash ROM, check mounted /system, flash boottest, reboot.
Wonder if your card is failing? I'm waffling towards ext2 to avoid journaling since the f2fs seemed buggy.

Your phone is weird. I'd trade it to keep on hand for stress tests if I had an S laying around.

 

[nitestalkr]

I meant flash ROM, check mounted /system, flash boottest, reboot.
Wonder if your card is failing? I'm waffling towards ext2 to avoid journaling since the f2fs seemed buggy.

Your phone is weird. I'd trade it to keep on hand for stress tests if I had an S laying around.

I was about to say more or less the same thing. I was starting to think that maybe the SD card locked itself in RO mode, till I figured that wouldn't be the case, due to having the newest zips on the SD card. Possibly bad partitioning? Try repartitioning through squid's twrp recovery if you haven't that already.

Also, after extended use of the last ext4 rom update, it seems to start slowing down and locking up more than usual. Having to take some extended time to complete a few simple tasks gets a lil exhausting sometimes.

Sent from my LG-VM670 using Tapatalk 2

 

[Shinkenred]

I meant flash ROM, check mounted /system, flash boottest, reboot.
Wonder if your card is failing? I'm waffling towards ext2 to avoid journaling since the f2fs seemed buggy.

Your phone is weird. I'd trade it to keep on hand for stress tests if I had an S laying around.

Flash ROM...done.
Mount & check /system...done, subdirectories are present.
Flash boottest...done.
Reboot System...done...and...so far, it seems to be working! At the CM11 logo now...

...it worked! But after adjusting some settings and rebooting to recovery to flash the Sprint Fix & gapps...it's back to not booting at all.

Back to JUST ROM&boottest, and it works. Not sure if it's the Sprint Fix or either of the new gapps that's the problem...

 

[bigsupersquid]

...
Also, after extended use of the last ext4 rom update, it seems to start slowing down and locking up more than usual. Having to take some extended time to complete a few simple tasks gets a lil exhausting sometimes.

Sent from my LG-VM670 using Tapatalk 2

that is the same as the f2fs acted. just fine at first then the cards didn't like it anymore.
Another reason to try ext2. Plus ext2 (and vfat) can be resized in recovery rather than completely repartitioned, which would be nice.

Flash ROM...done.
Mount & check /system...done, subdirectories are present.
Flash boottest...done.
Reboot System...done...and...so far, it seems to be working! At the CM11 logo now...

...it worked! But after adjusting some settings and rebooting to recovery to flash the Sprint Fix & gapps...it's back to not booting at all.

Back to JUST ROM&boottest, and it works. Not sure if it's the Sprint Fix or either of the new gapps that's the problem...

I did test the sprint fix and gapps... neither bootlooped me. no other feedback on sprint test.
you could try 2nd newest gapps (the androidfilehost set, I'm not maintaining the google drive stuff at this time.)
I suggest first try rom, boottest, gapps, reboot. the sprint fix is most likely to bork it since perms on build.prop will bootloop if wrong.

 

[nitestalkr]

Hey Squid, could you possibly make a flashable zip to remap the button above the camera button to act as the power button? My power button isn't as reliable as it used to be, especially when it comes to bringing up the power menu.
I know some users could benefit from it as well who may be experiencing the same issue.
It'd be greatly appreciated. Thanks in advance!

Sent from my LG-VM670 using Tapatalk 2

 

[bigsupersquid]

Hey Squid, could you possibly make a flashable zip to remap the button above the camera button to act as the power button? My power button isn't as reliable as it used to be, especially when it comes to bringing up the power menu.
I know some users could benefit from it as well who may be experiencing the same issue.
It'd be greatly appreciated. Thanks in advance!

Sent from my LG-VM670 using Tapatalk 2

I can look into it, but it'd only work after the rom boots.
even if I put it in the kernel itself. The bootloader has its own kernel and keymap...

the o1 guys use a mod that substitutes a taskbar tap for power button I think.

 

[nitestalkr]

I can look into it, but it'd only work after the rom boots.
even if I put it in the kernel itself. The bootloader has its own kernel and keymap...

the o1 guys use a mod that substitutes a taskbar tap for power button I think.

I don't have an issue turning the phone on with the power button, just locking the phone and getting to the power menu. I have to press it pretty hard just right and in a certain way, making accessing the power menu pretty difficult sometimes by locking the phone instead.
I did a bit of digging into gravity box from xposed, and found that i can edit the actions of the front buttons. It has a few more options than in the ROMs system settings that are pretty helpful.
I changed the menu button long press to power menu, and double tap menu to turn off screen/lock phone.
This should work for me for now but it'd be better to have the side button to be my power button substitute.

Sent from my LG-VM670

 

[bigsupersquid]

I don't have an issue turning the phone on with the power button, just locking the phone and getting to the power menu. I have to press it pretty hard just right and in a certain way, making accessing the power menu pretty difficult sometimes by locking the phone instead.
I did a bit of digging into gravity box from xposed, and found that i can edit the actions of the front buttons. It has a few more options than in the ROMs system settings that are pretty helpful.
I changed the menu button long press to power menu, and double tap menu to turn off screen/lock phone.
This should work for me for now but it'd be better to have the side button to be my power button substitute.

Sent from my LG-VM670

Ok, I got it. it's the old voice search button. Not even in the thunder-keypad.kl
key 216.

This should add that key as a second power button.
It shouldn't interfere with the Sprint keyswap either. I still need to redo that with awk, it's cool.

here, in the new tweaks folder
adding to OPs. Y'all ask for interesting things.

 

[dradzanowski]

Hey, I'm thinking of getting a new phone for Christmas. toying with the idea.
Before I leave, I gotta know, does anyone have news on fresh install space, ease of install, reliability? Also toying with reinstalling the ROM.

 

[BradN2]

If google wants to update gapps itself and store in /data, maybe a different approach might be: What is the smallest gapps (or parts of it) that can be put in /system and still allow the update function to succeed?

 

[bigsupersquid]

If google wants to update gapps itself nmiand store in /data, maybe a different approach might be: What is the smallest gapps (or parts of it) that can be put in /system and still allow the update function to succeed?

that would be the oldest 4.4 ones.
problem is /data space also limited.
current gms and vending way over 50mB once they've synced themselves.
if gapps gonna take one third of user app storage, then there's not much room without using card storage anyway. can't even fit the /extras apps with that.
spoils the point of internal if you can only have a small handful of apps...

 

[Shinkenred]

you could try 2nd newest gapps (the androidfilehost set, I'm not maintaining the google drive stuff at this time.)
I suggest first try rom, boottest, gapps, reboot. the sprint fix is most likely to bork it since perms on build.prop will bootloop if wrong.

Second newest is the 10/28 one, right? That's the one I've had anyway - didn't even know about the 11/04 one until just now, lol. Hopefully, this works...having to rely on that JB ROM when my memory card ain't formatted specifically for it (and then again, even if it were) is getting to be a pain in the nuts. I mean it's technology acting stupid to the point that it makes me want to BREAK IT...and I mean hurl this mofo into a smurfin' wall or something equally violent.

 

[BradN2]

I made some more tests with those two optimus S's I had that wouldn't run the OS2SD.

I loaded on the internal ROM, and the one that FC'd phone still does so, and the one that FC'd acore fails to execute the updater binary near the end of installation. Didn't try booting it. Tried swapping SD cards and same behavior for that one. I also noticed a lot of soft restarting inside the recovery for that second phone.

I'm thinking these two are just bad phones, but it's strange that all the 2.2/2.3 roms I tried were happy with them.

 

[bigsupersquid]

I made some more tests with those two optimus S's I had that wouldn't run the OS2SD.

I loaded on the internal ROM, and the one that FC'd phone still does so, and the one that FC'd acore fails to execute the updater binary near the end of installation. Didn't try booting it. Tried swapping SD cards and same behavior for that one. I also noticed a lot of soft restarting inside the recovery for that second phone.

I'm thinking these two are just bad phones, but it's strange that all the 2.2/2.3 roms I tried were happy with them.

I'd suspect they'd be ok with most roms and recoveries using 2.6.32 kernel(froyo)

touchy hardware like those and shinkenred's phone may just be stuck with stock-based kernel, froyo or gingerbread.
they're pretty cheap these days... so am I though, so I understand not buying a replacement just to run newer software.

 

[Shinkenred]

Okay, so I tried ROM>boottest>11/04 gapps. It works, but not without a bit of oddity: I used TB to get rid of certain safe-to-ditch system apps...only for them to mysteriously come right back upon reboot.

Also had to bump it down from my now-usual 480/729 to 480/600 because it would randomly reboot itself for no reason. A lot. (Never seen that happen with the CPU Max set to 729, this was usually 787 and up!)

Otherwise, it seems to work fine. I'll be more comfortable when a Sprint fix that's nice with the ROM>boottest>gapps combo comes along...still haven't got accustomed to the reversed buttons.

And my Optimus S hardly ever had problems with ICS ROMs...it's JB and up where she doesn't seem to play nice. (Example: BobZhome CM10 seemed fine, but would have wakelock when I listened to music. I thought all that came from the Rocket Player music player app...nope, that happens with the stock music player, too.)