S21 Android 12 "item already copied to clipboard" pop-up [SOLVED] - Samsung Galaxy S21 Questions

SM-G991U - Since Android 12 upgrade, often when unlocking I set a random pop-up that says, "item already copied to clipboard". I can't find anything to tun it off and it screaming doesn't affect to issue either. Anyone else have this and fix it? It makes no sense.

I'm also experiencing this but unfortunately I've no idea what's causing it. I'll keep an eye out for more reports of it.

I found some complaints on the Samsung forum too. Nothing suggested seems to fix it. I keep f'ing with settings that not only don't fix this but other things then get FU. Supper annoying.
What I think is happening is that unlocking the screen triggers the copying to clipboard pop-up but it's just the message. I can't see that anything is copied to clipboard except text I choose.
Not sure my AT&T POS can be rooted easily but when I get tired of this clipboard nonsense I'll look into it. I imagine a custom de-bloated ROM will fix it is Samsung won't.

Do you have KDE Connect installed? If so, could you try disabling Clipboard Sync in the plugin settings and see whether that stops the pop-ups?

Thanks. That suggestion has promise. I assume that worked for you. I've disabled it and will let you know after a day or two. Maybe the reason it isn't a huge problem is that that Android/Linux users aren't a big user base?

Since I've disabled that option in KDE Connect I've not seen the pop-up once (been a couple of days).
It makes sense because I think KDE Connect is regularly copying stuff to the clipboard from the connected computer. A lot of the time it will be the same data and whereas Android 11 never reported it, Android 12 obviously does.
So it's not an Android issue as such (although why _would_ it report that a needless copy to clipboard operation has been performed? It would just be an annoyance anyway!), I think KDE Connect needs to change to a check before copying to the clipboard.

Raised a bug: https://bugs.kde.org/show_bug.cgi?id=446567

Excellent. You totally nailed KDE Connect as causing it. I haven't gotten the pop-up for 2 days now.
KDE Connect could "fix it" by simply making the "feature" off by default. I'm still inclined to think Android should fix it. Earlier Android releases didn't have this problem. I've had KDE Connect for years.
Thanks for the work around!

I am having this issue( item already copied to clipboard) with a new Samsung A52 (recently updated to android 12 One UI 4.0 but was doing the same prior to update), i do not have KDE connect installed that i can find.

Well, since removing KDE Connect I haven't had any issue with it. I suggest you start a new thread for the A52. This thread solves is for the S21.

UbinTook said:
I am having this issue( item already copied to clipboard) with a new Samsung A52 (recently updated to android 12 One UI 4.0 but was doing the same prior to update), i do not have KDE connect installed that i can find.
Click to expand...
Click to collapse
Same, i have the same issue on Galaxy Fold 3 and no KDE installed

Crazy idea but knowing that removing KDE Connect from the S21 fixed the issue, install KDE Connect and then uninstall KDE Connect. Maybe it leaves some residual that corrects the problem. Can't hurt.
I also recommend starting a thread for the A52 asking this question.

jerryp7 said:
Crazier things have happened ! i will look into that and see if it works .
i have indeed started a thread in the A52 forum ( about 3 weeks ago)with no responses as of yet .
(https://forum.xda-developers.com/t/...ied-to-clipboard-copied-to-clipboard.4392851/)
Click to expand...
Click to collapse

Best I can do is keep my fingers crossed for you. Sorry

It is not an issue. It's a feature in Android 12 that warns user that the app is copying the content of the clipboard. It's a privacy feature and you can turn it off at settings - privacy.

Didn't work for me while KDE Connect was installed. Maybe this is the problem "Alert when clipboard accessed" being turned on under privacy for the A52 users.

Related

[Q] Sideloading Apks to multiple devices at once

Hullo.
Looking for a little advice from folks about sideloading apks to multiple android devices at once (like, 8 or 9 of em). Searched around the forums a bit and couldn't find anything directly relating to this issue, so I figured I'd ask. I dunno if this belongs more in App development, but its an Android specific issue so...
At present I'm using Test Flight App (I'd post the URL but I'm too much of a noob here) to manage builds and releases. Its really great for getting beta builds out to the studio team, and to various beta testers and potential partners.
However there are a few issues with it, which are particularly problematic for quick iterations etc.
1) Actually downloading the apks is a manual process per device. So if you've a small QA team (or are working solo) it takes alot of time to get the newest build onto everything.
2) Each build has to be uploaded via the Test Flight website, then distributed to users on a build by build basis. This is a difficult to automate process, so makes having any kind of continuous integration system for nightlies etc. difficult at best.
I've been looking into possibly doing something like installing a Dropbox on each device and automating CI builds to a dedicated folder, which is shared via Dropbox to everything, but its a bit of work up front to get it working and I may still have to actually manually install the things each time.
Any of you guys had any experience attempting to do something like this?
Figured I might as well come back and answer my own question incase anyone else was wondering.
Ended up using a USB hub to connect multiple devices then running a script that used ADB to get all attached devices, then passed that list one by one into the adb install function.
Still not ideal, as it requires a wired connection for each phone, but works for now.
Dansixminute said:
Figured I might as well come back and answer my own question incase anyone else was wondering.
Ended up using a USB hub to connect multiple devices then running a script that used ADB to get all attached devices, then passed that list one by one into the adb install function.
Still not ideal, as it requires a wired connection for each phone, but works for now.
Click to expand...
Click to collapse
How about Wireless ADB?
Check ADB Wireless on Play Store. (Unfortunately all phones must be rooted, because it requires ADB port to be set to 5555)
https://play.google.com/store/apps/details?id=com.wave18.adbwireless
I think you are using batch file to get ADB script for all devices.
Press Thanks if helped.

Can't change location or screen orientation

