One last note: Users that have installed the previous versions should/ are adviced to download the new version from the other thread. The new version addresses the problem that one can't boot into the system because of a conflict between a particular density setting and a launcher and or widget.
The apk's attached to this post are now removed. Head over to the new thread to download the app.
Update v2.1 * addresses some problems other devices than the Galaxy S variants had with the former version. * some minor cosmetic changes. (note: I also opened a thread on the android developers forum, so other devices can profit from this tweak as well. I have decided to post my updates there and, of course, on the Android Market. The new thread can be found http://forum.xda-developers.com/showthread.php?t=765639
Update v2.0 * Added option to turn on/off compability settings for app scaling. * Possibility to restore default density setting (the default density that is stored is the density of your screen when you run the tool for the first time). * Added helpfile * Added option to reboot automatically after changing the density.
Update v1.1: a) Optimization of code: faster, more safe b) some cosmetic changes
I created a little app to play with the LCD Density Settings as described in this thread. The app lets you set the LCD Density Setting without edditing the build.prop file (directly).
Be aware that the tweak only will work with launchers like LauncherPro. It doesn't work with Samsungs own TouchWizardLauncher. (If you insist on experimenting with the TWLauncher, make sure that you have the USB Debugger enabled to get you out of the mess ).
Only requirements for this app to work is that you are rooted and have su, busybox and Superuser installed (in fact you have all those apps installed when you have rooted your device the "regular" way) AND that you like to experiment with things.. if you know what I mean.
Click to expand...
Click to collapse
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instead of a donation you can consider to buy the app from the Android Market (0,75 euro). Search for LCD Density Changer or scan:
I will keep this app for free for download and always up to date here on this forum!
Future work
I will keep on investigating how the software environment can be made compatible with lower density settings. My intention is to update the app constantly with new tweaks and settings so that eventually it can function as a full control panel for the density tweak.
Thanks to jdsemler who discovered this tweak.
Note: if you don't want to take any risk, make sure you make a nandroid backup. Although the new version is reported to be error-free, it is always a good idea to create a full system backup before one is going to play with these kind of tools.
(also) thanks to
* bratfink for giving some very useful input
* Cutefox for bringing to our attention that turning of the compatibility mode via an app called "Spare Parts" solves the scaling problem.
* Nelson Mandela for bringing peace
* Mahatma Ghandi for his inspiration
* Bell for inventing the phone
* Samsung for the upcomming GPS fix
* and many, many others I forgot to mention.
Download history
LCD Density Changer.apk (16.3 KB, 223 views)
LCD Density Changer v1.1.apk (17.6 KB, 91 views)
LCD Density Changer v2.0.apk (28.9 KB, 264 views)
What are the standard values?
HDPI = 240 (Galaxy S default)
MDPI = 160
LDPI = 120
The larger the number, the larger the stuff on-screen is. The smaller the number, the smaller stuff is. The smaller numbers are great for getting more stuff on screen to see, like when using RSS readers to see more articles on the screen before you have to scroll.
jdsemler said:
HDPI = 240 (Galaxy S default)
MDPI = 160
LDPI = 120
The larger the number, the larger the stuff on-screen is. The smaller the number, the smaller stuff is. The smaller numbers are great for getting more stuff on screen to see, like when using RSS readers to see more articles on the screen before you have to scroll.
Click to expand...
Click to collapse
Yeah, it's such a nice tweak. Thanks again! Any progression on the scaling issue?
Nothing useful yet. I'm convinced that the /system.prop is the problem. Somehow, they are updating that file on every reboot, and it is impacting certain apps that are having the 240 value passed to them from that file, which makes them render in that set size.
Take Root Explorer for example. It runs in a very small area when not in HDPI mode on the Samsung device. I installed it on my Dell Streak, which natively is set to run in MDPI mode, and it goes full screen without issue. I then set it for LDPI, and it goes full screen again. Going to HDPI also makes no issue, so it is something that Samsung is doing, and if we can figure out what is updating /system.prop and stop it, I think we'll have it licked.
I think I'm way out of my league when it comes to debugging the Samsung's behavior though.
Can someone post the original build.prop because mine seems to be 0 byte and I can see anything on the screen.
Thanks.
jdsemler said:
Nothing useful yet. I'm convinced that the /system.prop is the problem. Somehow, they are updating that file on every reboot, and it is impacting certain apps that are having the 240 value passed to them from that file, which makes them render in that set size.
Take Root Explorer for example. It runs in a very small area when not in HDPI mode on the Samsung device. I installed it on my Dell Streak, which natively is set to run in MDPI mode, and it goes full screen without issue. I then set it for LDPI, and it goes full screen again. Going to HDPI also makes no issue, so it is something that Samsung is doing, and if we can figure out what is updating /system.prop and stop it, I think we'll have it licked.
I think I'm way out of my league when it comes to debugging the Samsung's behavior though.
Click to expand...
Click to collapse
nonetheless a very interesting problem. The thing that intrigues me is that some apps run full screen without any problem. I'm gonna decompile those apps later on to see how they have defined the layout.
BTW can you upload some of the dell streak prop files that may be relevant in this case?
lpsi2000 said:
Can someone post the original build.prop because mine seems to be 0 byte and I can see anything on the screen.
Thanks.
Click to expand...
Click to collapse
Did you use my app? Because in that case that's not good. What did you do?
Have you rooted your device, did you have busybox installed? Have you granted superuser permission?
Anyway, I attached the build.prop from my Galaxy S.
EDIT if it's right there's a copy of build.prop in the folder /data/data/com.beansoft.lcd_density_setting (or something like that). Can you look and see if that file is 0 bytes to? Otherwise, copy that back to the system folder
I attached my default (HDPI setting) Samsung build.prop and my current Dell Streak build.prop.
The Streak build.prop has a different fingerprint, because I'm using the 2.1 build and had to have a recognized (by Market) fingerprint to get to my protected apps.
The Streak does not have a /system.prop file, unlike the Samsung.
System.prob
It does seem that the dpi settings in system.prop are what seems to be the issue with some of these applications. I could be that the samsung framework explicitly allows 240 as the only acceptable dpi and thus restores the system.prop automatically if it finds a different value.
In this case if someone doesnt mind flashing or is currently using that vanilla custom rom that works on the SGS (Its in its Alpha stages) then it would be interesting to see if the changes are permant and accross the board when using vanilla. Anyone care to try?
bratfink said:
It does seem that the dpi settings in system.prop are what seems to be the issue with some of these applications. I could be that the samsung framework explicitly allows 240 as the only acceptable dpi and thus restores the system.prop automatically if it finds a different value.
In this case if someone doesnt mind flashing or is currently using that vanilla custom rom that works on the SGS (Its in its Alpha stages) then it would be interesting to see if the changes are permant and accross the board when using vanilla. Anyone care to try?
Click to expand...
Click to collapse
Makes sense. Question though, when do all these prop files load? Don't think it will work, but can an app at boottime change the system.prob values so that it doesn't affect the modified dpi value?
tried using your app to change the setting to 220, and the at&t logo pops up, the samsung sound goes off, and the screen stays blank. I can't get access to su in adb shell and all I can do is reboot. what's going on?
asrrin29 said:
tried using your app to change the setting to 220, and the at&t logo pops up, the samsung sound goes off, and the screen stays blank. I can't get access to su in adb shell and all I can do is reboot. what's going on?
Click to expand...
Click to collapse
I suppose you have a rooted device with the whole sjabang (SuperUser and Busybox) installed on it?
appelflap said:
I suppose you have a rooted device with the whole sjabang (SuperUser and Busybox) installed on it?
Click to expand...
Click to collapse
yes. when I try to use su I get
[1] Segmentation fault su
appelflap said:
Did you use my app? Because in that case that's not good. What did you do?
Have you rooted your device, did you have busybox installed? Have you granted superuser permission?
Anyway, I attached the build.prop from my Galaxy S.
EDIT if it's right there's a copy of build.prop in the folder /data/data/com.beansoft.lcd_density_setting (or something like that). Can you look and see if that file is 0 bytes to? Otherwise, copy that back to the system folder
Click to expand...
Click to collapse
Yes, the app is what I use and I can't even get su to work under adb shell. It looks like I am going to need to re flash.
Used the app, same result....
Reflashing now... Normally not a problem for me to reflash, but I didn't get to backup my text messages and notepad -_-
Oh well...
asrrin29 said:
yes. when I try to use su I get
[1] Segmentation fault su
Click to expand...
Click to collapse
that's weird. all I do in the app is trigger some shell commands like "su" and "busybox cp". But can't you try to do the rooting procedure again by "apply: /sdcard/update.zip" in adb?
Makes me wonder if there are any users, except me, who got this app working?
appelflap said:
that's weird. all I do in the app is trigger some shell commands like "su" and "busybox cp". But can't you try to do the rooting procedure again by "apply: /sdcard/update.zip" in adb?
Makes me wonder if there are any users, except me, who got this app working?
Click to expand...
Click to collapse
not sure that's going to work, because I can't get super user access until I grant it permission without a ui.
F_L_Abs said:
Used the app, same result....
Reflashing now... Normally not a problem for me to reflash, but I didn't get to backup my text messages and notepad -_-
Oh well...
Click to expand...
Click to collapse
I'm sorry ... The Android SDK isn't the best toolkit to do such low level system hacking. The security levels are high, and to break them you have to do all kind of weird stuff. Anyway, I changed the first post and put a extra warning in it.
Is there a way to use Odin 3 to restore the files changed?
Related
Just now I applied a trick to have more info on my screen by changing the dpi setting. To to so in /system/build.prop modify the following line:
Code:
ro.sf.lcd_density=240
I changed it to 200. After modifying the settings in Launcher Pro I now have 6 rows and 5 columns in my homescreens which still have enough space in between.
You need root access to change system files. The file manager also needs to have root access. I used Super Manager for this.
I got this hack from doid-life. They also give an alternative way using adb.
You can also alter the build.prop by installing the PropEditor-0.3.apk from the following link;
http://code.google.com/p/net-widgetron-propeditor/downloads/detail?name=PropEditor-0.3.apk
Thanks, that made it a lot easier!
Now I also changed these lines:
Code:
ro.wifi.channels=14
wifi.supplicant_scan_interval=90
This way all 14 wifi channels are available (also in 3G mobile hotspot) and the phone scans every 90 seconds for new wifi networks instead of the default 45 seconds. As I always have wifi on that saves some battery.
Ok this is weird. I just discovered that anything else than 240 dpi renders the dialer unusable. Sometimes it opens to only close again a split second later. Pitty because I really like the lower dpi setting. Back at 240 dpi it feels like a phone for the vision impaired.
Can i ask how exactly are the changes brought to dpi adjust?
Sent from my MB525 using XDA App
Can someone please post a screenshot? Because I think this will make everything smaller so it's very hard to read anything.
LCDDensity for Root makes the same, you can find it on the market, free of charge.
Foxhound.kl said:
You can also alter the build.prop by installing the PropEditor-0.3.apk from the following link;
http://code.google.com/p/net-widgetron-propeditor/downloads/detail?name=PropEditor-0.3.apk
Click to expand...
Click to collapse
Cool thanks for this.
I started changing screen density with my HD2 when they only had android from sd card. Basically lower number means "higher definition" and you can fit more things on the screen.
so waht does having 14 channels for WIFI do?
When I change the pixel density, I get FC when opening „phone„. I am using Pay's ROM.
Jt612 said:
so waht does having 14 channels for WIFI do?
Click to expand...
Click to collapse
It allows people to connect to broadcasts on all possible WiFi channels around the world.
So North Americans who might be originally limited to 1-11 (is the NA device locked to this though?) won't miss out on the odd coffee shop hotspot overseas that broadcasts on 13.
m11kkaa said:
When I change the pixel density, I get FC when opening „phone„. I am using Pay's ROM.
Click to expand...
Click to collapse
Try to download spare parts from the market (if its not in that rom already) and uncheck compatibility mode and restart your phone. might work.
FULL CREDIT TO lambgx02!
Original Post | CWM
Guys check this out
Best result on Android 4.+
Description
Hey everyone,
So, I was experiencing significant lag as we all do from time to time, and decided I was going to get to the bottom of it.
After tracing and debugging for hours, I discovered the source of 90% of Android's lag. In a word, entropy (or lack thereof).
Google's JVM, like Sun's, reads from /dev/random. For all random data. Yes, the /dev/random that uses a very limited entropy pool.
Random data is used for all kinds of stuff.. UUID generation, session keys, SSL.. when we run out of entropy, the process blocks. That manifests itself as lag. The process cannot continue until the kernel generates more high quality random data.
So, I cross-compiled rngd, and used it to feed /dev/urandom into /dev/random at 1 second intervals.
Result? I have never used an Android device this fast.
It is literally five times faster in many cases. Chrome, maps, and other heavy applications load in about 1/2 a second, and map tiles populate as fast as I can scroll. Task switching is instantaneous. You know how sometimes when you hit the home button, it takes 5-10 seconds for the home screen to repopulate? Yeah. Blocking on read of /dev/random. Problem solved. But don't take my word for it .. give it a shot!
Update!
I've built a very simple Android app that bundles the binary, and starts/stops the service (on boot if selected). I'll be adding more instrumentation, but for now, give it a shot! This APK does not modify /system in any way, so should be perfectly safe.
This is my first userspace Android app, so bear with me!
Note that this APK is actually compatible with all Android versions, and all (armel) devices. It's not at all specific to the Captivate Glide.
Click to expand...
Click to collapse
Quote Original Post link - Click Here
Requirements
An Android device! No iPhone's allowed!
Need Root
[Optional]-Root File manager
Ryuinferno said:
Before doing anything, please read the first post of this thread to understand how this thing functions!
Read it here: First post
First things first I am not the OP but things need to be sorted out...Ok...this thread is starting to get more and more attention, which is good because with more people to test things out, the more feedbacks and the more improvements can be done...however, the thread is now cluttered by tons on unhelpful posts, like "how to use this", "do I need root" etc...useful posts get pushed wayyy behind, until it is hard for people who are really trying to discuss to keep track...so I am here to answer the basic questions:
Do you need root for the app?:
Yes
Can it work on xxx device?:
Yes, as long as your device is arm based
Where to download the app?:
Here: http://forum.xda-developers.com/attachment.php?attachmentid=1640660&d=1358063993
Or search Play Store for a donate version...
The other 2 attachments are the rngd binary and a diff patch, which are not really required for end users...
How do I know that it is working?
Prior to starting seeder entropy generator through the app (v1.2.4 onwards), the bar below will only show numbers around 100-200++. After you start it, if the bar fills up and the value shoots up to 4000++, then it is working.
Do I have a risk of bricking my device?
No because the app won't modify system files at all...anything just uninstall...
For the zip, it only adds files to your system partition...does not modify any, so if you want to stop using this, you can disable it via the extended menu script...
It does not do anything/It is placebo/I see no improvements/It is awesome!/Wow!:
Well, this is not constructive or helpful...NOT AT ALL...keep in mind that this is still a WIP...research and discussions are still going on...if it is not working or you feel no change or a great improvement, please describe more and explain...which a lot of others are already doing so......keep it up!
Seems that certain people are so bugged by the app...so...for those who prefer to run this via a script and init.d, read on...(the script works the same as the app, but with a few extra features)
=======================================================================================================================
UPDATE: Seeder_v7 is out, as suggested by pepoluan, it now detects for qrngd (built in rngd for Qualcomm Snapdragon-based devices), if it is there, then it will not start as rngd may conflict with it...the rngd binary is also using the latest version (it is turned off when screen is off)...users of previous versions can just flash it over...
INSTALLING
You need init.d support for this!
Download and flash:
http://www.androidfilehost.com/?fid=9390248398092764755
How to use this script?:
After flashing, launch terminal emulator and type
Code:
su
seeder
You will get a menu like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE: There will be NO app after flashing! This only installs the necessary binaries and scripts...
For those who cannot install via recovery:
You get a status 0 error -> replace the update-binary in Seeder_v6.zip with one from another zip that works with your device
OR
Use the new installation method!
Instructions:
1. Download Seeder_v7_non-CWM.zip from here:
http://www.androidfilehost.com/?fid=9390248398092764756
2. Extract the zip, you will get a folder named "install"
3. Place the folder in the root of your sdcard (/sdcard)
4. Launch terminal emulator, type:
Code:
su
cd /sdcard/install
sh install.sh
5. Ignore any error messages (those are only warnings, only happens to current users)
6. You are done! The script will auto-delete the "install" folder as it is not required anymore...
Sample output:
UNINSTALLING:
And now for the way to clean up Seeder_7:
Via recovery:
Flash Seeder_v6&7_Uninstall.zip:
http://www.androidfilehost.com/?fid=9390248398092764753
Via terminal:
1. Download Seeder_v6&7_Uninstall_non-CWM.zip:
http://www.androidfilehost.com/?fid=9390248398092764145
2. Extract it to the root of your sdcard (/sdcard), you should get a file named uninstall.sh
3. Launch terminal emulator and type this:
Code:
su
cd /sdcard
sh uninstall.sh
4. You are done! Everything gets cleaned up, including uninstall.sh...
Click to expand...
Click to collapse
Updates
There has been a lot of controversy about Seeder/rngd. In newer versions of Dalvik, nothing touches /dev/random, and yet many users (including myself) still notice a lag reduction. There are theories ranging from kernel lock contention to UI polling load when crediting the entropy pool to simply kicking the governor. And many who believe it's all placebo. I'm trying my best to figure out what exactly is happening, and others are as well.
Someone asked how I arrived at the conclusion I did when I started the thread back in November, and I posted this; I think it might be better served here:
A while back one of the webapps I was hosting on Tomcat (server-side) was experiencing some inexplicable latency and while stracing java I saw it frequently hanging on read()'s from /dev/random. I checked the available entropy, and it was constantly under 250 or so. It was a VM, no HWRNG, so I decided to use rngd to push urandom->random.
Dropped session creation times under load from 5-10 seconds to less than a second.
It's worth noting that Linux is one of very few OSes that have a blocking RNG device. Free/OpenBSD, Windows, etc.. essentially only provide urandom. It's generally considered secure, even for long-term crypto keys, so long as the initial seed is big (and random) enough.
Checked on my device, and saw a few processes grabbing /dev/random. /proc/sys/kernel/random/entropy_avail reporting depleted input pool. Figured it was worth a shot, so I rebuilt rngd for arm (with a few patches, linked on first page), and tried it out. It made a significant difference. Posted it up on this thread, and had a lot of positive feedback. Wanted to get into Android development, so figured.. why not wrap a little UI around it. More positive feedback, so I threw it on the market as well.
I had no idea it would take off like this and was shocked when I saw it Thursday morning. I'm in the awkward position now of explaining why it seems to work for some people, and not for others, especially given the fact Dalvik doesn't have references to /dev/random as of ICS. Theories abound, but it looks like it might be an issue of polling the UI for input events when the entropy pool drops (which never happens so long as rngd is running).
I'm doing this as a hobby. I'm a *nix admin by trade, and can only spend time working on this stuff on evenings and weekends, and the last few weeks have been kinda nuts.
I want to stress to everyone that:
a) It doesn't work the way I thought it did on later Android builds, but it does reduce latency for me and many others even on these builds,
b) I'm offering (and always will offer) Seeder for free to everyone on XDA,
c) Like I say in the market description, if anyone has purchased it and it isn't working, PLEASE email me for a refund (and let me know what device you're on if you're willing).
I was one of the first to root the Captivate glide (my first Android phone), and submitted the A2DP bitpool patch; I was active in the n900 community. I hope everyone understands that I'm doing my best here!
I hope the technique proves useful to people, and if there is in fact contention at the kernel level, I hope it's solved so we all benefit.
Version 2.0.0 attached. No changes.
Version 2.0.0b1 attached. New performance profile selector, I/O queue extender, and power saving control. Improved root checking.
Version 1.4.0 attached. Major refactoring. Service control now fully asynchronous.
Version 1.3.1 attached. No changes from 1.3.1-beta.
Version 1.3.1-beta released. New root check method during ANR-sensitive code.
Version 1.3.0 attached. Proper IntentServices for process control, and notification on upgrade / loss of root / autostart failure.
Version 1.2.9 attached. Yet another update to the upgrade/autostart code.
Version 1.2.8 attached. Asynchronous startup of rngd during boot; this should solve the remaining autostart problems some users have reported.
Version 1.2.7 released. This version introduces a much more efficient suspend-on-sleep mode for rngd.
Version 1.2.6 released. This version reverts the suspend-on-sleep rngd change which may have been contributing to new latency. I'm sorting out a better way of implementing it.
Version 1.2.5 released. This version should fix the autostart failure some users have seen.
Version 1.2.4 released. This version implements a progress bar displaying your currently available entropy, as well as automatic rngd restart on upgrade.
Version 1.2 released. This version implements rngd suspend-on-sleep, and contains minor user interface updates, more robust process and superuser checks, and a new icon (thanks Nathanel!)
Version 1.1 released. This version uses the release signature, so you will need to uninstall the old XDA version first!
Download and flash this if you dont know what to download xD Click here!
if this really works... wow
then it should be included in all custom ROMs from now on and a patch merged into AOSP
Holy crap dude! Using it now on my Gnex. Gunna give a few to see if it really does increase performance. As far as I can tell since installation scrolling in tapatalk has increased tenfold.
Sent from my Galaxy Nexus
Holy crap! Gonna try this now!
EDIT: I've got TWRP, will the CWM zip work in it?
Larry94 said:
Holy crap! Gonna try this now!
EDIT: I've got TWRP, will the CWM zip work in it?
Click to expand...
Click to collapse
I've not tried on TWRP but should work! Flash it! This works on any device also
Sent from my Nexus 7 using xda premium
bradman117 said:
I've not tried on TWRP but should work! Flash it! This works on any device also
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hmm, only files I have in xbin after flashing is bttest, dexdump, and su. :/
Larry94 said:
Hmm, only files I have in xbin after flashing is bttest, dexdump, and su. :/
Click to expand...
Click to collapse
U need to do it manually then with root explorer. Look at bottom of my post. Or try redownload and flash
Sent from my Nexus 7 using xda premium
I just use the app... It seems to work just fine
Sent from my Galaxy Nexus
ÜBER™ said:
I just use the app... It seems to work just fine
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I got tired of turning it on every reboot that's why I used flash.
Sent from my Nexus 7 using xda premium
Just unzip flash and download other file I put up under were I put were the files go. Place and fix the files permission
Sent from my Nexus 7 using xda premium
bradman117 said:
I got tired of turning it on every reboot that's why I used flash.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
It has a set on boot option.
Sent from my Nexus 7
bradman117 said:
I got tired of turning it on every reboot that's why I used flash.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Would you mind doing me a quick favor? The permissions look a little different in ES File explorer. Would you install it, navigate to the different files, long press, properties, and select permissions and grab a screen shot?
I don't feel any improvements on my Nexus7, someone yes¿
Br.
Seems to work for me. Modern Combat 4 used to lag before, flashed this and played a match with no lag. You have my thanks
Sent from my ParanoidAndroid/franco.Kernel powered Nexus 7 with XDA Premium
Nothing for me either and everytime I go into the app it shows it as off.
I flashed the CWM version because the app wouldn't stay on or switch on at boot. Haven't really noticed any difference yet, because I don't have any game that lags, including vice city on max settings, and I'm not over clocking yet either.
If MC4 has the occasional stutter then I'll try installing that and see.
Edit: forgot to mention, I also put it on my galaxy s1, and I can tell you that I do notice a definite difference on that.
Sent from my Nexus 7 using Tapatalk HD
I think I need a kernel with init.d support right?
Don't work on stock...
\\\... send with the Nexus 7 3G ...///
IAmNice said:
Above check set on boot
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
I did. It didn't work for me.
Sent from my Nexus 7 using Tapatalk HD
DominatingSystem said:
I think I need a kernel with init.d support right?
Don't work on stock...
\\\... send with the Nexus 7 3G ...///
Click to expand...
Click to collapse
ya u need custom kernel that supports init.d.
knuckles1978 said:
I did. It didn't work for me.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
thats why i put files on manually. set on boot didn't work for me
----EDIT---
Updated post, added downloads if you want to do it manually
As title states, it seems the stock apps are a little pain in the (you know what) to prevent the phone from doing what I want.
There's no custom ROMs yet so I'm more-or-less just playing with the stock ROM to get things working.
It seems like I can't get the DPI to go beyond 530 without annoying the stock apps. Stock is 640 DPI. DPI scaling makes full use of the stupid high resolution of the screen. I couldn't stand out of the box two notifications and bam you're scrolling in the notification tab. Add a few icon notifications and the whole bar is taken up. Silly for such a high resolution phone.
Bunch of Xposed tweaks later and bam. It works like a charm (including play store). Go below 530 DPI and the stock apps crash (see photos). Anyways smarter than me to figure this one out?
Photos tell a lot. It's night and day difference and now an awesome phone.
STOCK BIG FONT (removed some of the bloat)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THIS IS HOW IT SHOULD LOOK STOCK (DPI in the 400s)
THEN BAM!!!
EDIT: GOT IT. 530DPI is the limit. Now if someone smarter than me can figure out how to get the apps to play nicely I'm down. Otherwise I'm pretty happy with it as is.
Left: 530DPI / Right: 640DPI (stock)
480 dpi amd 1080p
Sent from my SGH-T889 using XDA Premium 4 mobile app
install apps setting from xposed
Sent from Mars
hello00 said:
install apps setting from xposed
Sent from Mars
Click to expand...
Click to collapse
I did. Wasn't playing nice. Which apps would I have to set? (Phone, messaging etc.??) What settings do you throw those at?
Nosferatu. said:
I did. Wasn't playing nice. Which apps would I have to set? (Phone, messaging etc.??) What settings do you throw those at?
Click to expand...
Click to collapse
What I did was do system wide 530, then set LG Home to 640 (anything lower looks wonky). As far as I can tell, everything works at 530. If you want other apps at a lower DPI, if I were you, I'd just change their settings on an app by app basis through App Settings.
Sent from my LG-D851 using Tapatalk
partylikeaninjastar said:
What I did was do system wide 530, then set LG Home to 640 (anything lower looks wonky). As far as I can tell, everything works at 530. If you want other apps at a lower DPI, if I were you, I'd just change their settings on an app by app basis through App Settings.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Awesome thanks.
I've done pretty much the same thing as you guys, rooted and used Texdroider to change system-wide DPI to 530. It looks perfect, all stock LG apps work fine, nothing out of place except for that stock Smart Alert / Weather widget, which is fine with me since I use the weather-only widget anyways.
Stock LG launcher with Xposed, and I didn't have to use App Settings to change the launcher to 640, it doesn't need it. I simply used G3 TweaksBox to change the home page layout grid to 5x6 to make it match the looks of the stock 5x5, and the app drawer to 5x6 to take advantage of the extra screen real estate. With just a few tweaks, I have my phone now looking almost identical to my old G2 that was running the same stuff.
One other thing I did is edit the build.prop settings just as mentioned here:
http://forum.xda-developers.com/verizon-lg-g3/general/mod-add-apps-support-to-splitview-t2825776
This lets every app work in Multi Window mode, which is the way it should be. After doing this, I used App Settings to force rotation on the normally-landscape Slingplayer. Now I can have Slingplayer on the top third of the screen in portrait mode while using Chrome on the bottom two-thirds. Perfect!
No crashes or issues with anything so far...
For those of you that changed your DPIs, are you having any problems with the Play Store? Normally, when I edit my DPI, I also install the multi-DPI play store; however, with this device I get gapps FC's by doing that. Just wondering if the stock Play Store starts limiting apps with the DPI change.
I have a quick circle case...and I like 530 dpi...but it jacks up the quick circle...I don't know what app to put back to 640 with xposed and "app settings" anybody know?
Sent from my T-Mobile G3!
Previous Smart Phones: SDA/Juno/G1/HTC HD2/Vibrant/SGS2/SGS3/Nexus4/Nexus5
pychobj2001 said:
I have a quick circle case...and I like 530 dpi...but it jacks up the quick circle...I don't know what app to put back to 640 with xposed and "app settings" anybody know?
Sent from my T-Mobile G3!
Previous Smart Phones: SDA/Juno/G1/HTC HD2/Vibrant/SGS2/SGS3/Nexus4/Nexus5
Click to expand...
Click to collapse
My guess is SystemUI
Sent from my LG-D851 using Tapatalk
partylikeaninjastar said:
My guess is SystemUI
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Isn't that like the primary thing you want to be at the lower DPI? lol
Mi|enko said:
Isn't that like the primary thing you want to be at the lower DPI? lol
Click to expand...
Click to collapse
My thoughts exactly..I hope it's not integrated into system ui...then changing the dpi doesn't do much if I have to have that at 640....maybe I'll just keep trying different app dpi changes...unless aosp comes out..then this circle case might be useless if I switch to aosp
Sent from my T-Mobile G3!
Previous Smart Phones: SDA/Juno/G1/HTC HD2/Vibrant/SGS2/SGS3/Nexus4/Nexus5
Also, when adjusting the DPI, I run into this problem. . . and bear with me, as it's a little strange. If I edit the DPI, I can still get into the app settings; however, if I click an app to review it's data, I immediately get a settings FC. Additionally, my external SD is no longer accessible on the device. I'm thinking these are related, but it's still a weird issue nonetheless. Going to try forcing the DPI of settings with App Settings and see if this changes the experience at all. Will report back.
Edit: Couldn't figure it out. Nothing makes sense as to why individual app settings crash and the SD card can't be accessed when lowering the DPI. So, what I did instead was set the DPI back to 640 and then went in and individually lowered the DPI for all the apps I wanted (SystemUI included) down to 530 via App Settings. No force closes, SD card is readable. . . all is right in the world.
Mi|enko said:
Also, when adjusting the DPI, I run into this problem. . . and bear with me, as it's a little strange. If I edit the DPI, I can still get into the app settings; however, if I click an app to review it's data, I immediately get a settings FC. Additionally, my external SD is no longer accessible on the device. I'm thinking these are related, but it's still a weird issue nonetheless. Going to try forcing the DPI of settings with App Settings and see if this changes the experience at all. Will report back.
Edit: Couldn't figure it out. Nothing makes sense as to why individual app settings crash and the SD card can't be accessed when lowering the DPI. So, what I did instead was set the DPI back to 640 and then went in and individually lowered the DPI for all the apps I wanted (SystemUI included) down to 530 via App Settings. No force closes, SD card is readable. . . all is right in the world.
Click to expand...
Click to collapse
That's strange that you're having so many problems, I haven't had a single issue or FC with anything. My Play Store works fine, I saw you were also asking about that.
Do you have Xposed installed? If so, what modules?
This G3 was by far the easiest phone to root and tweak that I've ever owned, I've got it running exactly the way I want and am not even interested in trying a different ROM.
orbitalcomp said:
That's strange that you're having so many problems, I haven't had a single issue or FC with anything. My Play Store works fine, I saw you were also asking about that.
Do you have Xposed installed? If so, what modules?
This G3 was by far the easiest phone to root and tweak that I've ever owned, I've got it running exactly the way I want and am not even interested in trying a different ROM.
Click to expand...
Click to collapse
Yeah, I'm not sure exactly. I have just about every high end phone imaginable, but this is my first non-nexus LG experience (not to mention QHD) and the first time I've had these problems. DPI's usually the first thing I change on any device, ironically.
At first, I thought it was the apps I was removing and maybe breaking some dependencies, but narrowed it down to the DPI over the last couple days. Even did a fresh flash today. The moment I changed the DPI and rebooted, I got a gapps FC @ boot. Couldn't access individual app settings and SD wouldn't mount. And it was the only customization I made.
Here's a screenshot of the modules I'm using.
Mi|enko said:
Yeah, I'm not sure exactly. I have just about every high end phone imaginable, but this is my first non-nexus LG experience (not to mention QHD) and the first time I've had these problems. DPI's usually the first thing I change on any device, ironically.
At first, I thought it was the apps I was removing and maybe breaking some dependencies, but narrowed it down to the DPI over the last couple days. Even did a fresh flash today. The moment I changed the DPI and rebooted, I got a gapps FC @ boot. Couldn't access individual app settings and SD wouldn't mount. And it was the only customization I made.
Here's a screenshot of the modules I'm using.
View attachment 2869317
Click to expand...
Click to collapse
Out of that list of modules, I'm only using App Settings and G3 TweaksBox, plus Pandora Patcher. That's all I'm using. I haven't used TiB or anything else to free or move any stock apps, I simply used the built-in Disable feature for 4 or 5 harmless apps.
I ran Purple Drake on a Mac and did the TWRP install and root check boot image option. I wonder if any of those things I did or didn't do had anything to do with how mind's running?
Also, the G3TB I'm using is the version from the Play Store, not the beta from the xda thread...mine just updated to v1.1 this morning.
orbitalcomp said:
Out of that list of modules, I'm only using App Settings and G3 TweaksBox, plus Pandora Patcher. That's all I'm using. I haven't used TiB or anything else to free or move any stock apps, I simply used the built-in Disable feature for 4 or 5 harmless apps.
I ran Purple Drake on a Mac and did the TWRP install and root check boot image option. I wonder if any of those things I did or didn't do had anything to do with how mind's running?
Also, the G3TB I'm using is the version from the Play Store, not the beta from the xda thread...mine just updated to v1.1 this morning.
Click to expand...
Click to collapse
I thought it could've been an over customization thing as well. But the fresh flash with only the DPI being changed killed that theory. No xposed, no modules, no app deletion, etc. Mine was rooted with PD on a Mac as well. It's all good though. Leaving the DPI alone and just editing via App Settings has gotten me the same results without the problems I was seeing.
Mi|enko said:
I thought it could've been an over customization thing as well. But the fresh flash with only the DPI being changed killed that theory. No xposed, no modules, no app deletion, etc. Mine was rooted with PD on a Mac as well. It's all good though. Leaving the DPI alone and just editing via App Settings has gotten me the same results without the problems I was seeing.
Click to expand...
Click to collapse
I had the same bug, I couldnt open the settings to uninstall apps. settings opened, but you couldnt open the actual app settings.
I fixed it by doing a nandroid backup, doing a factory reset, then loading the backup I just made and settings worked again, no other changes made?
I found this out when I first rooted the G3 and had another big issue, could not solve it, did a factory reset, loaded my first nandroid, but it was corrupted, so I did another full wipe and loaded the nandroid I made before I did my first factory reset (the one that I had issues with) but it worked great all problems gone.
So, the posts in this thread have been very helpful. DPI is usually one of the first tweaks that I administer to any rom. I'd found zero success in using my normal modification of editing the build.prop file directly, I started getting force closes from system apps even when not going below 530DPI. Using App Settings module in Xposed to modify Android System rectified this for me, all is right now. :good:
Changing the DPI of the G3 really transforms it, so much so that I would have a hard time going back to stock DPI now. I had done this once before on my G2 and Note II and loved the results, but those were also not as large to begin with. The G3 comes out of the box as if it's designed for visually impaired users.
One other subtle tweak I did was set my status bar to solid black using G3 TweaksBox. Not only does it match the black nav bar now, but I think it just looks better than that gray color LG uses by default in non-LG apps.
I am trying to change the screen density, as the default 480 density is just ridiculous.
But editing the build.prop changes nothing, as I saw in another thread, I should be modifying the file that references my phone model which should be build.ze551.dual.2p3GHz.prop (Zenfone 2 4GB, 32GB, 2.3ghz, dual sim).
But even including the line: "ro.sf.lcd_density=360" (this line does not exist there, I have to add it). Nothing happens after reboot.
I believe that I am editing the correct file as I tried to add the line "qemu.hw.mainkeys=0" and after reboot I got screen software buttons.
but the density does not change. I know I could use the method of execute in adb: "adb shell wm density 360" but with this method the swiftkey keyboard software does not work correctly and I heard that changing the density with build.prop it would work.
Can someone help me ? I really want to change the density.
check this thread: http://forum.xda-developers.com/zenfone2/general/tip-adjusting-dpi-root-t3098690
aktentasche said:
check this thread: http://forum.xda-developers.com/zenfone2/general/tip-adjusting-dpi-root-t3098690
Click to expand...
Click to collapse
Thanks. but as I said this method is what I am trying to avoid because a lot of apps stops working correctly like Whatsapp, Instagram, Photo editing software, Swiftkey, power save app, etc.
I've done the build.prop method on a lot of other devices and it always work like a charm, everything works nice. But for some reason it is not working with Zenfone and I am trying to figure out why.
JuniorBR790 said:
Thanks. but as I said this method is what I am trying to avoid because a lot of apps stops working correctly like Whatsapp, Instagram, Photo editing software, Swiftkey, power save app, etc.
I've done the build.prop method on a lot of other devices and it always work like a charm, everything works nice. But for some reason it is not working with Zenfone and I am trying to figure out why.
Click to expand...
Click to collapse
I'm also having the same issue. I haven't been able to find any sort of solution for this either. I might try a custom ROM just do I can do the build.prop change for density.
Sent from my ASUS_Z00AD using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
***Works on ONE UI 4, 4.1 and 5 for all versions of s20, s21 and s22 (now works on S22U too)***
Due to some bad optimizations by Samsung , we are facing a lot of battery issues and a couple of random lags. With this script, I have got something between 7h and 9h of SOT.
In a few tests in Brasil, the users are getting a much better battery life. This script have some things like:
=> Removing items that can sometimes be undesirable according to the user, so you can select wich services will be disabled, such as bixby, AR camera features, microsoft apps, google apps (not the main like gmail and photos, but the secondary ones like bookmar provider, docs), ANT (there are people who don't even know what it is so this is usually useless here in Brazil).
=> Disable the Camera Light Sensor which is a bug on One UI 4.0 and 4.1, galaxy S have a light sensor to calculate the automatic brightness, however, since One UI 4.0 it ends up using the front camera for this, annihilating the screen time of the device. When camera light sensor are disbled, the device will properly use the dedicated light sensor and the automatic brightness be more responsive and battery friendly.
=> Enable the option to disable Ram Plus, where the 0GB option will appear in the options above 2GB, which you can disable if you want (Recomended only on ONE UI 4, because One UI5 comes with disable RAM Plus option available) .
Throughout the script, it will ask which item you want to be removed, so if you use DEX, just answer "n" when it asks if you want to remove it.
Resetting the device to factory defaults will completely reverse everything the script does, so it is not permanent and does not void your device's warranty.
The procedure is simple:
In your cellphone:
1 - Enable Developer options and USB Debug:
Go to Settings > About Phone > Software Information click on "build number" several times until it appears that developer mode is enabled.
2 - Now go to Settings > Developer Options and click enable right at the top of the page and look for the USB Debugging option and enable it too.
3 - Connect your phone to the computer and if a window appears asking for permission, grant it (you will be granting permission for your computer to access your phone in developer mode. If it doesn't appear now, no problem, this window may appear later when we run the script, but it usually appears right here.
On your PC:
4 - Download the script:
ONE UI 4 and 5: Debloat and optimize Galaxy S20 S21 AND S22 for ONE UI 4-5
5 - Extract it and run the "debloat and optimize" file (perhaps at that time the aforementioned window will appear on the cell phone asking for permission).
The script will guide you asking for all possible options which are 10:
Remove Microsoft apps?(You can reinstall the app later from the playstore)[Y/N]?
Remove Netflix?(You can reinstall the app later from playstore)[Y/N]?
Remove Facebook?(You can reinstall the app later from playstore)[Y/N]?
Remove Google Apps?(You can reinstall the app later from playstore)[Y/N]?
Remove DEX?(You will no longer have the DEX function)[Y/N]?
Remove ANT?(If you don't know what it is, you can remove it without fear)[Y/N]?
Remove Bixby?(You will still have the bixby routines, but no longer the voice assistant)[Y/N]?
Remove Augmented Reality Functions from Camera?(You will no longer have AR Sticker in Camera)[Y/N]?
Apply adaptive brightness correction? (by disabling the camera light sensor, improving auto brightness response and increasing battery life)[Y/N]?
Enable Ram Plus extra options? (enable options to increase or disable Ram Plus in Settings, Device and Battery Support, Memory) [Y/N]?
6 - When it finishes, the phone will restart. All options can somehow be reversed by downloading the apps from the Play Store again, except for DEX, Bixby and Sticker AR mode, but which can be reversed with another script that I'm still building or resetting your device to factory defaults.
Any doubt I will be available
My personal options are: ONE UI 4 - Y for all except dex (because I use dex, if you won't use, you can safe remove)
ONE UI 5: Y for all except Dex
After the script you can safe reinstall some apps back like Facebook and Google from Playstore, but now this will comes without Samsung bloatware.
Edit1: the link are updated to a new version fixing one hand mode
Edit2: release of a version to apply on ONE UI5.
Edit3: Unifying One UI 4 and 5 scripts, added new options for Game Launcher, ledcover and Wellbeing, doesn't disable Android Auto anymore, and added fix for media provider Bug in all S21 series.
and finaly the link to rollback the script: Rebloat ONE UI 4.1+ (works on ONE UI 5 too)
danilomazzaro said:
View attachment 5782457
***Works on ONE UI 4, 4.1 and 5 for all versions of s20, s21 and s22 (except for S22U)***
Due to some bad optimizations by Samsung , we are facing a lot of battery issues and a couple of random lags. With this script, I have got something between 7h and 9h of SOT.
In a few tests in Brasil, the users are getting a much better battery life. This script have some things like:
=> Removing items that can sometimes be undesirable according to the user, so you can select wich services will be disabled, such as bixby, AR camera features, microsoft apps, google apps (not the main like gmail and photos, but the secondary ones like bookmar provider, docs), ANT (there are people who don't even know what it is so this is usually useless here in Brazil).
=> Disable the Camera Light Sensor which is a bug on One UI 4.0 and 4.1, galaxy S have a light sensor to calculate the automatic brightness, however, since One UI 4.0 it ends up using the front camera for this, annihilating the screen time of the device. When camera light sensor are disbled, the device will properly use the dedicated light sensor and the automatic brightness be more responsive and battery friendly.
=> Enable the option to disable Ram Plus, where the 0GB option will appear in the options above 2GB, which you can disable if you want (Recomended only on ONE UI 4, because One UI5 comes with disable RAM Plus option available) .
Throughout the script, it will ask which item you want to be removed, so if you use DEX, just answer "n" when it asks if you want to remove it.
Resetting the device to factory defaults will completely reverse everything the script does, so it is not permanent and does not void your device's warranty. If you want, there are a Revert back script too.
The procedure is simple:
In your cellphone:
1 - Enable Developer options and USB Debug:
Go to Settings > About Phone > Software Information click on "build number" several times until it appears that developer mode is enabled.
2 - Now go to Settings > Developer Options and click enable right at the top of the page and look for the USB Debugging option and enable it too.
3 - Connect your phone to the computer and if a window appears asking for permission, grant it (you will be granting permission for your computer to access your phone in developer mode. If it doesn't appear now, no problem, this window may appear later when we run the script, but it usually appears right here.
On your PC:
4 - Download the script:
ONE UI 4.1+: Debloat and optimize Galaxy S20 S21 AND S22 except S22U v2
ONE UI 5: Debloat and optimize Galaxy S20 S21 AND S22 for ONE UI 5
5 - Extract it and run the "debloat and optimize" file (perhaps at that time the aforementioned window will appear on the cell phone asking for permission).
The script will guide you asking for all possible options which are 10:
Remove Microsoft apps?(You can reinstall the app later from the playstore)[Y/N]?
Remove Netflix?(You can reinstall the app later from playstore)[Y/N]?
Remove Facebook?(You can reinstall the app later from playstore)[Y/N]?
Remove Google Apps?(You can reinstall the app later from playstore)[Y/N]?
Remove DEX?(You will no longer have the DEX function)[Y/N]?
Remove ANT?(If you don't know what it is, you can remove it without fear)[Y/N]?
Remove Bixby?(You will still have the bixby routines, but no longer the voice assistant)[Y/N]?
Remove Augmented Reality Functions from Camera?(You will no longer have AR Sticker in Camera)[Y/N]?
Apply adaptive brightness correction? (by disabling the camera light sensor, improving auto brightness response and increasing battery life)[Y/N]?
Enable Ram Plus extra options? (enable options to increase or disable Ram Plus in Settings, Device and Battery Support, Memory) [Y/N]?
6 - When it finishes, the phone will restart. All options can somehow be reversed by downloading the apps from the Play Store again, except for DEX, Bixby and Sticker AR mode, but which can be reversed with another script that I'm still building or resetting your device to factory defaults.
Any doubt I will be available
My personal options are: ONE UI 4 - Y for all except dex (because I use dex, if you won't use, you can safe remove)
ONE UI 5: Y for all except Dex
After the script you can safe reinstall some apps back like Facebook and Google from Playstore, but now this will comes without Samsung bloatware.
Edit1: the link are updated to a new version fixing one hand mode
Edit2: release of a version to apply on ONE UI5.
and finaly the link to rollback the script: Rebloat ONE UI 4.1+ and 5 (works on ONE UI 5 too)
Click to expand...
Click to collapse
Is this tips work's on S21 fe ?
Does this script disable samsung pay/wallet?
Diegogyn said:
Does this script disable samsung pay/wallet?
Click to expand...
Click to collapse
It didn't for me
dicky_101 said:
Is this tips work's on S21 fe ?
Click to expand...
Click to collapse
Yes, works for any s20, s21 and s22 variant. The camera light sensor was fixed on one UI 5
Diegogyn said:
Does this script disable samsung pay/wallet?
Click to expand...
Click to collapse
It doesn't disable Samsung pay.
I can't see any difference with battery life on my s21 fe after debloating by your guide. At least it didn't go wrong either.
Hi. I can't run the script for s21 with OneUI 5. the grant permission window doesn't appear. No window after connection and after runnig script too. But another version of ADB (from minimal ADB tool) on my PC is working and permission window is appearing when it is need. It seems your ADB version have some modifications. How can i run this script with another working ADB on my PC. I've tried and cleared "Revoke USB debugging authorisations" too. But no changes. Thanks for any help.
UPD: it is working on another PC. Thanks!!
damcio200 said:
I can't see any difference with battery life on my s21 fe after debloating by your guide. At least it didn't go wrong either.
Click to expand...
Click to collapse
Are you using A12 or A13? Ifound a new bug on One Ui 5 and I will add to script. This bug are happening with android media provider, this make device never deep sleep. If you want try, you can run again and select "n" for all, the scrip will fix media provider bug.
danilomazzaro said:
Are you using A12 or A13? Ifound a new bug on One Ui 5 and I will add to script. This bug are happening with android media provider, this make device never deep sleep. If you want try, you can run again and select "n" for all, the scrip will fix media provider bug.
Click to expand...
Click to collapse
I'm on Android 13. You mean to run the same script and press "N" in all cases ? Or there is a refreshed link in the first post ?
Hi! The native messaging app is no longer notifying me when I receive an SMS. I'm on Android 12. Any suggestions? Thank you very much! =D
damcio200 said:
I'm on Android 13. You mean to run the same script and press "N" in all cases ? Or there is a refreshed link in the first post ?
Click to expand...
Click to collapse
I did updated the file for One UI 5. You can download it again and run. I have suggested "n" for all because this skip direct for optimization lines (only for not override your previous selected options). On this version, you will get at the end one message like: "S21 variant detected". If this message appears, the proper code for fix media provider are executed well.
danielfilosofia said:
Hi! The native messaging app is no longer notifying me when I receive an SMS. I'm on Android 12. Any suggestions? Thank you very much! =D
Click to expand...
Click to collapse
Open message app. Go to settings -> notifications. Check if "allow notifications" are toggled. if yes and still no receiving notifications, on this same path, go to "notifications categories" and check if all your categories have notifications allowed.
danilomazzaro said:
I did updated the file for One UI 5. You can download it again and run. I have suggested "n" for all because this skip direct for optimization lines (only for not override your previous selected options). On this version, you will get at the end one message like: "S21 variant detected". If this message appears, the proper code for fix media provider are executed well.
Click to expand...
Click to collapse
Alright, did the update just now. Will let you know if I see any difference now
danilomazzaro said:
I did updated the file for One UI 5. You can download it again and run. I have suggested "n" for all because this skip direct for optimization lines (only for not override your previous selected options). On this version, you will get at the end one message like: "S21 variant detected". If this message appears, the proper code for fix media provider are executed well.
Click to expand...
Click to collapse
I did everything correctly, but there is no message like you say should be. I did it twice just to be sure. Look at the screenshot below. Everything seems fine to me.
damcio200 said:
I did everything correctly, but there is no message like you say should be. I did it twice just to be sure. Look at the screenshot below. Everything seems fine to me.
View attachment 5787293
Click to expand...
Click to collapse
Yep. Thanks for your feedback. With your screenshot I found the bug. I will fix in a couple of hours, but if you want to try you can fix it in one of two ways:
1- the easyest way: right click on .bat file, search G991 and change to G990, save and run again.
OR
if you know about adb, you will run "adb shell dumpsys deviceidle whitelist +com.google.android.providers.media.module" (without quotes)
danilomazzaro said:
Open message app. Go to settings -> notifications. Check if "allow notifications" are toggled. if yes and still no receiving notifications, on this same path, go to "notifications categories" and check if all your categories have notifications allowed.
Click to expand...
Click to collapse
Thanks man! The problem was here. Sorry my "noob" ;-)
Worked on S21 FE
Thanks
It looks like battery really lasts longer. However. I noticed that I am missing digital wellbeing and game launcher.
I assume that script deleted them? Does reverse script returns them? And if it does should I?
Sita021 said:
It looks like battery really lasts longer. However. I noticed that I am missing digital wellbeing and game launcher.
I assume that script deleted them? Does reverse script returns them? And if it does should I?
Click to expand...
Click to collapse
I'm uploading the new version with this two packages selectables (you dont need run it). To restore this two disabled packages (wellbeing and game launcher) you need run this scripts:
Wellbeing reenable:
Digital Wellbeing reenable.zip
drive.google.com
Game Launcher reenable: https://drive.google.com/file/d/12lzbApvl66zlEMSlWhveVx3rh88wCE2U/view?usp=share_link
PS: thanks for your feedback