yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini Android Development] 115ek:
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 :o

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...
[Galaxy S III Mini Android Development] New Macław:
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 ----------

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.
[Galaxy S III Mini Android Development] 115ek:
I know that it isn't hard :cool:

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? ;)

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:
[Galaxy S III Mini Android Development] New Macław:
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.
[Galaxy S III Mini Android Development] 115ek:
That sounds great. Keep up your work :good:
[Galaxy S III Mini Android Development] ChronoMonochrome:
You're welcome :)

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.

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.

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.
[Galaxy S III Mini Android Development] 115ek:
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 ;)

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.

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. :cool:
[Galaxy S III Mini Android Development] ChronoMonochrome:
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.

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.

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.

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.
[Galaxy S III Mini Android Development] 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. :confused:
[Galaxy S III Mini Android Development] ChronoMonochrome:
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).
[Galaxy S III Mini Android Development] 3liteking148:
New Update

Changelog:

LineageOS source update (June security patch level)

Fix Wifi Autoconnection after deep sleep (based on [MENTION=5695278]ChronoMonochrome[/MENTION]'s hack for it)

Applied SergeyL's patch for AudioFX (now the app starts)

Added Snap Camera (thanks [MENTION=8036586]115ek[/MENTION])

[MENTION=5695278]ChronoMonochrome[/MENTION] I have a new patch for Wifi Autoconnection which just edits one line (here)

Download Link: https://www.androidfilehost.com/?fid=889764386195906431
[Galaxy S III Mini Android Development] isaak:
This release is still valid for S Advance, right?

Probably S Advance users should be informed about the existence of this topic.
[Galaxy S III Mini Android Development] 3liteking148:
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).
[Galaxy S III Mini Android Development] gh0stzk:
Sexy changelog.. Very very smooth, ty king
[Galaxy S III Mini Android Development] 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?
[Galaxy S III Mini Android Development] gh0stzk:
[MENTION=7606633]3liteking148[/MENTION] 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.
[Galaxy S III Mini Android Development] +BOB+:
Hi 3liteking148,

do you plan also to update your Resurection Remix with the new patch for Wifi Autoconnection?
[Galaxy S III Mini Android Development] aelfinn:
+1
[Galaxy S III Mini Android Development] fl4shb4ng:
Totally agreeing. Awesome build :good::laugh:
[Galaxy S III Mini Android Development] Haitham.M:
Download (Gapps) not completed Please fix the problem
[Galaxy S III Mini Android Development] gh0stzk:
Download from opengapps.org
[Galaxy S III Mini Android Development] exwan:
the latest version is awesome. all working great. only downside for is the in call volume is too low. (the earpiece volume)

is there any way to get it higher?
[Galaxy S III Mini Android Development] Frol:
The latest version works smoothly, but the phone occasionally (3-5 times a day) loses SIM card ("no SIM card"). Does anyone experience the same behavior? Neither "airplane mode", nor reboot, nor physical SIM card replace help :(

NOTE: I have been using these firmwares since the February 2017, and I haven't experienced such an issue with 6.0 and previous 7.x releases.
[Galaxy S III Mini Android Development] lucamtb:
Dear Team,

I have an original S3 mini, can I flash directly this rom or do I need to root it first?

THX

Luca
[Galaxy S III Mini Android Development] dazzaa:
hi, what's the easiest way to root the image, i want to try running the phone as a samba server. cheers.
[Galaxy S III Mini Android Development] lucamtb:
I tried to root the TWRP on a stock S3 mini but the mobile say me that the zip file is not signed.

What do I need to do in order to make it working?

Luca
[Galaxy S III Mini Android Development] mauam:
Flash SuperSU system mode from here.
[Galaxy S III Mini Android Development] tyyee:
a few problems.

Would like to ask, anyone out there has the same problem like me.( My device is i8910N)

1) Something wrong with the Video recording, it said that wrong resolution and hang.

2) The wifi will automatically disconnect after a while

3) Charging without turning on the phone, sometimes it won't fully charge the phone.

please share if you have the same problem and any solution......
[Galaxy S III Mini Android Development] mauriciognr:
I made a full tutorial on how to install this ROM from zero, and by zero i mean stock rom. Is in SPANISH. Hope this is ok with OP.

[YOUTUBE]YhoaeUYoyTQ[/YOUTUBE]
[Galaxy S III Mini Android Development] DallasBelt:
Thanks a lot for this ROM! I couldn't stand stock Jelly Bean! There are some issues here and there, but considering that the device is very hardware outdated, I think it works really good.

