[ROM][4.4.4] LineageOS 11.0 for LG Optimus One [OS2SD][19.03.13]

[bigsupersquid]

sometimes that lag is so bad it won't screen on and just falls back asleep. it is definitely a problem.
started trying this: (in system.prop, thunderc since my o1 broke)

# sleep modes
pm.sleep_mode=3
#usage:
#pm.sleep_mode=0 -> collapse suspend
#pm.sleep_mode=1 -> collapse (will totally power off the cpu)
#pm.sleep_mode=2 -> sleep (cpu is still on, but put into low power mode (registers are still saved)
#pm.sleep_mode=3 -> slow Clock and Wait for Interrupt (lowered frequency and voltage)
#pm.sleep_mode=4 -> wait for interrupt (no change in cpu clock or voltage)

in the system props seems to help with the slow wake.
mode 0,1,2 all lag badly on wakeup. need to test 4 and see it it's better, but it'll probably remove any deep sleep benefits.
and apparently 3 is the default. My experimental builds are all that's using 0,1,2.

 

[aaopt]

After using OS2SD for over a month I've decided to try mount /data on sdcard and leave /system on internal.
This is how DATA2SD born.
The main reason of this change is to fix phone slow downs which occurred while I was using OS2SD. Sometimes it appeared as phone just won't wake up from sleep for a minute after key was pressed. So until cause of I/O performance drop will be found I'll be experimenting with this project.
I'm testing this for a day, but overall performance seems to be much better.

I tested a couple CM11 internal ROMs before trying OS2SD. Nothing worked well for me, at least not after I installed GApps. Seems the space on the system partition was just too tight. What I really wanted to try was something like DATA2SD but reusing space from the internal /data partition for /system/app and/or /system/priv-app. But I decided to just go with your OS2SD setup because standards are good... and that way I wouldn't have to make my own TWRP.

So I bought a few SanDisk Ultra 16GB cards, very reasonable at Amazon. Actually they were on sale for even less yesterday but I had already bought three last week. I was impressed by how much faster TWRP was to install ROMs to the new SD card vs installing to internal. I do still definitely see lag on wake though.

So, I have to ask... considering OS2SD vs DATA2SD, is DATA2SD really better for overall performance? Or, aside from lag on wake, maybe OS2SD is faster?

To flash Rom and Gapps use twrp-2.7.1.0-20140831-MULTI-F2FS-p500.zip with Internal mode on

DATA2SD is definitely more important than OS2SD. And it seems some people may want to choose. Using current TWRP with DATA2SD (but OS internal) ROMs is not ideal though. If you want to back up both data and system, you have to do them separately and switch modes in between. Am I right?

The idea that TWRP can support both internal and external data, and both internal and external system, is wonderful. But to make it really seamless, it needs work. One approach:

• Remove the mode switch button.
• ROM install zips should go back to explicit mounting rather than relying on TWRP fstab.
• Update zips and GApps zips should continue to use your busybox trick.
• After every zip install-- including between zips when stacking multiple zips-- and during TWRP boot, TWRP should rewrite its own fstab. All the /data and /system related mounts from its own fstab should be removed, and replaced by the /data and /system related mounts from the boot.img partition's fstab. (Removing "ro" but keeping other boot options.)

I'm not saying it's easy, but if you can pull it off, TWRP would be much more seamless. No need to worry about mode switch, no need to remember to switch to "internal" mode before you do anything if the currently installed ROM is "internal", and all the TWRP mount and backup buttons should "do the right thing" regardless of whether the currently installed ROM is internal, DATA2SD, or OS2SD.

 

[xdema]

sometimes that lag is so bad it won't screen on and just falls back asleep. it is definitely a problem.
started trying this: (in system.prop, thunderc since my o1 broke)

# sleep modes
pm.sleep_mode=3
#usage:
#pm.sleep_mode=0 -> collapse suspend
#pm.sleep_mode=1 -> collapse (will totally power off the cpu)
#pm.sleep_mode=2 -> sleep (cpu is still on, but put into low power mode (registers are still saved)
#pm.sleep_mode=3 -> slow Clock and Wait for Interrupt (lowered frequency and voltage)
#pm.sleep_mode=4 -> wait for interrupt (no change in cpu clock or voltage)

in the system props seems to help with the slow wake.
mode 0,1,2 all lag badly on wakeup. need to test 4 and see it it's better, but it'll probably remove any deep sleep benefits.
and apparently 3 is the default. My experimental builds are all that's using 0,1,2.

