[ROM][7.1.2] LineageOS 14.1 for GT-I8190/GT-I9070 [2017-06-09]

[115ek]

So I searched for MALLOC_SVELTE and found it's good for low RAM devices so enabling it won't be bad. With dexpreopt, is the device faster or not?

Hey! I think it runs smoother. But my opinion isn't really objective. Any idea how to measure the speed?

P.S. I have already added the local_manifest.xml to OP for reference.

Great! Other people wanting to build on there own will be very happy

I've still got questions:
What build flavour you are using? user for your actual releases and eng for debugging?
Or userdebug because of it's root possibility?

Another thing:
Is it fortune, that New Macław also added Snap support in his newest build? https://xdaforums.com/showpost.php?p=72300827&postcount=312
Or do you share sources? I asked him several times for an updated device repo, but never got an answer. I can't understand this behaviour.
I thought it was the actual idea of android - that all is free for everyone...

 

[New Macław]

Hey! I think it runs smoother. But my opinion isn't really objective. Any idea how to measure the speed?


Great! Other people wanting to build on there own will be very happy

Another thing:
Is it fortune, that New Macław also added Snap support in his newest build? https://xdaforums.com/showpost.php?p=72300827&postcount=312
Or do you share sources? I asked him several times for an updated device repo, but never got an answer. I can't understand this behaviour.
I thought it was the actual idea of android - that all is free for everyone...

It isn't so hard to add Snap to your ROM - one line is required. Switched to it due to my community asked me to do so.

---------- Post added at 02:56 PM ---------- Previous post was at 02:53 PM ----------

So I searched for MALLOC_SVELTE and found it's good for low RAM devices so enabling it won't be bad. With dexpreopt, is the device faster or not?

P.S. I have already added the local_manifest.xml to OP for reference.

ROM with "dexpreopt" won't be much faster - only boot will be much faster, especially first. It means no rebuild of cache for preinstalled apps (these one that comes with ROM on /system partition).

But we have huge free space amount on /system partition, so I don't think it's a bad idea to use it.

 

[115ek]

It isn't so hard to add Snap to your ROM - one line is required. Switched to it due to my community asked me to do so.

I know that it isn't hard
That's the reason I can't understand why you didn't switched earlier. Camera2 was very, mhh, laggy (also deprecated). And why don't you share your device sources?

ROM with "dexpreopt" won't be much faster - only boot will be much faster, especially first. It means no rebuild of cache for preinstalled apps (these one that comes with ROM on /system partition).

But we have huge free space amount on /system partition, so I don't think it's a bad idea to use it.

Is there a possibility to test the speed? I just found out that's it is hard to say without any kind of benchmark. Except of the first boot. It's really rapid. You don't even need a clock for measuring to see the difference :laugh:

 

[New Macław]

I know that it isn't hard
That's the reason I can't understand why you didn't switched earlier. Camera2 was very, mhh, laggy (also deprecated). And why don't you share your device sources?

Hmmm. Why? Because I work on device in parts - first I've fixed GPS, then went to camera etc. I am prioritising parts that works worst - GPS was not working at all. That's all

Will share sources, but I have no repo for now - just ****ty private repo with junk commits names and have to reorganise it first - haven't had enough time last months, but I hope this month I will finally push them to GitHub.

 

[115ek]

Hmmm. Why? Because I work on device in parts - first I've fixed GPS, then went to camera etc. I am prioritising parts that works worst - GPS was not working at all. That's all

Will share sources, but I have no repo for now - just ****ty private repo with junk commits names and have to reorganise it first - haven't had enough time last months, but I hope this month I will finally push them to GitHub.

That sounds great. Keep up your work :good:

 

[ChronoMonochrome]

Yeah! I'm so happy at the moment. Invested several hours and now it works. Thank you so much for your tip with adding the stlport repo. You saved me a lot of time.

You're welcome

The android build process is such a huge and complex thing - it's not very easy to get into it. How did you learned all that stuff? Trial and error?

Yeah, it was (and still is) a tedious way of the trial and error. At the moment I've ever started working on ROMs development I was already experienced with a kernel development so it wasn't too tough as if I'd start learning it from scratch.

