Trying to search ("Search: contains") results in a crash as soon as the
third character is keyed.

Anyone else noticed this with v4.0.3?
(see <https://xdaforums.com/t/discussion-muntashirakon-app-manager.4674128/post-90086585>)

There was no problem with v4.0.2.

--
Jeff

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, 27 May 2025 13:48:05 +0100, Jeff Layman wrote :

Trying to search ("Search: contains") results in a crash as soon as the
third character is keyed.

Anyone else noticed this with v4.0.3?
(see <https://xdaforums.com/t/discussion-muntashirakon-app-manager.4674128/post-90086585>)

There was no problem with v4.0.2.

Hi Jeff,
Muntashirakon, as you know, is one of my favorite apps.

I don't generally search in Muntashirakon, so let me run a search.
1. Start App Manager
2. Wait for it to find all the apps
3. Type Google in the search bar

Works fine, Samsung Galaxy A series, Android 13.
My version of Muntashirakon is only 3.1.7(430) though.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 27/05/2025 15:51, Marion wrote:

On Tue, 27 May 2025 13:48:05 +0100, Jeff Layman wrote :

Trying to search ("Search: contains") results in a crash as soon as the
third character is keyed.

Anyone else noticed this with v4.0.3?
(see
<https://xdaforums.com/t/discussion-muntashirakon-app-manager.4674128/post-90086585>)

There was no problem with v4.0.2.

Hi Jeff,
Muntashirakon, as you know, is one of my favorite apps.

I don't generally search in Muntashirakon, so let me run a search.
1. Start App Manager
2. Wait for it to find all the apps
3. Type Google in the search bar

Works fine, Samsung Galaxy A series, Android 13.
My version of Muntashirakon is only 3.1.7(430) though.

Thanks for the reply. I think there's a definite issue with v4.0.3. I
hope a fix appears before too long, but if it doesn't I've just
uninstalled it and replaced it with v4.0.2.

--
Jeff

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Jeff Layman wrote:

Trying to search ("Search: contains") results in a crash as soon as the
third character is keyed.

Anyone else noticed this with v4.0.3?

Still on 3.1.7(430), and I'll leave it alone since other versions were reluctant to run after installation

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, 27 May 2025 17:10:58 +0100, Jeff Layman wrote :

Works fine, Samsung Galaxy A series, Android 13.
My version of Muntashirakon is only 3.1.7(430) though.

Thanks for the reply. I think there's a definite issue with v4.0.3. I
hope a fix appears before too long, but if it doesn't I've just
uninstalled it and replaced it with v4.0.2.

I think Andy and a couple of others are using Muntashirakon, where he's on
a Pixel, as I recall. You've helped me in the past, so while I normally do
not update an app unless I feel there is something in it that I want, I
will update it now and document the steps for others to take.

On Windows, I went to the canonical Muntashirakon site to download it.
<https://github.com/MuntashirAkon/AppManager>
<https://github.com/MuntashirAkon/AppManager/releases/tag/v4.0.3>
<https://github.com/MuntashirAkon/AppManager/releases/download/v4.0.3/AppManager_v4.0.3.apk>
Name: AppManager_v4.0.3.apk
Size: 26982371 bytes (25 MiB)
SHA256: 67E4ECB79BFCC875630923D04FBA60D8AF84CCD838D7A29736B6DD544D0B7DBA

Since Windows & Android share the same mounted drive, it was already
on Android where all I had to do was doubleclick in the mirrored
Android window on the APK to install it.

This updated the existing Muntashirakon to version 4.0.3(443) since the previous one was also from Github so the signing keys matched both.

Then when I started Muntashirakon and let it populate the existing
packages, I ran a search for "goo" & then "goog" & "google", etc.

Unfortunately, it worked.
My system is Android 13, Galaxy A32-5G.

Don't know what to tell you other than to ask Andy to take a swipe.

Sorry I can't help more - but let us know your platform and maybe
someone with a similar device and Android OS can take a look at it.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, 28 May 2025 08:31:19 +0100, Jeff Layman wrote :

Thanks for spending time updating and trying the new version. FWIW, the previous version (v4.0.2) I reinstalled is fine. I tried searching in
the same way that crashed 4.0.3 and it worked without problem. I've
turned off the F-Droid update for the next version, but if 4.0.4 appears
it should notify me that it's available.

Well, also FWIW, Andy had problems a couple of years ago with
Muntashirakon, which he found in something like two or three consecutive versions until Muntashirakon finally ran right for him (which we have to
give him credit for not giving up, 'cuz it was we who talked him into installing it in the first place).

Even I had problems with it at some point where it wouldn't take searches, perhaps similar to your problem as I don't recall the issue - which
magically fixed itself after a couple of versions. I never reported it 'cuz
I operate the Android from the PC so I didn't know if it was just me.

I don't know if you've ever seen it (I hadn't until I had a problem),
but the Muntashirakon App Manager pops up its own crash report box, and offers to send the crash details to the dev. I chose email and if you're interested the main crash info from the body of the email appear below -
at the bottom are my Xiaomi phone details.

Ah. I'd never seen that. I'm generally not one to report bugs DIRECTLY from
my phone because of the privacy issues potentially involved - but - as you
may be aware - I converse with developers on XDA when they're active there.

In fact, the thread you linked to in the OP is a thread I authored, which,
I assume you're aware of. I don't think the developers of Muntashirakon are active though, on XDA (or if they are, I'm not aware of their canonical thread). So my threads "becomes" the canonical thread, I guess.

Thanks for being a good quarterback by throwing the ball to Muntashirakon
to fix. Much appreciated you did that for the team. Luckily, as in the case
of Andy and me, whoever the developer is, he's been actively supporting the
App Manager for quite some time so I have confidence it will be fixed.

As you know, if I had to list the top ten Android apps I have on my system, Muntashirakon is one of them (mainly for debugging packages, but also for creating one-tap homescreen folder shortcuts to Activities inside apps).

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 28/05/2025 02:25, Marion wrote:

On Tue, 27 May 2025 17:10:58 +0100, Jeff Layman wrote :

Works fine, Samsung Galaxy A series, Android 13.
My version of Muntashirakon is only 3.1.7(430) though.

Thanks for the reply. I think there's a definite issue with v4.0.3. I
hope a fix appears before too long, but if it doesn't I've just
uninstalled it and replaced it with v4.0.2.

I think Andy and a couple of others are using Muntashirakon, where he's on
a Pixel, as I recall. You've helped me in the past, so while I normally do not update an app unless I feel there is something in it that I want, I
will update it now and document the steps for others to take.

On Windows, I went to the canonical Muntashirakon site to download it.
<https://github.com/MuntashirAkon/AppManager>
<https://github.com/MuntashirAkon/AppManager/releases/tag/v4.0.3>
<https://github.com/MuntashirAkon/AppManager/releases/download/v4.0.3/AppManager_v4.0.3.apk>
Name: AppManager_v4.0.3.apk
Size: 26982371 bytes (25 MiB)
SHA256: 67E4ECB79BFCC875630923D04FBA60D8AF84CCD838D7A29736B6DD544D0B7DBA

Since Windows & Android share the same mounted drive, it was already
on Android where all I had to do was doubleclick in the mirrored
Android window on the APK to install it.

This updated the existing Muntashirakon to version 4.0.3(443) since the previous one was also from Github so the signing keys matched both.

Then when I started Muntashirakon and let it populate the existing
packages, I ran a search for "goo" & then "goog" & "google", etc.

Unfortunately, it worked.
My system is Android 13, Galaxy A32-5G.

Don't know what to tell you other than to ask Andy to take a swipe.

Sorry I can't help more - but let us know your platform and maybe
someone with a similar device and Android OS can take a look at it.

Thanks for spending time updating and trying the new version. FWIW, the previous version (v4.0.2) I reinstalled is fine. I tried searching in
the same way that crashed 4.0.3 and it worked without problem. I've
turned off the F-Droid update for the next version, but if 4.0.4 appears
it should notify me that it's available.

I don't know if you've ever seen it (I hadn't until I had a problem),
but the Muntashirakon App Manager pops up its own crash report box, and
offers to send the crash details to the dev. I chose email and if you're interested the main crash info from the body of the email appear below -
at the bottom are my Xiaomi phone details.

============================================================= java.lang.IndexOutOfBoundsException: Inconsistency detected. Invalid
item position 5(offset:-1).state:10 io.github.muntashirakon.widget.RecyclerView{86eadd7 VFED..... ......ID 0,0-1080,2110 #7f0901e0 app:id/item_list aid=1073741827}, adapter:io.github.muntashirakon.AppManager.main.MainRecyclerAdapter@1def451, layout:io.github.muntashirakon.view.AutoFitGridLayoutManager@b61b6c4, context:io.github.muntashirakon.AppManager.main.MainActivity@a9e7614

at androidx.recyclerview.widget.RecyclerView$Recycler.tryGetViewHolderForPositionByDeadline(RecyclerView.java:6821)
at androidx.recyclerview.widget.RecyclerView$Recycler.getViewForPosition(RecyclerView.java:6757
...
(another 61 lines beginning with "at" appear here - if you're interested
I can post them)

Device Info:
App version: 4.0.3
App version code: 443
Android build version: V14.0.5.0.TKSEUVF
Android release version: 13
Android SDK version: 33
Android build ID: TP1A.220624.014
Device brand: Redmi
Device manufacturer: Xiaomi
Device name: camellian
Device model: M2103K19G
Device product name: camellian_eea
Device hardware name: mt6833
ABIs: [arm64-v8a, armeabi-v7a, armeabi]
ABIs (32bit): [armeabi-v7a, armeabi]
ABIs (64bit): [arm64-v8a]
System language: en-GB
In-App Language: auto
Mode: no-root
Inferred Mode: No root =============================================================

--
Jeff

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, 27 May 2025 17:02:19 +0100, Andy Burns wrote :

Trying to search ("Search: contains") results in a crash as soon as the
third character is keyed.

Anyone else noticed this with v4.0.3?

Still on 3.1.7(430), and I'll leave it alone since other versions were reluctant to run after installation

Funny story. It wasn't crashing the day I tested it, but now it's crashing
as soon as I get to the third letter in a search in Muntashirakon.

It's exactly what Jeff was seeing in 4.0.3 (443) which is the same version.
I cleared the cache & data but it still crashed at the third letter.

Crash log below.
I checked for a later version:
<https://github.com/MuntashirAkon/AppManager>

Looks like there is a version 4.0.4 released 3 days ago. https://github.com/MuntashirAkon/AppManager/releases/tag/v4.0.4

Release notes say "Prevent crashing while searching".
That's got to be what Jeff found.

So I downloaded the new version. https://github.com/MuntashirAkon/AppManager/releases/download/v4.0.4/AppManager_v4.0.4.apk
Name: AppManager_v4.0.4.apk
Size: 26986467 bytes (25 MiB)
SHA256: 225F95474CFFE2C4DBB264E7C4555DC2E7155DE71A77DD78B69C5662E112DDA7

It works now.
Muntashirakon is the best app manager (by far) on Android!

CRASH LOG OF 4.0.3

java.lang.IndexOutOfBoundsException: Inconsistency detected. Invalid item position 5(offset:-1).state:9 io.github.muntashirakon.widget.RecyclerView{cf966f9 VFED..... ......ID 0,0-720,1411 #7f0901e0 app:id/item_list aid=1073741826}, adapter:io.github.muntashirakon.AppManager.main.MainRecyclerAdapter@aaa60c1, layout:io.github.muntashirakon.view.AutoFitGridLayoutManager@9787948, context:io.github.muntashirakon.AppManager.main.MainActivity@13d1ce2
at androidx.recyclerview.widget.RecyclerView$Recycler.tryGetViewHolderForPositionByDeadline(RecyclerView.java:6821)
at androidx.recyclerview.widget.RecyclerView$Recycler.getViewForPosition(RecyclerView.java:6757)
at androidx.recyclerview.widget.RecyclerView$Recycler.getViewForPosition(RecyclerView.java:6753)
at androidx.recyclerview.widget.LinearLayoutManager$LayoutState.next(LinearLayoutManager.java:2362)
at androidx.recyclerview.widget.GridLayoutManager.layoutChunk(GridLayoutManager.java:584)
at androidx.recyclerview.widget.LinearLayoutManager.fill(LinearLayoutManager.java:1622)
at androidx.recyclerview.widget.LinearLayoutManager.onLayoutChildren(LinearLayoutManager.java:687)
at androidx.recyclerview.widget.GridLayoutManager.onLayoutChildren(GridLayoutManager.java:182)
at io.github.muntashirakon.view.AutoFitGridLayoutManager.onLayoutChildren(AutoFitGridLayoutManager.java:44)
at androidx.recyclerview.widget.RecyclerView.dispatchLayoutStep1(RecyclerView.java:4591)
at androidx.recyclerview.widget.RecyclerView.dispatchLayout(RecyclerView.java:4346)
at androidx.recyclerview.widget.RecyclerView.onLayout(RecyclerView.java:4919)
at android.view.View.layout(View.java:24969)
at android.view.ViewGroup.layout(ViewGroup.java:6784)
at androidx.swiperefreshlayout.widget.SwipeRefreshLayout.onLayout(SwipeRefreshLayout.java:704)
at android.view.View.layout(View.java:24969)
at android.view.ViewGroup.layout(ViewGroup.java:6784)
at com.google.android.material.appbar.HeaderScrollingViewBehavior.layoutChild(HeaderScrollingViewBehavior.java:149)
at com.google.android.material.appbar.ViewOffsetBehavior.onLayoutChild(ViewOffsetBehavior.java:43)
at com.google.android.material.appbar.AppBarLayout$ScrollingViewBehavior.onLayoutChild(AppBarLayout.java:2365)
at androidx.coordinatorlayout.widget.CoordinatorLayout.onLayout(CoordinatorLayout.java:918)
at android.view.View.layout(View.java:24969)
at android.view.ViewGroup.layout(ViewGroup.java:6784)
at android.widget.FrameLayout.layoutChildren(FrameLayout.java:332)
at android.widget.FrameLayout.onLayout(FrameLayout.java:270)
at android.view.View.layout(View.java:24969)
at android.view.ViewGroup.layout(ViewGroup.java:6784)
at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1829)
at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1673)
at android.widget.LinearLayout.onLayout(LinearLayout.java:1582)
at android.view.View.layout(View.java:24969)
at android.view.ViewGroup.layout(ViewGroup.java:6784)
at android.widget.FrameLayout.layoutChildren(FrameLayout.java:332)
at android.widget.FrameLayout.onLayout(FrameLayout.java:270)
at android.view.View.layout(View.java:24969)
at android.view.ViewGroup.layout(ViewGroup.java:6784)
at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1829)
at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1673)
at android.widget.LinearLayout.onLayout(LinearLayout.java:1582)
at android.view.View.layout(View.java:24969)
at android.view.ViewGroup.layout(ViewGroup.java:6784)
at android.widget.FrameLayout.layoutChildren(FrameLayout.java:332)
at android.widget.FrameLayout.onLayout(FrameLayout.java:270)
at com.android.internal.policy.DecorView.onLayout(DecorView.java:1431)
at android.view.View.layout(View.java:24969)
at android.view.ViewGroup.layout(ViewGroup.java:6784)
at android.view.ViewRootImpl.performLayout(ViewRootImpl.java:4917)
at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:4240)
at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:3116)
at
android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:10885)
at
android.view.Choreographer$CallbackRecord.run(Choreographer.java:1301)
at
android.view.Choreographer$CallbackRecord.run(Choreographer.java:1309)
at android.view.Choreographer.doCallbacks(Choreographer.java:923)
at android.view.Choreographer.doFrame(Choreographer.java:852)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1283)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.app.ActivityThread.main(ActivityThread.java:8762)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 03/06/2025 20:09, Marion wrote:

On Tue, 27 May 2025 17:02:19 +0100, Andy Burns wrote :

Trying to search ("Search: contains") results in a crash as soon as the
third character is keyed.

Anyone else noticed this with v4.0.3?

Still on 3.1.7(430), and I'll leave it alone since other versions were
reluctant to run after installation

Funny story. It wasn't crashing the day I tested it, but now it's crashing
as soon as I get to the third letter in a search in Muntashirakon.

It's exactly what Jeff was seeing in 4.0.3 (443) which is the same version.
I cleared the cache & data but it still crashed at the third letter.

Crash log below.
I checked for a later version:
<https://github.com/MuntashirAkon/AppManager>

Looks like there is a version 4.0.4 released 3 days ago. https://github.com/MuntashirAkon/AppManager/releases/tag/v4.0.4

Thanks for the heads-up. It hasn't appeared in F-Droid yet, but there's
no hurry. I only disabled the F-Droid update to 4.0.3 after reinstalling
4.0.2, so I expect that F-Droid will notify me when 4.0.4 appears there.

Release notes say "Prevent crashing while searching".
That's got to be what Jeff found.

Looks like it. Perhaps it was my crash report email to the dev which
resulted in the new update, but even if it wasn't it shows how quickly
the dev is dealing with problems. If only all devs reacted so quickly...

So I downloaded the new version. https://github.com/MuntashirAkon/AppManager/releases/download/v4.0.4/AppManager_v4.0.4.apk
Name: AppManager_v4.0.4.apk
Size: 26986467 bytes (25 MiB)
SHA256: 225F95474CFFE2C4DBB264E7C4555DC2E7155DE71A77DD78B69C5662E112DDA7

It works now.
Muntashirakon is the best app manager (by far) on Android!

Have you tried anything else of his, such as the Android Debloat List?

--
Jeff

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thu, 5 Jun 2025 13:17:41 +0100, Jeff Layman wrote :

Looks like there is a version 4.0.4 released 3 days ago.
https://github.com/MuntashirAkon/AppManager/releases/tag/v4.0.4

Thanks for the heads-up. It hasn't appeared in F-Droid yet, but there's
no hurry. I only disabled the F-Droid update to 4.0.3 after reinstalling 4.0.2, so I expect that F-Droid will notify me when 4.0.4 appears there.

Thanks for updating the thread as I was worried you might not have been checking it. I'm confused why I didn't see the problem initially, but it
was reproduceable every search when it got to the third letter.

I generally don't use the F-Droid app for two reasons, one of which is that F-Droid Basic is generally considered to be updated more often, but the
other of which is that I use a web browser on Windows to get my open source tools, where F-Droid's repository, thankfully, is open to web browsers.
<https://f-droid.org/packages/org.fdroid.basic/>

As you likely are well aware, due to signature tests, I think, if you want
to "update" (versus delete & install) then you have to use the same repo
for the update that you used for the package that you're updating.

Release notes say "Prevent crashing while searching".
That's got to be what Jeff found.

Looks like it. Perhaps it was my crash report email to the dev which
resulted in the new update, but even if it wasn't it shows how quickly
the dev is dealing with problems. If only all devs reacted so quickly.

Agree. I find Muntashirakon, Aurora, NewPipe & Skyica developers to be very responsive to bugs, which is a nice thing about these non-mainstream apps.

So I downloaded the new version.
https://github.com/MuntashirAkon/AppManager/releases/download/v4.0.4/AppManager_v4.0.4.apk
Name: AppManager_v4.0.4.apk
Size: 26986467 bytes (25 MiB)
SHA256: 225F95474CFFE2C4DBB264E7C4555DC2E7155DE71A77DD78B69C5662E112DDA7 >>
It works now.
Muntashirakon is the best app manager (by far) on Android!

Have you tried anything else of his, such as the Android Debloat List?

Long ago I tested all the free app managers and settled on Muntashirakon as
the best, not the least because it doesn't truncate long package names.

Then I found out that it can make creating one-tap shortcuts to public activities a breeze, and I started also using it to evaluate software.

Muntashirakon can tell you software trackers, for example, but it turns out
I'm not a bad judge of software so I rarely keep software with trackers
(unless they're the only game in town, such as with cartoonify AI apps).

Even if you have apps with trackers, Muntashirakon has an option in the debloating GUI to "Block/unblock trackers" for all selected apps.

Also, Muntashirakon tells you, in red or pink, depending on the severity,
what it considers an unsafe app, or if it can "open links", which is a nice feature since you can check every app just after you install it.

I generally do not run the Muntashirakon debloater since I have a Samsung
and all the adb debloating commands are readily availble on the net, but I
just checked it just now, and it found a lot of apps it wants me to
debloat, where I was surprised how many there were still left.

About half (roughly) said "Safe to remove" in green, and the other half
said "Exercise caution" in orange. Some said "Replace with alternative" in purpose.

Examples of "Replace with alternative" were...
Tags <com.android.apps.tag>
CarrierConfig <com.android.carrierconfig>
One Handed Mode <com.android.internal.systemui.onehanded.gestural
Maps <com.google.android.apps.maps>
Google Calendar Sync <com.google.android.syncadapters.calendar>
etc.

Examples of "Safe to Remove" were...
Bluetooth MIDI Service <com.android.bluetoothmidiservice>
Call Log Backup/Restore <com.android.callogbackup>
CTSSHIM <com.android.cts.ctsshim>
Basic Daydreams <com.android.dreams.basic>
Photo Screensavers <com.android.dreams.phototable>
etc.

Examples of "Exercise caution" were...
Dynamic System Updates <comp.android.dynsystem>
OSULogin <com.android.hotspot2.osulogin>
HTML Viewer <com.android.htmlviewer>
Input Devices <com.android.inputdevices>
Phone services <com.android.phone>
etc.

Some of the "Exercise Caution" list had explanations, such as...
Work Setup <com.android.managedprovisioning> "Needed for sandbox apps such
as Shelter or Insular/Island".

It could be an entire thread in and of itself what to do with each of those apps. For example, I just hit "block/unblock trackers" for all those apps
which showed up in the debloating list. I'll let you know what happens if something negative occurs.

We could have an entire newsgroup on Muntashirakon alone. :)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)