I had problems trying to get into TWRP. Reboot into recovery causes bootloop, so I have to enter manually with buttons combination. But even that doesn't work at first try. Anyways, not a big deal. I want to see how good is battery life. BTW, how is this ROM compared to New Maclaw's? Has anyone tried it?
[Galaxy S III Mini Android Development] fl4shb4ng:
My battery lasts 2 weeks with 6-7 hours sot. Download a app that forces doze like greenify and the tablet will lose 0% over night
[Galaxy S III Mini Android Development] scelet:
New life for old phone.

It's awesome! Last ROM+mini Gapps+SuperSU - all OK.

For complete happiness, only one thing is missing: Magisk.

Many thanks.
[Galaxy S III Mini Android Development] DallasBelt:
Thanks for sharing your experience! I guess I need a new battery, because even with Greenify it losses power very quickly.
[Galaxy S III Mini Android Development] Knoose:
Hi there! I am trying to flash this rom with twrp 3.0.2. on my 9070p

I am able to manage to get it flashed but the system partition is too small for me to flash even the gapps pico. Is there a way around this?

Kind regards,

Knoose
[Galaxy S III Mini Android Development] fun_boy:
After installing this rom on i8190n experience problem with phone rings. With incoming calls I do not hear rings until the last one.

Then I hear the half of last ring before phone switches to voicemail. Anyone knows how to fix this problem?

Thanks
[Galaxy S III Mini Android Development] armorgeddon:
So can I just flash lineage-14.1-20170609-UNOFFICIAL-golden.zip onto the Advance S GT-I9070 despite it's name suggesting it's for the SIII mini GT-I8190? Thanks in advance!
[Galaxy S III Mini Android Development] Knoose:
Ah jup :) i have the advance p and it sorta works. Apart from the priblem mentioned a few posts above
[Galaxy S III Mini Android Development] fun_boy:
Can anyone explain please how to install Sim Toolkit on LineageOS 14.1 for GT-I8190N?
[Galaxy S III Mini Android Development] doobleshaft:
So far so good for me. TWRP 3.0.2-1 installed on i8190 and about to replace an older version of CM with LineageOS 14.1. I expect this to go ok.

One outstanding issue for me that I haven't resolved yet is that I get a garbage logo at switch on. Returning to stock has had no effect and flashing to any other suitable Rom including replacing the Cyanogen Mod variant I had (12.1 I think...) didn't cure this.

Any suggestions? I'm not even sure what I did to do this. The phone is useable but it makes getting into recovery a bit harder.
[Galaxy S III Mini Android Development] yesh.math:
ROM is Awesome, Lags a bit sometimes. I'm facing problem with WIFI Hotspot whenever i turn on portable Wifi Hotspot i can see error in there. it never turns on even after reboot. Can anyone help me out with this issue
[Galaxy S III Mini Android Development] armorgeddon:
I tried to adb reboot bootloader to flash the TWRP recovery.img-file, but my Samsung Galaxy S Advance GT-I9070 just does a normal reboot instead of going into the bootloader. Any ideas?
[Galaxy S III Mini Android Development] Knoose:
Hmmm I came from another cudtom rom i installed a while ago, remember having this issue as well but i am unsure how i resolved it. I rember following the tutorial for carbon rom which allowed me to use twrp and retain its use. From there i flashed lineage. Mind you though, it does have some instability isdues on our device. I would not recomend it as a daily driver yet
[Galaxy S III Mini Android Development] armorgeddon:
I now tried to flash lineage-14.1-20170609-UNOFFICIAL-golden.zip onto my GT-I9070, but TWRP tells me that the package is only for golden, i8190 :( While this project is great is clearly lacks in the documentation, because the opening post says that this ROM support the GT-I9070. I'll now try out cm14.1-20161223-UNOFFICIAL-janice_UNTESTED.zip.
[Galaxy S III Mini Android Development] Knoose:
Which twrp version are you using?
[Galaxy S III Mini Android Development] Dreackm:
It does seem to be a corrupted boit logo (the very first image to be displayed upon switching on the phone). It happened to me once and I did have hard time getting into recovery too.

What worked for me was flashing a new param file, you can get one from here https://xdaforums.com/showthread.php?t=2432783
[Galaxy S III Mini Android Development] mauam:
Or you can find the original bootlogo here.
[Galaxy S III Mini Android Development] armorgeddon:
Thanks for your answers! It was 2.6x since I couldn't find or rather install a newer version. Doesn't matter now though, because I now flashed NovaFusion's CM11 onto the Advance S and it runs pretty much perfect.
[Galaxy S III Mini Android Development] klaus-hamburg:
Thanks for keeping this device still alive with current android.

Works fine for me . :good: :) :good: :)
[Galaxy S III Mini Android Development] mauriciognr:
Hi guys i share you a video i made running Antutu Benchmark in the S3 mini with this ROM Hope this is ok with OP.

