yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini Original Android Development] pm-cz:
Hello,

I have installed today's version (a clean install) and so far I have encountered following issues:

- System brightness control does not work (and brightness menu entry in settings shows Adaptive brightness on even there is no light sensor in this device). When I used external brightness application and turned off auto brightness, the adjustment was possible.

- Night mode settings does not seem to influence anything but LiveDisplay works.

- The quick access icons which are more than a page away from top cannot be inserted (they are lost during moving up more than a page) in edit mode, extra icons such as LTE are present

- WiFi disconnects when screen is off after some time (observed on 2.4+5GHz N network ESS) and has to be reconnected manually

- WiFi settings have not been restored from cloud but that might be normal

- Magisk installation does not detect boot partition (and probably is not working as a message requesting storage access appears event it is enabled in application setting)
[Galaxy S III Mini Original Android Development] +BOB+:
Great!

This release is a big step forward.

Now I only miss wifi auto connect (works on boot, but not later) and BLN.
[Galaxy S III Mini Original Android Development] fergus2016:
I choose zzmovee - one core falls asleep, the phone hangs and reboots.

When you already correct the kernel shutdown ?????

2) The quick access icons which are more than a page away from top cannot be inserted (they are lost during moving up more than a page) in edit mode, extra icons such as LTE are present

3) the battery is quickly discharged during use, compared to 6.0.1
[Galaxy S III Mini Original Android Development] SniiKz:
I was testing the ROM and by the time the performance is not affected by that mode, good job maclaw
[Galaxy S III Mini Original Android Development] jcbportela:
No WiFi auto re-connect

Overall performance is good (compared with LOS14.1 that I was trying), but suffer from same issue of LOS14.1: no automatic re-connect to previously saved network when it becomes available.

Good job!
[Galaxy S III Mini Original Android Development] bsix-n:
Its now very stable? No hangs even when im not using any app in background? My phone hang alot sometime, i cant answer incoming call but my phone ring.. all this in previus build (0507) alot of bug with performance !! And i see that consume alot of RAm.. i still with ~178 maximum 200mb of free Ram
[Galaxy S III Mini Original Android Development] fergus2016:
Few free RAM.

It brakes at a frequency below 400 Mhz (6.0.1 does not brake)

Poorly catches the network. Where on 6.0.1 there was a weak "H" signal, 7.1.2 "E" or no internet at all.

Zzmovее, abyssplug - when the kernel is shut down, the phone hangs several times and reboots. I have to use another governor.
[Galaxy S III Mini Original Android Development] bsix-n:
So what frequency i have to use? Coz my phone hang alot and yes sometime i have to pull out the baterry and sometimes reboot

"Frequency" i mean governor..
[Galaxy S III Mini Original Android Development] fergus2016:
Any governor who does not sleep on the core. (That is, except zzmovee and abysplug).

I'm still using ondemand, but I'll take it again 6.0.1. Since 7.1.2 is moist again.
[Galaxy S III Mini Original Android Development] b_henry:
1) https://xdaforums.com/showpost.php?p=72185537&postcount=57

2) Nougat bug (google before you post a buglist)

3) wipe and try again
[Galaxy S III Mini Original Android Development] Bahaadir:
thanks dude you are the best!! How its battery life btw?
[Galaxy S III Mini Original Android Development] fergus2016:
Full wipe, hard reset, format data : The battery discharges quickly. On 6.0.1 and others lives longer.

Hotplug - saves the battery well with active use. Two cores at the maximum frequency are needed at startup, and sometimes when watching videos in high quality. All the rest of the time one core at a frequency of 200-1000 MHz perfectly copes with the tasks, without sacrificing performance.

7.1.2 (20170516) - Music falters when you scroll through the news feed in VK, or when you launch applications.

The system generally slows down and there is no plan, it jerks. There is not enough power s3 mini for 7 Android.

Delivered CM11 with the core 1N148 to f2fs - great performance, smooth interface, Internet speed. No glitch with the unlocking of the screen.

Video reproduced without falling behind the picture from the sound and with any quality.

A large set of network settings (rather than one reno and cubic). There are many CPU and frequency drivers. The battery lives well when used. Autonomy is magnificent.

In general, this is the most successful combination for the s3 mini today. Better than this firmware is not.