Okay. I'll investigate further. These sudden reboots are very hard to fix. You don't know when they appear - and if they do - you don't get it because you're sleeping...
Anyway, big thanks to you! You saved my sunday

You can use uptime terminal command (or particularly any app that shows how many time was spent since the device boot up). If you find this time is lesser than you expect - it can be that the device has rebooted, in this case you can still capture /proc/last_kmsg log to find any information about reboot.

Great
Does someone know what effect

MALLOC_SVELTE := true

has got? I thought it may be good for low RAM devices. But please correct me if I'm wrong.
I also thought about using

WITH_DEXPREOPT := true

maybe with some special parameters. It's explained here: https://source.android.com/devices/tech/dalvik/configure#compilation_options .
I've got this from a LegacyXperia guy, SteadyQuad. See his patchset here: http://review.msm7x30.org/#/c/1609/.
Google just says the first boot time will be optimized. But SteadyQuad also reports a better system responsiveness (Launcher, inCallUI, etc).
The negative side effect is of course a larger system image. I don't know if that makes problems. What do you think about it? Any experts out there?

Edit: Build just finished with

WITH_DEXPREOPT := true

.
-> 370 MB :laugh: But I was able to install it. First bootup time without wiping /system /data /cache was 1:20 min.
Even with complete wipe it just needs 1:33 min to boot up.

Nice discussion here
As for about

MALLOC_SVELTE := true

- I have heard that our devices' camera doesn't play nicely with this flag. I can't test things right now, as I'm slowly moving forward with the compilation of AOSP-based ROM (it's actually a mess right now, RIL doesn't work as some required telephony patches are missing).
About dex preoptimizaion - some benchmarks (e.g. Quadrant) can show a better VM runtime performance. In the most cases it doesn't affect an overall performance, as many apps put the most performance-critical code into a native JNI libraries. Personally I anyway prefer dex optimized ROMs as it can reduce the boot up time (and any further boot time after a wipe), at the cost of an installation time and /system partition space. The positive side is that the less space on /data is used (if position-independent code flag is enabled), the worst effects are that any change in framework.jar will require you to rebuild any Java targets + as far as I know, Xposed doesn't work with postition-independent dex preopt flag.

 

[115ek]

You can use uptime terminal command (or particularly any app that shows how many time was spent since the device boot up). If you find this time is lesser than you expect - it can be that the device has rebooted, in this case you can still capture /proc/last_kmsg log to find any information about reboot.

Such an easy trick. I didn't thought about it. It's so good that there are people who already had the most kinds of problems and share their experience. That saves so much time and frustration. But I think some frustration is necessary

Nice discussion here
As for about

MALLOC_SVELTE := true

- I have heard that our devices' camera doesn't play nicely with this flag. I can't test things right now, as I'm slowly moving forward with the compilation of AOSP-based ROM (it's actually a mess right now, RIL doesn't work as some required telephony patches are missing).

You're from the kernel side aren't you? So what is SVELTE really doing? Malloc sounds like low level kernel-stuff and memory management. Does SVELTE optimize the memory usage or allocation?
Anyway, I'm going to test how the camera behaves. The build is already finished, just need to flash it.

About dex preoptimizaion - some benchmarks (e.g. Quadrant) can show a better VM runtime performance. In the most cases it doesn't affect an overall performance, as many apps put the most performance-critical code into a native JNI libraries. Personally I anyway prefer dex optimized ROMs as it can reduce the boot up time (and any further boot time after a wipe), at the cost of an installation time and /system partition space. The positive side is that the less space on /data is used (if position-independent code flag is enabled), the worst effects are that any change in framework.jar will require you to rebuild any Java targets + as far as I know, Xposed doesn't work with postition-independent dex preopt flag.

Okay, so you think WITH_DEXPREOPT_PIC := true is the best way to go? In size it doesn't seem to be very different compared to only WITH_DEXPREOPT := true.

And where did you get the experience and source code for the low level things (the whole u8500 platform things...) from? I've got an Ace Plus lying around here. The custom ROM development stopped at CM11. And I thought about doing something for it. But where to start if you want to bring all the things to android 7? Is it better to take the steps in between, so Lollipop or marshmallow? I think it's really hard. But enabling the Snap camera isn't really challenging. There so many more interesting problems out there.

 

