Database Users

[Guide] Expanding the limit of multitouch points (root needed)

Let's cut the crap. Seems like somebody on a Chinese forum figured out the way to apply the mod to MM2. I just translate it into English.
1. Download the attachment and unzip milestone2_more.ko to the root of sd
2. mount /system/ r/w
3. copy milestone2_more.ko to /system/lib/modules/
4. open terminal emulator
5. input the following command
su
chmod 644 /system/lib/modules/milestone2_more.ko
insmod /system/lib/modules/milestone2_more.ko touch_num=6
(the guy said if you choose a number greater than 6 the system will crash)
now you should get a 6-point-multitouch
original thread: http://bbs.gfan.com/android-1997547-1-1.html

Thank you soooooooo much! )))

Works but MT is still buggy...

oh my god.. thank you, it works.
5 is more than enough

OMG!! You made my day!
Sent from my A953 using XDA Premium App

Is this permanent? Or it'll go away when we reboot?
Sent from my A953 using XDA App

It will go away when you reboot, but its not a big deal to use the command again
Sent from my A953 using XDA Premium App

Just make a init.d script to load it up when the system boots and you won't have to worry about it again..

Just did this, but I think i wrote it wrong. Please correct me
I created a blank file and wrote inside it:
insmod /system/lib/modules/multitouchfix.ko (I replaced the name)
And saved the file as 99multitouchfix inside /system/etc/init.d/
I also fixed permissions for both files
Sent from my A953

Is it working Aragorn?

Thank you. I'll try it when I get home!

inheme said:
Is it working Aragorn?
Click to expand...
Click to collapse
Nope. The module works, but not the init.d script

you can use autostart from Market

AragornPE said:
Nope. The module works, but not the init.d script
Click to expand...
Click to collapse
Try this script:
Code:
#!/system/bin/sh
# Load 5 finger multitouch module
insmod /system/lib/modules/defy_more.ko
Also note that the first touch after reboot is delayed.

dangpzanco said:
Try this script:
Code:
#!/system/bin/sh
# Load 5 finger multitouch module
insmod /system/lib/modules/defy_more.ko
Also note that the first touch after reboot is delayed.
Click to expand...
Click to collapse
I'll try that as soon as my M2 wakes up, long day for it today =P

Actually,the patch is developed by korean , the XDA thread is http://forum.xda-developers.com/showthread.php?t=1162327
Autoload after reboot: copy install-recovery.sh to /system/etc and set rwxr-xr-x .
If you wanna change the touch point limit , open install-recovery.sh with text editor , change the number that follows "touch_num=". The range is 1~10.
My own test shows more than 6 touch points will NOT lead to system crash , but make it back to 2 points...orz. Since the same patch on D2/D2G/DEFY enable up to 10 points, why
m2 cound not
Ah, forgot to say , the autoload patch is ported from http://bbs.gfan.com/android-1997547-1-1.html

Neither autostart or init.d script worked. Going to try the install recovery
Sent from my A953

Install recovery didn't work either
Maybe I'm doing something wrong?
Sent from my A953

AragornPE said:
Neither autostart or init.d script worked. Going to try the install recovery
Sent from my A953
Click to expand...
Click to collapse
Did you set the permission properly，both milestone2_more.ko and install.sh.

All works fine, both the milestone2_more.ko and the install recovery, no problem at all, have 4 MT points now

ATT 2.3.5 SystemUI Quickpanel

ATT 2.3.5 SystemUI
quickpanel_title_background.9 I Can not define

This is nice!
A few suggestions:
- Less icon spacing. Should fit at least 5 on the screen at once.
- No vibrate icon. It's unnecessary. Holding the power button works fine.
- Brightness control.

Thank you. Well done
Sent from my MB860 using Tapatalk

Hi can I install this on rooted locked atrix on 2.3.4!? I'm on UK retail. The thanks
Sent from my MB860 using XDA App

Wow. This is what I wanted.
Thank you

I'm on a rooted US ATT 2.3.4. How can I get this to install? I tried abd install, that didn't work...
--Q
EDIT: I think I figured it out. You have to go into /system/app and rename SystemUI.apk and SystemUI.odex to have .bak then copy the modified SystemUI.apk and then chmod 644 it. Rebooting now...will keep you posted!
EDIT2: Yep! Totally worked! GENIUS!! THANKS!

