yashsingh1/xdaforums huggingface dataset:
[Amazfit] TumiBC:
I would also add there might be a problem with your smartphone bluetooth as well. I used Mi Band 1, 2, 3 and now 4. I also had 2 smartwatches and now Stratos. I also changed 2 smartphones and I never ever had connection problems with Mi Band on any version of it. Mi Band for me is by far the most stable bluetooth connection I've ever used on any bluetooth device and I have over dozen various bluetooth devices. Stable connection, along with battery life is why I'm still loyal to Mi Band. I had various situations where I couldn't connect to plain bluetooth speaker, or sometimes even Stratos disconnects and in each case Mi Band connection is the only one that would still be stable. But that is just my personal experience as it's impossible to account for all the different hardware out there.
[Amazfit] hpto:
Agree with you. I have an Verge, which is, till the moment, a money waste.

Software is the problem, let's see if Xiaomi do something.
[Amazfit] lfom:
You will wait forever, Xiaomi has nothing to do with Pace, Verge or Stratos...
[Amazfit] hpto:
Amazfit don't are an trademark from Xiaomi?

Btw, a money waste. Mi band do the job and far better.
[Amazfit] lfom:
No, it's Huami's.
[Amazfit] Miha1234:
Thank you all for replies!

I don't think the watch is broken (in a sense, that warranty should be claimed) and I'll tell you why.

I may have been a little misunderstood in my first post (English is not my first language). The watch doesn't act up all the time. But frequently enough, that it cannot be relied upon. I don't need a watch that works 70 % of the time (which this one does). So, let me add a few things to my points in my previous post:

5. That happened twice (see number 5 in my first post). Rebooting the watch helped. And let me stress again, that it would happen a lot more often, if I didn't reboot or factory reset the watch every time it starts to act up (3-4 times per month).

6. If that was a hardware error (se number 6 in my first post), GPS data would be wrong (this happened only during my last two runs!). But the GPS data that the watch recorded during the run was correct. If it wasn't, Strava would be wrong, too. Activity (run) was measured (interpreted?) incorrectly by the watch and Amazfit app. Strava got the same (raw?) data and it gave correct results (kilometers, pace). If the watch was faulty, the GPS data would be faulty, too. But the hardware, it seems, is fine. Just the software is bad.

7. HR monitoring is just bad on this watch. I don't think I'm the only one that noticed that.

8. Steps and HR data syncing with the app currently works. It started to work the next day. But I noticed something strange. When syncing wasn't working, the Amazfit app said for steps and HR "08/17 19:52" (something like that, I don't remember the exact time). But it was only 11 o'clock! So, the app was claiming, that the last sync with the watch was in the future. Probably that's why it wasn't syncing. And that is not a harware error, it's the software.

So, I don't think the watch is faulty, it's just the software that's bad. That was my point all along. Right now, the watch is working fine. It was working fine yesterday and the day before that, when I was bicycling. But that is not enough. I want a watch that works all the time.
[Amazfit] nichamelin:
Amazfit stratos 3.0: poor watch

The watch is unreliable, sunset and sunrize notifications come and go without reason. Very disappointing.
[Amazfit] sykomaniac:
You could use my app for sunrise and sunset times.

https://xdaforums.com/smartwatch/amazfit/app-amazfit-sun-widget-t4023903
[Samsung Galaxy S10e Questions & Answers] Techoye:
When I try logging in the game, it goes to "Redeeming offline purchases", and then a Samsung In app Purchases prompt comes up saying "Unkown error occurred.[lib_bind]"

This,however, can be solved when uninstalling galaxy store's updates. But when trying to redeem their promotional skin, I again, get an error "Unknown error occurred. (E9702/6050/com.epicgames.fortnite)"

Sometimes galaxy store just crashes when I launch Fortnite.

I've messaged their support (samsung and epic), but epic redirects me to samsung and vice versa.

I also have root access and TWRP, so I'm open to using more root type ways to solve this.
[Samsung Galaxy S10e Questions & Answers] ExtremeGrief:
Its because you have root
[Samsung Galaxy S10e Questions & Answers] Techoye:
Disabled, safetynet check doesn't pick up root and still same errors persist...
[Samsung Galaxy S10e Questions & Answers] ExtremeGrief:
reinstall stock rom
[Samsung Galaxy S10e Questions & Answers] Incursio27:
Did you solve this?
[One (M8) Q&A, Help & Troubleshooting] DistincTHD:
I am running TWRP v2.8.1.0 and I've tried on this phone already years ago to fix this issue but to no avail but i'm back and trying to tackle it once again.