Hi all,
Hope I'm posting this in the right place. If not, please move.
I have Remix_OS_for_PC_Android_M_64bit_B2016072603 installed as a virtual guest in Virtualbox 5.0.24_Ubuntu r1083 with Xubuntu-core 16.04 as the host machine. Using a Toshiba Satellite Pro L510. Took me four days to nut out how to get to this point, but installed and booting and stable now.
My issues:
1/ Location: When I try to run an app from Play Store it thinks I'm outside of Australia/New Zealand (the app I'm trying to run is specific to those regions). I'm in Australia, the app works fine on my phone (am logging in exactly the same way).
(* Update: I installed GPS Status and it tells me GPS is not switched on. Was hoping to then change the location with Fake GPS, which I also installed. It won't do anything with same message: GPS not enabled or similar.)
2/ Resolution: The screen defaults to portrait, as expected I suppose, but I have a 1366x768 monitor and it doesn't fit in the screen. Consequently, I have a scroll bar because as Virtualbox Guest Additions is not compatible with Remix OS at this point there is no mouse integration (I need to hit Right Control to use mouse in host and same to use in guest again). I need to press a bunch of keys to just scroll the screen up and get back to where I was going. :|
Other than that, all working great, Remix OS is great, thanks to the team that created it. The main reason I was wanting to use it is to use this one app on my computer (AFL Live) and plug my computer into the TV. I don't use my phone for anything other than that one app, SMS and the occasional call so I am by no means an Android junky. In fact, before this, I knew very little about it (but a lot about Linux/Ubuntu).
This install has been a quest, a learning curve, and these are my last two hurdles so I'm calling for help if it's out there. Trawled the net, tried some things, but have hit a brick wall with these two problems.
My first post so not sure of the protocol. If these two issues should be the subject of two separate threads, mods please advise and I will edit accordingly and create a new thread.
Tnx in advance.
(* Further update: Just having a read of this: http://forum.xda-developers.com/remix/remix-os/remix-os-installation-rooting-t3293769
Wondering if rooting the device would allow me to change any of these, in particularly, the location to Australia where it should be, or switch on GPS so my app can see where I actually am. I'm presuming it thinks I am in the Cocos Islands or somewhere else!)
(* And further update: The screen resolution was as easy as typing Alt+F1 to launch a terminal then 'wm size 1366x768'. That looked terrible, though, so changed it to 1048x768 (from memory) and it is good enough, though not perfect. I may be able to get closer with further tweaking. Now the last, and most important, hurdle to leap: How do I get Remix OS, and more specifically my AFL app, to know I'm in Australia. Frustration. It's taken about ten days, on and off, to get here and still not quite where I want to be, but hopefully my travails can help someone else along the way ...)
Gave up on it. If anyone comes up with a way of running Remix OS in Virtualbox and setting the location, please post. Guestadditions would probably fix it and maybe one day ROS will be compatible with it.
On the other hand, I did learn a lot more about Android than I cared to know, but am now thinking about buying my first ever Android tablet to do the job with a USB/HDMI adapter.

Bugs in official Lineage OS 14.1 and Resurrection Remix 5.8.4 for Galaxy S2 GT-I9100

The info about the issues provided as on 2017 September 13.
The text was last edited on 2019 August 24.
Hello.
Sorry for mistakes in my poor English.
I had used every day LOS14.1 and RR5.8.3-5.8.4 custom ROMs for Samsung Galaxy S2 (model: GT-I9100) for more than 2 months in the middle of 2017 and this is my serious test report:
1) When you will get an incoming phone call, receive a message via cellular network or a file via bluetooth then Galaxy S2 with the custom ROM will rings and vibrates but the screen can be fully dark for several seconds without any notification about it.
This bug almost does not exist in RR 5.8.4.
2) Multiple issues are with the smartphone storages (internal and external).
a) Some apps can do not work with the smartphone storages. They can start to work with storages after the smartphone reboot or after few reboots only.
The same bug is in the Resurrection Remix ROM 5.8.4. The screenshots attached to this message proof the existense of this bug in RR 5.8.4.
b) Only during my attempt to use the custom ROMs LOS 14.1 and RR 5.8.3-5.8.4 on Samsung Galaxy S2, I lost the 1 file (it was the important file to me) on an external microSD card and yet file explorer apps start to show the 2 suspicious unerasable zero size files in file listings there, which I can not delete nor rename nor even copy - file explorers to continue to show they in file listings still today after years on my microSD card. It is interesting that these zero size undeletable files was discovered not in an upper directory but instead deep in the old different long directories on my microSD card. Thus, may they was implemented hiddenly as masking labels there for a reason remained unknown.
c) Impossible to appoint an user installed file explorer app as a default file explorer for pick-up files from another programs. For instance, when the smartphone user want to send a file via Skype then there is always only the file explorer opens with the poor and uncomfortable interface, which implemented in the custom ROM as default forever. And only then from its ugly interface the user can choose one of other installed file explorers for using they once for find and pick-up a file.
The famous FX File Explorer app does not work with the default internal folder 'Documents'. The app also can not delete a group of selected files on an external SD card.
The RR 5.8.4 ROM haves even 2 implemented file manager apps which work smooth but they both have poor UIs with limited functions.
Factually, do not providing Android APIs correctly the custom ROM developers refuse to use user installed apps fullfledgely but instead they compel the users of their ROMs to use only an ersatz bloatware soft implemented by the ROM developers in the custom ROMs.
3) The big battery drain after every reboot and a significant battery drain in general.
As more media files (videous, images include offline map tiles, sounds) are in the internal or external storage (an microSD card) of smartphone then more extensive battery drain Galaxy S2 will suffer after every reboot and after some operations with access to storages. This bug appears in both ROMs: in Lineage OS 14.1 and in Resurrection Remix 5.8.3 - 5.8.4.
For instance, if 128GB microSD card almost full of various videous and photos is in the smartphone then it becomes very hot for more than 1 hour after every reboot!
Some my futher research reveals that the high temperature with the battery drain caused by the dubious activity of Media Storage app implemented in the Lineage OS based ROMs hiddenly. This app finds and analises all media files (and may more) by unoptimized and uneffective way creating and saving big hidden databases, wasting CPU, a battery and an internal storage.
Unfortunately, disabling of this dubious hidden app leads to the smartphone loses functionality partly.
Please, pay in opinion that this bug produces the same traces as usually produced by some hidden virus activity: excessive scanning of user files, an unexpected load on the hardware, eventual draining of the battery...
4) Multiple lags (short freezes) are at various programs interfaces using. A main Android 7 menu is more or less smooth only.
For instance, Skype app version 8 has lags to several seconds in its menu.
Also the smartphone touchscreen is more sensible with the latest original Samsung's firmware (Android 4.1.2) rather than with LOS 14.1 or RR 5.8.4.
On another hand, Galaxy S2 with LOS 14.1 or with RR 5.8.4 scores more points in AnTuTu test but it is only mostly due to becoming of supporting F2FS and yet getting additional points for an newer additional rendering engine.
5) Sometimes over-the-air updates becomes impossible due to already after downloading an update file the smartphone then displays an error message 'Unable to reboot into recovery'. For instance, this bug appears after 2nd August 2017 and 23th August 2017 updates.
6) Camera1 and Camera2 APIs do not provided correctly. Some serious camera apps report about it clearly by a message and then close. Another camera apps are buggy.
I just will give few examples...
All videous recorded with a mono sound only but can be saved as allegedly with a stereo sound.
The famous A Better Camera app by Almalence loses all its settings unexpectedly time to time and becomes as its first launch again. This bug does not exist in RR 5.8.4 but instead there is another bug with A Better Camera app: it can not record videous with scene mode setting. And it is very sad due to the app can significantly improve the camera in our old device specially for photo and videorecordings in low light conditions (it can be reached by choosing manually ISO800 and then the Fireworks scene mode).
The implemented in the ROM the Snap camera app is very weak with the ugly uncomfortable interface.
7) There is a trouble to enter the year manually in the data settings in a portrait mode due to number of years limitation. The same bug was in RR 5.8.3 but it was fixed in RR 5.8.4.
This bug does not exist in a landscape mode.
8) It can send and receive only the very limited kinds of files via bluetooth, which filename extensions are listed among a poor list of files recognised by the custom ROM itself (not by user installed apps). Factually, it is like an unwanted blocking filter at the bluetooth.
For instance, you can create an effective compressed .zipx archive file by the WinZip app for Android OS on Galaxy S2 but you will be unable to send such archive file via bluetooth. And you will be unable to receive such files too.
Many file extensions do not recognized by the custom smartphone ROM: among they are modern Opus music format, RAR archives and etc, etc. You will be unable to send or receive they via bluetooth.
The same bug is in RR 5.8.4.
Please, pay in opinion this issue does not seem as a mistake of the ROM developers but just opposit: it seems more as an unwanted blocking filter specially implemented on the bluetooth. And their reason for it remains unclear and suspicious.
9) There is an implemented feature to record a phone call but there is not an option to record all phone calls automatically. Instead only after hand up there inside the tree of dialer settings appears a hidden option which allow manually start to record the current call. So, if you want to record the call then only already during the call you need to go into the dialer menu tree and activate this hidden option, which is uncomfortable.
Moreover, external apps for phone call recordings does not work properly with this ROM (they do not record sounds from another side).
The same bug is and in RR 5.8.4.
10) The famous SuperSU root tool by ChainFire does not compatible with Lineage OS 14.1 for Galaxy S2. And apps which require only the SuperSU root can do not work properly.
The same bug is in the Resurrection Remix 5.8.4.
11) The small window with the text 'MTP host error' appears in the screen foreground like a ghost.
The same bug is in RR 5.8.4.
12) The settings menu haves a white background everywhere and it causes wasting of short lifetime span of pixels of OLED display triggering yet the additional unwanted battery drain and provoking an eye strain.
Unfortunately, a wallpaper does not change it.
There is not a simple option in the settings menu for just to change its white background to black.
It is not a bug but it is a significant disadvantage of the Lineage based ROMs - specially the Resurrection Remix ROM, which haves miltiple various settings and options but except needful simple this one.
13) The official Lineage OS bug tracker does not accept bug reports by easy way. Instead it requests a registration in advance via a full user name and other personal data, which can be sensitive and used by unappropriate way. It does not allow the registration via the World famous and trusted Google+ or Facebook social networks. Moreover, sometimes the bug tracker does not work and have an announcement about sheduled technical maintenance on a web-hosting side.
14) The ROM developers do not fix even well known simple bugs like described here at the points 8 or 9.
Talking very softly: some XDA forum users (include moderators) also do not welcome for public bug reports in proper topics of the XDA forum. It seems like they conceal the existence of many bugs and only lure new people to become victims of the buggy ROMs. And I did started this topic for stop it.
I do not know what their purpose is exactly.
But after some time observation it is possible to determine that someone actually regularly 'dilute' proper topics on the XDA forum by short luring messages in parrot style like 'I had installed it and it is great!' Unfortunately, such kind of simple messages are just alluring fakes high probably.
The another short trap parrot messages are like that 'It runs fast and smooth!'. The deception there is that it attracts only by the Android 7.1.2 menu appearance on the old device for purposes like a brag but really conceal that the whole device with this ROM becomes unreliable for serious fullfledge using.
I was attracted by topics on the XDA forum about Android 7.1.2 for Samsung Galaxy S2 (model: GT-I9100) and I had lost more than 2 months period installing latest Lineage OS 14.1 updates and Resurrection Remix ROMs 5.8.3 - 5.8.4 and I had decided that the last official Samsung's firmware with Android 4.1.2 is not ideal but much reliable on Galaxy S2 rather than LOS 14.1 or RR 5.8.4.
15) The custom ROMs does not provided as a single useful full package unlike it was with a Samsung's official firmwares. Actually, things, which called Lineage OS 14.1 or RR 5.8.4 for Galaxy S2, are main parts of unresonant firmwares only. It means that in a case of installing such firmwares the user discovers many disadvantages of they and after asking questions on the XDA forum he gets endless tips like: to find in the internet and install other necessly parts and yet to make very specific technical adjustments manually or even experiment with they. All it can be interesting and feasible for the smartphone entusiasts but not for an ordinary user.
For instance, some messages on the XDA forum suggest to download and install the special version of Kernel Adiutor app then run it and experiment with its settings for make the smartphone runs smooth because the ROM developers did not preselect best settings and did not adjusted they before as default values. Moreover, you will need to find in the internet and install separately yet a modem firmware for a better signal, the Substratum app and a proper theme just for make the screen background black everywhere and etc, etc.
Factually, Lineage OS 14.1 and Resurrection Remix 5.8.3 or 5.8.4 ROMs for the Samsung Galaxy S2 smartphone are not 'Plug&Play' kind of firmwares. They are unfeasible for an average user.
Please, pay serious attention: an user of these buggy custom ROMs can get a negative impact to his behavior (even to his mental health) and to his business.
JaLoou said:
[...]last official Samsung's firmware with Android 4.1.2 is not ideal but much reliable on Galaxy S2[...]
Click to expand...
Click to collapse
Obvious obviousness.
Custom ROMs are not meant to replace commercial firmware, but so that the community can learn and be happy to discover new things.
The screenshots, published with this message, proof the big battery drain after reboot and yet just after charging without even using the Galaxy S2.
I had experiment specially:
after the middle of a night I had swithed off my smartphone, I charged it to 100%, unplugged then I switched it on and leaved immidiately for several hours while I sleeping to late morning.
Then I got the varios battery stats and saved it on the 3 screenshots.
So, everyone can see that the battery lost 39% from full charge without the smartphone being used by the user for several hours.
Moreover, there is a big battery drain just after every charging without the smartphone using and 4th screenshot proofs it too.
And later in response to some nit-pick criticism about this battery consumption test then I had attached yet here a 5th screenshot of the same stand-by battery test on my device swithing on after a full charge but with Samsung's latest official firmware with Android 4.1.2. So, 5 screenshots here give a full picture for compare easy the custom ROMs and Samsung's latest official firmware with Android 4.1.2 in the terms of power consumption.
You can see it clearly that Samsung's latest official healty ROM with Android 4.1.2 consumes not only much less power in stand-by mode but also it consumes power for another purposes at all mostly for cellular network only while the suspicious custom ROMs like LOS 14.1 or RR 5.8.3-5.8.4 consume the enormous big amount of power like crocodiles at stand-by mode for the unwanted excessive file scanning on the user's smartphone!
The next screenshot proofs the bug of inability to install over-the-air updates (after a firmware update file already downloaded the smartphone shows the error message 'Unable to reboot into recovery').
Please keep in mind that none of the developers gets paid for his work. Complaining about bugs not being fixed like this appears disrespectful to me.
Thanks anyway for the thread, might help some people to decide whether to give this ROM a shot or not.
A big thanks to the XDA-Devs for this ROM which I have on my phone since 2 months.
In this time, I haven't been able to "seriously" use my phone. Everything is working except the bugs mentionned above, but the phone has become soooo slow... and some issues with battery life also. Sometimes the device just gets hot in my pocket for no reason, drains half the battery in a few minutes (though I have done the "calibration").
Every action becomes a hassle, but works in the end. It's like using Windows 95 on a 486.
So: nice if you want to try out stuff, but no to recommended for every day use IMHO.
BenjyTec said:
Please keep in mind that none of the developers gets paid for his work. Complaining about bugs not being fixed like this appears disrespectful to me.
Thanks anyway for the thread, might help some people to decide whether to give this ROM a shot or not.
Click to expand...
Click to collapse
Concealing many bugs the ROM developers did lured me (and many others) as free unpaid beta-testers for their unreliable ROM.
Moreover, the bug tracking functions in Lineage OS and Resurrection Remix are not clear and suspicious. Persons who manage it can get easy a various sensitive information about the smartphone users and can use this data by unappropriate way.
If sort the all known bugs then it is possible to reveal easy that the most part of they haves access to user files on the smartphone. These bugs are:
- the unwanted blocking filter at bluetooth,
- excessive user files scanning,
- wrongly provided Android APIs accompanied with attempts to constraint the users to use only the bloatware ersatz file managers implemented in the custom ROMs and an ugly bloatware ersatz camera app.
The bugs mentioned above are well known but did not fixed for a long period of time. And it triggers really an assumption that they can be specially implemented in the custom ROMs for get a full control over the user files without the user knowledge about it. By another words they are not the unfixed bugs but they are the traces of hidden viruses implemented in the custom ROMs.
These viruses can be ordered and paid masking via chains of proxies by an interested party. Ordered viruses and vulnerabilities can be easy implemented villaintly inside some of many allegedly useful patches on every stage in a long way from an initial open publication of Google's Android source code to a last compilation for get a firmware binary file for a target gadget model.
The device Samsung Galaxy S2 was sold over 40 millions (according to Wikipedia). High probably several millions (may even decades of millions) are remain in use today. And they are an attractive target for an interested party.
Moreover, viruses implemented in a firmware almost impossible to determine by an antivirus software.
The party interested in productions of infected custom ROMs can be also discovered easy by researching and proper sorting the several users of the XDA forum, which was indicated in the hostil activity: they was against the public exposures of serious issues in the custom ROMs, they did tried masked to blackwash me and they lure really new people to become unwill victims of the unreliable custom ROMs. The convinced persons are all have same specific feature...
Unfortunately, one of the XDA moderators forbid to explain about it futher.
But what I allowed to tell here is that any custom ROM development can be supported by a party interested in a mass distribution of viruses hidden in firmwares.
Complaining about bugs not being fixed like this appears disrespectful to me.
Click to expand...
Click to collapse
Fully disagreed, as long it's constructive critism it helps other to see what is currently working and what not to easier decide to switch to the ROM or not. The main reason is (I asume) to show the list of bugs, which make sense cause the specific LOS thread not shows the current issue, or you need to go trough each comment separately.
I'm glad we still getting updates and **** but some bugs are years old and just migrated because no one seriously took a closer look at it, so I'm happy that this thread exist to share the experience and to list the known issue.
Here you are, not the developers, not doing the right thing.
You want everything at once, and what you did for it.
https://forum.xda-developers.com/showpost.php?p=73346796&postcount=1814
CHEF-KOCH said:
Fully disagreed, as long it's constructive critism it helps other to see what is currently working and what not to easier decide to switch to the ROM or not. The main reason is (I asume) to show the list of bugs, which make sense cause the specific LOS thread not shows the current issue, or you need to go trough each comment separately.
Click to expand...
Click to collapse
Exactly what I wrote in the second half of my post
I understood the purpose of this thread. What I said just refers to two or three sentences the OP posted. Thank you and goodbye.
JaLoou said:
In this message I only want to publish screenshots, which proof just one of many stupid bugs in Lineage OS 14.1 (Android 7.1.2) for Samsung Galaxy S2 (GT-I9100) smartphone.
As you can see sometimes an user is able to press link 'connect' after entering even 5 symbols of password for WiFi!
But an user is denied of possibility to connect to a WiFi hotspot if he did entered a password of 8 symbol length!
Or 9 symbols and etc, etc!
I did received and installed new updates for Lineage 14.1 every week but NO one known bug was fixed include this one.
Click to expand...
Click to collapse
First of all, Please don't use !!!!!! It looks like you offend people!! Even people who tries to help you!
Secondly, the issue isn't an issue of i9100. It is an issue of the ROM, meaning on all devices. A device maintainer maintains his devices when something changes in the ROM (changes in LineageOS and Android google sources) to keep it up to date.
Thirdly, have you ever connected with your dummy passwords to the Wifi Access Point? Or are you just trying to find "stupid" bugs?
There is a validation mechanism depending on the used security type of the Access Point which is auto detected
WPA2 PSK => minimal password length is 8 WEP
WEP40/104/128 => valid lengths 5, 13, 16 or HEX-values valid lengths 10, 26, 32 and ofcourse 0-9 A-F as allowed characters
If you want to help, try to configure your WIFI access points and verify LineageOS's behavior when configuring with WPA2 PSK/WEP.
Also look in JIRA if the issue is already reported. I saw this issue last week about wifi-password for example:
https://jira.lineageos.org/browse/REGRESSION-912?jql=text ~ "wifi password"
---------- Post added at 06:46 PM ---------- Previous post was at 05:55 PM ----------
Here are my comments on your reported bugs.
1) When you will get an incoming phone call or receive a message then your Galaxy S2 will ring and vibrate but the screen can be fully dark without any notification about the call.
I'm aware of this symptom. The problem is memory and running background processes. Having to much apps installed (Facebook, instagram, snapchat, etc) causes the OS to memory swap when the phone-app must be active. ART uses more memory than Dalvik.
2) Some programs can not work with an external SD card. They can start to work with it after reboot or after few reboots only.
Which programs? The solution is probably using emulated storage.
3) Galaxy S2 with Lineage OS 14.1 becomes hot with a big battery drain for some significant period of time after every reboot. So, rebooting trying to make installed apps work properly you can just quickly fully empty your battery and finish on it.
This is a known issue and can't be resolved. Android 7.1.2 takes more boottime than 4.1.2. The CPU is constantly at 1200Mhz during boot and several minutes after boot because of apps starting up. Our 1600mah battery can't cover this 'boot'-drainage multiple times. It needs 'resting' time to stablelize (like a car battery). Try the app Battery Log to see how the CPU at max speed is pulling the voltage down.
4) The famous FX File Explorer app does not work with the default internal folder 'Documents'.
When you will delete a file on an external SD card this app may not delete it but just rename the file to hidden only (a name started with a dot).
There is another file manager app implemented in the ROM but its interface seems very poor and uncomfortable.
I don't know what the issue with this App. A possible issue could be that we don't use emulated storage
5) Sometimes there is impossible to connect to a password protected WiFi hot-spot due to the link 'CONNECT' in the WiFi menu remains inactive (gray coloured) after password typing 8 symbols or more. This bug appears constantly at a connection with some password protected WiFi hotspots only. And it can become a serious unexpected trouble if you are on the go and in a need to connect to a new hot-spot.
This is by design. Validation depends on used security WEP/WPA2 PSK
6) Camera1 and Camera2 api do not provided correctly. So, camera apps are buggy.
For instance, the famous A Better Camera app by Almalence loses all its settings unexpectedly time to time and becomes as its first launch again. Yet there are another troubles with A Better Camera app.
The implemented in the ROM the Snap camera app is very weak with the ugly uncomfortable interface.
A great of effort has been made to make the legacy Camera api's work in the framework for legacy devices like our i9100 since google dropped its support. It is not perfect and probably never will be. Expect same issues later on in Android O.
7) There is a trouble to enter the year manually in the data settings in a portrait mode due to number of years limitation. This bug does not exist in a landscape mode.
Use small display view. We have a very low-res phone for 2017
8) There is an implemented feature to record a phone call but there is not an option to record all phone calls automatically. Instead only after hand up there inside the dialer settings appears a hidden option which allow manually start to record the current call. So, if you want to record the call then only already during the call you need to go into the dialer menu and activate this hidden option, which is uncomfortable.
Moreover, external apps for phone call recordings does not work properly with this ROM.
Was there ever a automatic recording option in the ROM? We need to investigate some apps why it fails recording.
9) The famous SuperSU root tool does not compatible with Lineage OS 14.1 for Galaxy S2. And apps which require only the SuperSU root can do not work properly.
It is still an issue I think. Please see http://www.lineageosrom.com/2017/01/download-supersuzp-and-su-removalzip.html
10) The small window with the text 'MTP host error' appears in the screen foreground like a ghost.
Our old kernel needs some patches, but it is unclear which patches.
11) The official Lineage OS bug tracker does not accept bug reports by easy way. Instead it requests a registration in advance via a full user name and other personal data, which can be sensitive and used by unappropriate way. It does not allow the registration via the World famous and trusted Google+ or Facebook social networks. Moreover, sometimes the bug tracker does not work and have an announcement about sheduled technical maintenance on a web-hosting side.
12) The ROM developers do not fix even well known simple bugs like described here at the points 5 or 7.
Seems they also do not welcome for public bug reports in proper topics on the XDA forum. It seems like they conceal the existence of many bugs and only lure new people to become victims of their buggy ROM. And I did started this topic for stop it.
I do not know what their purpose is exactly.
But after some time observation it is possible to determine that someone actually regularly 'dilute' proper topics on the XDA forum by short luring messages like 'I had installed it and it is great!' Unfortunately, such kind of simple messages are just alluring fakes high probably.
The another short trap messages are like that 'It runs fast and smooth!'. The deception there is that it attracts only by the Android 7.1.2 menu appearance on the old device for purposes like a brag but really conceal that the whole device with this ROM becomes unreliable for serious using.
I was attracted by topics on the XDA forum about Android 7.1.2 for Samsung Galaxy S2 (model: GT-I9100) and I had lost 1 month period installing latest Lineage OS 14.1 updates and Resurrection Remix 5.8.3 and I decide that the last official Samsung's firmware with Android 4.1.2 is not ideal but much reliable on Galaxy S2 rather than LOS 14.1 or RR 5.8.3.[/QUOTE]
I'm using 2 S2's as daily drive. One for work and one private. I don't have many big apps installed and use my s2 also as car navigation using waze or Google maps. Yes sometimes you have to be patient for a 6 year old device.
Hello.
It is good that the ROM developer had come here in this topic at least.
First of all I do not offend all people. I help Galaxy S2 users to do not fall in the trap, in which I had falled already after being lured by false messages on the XDA forum about allegedly the existence of good ROM Lineage OS with Android 7.1.2 for i9100...
But the ROM is very buggy actually.
For second, all bugs which I described in this topic do not exist in the Samsung's official firmware for Galaxy S2 but only in Lineage and Lineage related ROMs like Resurrection Remix 5.8.3.
JaLoou said:
Hello.
It is good that the ROM developer had come here in this topic at least.
First of all I do not offend all people. I help Galaxy S2 users to do not fall in the trap, in which I had falled already after being lured by false messages on the XDA forum about allegedly the existence of good ROM Lineage OS with Android 7.1.2 for i9100...
But the ROM is very buggy actually.
For second, all bugs which I described in this topic do not exist in the Samsung's official firmware for Galaxy S2 but only in Lineage and Lineage related ROMs like Resurrection Remix 5.8.3.
For instance, with Samsung's official firmware I was able to connect to the exact 2 WiFi hot-spots (as in the screenshots published before) and to many more. But with Lineage 14.1 (and RR 5.8.3) I'm unable to connect to the same 2 WiFi hot-spots. This is enough.
It does not matter which security use this 2 WiFi hot-spots. I was able to connect to them before with the Samsung's official firmware and now I'm unable to connect to them with Lineage.
Before I was able to enter the proper passwords to them. Now I'm unable to do it.
Click to expand...
Click to collapse
In my opinion, you are making a cardinal mistake comparing Stock Android with version 4.1.2 with custom ROM version 7.1.2.
Each of these versions represents a far different operating model in the hardware layer.
But test yourself, if you have enough free time.
ze7zez said:
In my opinion, you are making a cardinal mistake comparing Stock Android with version 4.1.2 with custom ROM version 7.1.2.
Each of these versions represents a far different operating model in the hardware layer.
But test yourself, if you have enough free time.
Click to expand...
Click to collapse
I'm explaining about bugs exactly. They are simple stupid bugs in the Lineage ROM for Galaxy S2, which people face with.
It is also clear that the ROM developers conceal bugs only instead of fixing they.
I had attached the screenshot to this message, which proofs the bug with a manual inability to enter the current year correctly in a date settings at a portrait mode due to an unwanted limitation of number of years available for choose from.
JaLoou said:
Hello.
It is good that the ROM developer had come here in this topic at least.
First of all I do not offend all people. I help Galaxy S2 users to do not fall in the trap, in which I had falled already after being lured by false messages on the XDA forum about allegedly the existence of good ROM Lineage OS with Android 7.1.2 for i9100...
But the ROM is very buggy actually.
For second, all bugs which I described in this topic do not exist in the Samsung's official firmware for Galaxy S2 but only in Lineage and Lineage related ROMs like Resurrection Remix 5.8.3.
For instance, with Samsung's official firmware I was able to connect to the exact 2 WiFi hot-spots (as in the screenshots published before) and to many more. But with Lineage 14.1 (and RR 5.8.3) I'm unable to connect to the same 2 WiFi hot-spots. This is enough.
It does not matter which security use this 2 WiFi hot-spots. I was able to connect to them before with the Samsung's official firmware Android 4.1.2 and now I'm unable to connect to them with Lineage Android 7.1.2.
Before I was able to enter the proper passwords to them. Now I'm unable to do it.
The WiFi hot-spot 'Net 48' haves the password of 10 symbols length. So, it is not WEP secured exactly. But with Lineage Android 7.1.2 I unable to connect to this hot-spot now but before I was able to connect to this hot-spot with the Samsung's official firmware Android 4.1.2 quickly and without any delays.
Click to expand...
Click to collapse
That's important information you describe about the wifi. Please determine which security and password you are using so we can reproduce the issue. The Name of your sid doesn't matter.
rINanDO said:
That's important information you describe about the wifi. Please determine which security and password you are using so we can reproduce the issue. The Name of your sid doesn't matter.
Click to expand...
Click to collapse
Found the bug! It was introduced in linageos since April 27th. https://github.com/LineageOS/androi...mmit/9663c3179fad5e7de7bf4bf31e40649749f33861
The newly introduced faulty input validation is incorrect for WEP. It should not distinguish hex values or plain characters on input. I will create a fix for this.
Some serious camera apps report clearly about the wrong implementation of Camera2 API in Lineage 14.1 for Galaxy S2. I had attached screenshots to this message for proof it.
Hello.
The bug with entering password for connect to some WiFi hot spots, which about I did reported here few times, this bug was fixed or such reporting was my mistake and I really sorry for that. Now I'm able to connect to the 2 WiFi hot-spots, to which I was unable to connect before. Probably, both WiFi hot-spots are WEP secured with passwords of 10 (decimal) symbols length.
Please, excuse me for disturbance about this bug. Probably, I was mistaken due to I did not know about password lenghts limits to 5 and 10 (decimal) symbols in the WEP.
Very sorry.
But another bugs in the ROM continue to exist and they need to be fixed.
JaLoou said:
Hello.
The bug with entering password for connect to some WiFi hot spots, which about I did reported here few times, this bug was fixed or such reporting was my mistake and I really sorry for that. Now I'm able to connect to the 2 WiFi hot-spots, to which I was unable to connect before. Probably, both WiFi hot-spots are WEP secured with passwords of 10 (decimal) symbols length.
Please, excuse me for disturbance about this bug. Probably, I was mistaken due to I did not know about password lenghts limits to 5 and 10 (decimal) symbols in the WEP.
Very sorry.
But another bugs in the ROM continue to exist and they need to be fixed.
Click to expand...
Click to collapse
It is ok. No bad feelings. The very confusing password length has been removed in the official. It was not in Google's android source anyway and the LOS team has merged my commit.
Other good news, I found a workaround to get the camera scene-mode working! It is possibly a bug in the camera firmware which resets the scenemode when the camera starts streaming. It will be in the next official build. As far as I can reproduce, the actual 'night vision'-mode is fireworks.
rINanDO said:
It is ok. No bad feelings. The very confusing password length has been removed in the official. It was not in Google's android source anyway and the LOS team has merged my commit.
Other good news, I found a workaround to get the camera scene-mode working! It is possibly a bug in the camera firmware which resets the scenemode when the camera starts streaming. It will be in the next official build. As far as I can reproduce, the actual 'night vision'-mode is fireworks.
Click to expand...
Click to collapse
Hello.
The semi night vision trick for videorecording by A Better Camera app is to choose manually ISO800 and then choose the scene mode 'Fireworks'.
For more brightness enhancement you can yet choose the 'Cloudly' white balance preset.
I have an old small app, which updates the camera firmware on i9100. I had attached this app to the message. May it will help to someone.
I'm a noob but I think the problem with A Better Camera app is not in the camera hardware but somewhere close to a memory (RAM or flash). And I will try to explain it:
if I launch A Better Camera app for a first time then it shows a simple introductive help on its screen.
If I close the app and run it again then it does not shows the intro help at next launches. It is ok.
But if I press the home button for long time then I get a list of recent apps on the screen and if I scroll it up and clear all the recents list
then only A Better Camera app loses all its settings and becomes like at its first launch (there an introductive help appears again after the app launch).
This bug was not with the Samsung's official firmware Android 4.1.2.
A Better Camera app can improve the camera of our smartphone significantly for video recordings at low light conditions. Moreover, A Better Camera app provides the best DRO-mode among other camera apps, IMHO. It is like a second life for the old camera of our smartphone. So, please pay attention to fix the bug with A Better Camera app.

