yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 4 Unified Development] x2k13:
Why don't you just setup 5GHz wifi on your phone, as in: Don't enter the password for 2,4 GHz wifi? That way it doesn't connect to 2,4, just 5.
[Samsung Galaxy S 4 Unified Development] xperanto:
The S4 is somehow picky about wlan. For example, i have a raspberry as an accesspoint. Using the internal wlan of it with the right regioncodesettings everything is fine.

Using a specific external usb-wlan-stick with the right settings, i get random disconnections with the s4, while other phones/clients don`t have any issues.

I think (assume) that i get the disconnections, while the s4 is scanning for other networks.

Try to reduce "wifi scan throttling" under settings -> developer options (you have to enable them) by enabling it.

Also make sure that your wlan-accesspoint uses channels are used "internationally", see wlan channel list , i.e. channels 1 to 11 for 2,4ghz and for 5ghz see link.

Maybe it helps. I have encountered the same behaviour with a wifi-stick, where the regioncode was hardcoded in firmware, which differed from the systemsettings of the OS.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
please provider the way to that setting *on* the phone (to connect to 5GHz only).

obviously - or as I understand it - the OP does/makes "roaming" (same SSID for both wifi bands, one password) and want to stay with that to prevent to change the wifi settings on all his other devices

one way to bind the phone to one wifi band only in such roaming environment would be to connect with the specific MAC of the router's 5 GHz Band only.

How ?

Don't know !

anyway, that doesn't come without cost's: phone wifi in other (outdoor) environments ?

slightly remembering I've seen such MAC binding somewhere ...
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
well, you provided a nice description that one always should read "S4 is bad about wifi" as "S4 is bad about wifi *in* my/that specific wifi environment" and that (some) wifi chip vendor's cook their own soup.
[Samsung Galaxy S 4 Unified Development] npjohnson:
This is the stock recovery, not lineage recovery, you booted stock after flashing recovery before booting into recovery ;p

Yeah, formatting via TWRP is unsupported, another guy pushed a fix for it, I merged it, so TWRP builds should work now.

Yeah, formatting via TWRP is unsupported, another guy pushed a fix for it, I merged it, so TWRP builds should work now.

Yeah, formatting via TWRP is unsupported, another guy pushed a fix for it, I merged it, so TWRP builds should work now.

Yeah, formatting via TWRP is unsupported, another guy pushed a fix for it, I merged it, so TWRP builds should work now. you nailed the reason btw, twrp now reserves that space for encryption metadata after two days ago's build (:
[Samsung Galaxy S 4 Unified Development] 0xfab1:
Hi again

There was recently a good discussion on this question in an XDA thread for another Samsung device.

My conclusion to the whole thing: Without "dirty tricks" in the router configuration you can't get 5 GHz-only and for me it wouldn't be a real solution either, because it wouldn't work in places where you are not connected to your own Wi-Fi network. With the settings options available in the OS these days, I don't think it's possible to do frequency band selection on an Android device - unfortunately, the "Prefer 5GHz" option has been removed from Android.

To answer your question: There are some few apps in the Play Store that promise to let you choose your preferred frequency band - might be worth a try :)
[Samsung Galaxy S 4 Unified Development] x2k13:
I just can say how I configured it on my OpenWRT router at home.

Two seperate network Interfaces, one is serving 2,4 GHz - WLAN0, the other one 5 GHz - WLAN1. Both use the same password, but they are seen by the phone as two different wifi SSIDs.

Now, if you just connect to the 5 GHz SSID - WLAN1, you never connect to 2,4 because your phone doesn't know anything about WLAN0.
[Samsung Galaxy S 4 Unified Development] droi1:
thanks to all of you information's about Wifi it motivated me to look into my Router Settings once again ;). I think its fixed for now i disabled Band Steering in my Router Settings! Funny enough claims to make Wifi better and stable:ROFLMAO: well with most of my newer Devices it was no problem but with older ones. So now my Devices choose when they need change 2,4ghz/5ghz and not my Router (y)
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
sounds like a Fritzbox....

are you aware of this forum:

AVM

www.ip-phone-forum.de
[Samsung Galaxy S 4 Unified Development] droi1:
Yes its a Fritzbox, i know that forum. ;)
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
I know such an config.

the disadvantage is when you move out of the range of the 5 Ghz, it leads to no wifi.

while 2.4 would be still visible/connectable at that distance.
[Samsung Galaxy S 4 Unified Development] x2k13:
That's true, but that's what you wanted, isn't it?
[Samsung Galaxy S 4 Unified Development] karlico:
Yeah. you are right🙃
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
No !

please read again what the OP's problem was and what he doesn't (didn't ?) want to do.

and what I wrote in #146
[Samsung Galaxy S 4 Unified Development] Savatage76:
hello! sometime stock music player jump from a point To another in the same track, about 3 or 4 seconds forward. anyone have the same ? with prevoius ROM it doesn't happen
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
no, not here.

music/movie are playing fine
[Samsung Galaxy S 4 Unified Development] Ally Wilke:
Newb here.I have a rooted S4 spl720.Do I have to unroot or do anything else before installing LOS?Thx.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
AFAIK, no.

I'm currently not sure regarding current LOS release, but elder LOS/Cyanogen had root per default (flash)
[Samsung Galaxy S 4 Unified Development] kurtn:
That was not the question
[Samsung Galaxy S 4 Unified Development] kurtn:
Only thing you really need is a custom recovery. If rooted, you can install it with twrp app.
[Samsung Galaxy S 4 Unified Development] rw_on_xda:
no ?!

just don't overread what comes after my "AFAIK"

okay, today is sunday ...:cool:
[Samsung Galaxy S 4 Unified Development] Ally Wilke:
Thank you for the replys.
[Samsung Galaxy S 4 Unified Development] MZWiZard:
Thank you for keeping life in this old phone!! 😃
[Samsung Galaxy S 4 Unified Development] npjohnson:
My response to all of these is "Please just follow the wiki guide, and you'll be fine."

We do not ship root, nor do we have the option for it, use Magisk if you want root.
[Samsung Galaxy S 4 Unified Development] xperanto:
In addition to @npjohnson`s post keep also in mind, that in LOS 18.1 you can still enable adb root in developer options without installing anything, if you want to make any changes or modify any configs, (i.e. apns, apps etc.). This option is quiet helpful and enough for many users.

