[ALL ROM][4.4+] How to Completely Reduce Lag - Galaxy Grand Prime General

I already discussed this on the Prime thread, but I'll just post it into a new post for everyone.
This will also enable "Android Go Mode" on Android Oreo and above!
https://forum.xda-developers.com/an...mod-low-ram-property-patcher-android-t3737373
Skip to the second post if you just wanted the entries.
After an extensive research on how Grand Prime's Stock ROMs doesn't lag too much, I seem to have found the answer.
Samsung was able to get away from the lagging by adding this entry to the build.prop of the stock Grand Prime:
Code:
ro.config.low_ram=true
This entry sets the ROM to detect that the device has low RAM and thus, keeps background processes to a minimum. It also reduces system animations and visual effects. This is a standard with all Android builds (starting with 4.x), so this will work even on an AOSP-based Custom ROM.
Fun fact: This is also L Speed's "Low RAM" setting.
This works fine on most ROMs, especially TouchWiz ROMs running Android 5.0.2 and 5.1.1-based, and enables "Android Go" on AOSP Oreo ones. But the situation is different on other versions of Android before 8.0.
It completely disables SystemUI tinting. So it means that the status bar wouldn't be tinted, even if the app supports it.
It will also disable Google Now on Tap (on 6.0+) and Google Assistant (on 7.0+). The Assistant Go app can be installed, but only works on Oreo.
It disables lock screen wallpapers on TouchWiz ROMs running Android 6.0+, and AOSP ROMs running 7.0+ (Prime and Miix are unaffected). This also makes the Samsung Launcher crash on Samsung Experience (running Android 7.0+) ROMs. Again, Prime and Miix are unaffected.
But fortunately, this re-enables SystemUI tinting starting 5.0+.
Code:
persist.sys.force_highendgfx=true
This also works on 7.x ROMs, too. But this would never work on KitKat. The Google Asistant (or Now on Tap), though, wouldn't be re-enabled.
Few tests also shown that this entry caused more lagging. So add it at your own risk.

How to do this?
Simply add these entries to the build.prop of any ROM you wish to reduce the lag.
Code:
# Go Mode - HybridTeam 20180406
ro.config.low_ram=true
# Unquote at your own risk. Re-enables SystemUI tinting
# persist.sys.force_highendgfx=true
It's preferred to add it on the top, just after device information props (few ROMs, especially TouchWiz ones, has the same entry, though set as false).
Tell me if it works for you or not below!

Jovic77 said:
How to do this?
Simply add these entries to the build.prop of any ROM you wish to reduce the lag.
Code:
# Sets device as low-RAM but still enables SystemUI tinting - HybridDevelopers 20170730
ro.config.low_ram=true
persist.sys.force_highendgfx=true
This better works if you put it after RIL/Stagefright entries.
Tell me if it works for you or not below!
Click to expand...
Click to collapse
how can i find RIL/Stagefright entries

Seif.Kemo said:
How to do this?
Simply add these entries to the build.prop of any ROM you wish to reduce the lag.
how can i find RIL/Stagefright entries
Click to expand...
Click to collapse
It's just the preffered location. You can put it anywhere.

Jovic77 said:
It's just the preffered location. You can put it anywhere.
Click to expand...
Click to collapse
So i can put it below ro.pip.gated or qemu.hw.mainkeys=0?

Other Dimitri said:
So i can put it below ro.pip.gated or qemu.hw.mainkeys=0?
Click to expand...
Click to collapse
Yep. But just make sure that a similar entry doesn't exist at the top, for this will not work.

Updated for new updates on these entries, and Oreo compatibility!

Related

[MOD][XPOSED] Phab7 v1.00 no-reboot UI Switcher

