yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Android Development] Tom Mix:
wayne...

[MENTION=276902]whoever[/MENTION]

so the md5 is back and the build is gone...

build/core/product_config.mk:245: *** Can not locate config makefile for product "aokp_serranoltexx". Stop.

http://xfer.aokp.co/get.php?p=AOKP/...ranoltexx_nougat_nightly_2018-03-28_build.log

is it a farewell :confused:
[Galaxy S 4 Mini Android Development] csendre:
Nougat builds are moving to a weekly schedule now. Also, there were some other changes to the build script and servers, maybe this is why builds disappeared for a while. Just checked, last two builds are up there now. From now, only the last two successful builds will be available to save space
[Galaxy S 4 Mini Android Development] quietlaugh:
Hello Csendre,

I could find the oreo topic from Arco68 but will there be regular updates as well? Your build are the latest but have you started a topic I have missed?

Still having the issue with your oreo builts that the initial setup does not start and I cannot sync my google account on my phone afterwards... Bit odd but I am still trying things :)

(could it be because I am mounting my adopted sdcard by copying the key into the mis/vold folder and the card was adopted by nougat?)

Thanks
[Galaxy S 4 Mini Android Development] der_Kief:
is this ROM still maintained ?

I ask because i want to know if latest security updates (March and April) will be integrated.

Hopefully this will be done ....
[Galaxy S 4 Mini Android Development] csendre:
Did you read my post on this same page???
[Galaxy S 4 Mini Android Development] der_Kief:
i read it but i sucessfully supressed it :) sorry for that

Hopefully security updates will merged soon .....
[Galaxy S 4 Mini Android Development] csendre:
I saw a ton of nougat stuff merged around noon today, including March security patches. You can always follow gerrit, link in the OP.

People focus more on Oreo these days so nougat is slower
[Galaxy S 4 Mini Android Development] Tom Mix:
strange... md5

[MENTION=575448]Board[/MENTION]

is it only stupid me, or are the md5 gone again:confused:
[Galaxy S 4 Mini Android Development] o0chtm0o:
I don't understand why server builds for serrano3gxx, serranodsdd and not for serranoltexx the same day... Today for example
[Galaxy S 4 Mini Android Development] Tom Mix:
still no md5

[MENTION=219647]wayne[/MENTION]

still no md5 on aokp x-fer ;)
[Galaxy S 4 Mini Android Development] csendre:
Build order got shoveled up a little after the server rebuild. You are getting a fresher build, what's the problem? :D

There are some issues with the script, sometimes it works, sometimes not so well. Will be looked at
[Galaxy S 4 Mini Android Development] Tom Mix:
security flaw: AOKP related?

hello world

i have found an, severe security flaw comparing CM11 vs. AOKP N

to reproduce do the following:

enable the option 'scramble layout' on lockscreen

once enabled the numbers layout is scrambled

for PiN-input to unlock.

now the flaw:

on my CM11 ROM the layout is scrambled every time i

turn on my display. (maybe just to check the time)

on AOKP the layout is not scrambled until the device is unlocked! :eek:

so it is very easy to an 'interested' person to turn on my device

i have left on the desk, to capture the actual layout and peek

on my unlock pattern while i am entering the pin, et voila!

the goal of the function: scramble the layout is meaningless now!

is silly me the only concerned :rolleyes:

or did i miss an option.

[MENTION=5416372]csendre[/MENTION]

thx for the reply, i hope the script gets well soon :fingers-crossed:
[Galaxy S 4 Mini Android Development] Tom Mix:
hm...

:confused:

:(

:crying:

:crying:

:crying:
[Galaxy S 4 Mini Android Development] blumentopf75:
Newer versions of Signal Messenger crash

Hello,

Im using this ROM for 1 week, and I'm ver satified with it. Thank you.

But there is one issue with the Signal messenger.

I restored the Signal-backup from my former ROM installation (was XenonHD).

Restoring only works up to Signal version 4.17.5, alls later version chrash after restoring the backup und crash immediately after restart. When I upgrade to newer versions after restoring with 4.17.5, the newer app crashes on start too.

So I asked to Signal support, but they sayed, the problem belongs to an LinageOS issue, where AKOP is based on (as I understand it). It is not in theyr hands. The LOS issue is the following:

Are you using LineageOS? If you are then it sounds like you are coming across a pretty severe LineageOS bug and it is out of our control. You can raise the issue with them to ask them to prioritize fixing this: https://review.lineageos.org/#/c/208870/
​

I can't deal with the information on the linked website, sorry

So could you say me, if this LOS issue is related to our AKOP ROM?

And will there be a fix sometime?

So long, i will stay on Signal 4.17.5.

Thank you again, never had a ROM what works so reliably and flawlessly.

Wolfgang
[Galaxy S 4 Mini Android Development] FragDetector:
Good evening! I have this situation. When calling a video in WhatsApp on any 7.1.2 firmware such a screen. It happens normally, but in most cases I see just such an image. What could be the problem? Help me please.

If something is not correctly written, do not judge strictly, I am from Russia. In English, not about, the translator helped)

