New issue for my suggestion made in #145 :

I thought about something about widget, why not offer a second page, at left or right, for add some widget. KISS is very efficient to access app but sometime there is some widget that is really more fast. I think to an agenda widget for displaying all next events. It could be faster to swipe left or right to see it than open agenda app.

The main reason I think this would be useful is because a lot of icon packs don't apply the icons to certain applications unless the name is exactly the same.

For example, with the browser Lightning, only the generic Play Store version gets the icon changed and not the Lightning+/F-Droid version. Other launchers such as Nova have this option to manually change the icon but I've noticed that KISS does not, even though it's superior in every other conceivable way.

Hopefully I'm not the only one that would be interested in this and it will be implemented in the future.

Hey, I tried different widgets (calendars and messengers) and love the feature, but most of them are useless, because they don't update. They always show whatever they showed when I added them.

fix #752

WIP, do not merge

I need some feedback and help ;)

• [x] Get the name from the widget to display in the popup
• [x] Custom widget position and size
• [x] Scroll with the wallpaper
• [ ] Long press widget to enter edit mode
• [ ] Visual / drag&drop resize and position
• [ ] Grid placement option
• [ ] Allow for separate grid sizes for each screen / page
• [ ] Add padding that may be negative to better position the widget in the grid
• [ ] Re-add widget every X minutes on Oreo to force update the widget (will fix the clock widgets not updating)
• [ ] Test that every option works as expected

I own a Xiaomi Redmi Note 9 Pro Global Version (MIUI 12.5.8), once I've enabled the minimalistic interface that allows me to add widgets, I succesfully added a weather widget that still works fine, it still can be resized but if I try to add another widget the app simply does nothing.

Similar thing happened with the same phone configuration using the debug 3.17.0 .apk file: I've managed to add a widget but once I removed it I was unable to add it again or to add any other widget, I'll attach a gif for more context.

Steps to reproduce the behavior:

1. Go to the 3 dots menu
2. Click on "Add a Widget"
3. Select a Widget from the menu
4. Nothing happens

Expected behavior I expect the widgets to appear on my home screen

Screenshots

Additional information

• App version: 3.17.0
• App installed via: F-Droid:

Additional context If requested I can share my trace files

Hello, First of all many thanks for this great Launcher. I installed the beta release in order ti have a widget. It worked great until latest update (2.31.1). After update widget disappeared and there isn't any way to activate It anymore through the 3 dots menu.

Thanks Francesco

As far as I understand, the search function orders the results in a way that should be most relevant to the user. Could we have an option to apply a similar logic to the history, so that the elements can be also weighted by relevancy? For example, apps that are used often could fall back in history slower than others.

Hello everyone!

The Play Store / fDroid description have been there for 5 years now (KISS will soon be 9 years old! We built so much since this scrawny app built on Eclipse started on a689af79).

With @saveman71, @Amoki and @geekuillaume we worked on a new version, here is our current proposition:

https://github.com/Neamar/KISS/blob/00a4238692f8a3911f5bcf6fa1aff62cdca00130/fastlane/metadata/android/en-US/full_description.txt#L1-L23

Do you feel we're missing something? None of us are English native, is there anything that sounds incorrect?

We also updated the screenshots, see https://github.com/Neamar/KISS :)