[YOUTUBE]h4AWyRGtS84[/YOUTUBE]
[Galaxy S III Mini Android Development] axy_david:
anychance of overclock?
[Galaxy S III Mini Android Development] J's:
TWRP dedicated in this custom rom ( version 3.0.2) is available at the first page. All u need to do is to search how to convert .img files to .tar files (in XDA too) so that you can flash via ODIN.
[Galaxy S III Mini Android Development] tempuser123:
For me fixing screws for getting a GPS fix didn't work.

My solution: Use lineageos from novafusion.
[Galaxy S III Mini Android Development] AnDrOiiiD_YT:
[MENTION=7606633]3liteking148[/MENTION] are you sure that this works on the galaxy s advance? They have similiar specs but are the partition sizes also the same?

Edit: The SoC is also not the same. The S3 mini uses the U8420 and the S Advance the U8500...

Edit2: Sorry for the wrong informations. GSMARENA says that the S3 mini uses the U8420
[Galaxy S III Mini Android Development] axy_david:
DUD the s3 mini has the U8500
[Galaxy S III Mini Android Development] AnDrOiiiD_YT:
You're right GSMARENA has wrong information. I edited my post
[Galaxy S III Mini Android Development] NandoHiller:
Charging Problem

Shutdown/Reboot/Kill after charging cycle.

Is this problem known?

GT-I8190N

lineage-14.1-20170609-UNOFFICIAL-golden
[Galaxy S III Mini Android Development] aepot:
Time Zone being reset to GMT after few hours device idle time. Enabling/disabling airplane mode (register to cell network again) fixes this issue temporarly. Manual setting Time Zone also can be used as solution.

My TZ is +3 GMT. Mobile provider MTS RUS.

GT8190
[Galaxy S III Mini Android Development] Lovely sohan:
pleas cm.14. for gt-i8200 plezz....?
[Galaxy S III Mini Android Development] Enzycal:
Sim card not detected

I just went from stock to lineage-14.1-20170609-UNOFFICIAL-golden + open_gapps-arm-7.1-mini-20170927.

Everything works great except for the sim card not getting detected. Rebooting or clearing Cache/ Dalvik doesn't help.

Is there a modem update I could try flashing?
[Galaxy S III Mini Android Development] gh0stzk:
Thats an old release. elit3king is no more active.
[Galaxy S III Mini Android Development] Enzycal:
Oh I didn't know. I just looked for the latest version available available at the download link. It was uploaded on Jun 09, 2017.

Which is the latest working version then?

Thanks.

Rok
[Galaxy S III Mini Android Development] mauam:
Can I ask why do want to use this rom, when you have a more recent (from a more active dev) here!?
[Galaxy S III Mini Android Development] Enzycal:
I'm going to use it as my second phone as my main phone doesn't support dual sim. Thank you very much for the link, I realy appreciate it!
[Galaxy S III Mini Android Development] UnOrdinary:
[MENTION=7606633]3liteking148[/MENTION]

Hello Bro

Can Tell me that in this rom while calling is that getting low sound from earpiece?
[Galaxy S III Mini Android Development] UnOrdinary:
Hay this rom have Same Low Sound Problem While calling?
[Galaxy S III Mini Android Development] xEmre66:
3liteking is working on the 3.4 kernel. He is inactive but does something great in the background.
[Galaxy S III Mini Android Development] UnOrdinary:
I know

But 18 Days Ago He did last changes
[Galaxy S III Mini Android Development] asnachan:
it's 3 weeks that i am trying to root this devil device..it's my first time with rooting and i really can't belive is this madness hard.

there are like 1 bilion of guides that are totally different and no one of them works on me...

i am stucked there on twrp i installed the zip from the sd card what i have to do now? please end my suffering
[Galaxy S III Mini Android Development] Bludwurst:
It really shouldn't be hard; although Samsung (especially older devices) seem to always be an struggle (maybe it no longer is?)

The only dumb thing I can think of is that your TWRP is ancient.

Maybe give this newer one a try and see what happens? But be careful, as always.

https://xdaforums.com/showthread.php?t=2748327