If I try to wipe I get the error message "unable to mount /data", "unable to mount /cache", "unable to mount /system" and then a "failed."

If I try to Install anything I get similar messages

If I try to flash a new recovery via fastboot I get the message "Writing 'recovery' FAILED <remote: 'image update error'>

It's like i'm completely locked out and unable to boot into the OS also for whatever reason (CyanogenMod) last thing I remember possibly doing to cause this was flashing a new CyanogenMod at the time years ago and then I turned it off, turned it back on and nothing would work anymore i'd just be stuck on the CM Loading boot screen.

Phone is HTC One M8 with **TAMPERED** and **UNLOCKED** + S-ON.

Thanks for any help!
[One (M8) Q&A, Help & Troubleshooting] DistincTHD:
Bump! Please Help!
[Android Q&A, Help & Troubleshooting] myname12:
Hi guys,

I tried to google this but failed, so maybe you could answer this:

What is the exact location of the encryption key / master key (128 Bit AES) for the SD Card encryption on Android 9 (Samsung Galaxy S8, Build PPR1.180610.011.G950FXXU5DSFB), or how is it possible to extract it from the phone internal storage? Does it have a special file name, and which is that?

Thanks
[Galaxy S 4 Mini Android Development] mernurisha:
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed.

All the source code for LineageOS is available in the LineageOS Github repo.

Whats working?

WiFi

RIL

GPS

Camera

Flashlight

Camcorder

Bluetooth

FMRadio

IR

Lights

All Sensors

Sound / vibration

Mobile data

LiveDisplay support

Selinux enforce

Installation:

Download the zip(s)

Install a compatible Recovery (TWRP 3.2.x or higher is recommended)

Perform a backup of your current ROM (Optional)

Make a full wipe (system, data, cache, dalvik)

Flash LineageOS

Optional: Install the Google Apps

Reboot

Source code:

https://github.com/lineageos

https://github.com/Galaxy-MSM8916

Download:

rom: lineage-16.0

XDA:DevDB Information

LineageOS, ROM for Samsung Galaxy S4 mini VE(GT-I9195I)

Contributors

mernurisha

ROM OS Version: 9.0.0_r46

Security patch level: August 2020

ROM Kernel: Linux 3.10.x

Version Information

Status: Stable

Created 2019-08-17

Last Updated 2020-08-15
[Galaxy S 4 Mini Android Development] miccca:
I'm going to try this rom. thank you very much mernurisha

ps: so far everything i need works properly. perfect rom!
[Galaxy S 4 Mini Android Development] ffox.pl:
Apart from not detecting my SD-card your ROM is the best LineageOS I have ever used.
[Galaxy S 4 Mini Android Development] mernurisha:
Thanks for your feedback.

Can you please test this kernel and say if this recognizes your sd-card?

(Wipe cache, dalvik after kernel installation).
[Galaxy S 4 Mini Android Development] ffox.pl:
1. full wipe

2. install lineage-16.0-20190816-UNOFFICIAL-serranovelte.zip

3. wipe cache/dalvik

4. install LineageOS_Pie_Kernel.zip

5. wipe cache/dalvik

6. reboot system

and... ...no effects, this does not recognize my sd-card.
[Galaxy S 4 Mini Android Development] miccca:
I always use Samsung SD card for Samsung smartphone and never had a problem also with other rom either. try that who knows
[Galaxy S 4 Mini Android Development] mernurisha:
Unfortunately, I can not help you anymore. I have no problems with my sd card from Kingston 64GB.

It is difficult for me to understand. Because I don't have this problem.

Maybe you need to format your card with GParted or another software. Sorry.
[Galaxy S 4 Mini Android Development] ffox.pl:
I have no idea too. Others roms work perfect with this SD-card. I am going to buy a new one. I will give a report when I get it.

---------- Post added at 05:24 PM ---------- Previous post was at 05:20 PM ----------

I have no idea as well. Others roms detect this SD-card. I have just ordered Samsung Evo Plus 64GB MicroSDXC. It will come out soon.
[Galaxy S 4 Mini Android Development] miccca:
[MENTION=1801905]gdynia[/MENTION] don't forget format every time you sd card before using, but I assume you know
[Galaxy S 4 Mini Android Development] MrGoodtunes:
No problem with my 64GB Samsung EVO+ removeable memory card formated FAT32 with 32,768 allocation, using guiformat.exe (which is a free Windows app).

View attachment 4807553
[Galaxy S 4 Mini Android Development] OllyFunkster:
Great work, thank you!