(I've asked Weblate to add a new component for Fastlane, we'll be able to translate this in all the languages we collectively talk!) (and @saveman71 built a tool in #1479 to localize the screenshots too :heart:)

In LoadContactsPojos.java the field "homeNumber" is set true, if the contacts phone number starts with "+33\s?[1-5]" (which is specific for france, I guess). Depending on the value of "homeNumber" the send message button in the contacts view is hidden or shown.

A solution usable in other countries would be nice here.

TelephonyManager provides some info on the surrounding of the phone. But no drop-in solution.

Maybe we have to manually collect regexes for home number detection per country?

Hi,

As you can see in the screenshot, KISS searches for the letter input, but doesn't display them in the search bar:

I'm on Android 4.2.2, using a Fairphone FP1 (Full specifications see here).

In CatLog I searched for "KISS". This is the output:

08-24 16:35:04.917 I/ActivityManager(502): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=fr.neamar.kiss/.MainActivity} from pid 502
08-24 16:35:04.993 I/BufferQueue(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dbd688,api:0) setConsumerName: fr.neamar.kiss/fr.neamar.kiss.MainActivity
08-24 16:35:05.005 I/BufferQueue(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dbd688,api:0) connect: api=1
08-24 16:35:05.005 I/BufferQueue(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dbd688,api:1) setSynchronousMode: enabled=1
08-24 16:35:05.005 I/BufferQueue(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dbd688,api:1) setSynchronousMode: enabled=1
08-24 16:35:05.005 I/WindowManager(502): Gaining focus: Window{41f8bcf0 u0 fr.neamar.kiss/fr.neamar.kiss.MainActivity}
08-24 16:35:05.008 I/BufferQueue(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dbd688,api:1) new GraphicBuffer needed
08-24 16:35:05.100 I/BufferQueue(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dbd688,api:1) new GraphicBuffer needed
08-24 16:35:05.108 I/SurfaceTexture(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dc4960,api:1) [void* android::SurfaceTexture::createImage(EGLDisplay, const android::sp<android::GraphicBuffer>&)]
08-24 16:35:05.272 I/BufferQueue(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dbd688,api:1) new GraphicBuffer needed
08-24 16:35:05.280 I/SurfaceTexture(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dc4960,api:1) [void* android::SurfaceTexture::createImage(EGLDisplay, const android::sp<android::GraphicBuffer>&)]
08-24 16:35:05.324 I/BufferQueue(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dbd688,api:1) new GraphicBuffer needed
08-24 16:35:05.327 I/SurfaceTexture(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dc4960,api:1) [void* android::SurfaceTexture::createImage(EGLDisplay, const android::sp<android::GraphicBuffer>&)]
08-24 16:35:06.186 I/BufferQueue(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dbd688,api:1) [queue] fps:2.76, dur:1087.41, max:862.13, min:51.61
08-24 16:35:06.197 I/SurfaceTexture(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dc4960,api:1) [void* android::SurfaceTexture::createImage(EGLDisplay, const android::sp<android::GraphicBuffer>&)]
08-24 16:35:07.439 I/BufferQueue(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dbd688,api:1) [queue] fps:1.60, dur:1252.70, max:1173.49, min:79.21
08-24 16:35:07.448 I/BufferQueue(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dbd688,api:1) [release] fps:1.85, dur:2167.91, max:1172.68, min:47.32
08-24 16:35:08.311 I/WindowManager(502): Losing focus: Window{41f8bcf0 u0 fr.neamar.kiss/fr.neamar.kiss.MainActivity}
08-24 16:35:08.553 I/BufferQueue(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dbd688,api:1) disconnect: api=1
08-24 16:35:08.553 I/SurfaceTexture(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity] [virtual android::status_t android::SurfaceTexture::forceAuxConversionLocked()] mCurrentTexture:2, mCurrentBuf:0x41dc5908
08-24 16:35:08.553 I/BufferQueue(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dbd688,api:0) getReleasedBuffers: returning mask 0xffffffff
08-24 16:35:08.553 I/SurfaceTexture(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dc4960,api:0) destroying EGLImage dpy=0x1 img=0x41dca728
08-24 16:35:08.553 I/SurfaceTexture(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dc4960,api:0) destroying EGLImage dpy=0x1 img=0x41e5c750
08-24 16:35:08.553 I/SurfaceTexture(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dc4960,api:0) destroying EGLImage dpy=0x1 img=0x423e9460
08-24 16:35:08.553 I/SurfaceTexture(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dc4960,api:0) destroying EGLImage dpy=0x1 img=0x41dbe858
08-24 16:35:08.815 I/BufferQueue(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dbd688,api:0) consumerDisconnect
08-24 16:35:08.815 I/BufferQueue(130): [fr.neamar.kiss/fr.neamar.kiss.MainActivity](this:0x41dbd688,api:0) ~BufferQueue</code>

• app version 3.7.5 (from fdroid)
• android version P
• device used Xiaomi Redmi Note 5 Pro (whyred) and Xiaomi Mi Max 3 (nitrogen)
• custom settings that might have an impact: no idea (tried with and without the "root option" and with and without the "widget option") nothing changed

I use on both phones custom ROMs based on aosp (havoc os and cosp).

Other that displaying the briefcase badge on work profile app icons, KISS doesn't really do much to differentiate work apps from personal apps.

At the moment I assign a "work" tag to all my work apps manually and make this available in the menu to quickly filter for work apps.

It feels like there could be a few possible improvements here that would make identifying work apps easier.

1. Having a tag e.g. "work" assigned to all work profile apps automatically, so I don't need to remember to manage this tag when installing new work apps
2. Displaying greyed out work apps icons in the search and app list when the work profile isn't active
3. Some control around whether work apps should be displayed in the app list or when searching based on whether the work profile is on/off, possibly combined with a quick toggle in the menu to turn the work profile on/off fron there
4. Some kind of different icon shape or color to make it obvious which app belongs to a work profile when there are duplicates e.g. Google play store may appear twice, one for each profile

First of all, sorry for not reporting earlier (when 3.17.0 released). The crash still occurs in 3.17.1.

Describe the crash When scrolling through app list (main one or after search), certain apps icons do not show up and KISS end up crashing. Also, the scrolling became quite stuttering when moving over certain apps.

To Reproduce Fresh install, default settings. Contacts access allowed or disabled, no matter what. Just click the main circle button and scroll up through apps list.

Stack trace