Screenshot:

I could not upload the image here, the above link to the screenshot.
[Galaxy S 4 Mini Android Development] blumentopf75:
Ok every thing is fine now, finally it was an signal bug which is fixed in signal 4.20.6 .

So if you deal with using signal, use this version.

So far, thanks for this Rom again

Wolfgang

---------- Post added at 08:29 AM ---------- Previous post was at 08:18 AM ----------

One question:

is it normal, that I can access some dirs and files with one file manager, but I cant with another one?

What could be the reason?

They both dont run as root (as far as I know)

One is the standard file manager of this ROM, the other one is GhostCommander.

Also some Apps cant read and write to some Dirs on internal and external volume.

I compared the access-rights and ownership of them at the commandline, and they art completely equal.

Ok, thank you, Wolfgang
[Galaxy S 4 Mini Android Development] Derek.rus:
Why not update the security patches of Android!?In buildprop is from 5.03.2018(March)!Or are there any serious problems?

https://yadi.sk/i/M-bE6i3b3XtTkT
[Galaxy S 4 Mini Android Development] pedro311:
Yeap, something not right here... :(
[Galaxy S 4 Mini Android Development] csendre:
Will look into it later this week

Update: I updated all nougat repos and commits should be merged soon. Next builds will be fully up to date
[Galaxy S 4 Mini Android Development] csendre:
I saw your PM as well, unfortunately I have no clue why is this happening. Last time I checked, all was working fine for me. Does anyone else have this issue?
[Galaxy S 4 Mini Android Development] mosquera25:
Recomendacion

disculpen quisiera informacion si es recomendable instalar esta rom, tengo el modelo s4 mini i9192 y actualmente tengo android 6.0.1 .. espero respuesta.. de antemano se que sus rom son muy buenas
[Galaxy S 4 Mini Android Development] coldgin_:
delete
[Galaxy S 4 Mini Android Development] Tom Mix:
hello world

any news on the scrambled layout issue?
[Galaxy S 4 Mini Android Development] kevinarol:
Will this ROM stop support for S4 mini lineup too? Due to recent comment from Arco68.

I hope AOKP team can brings us Security Month patches at least for the rest of the year ?
[Galaxy S 4 Mini Android Development] blumentopf75:
Why can't I create files in external SDCard?

Hello,

after working while with this ROM, I experienced one problem, what I don't understand:

Some Apps can't create or edit files on the external SDCard.

I formatted the card as removable (mobile) memory (not internal), but also tried to format on desktop PC with ext4-fs.

But I have the same result: I can put files on it via USB from PC an delete them, but some Apps (for instance Ghost Commander) cant create files or dirs there.

But they can read them.

TrekBuddy (a Geochaching App) says permission denied from java framework.

What's the reason and can I go over it with some workaround.

On internal memory I don't experience such problems.

Anything else seems to work fine with this ROM, I love it very much, Thank you.

Greets from Saxonia, blumentopf75
[Galaxy S 4 Mini Android Development] csendre:
Merged July security patches into AOKP sources, next set of builds will include them.
[Galaxy S 4 Mini Android Development] pedro311:
Great, thank you!
[Galaxy S 4 Mini Android Development] cobra-dk:
Hi guys,

I have just switched to AOKP from LineageOS 14.1 and the main difference I see is all the customization possibilities on this rom which is nice.

However, I can't seem to find the quick tile for changing to another system profile. Am I blind or is it just not there for some reason?
[Galaxy S 4 Mini Android Development] Tom Mix:
chosen one

[MENTION=837109]world[/MENTION] no one is using this security related feature anmymore or never had? this is more than ...
[Galaxy S 4 Mini Android Development] serranolte:
Microphone volume very low

Hello,

the microphone volume is very low for me.

Does anybody else have this issue or knows how to fix it?

I think it is ROM related.
[Galaxy S 4 Mini Android Development] cobra-dk:
Hi guys,

How do you enable the quick tile for changing to another system profile?

I just cant find it anywhere, maybe it's hidden somewhere in the many settings on this rom?

Anybody?

Anybody?
[Galaxy S 4 Mini Android Development] Arslan140:
There is no quick tile for system profile.

Instead of that you can manually go into settings>Setting Profiles.
[Galaxy S 4 Mini Android Development] cobra-dk:
Oh, bummer :(

Well, back to crDroid then I guess.

Thanks for getting back to me anyway!
[Galaxy S 4 Mini Android Development] csendre:
Just added it to sources, should be there from next build
[Galaxy S 4 Mini Android Development] cobra-dk:
Hi csendre!

Oh that is super good news!

Looking forward to that. Thanks!
[Galaxy S 4 Mini Android Development] csendre:
Just updated nougat sources this morning so the LTE build scheduled for today will be fully up to date and August security patches.

Unfortunately the builds from 08/23 for the 3G & DS completed before the updates, however, I asked for these builds to be restarted. Hope to have an up to date build for these soon.
[Galaxy S 4 Mini Android Development] lebvlad:
Can somebody tell me something about AOKP recovery.img?

I want to try it, but i can't find any installation instructions. I tried to install it via Fastboot but stuck (Fastboot say it can't find my phone :eek:)

Is it better for my i9195 than TWRP?

Thank you for any information. :highfive:

P.S. One more question. (Im new to AOKP ROMs). Is there any ota updater for this ROM? I had Lineage OS 14.1 before AOKP and there was built in OTA updater. Is there something simillar in AOKP ROM?
[Galaxy S 4 Mini Android Development] csendre:
Don't use the recovery, it is a slightly modified version of the lineage recovery, not good. Stay with TWRP

No OTA update, it was discussed and will not be added. No point really since there are no modular updates and you have to download the full ROM anyway. I never saw the purpose of it in Lineage either.
[Galaxy S 4 Mini Android Development] lebvlad:
Thank you. Yes the full OTA support is not necessary I agree, but small pop-up "You have new update" like in Lineage OS could be very helpful. I thought it built-in Lineage OS function, and if I understood right AOKP based on it, that's why I asked.
[Galaxy S 4 Mini Android Development] toejam119:
Today I finally moved from LineageOS 14.1 to AOKP ROM Nougat and everything seems to be working great, except every time I boot up and get to the lockscreen I get the following error

It only appears for a few seconds and during/after I enter PIN then it disappears after about 2 seconds since the phone finds a network. It also makes a 1-2 second appearance whenever I go from 3G to 2G only. So it's only an annoyance. I tried switching radio bands in the "phone info" menu between "Automatic", "Europe" and "Automatic" but had no effect. APN settings are correct (same as before). I did not have this error message when in LineageOS 14.1. The "Telia FI" is the correct network which I use. Also when I go to the Mobile network settings -> Network operators, there reads "No networks found" though during this time it is connected to my network and it works fine. I have "Choose automatically" selected. When I manually search networks it finds three different ISPs and when I select Telia FI it again says "No networks found" (though it works fine), not sure if this is normal or not.

It feels like the phone is too eager to show the error, like it should wait a little more with no connection before showing the message (timeout set too low or something).

Is this something others have too, or am I the only one?

Phone: serranoltexx

ROM: aokp_serranoltexx_nougat_nightly_2018-08-24_ota (tried with aokp_serranoltexx_nougat_nightly_2018-08-17_ota also but no effect)

I made a clean flash, I wiped Dalvik, System, Data, Internal Storage, Cache. Also flashed open_gapps-arm-7.1-nano-20180824

Edit/solution: I did a full shut down (not just full restart) and the error message does not come anymore.
[Galaxy S 4 Mini Android Development] rozjerik:
ROM Control connections google servers

Hello

My old serranoltexx runs very well with aokp, thanks a lot for the great job.

But I have a question for users or developers: every time I connect my device in lte or wifi, I see via netstat that ROM Control (native) connects to 172.217.22.131:80 & 172.217.22.132:443 ( whois google) and listen on port 68, ok. The sending of statistics is disabled, and updates are downloaded manually, I do not have google play.

I do not remember having this type of connection on other rom, so if someone can explain to me the interest of connections to google, it will reassure me a lot.

Thank you very much in advance and sorry for my bad english.
[Galaxy S 4 Mini Android Development] csendre:
Good catch :) That is a one time ping and it connects back to AOKP for first time installation statistics. Check this out: http://stats.aokp.co Lineage also has this, we just changed the server address so that feedback comes to us.
[Galaxy S 4 Mini Android Development] fassal:
Can someone tell me whether full encryption is working with this ROM? Thanks!
[Galaxy S 4 Mini Android Development] pedro311:
Yeap, it's working good.
[Galaxy S 4 Mini Android Development] fassal:
Which TWRP Version should I use? The one from the OP (first page) or the general one for serranoltexx?

