yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] Alex-71:
I tried about 130 test alarms after applying the kernel.zip and could not reproduce the issue so far.

But after that i found a 100 % way to produce a missed alarm. Just set two alarms at the same time, then one will be missed.

I don't know if this is a expected behaviour or somehow related to the bug. But it gave me the idea that maybe the amount of alarms could be the reason why some users are facing the issue and others not. I normally switch between 3 different alarms depending on the weekday (so i always have one active and two passive alarms).
[Galaxy S 4 Mini Original Android Development] turbare:
Did anyone else get a battery drain? Just dropped to 3%.
[Galaxy S 4 Mini Original Android Development] IronRoo:
No. (I have LTE ver)

Are you on latest nightly? Or are you talking about the above test kernel?
[Galaxy S 4 Mini Original Android Development] turbare:
Latest nightly, no kernel modifications, fully "stock" as you might call it.

3G version of the phone.
[Galaxy S 4 Mini Original Android Development] sej7278:
but i found that alarms set only a few minutes away never fail anyway (so 130 alarms a minute or so apart should all work). only ones set hours in the future - so the phone is well and truly asleep - seem to fail before the new kernel.

my alarm went off this morning again after being left from 4pm to 9am with the new kernel, so that's two mornings in a row its worked. seems the new kernel rather than the new deskclock2 is what has fixed it.

i never have more than one alarm set per day and not set to repeat.
[Galaxy S 4 Mini Original Android Development] arco68:
Someone mentioned having problems with automatic time zone. Could you test if flashing this fixes it?

http://www.mediafire.com/file/37v7sejbv92jcbh/telephony.zip
[Galaxy S 4 Mini Original Android Development] ghines:
Is anyone else having issues displaying the ROM changes on the Lineage Website? I've tried several browsers and it either displays a page of changes only or nothing at all.
[Galaxy S 4 Mini Original Android Development] JimmyRay:
Seems to be working fine here.
[Galaxy S 4 Mini Original Android Development] rellieberman:
I can confirm I first experienced this problem over two weeks ago. Some times no merges are displayed and some times it gets stuck trying to load more than the first few. I'm pretty sure it starded when gerrit was updated to a new vesion.
[Galaxy S 4 Mini Original Android Development] csendre:
I am one of them and actually I guess all of us but this seems to be country/provider dependent. When I travelled in Europe this summer it was working well wherever I went, when I am home in Canada (Rogers Wireless) or in the US, it is screwed up.

Unfortunately this fix didn't help, let me know if I can help with testing anything else.

Unrelated; tested the new GPS HAL which will come out in tomorrow's build and I am having difficulty getting a fix on Waze. Strangely, other GPS apps like iGO or GPS test don't have a problem with it.
[Galaxy S 4 Mini Original Android Development] IronRoo:
Edit: This is NOT WORKING now, worked for a bit, but now it's back to GMT. :confused:
[Galaxy S 4 Mini Original Android Development] echo124:
On of the best devices - thanks [MENTION=3044346]arco68[/MENTION]
[Galaxy S 4 Mini Original Android Development] JimmyRay:
Ooh...fullscreen mode (YouTube etc.) now working in Jelly!

I think that's the only thing I was missing.

Great little browser!
[Galaxy S 4 Mini Original Android Development] sej7278:
alarm worked again this morning with the tweaked kernel and deskclock2, that's 4 days in a row now
[Galaxy S 4 Mini Original Android Development] Kreacher01:
After a dirty upgrade from weekly 2017-07-21 to the current weekly 2017-07-28 I noticed one issue with the camera app Snap:

If the option to use the power button as shutter release is enabled, the app does not start. I had to to clear data of the app to get it working again. As soon as I try do enable this option again the app closes immediately (fc).

I assume that this is related to the move of Snap from priv-app to app.

Attached you'll find a logcat, it's a permission issue:

07-28 16:56:44.552 W/PackageManager( 603): Not granting permission android.permission.PREVENT_POWER_KEY to package org.cyanogenmod.snap (protectionLevel=18 flags=0x3858bc45)

...

07-28 16:57:50.987 E/MessageQueue-JNI( 2273): java.lang.SecurityException: No permission to prevent power key: Neither user 10026 nor current process has android.permission.PREVENT_POWER_KEY.

EDIT: Removed logcat because issue has been addressed, new changes to move Snap and Gallery back to priv-app are on the way.
[Galaxy S 4 Mini Original Android Development] MaGu1000:
After a upgrade from weekly 2017-07-21 to the current weekly 2017-07-28 I see a problem with the camera too.

I cannot select the SD-card to store pictures anymore und if I try to take a video on SD-card the camara crash.

Is there a workaround?
[Galaxy S 4 Mini Original Android Development] Kreacher01:
Same issue here. I can select SD card for storage for photos and for video but it did not work:

- I can take a photo and it's displayed in the circle shaped "preview" of the Snap internal gallery. But when I enter this gallery there are only grey rectangles. Lineage gallery app does not display the newly taken photos at all

- When I try to record a video (storage SD card) Snap crashes immediately.

07-28 18:38:56.213 E/AndroidRuntime(16910): FATAL EXCEPTION: main

07-28 18:38:56.213 E/AndroidRuntime(16910): Process: org.cyanogenmod.snap, PID: 16910

07-28 18:38:56.213 E/AndroidRuntime(16910): java.lang.RuntimeException: java.io.FileNotFoundException: /storage/DB9F-1615/DCIM/Camera/VID_20170728_183856.mp4: open failed: EACCES (Permission denied)

I assume this is related to this revert: https://review.lineageos.org/#/c/182101/