Do I really need to use adb or can do chmod by using some tool on phone?
Sent from my MB860 using XDA App

You can do all this with Root Explorer if you have it. Same idea.

I think the OP is trying to edit the SystemUI.apk to include more functions. If so, may take a look here. Not sure if that will help too much or not...?
for the other posting people, here's what I have been running for a while..
basically Darkside's stock SystemUI with a theme hacked together from thread mentioned above as well. MIUI Icon set I think is what he says...
To install:
Download file to C: or where ever(if downloaded to someplace else, fix path in the commands below).
Start Menu --> Run --> cmd
On Windows 7 (or XP): hold the Windows Key on keyboard and press R together. Input CMD and hit OK
On Linux: well, you know whats up
On MAC: unplug the computer and toss it out the window.. j/k. This wont work for you though. Follow normal procedure to use ADB in your teminal
Inside CMD Prompt, in this order:
adb push C:\SystemUI.apk /sdcard/SystemUI.apk
adb shell
su
/bin/mount -o remount,rw /system
cp /sdcard/SystemUI.apk /system/app/SystemUI.apk
chmod 644 /system/app/SystemUI.apk
exit
exit
adb reboot

Lack of ability to use a lot of smali. Or else can do more...

ein1002 said:
Lack of ability to use a lot of smali. Or else can do more...
Click to expand...
Click to collapse
I love the last one you've posted.
But could you please replace the vibration by the luminisity control?
And the order would be:
Wifi; Mobile DATA; Bluetooth; GPS, Brightness, Screen Orientation

Shaydar said:
I love the last one you've posted.
But could you please replace the vibration by the luminisity control?
And the order would be:
Wifi; Mobile DATA; Bluetooth; GPS, Brightness, Screen Orientation
Click to expand...
Click to collapse
I have no way to make the right moves Brightness：（
So I removed the BrightnessSettingButton
Leaving only the image resources
Hope someone can fix. And add this part.
sorry. My English is not good

Thanks, It does not matter anyway.
The Screen is so bright that I always set the brightness to its lowest.

malfuncion said:
I think the OP is trying to edit the SystemUI.apk to include more functions. If so, may take a look here. Not sure if that will help too much or not...?
for the other posting people, here's what I have been running for a while..
basically Darkside's stock SystemUI with a theme hacked together from thread mentioned above as well. MIUI Icon set I think is what he says...
To install:
Download file to C: or where ever(if downloaded to someplace else, fix path in the commands below).
Start Menu --> Run --> cmd
On Windows 7 (or XP): hold the Windows Key on keyboard and press R together. Input CMD and hit OK
On Linux: well, you know whats up
On MAC: unplug the computer and toss it out the window.. j/k. This wont work for you though. Follow normal procedure to use ADB in your teminal
Inside CMD Prompt, in this order:
adb push C:\SystemUI.apk /sdcard/SystemUI.apk
adb shell
su
/bin/mount -o remount,rw /system
cp /sdcard/SystemUI.apk /system/app/SystemUI.apk
chmod 644 /system/app/SystemUI.apk
exit
exit
adb reboot
Click to expand...
Click to collapse
Many many thanks! This needs to be in new thread. please post it or I will.
I really liked the darkside ROM, But I soft bricked my phone at least 15 times trying Arabic letters connecting solutions under 2.3.5. So I flashed the Aura ROM missing the quick panel from the Darkside ROM the most.
Not only I have the quick panel now with Aura 2.3.4, the icons also look cleaner/better.
Great job. Thanks to you and Nottach also!

CyberPunk7t9 said:
Many many thanks! This needs to be in new thread. please post it or I will.
I really liked the darkside ROM, But I soft bricked my phone at least 15 times trying Arabic letters connecting solutions under 2.3.5. So I flashed the Aura ROM missing the quick panel from the Darkside ROM the most.
Not only I have the quick panel now with Aura 2.3.4, the icons also look cleaner/better.
Great job. Thanks to you and Nottach also!
Click to expand...
Click to collapse
Any chance you upload your version and share it? I'm looking for exactly the same thing and sadly 2.3.5 Darkside ain't providing that.
Sent from my Atrix 4g using Tapatalk