Can I update AOKP just by flashing it while using encryption?

Thank you!
[Galaxy S 4 Mini Android Development] toejam119:
I used the TWRP serranoltexx 3.2.3-0 (2018-07-31) from twrp.me with aokp_serranoltexx_nougat_nightly_2018-08-24_ota, and it worked fine.
[Galaxy S 4 Mini Android Development] fassal:
BIG THANKS to csendre and AOKP. I am just testing this ROM to use it as a daily driver and so far I really like it and those unicorn extras come in handy. Thanks!
[Galaxy S 4 Mini Android Development] mario24601:
First time trying AOKP, might be dumb question but is AOKP considered safe? As safe as let's say LOS? Just don't want my phone and data compromised. Thanks.
[Galaxy S 4 Mini Android Development] serranolte:
[MENTION=3044346]arco68[/MENTION] can you possibly help here?

This seems to be an issue with many other phones too when they run on alternative Android mods, and apparently is related to some identifier numbers for the microphones being assigned wrongly in some audio mixer XML files.

It happens when recording a voice message using the handsfree position or mode.
[Galaxy S 4 Mini Android Development] iphuang:
Disappeared APP Sidebar

My phone is S4 mini 3g, running the 2018-9-6 AOKP build. Everything works well but I noticed a strange event. Sometimes the back button (hard button) stops working. And the App sidebar does not work. Restarting the phone restores the functions. How do they happen?
[Galaxy S 4 Mini Android Development] adf7798:
Hi, I've the latest build, and I want to know if it's normal that when a notification arrives with ambient display enabled the brightness is at the minimum level. So, no problem during the night, but during the day it's impossible to see the notification. If I override default settings of ambient display, I only can set a "static" level of brightness, and there's not an option to set it at the level of the phone brightness. So is there a way to do this? On lineage ambient display behaviour is that one
[Galaxy S 4 Mini Android Development] HumbaBumba:
Lockscreenproblem with AOKP-Rom!