Gallery 2 was also moved from priv-app to app (https://review.lineageos.org/#/c/182102/)

I don't think that there's a workaround so I'll go back to weekly 2017-07-21. I took another logcat containing the above mentioned issues.

EDIT: There's already a change to fix the power button issue but this change has some drawbacks... (https://review.lineageos.org/#/c/182316/)

Signing snap with the platform key was merged by arco68 some time ago but was revoked later with another change.

Perhaps this fix will also fix the SD card storage issues.

EDIT2: Removed logcat because issue has been addressed, new changes to move Snap and Gallery back to priv-app are on the way.
[Galaxy S 4 Mini Original Android Development] arco68:
Yeah it seems it's mostly in the US there's issues with time zone. There's a patch they did in klte you might want to try. I tested it here, but it didn't quite work for me.

https://github.com/LineageOS/androi...mmit/a4fd5483522475cc18fb13e43e75c3ea93e9017b

About GPS and Waze, I did a quick test and got a fix just fine.
[Galaxy S 4 Mini Original Android Development] Kreacher01:
I got Snap to work at the 2017-07-28 weekly by moving the folder Snap (including snap.apk) from /system/app back to /system/priv-app via TWRP.
[Galaxy S 4 Mini Original Android Development] MJay99:
Yes, been seeing similar, on the website as well on a third party app trying to reflect these changes there.
[Galaxy S 4 Mini Original Android Development] csendre:
This was a great find, it actually works for me, been testing it for a few hours. Thank you!

I already kanged it for the AOKP repo. Will test on Lineage on 9195 as well and report back

https://github.com/AOKP/device_sams...mmit/c1cef36cd07415099bb105c884a79754cae04203

Update: Unfortunately something is still wrong; on my 9192 works great but on the 9195 the time does not auto update at all when I build with the same exact RIL. [MENTION=3044346]arco68[/MENTION] any idea?
[Galaxy S 4 Mini Original Android Development] echo124:
[MENTION=3044346]arco68[/MENTION] [MENTION=5416372]csendre[/MENTION] thanks for all your work! Shame there are no other devices like s4 mini size, with such great support for LOS.
[Galaxy S 4 Mini Original Android Development] JohnSoong:
I was having time zone problems as well. Like [MENTION=5416372]csendre[/MENTION], I am also in Canada (Virgin/Bell).

I flashed the file from [MENTION=3044346]arco68[/MENTION], and also wiped cache and Dalvik after. After rebooting, Time zone is now correct.

Before the flash, I tested by turning autotimezone off, and the time immediately reverted back to GMT 0. Now with the zip, the settings is reporting correct time zone (GMT -6 ) and I am getting the correct time.

Now, about a half dozen builds back, I did have correct auto time zone on boot, but that went back to GMT 0 after a few hours. So I am hoping this fix will stick.

Thanks [MENTION=3044346]arco68[/MENTION] for working on this!!

[MENTION=5416372]csendre[/MENTION] - Did you wipe cache after you flashed? Wonder if this is a Bell Rogers difference, or if I got lucky on the flashing procedure.

EDIT: Time zone reverted to GMT 0 after a couple hrs. Reboot with the Auto Timezone on and it seemed to have fixed it. .... hopefully for good!
[Galaxy S 4 Mini Original Android Development] csendre:
I tested it on a clean flash. Usually that is what I do to eliminate interferences from other stuff.
[Galaxy S 4 Mini Original Android Development] ghines:
Yep, I was having problems with the automatic time zone not working. Flashed your zip, rebooted, turned on automatic time zone. Timezone was still incorrect. Rebooted and all is good now. :) Thank you.
[Galaxy S 4 Mini Original Android Development] IronRoo:
it worked for me but after 30min-1hr it went back to GMT, as it did for [MENTION=7584536]JohnSoong[/MENTION], will be interesting to see if it sticks. (which model do you have?). But rebooting like you did might be the trick. (I've now flashed the latest update, so don't know if it would have worked)
[Galaxy S 4 Mini Original Android Development] sillet91:
Hello everyone! I'm facing some problems, I don't know why , but when I make a call sometimes the phone crashes, and then reboot for it self, this happend to me three times ago since the last update, does anyone else have this problem? Thanks
[Galaxy S 4 Mini Original Android Development] IronRoo:
Yes, a couple of days ago I received a call and as I put the phone to my ear it rebooted, 0721 build.
[Galaxy S 4 Mini Original Android Development] IronRoo:
The good news is that after flashing the latest build I went to date & time and set automatic time zone to on, it didn't change to GMT but kept the correct time, so I rebooted. The time is still correct now, 4hrs later, so hope it will stick.
[Galaxy S 4 Mini Original Android Development] JohnSoong:
Same here. Applied the zip, turned on auto time zone, all is well for ~2 hrs, reverted back to GMT 0. Rebooting seemed to fix the issue ... It seems you need to have auto time zone ON before rebooting for this to work. Fingers crossed that the fix will stick this time.

EDIT : reverted back to GMT 0 after about 4 hours ....
[Galaxy S 4 Mini Original Android Development] arco68:
That was the issue on my 9195 as well. I'll try to take a closer look at it.
[Galaxy S 4 Mini Original Android Development] csendre:
I don't understand.. tested a few more times even on AOKP, and works flawlessly on 9192 but stops auto update on 9195
[Galaxy S 4 Mini Original Android Development] arco68:
Try this one: https://github.com/LineageOS/androi...mmit/d64a951929bce6e6d694675122235edcdf7fa677

Seems to be working for me.
[Galaxy S 4 Mini Original Android Development] Chriss123456789:
How can I update my LOS on my GT-I9195 with Magisk to a newer nightly without data loss? I have tried to dirty flash it through TWRP 3.1.0 and all I get was a bootloop with data loss.
[Galaxy S 4 Mini Original Android Development] Diresh:
Maybe remove magisk first and then flash rom+gapps then reboot and then flash magisk
[Galaxy S 4 Mini Original Android Development] ghines:
Same here, i9195 worked for about an hour before returning to GMT time. Darn......
[Galaxy S 4 Mini Original Android Development] xalo.sher:
Hey,