Abu-7abash said:
Any chance you upload your version and share it? I'm looking for exactly the same thing and sadly 2.3.5 Darkside ain't providing that.
Sent from my Atrix 4g using Tapatalk
Click to expand...
Click to collapse
It's just the latest Aura ROM (found in the development section) + this awesome quick panel MOD.
Aura is based on 2.3.4. I noticed that arabic fonts were connecting properly in the system+browser with Aura ROM as-is. No framework.jar or lebwebcore.is hacks are needed with that ROM.
Root+Battery % icons MOD+No carrier logo MOD+proper Arabic font connecting+this quick panel MOD is pretty much what I want now in my Atrix. Currently happy to have all that.
Not to mention a lot of other plus features Aura ROM adds.

Hi,
I was using this mod on 2.3.4 and it was great! Just upgraded to Android OS 2.3.6 (att build 4.5.141) and it just boot loops until I replace it back with the original. Is there any way to modify this to work on 2.3.6? Or, is there a version around that I'm not finding that will work on 2.3.6?
Thanks!
--Q

|Solution] On Screen HW info/Samsung Service Menu On Home Screen. [Guide]

Credit Goes to Jokesy,
Getting HW/FW on Home Screen ?
Then this Solution is for You!
Jokesy said:
Solution: there are two ways of solving it. Pick the one you find easier.
Root access needed
Option 1.
Download from Market "Terminal Emulator"
Open it and type this commands:
su
echo -n ON > /efs/imei/keystr
sync
reboot
Option 2.
You need a root capable explorer. I recommend Root explorer, solid explorer or Es file explorer.
- Using root explorer locate the /efs/imei/ folder.
In that folder there should be a file called "keystr", but will most likely be missing in your case
- using root explorer create a new file called "keystr"
- also in root explorer open the file keystr in text editor and type "ON"
- make sure you save the file.
-reboot.
Swyped from my Samsung Galaxy SII
Supercharged ParanoidAndroid 2.12
Dorimanx kernel 5.76B
GT I9100
Next phone: Galaxy NOTE II
Click to expand...
Click to collapse
Made this Thread Because alot of People Questioning about this.
Please Correct me if there's already a Guide Here.
Peace
Hit Thanks & It will Disappear
Sent from S II Running Fully Modified Official ICS 4.0.4
Next Device: Upcoming Nexus

Sorry, what do you mean by "on desktop"? On a desktop computer?

adotkdotjh said:
Sorry, what do you mean by "on desktop"? On a desktop computer?
Click to expand...
Click to collapse
Sorry...
Changed :thumbup:
Peace
Hit Thanks & It will Disappear
Sent from S II Running Fully Modified Official ICS 4.0.4
Next Device: Upcoming Nexus

still with problem
Hi, i did all steps but the problem still on my screen. Anyone can help me?
Thanks
Sorry my english

do i need to use tw launcher? on nova launcher nothing appear.

[HOW TO] Unlock tethering on Marshmallow 6.0

Google made a change from Android 4.1.2 which allows operators to know when users are using tethering and conveniently block tethered devices from accessing internet.
This can be fixed permanently using the following procedure and no root required on all rom types (stock, mod):
1) Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
2) Enable USB debugging under Settings -> Developer options
3) Connect the device with a USB cable to a computer with the Android SDK platform tools installed
4) Start an adb shell: adb shell
5) In the adb shell, run this command:
Code:
settings put global tether_dun_required 0
Tested on Nexus 5 & 6 with Marshmallow STOCK ROM

Just tried this on a freshly imaged Verizon Nexus 6 with Marshmallow, and I'm still getting the prompt for subscribing to tethering.

Can you do this with sqlite editor? If so, how?

net.tethering.noprovisioning=true
Pasted at end of build prop. Save. Reboot. Done.

Can this be tried even if the Nexus6 boot loader is locked, without unlocking it ?
Sent from my VS985 4G using Tapatalk

trent999 said:
Can this be tried even if the Nexus6 boot loader is locked, without unlocking it ?
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
You need root to edit the build prop like this but you can also edit the build prop thru adb commands
Sent from my Nexus 6 using Tapatalk