The proximity sensor appears to work fine for ambient display, however some options are missing from the ambient display settings, that were present in danil_e71's builds: there is no option to show notifications on remove from pocket (it appears to only show them for a "wave" gesture) and also there is no option to use the proximity sensor to prevent the power button from waking the screen while it is in a pocket. These would be very handy if they could be added!

Thanks again.
[Galaxy S 4 Mini Android Development] MrGoodtunes:
Maybe I spoke too soon, because of trouble after 3 days with everything working fine.

Problems started when I tried to install my favorite old version of Firefox from removeable SD card. Install went okay, but Firefox had some problem and could not open. So I uninstall'd it and went to PlayStore for latest version. But its download show'd only pending, same for any PlayStore download. So I clear'd PlayStore cache, data, and restarted device. This brought notification indicating my SD card had corrupted, needed formating! But desktop PC shows card is totally okay, and TWRP see's card as okay too.

For now, I've gone back to Danil's j33 Pie. Will try another clean install of this build when I find time, because it starts more smoothly (doesn't have the sudden bright screen flash that Danil's has) and mainly because [MENTION=9489673]mernurisha[/MENTION] is being very conscientious about making it work properly.
[Galaxy S 4 Mini Android Development] OllyFunkster:
I've switched over to using this as my main phone now, no issues with SD card (64GB Samsung EVO Plus) so far. It is formatted to expand internal storage.

Unrelated to the above: I have no idea if this is a LineageOS problem, a device problem, or other, but Telegram video selfies have a squished aspect ratio. I've created a ticket on the Telegram-FOSS github: https://github.com/Telegram-FOSS-Team/Telegram-FOSS/issues/358

I don't really expect anyone to know how to fix that, but I thought I'd mention it in case anyone else has a similar issue :)
[Galaxy S 4 Mini Android Development] ffox.pl:
A new Samsung Evo Plus 64GB MicroSDXC has been detected and worked fine so far. Kingston memory has never let me down but this time my Kingston microSDXC 64GB UHS-I Class 10 has failed. Probably it has a hidden defect. Thank you all for help.

---------- Post added at 12:25 PM ---------- Previous post was at 12:23 PM ----------

While zipping and unzipping a file Samsung Evo Plus 64GB MicroSDXC was corrupted for me once as well. It had to be formatted to work. It was on danil_e71's LOS 16 so this is probably not the mernurisha's LOS 16 fault.
[Galaxy S 4 Mini Android Development] MrGoodtunes:
Agreed. My SDcard issue appears to simply be Google's way of assuring safety, security; by ruling out a card that contains old unsupported software causing issues with latest OS.
[Galaxy S 4 Mini Android Development] ffox.pl:
Mernurisha's rom is one of the best I have used. One bothers me. Although the call volume is set to the maximum, the caller can be heard very quietly. Any ideas?

The second disadvantage is that in the mode when the loudspeaker is switched on, the interlocutor hears feedback so loud and conversation is practically impossible.
[Galaxy S 4 Mini Android Development] mernurisha:
Try to install the sound-fix of PixelExperience thread over TWRP. Is the same for all pie roms.

Maybe this helps.
[Galaxy S 4 Mini Android Development] miccca:
my only problem is when i switch on the loudspeaker then my conversation partner suffers from reverberation

I already flashed sound fix but the problem is still there I sincerely hope that mernurisha can tackle this problem
[Galaxy S 4 Mini Android Development] mernurisha:
I've never used a loudspeaker on until now. I'll take a look.
[Galaxy S 4 Mini Android Development] Nethill:
Can i found somewhere rom to GT-I9195? no VE model.. - because i get "updater process ended with signal 4" error message
[Galaxy S 4 Mini Android Development] siloz:
merry belated christmas everyone :)

mernurisha, thank you very much for the gift! i'm very happy with it!

i just love this lightweight and handy mobile phone with your rom :victory:

another little thing:

ksmd seems to need battery consumptive permanent 50% cpu power

fix:

echo 2 >/sys/kernel/mm/ksm/run

(maybe we could try using swap/zram instead?)

check youself with:

adb shell
su
top

(use adb! ksmd doesn't come on the scene on our device's own terminal!)

OT: how many posts do we need to write without %&"$ google captcha on xda-developers :mad:
[Galaxy S 4 Mini Android Development] mernurisha:
Hi,

Ksmd is activated in ramdisk. Set to 1. Default ist 0. Set to 2 - stop ksmd. In the next build I will set it to 2. Thanks for the hint.

Swap-zram is already in use.