I have an old GT-I9195 running on CM12.1 - I am interested in updateing to Lineage 14. HaS anyone done that before, because I'd like to know if there is a boost in performance or battery life. Or should I rather use CM13?

Thanks in advance ;)
[Galaxy S 4 Mini Original Android Development] csendre:
Yep, works here as well on the 9195. Will check on the 9192 too.

Update: Confirmed working on both 9192 and 9195. Amazing what two extra lines of code can do :) In my opinion it is good to merge into our RIL. Finally we have a working auto time zone. Thankf fot the find [MENTION=3044346]arco68[/MENTION]!
[Galaxy S 4 Mini Original Android Development] mario24601:
What if you manually adjust time and turn off auto time update?
[Galaxy S 4 Mini Original Android Development] IronRoo:
My time just reverted to GMT, pretty much as expected, lasted at least 24hrs though, not that it matters as we'll have the proper fix in the near future :)
[Galaxy S 4 Mini Original Android Development] JohnSoong:
I have ran both CM 13 & LOS 14/ 14.1 on the I9195. Without a doubt, both ROM ran faster than stock. (Getting rid of all the Samsung bloat did wonders.)

I think 14.1 gave me a bit better battery life. Performance wise it is a wash. There are a few issues with the LOS ( browse some of the posts to see the details, all relatively minor) which were not there with CM 13. However, you get much better security with 14 vs 13, as the last official CM 13 was last Nov, while we are up to July security update already. So I think it is worthwhile to stay on the latest Android.

I never tried CM 12 on this phone. But on my last phone, CM 13 beats CM 12 in all ways.
[Galaxy S 4 Mini Original Android Development] csendre:
[MENTION=5975519]IronRoo[/MENTION] the proper fix is the one to the RIL. This shouldn't be ROM dependent (unless the ROM is screwed up) it should work the same in all Lineage based ROMs as well as AOSP-CAF
[Galaxy S 4 Mini Original Android Development] IronRoo:
Yes that works fine, also in fact auto time from network works great, but automatically adjusting time zone does not.

( it would be nice to have auto time zone working for those of us that live near state/country borders that we cross often)

---------- Post added at 01:54 AM ---------- Previous post was at 01:45 AM ----------

Yes, thanks, I assumed that would be the case, just wanted to mention that mine was working somehow without the RIL fix in case it gave you or [MENTION=3044346]arco68[/MENTION] another clue as to what might have been happening on our device. Look forward to this small bug being fixed for all in future build with RIL fix. :victory:

---------- Post added at 02:04 AM ---------- Previous post was at 01:54 AM ----------

just seen your edit. I wonder if mine will still revert to GMT at some point, strange that the time tell revert to GMT seems to vary a lot. Well at least it probably won't matter as Arco now has the RIL fix, that seems to be sticking
[Galaxy S 4 Mini Original Android Development] ghines:
Sorry for the noob question, but how do I install this?
[Galaxy S 4 Mini Original Android Development] IronRoo:
You can't (well unless you are going to build your own rom). We'll have to wait until Arco implements it in one of his weekly updates.
[Galaxy S 4 Mini Original Android Development] cancunia:
Just got my s4 mini and thought I'd take a look at Android 7. Thanks for all the hard work on the ROM, thought that I'd best mention the Gapps link on the first post points to Gapps 6, which fails on install if you're using Android 7.
[Galaxy S 4 Mini Original Android Development] xalo.sher:
Thanks JohnSoong for the infos ;)
[Galaxy S 4 Mini Original Android Development] Childe89:
Since flashing last nightly 20170728 I have problem with Camera - photos I take won´t get saved on my SD card - if i check them through last taken images in camera It´s just grey picture, and in gallery they´re not present. If i change saving into internal memory, It works normal. Anobyody else? Or It´s my SD card gone faulty...
[Galaxy S 4 Mini Original Android Development] IronRoo:
Yes, seems to be a bug this build, same with mine, see posts on page 165 (with a work around)