FATAL EXCEPTION: main Process: fr.neamar.kiss, PID: 4113 java.lang.RuntimeException: Canvas: trying to draw too large(112741924bytes) bitmap. at android.graphics.RecordingCanvas.throwIfCannotDraw(RecordingCanvas.java:266) at android.graphics.BaseRecordingCanvas.drawBitmap(BaseRecordingCanvas.java:94) at android.graphics.drawable.BitmapDrawable.draw(BitmapDrawable.java:549) at android.widget.ImageView.onDraw(ImageView.java:1446) at android.view.View.draw(View.java:23195) at android.view.View.updateDisplayListIfDirty(View.java:22062) at android.view.View.draw(View.java:22926) at android.view.ViewGroup.drawChild(ViewGroup.java:4529) at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4290) at android.view.View.updateDisplayListIfDirty(View.java:22053) at android.view.View.draw(View.java:22926) at android.view.ViewGroup.drawChild(ViewGroup.java:4529) at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4290) at android.view.View.updateDisplayListIfDirty(View.java:22053) at android.view.View.draw(View.java:22926) at android.view.ViewGroup.drawChild(ViewGroup.java:4529) at android.widget.ListView.drawChild(ListView.java:3613) at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4290) at android.widget.AbsListView.dispatchDraw(AbsListView.java:2699) at android.widget.ListView.dispatchDraw(ListView.java:3608) at android.view.View.draw(View.java:23198) at android.widget.AbsListView.draw(AbsListView.java:4453) at android.view.View.updateDisplayListIfDirty(View.java:22062) at android.view.View.draw(View.java:22926) at android.view.ViewGroup.drawChild(ViewGroup.java:4529) at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4290) at android.view.View.draw(View.java:23198) at android.view.View.updateDisplayListIfDirty(View.java:22062) at android.view.View.draw(View.java:22926) at android.view.ViewGroup.drawChild(ViewGroup.java:4529) at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4290) at android.view.View.updateDisplayListIfDirty(View.java:22053) at android.view.View.draw(View.java:22926) at android.view.ViewGroup.drawChild(ViewGroup.java:4529) at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4290) at android.view.View.updateDisplayListIfDirty(View.java:22053) at android.view.View.draw(View.java:22926) at android.view.ViewGroup.drawChild(ViewGroup.java:4529) at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4290) at android.view.View.updateDisplayListIfDirty(View.java:22053) at android.view.View.draw(View.java:22926) at android.view.ViewGroup.drawChild(ViewGroup.java:4529) at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4290) at android.view.View.draw(View.java:23198) at com.android.internal.policy.DecorView.draw(DecorView.java:819) at android.view.View.updateDisplayListIfDirty(View.java:22062) at android.view.ThreadedRenderer.updateViewTreeDisplayList(ThreadedRenderer.java:682) at android.view.ThreadedRenderer.updateRootDisplayList(ThreadedRenderer.java:688) at android.view.ThreadedRenderer.draw(ThreadedRenderer.java:786) at android.view.ViewRootImpl.draw(ViewRootImpl.java:4579) at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:4290) at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:3517) at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:2286) at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:8948) at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1231) at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1239) at android.view.Choreographer.doCallbacks(Choreographer.java:899) at android.view.Choreographer.doFrame(Choreographer.java:832) at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1214) at android.os.Handler.handleCallback(Handler.java:942) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loopOnce(Looper.java:201) at android.os.Looper.loop(Looper.java:288) at android.app.ActivityThread.main(ActivityThread.java:7898) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)

Is your feature request related to a problem? Please describe. I'm always frustrated when the app is in normal,non-milimalistic mode and I cant double tap lock the screen.

If we have small sized history ,so that there's some empty space on upper part of the screen,we can click on them for some gestures.

Issue Having installed a larger number of websearch strings (Brave, Google, Google Maps, Takoboto, LEO etc. ), the options from which to choose quickly get cluttered, especially since there is no clear separation between websearches and other results (app shortcuts for instance).

Suggested solution A visual separation of websearch options from other results. This could be a different font, or a separate space with horizontal scrolling (either above the search bar or at the top of the screen). But basically any way of separation would work.

Benefit Increased speed/productivity

Example for solution Kvaesitso does this quite well, with websearches having a smaller, bold font, with horizontal scrolling attached to the search bar. I like the KISS approach better in basically everything else (simplicity, list view, etc.), which is why I am suggesting this feature.

A small gripe I have is that I don't like "adaptive" icons, since they're made to be all the same shape and I struggle to differentiate between them when scrolling a list.

Most apps I've encountered have a "legacy" icon which is displayed when installing on android versions below 8 (Oreo), or when displayed in launchers that don't support adaptive icons, and I'd like to be able to click a toggle to force this behaviour in KISS. Alternatively, the toggle could display only the foreground part of the adaptive icon, or maybe a mix of both, falling back to "foreground only" if a "legacy" icon is not available

I have tried using icon packs and themes to solve this problem, but naturally this only fixes the icons for popular apps. Nova Launcher supports this feature, but as good as it is, Nova doesn't suit all my preferences.

Unfortunately I'm not able to contribute code at this time, while I'm familiar with programming, I'm not competent (or confident) enough to try and make this myself.