[ChronoMonochrome]

You're from the kernel side aren't you? So what is SVELTE really doing? Malloc sounds like low level kernel-stuff and memory management. Does SVELTE optimize the memory usage or allocation?
Anyway, I'm going to test how the camera behaves. The build is already finished, just need to flash it.

This option changes the configuration of the jemalloc memory allocator:

ifeq ($(MALLOC_SVELTE),true)
# Use a single arena on svelte devices to keep the PSS consumption as low
# as possible.
jemalloc_common_cflags += \
        -DANDROID_MAX_ARENAS=1 \

else
# Only enable the tcache on non-svelte configurations, to save PSS.
jemalloc_common_cflags += \
        -DANDROID_MAX_ARENAS=2 \
        -DJEMALLOC_TCACHE \
        -DANDROID_TCACHE_NSLOTS_SMALL_MAX=8 \
        -DANDROID_TCACHE_NSLOTS_LARGE=16 \

endif

So, enabling this flag can reduce PSS footprint, at the some extent. Though, I really can't say if this configuration is an optimal.

Okay, so you think WITH_DEXPREOPT_PIC := true is the best way to go? In size it doesn't seem to be very different compared to only WITH_DEXPREOPT := true.

Enabling WITH_DEXPREOPT_PIC := true aboids creating the ART cache on /data partition (so, all the ART stuff gets loaded directly from /system partition), though as I said previously, Xposed can't work with this flag enabled, so using it's arguable.

And where did you get the experience and source code for the low level things (the whole u8500 platform things...) from?

We have already had a source code for the platform since JB was released (device tree, some open source libs and kernel source) - there are also some sources that were leaked later, though so far only a bit of those are actually can be used (gralloc, hwcomposer, copybit etc). At the beginning of the kernel development I have just started cherry-picking commits from other kernel repositories I could find. Later, I started experimenting with the various configs and porting some stuff on my own. Still, various repositories is a good source to learn from.

I've got an Ace Plus lying around here. The custom ROM development stopped at CM11. And I thought about doing something for it. But where to start if you want to bring all the things to android 7? Is it better to take the steps in between, so Lollipop or marshmallow? I think it's really hard. But enabling the Snap camera isn't really challenging. There so many more interesting problems out there.

Yep, I would start from bringing up lollipop first (actually it's better first to build CM11, just to ensure that you don't miss any necessary fixes at this point), then the further android releases. The most of the device fixes, that are required to be used in, e.g. android 5.0, are still likely will be needed later. So far I know only one exception - we had a non-working audio on android 7.0 (nor we had any clues about fixing), so we have just skipped this android release, - thanks to 7.1 release we have gotten audio working again.

 

[115ek]

I'm getting very reproducable reboots when connecting to the wifi:

--------- beginning of crash
05-15 23:52:37.915  2753  6205 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x78 in tid 6205 (Thread-59)
05-15 23:52:38.002  2753  6205 F libc    : failed to resend signal during crash: Operation not permitted
05-15 23:52:38.069  5727  6134 E AndroidRuntime: FATAL EXCEPTION: WifiSettings
05-15 23:52:38.069  5727  6134 E AndroidRuntime: Process: com.android.settings, PID: 5727
05-15 23:52:38.069  5727  6134 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
05-15 23:52:49.263  6753  6753 I chatty  : uid=1000 system_server expire 267 lines
05-15 23:52:51.585  6753  6831 I chatty  : uid=1000 system_server expire 4 lines
05-15 23:52:52.185  6753  6944 I chatty  : uid=1000 system_server expire 7 lines
05-15 23:52:52.189  6753  6946 I chatty  : uid=1000 system_server expire 6 lines
05-15 23:52:52.222  6753  6947 I chatty  : uid=1000 system_server expire 6 lines
05-15 23:52:52.528  6753  6948 I chatty  : uid=1000 system_server expire 2 lines
05-15 23:52:52.864  6753  6945 I chatty  : uid=1000 system_server expire 3 lines
05-15 23:52:53.404  6753  6949 I chatty  : uid=1000 system_server expire 1 line
05-15 23:52:54.659  6753  6796 I chatty  : uid=1000 system_server expire 1 line
05-15 23:52:56.326  6753  6789 I chatty  : uid=1000 system_server expire 2 lines
05-15 23:52:56.395  6753  6972 I chatty  : uid=1000 system_server expire 39 lines
05-15 23:52:56.405  6753  6974 I chatty  : uid=1000 system_server expire 2 lines
05-15 23:52:56.446  6753  6973 I chatty  : uid=1000 system_server expire 2 lines
05-15 23:52:56.643  6753  6975 I chatty  : uid=1000 system_server expire 1 line
05-15 23:52:57.335  6239  6928 D NetlinkEvent: Unknown ifindex 11 in RTM_DELADDR
05-15 23:52:59.091  6753  6753 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.pattern.key: open failed: ENOENT (No such file or directory)
05-15 23:52:59.092  6753  6753 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.gesture.key: open failed: ENOENT (No such file or directory)
05-15 23:52:59.093  6753  6753 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gesture.key: open failed: ENOENT (No such file or directory)