so, if i've understand your list, with this pm.sleep we can save max battery with the mode 1 (cpu power off->so we have to restore registers etc.), mode 2 make apps sleep.
I've few problem of phone wake up, with old os2sd, sometimes happens when i lock&unlock one after one. (sandisk ultra class 10 SDHC I )
on 2nd p500 has a lot of wake up issue, and generic lag with os2sd f2fs & gapps (transcend class 10 SDHC) maybe it's a problem related to the sd

 

[bigsupersquid]

so, if i've understand your list, with this pm.sleep we can save max battery with the mode 1 (cpu power off->so we have to restore registers etc.), mode 2 make apps sleep.
I've few problem of phone wake up, with old os2sd, sometimes happens when i lock&unlock one after one. (sandisk ultra class 10 SDHC I )
on 2nd p500 has a lot of wake up issue, and generic lag with os2sd f2fs & gapps (transcend class 10 SDHC) maybe it's a problem related to the sd

I've had very little luck playing with the pm sleep settings.
better to watch your ram usage and kill unnecessary things running if it gets too high.

 

[xdema]

So, I have to ask... considering OS2SD vs DATA2SD, is DATA2SD really better for overall performance? Or, aside from lag on wake, maybe OS2SD is faster?

DATA2SD is definitely more important than OS2SD. And it seems some people may want to choose. Using current TWRP with DATA2SD (but OS internal) ROMs is not ideal though. If you want to back up both data and system, you have to do them separately and switch modes in between. Am I right?

about the installation method, automatic recognize the type of rom by twrp & backup etc. i agree with you but i think these changes could be done when the project will be more stable/tested

about performance comparatives between data2sd & os2sd, aren't we here to do that?

Thanks to @HardLight i'll have something to do this rainy week end

I've had very little luck playing with the pm sleep settings.
better to watch your ram usage and kill unnecessary things running if it gets too high.

no the ram was "empty", no apps installed except gapps, i have took a 2nd sd from sandisk to test the problem, but now i'll test the data2sd

the "strange" is with daily phone i've 99 apps on the phone, RAM: usually 300mb used & 120 free (whatsapp, message, swiftkey, copilot and settings, take >20mb each one) the others are not enabled to automatically start up (amazon, appfree,titanium), so i've ram when needed.

some apps lags on start (i.e. settings), but it's ok, and few seconds (1-3 max) of wake up problem sometimes (as i said when i try to fast lock&unlock ) on 18/08 os2sd rom.

 

[bigsupersquid]

...
no the ram was empty, no apps installed except gapps, i have took a 2nd sd from sandisk to test the problem

card may shut down during sleep and be unreadable until it remounts. gotta check into that more.

 

[angelgzg]

That I can do to make wifi work?

Edit: Work

 

[bigsupersquid]

I kept seeing this repeat in logcat on thunderc, checked, and it happens on thunderg too.
over and over again.
W/SchedPolicy( 597): add_tid_to_cgroup failed to write '1192' (Permission denied); policy=0
W/System.err( 597): java.lang.SecurityException: No permission to set to given group

this commit fixes it.
But, I put it in init.qcom.rc, rather than digging into the stock init.rc.