Edit: bug fixed in 0804 nightly build.
[Galaxy S 4 Mini Original Android Development] echo124:
[MENTION=3044346]arco68[/MENTION] [MENTION=5416372]csendre[/MENTION] feature question - is there a LOS notification feature that can act as a notification led on phones with no notification led? A small dot in the corner of the screen? That would be very nice ;)
[Galaxy S 4 Mini Original Android Development] Flyser:
BLN would be nice.
[Galaxy S 4 Mini Original Android Development] csendre:
Yes. We have BLN
[Galaxy S 4 Mini Original Android Development] echo124:
Is bln ambient display? Is there a way to just have a dot light up from time to time?
[Galaxy S 4 Mini Original Android Development] imarsh72:
NoLed from the play store can do that , have tried it myself but much prefer BLN
[Galaxy S 4 Mini Original Android Development] csendre:
No it has nothing to do with ambient display. It is a feature added by arco long ago, it uses the hw button lights as notification..

You can make it work by creating a script to enable it in data/local called userinit.sh with the following text

echo 1 > /sys/class/misc/backlightnotification/enabled

This will make the lights turn on solid. If you want blinking, you can use this script, works for me: https://github.com/loomy/androidstuf...er/userinit.sh
[Galaxy S 4 Mini Original Android Development] echo124:
Wow! Amazing! It use led light in the buttons!? That's very cool! Will try it soon, also github link broken? Thank you!!
[Galaxy S 4 Mini Original Android Development] csendre:
Here: https://github.com/loomy/androidstuff/blob/master/userinit.sh

This is not mine, I just came across it searching and been using it for a long time.
[Galaxy S 4 Mini Original Android Development] Alex-71:
Not here. I had many broken alarms while testing with short-term settings (but less often after change 172638 was merged). And at least one after the installation of deskclock2.zip.. So after 130 test-alarms without any issues i am cautiously optimistic that the kernel patch finally did it. Though i have no idea what number would be enough for arco to be absolutely sure.

Hm, bln doesn't work for me. I tried the simple script first and then the "blinking" one. I also applied chmod 755. Is there anything else to consider?
[Galaxy S 4 Mini Original Android Development] csendre:
Not sure why, I saw others reporting this as well, but for me it always worked (except for a short period when LOS had a sepolicy issue) You can try chmod a+x with adb or terminal and of course you have to reboot
[Galaxy S 4 Mini Original Android Development] ghines:
But BLN won't work unless you do the following:

You have to disable "Ambient Display" in settings->display to get calendar notifications and messages to work with BLN.

Every time you restart your phone you have to enable Do not disturb and then deactivate it to get BLN working with missed calls.
[Galaxy S 4 Mini Original Android Development] echo124:
Set permission to 755, rebooted o latest nightly, disabled ambient display - didnt work. Does it work on last builds of cm/los13?
[Galaxy S 4 Mini Original Android Development] Shmaic:
GOOD ROM

OK PPL. So after one month testing I must admit that this ROM is F*g Good. Initial lags were due to the rom settling down. Also I cannot expect fast internal memory from 5 years old phone. But after one month usage with 70 apps installed and ~400 hours uptime without the need of rebooting I'm saying this ROM made S4 Mini alive again. Good ROM, Good Phone.
[Galaxy S 4 Mini Original Android Development] christiangre28:
I can't use the Google camera app properly. I can use it pretty ok with the version included in the gapps but not any newer version .Is that happening only to me or there is a way to fix it?
[Galaxy S 4 Mini Original Android Development] csendre:
Did you try chmod a+x? That sets it to be executable. Did not use 13 in ages but it used to work. It definitely should work on latest 14.1
[Galaxy S 4 Mini Original Android Development] echo124:
Sry not aware how to perform this
[Galaxy S 4 Mini Original Android Development] csendre:
If you are using adb you can run: "adb shell chmod a+x /data/local/userinit.sh" or from terminal just simply run "chmod a+x /data/local/userinit.sh" but get root access first
[Galaxy S 4 Mini Original Android Development] IronRoo:
I don't use Google camera but I think it is a known issue, you have to flash with Gapps (on all phones/rom).