I think you can't find the issue in these lines. Or can you? But I didn't want to post the whole logcat, there are a lot of personal informations...
Don't know if that's caused by SVELTE. I didn't activate the wifi in earlier builds. New Macław has got the same problem in his newest build. So maybe it's an lineage issue.

 

[ChronoMonochrome]

I'm getting very reproducable reboots when connecting to the wifi:

--------- beginning of crash
05-15 23:52:37.915  2753  6205 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x78 in tid 6205 (Thread-59)
05-15 23:52:38.002  2753  6205 F libc    : failed to resend signal during crash: Operation not permitted
05-15 23:52:38.069  5727  6134 E AndroidRuntime: FATAL EXCEPTION: WifiSettings
05-15 23:52:38.069  5727  6134 E AndroidRuntime: Process: com.android.settings, PID: 5727
05-15 23:52:38.069  5727  6134 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
05-15 23:52:49.263  6753  6753 I chatty  : uid=1000 system_server expire 267 lines
05-15 23:52:51.585  6753  6831 I chatty  : uid=1000 system_server expire 4 lines
05-15 23:52:52.185  6753  6944 I chatty  : uid=1000 system_server expire 7 lines
05-15 23:52:52.189  6753  6946 I chatty  : uid=1000 system_server expire 6 lines
05-15 23:52:52.222  6753  6947 I chatty  : uid=1000 system_server expire 6 lines
05-15 23:52:52.528  6753  6948 I chatty  : uid=1000 system_server expire 2 lines
05-15 23:52:52.864  6753  6945 I chatty  : uid=1000 system_server expire 3 lines
05-15 23:52:53.404  6753  6949 I chatty  : uid=1000 system_server expire 1 line
05-15 23:52:54.659  6753  6796 I chatty  : uid=1000 system_server expire 1 line
05-15 23:52:56.326  6753  6789 I chatty  : uid=1000 system_server expire 2 lines
05-15 23:52:56.395  6753  6972 I chatty  : uid=1000 system_server expire 39 lines
05-15 23:52:56.405  6753  6974 I chatty  : uid=1000 system_server expire 2 lines
05-15 23:52:56.446  6753  6973 I chatty  : uid=1000 system_server expire 2 lines
05-15 23:52:56.643  6753  6975 I chatty  : uid=1000 system_server expire 1 line
05-15 23:52:57.335  6239  6928 D NetlinkEvent: Unknown ifindex 11 in RTM_DELADDR
05-15 23:52:59.091  6753  6753 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.pattern.key: open failed: ENOENT (No such file or directory)
05-15 23:52:59.092  6753  6753 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.gesture.key: open failed: ENOENT (No such file or directory)
05-15 23:52:59.093  6753  6753 E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gesture.key: open failed: ENOENT (No such file or directory)

I think you can't find the issue in these lines. Or can you? But I didn't want to post the whole logcat, there are a lot of personal informations...
Don't know if that's caused by SVELTE. I didn't activate the wifi in earlier builds. New Macław has got the same problem in his newest build. So maybe it's an lineage issue.