Perpetual Infection. Is it possible?

Hi guys, I was just thinking if my PC , from which i read emails sent for my gmail account which is the same account I have on my Android device , gets hacked one day, and the hacker also has some virus app hidden at Play Store, if he could remotely keep installing this virus app at my Android device perpetually , even if I format my device .
Gmail is pretty bullet proof as long as you don't bring in downloads. What's kept in the cloud, stays in the cloud.
Never in over 12 years had a virus infect either Android or Window device via Gmail. Which is why I use it.
Most infections are downloaded or installed by the user including those nasty jpegs and pngs. Had one recently that destroyed files in my downloads folder but never got beyond that.
Perhaps because I discovered it within minutes and was able to isolated it ie delete it.
Simply changing your password after the Android reload would defeat the hacker anyway. Right?
For real paranoia there are viruses that can allegedly escape a reload purge by hiding in what should be immutable areas of the internal memory. Presumably only a firmware reflash could eradicate them.
The SD card is another hiding place...
Keep at least 2 hdd backups of it that are physically and electronically isolated from each other. Enforce this isolation if there is the slightest sign of malware until it's eliminated.
Losing your head with a infected device can destroy your whole data base... got to keep them separated.
It may get one, even two devices but not the isolated hdds unless you screw up bad.
Tks for the reply and for the hints
The reason for my thread was that I got at my new tablet, an adware which would pop up the Google Play Store with the app IQ Option ( a Forex app , from IQ Option ) . The IQ option "pop up" started after installing Netflix , Amazon Prime and... a paid calculator app called Calculator Infinity from Inception Mobile.
I already contacted Samsung which asked me to take the tablet to the repair service, I contacted Google which asked me to take numerous steps which didnt prove succesful, including formating the device.... It has stopped after 2 months, not sure why ( Android update??? Banishment of IQ Option Forex of Brazil due to law transgressions??) . I dont think it was the law enforcement since I saw some cases reporting this virus at another foruns after the banishment of IQ Option... Due to the pandemic, I didnt take the tablet yet to service repair. Planning to do it at march. But I would like some more advices... Dont want to migrate in the future for IOS because of this.
P.S: Ive already flagged the app at the Google Play Store, but Im afraid Im pointing the wrong culrprit... Nothing happened , so maybe Google didnt find anything...
If you reloaded the OS that should be the end of it unless you installed it after the reload or it's in your data that you added after the reload.
It may not be the app(s) you suspect...
Scan with Malwarebytes.
Thats the question, it was a new tablet . I instaled only Netflix, Amazon Prime and when I put this calculator app, the problem started. As soon as the the problem started, I ran the antivirus that comes with Samsung tablet ( McAfee ) , and nothing was detected, I later instaled Avast, nothing was detected, then AVG, nothing was detected again, but the problem continued for 2 months.
@malandrex
Forget all the mentioned scanners and comparable ones: they all are absolutley useless on Android. These scanners all exist for one purpose only: to pull money out of the pocket of fearful Android users like John Doe / Jane Doe
Take note that latest Android versions by default come with AVB ( read: Android Verified Boot ) feature, what prevents any changes can be made to Android's system - of course unless this feature gets disabled by user ( what is a bit complicated because user must know how to modify device's bootloader ).
Knowing this you must not fear Android's system gets infected, IMO.
jwoegerbauer said:
@malandrex
Forget all the mentioned scanners and comparable ones: they all are absolutley useless on Android. These scanners all exist for one purpose only: to pull money out of the pocket of fearful Android users like John Doe / Jane Doe
Take note that latest Android versions by default come with AVB ( read: Android Verified Boot ) feature, what prevents any changes can be made to Android's system - of course unless this feature gets disabled by user ( what is a bit complicated because user must know how to modify device's bootloader ).
Knowing this you must not fear Android's system gets infected, IMO.
Click to expand...
Click to collapse
So what does explain the autonomous opening of Google Play at the app IQ Option on my new Galaxy tab s6 which was acquired at the beginning of 2020? This behavior lasted from february to april and resisted, during this period, inumerous factory resets. Was it caused from an adware installed by the calculator app?? Was an app remotely installed from a PC virus that used the same Google account of the tablet? Or was something else?