Phab7 is an on-the-fly UI switcher: select Phone, Phablet, or Tablet, then tap the Change button. The switch happens immediately - no reboot needed. A separate option lets you switch settings screen layouts (e.g. the Settings app) between Phone-style (separate screens for categories and details), and Tablet-style (categories and details, side-by-side).
Unlike other solutions, Phab7 has no effect on your apps beyond for their Settings screens. In particular, it will not alter the size or layout of your launcher's icons or dock (nor will it cause the tablet-style app-drawer icon to appear).
Note: Google removed Tablet mode from KitKat, so it is not available if you're running Android 4.4.x.
Installation
Important: if you have a beta version of Phab7 (v0.9x) currently installed, you must uninstall it before installing v1.0. Android will refuse to install it if one of the betas is present.
if you don't already have XposedInstaller on your system, see this thread
install Phab7.apk the same way you'd install any other sideloaded app
enable Phab7 by reopening the XposedInstaller app and selecting 'Modules'
tap directly on the checkbox next to Phab7, then back out and reboot
after the initial reboot, you can open the Phab7 app and change UIs as many times as you wish without further reboots
Notes
Tablet UI mode is only available when running ICS or JB (v4.03 thru 4.3x). While Phab7 supports KitKat, it does not add back the Tablet mode that Google has removed.
Whether Phab7 works on your device depends almost entirely on your ROM's creators. If they removed the graphics and layouts needed for a given UI mode, SystemUI.apk is guaranteed to force-close when you select that mode. A "Keep-Or-Cancel" dialog will automatically restore your settings after 12 seconds if this happens when you choose an incompatible UI mode. Clear the "Unfortunately" popup and you're good to go.
the Settings-layout feature takes effect when an app is first launched. To see its effect on running apps (e.g. the system's Settings app). tap the "Recents" button and swipe the app away , then reopen the app.
File
Phab7.apk - v1.00
Credits
barrmulio - the first to identify the system changes needed to implement alternate UIs
_TB_TB_ - author of TabletUI trigger who first realized that UI-switching could be done by an Xposed module
History
2014/01/22 - v1.00 - initial stable release
2014/01/05 - v0.99 - added keep-or-cancel dialog
2013/12/13 - v0.97 - added scaling for all modes
2013/12/10 - v0.96 - fixed KitKat-specific bug
2013/12/09 - v0.95 - added Tablet UI scaling
2013/11/30 - v0.92 - added support for KitKat
2013/11/27 - v0.90 - initial release
Gonna try it on S4 v4.3
Sent from my GT-I9505 using XDA Premium 4 mobile app
---------- Post added at 08:08 AM ---------- Previous post was at 08:02 AM ----------
Ring of FC ;p
Sent from my GT-I9505 using XDA Premium 4 mobile app
Tried it, changes fine to tablet mode. Just a few layout issues. And the nav glow doesn't fade.
See screenshot.
Xperia Z running eXistenZ 4.10 rom.
Subscribed, this looks promising.
{
"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"
}
Sent from Z Beast
For me with android 4.1 only settings work and status bar and nav bar don t work
Sent from my LT26i using Tapatalk
Great job. tested working on CM10. status bar looks monster
it could have better you provided DPI settings along with phab7. though i can manage with app settings
the give attachment is flashable zip i just extracted phab7.apk and installed normally
why this is not available in xposed Repo..
reversegear said:
why this is not available in xposed Repo..
Click to expand...
Click to collapse
I think because it's new and in beta
Sent from Z Beast
Now we need not wait for updated Paranoid!! OK Paranoid does do some of this stuff better/more consistantly than AppSetting and this module, but ...
Great!
Wanna outdo Paranoid: Tablet mode mostly more usable in landscape, so ... get the idea?
EDIT: Results using the mod on my LG P500 running cm-10.2 with 4,4 Google Now launcher: I can use AppSetting module to force this launcher to rotate but it does not handle this correctly.
Settings UIs work as promised! This is what I really missed not having Paranoid.
Navigation bar: Question -- what if I do not use one (phone has HW buttons--remember those)? Module should accept phone setting.
Anyway, tablet mode: Repeated FCs of systemUI until I changed to other mode:
Phablet mode: Navigation bar shows as promised. Notifications not effected.
Phone mode: No way to correctly test with this launcher.
Went back to default: Icon bar, no navigation bar.
If I remember from Paranoid, tablet mode put notifications bar on the bottom right. Phablet left it on top, opening to half-height, had to change dpi to fit it to screen width correctly. So tablet mode, once working, would either have both at bottom right justified or just the notifications as chosen in the phone's settings! Someone check current Paranoid.
Compatible with KitKat?
Wysłane z mojego Ascend G510 przy użyciu Tapatalka
Don't flash that zip!
reversegear said:
the give attachment is flashable zip i just extracted phab7.apk and installed normally
Click to expand...
Click to collapse
OMG!!!! My apologies! The zip that was posted (in error) was only for the Hisense Sero 7 Pro and contained a tablet-specific mod to SystemUI.apk.
The script in that zip checks for the model, so it should have failed if you tried to flash it on any other device. However, if somehow you succeeded in flashing it, you will have to restore your ROM's original SystemUI.apk. The original, along with SystemUI.odex if present, is in your /system/app folder with '-org' appended to it. If you have problems handling this, I can create an update.zip to do this for you.
Again, my apologies - it was late...
This's amazing. Thanks a lot dev. Looking forward for new versions:laugh:
Saeedblack said:
For me with android 4.1 only settings work and status bar and nav bar don t work
Click to expand...
Click to collapse
Dovidhalevi said:
tablet mode: Repeated FCs of systemUI until I changed to other mode:
Phablet mode: Navigation bar shows as promised. Notifications not effected.
Phone mode: No way to correctly test with this launcher.
Click to expand...
Click to collapse
Generally speaking: if "nothing happens", the issue probably lies within Phab7; if SystemUI FCs, then it's probably your ROM.
For Phab7 problems, XposedInstaller's debug.log should identify the problem - you can find it in /data/data/de.robv.android.xposed.installer/log/debug.log. Pull the file and attach it to a posting. For ROM problems, I'd need a logcat log that covers the time period when the FC occurred. If you need help generating one, let me know. (logcat logs for Phab7 issues are certainly welcome too, however, they have to include system startup to be useful.)
For SystemUI FCs, a possible cause is vendor customization of a particular NavBar layout that wasn't carried over to the other versions. The tablet I use is a perfect example. It defaults to Phablet and has a screenshot button (which most everyone hates). The button wasn't implemented for Phone since they assumed it would never be used, so SystemUI FCs in Phone UI when their code goes looking for a button that doesn't exist. To get it to work, I had to patch their systemui.apk to get rid of both the button and the code that references it. This is not something I'd want to try on a device I don't own.
Bottom line: I'd be happy to implement reasonable workarounds to enhance compatibility with the widest range of devices, but even then, not all modes will work with all devices.
dolorespark said:
Generally speaking: if "nothing happens", the issue probably lies within Phab7; if SystemUI FCs, then it's probably your ROM.
For Phab7 problems, XposedInstaller's debug.log should identify the problem - you can find it in /data/data/de.robv.android.xposed.installer/log/debug.log. Pull the file and attach it to a posting. For ROM problems, I'd need a logcat log that covers the time period when the FC occurred. If you need help generating one, let me know. (logcat logs for Phab7 issues are certainly welcome too, however, they have to include system startup to be useful.)
For SystemUI FCs, a possible cause is vendor customization of a particular NavBar layout that wasn't carried over to the other versions. The tablet I use is a perfect example. It defaults to Phablet and has a screenshot button (which most everyone hates). The button wasn't implemented for Phone since they assumed it would never be used, so SystemUI FCs in Phone UI when their code goes looking for a button that doesn't exist. To get it to work, I had to patch their systemui.apk to get rid of both the button and the code that references it. This is not something I'd want to try on a device I don't own.
Bottom line: I'd be happy to implement reasonable workarounds to enhance compatibility with the widest range of devices, but even then, not all modes will work with all devices.
Click to expand...
Click to collapse
and this is an older device.
I am attaching the debug.log, but changing the name to debug.txt to get in on here.
On my N7, checking 'tablet' in system settings changes the module's menu just fine but has no effect on Rom settings.
Setting default ui to phablet didn't help either.
Debug log: https://www.dropbox.com/s/zlp89tbus6o23qi/xposed_debug_20131127_194414.log
N7(flo)-Rastakat-franco.kernel
N4(mako)-PKK-franco.kernel
dolorespark said:
Generally speaking: if "nothing happens", the issue probably lies within Phab7; if SystemUI FCs, then it's probably your ROM.
For Phab7 problems, XposedInstaller's debug.log should identify the problem - you can find it in /data/data/de.robv.android.xposed.installer/log/debug.log. Pull the file and attach it to a posting. For ROM problems, I'd need a logcat log that covers the time period when the FC occurred. If you need help generating one, let me know. (logcat logs for Phab7 issues are certainly welcome too, however, they have to include system startup to be useful.)
For SystemUI FCs, a possible cause is vendor customization of a particular NavBar layout that wasn't carried over to the other versions. The tablet I use is a perfect example. It defaults to Phablet and has a screenshot button (which most everyone hates). The button wasn't implemented for Phone since they assumed it would never be used, so SystemUI FCs in Phone UI when their code goes looking for a button that doesn't exist. To get it to work, I had to patch their systemui.apk to get rid of both the button and the code that references it. This is not something I'd want to try on a device I don't own.
Bottom line: I'd be happy to implement reasonable workarounds to enhance compatibility with the widest range of devices, but even then, not all modes will work with all devices.
Click to expand...
Click to collapse
for me it have been FC for first run and after reboot it never appear again but don t have FC
also here you are i attached log that you notice
No TabletUI in KitKat
MMeester said:
On my N7, checking 'tablet' in system settings changes the module's menu just fine but has no effect on Rom settings. Setting default ui to phablet didn't help either.
N7(flo)-Rastakat-franco.kernel
Click to expand...
Click to collapse
Is this a KitKat-based ROM? Sadly, all of the code and resources needed to support Tablet UI have been stripped from Android v4.4. Because Phab7 v0.9 doesn't make provisions for this change, the UI switcher doesn't work. I will fix that ASAP so that at least Phone and Phablet are available. Restoring Tablet UI may be more than an Xposed module can/should do, but I'll investigate...
However, the Settings screen mod should still work. As mentioned in the OP, if the system's Settings app is already running, you'll have to remove it from "Recents" and reopen it. If you reboot with "Tablet-style" settings in place and it still doesn't work, let me know.
Dovidhalevi said:
and this is an older device.
I am attaching the debug.log, but changing the name to debug.txt to get in on here.
Click to expand...
Click to collapse
You didn't describe where you're having problems. During one session, one of your other Xposed modules (com.wisdomsky.xploit) failed every time, even when Phab7 hadn't made any changes. After a reboot, the problems were gone but so were Phab7's standard messages. What changed?
dolorespark said:
You didn't describe where you're having problems. During one session, one of your other Xposed modules (com.wisdomsky.xploit) failed every time, even when Phab7 hadn't made any changes. After a reboot, the problems were gone but so were Phab7's standard messages. What changed?
Click to expand...
Click to collapse
I first tried it before rebooting, then realized that it cannot work that way and rebooted. Then Phab7 worked as described.
Since wisdonsky operates on the notifications bar, could be that the interaction with tablet mode trying to move that is what is noted.
dolorespark said:
Is this a KitKat-based ROM?
Click to expand...
Click to collapse
Yes.
However, the Settings screen mod should still work. As mentioned in the OP, if the system's Settings app is already running, you'll have to remove it from "Recents" and reopen it. If you reboot with "Tablet-style" settings in place and it still doesn't work, let me know.
Click to expand...
Click to collapse
Sadly, no change in settings app after a reboot. Do you need any logs?
Thank you for looking into the issue.
N7(flo)-Rastakat-franco.kernel
N4(mako)-PKK-franco.kernel
Can I ask what in the system side of things this is targeting? Only asking because I had a problem with Tablet mode where I changed compatibility mode, and that then caused constant FC of SystemUI.
Also where are the settings stored? I managed to get out of the fc loop, but am now left with a layout problem of my System UI. Nothing major, but even if I change SystemUI, it persists.
Any help appreciated.
Metallijim said:
Can I ask what in the system side of things this is targeting? Only asking because I had a problem with Tablet mode where I changed compatibility mode, and that then caused constant FC of SystemUI.
Also where are the settings stored? I managed to get out of the fc loop, but am now left with a layout problem of my System UI. Nothing major, but even if I change SystemUI, it persists.
Click to expand...
Click to collapse
Phab7 is designed to do as little as possible to achieve its goals - in some cases, perhaps too little. For Phone and Phablet, it does some setup when SysUI starts and that's it. For Tablet, it has to be slightly more intrusive but not much.
Sadly, I had no way to test compatibility mode so I'm not surprised that it has issues. Recovery from most any problem should be as simple as switching to another UI. In this case, getting out of TabletUI, then returning without touching the compatibility button should cure what ails you.
If you get repeated FCs in SystemUI, one way out is to leave the toast up there, then from ADB, delete /data/data/com.e_vertise.dopa.phab7/shared_prefs/settings.xml. When you dismiss the toast and SysUI restarts, you should be back to your device's default settings.
Note: if I understand things correctly, Android may try to reload SysUI's Java code several times using the same process before it gives up and kills that process. Once it restarts SystemUI using a new process, you're certain to be back to normal if you've deleted Phab7's settings file.
We'll soon find out if it works on KitKat. Yes I know how to disable Xposed from recovery. Using it on KitKat doesn't seem to cause any crashes, but it doesn't do anything at all on KitKat.
Sent from my Nexus 7 using Tapatalk 4

[Xposed][APP][1.0.1][ICS-LP]SwipeBack2 - Finally back alive

Download link is in the thread, do not use the "Download" section in XDA DEVDB, my network has some problems with it for now.
After nearly one year's silence, SwipeBack is now back alive, known as SwipeBack2.
SwipeBack2 is the continue of SwipeBack. It has still the basic feature, swipe-to-return gesture, inspired by the library SwipeBackLayout written by @ikew0ng(a.k.a. IssacWong, 碎星iKe, 碎iKe). It provides a smooth, nature-like and highly customizable swipe-to-return gesture. This module is initially a wrapper of SwipeBackLayout in Xposed, and was welcomed widely by Xposed users. Gradually it has gained much new features that is more than SwipeBackLayout.
If you have installed the old SwipeBack, please uninstall it first, and then you can install SwipeBack2
Features:
* Swipe-to-return gesture
* Per-activity settings which means you are able to customize settings on <strong>each page of each app</strong>
* Experimental hacks for Lollipop (may not work, use with caution, do not turn it on globally)
* More experimental features are coming in future releases.
Note that SwipeBack2 is now only a rewrite and a port to Lollipop (but it still works on ICS/JB/KK). It has many work to-do, as:
* Pure-gesture mode (disable scrolling effects, enables compatibility with apps that consist of Fragments but not Activities, and can work with Browsers)
* Fully-costomizable trigger area (at <strong>any</strong> position on the edge, to fix compatibility with apps that has a gesture like drawers already)
* Automatic bug report and crash log submitter
* More (<strong>advices are always welcome)
SwipeBack2 is free software released under the terms of GNU GPLv3. Source code available at https://github.com/PaperAirplane-Dev-Team/SwipeBack
Changelog
1.0.2:
- Fix icons
- Add ability to show a settings shortcut to the current app activity in notif bar
This is a minor release. We will go to fix several bugs in the next few weeks
1.0.1:
- Fix crashes in main app UI
- Fixes for apps with wallpaper
Downloads
From Xposed Store: http://repo.xposed.info/module/info.papdt.swipeback
From Google Play Store: https://play.google.com/store/apps/details?id=info.papdt.swipeback
FAQs:
Q: Why renamed to SwipeBack2?
A: Because SwipeBack2 is completely rewritten, and is refactored to have a better stability and flexibility. And another reason is, that SwipeBack (us.shandian.swipeback) is blacklisted by Alipay because of the unsecure SwipeBack, so I just renamed it to SwipeBack2 (info.papdt.swipeback), hoping that it will not be blacklisted any more.
Q: Would you add feature X / fix bug X?
A: Feel free to send emails or open issues on GitHub page. I may not have time to reply to you all, but I will take a look at bug reports and feature requests and have the resonable ones implemented in new releases.
Q: SwipeBack is great! Do you accept donations?
A: Well, not now.
XDA:DevDB Information
SwipeBack2, Xposed for all devices (see above for details)
Contributors
PeterCxy
Source Code: https://github.com/PaperAirplane-Dev-Team/SwipeBack
Xposed Package Name: info.papdt.swipeback
Version Information
Status: Beta
Created 2015-03-31
Last Updated 2015-03-31
Crashes when loading the app, gets to about 80% then fc
Edit: logcat https://www.dropbox.com/s/jikihl6rkfijgiu/logcat_and_device_info.zip?dl=0
Not for me, works as it should. Everything fine. Just have to experiment a bit with the Lollipop Feature, few Apps don't like it as stated in the App.
Ty!
apps loaded well but cannot change settings any of the app "unfortunaly swipeback 2 has stopped" please fix it
using in note 2 phantom 13 ROM
Cannot get it working on a Nexus 5 with CM12, I don't know if I'm doing anything wrong but I don't think so. Just installed, enabled it on Xposed and restarted. It's not CAF, so it may be fault of the rom. What android and rom are you using?
EDIT:
Just disabled every other module and it's working now. I will try to find which one is causing the problem and report it because it may be useful to someone.
Works fine expect one bug - on Lollipop when I go to the task manager after swipe back an app it shows the launcher screen as the thumbnails for the swiped back app.
Works great on LG G2 XenonHD 5.0.2:good:
Fantastic Modul, easy to use. Just awesome. Thank you.
https://dl.dropboxusercontent.com/u/73964661/SCR_20150331_190900.mp4
https://dl.dropboxusercontent.com/u/73964661/SCR_20150331_184109.mp4
Galaxy S5 G900F CM12 Fusion ROM
good to see new version thanks for continuing this module
Sent from LG Optimus G
Im glad someone revived this amazing module ... please keep it updated ... i will keep giving feedback and any bugs if i find on this thread
Edit 1 Bugs-
1. While swiping back on Whatsapp it goes back perfectly from the Chat screen to the Chat list. But while Swiping back on other apps like Gallery or Instagram. It doesnt swipe back. It goes to Home Screen.
2.After Swiping back the Recent app page shows wrong thumbnails .. it shows the Home screen as thumbs instead of App last state. (Screenshot Attached)
3.Also after restart i got a com.location.google has stopped ... i may have said the term wrong .. but it was something regarding Location.
4. SB2 force closes if Global settings option is pressed.
Notes:
I have unistalled old Swipeback and Freshly Installed this.
I love this app and will continue to send feedback to make it best.
--
Kitkat - LG G2 D802 International Model - Stock Firmware.
Been waiting for this module to work, thx for it. Unfortunately there are some bugs, the Gmail animation is fine but the rest are broken with in the status bar, like in the video https://vimeo.com/123755651 (nexus 4 stock 5.0.1 and Franco kernel) . Keep up the good work
nicholes said:
apps loaded well but cannot change settings any of the app "unfortunaly swipeback 2 has stopped" please fix it
using in note 2 phantom 13 ROM
Click to expand...
Click to collapse
Same here...;/ (and I know logcat or gtfo
can anyone confirm if it is working on kitkat or not(mine dont work)
Expect the called bugs, great app!
crash at loading apps and breaks recent app menu
nicholes said:
can anyone confirm if it is working on kitkat or not(mine dont work)
Click to expand...
Click to collapse
it runs fine on my Nexus 5 running the latest SlimKat
For us new to this... What does it do?
Simply swipe to go back to the screen you were at previously?
HorstiG said:
Fantastic Modul, easy to use. Just awesome. Thank you.
https://dl.dropboxusercontent.com/u/73964661/SCR_20150331_190900.mp4
https://dl.dropboxusercontent.com/u/73964661/SCR_20150331_184109.mp4
Galaxy S5 G900F CM12 Fusion ROM
Click to expand...
Click to collapse
What is that widget you use? I attached a snip of it.
DeisNet said:
Been waiting for this module to work, thx for it. Unfortunately there are some bugs, the Gmail animation is fine but the rest are broken with in the status bar, like in the video https://vimeo.com/123755651 (nexus 4 stock 5.0.1 and Franco kernel) . Keep up the good work
Click to expand...
Click to collapse
Same here :/
Moto G 5.0.2
mcdavid said:
What is that widget you use? I attached a snip of it.
Click to expand...
Click to collapse
Hi, thats Zooper Widget Pro, Handmade

[APP][Xposed] Force 3 dots menu

Hi!
This is a very simple module: it forces all apps to use the 3 dots menu. I've created this because on CyanogenMod, for some reason, when i remap my menu button not all apps use the 3 dots menu. Some apps, like Titanium Backup, don't show any button at all, so i can't use the menu.
This module force that apps to show always the 3 dots menu, or a button to access it (Titanium shows an entire 'MENU' button).
No interface, just install and activate it.
Download link: http://repo.xposed.info/module/com.robertogl.yesmenubutton
Source: https://github.com/robertoglxda/Force-3-dots-menu
Tested on Cyanogen 5.1.1.
Changelog:
18/08/2015
V1.0
- Initial release
P.S. This is not a problem of all devices, so use this only if you need it.
P.S.2 I've looked inside MenuBeGone for this code (another Xposed module). Thanks to @adi1133 for that!
Just a quick suggestion for future development: you could work on adding a simple interface and let users toggle between force 3 dots and hide it
Either way keep up your good work with Xposed modules :highfive:
Markox89 said:
Just a quick suggestion for future development: you could work on adding a simple interface and let users toggle between force 3 dots and hide it
Either way keep up your good work with Xposed modules :highfive:
Click to expand...
Click to collapse
Well, thanks
I don't know if that is possible: I mean, if you want to disable the 3 dots you can disable the module, but the hook I've done is performed during the boot (at least, I think) of the phone, so an option like that won't work with a system turned on. A possibility is to create a list of app for which the users want the 3 dots menu, but I don't have time to look at it at the moment...
Inviato dal mio GT-I9505 utilizzando Tapatalk
robertogl said:
I don't know if that is possible: I mean, if you want to disable the 3 dots you can disable the module, but the hook I've done is performed during the boot (at least, I think) of the phone, so an option like that won't work with a system turned on.
Click to expand...
Click to collapse
What I meant was to let users choose if they want 3 dots always on (like it's now) or always off, both on a system wide basis
It could be a fair module improvement for its future if you'll have time, just my two cents
(I'm just speculating, no clue about what's possible, not really into Xposed development [emoji14] :angel
Markox89 said:
What I meant was to let users choose if they want 3 dots always on (like it's now) or always off, both on a system wide basis
It could be a fair module improvement for its future if you'll have time, just my two cents
Click to expand...
Click to collapse
This would be easy, but the same result can be achieved disabling the module from Xposed Installer. I really appreciate the suggestions, but for now i think i'll keep the module as it is. Less code, less problems
Also, it is not useful to enable a module that does nothing. It would not be a problem, but it would not be nice
Update first post with github's link with source.
Not working
Unfortunately it doesn't work an a Sony Xperia Z3 dual (D6633) running Xperia/AOSP NavBar Buttons
(also Xposed module which I use to do nothing else but to switch the back and recent apps-buttons.
Back moved to the right side, recent apps the other way.
No idea why.
Stockrom (rooted) 4.4.4
exis_tenz said:
Unfortunately it doesn't work an a Sony Xperia Z3 dual (D6633) running Xperia/AOSP NavBar Buttons
(also Xposed module which I use to do nothing else but to switch the back and recent apps-buttons.
Back moved to the right side, recent apps the other way.
No idea why.
Stockrom (rooted) 4.4.4
Click to expand...
Click to collapse
Have you tried disabling NavBar buttons module?
Inviato dal mio GT-I9505 utilizzando Tapatalk
This module is interesting to me because I'm a Nexus Player user. As discussed in other threads such as http://forum.xda-developers.com/nexus-player/help/3-dots-menu-t3067105 and http://forum.xda-developers.com/nex...sed-supports-android-5-0-x86-devices-t3146150, Google removed the 3-dots menu from Android TV devices as of Android v5.1 and higher. It is a very frustrating change that adversely affects multiple apps and your kind of module is what I was hoping to see as a possible solution. I just installed and enabled your module, then rebooted the device but I'm disappointed to report that this module does not yet restore the 3-dots menu on apps that are installed on the Nexus Player. Some examples of affected apps are AdAway, Xposed Installed and ZArchiver. The Xposed log does not indicate any errors with your module but I'd be happy to do any testing that may be needed to get this module working on the Nexus Player. I cannot overstate how helpful it would be if you could restore this critical feature to many apps that are limited in functionality by Android v5.1 and higher on Android TV devices.
Nope, because that isn't an option anyway.
I mean, I prefer NavBar over this. So probably it's a NavBar failure.
GabbyWC said:
This module is interesting to me because I'm a Nexus Player user. As discussed in other threads such as http://forum.xda-developers.com/nexus-player/help/3-dots-menu-t3067105 and http://forum.xda-developers.com/nex...sed-supports-android-5-0-x86-devices-t3146150, Google removed the 3-dots menu from Android TV devices as of Android v5.1 and higher. It is a very frustrating change that adversely affects multiple apps and your kind of module is what I was hoping to see as a possible solution. I just installed and enabled your module, then rebooted the device but I'm disappointed to report that this module does not yet restore the 3-dots menu on apps that are installed on the Nexus Player. Some examples of affected apps are AdAway, Xposed Installed and ZArchiver. The Xposed log does not indicate any errors with your module but I'd be happy to do any testing that may be needed to get this module working on the Nexus Player. I cannot overstate how helpful it would be if you could restore this critical feature to many apps that are limited in functionality by Android v5.1 and higher on Android TV devices.
Click to expand...
Click to collapse
I will look at this. I've you tried GravityBox? It should do a similar thing.
exis_tenz said:
Nope, because that isn't an option anyway.
I mean, I prefer NavBar over this. So probably it's a NavBar failure.
Click to expand...
Click to collapse
It's not an option, but the method this module hooks is here from android 4.x (maybe also 2.3), and it is the same on 5.x, so it should work. I don't know what NavBar does, so I can't say that there isn't an incompatibility. Or maybe Sony has changed a lot that...
Inviato dal mio GT-I9505 utilizzando Tapatalk
robertogl said:
I will look at this. I've you tried GravityBox? It should do a similar thing.
Click to expand...
Click to collapse
Hello, Roberto, and thanks for the reply. I did inquire about this matter with the developer of GravityBox, @C3C076, not too long ago. What he suggested was for me to try the "force overflow menu button" option found in his app's miscellaneous tweaks menu. It did not work, unfortunately, but he did state that the feature was carried over from Android 4.x and was not tested on Lollipop. I don't know if you happen to live in a country where the Nexus Player is sold but if you require the hardware in order to develop for it, this STB can be purchased for less than $100 USD at a retailer such as Walmart.
GabbyWC said:
Hello, Roberto, and thanks for the reply. I did inquire about this matter with the developer of GravityBox, @C3C076, not too long ago. What he suggested was for me to try the "force overflow menu button" option found in his app's miscellaneous tweaks menu. It did not work, unfortunately, but he did state that the feature was carried over from Android 4.x and was not tested on Lollipop. I don't know if you happen to live in a country where the Nexus Player is sold but if you require the hardware in order to test such a feature, this STB can be purchased for less than $100 USD at a retailer such as Walmart.
Click to expand...
Click to collapse
Yes, that options doesn't work for me too on lollipop. I'll search something in next days.
Inviato dal mio GT-I9505 utilizzando Tapatalk
I can see from your XDA profile that you live in Italy. Nexus Player should also be available in that country according to http://www.androidpolice.com/2015/0...nd-italy-norway-spain-sweden-and-switzerland/. I wish you the best of luck in solving this problem and am ready to help with any testing which you may require.
Just tried (uninstall NavBar). Than your app works.
Unfortunately I prefer NavBar over this handy add-on, so I will deinstall it.
But if definitely works an a Z3!
Sorry,didn't mean to be rude!
exis_tenz said:
Just tried (uninstall NavBar). Than your app works.
Unfortunately I prefer NavBar over this handy add-on, so I will deinstall it.
But if definitely works an a Z3!
Sorry,didn't mean to be rude!
Click to expand...
Click to collapse
No problem
Well, this modules work on similar things, so an incompatibility is expected. I don't think I can't make it compatible, sorry...
Maybe you can play with NavBar options and see if something change.
GabbyWC said:
I can see from your XDA profile that you live in Italy. Nexus Player should also be available in that country according to http://www.androidpolice.com/2015/0...nd-italy-norway-spain-sweden-and-switzerland/. I wish you the best of luck in solving this problem and am ready to help with any testing which you may require.
Click to expand...
Click to collapse
Could you people post here the Xposed log with my module active?
Inviato dal mio GT-I9505 utilizzando Tapatalk
Here's a screenshot which contains a recent Xposed log from my Nexus Player. The reason why I cannot copy-and-paste the text is because the 3 dot menu which provides the "Save to SD card" option is missing.
GabbyWC said:
Here's a screenshot which contains a recent Xposed log from my Nexus Player. The reason why I cannot copy-and-paste the text is because the 3 dot menu which provides the "Save to SD card" option is missing.
Click to expand...
Click to collapse
Could you please try the apk attached? Also, post the Xposed log after installing this.
Okay, I installed the test1 version and rebooted my Nexus Player. The 3 dot menu is still not restored but there's a lengthy Xposed log this time. There's currently no way of saving the log file as a document or copying-and-pasting the text inside of it so I had to take screenshots of the entire log (page by page) which required 49 screenshots in total. If you extract the contents of the two zip files in to one directory, you'll see that the PNG files are named in sequence with their date and time stamps. I hope this helps.
GabbyWC said:
Okay, I installed the test1 version and rebooted my Nexus Player. The 3 dot menu is still not restored but there's a lengthy Xposed log this time. There's currently no way of saving the log file as a document or copying-and-pasting the text inside of it so I had to take screenshots of the entire log (page by page) which required 49 screenshots in total. If you extract the contents of the two zip files in to one directory, you'll see that the PNG files are named in sequence with their date and time stamps. I hope this helps.
Click to expand...
Click to collapse
Well, thanks and sorry for that, i didn't imagine something like that. If this happens again, check the errors before doing such number of screenshot: they are always the same. So, try this. It seems that Google change something on Nexus Player...

[JB][P] AppOpsXposed Re 1.30.6 - Now with EdXposed support!

AppOpsXposed Re is a module for the Xposed framework that restores AppOps functionality on recent Android versions.
"Re" (short for "revised") version got a few updates compared to the original, making it work on newer Androids, like Nougat and Oreo.
Original thread by caspase: AppOpsXposed - AppOps for 4.3+
What is AppOps? What's the difference between AppOps and permissions?
AppOps is a feature that is included in Android starting with JellyBean 4.3. It allows the user to limit an apps functionality, regardless of permissions granted; for example, you can prevent an app from reading your contact list, or accessing your current location. The difference between revoking permissions and using AppOps is that in the latter case, the affected app will not know what happend and, most importantly, will (usually) not crash. In the case of the location, the app will think that the location is currently unavailable. In the case of your contact list, the app will see an empty list.
An important thing to keep in mind is that AppOps was not intended for end-users, so some features do not work as advertised. Limiting "Keep awake" for example has no effect, as this was not implemented by the Android developers.
Compatible with all Android versions from 4.3 'Jelly Bean' to 9.0 'Pie'.
Credits:
Xposed Framework: rovo89 & Tungstwenty
Original module: caspase
Download: AppOpsXposed Re on Xposed Module Repository
How to report problems efficiently?
- Enable the Debug log in settings
- Use functions that don't work as intended
- Export the logs from Xposed app and put them on PasteBin
- Post on the XDA thread the link along with more information about your device
XDA:DevDB Information
AppOpsXposed Re, Xposed for all devices (see above for details)
Contributors
Xspeed, caspase
Source Code: https://github.com/XspeedPL/AppOpsXposed
Xposed Package Name: at.jclehner.appopsxposed.re
Version Information
Status: Stable
Current Stable Version: 1.30.6
Stable Release Date: 2019-03-09
Created 2018-08-10
Last Updated 2019-03-08
you rock dude. I had to settle for my 2nd favorite rom for my daily driver bc it had no AppOps. Now I'm free!!! when I get time I will flash back and give this a try.
Thanks for sharing!!!!
Hey, thanks for your work (even though I'm still on Nougat).
I have three questions though:
- when I go into an app's persmissions screen the sliders in 1.30.4 turned green when turned on and grey when off. In 1.30.5 they're always grey, can this be modified so they change color depending on how their status is?
-also in an app's permission screen, the name of each permission was differently formated and translated in 1.30.4. Could this be ported over to your version of AppOps?
-the next thing didn't work with 1.30.4 either but maybe it can be fixed (or my phone simply isn't compatible), when I go to designs and change the icons of AppOpsXposed, none of them changes in the phone's settings / app overview screen.
I have some screenshots attached. My phone is the HTC 10 on Nougat, regularly rooted
sutobe said:
- when I go into an app's persmissions screen the sliders in 1.30.4 turned green when turned on and grey when off. In 1.30.5 they're always grey, can this be modified so they change color depending on how their status is?
Click to expand...
Click to collapse
It's really easy to change, I am experimenting with colors at the moment.
When I was releasing this I prioritized functionality over looks, but it will be done, no worries.
-also in an app's permission screen, the name of each permission was differently formated and translated in 1.30.4. Could this be ported over to your version of AppOps?
Click to expand...
Click to collapse
I am aware of that, the labels got messed up when I was porting the code base. I'll see what can be done.
-the next thing didn't work with 1.30.4 either but maybe it can be fixed (or my phone simply isn't compatible), when I go to designs and change the icons of AppOpsXposed, none of them changes in the phone's settings / app overview screen.
Click to expand...
Click to collapse
It actually works like the previous version. To see those changes you can either reboot or restart the "UI" process.
To make it work auto-magically a lot more work would be needed, and to be honest, for a single time use feature it's not worth it in my opinion.
It works
But after disabling some ops (permissions) those apps on going notification don't show the notification bar although they're running in the background.
But if i revert it then the notification shows
FC after start at HTC One M7 with Android 5 ROM
Sent from my HTC One using XDA Labs
Nice this cutie is now offical.
Used your inoffical mod since oh my gosh ..long time ago...about a year
on LP, MM, Nougat
:good:
Awww yeah!... Thankyou for this!
Auto close app everytym when i open :/
Mockingbird_ said:
Auto close app everytym when i open :/
Click to expand...
Click to collapse
How to report problems efficiently?
- Enable the Debug log in settings
- Use functions that don't work as intended
- Export the logs from Xposed app and put them on PasteBin
- Post on the XDA thread the link along with more information about your device
Click to expand...
Click to collapse
Maybe try caspase appsops.
For me it works now better with my nougat device. Better permisson controll* and less errors on apps with blocked permissions :good:
*possible to block audio focus on music, video, notification
Hi! What's the difference of this and the appopsxposed without the "re"?~
nijihana said:
Hi! What's the difference of this and the appopsxposed without the "re"?~
Click to expand...
Click to collapse
Original module was supposedly abandoned. This version was updated to support newer Androids, including Nougat and Oreo.
"Re" is short for "revised".
Xspeed said:
Original module was supposedly abandoned. This version was updated to support newer Androids, including Nougat and Oreo.
"Re" is short for "revised".
Click to expand...
Click to collapse
Thank you!
Any chance blocking apps permission to change system settings?
A language file for translation would be nice
edit:
Now i see modul can block "write system" e.g. it can denin on playstore / service but some apps still
change system ( froce app to run in backround) after install an update.
So if an app has no permission to write system how it can change settings even if i denin playstore & service permisson to change system? ^^^^
This app is broking the item "Fingerprint scanner" in the settings of phone. I get FC when I try to open it. My phone is HTC U11, Adrroid 8.0, ROM LeeDroid.
@Xspeed: 'Add OP_BOOT_COMPLETED' in the hacks menu still doesn't work after checking the box and rebooting, there is no option anywhere to control whether an app can start on boot. I'm running a pure AOSP ROM so there is no Privacy Guard, etc. Is there a workaround/fix for this?
Thanks!
@Xspeed Just curious, what are the chances of this getting updated for Pie?
toBsucht Psp said:
Now i see modul can block "write system" e.g. it can denin on playstore / service but some apps still
change system ( froce app to run in backround) after install an update.
So if an app has no permission to write system how it can change settings even if i denin playstore & service permisson to change system? ^^^^
Click to expand...
Click to collapse
What settings is the app changing after you disabled the permission?
smallKING81 said:
This app is broking the item "Fingerprint scanner" in the settings of phone. I get FC when I try to open it. My phone is HTC U11, Adrroid 8.0, ROM LeeDroid.
Click to expand...
Click to collapse
I am going to need LogCat during the FC from you to be able to see what's exactly wrong.
AnonVendetta said:
@Xspeed: 'Add OP_BOOT_COMPLETED' in the hacks menu still doesn't work after checking the box and rebooting, there is no option anywhere to control whether an app can start on boot. I'm running a pure AOSP ROM so there is no Privacy Guard, etc. Is there a workaround/fix for this?
Click to expand...
Click to collapse
This boot run blocking is actually a hack that works only on some devices, to be honest it doesn't work on mine either
bkkzak said:
@Xspeed Just curious, what are the chances of this getting updated for Pie?
Click to expand...
Click to collapse
If you mean EdXposed, you're unfortunately out of luck. This module HEAVILY relies on so called "resource hooks" that EdXposed doesn't support at the moment. Sorry
What is the difference between this app and AppOpsX from F-Droid? does it work on Android Pie?
MDV106 said:
What is the difference between this app and AppOpsX from F-Droid? does it work on Android Pie?
Click to expand...
Click to collapse
To be honest I've never heard of AppOpsX. The two applications work completely different under the hood.
There is stuff non-Xposed apps can't do, like adding a shortcut to AppOps on the app details activity.
Regarding your second question, YES!
The fresh new 1.30.6 version supports Android 9.0 Pie and EdXposed.
I managed to make it work by separating resource hooking related stuff to a second module and made it optional for other functionality.
Simple? Absolutely. Clever? Maybe. AppOps? Xposed. Sorry :/

[MOD] T280 5.1.1 [ARK3][ODEX] Ultra Stock - Samsung Experiance

T280 - Ultra Stock [ARK3] Samsung Experiance
Based on the latest stock firmware, with limited Google and Samsung bloat. What was removed can be installed through Play Store, or Galaxy Apps Store.
Added apps and features are a compilation, that were hand picked from various OEM firmwares, both phones and tablets built between 2015 and 2016.
This is a system backup from TWRP so, please backup before restoring this copy of my backup.
WHAT'S INCLUDED
FULL FEATURED ACCESSIBILITY w/ SOUND DETECTION
FULL FEATURED SECURED LOCKSCREEN
PASSIVE KERNEL
100% OPEN GAPPS COMPATIBLE (Nano installed)
MIRRORLINK
NEARBY
SCREEN MIRRORING
MAGISK ROOT
BUSYBOX
DRIVE LINK
SIDE PANEL (Mini softkeys - portrait only)
CAR MODE
TABLET SVOICE (Customizable wake up command, Mic always on & minimized)
SPEN (Finger input)
SNOTE4
SCRAPBOOK
EHANCED VOICE RECORDER (3 Modes)
DUAL SAMSUNG VIDEO PLAYERS (STOCK TABLET & PHONE POP OUT STYLE W/ DLNA CLIENT)
INTEGRATED ENHANCED PHOTO, VIDEO & AUDIO CLIP EDITING
THEMES & FULL THEME STORE
FEATURES
MULTIWINDOW RESIZE AND POP OUT WINDOW
NATIVE HVEC DECODING (buggy... needs recompiled driver)
PIN TO SCREEN
MEMORY BUG oFIX/WORK AROUND
WRITE TO EXTERNAL MEDIA FIX
KNOX & UNUSED INTERNATIONAL INPUTS REMOVED
DISABLED SAMSUNG MEMORY MANAGEMENT
REMOVED SMART MANAGER AND ITS SYSTEM COMPONENTS
CLEANED UP NOISE & BOOSTED MIC RECORDING GAINS
UNLOCKED ACCESSIBILITY FEAUTURES & OPTIONS
INSTALL TO EXTERNAL SD CARD ENABLED w/ ALWAYS ON/OFF OPTIONS
UNLOCKED QUICK SETTING TOGGLES
J5 & TAB4 SETTINGS UI MENUS (TOGGLED REBOOT TO SWITCH)
J5 PHONE SPOOF (For more additional enhanced apps on the store)
WIFI & GOVERNOR BOOST ENABLE/DISABLE
MODDED HOST FILE w/ ON/OFF
MODDED CSC FEAUTURES
ADDED MISSING FRAMEWORKS AND PERMISSIONS
ADDED REQUIRED MISSING LIBRARYS AND ENHANCEMENTS
LOGGING IS CLEANER THAN FACTORY - (Because of framework was looking for missing components, and my minimal debloating of required system components, which most custom firmwares have hidden by turning off logging, which is a no no.)
OUTSTANDING ISSUES
NONE! Well, as far as I have seen in with my testing, smooth and stable, without any random app issues.
Well, there are known issues that dont effect function, and some of which have work arounds.
The minor issues are... with Enhanced Voice Recorder, not being able to create voice to text memo. This tablet has a different audio muxer schema than what the Enhanced Voice Recorder application expects, for voice to text function. It only effects creation of words from recorded voice. No errors, just a lack of text output.
Car Mode only has half of its functions, since the tablet is not a phone. Outside of not being able to answer calls and messages... voice commands to play music and route with maps are fully functional. Maybe there is a way to hook blue tooth phone through tablet to control messages and calls as a head unit would. Then if that is the case, the car mode function is 100% functionable.
Signature and face lock are functional, but the settings ui have different call routine than tablets frameworks. The issues also includes a few other minor areas within the settings menu, depending on which settings ui you use. So the reason to toggle between one settings ui and the other. Once you play around with each settings ui, you will find the disadvantages of the few broken settings areas cancel out, by their availability being on the other ui.
If wanting face lock, secure lock screen is a work around. It allows proper call routines to enable face unlock, location unlock, voice unlock, and the rest or googles secure lock features that samsung does nof implement on this tablet.
There are about four (2 to 3 wee issues on each of the two settings ui that are available) hardly used areas that have issues. One is motion, within motion settings, the hook is not proper for the tablet, since the ui is hooked for phone. Plus even if motion settings had a proper hook, the lack of light sensor and other required sensors would make the setting as useless as bonding or connection boost, which is within the phone settings ui. Sounds is broken in phone settings uil but is fully functional in Tab 4 ui. Most of the sounds settings can be done within the volume control, and the apps that have settings for alarms, such as calander.
The fix can be done by a dev, to compare stock settings ui and framework.apk, and the other two variants of settings ui and framework.apk from the firmwares i used.
Because the tablet framework.apk is 90% complete over a full featured phone, the last issue is video player. The res folder within the framework.apk is missing the images for media players and other things. Adding the proper res files should clear up the black boxes for missing buttons. The buttons work, just no lables or images to inform function. Anyway you will need to get familiar with the functions to enjoy the benifits of the phone video player with pop out display and.... drum roll... DLNA client.
I have a thread on what I have done to make this rom happen. For refreference and some details as to whats been done, can be read there.
https://forum.xda-developers.com/galaxy-tab-a/how-to/converting-tab-st-280-to-samsung-j500f-t3911418
DOWNLOADS
Final release... no updates will be made, so don't ask.
https://mega.nz/#!onRRxaqD!4xetR27vQhrcjGXyxoOhysyq8uU2kYGdFRJQlKCH-z0
Unzip in your twrp backup folder, and restore in twrp. Be sure to wipe caches.
Here are some screen shot images of some of what is available on this firmware.
{
"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"
}
thank you man !!! really nice job !! i will test it ... first flash twrp and then restore your image !! fine ....
can you tell me how can i enable magisk (root) , you say (you may need to enable it with a utility or shell command) but not how
thanks
// after install magisk 18.1 its enabled "!!! thank you
A
yasars said:
thank you man !!! really nice job !! i will test it ... first flash twrp and then restore your image !! fine ....
can you tell me how can i enable magisk (root) , you say (you may need to enable it with a utility or shell command) but not how
thanks
// after install magisk 18.1 its enabled "!!! thank you
Click to expand...
Click to collapse
Thank you for giving it a try...
This is a test build before i include all the script mods.
You will not have root or passive kernel until I finalize my build.
This test build will keep your existing kernel and root, if rooted. Just will not have super su console installed. That will need to be installed to control su, if needed. I understand magisk can control su, but never tested.
The reason i did not include the scrips in the build, is to make sure if any issues that may come about in testing are not because of kernel or scripts that i plan on including.
I am running the scripts myself without issues, unless you consider loosing about 1.5hrs of total battery run time an issue. I get around 13 hours continuous run time, and around 15 hours stock.
The benefits in keeping hicups minimal with streamed media and heavly decoded formats, outway having an extra hour or two of battery time.
Once I make the final build, it will include the scripts and latest stock kernel with magisk root and the passive kernel with magisk root, as an addon option.
The scripts will be within the system with the user to setup as they need them with the given utilities in the rom, or with tasker if one should choose.
There will be a tutorial on each script and how to use the tools to enable or disable them.
The only mods included in the test build are, build.prop, install to external, modded hosts file, modded csc features file, and its utility to edit along with a few other non stock utilities.
You can manually remove utilities not needed, and replace with what ever to suit your needs within the system. Just make sure you do not consume the system partions free space. I find between 200mb to 120mb free space as a minimum, any smaller could raise issues.
Also i forgot to add not fota or security updates...they have been disabled or removed, not completely just inactive. I doubt samsung will provide anything further with this tablet. As i never saw much for Note 8.0, which is a better and more top of the line tablet for its day. Its up to modders to push getting a kernel built for newer custom builds, in which one can move on to when the opertunity comes.
I admit the mods are not a requirement, but do come in handy at times, escpecially once you get to play with them.
thank you man !!! really nice job !!
Thank you for this, working really well and makes the tab much more useful with the version of android we are stuck with
yasars said:
thank you man !!! really nice job !! i will test it ... first flash twrp and then restore your image !! fine ....
can you tell me how can i enable magisk (root) , you say (you may need to enable it with a utility or shell command) but not how
thanks
// after install magisk 18.1 its enabled "!!! thank you
Click to expand...
Click to collapse
mr_ppp said:
Thank you for this, working really well and makes the tab much more useful with the version of android we are stuck with
Click to expand...
Click to collapse
Thank you! Your the first that has responded back on trying my testing version. I will post a final next week some time. There has been a bit of clean up that did not transfer to the testing firmware. Some of which will require a one time run of a script to add a few files into data. They will allow mic calibration and some modules to load without logcat errors.
The main parts of the added functions are basic, but will make the basic functions more full featured like the bigger tablets. I am really liking the built in editing and finger stylus in most apps, and keyboard writing pad. Plus the voice recorder works very well, minus the lack of text conversion from spoken words.
Once the mic calibrates, you can easily record soft sounds without much hiss or digital noise. Though Svoice does mess with the internal mic settings, so as a simple fix to resolve mic gain issues, i recommend putting the tablet to sleep by pressing the power key, and wait 5 to 10 seconds and wake.
A hidden feature is backdrop screen saver. Its included in android tv, but will run fine on any device. It allows screen off when charging and sleeping. Once the tablet is fully charged it goes into dim backdrop images display. You dont need to touch the tablet to know its fully charged. If you dont want the backdrop to stay on, just press the power button once and the display will stay off.
It looks like nobody else has any comments, let alone any requests... not that I can do anything more.
It just would be nice to see a dev step in an consolidate the two settings ui apks into one and clean out the unused settings sections and correct the bad sections, which are small yet would make this a near perfect update for our tablets.
Have tested a functional smart face unlock, using secure lock screen. It is a work around for the broken settings section for face detection. Settings will not save after creating the face, and FC. Using secure lock screen will enable secure face.
Also this new firmware disables unsecure lockscreen options, which some may miss.
If using smart face for the first time, it may be a bit cumbersom, but it seems to work fairly well, once you get use to being detected.
After rebooting, face detect will not function for security. After unlocking, face detect will enable swipe once your face is detected. If not, it will stay in the unlock mode you set, until unlocked.
Blue tooth, location, and movement unlock will function similarly.
Signature lock is broken by the settings ui build being used by the system.
Voice note to txt is broken by the systems mixer and PCM mappings
I do not recommend using the voice to text function in voice recorder, mostly because it amplifies background noise and sets each word spoken as isolated audio, which may work with other voice audio to txt applications.
As a quick update... found the issues with voice recorder, and resolved it to be 98% reliable on the first try after reboot. Usually one would need to put the tablet to sleep and wait a few seconds to reset mic gain.
Found mic gain file missing along with other files that are not part of the latest build.
Will correct with a one time usage script to repopulate the missing files, which are not part of the existing system, into data
The mic gain will automatically adjust every reboot, if needed, and when voice recorder is used as well. It may take a few reboots or voice recorder uses to properly adjust once this firmware update is applied on a dirty flash.
No, i did not resolve voice to txt feature though voice recorder. But the memo feature does work just as clean as all the other recording options. Just with a 5 minute timer.
I also tested changing the wake up command to Svoice. You can reset the command, if you go into apps manager and clear out data for voice recorder and voice command. Svoice has a reset for itself in its settings.
Still messing around before finalizing and releasing my modded firmware.
I have noticed improvements overall, just looking deeper into obtaining more features if possible, like private mode and quick connect. As i touched upon them, but assumed limitations from framework and system ui.
Who knows, it may be some over looked files and such.
glad to see you are working in the t280. I still use this tablet for daily use but the stock rom it's not what I need.
I hope you release the rom very soon! Thanks!!! keep Going!
Lichsv said:
glad to see you are working in the t280. I still use this tablet for daily use but the stock rom it's not what I need.
I hope you release the rom very soon! Thanks!!! keep Going!
Click to expand...
Click to collapse
I am planning on releasing it soon... been testing a bit as i go. Mostly figuring out simplest way to have manual control over enhancements, while having some automation in the process. If i make it simple for me and leave out the abiltiy to revert back an option, many may find some issues that plague them.
Example, not all apps like being forced or moved to external sd card. Already found a few, and started toggling the option when needed. I will update my info to reflect that for reference for this fimware.
Also my hosts file is pretty intensive. It blocks some ads that other blockers dont block, but google has been working diligently in building its ad marketing scheme deeply into apk function. So some streaming apps may function slower than others when updating programmes. Play back may be effected by a delay while ads are not allowed to play, or not start at all unless backed out and restarted again. Old BBC America was that way. Depending of app, slider bar for skipping may not be shown, as all ad breaks are removed. Some show slider bar without ad breaks, and some have ad breaks but may limit half of the ads randomly depending on the server its connected to for ads. All in all, if you find an issue with internet connection or streaming playback, disable the hosts file and try again.
Hosts file and install to external SD, can be toggled on or off on the fly. The only reboot required option is to change settings ui. As each settings ui has a set of options that broaden the tablets abiltities, making it like two devices in one. Some settings carry over from being set by a different ui. So toggling may not be required as much until the tablet is fully setup. Though for my needs, i cant fully stay on one ui over the other, as the options are too varied without any other means to control or use without the ui.
Since nobody has mentioned any Samsung functions or unique apps missing or required... i limited my testing to wee bugs that may pop up on dirty flashes. Yes i have been dirty flashing over and over with different and updated system backups, to find the best or cleanest way to have an issue free update without creating issues if one should need to revert back to stock.
Once i have time i will lay out more updated information about features and included apps.
Okay, here is a snapshot of smanager once you restore my ti backup of the customized settings.
You will need to restore this file in ti backup... https://mega.nz/#!UjJzEa6b!Tl4osQhOUfrNy9i4ntFAvbitbAIKdTl7z787ujG94M4
To restore, just use menu and select import and point to the location of the downloaded backup file. Once restored, smanager will be setup properly for running scripts.
Notice the items in red... they are enabled and will only error when re-launched. All the other non red items are active for launching. Once launched the item will turn red, thus allowing you to quickly deturmine what has been enabled or disabled. They will stay as they are even after reboot.
I set up the defaults this way so there wont be any issues if one is to do a factory reset for a clean install of this firmware.
Notice the last item named run once... it fixes wee issues that the framework cannot install to data. They are small empty files, required for some features to function properly. Also there is a set of settings db files that will update toggles and enable universal functions that may not be seen without need of booting with a different settings ui.
The gear icon next to an item means it will run at boot up, on an internal delay by smanager.
The skull and cross-bones means su enabled. None of the scripts have su commands for safety.
The star means favorite, so like named items can be separated by enabling favorite to keep on top of non favorites.
Done! Updated original page and added a final version firmware for downloading. The previous reply is for final setup to enable features and mods.
gps not working?
juanysara said:
gps not working?
Click to expand...
Click to collapse
Your the first to have any issues, out of the many who downloaded and tried my system backup. Unfortunatly, I deleted by work files from many different factory firmwares, assuming everything was cool, since had very little feedback. I guess I could make another system backup, from my working tablet mods, to replace the one I uploaded on Mega, if others find any more issues.
If you have issues, revert back to your twrp system backup. I assume your model is not the same as mine. The system backup is for the 7.0 wifi only Tab A6.
Im continuously getting an error when i try to restore. extracttarfork() process ended with error=255
juanysara said:
gps not working?
Click to expand...
Click to collapse
emottau said:
Im continuously getting an error when i try to restore. extracttarfork() process ended with error=255
Click to expand...
Click to collapse
Try downloading again from mega, and try again. Else revert back to your system twrp backup.
Hello
I had to go back to the stock ROM and has already returned to work the GPS
It was the only way to make it work properly, I don't know if it's my device failure.
Too bad I can't use this ROM I've lost Snote, very useful to me is there any way I can use it in ROM stock PHE?
Thank you, for your time and your work and sorry for my bad English.
Edit: Sorry if you bother asking, but I'm trying to learn a little bit about android, I created a zip to install Snote, I got it to work but when I give it to create a da FC note Can you tell me it's wrong? thank
https://mega.nz/#!Vw5SEAxD!JAdpdtUQWpEWBQZa6AWdHd-UJDE280fnRwtXNCk02jw
Really tried it hard
Unfortunately GPS is killed and some UI issues in settings .... :crying:
I would really like to see a ROM with SD card integration (Android 6?) because this tab is so kewl.
Would you try to fix this ROM so we could give it a try? :angel:
Boot loop after restore
Tried this but just get a boot loop!
Same here boot looping

Categories

Resources