Well, there is nothing in log that can give a clue about wifi crashes. Normally you need a full backtrace that can be seen in a tombstone log (for this debuggerd is required to work properly with a kernel patch aforementioned earlier).

 

[3liteking148]

New Update

Changelog:

• LineageOS source update (June security patch level)
• Fix Wifi Autoconnection after deep sleep (based on @ChronoMonochrome's hack for it)
• Applied SergeyL's patch for AudioFX (now the app starts)
• Added Snap Camera (thanks @115ek)

@ChronoMonochrome I have a new patch for Wifi Autoconnection which just edits one line (here)

Download Link: https://www.androidfilehost.com/?fid=889764386195906431

 

[isaak]

Changelog:

• LineageOS source update (June security patch level)
• Fix Wifi Autoconnection after deep sleep (based on @ChronoMonochrome's hack for it)
• Applied SergeyL's patch for AudioFX (now the app starts)
• Added Snap Camera (thanks @115ek)

@ChronoMonochrome I have a new patch for Wifi Autoconnection which just edits one line (here)

Download Link: https://www.androidfilehost.com/?fid=889764386195906431

This release is still valid for S Advance, right?
Probably S Advance users should be informed about the existence of this topic.

 

[3liteking148]

This release is still valid for S Advance, right?
Probably S Advance users should be informed about the existence of this topic.

Yes it is but I haven't made changes to golden's (S3 Mini) vendor repo to flash the blobs seperately instead of it being integrated to the ROM to fix issues such as audio, RIL, etc. It will happen in next build (very soon).

 

[gh0stzk]

Changelog:
LineageOS source update (June security patch level)
Fix Wifi Autoconnection after deep sleep (based on @ChronoMonochrome's hack for it)
Applied SergeyL's patch for AudioFX (now the app starts)
Added Snap Camera (thanks @115ek)


@ChronoMonochrome I have a new patch for Wifi Autoconnection which just edits one line (here)

Download Link: https://www.androidfilehost.com/?fid=889764386195906431

Sexy changelog.. Very very smooth, ty king

 

[115ek]

I tested some build flags and observed these things, just if someone wants to know...

WITH_DEXPREOPT := true

--> reboot if connecting to wifi

MALLOC_SVELTE := true

--> reboot if executing USSD code

By building from original 3liteking148 source without changes I ran into problems when calling someone. The screen gets dark and you can't turn it on again to abort the call. Does someone also faced such an issue?

 

[gh0stzk]

@3liteking148 this build is great...

- Gallery finally doesnt feels laggy
- Gallery visual bug is fixed.
- Youtube no lagging or micro stops in playback.
- Instagram videos works. But u need to activate "start videos without sound" to make it work.
- Gps works well.
- System feels very smooth, and stable after 5 hrs


- Camera stops if u record a video WITH flash activated with videos with more than one minute of legenth.

Could u plis make magisk compatible.

 

[+BOB+]

Changelog:

• LineageOS source update (June security patch level)
• Fix Wifi Autoconnection after deep sleep (based on @ChronoMonochrome's hack for it)
• Applied SergeyL's patch for AudioFX (now the app starts)
• Added Snap Camera (thanks @115ek)

@ChronoMonochrome I have a new patch for Wifi Autoconnection which just edits one line (here)

Download Link: https://www.androidfilehost.com/?fid=889764386195906431

Hi 3liteking148,
do you plan also to update your Resurection Remix with the new patch for Wifi Autoconnection?

 

[aelfinn]

Hi @3liteking148 ,
do you plan also to update your Resurection Remix with the new patch for Wifi Autoconnection?

+1

 

[fl4shb4ng]

@3liteking148 this build is great...

- Gallery finally doesnt feels laggy
- Gallery visual bug is fixed.
- Youtube no lagging or micro stops in playback.
- Instagram videos works. But u need to activate "start videos without sound" to make it work.
- Gps works well.
- System feels very smooth, and stable after 5 hrs


- Camera stops if u record a video WITH flash activated with videos with more than one minute of legenth.

Could u plis make magisk compatible.

Totally agreeing. Awesome build :good::laugh:

 

[Haitham.M]

Download (Gapps) not completed Please fix the problem