18.1 runs very very smooth so far on my device. Great job!
[Samsung Galaxy S 4 Unified Development] NewIdenty:
Is greyscale mode in the Digital Wellbeing app missing for anyone else too? Or is it just me?

Edit: It did not work because Digital Wellbeing is not included as a system app in MindTheGapps package. Turning it into a system app using Magisk Systemize added back the advanced features like greyscale mode.

Dirty flashed from lineage 17, everything seems to work so far. I had to install Flexible Wallpaper to get rid of the stupid zoomed in wallpaper that is part of android 11.
[Samsung Galaxy S 4 Unified Development] popsicle and crackers:
Interesting.
[Samsung Galaxy S 4 Unified Development] vip5912:
After installing LOS 18.1 I gave up root (Magisk) for everyday use.

I only use "adb root" and TWRP recovery for root modifications.
[Samsung Galaxy S 4 Unified Development] Mowca:
Hello

How is 18.1 doing on s4 jfvelte (GT-I9515 / L)? The phone is not stuttering?
[Samsung Galaxy S 4 Unified Development] x2k13:
Same for me. I used to root all my devices back in the CM 12 times, but with TWRP at hand I simply don't need to have root as a security flaw (which root practically is) in userspace anymore.
[Samsung Galaxy S 4 Unified Development] npjohnson:
same as it was on 17.1
[Samsung Galaxy S 4 Unified Development] zyhk:
Hello.

Quite some time ago I asked @arco68 to replace "/vendor/etc/usb_audio_policy_configuration.xml" with 44.1kHz 32bit one, but recently Apple music released a hi-res. audio capable app (beta version). So I prepared a simple script that could change the USB sample rate to its appropriate one dynamically like Bluetooth LDAC, MacOS or Windows for avoiding annoying SRC (Sample Rate Conversion) distortion.

Under Magisk environment (changing its root name space mount mode to global needed), expand the attached zip file under "/sdcard" and execute this script.

Usage: sh /sdcard/USB_SampleRate_Changer/USB_SampleRate_Changer.sh [[44k|48k|88k|96k] [[16|24|32]]]

I recommend to use Script Manager or something for easiness.

Enjoy it!

Edit: Update V1.0 -> V1.3 (can be used under selinux enforcing and permissive modes))

Edit2: My script can support up to 96kHz only because of UAC driver's limitation. For those who want to unlock this limitation, see usb-samplerate-unlocker.

Edit3: latest version: USB SampleRate Changer
[Samsung Galaxy S 4 Unified Development] vip5912:
Question: If I install pure LineageOS (w/o GAPS) can I receive push messages (GMS) or it's part of Google framework?
[Samsung Galaxy S 4 Unified Development] kurtn:
It's part of GApps and microG. Many messaging apps have a fallback solution to use their own push
[Samsung Galaxy S 4 Unified Development] Savatage76:
I think lineage 17.1 is better than 18.1 at the moment