I actually think it should go upstream to androidarmv6 (since it affects more than one msm7x27 device, and it's a simple fix) but I don't have any gerrit set up yet.

It goes after "on boot", like so:

on boot

    ##fix "add_tid_to_cgroup failed to write" errors
    chmod 0660 /dev/cpuctl

    # allow reading kernel command line
    chmod 0644 /proc/cmdline

I got this accepted upstream so it should be fixed in jenkins builds from here on out.
turns out I did have my gerrit account set up but hadn't done anything with it.

 

[patil.ketan]

Edit: I installed DATA2SD version ROM and GAPPS. But I am not able to add google account, everytime I try it says, "Unable to contact google servers Please try later"
Is there a workaround to this?

 

[aaopt]

I installed OS2SD version ROM and GAPPS. But I am not able to add google account, everytime I try it says, "Unable to contact google servers Please try later"
Is there a workaround to this?

How big did you make your system partition? I had this error when installing an internal ROM and it seemed to be because the internal system partition wasn't quite big enough.

 

[patil.ketan]

Ohh sorry I had typo there...
I actually installed data2sd f2fs versions of ROM and gapps
I think the SD card partition should not matter for that.

Is there any other gapps version i can try?

Sent from my Nexus 4 using XDA Free mobile app

 

[haoss07]

card may shut down during sleep and be unreadable until it remounts. gotta check into that more.

i think this also happen to me this morning. usually i have problems waking up the device. but this morning i had the symptoms of a removed card with the rom on it (os2sd ). screen black with backlight on it. adb could not connect to get a log

 

[HardLight]

New OS2SD

Hi all,
After investigation why phone was slowing down after a while of usage even on DATA2SD, I found that the real cause of that was huge apps (fb, google play and etc) staying in background services and using to many phone recourses. After configuring greenify to put those and some system apps to sleep, now phone runs smoothly. I always have about 130 MB free RAM and it indicates that there are very few background apps running, try to keep this on your phones too.

Because I see no difference of performance between OS2SD and DATA2SD, I'll probably cancel DATA2SD branch from now.

Also new OS2SD f2fs build is uploaded.
Download

 

[haoss07]

can u provide a list of system apps that you tested and are safe to greenify ?
what they should help also

P.S. any changelog for last version ?

 

[HardLight]

can u provide a list of system apps that you tested and are safe to greenify ?
what they should help also

P.S. any changelog for last version ?

There is no sorting in greenify by app type so can't say nothing specific, but probably all apps is safe to hibernate. Just look apps under settings>apps>running and try hibernate them. If some functions won't work degreenify app.
Changelog is same as cm, no additional tweaks are needed for now.

 

[xdema]

can u provide a list of system apps that you tested and are safe to greenify ?
what they should help also

P.S. any changelog for last version ?

here there is a usefull thread

If you freeze then this will happen:

Dialer - can't make calls or answer incoming calls

Google Services Framework - Can't authenticate your device for Google services. No Cloud services will recognize you including the play store, cloud storage, streaming media, gmail, etc.
Google Play Services and Google Play Store - No play store or updates. With this and the services framework, taking them offline and/or clearing the data will confuse Google's servers and if you enable them they will either make you re-download some apps or won't let you update at all forcing a reset to fix.

Wallpaper - I recall there being some system functionality with the wallpaper, but I don't recall what it is. Sorry.
Contact - These are your contacts. You won't have any.
Google Account Manager - This is how Android differentiates the different types of accounts like POP email or Facebook, Yahoo, MSN etc.
Calendar - No appointments or reminders
Network Location - assists GPS with finding your location. If you have location services enabled, this will slow down locating you.

 

[HardLight]

GApps 20140920 OS2SD

Updated gapps uploaded: Download

here there is a usefull thread

If you freeze then this will happen:

Dialer - can't make calls or answer incoming calls

Google Services Framework - Can't authenticate your device for Google services. No Cloud services will recognize you including the play store, cloud storage, streaming media, gmail, etc.
Google Play Services and Google Play Store - No play store or updates. With this and the services framework, taking them offline and/or clearing the data will confuse Google's servers and if you enable them they will either make you re-download some apps or won't let you update at all forcing a reset to fix.

Wallpaper - I recall there being some system functionality with the wallpaper, but I don't recall what it is. Sorry.
Contact - These are your contacts. You won't have any.
Google Account Manager - This is how Android differentiates the different types of accounts like POP email or Facebook, Yahoo, MSN etc.
Calendar - No appointments or reminders
Network Location - assists GPS with finding your location. If you have location services enabled, this will slow down locating you.

Greenify does not freeze apps it just hibernates it so if system needs specific app it can be waken up.

 

[xdema]

Updated gapps uploaded: Download

Greenify does not freeze apps it just hibernates it so if system needs specific app it can be waken up.

thank's for the gapps

maybe i've misunderstood, but the user asked also for the system apps, not only user apps.
as the greenify dev wrote:

Beware, most system apps are critical to the basic functionality of your device, once greenified, you may lose some part of usability

 

[Syd_M]

I can't seem to install the GAPPS for the F2FS version (is it the same as the EXT4 version? because the link is the same). It appears to install, but when booting into the system, the GAPPS don't appear there. Does the system partition need to be bigger? I sized at 310MB (in GParted). The same GAPPS installs properly on the EXT4 version of the ROM.

 

[aaopt]

I can't seem to install the GAPPS for the F2FS version (is it the same as the EXT4 version? because the link is the same). It appears to install, but when booting into the system, the GAPPS don't appear there. Does the system partition need to be bigger? I sized at 310MB (in GParted). The same GAPPS installs properly on the EXT4 version of the ROM.

Sometimes it has to be done twice. Not sure why. Are you using f2fs version of TWRP?

Sent from my XT1034 using Tapatalk