Ocelot13 said:
net.tethering.noprovisioning=true
Pasted at end of build prop. Save. Reboot. Done.
Click to expand...
Click to collapse
I'm on Verizon and that's what I did also.
Sent from my Nexus 6 using Tapatalk

nexus6r3plicant01 said:
You need root to edit the build prop like this but you can also edit the build prop thru adb commands
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You don't need root to do it, you can make the change via recovery and adb shell commands.

wishkah said:
Can you do this with sqlite editor? If so, how?
Click to expand...
Click to collapse
I'm not sure this can be done with sqlite editor anymore because when I go to the file path data>data>com.android.providers.settings>databases there is no longer a settings.db in that location to edit.
Maybe I'm missing something.... IDK???

didn't work on my stock Nexus 6 - still says to contact ATT.
---------- Post added at 10:41 AM ---------- Previous post was at 10:32 AM ----------
Durthquake said:
didn't work on my stock Nexus 6 - still says to contact ATT.
Click to expand...
Click to collapse
editing the build.prop worked for me! thanks guys/gals

nexus6r3plicant01 said:
You need root to edit the build prop like this but you can also edit the build prop thru adb commands
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Is Rooot needed to do this through adb?

That is my question, too.
For right now, I want to wait to unlock and root. I have reasons...
Can I edit and replace build.prop somehow under those conditions ?
I have ADB and fastboot both working and have pulled a copy of the stock Lollipop build.prop onto my laptop. I can edit it, but can I push the revised copy back with the boot loader still locked and no root ?
I read somewhere about achieving temporary root via fastboot booting twrp, instead of flashing, but that fails for me and I cannot find the referencing thread.
Sent from my VS985 4G using Tapatalk

Same boat here. I'd love to enable this, but don't want to do too much as I'm switching to a 6P in two weeks.
Do you need root to mod this? i'm not able to R/W system without it I assume?