Edit: see section 7

https://github.com/opengapps/opengapps/wiki/FAQ

edit: actually reading it, maybe only applies to "first install", but might fix your problem anyhow doing a clean install ;)
[Galaxy S 4 Mini Original Android Development] piojan:
VoWiFi

Hi,

My network operator supports native VoWiFi (Wifi calling) and I have enable it on there side.

I have somewhere found that out phones might also support it...?

After adding this to build.prop:

persist.dbg.wfc_avail_ovr=1

there is an option with Wifi Calling preference. However the calls are not routed over WiFi.

Anyone knows more if VoWifFi might work on out S4 mini'es?
[Galaxy S 4 Mini Original Android Development] echo124:
Thanks very much xD! It worked! But the blinking one does not - for blinking one, all is the same as for non-blinking except script inside usereinit.sh - put it from that github page, rebooted, same perm as nonblinking. :?
[Galaxy S 4 Mini Original Android Development] csendre:
Yes, it should be the same, just copy and paste into the usernit.sh file. But don't use both in the same file. Either the single liner to enable solid lights or the script for blinking
[Galaxy S 4 Mini Original Android Development] mario24601:
So it is possible to use hardware buttons as led notification?

Thats awesome if true!
[Galaxy S 4 Mini Original Android Development] ZeroPointMax:
sorry for being off for so long. Anyways, it was a missing string in the setup, the setting was automatic disc-cleanup.
[Galaxy S 4 Mini Original Android Development] dav1129:
new to lineage OS

so I had been using CM 12.1 quite happily until today but decided to install latest build Lineage 14.1 to see what difference there might be. still early days for me but first thing I see is missing is cast screen from drawer and as before, how to configure which icons appear? am I going to be disappointed?

EDIT: in hindsight I remember that I saw some red lines E: unknown command [log] (twice) so thought the ZIP file didn't download properly. so I decided to to download it and install again. the tow most recent files failed some md5? check. So I tried the third most recent and got the same E: unknown command [log] error twice. I went ahead to install GApps and will see.

But still keen to hear whether built in cast screen is missing from Lineage.....
[Galaxy S 4 Mini Original Android Development] utfluc:
You have an outdated recovery
[Galaxy S 4 Mini Original Android Development] dav1129:
What so you mean outdated what? Outdated version of TWRP or Lineage?

The version of TWRP I am using is 3.0.2-1

Which the correct and most recent version of TWRP for i9192 variant and which is the most recent version of lineage OS I should be installing?
[Galaxy S 4 Mini Original Android Development] utfluc:
Sorry, I wasn't clear enough. I was referring to the log command error, that's related to an outdated TWRP, you can find version 3.1.x in the official TWRP web site.
[Galaxy S 4 Mini Original Android Development] dav1129:
I found it but doesn't it have to be a specific version for i9192 variant? The specific version I found for i9192 was 3.0.2-1 . Can I use any version of 3.1.1?
[Galaxy S 4 Mini Original Android Development] utfluc:
I'm not sure about i9192, I have the i9190 variant, sorry. Nevertheless it's just a warning error, it doesn't stop you from updating the ROM.
[Galaxy S 4 Mini Original Android Development] dav1129:
thanks. yes. I eventually got it installed and its all very new.

can you comment on whether cast screen is included in lineage OS? It was in Cyanogenmod 12.1 at least and easily acceptable from the top status bar...