First many thanks for your fantastic work! But i have to report a problem with the AOKP-Rom and only with this Rom. I'm using a serranoltexx as replacement for other smartphones (another S4mini with LineageOS 16.0, a LG G4 with LineageOS 15.1 (all with latest possible builds, TWRP and Magisk) and a Motorola Moto G6 with standard Android 8.0 (no TWRP, no Magisk, no open bootloader)). When my AOKP-S4 (serranoltexx) is unused for about one day and i will start with the home-button i can see a blue window with time and date in it and i can do nothing to start. All fingertips are useless. I have to start the smartphone with the powerbutton, then i can work perfectly normal. Because i am very happy with your ROM-Control and its options i hope you can help me to solve this problem! I am writing from Austria and in my opinion my English is not the best! Many thanks once more!
[Galaxy S 4 Mini Android Development] toejam119:
Do you mean the issue shown in the photo below?

This happens when you have Flip Cover enabled (= default) in settings and you move a magnet near the screen, then sometimes LineageOS gets stuck in it thinking you have a flip cover on even when you do not. You can get it off by swiping a magnet again on the screen or just get rid of the problem by disabling Flip Cover from option assuming you don't need the setting.

This happened with me when I carried two phone cases on top of each other at work and the other had a magnetic cover on it, when I sometimes moved my S4 Mini away from it, it would get stuck in this.
[Galaxy S 4 Mini Android Development] HumbaBumba:
Hi toejam119, many thanks!

I think you have rescued my AOKP-ROM from beeing killed! I've disabled the FlipCover-Setting and I'm shure you gave me the right instruction. Thank you for your quick help!
[Galaxy S 4 Mini Android Development] fassal:
Encryption related questions and volume keys wake not working

Hi. I have some small questions.

1) How can I set a different displaylock and boot password (encryption is enabled)? Answer:

vdc cryptfs changepw password 'current-password' 'new-password'

2) I remember (maybe in an older build) to be able to set maximum false password attempts with an option to reboot the phone after too many. Am I confounding something or was this

removed? I can't find it anymore. Answer:

For example use app Wrong PIN Shutdown