UPD: By the way, pop-up notifications VK do not work on 6.0.1 and 7.1.2. 4.4.4 works well.
[Galaxy S III Mini Original Android Development] docmorpheus:
Rom runs very smooth and stabile.

As already Mentoren, WIFI autoconnection with known networks does not work.

[MENTION=8218131]fergus2016[/MENTION]:

You are completely right, this ROM is not working perfect. But it is getting better and better with every release.

IMHO you can compare the S3 mini with an oldtimer car. Driving it makes fun, but you have to live with some restrictions. If you want to drive fast and comfortable you will have to buy a new up-to-date one.

Samsung told us, that an update from Jelly Bean to Kitkat would not be possible due to low RAM capability. Though Mr. Maclaw got it and keeps the device alive until now. Even with Nougat. But we all have to keep in mind, that its getting harder and harder withe every Android version and we will have to live with some issues that cannot be solved due to hardware limitations. But this is absolutely NOT the fault of Mr. Maclaw! In my opinion he is doing a great job.

If you feel better running your S3 mini with CM11 live long and happy with it. But please stop argue here. Or please be a little bit more constructive ;)
[Galaxy S III Mini Original Android Development] fergus2016:
Do not say that 7.1.2 is the most productive and smooth, because it is not on the s3 mini

7.1.2 on the s3 mini lag and brake. Even the music stutters without load. :хорошо:

What prevents the Maclaw from fixing the bug with the unlocking screen, which appeared on the 5.0.1 android and is still there, even on fresh 7.1.2? On 4.4.4 the bug was not yet there.
[Galaxy S III Mini Original Android Development] b_henry:
[MENTION=8218131]fergus2016[/MENTION] Do you have LiveDisplay disabled? Because if enabled, "night mode" slightly decreases performance or at least smoothness.