sdcard is supported in 17.1, not here.

for me 18.1 seems a downgrade respect 17.1....camera is very unstable and drain battery when remain blocked with the small icon in the upper bar.

probably, android 10, is the last usable android version for our old s4
[Samsung Galaxy S 4 Unified Development] vip5912:
I like 18.1.

I use sdcard 32GB as Adopted Storage and I have many space in phone for new apps.

I have no problems with camera and my (not new) battery is enough for one day of daily apps (phone, mails, messengers, news etc).

18.1 is more stable as 17.1 in my opinion.

I hope we will have support for this ROM as minimum 1 year (security updates) because new Android 12 is only for 64 bit phone (not for our 32 bit phone).
[Samsung Galaxy S 4 Unified Development] Savatage76:
in my experience the early versions of 18.1 seemed better.

in the last 5 or 6 versions the phone often has slowdowns and blocks that were not there before. It is well known that microsd used as an external space with android 11 (you can't save data like offline maps or other as other have said) has problems unfortunately.

I would like to believe you but in my situation it is the opposite...sorry for my english...
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] ayxse:
Hi, first off i want to start off by saying this.. ive had this device since April 29, 2020 and the issue has been noticeable ever since i got it, but it has gradually gotten worst. It usually happens when im browing in chrome or just using any kind of app for more than 3-5 minutes. Its gotten to the point where i literally just go into twitter browse my timeline for like a minute or two and i can noticeably see some tweets and the bottom navigation bar. Its so ridiculous that i started looking for threads and stuff on how to fix this issue but couldn't find anything until recently that i found a user on this forum explaining you can get rid of this by installing a rom on the device. For now im using an app called ghost screen and lowered the level of the intensity to 8% and the dim level to %8. That has fixed it but i don't feel like using the app all the time on the background. Can anyone recommend me the best rom i could use to fix this god forsaken issue? for now the only rom that im aware that i can fix this is pixel experience and just changing the color calibration on the display options. Is there a better rom that i could get that can do this too?
[Nextbit Robin] npjohnson:
Nextbit Robin

- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:

This is the Official Lineage OS 18.1 thread for the Nextbit Robin.

Downloads:

Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.

Official builds:

ether

Unofficial - built once a month by me, includes GApps and Pixel goodies:

ether

If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:

IMS (VoLTE/Wi-Fi Calling) doesn't work on LineageOS 16.0 and above - it's possible this feature may return in the future, though it unlikely, due to severely outdated proprietary blobs.

Find any? Report them according to this guide.

Notes:

The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.

Kernel Source: https://github.com/LineageOS/android_kernel_nextbit_msm8992
[Nextbit Robin] Raiz:
Amazing job!

Flashing right away !
[Nextbit Robin] blackuriel:
Thank you for your great work!

Just being curious, does it pass Google Safetynet?

If I remember correctly some previous LOS builds for ether actually passed it before.
[Nextbit Robin] npjohnson:
No clue, let me know!
[Nextbit Robin] Aung Chan Phyo:
nice now i have been install this rom so cool
[Nextbit Robin] iMohamedYaseen:
Upgrade went smooth. works perfectly fine.

Thanks for keeping ether alive!
[Nextbit Robin] ytsejam1138:
Is everyone's fingerprint sensor working? Mine was working on 17.1, but it doesn't seem to be recognized in 18.1. I didn't see this listed as a current issue with this build.
[Nextbit Robin] npjohnson:
Works here - took a lot of work to make it work actually lol

If you'd like to follow the wiki guide and submit a bug report I'd be happy to look it over!
[Nextbit Robin] Raiz:
+1 for the fingerprint reader, otherwise the rom is great
[Nextbit Robin] npjohnson:
Really gonna need logs to do just about anything here. Pls submit a bug according to the wiki.
[Nextbit Robin] Raiz:
Doing it asap. I'll attach the log to this post when ready (and will tag you).

Edit:

@npjohnson It fixed itself. What did I do:

1-Enable Developer Option

2-Enable USB Debbuging

3-Allow My PC

4-Started a log with adb

5-Went to the setting to register a FP

6-It worked

Still working after unpluging
[Nextbit Robin] ytsejam1138:
Those steps didn't work for me. I have attached my logfile.
[Nextbit Robin] Mchasard:
Thanks for this new Android 11 version for this device ...is there an expand menu to reboot on recovery mode ?
[Nextbit Robin] buzzywaw:
yes, if I not forgot, I think the advance reboot menu option is under button menu at the system, not in developer menu any longer, cmiiw ..