3) Wake by volume keys seems not to work for me, any suggestions? I have all other uses disabled, but only Home and Power Button wakes?

4) Does the kernel has an option to disable IPv6? Always when I reenable wlan0 commands like "echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6" or "echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6" get reset. Any suggestions? Answer:

For example use Xposed module Disable IPv6 by timjosten

Thank you!
[Galaxy S 4 Mini Android Development] fassal:
I put some scripts in init.d and also added a userinit.sh script in /data/local/ with all files and created folders permissions set to 0755 and User/Group Root. However, changes are not applied during boot. Any ideas?
[Galaxy S 4 Mini Android Development] csendre:
Just merged security patches into sources; next build will be Oct 5 patch level
[Galaxy S 4 Mini Android Development] iphuang:
QR code function of native camera

Well, I searched the thread and no one was taking about the QR scanning function of native camera.

The camera included in this ROM can be switched to QR scanner mode. I am happy to discover that.

However, it does not work. I feel sad.:(

3rd party QR scanner app works fine. But what is wrong with the included QR function in native camera?:eek:
[Galaxy S 4 Mini Android Development] Philipp_:
This weeks built apparently didn't work for the DS variant:

build/core/product_config.mk:250: *** _nic.PRODUCTS.[[device/samsung/serranodsdd/aokp.mk]]: "vendor/samsung/serrano-common/serrano-common-vendor.mk" does not exist. Stop.
[0;31m#### make failed to build some targets (1 seconds) ####[00m
[Galaxy S 4 Mini Android Development] csendre:
I'll look into it, however, nougat sorces were not updated in quite some time anyhow. Actually I am thinking to stop official nougat builds all together
[Galaxy S 4 Mini Android Development] toejam119:
Will you continue unofficial builds? Because yours is the only one with BLN support that still gets security updates.
[Galaxy S 4 Mini Android Development] Philipp_:
I really liked the builts on xfer and they get about 300 downloads each week. However, if you stop them, the builts were great and I had a lot of fun with them. So thank you very much!
[Galaxy S 4 Mini Android Development] csendre:
Problem is that nobody in the AOKP team is updating the nougat sources (with security patches, etc.) so I was doing it every month or so (others are busy with pie). The reason I am considering stopping the builds is that I have less and less time to update nougat sources. At the same time Arne had zero time to update device sources for nougat (which is why he dropped the official LOS builds) so basically even though you have a new build every single week, not much is changed in them so what is the point?

I'll try to update nougat sources once more and for the time being will leave the builds going, but not sure for how long. I am hoping to make official pie builds at some point (no BLN though) in the future but this will be heavily dependent on Arne as well as if he does not update selinux for pie, this will not be possible (and that is very time consuming so not sure what his plans are).

Update: the nougat build error was due to a change in the way github works. Fixed now
[Galaxy S 4 Mini Android Development] csendre:
Just updated nougat sources, commits should be merged soon. In theory next official builds should have February security patch level
[Galaxy S 4 Mini Android Development] toejam119:
This is excellent news. One last huff of air to the life of S4 Mini with BLN.

However, if they do not implement BLN in LineageOS Android 9 then I'm afraid I'll have to switch phones. So far the only modern Android phone, that I know, with notification LED and under 5" screen is Sony Xperia XZ1 Compact (released 2017), luckily there are people making unofficial LineageOS for it.
[Galaxy S 4 Mini Android Development] adf7798:
Hi guys, I've tried this ROM 2-3 months ago, then I changed to LOS 15.1 by arco, but now I want to re-try this ROM because I think Nougat is more stable than oreo. So, in these 2-3 months, what were the main changes/improvements? And looking to download site, I'm a bit confused: there's the last build that has a older date than the second one (sreenshot below), so what is the "true" latest build? And the most stable?

Thanks
[Galaxy S 4 Mini Android Development] csendre:
Go by the date in the file name. Maybe they moved things around on the server and this is why "last modified" date is different

For a very long time there are no more changes just security updates. ROM reached final development stage
[Galaxy S 4 Mini Android Development] Philipp_:
Csendre, thank you very much for revivifying this ROM for the time being!
[Galaxy S 4 Mini Android Development] kurtn:
Hey what's that thing with aokp recovery? Should I try? What's the difference to twrp?
[Galaxy S 4 Mini Android Development] csendre:
It is a branded and modded CM recovery. Stick with TWRP
[Galaxy S 4 Mini Android Development] zorzibaffo:
Thank you very much for this rom. My device gets a new life.