So, this link provides information on how to make the modifications to the build.prop without root which is what I needed to make things happen on Verizon. Note that this does make the scary This device is corrupt... message appear at bootup. Specific steps I followed (assuming you've got adb working and USB debugging enabled):
- Download TWRP 2.8.7.1 from here
- adb reboot bootloader
- fastboot boot twrp-2.8.7.1-shamu.img
- When TWRP finishes booting, click Mount and check the box for /system
- adb pull /system/build.prop
- Use your favorite text editor to add the line net.tethering.noprovisioning=true to the build.prop file you just downloaded off the phone. Save the file.
- adb push build.prop /system/
- adb shell chmod 644 /system/build.prop
- adb shell settings put global tether_dun_required 0
- adb reboot
And voila. When you reboot you'll be able to tether. At least I was.

Yes, the above is what I have been looking at, but it is important to realize it requires an unlocked bootloader, which requires a total phone wipe.
Plus I am concerned that this will prevent any future OTA, like to Marshmallow for mine, and also make it impossible to use Android Pay on that device, if those issues matter to you.
Yes, I know it is self-limiting to have a stock, locked N6.
Sent from my Nexus 6 using Tapatalk

pmhesse said:
Note that this does make the scary This device is corrupt... message appear at bootup.
Click to expand...
Click to collapse
Also note that this will also make you unable to apply any future OTAs (neither pushed to you by Google, nor sideloaded via ADB).
18 months ago, before /system validation became a thing, I would have recommended this method to a lot of "casual" modders - booting to TWRP to fix a couple things, and then going on their merry way with an unrooted "stock" (or close enough to it as to not matter) device.
Now that /system validation is a thing (breaks OTA applicability, dm-verity), I wonder if it's actually more advisable that people keep TWRP installed, and take the time to fully educate themselves about what they're doing, so that in the future they can fix things themselves more easily (and manually apply the monthly security patches, etc.).
I'm honestly not sure about the right answer - what do folks think?

pmhesse said:
So, this link provides information on how to make the modifications to the build.prop without root which is what I needed to make things happen on Verizon. Note that this does make the scary This device is corrupt... message appear at bootup. Specific steps I followed (assuming you've got adb working and USB debugging enabled):
- Download TWRP 2.8.7.1 from here
- adb reboot bootloader
- fastboot boot twrp-2.8.7.1-shamu.img
- When TWRP finishes booting, click Mount and check the box for /system
- adb pull /system/build.prop
- Use your favorite text editor to add the line net.tethering.noprovisioning=true to the build.prop file you just downloaded off the phone. Save the file.
- adb push build.prop /system/
- adb shell chmod 644 /system/build.prop
- adb shell settings put global tether_dun_required 0
- adb reboot
And voila. When you reboot you'll be able to tether. At least I was.
Click to expand...
Click to collapse
Ah. I don't have TWRP installed. Thats what I was missing. I went full stock besides my unlocked bootloader with Marshmallow. Not being able to Android Pay also sucks as I do use that. Wonder if I set it up first, then do this if it will let me still use the cards I load.

Durthquake said:
didn't work on my stock Nexus 6 - still says to contact ATT.
---------- Post added at 10:41 AM ---------- Previous post was at 10:32 AM ----------
editing the build.prop worked for me! thanks guys/gals
Click to expand...
Click to collapse
So the command did not work but adding the net..etc to build prop worked anyone in T-Mobile done this yet? Thanks

Correct, the command didn't work, but the line at end of build.prop did. Should work for any carrier.

Ocelot13 said:
net.tethering.noprovisioning=true
Pasted at end of build prop. Save. Reboot. Done.
Click to expand...
Click to collapse
Thank you!

Alternative Launcher + Backup Launcher

Thanks to @jkchr1s for the steps
I have also attached a backup com.amazonfire launcher just incase soeone messes up.
Working Launcher replacement thanks to @diegocr and @Awesomeslayerg ! Here's the steps:
See @diegocr post at http://forum.xda-developers.com/show...8&postcount=23 and download "boot-firelauncher.img"
Enable USB debugging
Install your launcher of choice!
On your computer, run
Code:
adb reboot bootloader
Once your tablet reboots in to fastboot, run on your computer (if you are not in the same directory as boot-firelauncher.img, put the full path):
Code:
fastboot boot boot-firelauncher.img
Tablet will reboot
Once booted open an adb shell:
Code:
adb shell
To back up the existing app, run:
Code:
cp /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk /sdcard/Download/com.amazon.firelauncher.apk
Then nuke it!
Code:
rm /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk
Now, run to restart your device:
Code:
reboot
Confirmed working on my tablet with FireOS 5.0.1.
Enjoy!
If you mess up and your fire dosent have a launcher then download the apk file and adb sideload it once your at the lock screen.

Just wanted to mention can keep the Fire launcher installed without having it forced as default. Follow the above then using a file manager go to where you made a copy of the apk file and install it. It will install and can be used and selected as home or not via the usual home method.

You sir deserve a medal sir! You just saved me 15 € for Netflix and chilling.

or just use Titanium Backup with Pro Key, to Freeze the app

Someone care to explain a bit more? Does this allow us to select a new launcher within system settings making the home button select this launcher?

ruokblah said:
Someone care to explain a bit more? Does this allow us to select a new launcher within system settings making the home button select this launcher?
Click to expand...
Click to collapse
yes
Sent from my KFFOWI using XDA One

After removing the default launcher, I moved to Nova launcher and lost access to all the apps I had saved to my SD card via the system settings. Does this have something to do with the firelauncher? Is there a way to re-enable sd card read/write access?

shiz0id said:
After removing the default launcher, I moved to Nova launcher and lost access to all the apps I had saved to my SD card via the system settings. Does this have something to do with the firelauncher?
Click to expand...
Click to collapse
shouldn't, did you remove other amazon apps?

sd_shadow said:
shouldn't, did you remove other amazon apps?
Click to expand...
Click to collapse
nope, just the FireLauncher, the apps are grayed out in nova, if that means anything.

shiz0id said:
nope, just the FireLauncher, the apps are grayed out in nova, if that means anything.
Click to expand...
Click to collapse
Apps on sd card working fine with Google now launcher
Sent from my KFFOWI using Tapatalk

sd_shadow said:
Apps on sd card working fine with Google now launcher
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
fixed after forcing a restart of nova, appears to be some kind of issue with the app itself
On another note, do you know any way to re-enable sd card write access?

shiz0id said:
fixed after forcing a restart of nova, appears to be some kind of issue with the app itself
On another note, do you know any way to re-enable sd card write access?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=nextapp.sdfix
Sent from my KFFOWI using Tapatalk

Awesomeslayerg said:
Thanks to @jkchr1s for the steps
I have also attached a backup com.amazonfire launcher just incase soeone messes up.
Working Launcher replacement thanks to @diegocr and @Awesomeslayerg ! Here's the steps:
See @diegocr post at http://forum.xda-developers.com/show...8&postcount=23 and download "boot-firelauncher.img"
Enable USB debugging
Install your launcher of choice!
On your computer, run
Code:
adb reboot bootloader
Once your tablet reboots in to fastboot, run on your computer (if you are not in the same directory as boot-firelauncher.img, put the full path):
Code:
fastboot boot boot-firelauncher.img
Tablet will reboot
Once booted open an adb shell:
Code:
adb shell
To back up the existing app, run:
Code:
cp /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk /sdcard/Download/com.amazon.firelauncher.apk
Then nuke it!
Code:
rm /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk
Now, run to restart your device:
Code:
reboot
Confirmed working on my tablet with FireOS 5.0.1.
Enjoy!
If you mess up and your fire dosent have a launcher then download the apk file and adb sideload it once your at the lock screen.
Click to expand...
Click to collapse
I found it was easier to download a 2nd launcher (google now/apex/nova) after I gained root access, then backup the com.amazon.firelauncher in the system/priv-app folder to my SD card or outside the priv-app folder using es file browser. Delete the com.amazon.firelauncher folder inside priv-app, restart the tablet then I was asked on reboot to confirm the default launcher.
Thought it may help someone out who doesn't fancy running the commands.
Cheers as this forum has helped me a lot, much appreciated for all the hard working devs!

Awesomeslayerg said:
Thanks to @jkchr1s for the steps
I have also attached a backup com.amazonfire launcher just incase soeone messes up.
Working Launcher replacement thanks to @diegocr and @Awesomeslayerg ! Here's the steps:
See @diegocr post at http://forum.xda-developers.com/show...8&postcount=23 and download "boot-firelauncher.img"
Enable USB debugging
Install your launcher of choice!
On your computer, run
Code:
adb reboot bootloader
Once your tablet reboots in to fastboot, run on your computer (if you are not in the same directory as boot-firelauncher.img, put the full path):
Code:
fastboot boot boot-firelauncher.img
Tablet will reboot
Once booted open an adb shell:
Code:
adb shell
To back up the existing app, run:
Code:
cp /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk /sdcard/Download/com.amazon.firelauncher.apk
Then nuke it!
Code:
rm /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk
Now, run to restart your device:
Code:
reboot
Confirmed working on my tablet with FireOS 5.0.1.
Enjoy!
If you mess up and your fire dosent have a launcher then download the apk file and adb sideload it once your at the lock screen.
Click to expand...
Click to collapse
Could the "boot-firelauncher.img" also be used for the Fire HD 10?

Black Hawk90 said:
Could the "boot-firelauncher.img" also be used for the Fire HD 10?
Click to expand...
Click to collapse
Yes, see [Root] Amazon Fire HD 8 & 10 (5th Gen 2015) for details

Anyone noticed that you cant pin widgets to the startscreen?
Everytime i try, it redirects me to the Amazon-Settings app und the widget isnt pinned.
This happens when the widgets are larger than 1x1

*Igel* said:
Anyone noticed that you cant pin widgets to the startscreen?
Everytime i try, it redirects me to the Amazon-Settings app und the widget isnt pinned.
This happens when the widgets are larger than 1x1
Click to expand...
Click to collapse
Widgets are working for me with Now launcher

*Igel* said:
Anyone noticed that you cant pin widgets to the startscreen?
Everytime i try, it redirects me to the Amazon-Settings app und the widget isnt pinned.
This happens when the widgets are larger than 1x1
Click to expand...
Click to collapse
Convert the launcher to a system app.

csolanol said:
Convert the launcher to a system app.
Click to expand...
Click to collapse
How would I convert it to a system app?

I've found https://play.google.com/store/apps/details?id=de.j4velin.systemappmover&hl=en which works good.
Moved my new apex launcher to system map, reboot was required, then widgets worked with apex launcher which hadn't worked before.