Which build are you using now? The last Los 16 has low battery consumption.

! ksmd In Havoc rom not activated.
[Galaxy S 4 Mini Android Development] tigertail:
I just tried to get the Magisk-v20.1 to the S4mini GT i9195 through TWRP 3.3. 1-0, but constantly getting a "zip signature verification failed!" error. I have downloaded the zip again from github and the direct link here is xda, but got the same result. I wiped Cache&Dalvik.

The difference to what you did is, that I had installed the ROM+GAppsPico installed before I tried to flash Magisk. I found one thread for another device on the forum. They had the same problem, but there was no solution found. Some guy got in bad trouble when he unchecked the zip verification. I did not find help in the tutorials, Instructions and the troubleshoot wiki.

Then I tried wiping all and doing a fresh install with twrp: Magisk (no zip verification)-ROM-GApps(both with zip verification). Then reboot. The Rom started ok, also no twrp error. MagiskManager was not installed. I installed the apk and it said "Magisk not installed".

Any advice what I could try else?
[Galaxy S 4 Mini Android Development] msbln:
Probably not helpful but I can only report my experiences:

- I simply flashed Magisk-v20.1.zip after ROM+GAppsPico.

- When Zip-verification is enabled, the error message for Magisk appears. I couldn't find any md5-file, so I installed without verification.

- After installation, the MagiskManager was already present without any further installation steps

What's the twrp-terminal showing when you install Magisk without verification?

Maybe you try a different installation/reboot order, i.e. ROM+GApps+Boot+Magisk