edit: Regarding "lockscreen bug", it sometimes happened even on OmniROM 5.1.1 and I dare to say that far more often than on these roms..
[Galaxy S III Mini Original Android Development] cango123:
Uff... Bruh if you don't like it, go back to stock and stop complaining about every f****** issue... Don't forget that maclaw and all the other devs don't take money for this, it's just a hobby...
[Galaxy S III Mini Original Android Development] Gazklatic:
Hi, i have a problem. When i activate the lockscreen in PIN and i turn on the fast unlock, dont recognize the pin when i have to unlock my phone again. Please fix it. But the ROM is excellent ;)
[Galaxy S III Mini Original Android Development] docmorpheus:
Hmm... strange. Using PIN with fast unlock for several weeks now without any issues :confused:
[Galaxy S III Mini Original Android Development] jcbportela:
Is there any quick fix for the WiFi autoconnection "issue"?
[Galaxy S III Mini Original Android Development] psisop:
Wich one releases its work? 1 of 3 if i`m remember correctly.
[Galaxy S III Mini Original Android Development] New Macław:
New stable release is out!

http://novafusion.pl/
[Galaxy S III Mini Original Android Development] Aayhan:
samsung boot logo stayed (Nougat 7.1.1 (Resurrection Remix) 20170412)
[Galaxy S III Mini Original Android Development] Robbe2:
First upgraded from 6.0.1, later a clean installation.

Thanks anyway for your effort.

Samsung boot loop. With and without gapps.

S3 mini GT I8190

Twrp 2.8.0.0
[Galaxy S III Mini Original Android Development] New Macław:
Flashed by recovery? Using f2fs?

I am sure this release is 100% working. we need to investigate your case. I am almost sure download has been broken - please, redownload the package and check MD5.
[Galaxy S III Mini Original Android Development] Willekin:
Even if I format System/Data/Cache with TWRP to f2fs, when i press Install it automatically format System EXT4 and after a few seconds it says Success.

After reboot stuck on Samsung Logo.
[Galaxy S III Mini Original Android Development] New Macław:
Use ext4 only. Probably f2fs support is too unstable for now!
[Galaxy S III Mini Original Android Development] Willekin:
I also tried that, format all to EXT4 but after reboot stuck on Samsung Logo.

This Release takes only a few seconds to install (max 5 sec.)

The Release from 05.04.17 took much longer.
[Galaxy S III Mini Original Android Development] New Macław:
Something is wrong with your ZIP. Please redownload it. We've already confirmed on Facebook that issue was F2FS.
[Galaxy S III Mini Original Android Development] Minfred:
Hi,

flashed the rom from 170412 (today).

I came from CM12, wiped dalvik, cache and internal storage and flashed the rom and pico-gapps.

Thanks for your work, you do a great job!

Unfortunately i have some issues:

- flash and first boot took some time, you have to be patient :D

- wifi doesn't work after deepsleep

- sometimes the device slows down :/

Can I support in any way?

Greetz
[Galaxy S III Mini Original Android Development] New Macław:
Thanks for report, all of listed issues are going to be resolved.

Regards
[Galaxy S III Mini Original Android Development] Robbe2:
Hi New Maclaw

I used TWRP 2.8.0.0 and I keep ext4 in all the partitions.

I will redownload the ROM again and test it and let you now
[Galaxy S III Mini Original Android Development] tombixda:
Please give me another link to the file "rr7.1_golden.nova.20170412.ODIN_TWRP.zip" I download it several times and still crc error when unzipping.

Thank you!
[Galaxy S III Mini Original Android Development] gh0stzk:
I download 3 times the rom i also checked de md5 and is different from the one maclaw provide MD5: b775082f735922c975d5b935eae8fc27 thats the nova md5. my md5 is different.. maybe is trhe zip.. but i download 3 times.. someone could upload to another server?

i have bootloop in samsung screen
[Galaxy S III Mini Original Android Development] brka35:
hi New Macław build 170412 not working for me i get bootloop,,,,, stuck on samsung logo but i tested your build 170406 that you give me

via private mail: i find bug with wifi autoconetion after deep sleep,,,,,offline charging not working..... slow animations, youtube 480p dont working, but i must say battery life is good
[Galaxy S III Mini Original Android Development] Robbe2:
Hi New Maclaw

Redownloaded the package and now finally started.

I am upgrading from RR 6.0.1

Pico gapps 12/04/2017

The screen is kind of slow in response.

Sim in my case is detected immediately

Starting Magisk Manager makes the cell to restart.

Not able to open the clock app and to establish a clock widget

Camera working in photos and videos

WhatsApp working OK

That is all for the moment.

Not able to make Magisk Manager work

Nice ROM and great job guys.
[Galaxy S III Mini Original Android Development] JoshuaHoff:
I am with the same problem every time that i download and redownload the zip it comes with a different MD5.
[Galaxy S III Mini Original Android Development] tombixda:
I also downloaded both versions several times using different browsers and always tried to unpack 7-zip or winrar ends with a CRC error :(
[Galaxy S III Mini Original Android Development] fergus2016:
No. LiveDisplay disabled. CPU governor - interactive. With these settings, the screen does not immediately react to touching to unlock. This problem started with Android 5.0.1.
[Galaxy S III Mini Original Android Development] New Macław:
Fighting with Wifi hotspot. [MENTION=5695278]ChronoMonochrome[/MENTION], any ideas?
[Galaxy S III Mini Original Android Development] Gazklatic:
I mean, with a large pin, the phone un fast unlock dont recognize the pin. Then with a short pin, it works perfect.
[Galaxy S III Mini Original Android Development] ChronoMonochrome:
I've recently built Omni 7.1, and I haven't encountered problems with the wifi hotspot (I have only checked whether it can start at all, without checking if anyone can connect to it). Maybe something in these configs can be useful - https://github.com/ChronoMonochrome/android_device_samsung_codina/tree/cm-14.1/configsnew

- I remember, SergeyL was changing something in p2p_supplicant_overlay.conf / wpa_supplicant_overlay.conf.

UPD. nah, just remembered an issue with the netd on 7.1 - try this patch out: https://github.com/ChronoMonochrome...em-netd_W00-Revert-start-tethering-IPv6.patch
[Galaxy S III Mini Original Android Development] b_henry:
Hotspot itself can start, other devices can connect to it, BUT if you enable mobile data, immediately stops with error.
[Galaxy S III Mini Original Android Development] bsix-n:
Hi all im here to say to you guys that im no longer a s3 mini user, i purchased an s4 mini Duos yestarday that is more beterr to use becouse my old s3mini still With lag even with stock Rom i think was a Mother board memory goes slow why i dont Know, but thank you all for the support [MENTION=1806372]newmac[/MENTION]law sir keep doing this great job keep support all s3 mini users you are the Best....

---------- Post added at 02:04 PM ---------- Previous post was at 02:03 PM ----------

Hi all im here to say to you guys that im no longer a s3 mini user, i purchased an s4 mini Duos yestarday that is more beterr to use becouse my old s3mini still With lag even with stock Rom i think was a Mother board memory goes slow why i dont Know, but thank you all for the support [MENTION=1806372]newmac[/MENTION]law sir keep doing this great job keep support all s3 mini users you are the Best....
[Galaxy S III Mini Original Android Development] ChronoMonochrome:
That's probably just an error with the setting forwarding rules via netd - will check it when I get home.
[Galaxy S III Mini Original Android Development] New Macław:
Damn, will test it right now. You rock dude!
[Galaxy S III Mini Original Android Development] JoshuaHoff:
Does any one know how to swap internal sd to external like the Xposed Module "XinternalSD" does?
[Galaxy S III Mini Original Android Development] ChronoMonochrome:
@up, there is no a solution "out of the box", since android 6.0 was released. A well known way to swap internal <--> external sdcard is to use a kernel with a custom fstab ( changing the mount points like so will do: https://github.com/ChronoMonochrome..._kernel/blob/master/genfstab/fstab4_v2.0_swap - this will mount an external sdcard as /sdcard, the internal one as /storage/sdcard1 . Not sure if it works with the adoptable storage feature introduced in 6.0 (we were never using this feature).
[Galaxy S III Mini Original Android Development] New Macław:
New release with working all the tethers (thanks to [MENTION=5695278]ChronoMonochrome[/MENTION]) is here! Wifi connection stability is also much improved.

Get it right now:

http://novafusion.pl/
[Galaxy S III Mini Original Android Development] danilisilva7:
Wifi still disconnects when the screen is turned off.

Tethering is working correctly
[Galaxy S III Mini Original Android Development] ChronoMonochrome:
No-no, it's only thanks to SergeyL, I haven't actually done anything on the wifi part in 7.1.
[Galaxy S III Mini Original Android Development] +BOB+:
Hi, did you adjust wifi is always on on deep sleep at wifi settings?

---------- Post added at 15:38 ---------- Previous post was at 15:00 ----------

No problems with update, fast boot and it feels a bit snapier as bevore :good:

Made a dirty flash over previous version.
[Galaxy S III Mini Original Android Development] ente4:
Rooted??? No access to sd card.
[Galaxy S III Mini Original Android Development] b_henry:
Hi, is there any way to access the inbuilt root manager (not Magisk) to change or forget root permissions for apps? In developer options cannot be found anything about root...
[Galaxy S III Mini Original Android Development] danilisilva7:
I did complete cleaning and everything is working well, thank you.

Wifi continues disconnecting even after full wipe and installed via odin
[Galaxy S III Mini Original Android Development] +BOB+:
No problems here with access to sdcard and root.

---------- Post added at 23:12 ---------- Previous post was at 23:09 ----------

Open SuperSU app. You can find it at app drawer.
[Galaxy S III Mini Original Android Development] gh0stzk:
About that.. I thought that this was a general unsolved issue, but now i read, others dont have this issue.

With cm file manager i cant access my sd card, with root or without root, always a prompt said i need root acces to acces sd card.
[Galaxy S III Mini Original Android Development] b_henry:
So no other way than install a third party root manager... Thanks, I thought so.
[Galaxy S III Mini Original Android Development] hfm35:
Wifi not auto connect
[Galaxy S III Mini Original Android Development] +BOB+:
No, supersu app is included in the rom. You have just to use it.

Or am I wrong? Maybe I installed it bevore update, do not remember exactly.
[Galaxy S III Mini Original Android Development] ente4:
I installed SuperSu and Solid Explorer and now I have access to sd card. Thanks
[Galaxy S III Mini Original Android Development] b_henry:
In previous builds it definitely wasn't included. I'm now on LOS 14.1, so don't know if something was changed with the newest release.
[Galaxy S III Mini Original Android Development] vagelis74:
Any fix for the WiFi; it's the only problem of this gorgeous rom
[Galaxy S III Mini Original Android Development] gh0stzk:
Yes sr.. Is the only problem. At the moment
[Galaxy S III Mini Original Android Development] New Macław:
WIP, but maybe [MENTION=5695278]ChronoMonochrome[/MENTION] has any ideas also this time?
[Galaxy S III Mini Original Android Development] danilisilva7:
The wifi works correctly without gapps or microg, yesterday I did full wipe and only installed the system and the wifi worked correctly, I left downloading a big file at dawn and downloaded everything well, then I installed gapps and the wifi did not maintain the connection, I did wipe / System and I installed only rom and it worked well, I installed microg now and wifi does not keep the connection ...
[Galaxy S III Mini Original Android Development] ChronoMonochrome:
Yeah, I have some ideas regarding this issue, but neither I know what is the root cause of it, nor whether it's possible to fix not reliying on a hacks in the code. Since 6.0, it appeared that some changes regarding CLOCK_BOOTTIME was a reason for wifi autoconnection not working after the device enters deep sleep state. I have tried almost everything I could to bring this support in the kernel, but I'm still unsure what the proper solution would be and what I'm missing. The less "hackish" way in which wifi autoconnection was still working was commit https://github.com/UltimateROM/andr...mmit/426d5c5df0a2a156d4948c9178ba25a7bb2e300b (essentially, this increases a two intervals of time, mScanResultAutoJoinAge and mScanResultMaximumAge to the maximum integer value - maybe patching a condidtions in which these constants are used could bring more light into this issue? I have to admit, I was just blindly changing these values without figuring out how it actuall does work) . Unfortunately, wifi framework has changed a lot in 7.0, WifiAutoJoinController was now superseded in a favor of WifiQualifiedNetworkSelector class, the trick that worked before can't seem to be applied so easy as it was before. Now I remembered some of the more dirty changes I've attempted initially in 6.0 before the patch aforementioned:

1) https://github.com/ChronoMonochrome...2c113cc#diff-831775e87dd19c4714d172b65317328f and https://github.com/UltimateROM/android_system_core/commit/c5d2d57ca29e30aa4dde06dae808b14e2fcabb9a

This patchset allows switching between a different timekeeping methods provided in libutils via setting a property. According the comment left - https://github.com/ChronoMonochrome...13cc#diff-831775e87dd19c4714d172b65317328fR24 - METHOD_GETTIME seems to somehow eliminate this issue - but there a side effects though, like a clocks "freeze" in the statusbar, alarm clock not working and so on, so I had to choose another solution.

2) https://github.com/UltimateROM/android_system_core/commit/b56f3cf0025872d33acd87b2d225906fee9b8fad + https://github.com/UltimateROM/andr...mmit/b95ca03e3c77ba37ec77816bb3568301180a1f97 + https://github.com/ChronoMonochrome...3ffd8c4#diff-2cd3cb3bfd33e56ff7a39a2e20b0977d

This approach implements a new function elapsedRealtimeNanos1 that is callable from Java code and essentionally is the same METHOD_GETTIME provided by libutils via JNI-bindings. I don't remember if this patchset ever worked correctly, but this is probably first I'll check. It still can cause some unwanted side effects but it looks most promising.
[Galaxy S III Mini Original Android Development] cayrol92:
I tried to fully wipe and reflash two times. I have still some laggs with the quick settings bar and a lot of frame dropped in the UI. I can not receive files through BT.
[Galaxy S III Mini Original Android Development] Anonymous94:
After installing wifi signal is very weak, and sometimes my phone will not turn on after screen off but it only happens when i plug carger.

sorry for my english
[Galaxy S III Mini Original Android Development] fenerbuuh:
iam using zzmoove profile 4 and sio.

I really got no problems at all......but iam not using gapps or microg.

my wifi is perfect
[Galaxy S III Mini Original Android Development] greeceeeee:
Have you found xposed framework for nougat to get working xposed plugins?
[Galaxy S III Mini Original Android Development] New Macław:
It seems I was able to fix wifi auto connection with changing only two lines, based on your work of course.

Will test now its behaviour and battery usage and if I am right, will publish patch and release.

Thank you again for help, I hope I am right and finally I will be able to help you ;)