My phone came with pre-installed malware, and I'm desperate. What am I supposed to do now?

Hello everyone in the XDA Developers community, how are you? I hope that very good.
I come to you because I am desperate with my phone; Since they gave it to me (yes, this phone is a gift) about 3 or 4 months ago (it is a phone from the Sky Devices brand, more specifically the Sky Devices Platinum 5.0M) I had not noticed anything strange, until a couple of weeks After checking my applications in the phone settings, I noticed a very strange app, which calls itself “App Settings”, it seemed strange to me, but I uninstalled it without further ado, but after a while I check the apps and I realize that the app reappeared without prior notice, to which my alarms go off immediately and I resort to installing the trial version of Kaspersky Internet Security for Android, and after running both a quick scan and a full scan, it detects the Trojan in question (attached screenshots below). What I proceed to do now is to eliminate the Trojan in question with the AV, to which I reassure myself a bit, knowing that the AV "neutralized" the Trojan; I'm still normal, using it, when days later, when I see the recent apps, I see the happy "App Settings" running, to which I deduce that the supposed virus survived, to which I resort to different AVs, such as Malwarebytes and ESET, both without throwing me any results. Tired, I let the matter pass and I don't give it much importance. Now we come to today: I begin to notice that the phone is draining the battery too quickly, apart from the fact that there is something that makes it not recognize the SIM (it is not the phone, because before it recognized it, apart from the fact that the SIM is new), I go to Settings to see the applications and I see that the infection has become worse: there are many more apps of its kind, such as a Flashlight call (I don't use external flashlights, I always use the one on the phone), another call " system service ”, and others that by the logo, I deduce that they come from the first one. My question comes in here: what should I do with the phone, given the evidence of infection? I need your help urgently, because if my phone continues like this, with your forgiveness, I will smash it against the wall without further ado, because this virus has me fed up.
Thank you all and I await your responses.
PS: The Sky Devices brand is from the United States, so it can't be that Chinese.
PS2: It should also be clarified that when I eliminate the virus with Kaspersky, more appear again, I attach screenshots below.
PS3: Yes, I know that this question has nothing to do with development, or ROM's or anything like that, I'm just desperate; this virus has me crazy, and I have also published my problem in the Kaspersky Community Forums, also in HTCMania , and nowhere do they answer me, and all I want is to get rid of this damn virus once and for all.
PS4: BTW, I am from Colombia, that is why in the screenshots that I attached you can see everything in Spanish.
Device Information
Brand: Sky Devices
Reference: Sky Devices Platinum 5.0M
OS installed: Android 7.0 Nougat (Official ROM)
Kaspersky AV version installed: Latest (v11.68.4.5635)

Categories

Resources