I've return to LOS 17 just because having trouble with finger print
[Nextbit Robin] Raiz:
Try this is worked for me ;)
[Nextbit Robin] buzzywaw:
noob qustion, how to crate log with adb? and what is registering FP on step 5

thx
[Nextbit Robin] Raiz:
registering FP (=fingerprint) is when you add a new fingerprint. To create a log with adb use this command:

adb logcat -v long > FPR.txt

You need to have adb up and running of course but since you unlocked your bootloader I don't think it's an issue for you.

And this may not solve your problem, I was just lucky when doing it. If you're lucky it'll fix it for you too, but otherwise I won't be suprised if you tell me that it didn't worked
[Nextbit Robin] ytsejam1138:
Retried the workaround/fix from @Raiz and it fixed the fingerprint reader. Thanks @Raiz
[Nextbit Robin] vandyswa:
fingerprint not working here, I have adb dev ready, but won't try the workaround in case there's something else you'd like to know from a device w. the problem.
[Nextbit Robin] blackuriel:
Same here, when going to FP registration settings it just shows the place where the sensor is on the phone and doesn't go to the next step.

I tried flashing 04/01, 04/04 and 04/11 builds and it's the same situation on each one of them.

Btw. if anyone is wondering all three builds pass the Safetynet test.
[Nextbit Robin] blackuriel:
Chrome on Lineage OS 18.1

Does anyone else also has a problem with Chrome closing/crashing by itself?

Tried updating the app, also tried installing the newest Android Web View and tried the newest MindtheGapps. Nothing works and Chrome closes itself after 1-2 sec. Opening it copule of times makes Chrome freeze.

I don't know if this is a problem with Robin or maybe something bigger.
[Nextbit Robin] ytsejam1138:
I've experienced the same thing. Happens on Chrome Beta as well.
[Nextbit Robin] Mchasard:
I just saw that diary isn't synchronisée with m'y Google account...

Am i the only Guy?
[Nextbit Robin] AiZ_fr:
Hello,

First post here. I recently flash my Robin with 18.1 and I'm a really noob! Well, I had previously flash an Acer Iconia Tab A500 a long time ago but this is my first smartphone mod. I can use it everyday but I have some (not really annoying) problems.

The battery is getting old, I own the phone since September 2017 but it depletes really quickly when I use the phone. It's quite good in standby mode but when the screen is on, ouch! Anyway, I'm not an avid user, some texting and light Internet access so it's Ok.

As said above, Chrome only worked one time, just after installing it. Since then, it closes itself almost immediately. I've installed Firefox, which works well.

Can someone explain me where is the fingerprint configuration menu? I can't see it in the settings, even after the adb log trick.

Last thing, do you have quick GPS fix? I've discovered the new access rights brought by Android 11 so all GPS apps seems to start from zero when they launch. It takes ages to (not always) have positioning. I use GPS Test for example and it's weird: there must be at least 8 sat in use to have fix, when it works and these 8 sat are always GPS ones, never GLONASS nor BEIDOU, even if they have better signal.

Thanks to all people involved in this project!

AiZ
[Nextbit Robin] blackuriel:
Hi, welcome to the group!

For the fingerprint configuration menu, it should be under Settings > Security.

To be able to set a fingerprint you may have to set a lock screen PIN or pattern.

For the battery, I bought two new batteries at AliExpress. Work like a charm.
[Nextbit Robin] ytsejam1138:
Chrome BETA appears to be working with the April 18th build.
[Nextbit Robin] blackuriel:
Thx for the info.

I tried BETA too and I could open it but could not connect with any website.

I tried downloading the newest Android System Webview and changing the settings in the Developer options but it didn't work either...
[Nextbit Robin] AiZ_fr:
Hello,

Thanks!

Even if I set a PIN or pattern, nothing appears under Settings > Security. Well, I'll see what happens with future updates...

Have you some recommendations for AliExpress sellers providing those batteries? I've watched some Youtube tutorials, it doesn't look that hard to open the phone.

Have a nice day,

AiZ​
[Nextbit Robin] namikiri:
Hello!

I've installed 18.1-20210418-nightly and it seems that this version has big issues with storage. No app can write files to internal storage. I've tried several apps: Telegram, TikTok and some other apps. They work fine with their app-specific storages but fail when trying to save files to /sdcard. Telegram can create directories and empty files but can't fill them with data, other apps can't do anything. Seems like a FUSE bug because when Telegram attempts to write a file, this message appears in logcat:

fusedaemon: Failed to check lock: Invalid argument

Does anyone have any solutions for this?
[Nextbit Robin] npjohnson:
a bug ticket please. The wiki details how to do so.
[Nextbit Robin] blackuriel:
Sorry for a late reply. Suddenly a lot of work in real life which had to be done asap (as always everything is)...

For the batteries, I bought this one with a strange name but works without a problem.

Here

As for opening Robin it is quite easy. I just watched and followed this video on Youtube.

Here

Mind that when you remove the upper piece of plastic, the glass that covers front camera tends to fall off.

Be careful not to lose it!
[Nextbit Robin] wpost:
It works for me on 18.1 without having to do anything special.
[Nextbit Robin] blackuriel:
@npjohnson Here is the bug ticket.

https://gitlab.com/LineageOS/issues/android/-/issues/3416

If you could please look into it.

Thank you!
[Nextbit Robin] npjohnson:
I will! On vacation for 2 weeks, but after that, sure!
[Nextbit Robin] blackuriel:
@npjohnson Just checked the May 9th build.

There is a very short lag before the FP sensor starts to work but works perfectly!

Tested both during the initial setup, as well as adding a fingerprint from the settings.

Also with and without Gapps.

Thank you very much!
[Nextbit Robin] Raiz:
The "little bug" the first time you register the FP is from long before LOS 18.1 and isn't really a big deal so I consider it fully functional.

Great job @npjohnson
[Nextbit Robin] npjohnson:
super happy to hear it. Yeah, the lag is it firing up lol, I mean it is old hardware at this point ;p - after it's up, all is fine.
[Nextbit Robin] blackuriel:
Thanks again!

I've been using this build for couple of days now and basically everything works great.

I have a problem with headphones though.

It seems that LOS is pushing the sound almost only through the left channel. As long as for the speakers it's not much of a problem, it is a big problem for the headphones. I think it's not giving two equal channels through the jack.

I tried changing the LR balance in the accessibility settings but then the L channel gets lower but R channel doesn't change much.

Anyone having a similar experience?

@npjohnson @Raiz Any ideas? Is this a new problem for LOS or something that nothing can be done about?
[Nextbit Robin] Raiz:
No problem on my side (using LOS without GApps).

Do you use Gapps, or did you flash any sound mod like Viper4Android or Dolby ?
[Nextbit Robin] blackuriel:
That's interesting, thanks!

Yes, I use MindtheGapps. The sound didn't work well so I flashed Viper4android.

If your's all right then I'll try to do a clean install of the ROM and check what was the reason.
[Nextbit Robin] npjohnson:
I suspect v4a is the issue, balance is fine here on skull candy headphones.
[Nextbit Robin] blackuriel:
Thank you both for the answer.

I'll reinstall the ROM then.
[Nextbit Robin] Raiz:
Congrats on your RD title btw, definitely deserved!
[Nextbit Robin] npjohnson:
ayyyy I hadn't even noticed!
[Nextbit Robin] blackuriel:
@npjohnson @Raiz

Sorry for a late report. I did a clean install and the audio channels are all ok.

I may have found a small bug connected with the microphone.

Sometimes after reboot or after a doze, apps like the native lineage recorder or any app using voip to call like whatsapp or skype, can't connect to microphone. I noticed that it gets fixed once I try to make a normal phone call.

I made a logcat and I think it says error -22 and error code -20.

Could you check if you can recreate the problem?

Or should I just make a bug ticket?
[Nextbit Robin] npjohnson:
yeah, I've seen this once! Thought it was a fluke! Ticket would be awesome!
[Nextbit Robin] blackuriel:
Here's the bug ticket

Bug ticket

If you could please look into it.

Thank you!
[Nextbit Robin] Brian_Jhan:
Sorry, but the NFC failed to turn on, any ideas? I used "NFC Card Emulator Pro" to suddenly found out the NFC just wouldn't turn on. I'm currently running on version 0613
[Nextbit Robin] blackuriel:
I'm also using version 0613 and my NFC works without a problem, so maybe you have a hardware problem?
[Nextbit Robin] Brian_Jhan:
It works fine on lineage os 16, maybe I should get it reflashed, also chrome crashes, any one here experiencing the same thing?
[Nextbit Robin] blackuriel:
Maybe that's the problem. I did a clean flash when the LOS 18.1 was released.

As for Chrome, tried many things and never got it working. In the end I switched to Firefox which works without a problem.
[Nextbit Robin] npjohnson:
weird, it works here - what gapps did you use?