Have you ever tried formating before ROM-flashing or Wiping all but inserted sd card? Please correct me, if this is a risky recommendation (but that's what I did).

An md5-file could easily be generated, but why should it run through only with successful verification on your device when it was not required on mine. But if it was me, I would give it a try nevertheless. But I'm really not a pro, just playing around :)

(You mentioned "i9195" without the "i" at the end as in "i9195i", probably a typo?)

---------- Post added at 08:23 PM ---------- Previous post was at 08:12 PM ----------

Checked on my presently 280 tasks in the adb shell via #top | grep ksm,

but nothing with "ksm" showed up. What did I do wrong?
[Galaxy S 4 Mini Android Development] tigertail:
Thanks. Very helpful to know someone else manage to install it without the verification, so that this is not my problem. I had checked the download against the keys, I am sure the download is ok. I did not know that there is a way to generate a MD5 file for a zip to get the TWRP verification to succeed. I need to see if I find some tutorial about that :o

Yes!! :good: That solved it. I had the wrong order. Now I just installed it over the running (still unrooted) ROM/GApps installation with TWRP. It printed out "Magisk Installer" and several steps what is was doing. It ended with "done." Then I wiped Cache/Dalvik and rebooted.

This time the Magisk Manager recognised the installation.

BTW:

You say I should install ROM+GApps+Boot+Magisk. That interesting. Why Boot and where would I get Boot?
[Galaxy S 4 Mini Android Development] ffox.pl:
Boot simply means that you have to boot the system and re-enter TWRP again. Then install Magisk.
[Galaxy S 4 Mini Android Development] msbln:
He's right. Sorry, next time I should write "Reboot to System" to be more clear.
[Galaxy S 4 Mini Android Development] micopl:
Using this rom for two weeks and all seems working great but battery life could be a bit better. I have on average 2%/hour drain when idle (no wifi, no mobile data, max. energy saving). My stock rom was superior in battery life. On the energy usage graph I have straight line downwards with a constant slope as if no energy saving during sleep was possible. Apart of that thanks for your good work.
[Galaxy S 4 Mini Android Development] miccca:
[MENTION=5646519]micopl[/MENTION] make a simple act restart your smartphone it can help
[Galaxy S 4 Mini Android Development] micopl:
Restart didn't help but I switched on the extremal energy saving (red cross on battery icon) and that worked, the device speed is still acceptable for me.
[Galaxy S 4 Mini Android Development] jakall:
Where I can find your source code, [MENTION=9489673]mernurisha[/MENTION]? Why not on github?
[Galaxy S 4 Mini Android Development] siloz:
sorry for being late :o

i was not at home the last weeks

i'm using your latest build

it runs very stable without ksmd, too :good:

i have noticed that the security patch level is at august 2019

i think to remember that an older build was already at september 2019?

i guess we would look pretty lost if you would buy a new device without sharing your proceedings :eek:

with your los 17 build i finally was able to crypt

and flash los 16 back to the encrypted phone :highfive:

who wants to recreate should keep an older twrp backup to go back to an unencrypted setup!

if you or somebody else here knows his way around selinux

maybe be we could figure this out together

there are only two little things to change for 100% hassle-free:

setenforce 1
[Galaxy S 4 Mini Android Development] miccca:
hello mernurisha is a new security patch in the making for this rom?

thank you.
[Galaxy S 4 Mini Android Development] mernurisha:
Hi,

new update with security patches from january coming soon. Probably with selinux in enforcing mode.
[Galaxy S 4 Mini Android Development] JFK1975:
Could you pls also take a look on the external storage?

With Daniels builds external storage works fine , with your builds only twrp is able to find the external SD, thx for your great work:good:
[Galaxy S 4 Mini Android Development] cristihan:
I don't think it's [MENTION=9489673]mernurisha[/MENTION] build's fault. I have never had problems with external SD card on this ROM.Format the micro SD on the laptop or change it with one from another manufacturer.
[Galaxy S 4 Mini Android Development] JFK1975:
Even they are all i9195i there are different models.

When I start twrp i can use the external SD and the sd is ok.

Great sunday :cool:

---------- Post added at 10:51 AM ---------- Previous post was at 10:50 AM ----------

Even they are all i9195i there are different models.

When I start twrp i can use the external SD and the sd is ok.

Great sunday :cool:
[Galaxy S 4 Mini Android Development] cristihan:
It sounds like a ROM issue, but it's rather hardware specific. I would try other microSD manufacturers too ... I think this test is more handy. :confused:
[Galaxy S 4 Mini Android Development] JFK1975:
Interesting point of view.

Guess it depends If the sun is shining when I try to use my sd?
[Galaxy S 4 Mini Android Development] cristihan:
Ok...maybe the link from bellow will help you.

https://xdaforums.com/showthread.php?t=1947560
[Galaxy S 4 Mini Android Development] JFK1975:
Thank you !
[Galaxy S 4 Mini Android Development] mernurisha:
New Update

The new update on the first page.

- security patch from january 2020

- selinux enforcing

And as always please full wipe before installing the new rom.
[Galaxy S 4 Mini Android Development] miccca:
thanks again mernurisha
[Galaxy S 4 Mini Android Development] JFK1975:
New rom has brought back access to my external sd!:cool:

Thank you very much, we are some lucky guys:cowboy:
[Galaxy S 4 Mini Android Development] micopl:
Battery life improved in my phone, great rom.
[Galaxy S 4 Mini Android Development] mernurisha:
:cool::good:
[Galaxy S 4 Mini Android Development] ffox.pl:
I found a problem... tapping Reset and System makes Power Off.
[Galaxy S 4 Mini Android Development] miccca:
I did a test as indicated but it works properly here my friend
[Galaxy S 4 Mini Android Development] ffox.pl:
It is possible the fault is I did not do full wipe.
[Galaxy S 4 Mini Android Development] wmiki75:
I did full wipe, and i get bootloop :(

LOS 17 started well
[Galaxy S 4 Mini Android Development] ffox.pl:
However, the issue occures. Tapping Reset and System makes Power Off. It only happens when it is being charged.
[Galaxy S 4 Mini Android Development] miccca:
I also performed a test for these but no problem but who knows maybe mernurisha has a solution for you.

at least my phone is working properly so far
[Galaxy S 4 Mini Android Development] mernurisha:
It's no big deal. This only happens when the charger cable is connected.

Press the power button again and you're done.

I've discovered another bug. The factory reset does not work.

Will look at it this weekend.
[Galaxy S 4 Mini Android Development] yourproblem:
thanks for the new update! (i've installed it)

Question: is the call volume (ear speaker) louder than previous version?
[Galaxy S 4 Mini Android Development] siloz:
sooo sorry mernurisha,

i messed up big time! you probably was dead right!

i guess i have had destroyed my system while experimenting

and fixed it heedless and half asleep with an old twrp backup :silly:

thank you very much for the update :good:
[Galaxy S 4 Mini Android Development] cristihan:
Thank you [MENTION=9489673]mernurisha[/MENTION] for your great work. I noticed an anomaly in the Cotacts, in the last build.

If there is a contact with two phone numbers...I edit the contact and delete one of the numbers and then add a new contact, with a different name from the one edited with that deleted number, the new contact will be duplicated and can no longer be deleted from Contacts.
[Galaxy S 4 Mini Android Development] mernurisha:
I can't say much about it. I'm on android 10. Maybe the fault is in the lineage source. Factory reset bug from last build was also from lineage source.

I will upload new update soon.