Related
Lets use our community and collaborate around achieving a solution to a full market with all applications available for download with no restrictions based upon our current resolution.
Spawned from discussion from this thread
A Primer From jnadke
jnadke said:
It's a problem with the Android SDK.
Starting with 1.6, Google introduced screen sizes: Small, Medium, and Large. Our devices have Small Screens (along with the HTC Tattoo). The G1/Dream has a Medium screen, and the Droid/Nexus a Large screen.
The problem is the SDK defaults to Medium and Large screens. It's up to the application developer to test the application for Small screens and proactively add the indicator for Small screen support.
Most developers never bother to indicate the app can run on Small screens, so it gets excluded from your view.
I'm not sure if the small screen thing is linked to the /data or your Google user account. If I knew which, I'd figure out some way to spoof it, so we can get the full market on small screens. If it's on the /data somewhere, then that's a much easier fix.
The fact that clearing your /data and booting up a 480x320 fixes it, seems to indicate it's a value in the /data. It'd be interesting to do a dump of two /data directories with only the market resolution changed and see how they differ on a binary level. Then perhaps we can add a patch to the menu of NoMoRootfs (or a patch that's applied every bootup... or lock down the file that's modified).
If it's on the account, then either you'd have to intercept the Market App's data packet that indicates screen size and modify it proactively, or you'd have to change parts of the SDK to report the screen size as larger than it really is (this would be hard to do because apps use that interface too... you'd have to be able to detect if the request is coming from the Market App).
Click to expand...
Click to collapse
Here is the original 1.6 Vending.apk and de-compiled BakSmali source.
For those not familiar with smali/baksmali here is a short tutorial:
Download the baksmali/smali tools here
Make your changes in the source than recompile the changes back into the Vending.apk by doing the following:
1.) Make changes to files in source and use smali to re-assemble file:
# java -Xmx512M -jar smali.jar -o classes.dex out/*
2.) Then add classes.dex back into the APK with your favorite archive tool (Winzip, Winrar, etc) or via command line like this:
# zip Vending.apk classes.dex
3.) Push the new Vending.apk back out to your device and test out the Vending application.
# adb shell mount -o remount,rw /system
# adb push Vending.apk /system/app
# adb shell mount -o remount,rw /system
Ready set go!
EDIT: This has now been solved by moneytoo in the Tattoo forums
Links:
Link to moneytoo's thread on Tattoo forum
Mirror
myn said:
Lets use our community and collaborate around achieving a solution to a full market with all applications available for download with no restrictions based upon our current resolution.
Spawned from discussion from this thread
A Primer From jnadke
Here is the original 1.6 Vending.apk and de-compiled BakSmali source.
For those not familiar with smali/baksmali here is a short tutorial:
Download the baksmali/smali tools here
Make your changes in the source than recompile the changes back into the Vending.apk by doing the following:
1.) Make changes to files in source and use smali to re-assemble file:
# java -Xmx512M -jar smali.jar -o classes.dex out/*
2.) Then add classes.dex back into the APK with your favorite archive tool (Winzip, Winrar, etc) or via command line like this:
# zip Vending.apk classes.dex
3.) Push the new Vending.apk back out to your device and test out the Vending application.
# adb shell mount -o remount,rw /system
# adb push Vending.apk /system/app
# adb shell mount -o remount,rw /system
Ready set go!
Click to expand...
Click to collapse
Excited to see this solved! I know the brainpower is in this community to do it. Also, if this is solved I bet it could somehow be replicated/ported for tattoo or other qvga androiders and the vogue-android community would get a lot of praise for this.
Before someone chimes in, this is about getting the market to work without the 320x480 trick. The 320x480 trick tends to reset after a few days (which may help debugging if we can figure out why).
Fixing this Market/resolution issue is at the top of my wish.
jnadke said:
Before someone chimes in, this is about getting the market to work without the 320x480 trick. The 320x480 trick tends to reset after a few days (which may help debugging if we can figure out why).
Click to expand...
Click to collapse
interestingly, after using the 320x480 trick about a month ago, my market has not reset. I did it with plemen's evolution donut, an earlier version that had experimental settings in the build.prop which broke google voice (the program would not even run with that build for some reason). been using the same data.img, but various builds since then, and I have FULL market the whole time.
tatnai said:
interestingly, after using the 320x480 trick about a month ago, my market has not reset. I did it with plemen's evolution donut, an earlier version that had experimental settings in the build.prop which broke google voice (the program would not even run with that build for some reason). been using the same data.img, but various builds since then, and I have FULL market the whole time.
Click to expand...
Click to collapse
hrm.. Very interesting indeed..
tatnai said:
interestingly, after using the 320x480 trick about a month ago, my market has not reset. I did it with plemen's evolution donut, an earlier version that had experimental settings in the build.prop which broke google voice (the program would not even run with that build for some reason). been using the same data.img, but various builds since then, and I have FULL market the whole time.
Click to expand...
Click to collapse
Can you post the build.prop?
I was initially unaware of what the "temporary fix" was. It sounds a lot more like it's a server-side account flag that's being set.
I plan on making a temporary solution, until I can figure out what flag is being set and how to fix it.
jnadke said:
Can you post the build.prop?
I was initially unaware of what the "temporary fix" was. It sounds a lot more like it's a server-side account flag that's being set.
I plan on making a temporary solution, until I can figure out what flag is being set and how to fix it.
Click to expand...
Click to collapse
i don't know if the build.prop was the only thing that was changed on that build, but i think so. can't get to it tonight though, work is killing me, gotta dig through my stuff.
Just an FYI for you guys, the market/app size limitation is set by lcd.density.
mssmison said:
Just an FYI for you guys, the market/app size limitation is set by lcd.density.
Click to expand...
Click to collapse
Are you sure? What's your basis for thinking this? If you do a lcd_density of 140 @ 320x480 do the apps go away?
http://d.android.com/guide/practices/screens_support.html
from
http://market.android.com/support/bin/answer.py?hl=en&answer=165590
This page indicates that it's resolution-dependent.
Now, it's possible for certain apps to be missing due to density constraints:
The platform supports a set of resource qualifiers that let you provide size- and density-specific resources, if needed. The qualifiers for size-specific resources are large, normal, and small, and those for density-specific resources are hdpi (high), mdpi (medium), and ldpi (low). The qualifiers correspond to the generalized densities given in Table 1, above.
The platform also provides a <supports-screens> manifest element, whose attributes android:largeScreens, android:normalScreens, and android:smallScreens let you specify what generalized screen sizes your application supports. A fourth attribute, android:anyDensity, lets you indicate whether or not your application includes built-in support for multiple densities.
Click to expand...
Click to collapse
In 320x480 we use a lcd_density of 160.
The rubric says a 320x480 device should be 3.0" to 3.5". That means lcd_density of 164 - 192. You may be missing apps that require "mdpi" (unless the range is a little softer and 160 is in the "mdpi" range).
I could be that changing the density triggers an update to the market. If you cross a density threshold, you might trigger an update from "mdpi" to "ldpi", and it updates resolution as well. Perhaps that's why tatnai's change stuck for so long. He booted up in 320x480 at "ldpi" and when he changed to 240x320 he remained in "ldpi".
mssmison said:
Just an FYI for you guys, the market/app size limitation is set by lcd.density.
Click to expand...
Click to collapse
That actually makes 100% sense.
As most know I've been working on an app to change LCD Density and a few other things. One of the things I've noticed and the the Android SDK makes pretty clear for compatibility sake is the three different types of display targets all of which are linked back to density: http://developer.android.com/guide/practices/screens_support.html
The DisplayMetrics class also reflects this too:
http://developer.android.com/reference/android/util/DisplayMetrics.html
Code:
Constants
public static final int DENSITY_DEFAULT
Since: API Level 4
The reference density used throughout the system.
Constant Value: 160 (0x000000a0)
public static final int DENSITY_HIGH
Since: API Level 4
Standard quantized DPI for high-density screens.
Constant Value: 240 (0x000000f0)
public static final int DENSITY_LOW
Since: API Level 4
Standard quantized DPI for low-density screens.
Constant Value: 120 (0x00000078)
public static final int DENSITY_MEDIUM
Since: API Level 4
Standard quantized DPI for medium-density screens.
Constant Value: 160 (0x000000a0)
I can confirm tonight but if someone wants to now, try running 240x320 in 160 density confirming full market is supported.
I noticed that in 320×480 there are some apps I cannot find. Like an app says there are skins on the market so I click on it and it takes me to the market but it says it cannot be found. Running 320×480 lcd 160, want me to change my density to 164-192. Somewhere in there?
cp0020 said:
I noticed that in 320×480 there are some apparel I cannot find. Like an app says there are skins on the market so I click on it and it takes me to the market but it says it cannot be found. Running 320×480 lcd 160, want me to change my density to 164-192. Somewhere in there?
Click to expand...
Click to collapse
public static final int DENSITY_MEDIUM
Since: API Level 4
Standard quantized DPI for medium-density screens.
Constant Value: 160 (0x000000a0)
Click to expand...
Click to collapse
According to Myn, 160 should work, but you can give it a try.
Keep in mind the skin may be for high-density screens, like the DROID.
Does it matter which one? As long as its 164 and up?
myn said:
That actually makes 100% sense.
As most know I've been working on an app to change LCD Density and a few other things. One of the things I've noticed and the the Android SDK makes pretty clear for compatibility sake is the three different types of display targets all of which are linked back to density:
I can confirm tonight but if someone wants to now, try running 240x320 in 160 density confirming full market is supported.
Click to expand...
Click to collapse
It's linked to density and resolution, in my opinion.
Unfortunately, running 320x240 at 160 doesn't work all that great, I've tried it a long time ago as a test for fixing the market. The home screen gets all bunched up (the applications are all on top of each-other), and there's no app tray.
cp0020 said:
Does it matter which one? As long as its 164 and up?
Click to expand...
Click to collapse
Not really, I'd shoot for somewhere in the middle though, like 176 (I chose that because its divisible by 4, the screen should look better).
Wait, how can it be lcd density controlling the market? For the full market trick when people flash the 320×480 nbh and sign in they are still using there build with lcd density of 110-120. You see what I'm saying? Sorry I might not have a clue what I'm talking about lol
jnadke said:
Not really, I'd shoot for somewhere in the middle though, like 176 (I chose that because its divisible by 4, the screen should look better).
Click to expand...
Click to collapse
OK but just to be on the safe side should I backup my data and start fresh?
cp0020 said:
I noticed that in 320×480 there are some apps I cannot find. Like an app says there are skins on the market so I click on it and it takes me to the market but it says it cannot be found. Running 320×480 lcd 160, want me to change my density to 164-192. Somewhere in there?
Click to expand...
Click to collapse
The applications themselves define in their manifest the supported resolutions:
Code:
<manifest xmlns:android="http://schemas.android.com/apk/res/android">
<supports-screens
android:largeScreens="true"
android:normalScreens="true"
android:smallScreens="true"
android:resizable="true"
android:anyDensity="true" />
</manifest>
With appear to again correspond with the density:
Low density (120), ldpi
Medium density (160), mdpi
High density (240), hdpi
cp0020 said:
OK but just to be on the safe side should I backup my data and start fresh?
Click to expand...
Click to collapse
Ideally fresh data and a virgin gmail. But a non-virgin gmail should be suffice.
Okay, this has been bugging me for a long time. I've been around since the beginning of G1 and have never seen a solution to this. I'm out of town on vacation, so my updates and responses may be slow. I've found a partial solution for this. If you don't want to read the fluff, drop down to Partial Solution sections, but be warned, this is not perfect (yet). Below is a quick spilling of my guts on this. Please excuse any grammar mistakes and fragmented thought. I posted this in DEV because more research needs to be done by someone that knows how this stuff works. If we get this worked out, I'll update this post with whatever information is necessary.
This post takes for granted the reader has some knowledge of file management and manipulation, so I won't get too detailed with how to copy/move/delete files. There is a lot of information here and I know most won't read it all, but I'm trying to get all the detail into this I can think of in hopes others have ideas that we can share.
I DO NOT KNOW THE RAMIFICATIONS OF WHAT THIS DOES! ANYTHING THAT HAPPENS TO YOUR PHONE IS YOUR FAULT, NOT MINE! Etc... Etc... Etc...
Issue: After flashing/Odin/wiping, sometimes the Market takes about a minute to load as does the app and security info screens. The Top Paid button is missing and all that's available is Top Free and Just In. Installing an app takes quite a bit of time. It eventually clears up, but it may take up to a week.
If you restore Market preferences via Titanium Backup or similar app, it can speed it up, but in the long run, you may get cross referenced apps over time or Market problems in general. For example, I install app1 and when it's finished, I select it in notifications and it takes me to app3. Some apps are also missing from Downloads and have to be installed again for them to show up. I also experience Titanium Backup not linking the Market correctly if at all. How to fix that is below, also.
How I Tested: I renamed /dbdata/databases/com.android.vending which reproduced the problem reliably and gave me a working set of databases and .xml's to look at.
Partial Solution: Save a copy of /dbdata/databases/com.android.vending/shared_prefs/vending_preferences.xml and put it back after you've restored your apps and opened Market once (just to lay down the directory structure). There are other files that will get more "stuff" back, but because of issues I've had between vending.apk versions, I choose to restore just this one file. It doesn't seem to change much. You can look in it and find some interesting things, but I've found changing it does very little if anything. Changing local_db_sync_required didn't do anything and it just reverted back to "false" for me.
What you will find, is Market will run quickly again BUT, you have no links so none of your apps show as installed. Although it will probably sync over time, the point of my messing around was fairly instant gratification. Thus the next section.
New Problem: Market speed is normal, but no apps are linked. Hey, I use Titanium backup! Fix Market links works, partially. I have 226 apps backed up in TB (Yes, this is why I wanted to get this working) and when I fixed Market links, it found 167. I fixed them again and it found 9, then 17, then 6 etc... It repeated some apps and never detected others. I checked and some of the "fixed" apps did not show in downloads... So I started looking. Menu -> Legend showed me part of the issue. Smiley face -vs- green M. For some reason, some of my apps were not linking properly. Here's how to get that part working.
Partial Solution: Here's what I did in TB. I filtered by Status: Backed up and Type: User. Starting at the top of the list, I long pressed on the first "smiley face" which means it didn't back up the Market link and if it was "Attached to Market", I Detached it. View in Market and installed the app. When it was done, I backed the app up again and viola, green M showing it backed up the Market link. I did this many, many more times to fix my links. It worked in all occasions as long as I could find the app in the Market. Of course, some apps installed outside the Market cannot be fixed (duh), but all others worked fine.
I still have a problem getting everything attached in one shot. If I fix Market links in TB, I still get strange results, but this is as close as I can get and I found quite a few apps that have not been linked for so long, they were a few revs behind, so I'm happy with how far I've gotten.
Questions that will be asked:
- Why didn't you force attach to Market with TB? Because it didn't work. Some indicated it did, but they didn't show up in Market as installed, they didn't back up as linked and some even reverted back to not being attached and the forced button was available. The above is how I got around all of that.
- What about the other cool DB's and .xml? I didn't find that it was worth any possible issues to restore anything else except this file. That is probably what got me into this in the first place. Your mileage may vary. DB's usually need an update script if any changes are made. If that doesn't happen and the schema doesn't match, that's usually bad. That's why a lot of ROM's require a wipe. The old doesn't match the new...
- Why can't you backup Market with TB now that it is working well? I could and it would probably work, but I know it won't work forever because it didn't before. It also won't help someone else who is in a similar situation. I've been using TB (paid) since it came out and I love it. But, it's not perfect.
- Why should I mess with this instead of waiting for it to fix itself? You probably shouldn't. I've found that if I did a restore of apps, some NEVER go back to the Downloads section without a re-install. That's my concern.
- I don't have any of these problems, why are you posting this? Because I and others have. The universe does not revolve around you. Please move on.
- Why did you post this in Dev? As I said in the beginning, because we need someone who knows how this OS works so maybe a reliable workaround can be had for all. I didn't post in DEV for exposure, I posted here because I started it and I don't know where to go. Maybe a fix can be turned into an app or incorporated directly within a ROM. Who knows? I'm not a DEVing, but I am troubleshooting an issue within the OS.
One thing I've found that helps, is I kinda ignore if it shows up in Downloads in the market after a restore. I check for updates using AppBrain app, it finds all the apps on the phone whether they're in the market or not. Then, whenever an app is updated, it directs you to the market download page. If the market link was broken, that will say "Install" instead of "Update", but an install at that point will update properly, and you'll now have a working market link.
The main goal of having apps show up in the market, IMHO, is updates and uninstalls. Use the system uninstaller rather than the market for uninstalls, and use AppBrain to find updates. Works for me.
Thanks a lot for putting this up! I was banging my head against the wall last night, as I ran into this issue again and couldnt remember how I fixed it on my G1
zimphishmonger said:
Thanks a lot for putting this up! I was banging my head against the wall last night, as I ran into this issue again and couldnt remember how I fixed it on my G1
Click to expand...
Click to collapse
yw
lotherius said:
One thing I've found that helps, is I kinda ignore if it shows up in Downloads in the market after a restore. I check for updates using AppBrain app, it finds all the apps on the phone whether they're in the market or not. Then, whenever an app is updated, it directs you to the market download page. If the market link was broken, that will say "Install" instead of "Update", but an install at that point will update properly, and you'll now have a working market link.
The main goal of having apps show up in the market, IMHO, is updates and uninstalls. Use the system uninstaller rather than the market for uninstalls, and use AppBrain to find updates. Works for me.
Click to expand...
Click to collapse
I rarely uninstall via market. Have an app that throws me straight to the system uninstaller from the apps icon. I like appbrain, but it exhibits the same issue as the Market for me as far as detecting installed apps in some cases. I use the Market for updates and it works fine for me as long as the apps are linked. I think it has something to do with the hash getting messed up in the assets.db
Hey guys,
Seems there's a lot of ways you can improve the speed of Android in general. Some seem to be snakeoil... others, work quite well and there's proof to back it up.
I'm only interested in discussing the latter .
A lot of people have helped me gather a better understanding of Android (hyc, stinebd to name a few) in addition to a lot of Google searching. I am going to compile a list of what I have done, I would like to hear what you guys have done! Most app killer apps / app control will already be addressed, so those tools need not apply... I'm looking for real, permanent fixes here without adding more apps!
I am also trying to have topics that are easy working up to advanced. Obviously the more advanced topics are going to be harder to do. You've been warned.
So here's the disclaimer.
****DISCLAIMER****
Speed is as always relative. That basically means I don't want arguments about which build is faster. I want to argue about how to make every build faster .
Also, these tips should apply to any build, any device... they are pretty generic tips, but are obviously specific to Android, with some idiosyncrasies that apply to our port that wouldn't apply to native Android devices. Some is common sense, others are real ways to tear into the system. Hope you enjoy it!
Topic 1
Difficulty Easy - Apps/Widgets
I've noticed the number of widgets i have on my screens, or the number of apps that I have installed/are running in the background to greatly effect performance, in an obviously negative way.
Once I removed all the widgets (I only have the basic analog clock widget & the Google search widget on one desktop...) this seemed to improve general speed. One minor thing to check is if apps are set to auto/background sync. Only enable the ones you really want syncing, others just check manually.
On this same topic, replacing the launcher (the stock launcher in Android, Launcher2 is quite slow) can help immensely. I like ADW, but I've used LauncherPro in the past and it is good. Zeam also seems like a good launcher. I haven't used Go Launcher EX, I've heard good and bad things about it. Use what works best for you, try 'em all!
The last thing on this topic I would like to mention is animations. Settings -> Display -> Animation -> No animations can make the phone feel quite a bit snappier, obviously at the expense of the look/feel of the OS.
Topic 2
Difficulty Easy - Controlling app 'net Access
This leads me into the next topic, DroidWall. I've noticed that blocking apps from accessing the internet has been a very good thing - it's not so much a performance booster (although it probably does provide a little bump) it's mostly about battery life. Just be warned, if you block an app that is set to background sync, it will probably have very negative effects. Only disable an app's access to the internet with DroidWall after you've checked that app's background sync feature is disabled. I have a few apps allowed in DroidWall, and the rest are blocked. You can "whitelist" everything and check apps you want to block, or "blacklist" everything and check the apps you want to allow. It's a little annoying to remember to enable/disable DroidWall (I use the DroidWall widget to enable/disable it globally) but if you do, it is much better - you have complete control over how apps access the 'net on your device. It is available on the Market.
Topic 3
Difficulty Moderate - SD cache/readahead tweaking
The only reason I'm calling this one 'moderate' is the number of choices you have for settings for this... It's basically telling the SD card how much to hold on to or... read "ahead" if you will . This was turned way up in FRX07, (from 256kb to 2048kb or 2mb...) and I think this might be the source of a lot of the complaints of 'mini-resets' if you will where the boot animation is suddenly seen after a long system hang...
So some cards will work better with a larger setting - I've heard some with spankin new C6 cards that said 3072kb or 3mb was a good setting. Others have found a sweet spot at 256kb or 1024kb (1mb).
There are two ways of doing this - you can hack the init in the rootfs and adjust the setting manually, or be lazy like me and use SD Booster (from the Market). Adjusts the same settings, and they are applied immediately!
I would like to find a "sweet spot" - a good default if you will. Can folks test out 512kb and 1024kb, see if you have any more mini-resets within Android or any other slowness, etc... Obviously this isn't a cure-all for the slowness or the mini-resets, what we're looking to do is mitigate the effects. So let's focus on that, thanks!
Topic 4
Difficulty Moderate - Overclocking
Overclocking is obviously one relatively easy way to improve the speed of Android. In your startup.txt, add a line
Code:
acpuclock.oc_freq_khz=710400
for example to overclock to 710.4mhz. How did I find this value? I actually put in 714000, but if you look at dmesg near the beginning you'll see "ACPU running at ..." - that's what clock is the actual maximum. It goes in 19.2khz increments.
Feel free to experiment with how high your phone can go, just be warned that the higher you go the potential for failure goes up as well . Phone shouldn't blow up, but it might not work correctly or at all. Rebooting and scaling it back will fix it.
Here's the full *example* startup.txt:
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod400 acpuclock.oc_freq_khz=710400"
boot
You can put the command anywhere in the cmdline section, just make sure it's between the quotes and at least one space between each command.
Topic 5
Difficulty Advanced - How Android Manages Memory/apps
Ok, I'm going to take two approaches to this. The first, is the full explanation on how Android manages memory.
Please feel free to read the post I originally read that inspired me to start looking at this stuff - How to configure Android's *internal* taskkiller. It was very helpful for me to grasp how Android manages applications. This is the reason why application killers are not a good thing...
If you want to do it manually, Starfox suggests:
Code:
echo "1536,3072,8192,10240,12288,20480" > /sys/module/lowmemorykiller/parameters/minfree
To try to do these commands, adb is very useful. Once you get adb shell working, then you just need to "su" (provides 'super user' privileges (root)) and put in the echo command above ^^.
I had another user (thanks icevapor) suggest this script -
[Script] V6 SuperCharger! HTK & BulletProof Launchers! The ONLY Android MEMORY FIXER!
I tried it myself, and it works very well. This thread is a little overwhelming, but the jist of it is this:
Install Script Manager (on the Market)
Run the V6 SuperCharger script. I use "Aggressive 1 Settings" (#2) and then I use the OOM Grouping Fixes & "Hard to Kill" launcher (#17)
Point Script Manager to run /data/99SuperCharger.sh to run as root & on boot. This will ensure the tweaks are reapplied after a reboot.
Topic 6
Difficulty Advanced - Managing Apps that auto-start on boot
This is one of the most annoying things in Android. When you have no apps installed, it seems very fast. Then you install apps, and you never seem to get that original speed back... Now you can!
This is kind of difficult to do, I am still getting the hang of it... but here goes. All credit goes to hyc, his original post.
The basic idea here is you run a logcat (adb logcat is easiest here, or you can use GetLogs to pull logcat...) Look in this log for "for broadcast" and find apps that start on boot. For example,
Code:
Line 41: I/ActivityManager( 1394): Start proc nextapp.systempanel for broadcast nextapp.systempanel/.monitorservice.BootReceiver: pid=1752 uid=10060 gids={3003, 1015}
Notice there are two sides of the "for broadcast". The name of the package (nextapp.systempanel) and the name of the service, "nextapp.systempanel/.monitorservice.BootReceive". I made the mistake of disabling the app (the left side). Do not do this, you want to disable the right side!
So in the shell,
Code:
pm disable nextapp.systempanel/.monitorservice.BootReceive
This will be persistent across boots, it will go with your data.img.
Obviously this was just one example of an app to disable. So long as you disable the right side (after the 'for broadcast') you shouldn't disable anything that will cause a serious problem. The apps should still work, but for example if you disable Google Voice you won't get messages until you open the app. So think about that... You disable Titanium Backup schedules.BootReceiver, the schedules for Titanium Backup (if you have any) won't run. Stuff like that. Disable calendar, you won't get calendar events... Disable clock no alarms. Get it? Good. I have been rebooting several times, and I keep checking what is set to start on boot. I'm not quite happy with it yet, but there's some things I'm leery of disabling. Just be wary, if you do disable something and don't like it - just pm enable <whatever you disabled>.
Now experiment away! The one caveat is if you do break something with pm disable (and it's serious) you might get a failure to boot. It really depends on how bad you mess up. If you make a copy of your data.img before you start making these changes, you can revert to that data.img and start back there.
Alright guys. Going to use this thread as a way to brainstorm about ways to improve the speed. Read up what I've posted, let me know if I did anything wrong... Also let me know what you guys do to improve speed!
Don't care about what build you're running, this thread isn't about what build is fastest - this is a how do I make every build faster thread.
I also realize I posted this in the Rhodium section - I want to see if there's any TOPAa-specific tweaks that others should be made aware of!
Update to this - I changed around how topic 4 is done. Feel free to re-read that section.
Thanks arrrghhh, but for startup stuff, there are some apps doing the job, like Startup Manager or Startup Cleaner pro (found in Market), honestly haven't tried them yet but from rating, some of them has got 4.1/5.. What do you think mate?
metho88 said:
Thanks arrrghhh, but for startup stuff, there are some apps doing the job, like Startup Manager or Startup Cleaner pro (found in Market), honestly haven't tried them yet but from rating, some of them has got 4.1/5.. What do you think mate?
Click to expand...
Click to collapse
For the pm disable stuff? If you find an app that does it, more power to you. I want to control Android directly, hence the reason I went with a script that utilizes that concept. The pm disable stuff is obnoxious I know - so if you do find an app that'll do it for you, have at it. I didn't want to add any more apps into the mix if it wasn't necessary .
Rhod400 in startup.txt
Does physkeyboard=rhod400 cahnge the keyboard layout when texting?Does it make it bigger or what is that cmdline for?
1edge1 said:
Does physkeyboard=rhod400 cahnge the keyboard layout when texting?Does it make it bigger or what is that cmdline for?
Click to expand...
Click to collapse
Sorry, that part is completely irrelevant to TOPA. It is for a RHOD400, sets up the physical keyboard. You were only supposed to look at the acpu clock command, as it fits in the startup.txt... lol.
Use the startup for your device, I'm just showing you how the line should appear in the startup.txt...
arrrghhh said:
Sorry, that part is completely irrelevant to TOPA. It is for a RHOD400, sets up the physical keyboard. You were only supposed to look at the acpu clock command, as it fits in the startup.txt... lol.
Use the startup for your device, I'm just showing you how the line should appear in the startup.txt...
Click to expand...
Click to collapse
yeah i do use the startup for topaz. Was just wondering. haha. thanx for clearing it up
Hello,
I have with me an app I would like to share with the HD2, and XDA community which I previously found on the Google Market which now doesnt exist anymore.
I managed to copy out the APK and I will attach below.
The app is good for
Listing all your installed apps quickly so you can remove them
Smooth scrolling
Sort by Name/Size/Last Installed/Install Location
Search
Just needs to build cache during first launch, and doesnt work on LANDSCAPE, which are the only disadvantages of it.
I personally use the Last Installed sorting mechanism, to view all the last installed and remove. I install quite a number of apps and usually when I found that it sucked, I enter this app quickly and remove them (latest apps appear on top of the list)
I have been using this since 2.2 FROYO and it doesnt seem to give errors back then. On GB 2.3, I noticed an occasional error message :
[Opps Sorry I got error ] but this doesnt stop it from uninstalling the application.
I have given this app rigorous testing and it has survived 2.2+ and 2.3+ Androids application removal, whether it produces errors or not.
I also noticed that this app has been removed from the Google Market, without reason from the developer / Google. Hence I would not mention anything about future release or support, neither do I know whether it would damage your device/ operating system but I certainly ONLY been using this app to remove applications and it has been TREMENDOUSLY awesome. Give it a try, and let me know whether you found similiar apps in terms of speed, features and outlook.
Credits to its developer, which I remember to be known as MINIGUY after a few Googles. I also couldnt find this application anymore hence I am posting it here
If this has been posted before I apologize.
Dont forget to click the THANKS button if you found this app useful
On another note, this applications is FREE and is not WAREZ
It sounds like appsaver.. is it better?
Hnktc said:
It sounds like appsaver.. is it better?
Click to expand...
Click to collapse
i think ive tried appsaver but this is an app that lists out all your apps pretty quickly and lets u just choose to uninstall them
its like add/remove programs, but way way faster than anything ive tried especially 200 apps
default manage applications takes nearly 15 seconds to load, while this takes 1-2 seconds, tops
Thanks for the app. I will give it a try! :0)
I realized that this application was ripped and published as someone else's work as follow up
its called "Uninstaller" in market , which uses the same error message, logo, text, font, settings, buttons, icons
you are free to use both as they produce the same results and same settings
Hi everyone one... I am looking forward to making my SM-T280 have a wee better features.
Have modded it with some extra features, but find peeps here are lazy, sor I will be accessing Russian help with a real firmware upgrade for such a great tablet. Will post more info soon.
Major change up
Seems that while waiting, I came up with a simple system file updates from three devices. Sinice the J1 is more compatible to the Table A 7.0 I spoofed the J1 build.prop settings to make Chrome layout look better, whIle system is forced in landscape mode. I also transfered over some system files, which were univereal that were not included in the basic 7.0 tablet.
So far, I have updated my bluetooth profiles and additional automobile connectivity presets, while updating wifi firmware from latest J3 phone firmware running LP. I also included a few J5 additions as well.
Now my tablet is being long term always on tested for stability.
Here is a list of added or enabled features that is on my Tab A 7.0.
FM Radio with recording
Full featured All share services
Samsung Video player with DNLA and pop out play functions
Screen Cast
Car mode with link functionality
Updated bluetooth profiles
Updated settings and system options... which I now forget what was missing, as I am now use to them.
Added missing frameworks and lib files.
Now working on a few lib files for virtual display and quick connect functionality.
An added note... wifi speeds and connectivity are much better now. Before updates I got 33mbps and delayed connections to my home network, now I get 38mbps and a fast connection when turned on.
keep it up !!!!!
dcap0187 said:
keep it up !!!!!
Click to expand...
Click to collapse
Will do... though it's been a wild ride with roller coaster events leaving me just about to kick the efforts all out the door.
Excuse the bad typing... explained at the bottom of this reply.
First of... 5.1.1 is an odd animal to get use to from 4.4 and 7.1 variants of android.
I did not realize that 5.1.1 was an abortion in the community efforts to mod and support. Most of the info I grabbed as I started was too outdated and hard to find good stuff was lost over time, server cleanup and lack of dev file space for continuing on for future builds.
So, after dumping xposed for 5.1.1 and going odex based stock, I am satisfied with hown far I have gotten.
Example... with xposed I was able to get private mode to function but... had not much reserved memory available in root storage. Even though the specs given on theach T280 state 1.5MB, which is wrong... it has plenty of room to hold more apk and .so files.
To keep speed and allow for optimum system storage use, I gave up xposed and dived into mixing 10 different stock firmwares from Samsung.
Here is a small list of known working stock firmwares, that allow transplanting apks and mostly library files over to our devices. J1, J2, J3, A3, A5, Note4, Tab S, Tab A series... both 2015 and 2016 models.
I found some custom ROMs that were odex and deodex factory firmwares, that had no disclaimer on useage.
To get missing quick settings features, I had kept an old SQL editor to patch the system db with all the useful toggles and removal of unnecessary ones.
Mirror link 100% functional, and 98% of all Accessibility features are available and operational. Finger Spen in all apps that support spen. Yes, that means the internal photo studio editor that plugs into gallery will fully function. Though I miss the 4.4 version on kitkat, as the later versions are simplified in options, like adding notes behind photos and quick file management features. WFD, Nearby, Ultra Power Saving, Side Key Panel, Full featured multi windows. Backdrop, Smart Face and Signature lock, Smart Cover, and Universal Switch are unlocked and functional.
Care Mode is 50% functional, as the tablet is not a phone, so Maps and Music are fully functional only. Bonus! Voice link via S6 S Voice. It's fully functional with out any issues that I can tell. The only issue is screen DPI to launch S Voice directly from the launcher. Found that the drawing function dumps when hour glass is extracted for screen write. I guess a simple resizing of the images within the apk will correct the FC. I am not a developer and do not mod apk files, even though from what I gather, is one of the simplist mods one can in customizations.
Since Drive Link is a UI to S Voice internals, just use Drive link to do most all of your S Voice needs. No modifications nended to S Voice apk.
Also Voice Wake is part of the package... which allows interaction between Drive Link on voice commands. Without it, you need to touch the mic to wake up S Voice when using Drive Link.
At this time... I need to find a proper WithTV package (note 4 has issues), a proper display.so lib, a way to enable gestures... I had it going in xposed with a few unknown files lost when over written while testing. Don't recall what rom I extracted from, so some day I may stumble upon it once again. I vaguely recall, the ROM was based from India, or TW. May have to look into touchwiz framework patch to get Smart Stay, Smart Pause and Smart Scroll functioning. It's not a priority as I never used them, and don't use S Browser.
SNote should work, since finger input for spen functions. Only if a developer would make an app to enable finger input as air touch enable. Example... double tap spen detatch/attach toggle. Then I can add Spen SDK and permissions to use my finger for Spen features. I had tested with stock settings menu, and it does have over 50% of the features hidden and S Pen is one of them, just no switch to detect input.
As for private mode... from what I gather, it may be that I need to flash my tablet with a clean fresh factory build and patch to enable private mode firstly. In my mad attempts to keep storage space from being consumed by uneccessary files, I recall deleting an odd file that happened to be a database file created by Private Mode. Once deleted private mode will no longer function. A factory wipe may recover, but in my case there is something changed that needed a full wipe and clean install.
I was not so keen with the Tab A setup UI, so I tested with various Phone models, the A5 and A3 setup UI is like stock but has a slightly better layout and added features that stock does not have.
I did not bother to try enabling Internet Calling and Messaging. Mostly because the last time a developer tried to do something like that, they ended up not being able to compile a working mod. So its all beyond me on diving into such a thing. There is more than just adding a dialer interface.
Well that's pretty much all I can recall in a nutshell. I am going to mess with correcting the Samsung keyboard issues from one of the framework files I am using. Its locked my popup symbols for multiple entry, which would be nice if I had a use for that feature. I have to tap away from the symold list to close the list and then type. Also even more annoying is the spelling and auto correct has greatly became touchy. It seems it wants to correct incorrectly on even the simplest words. Thus my writing looks bad, especially on long paragraphs like on this reply.
Quick update.... disabled chrome spell check and found Samsung keyboard easier to manage on spellchecking... though there is some issues still, so I will dive further.
Removed gesture service, since it requires light sensor, and included spen SDK for SNote to load, and talkback to allow voice interaction in accessibility features. Will try and fit in SNote and Voice Note, as the stock firmware is missing key lib files.
Sticking with A3 / A5 Settings2.apk as it is best all around.
Working on Qconnect, S6 Toolbar, and Personal mode.
Will not fix S6_SVoice.zip for direct useage, as it is only for drive link voice operation only. You can use a S4 SVoice as an option for direct useage. But not installed together. Both SVoice and TTS are huge installs, but a lot less than using all Google. Apps. In fact maps and Google play storeally and services are the only Google Apps I have outside of Chrome.
Ok, I got some of the keyboard spellchecking issues sorted out. Installed the latest open gapps, just to remove most of the Google updates stored on data/apps. Doing so cleans up space and removes some issues with conflicting .so files and apks. Found Chrome was in need of removal on its updates, and I manually copied it into system app folder for the system to make it into a system load when rebooted. Then Uninstalled the update that was chrome left in data/app folder.
Nown for the additional additions...
NOTE4
SVoice Note with voice to text and 3 recording types.
Face Lock functionality
Talkback
No go apps that will not be added... QuickConnect, S6 Toolbox, Smart Stay, Smart Pause, Smart Scroll, Private Mode, and Air Gesture. I gather framework will need adjusted, and systemui may have QuickConnect and Toolbox presets with disabled pointers to launch them.
I may try a few systemui for other devices, like I have with settings2.
Considering how much of the Samsung features I unlocked and added, the only feature I will miss and is worth the effort to attempt further, is QuickConnect. It is a pretty snazzy tool with some interesting features that make it a go to for sharing and connectivity.
When I create a twrp backup of my competed system, it can be restored over existing installation. A dirty flash if you so call it. Just wipe cache before rebooting. It will take about 10 minutea or more, depending on what has been installed.
You can remove some none stock apps as you see fit, as they are for ease of maintenance when flashing clean.
I added a few things to make the tablet more useful for my own use. One is S5 video player. Mainly because it is full featured, allowing pop out video, and built in DLNA to stream from my router media storage and TV box.
If some videos are not compatible, I use aDLNA to launch MX Player for decode that is not compatible to my hardware.
I kept the stock video player, so the additional S5 video player may be removed if one chooses.
One issue is the buttons in S5 Video are not dpi proper on the layout. So black boxes are shown without any context. You can play around to memorize what black box does what, or I'd you are familiar enough with phone style video player pretty 2016, it should not be so difficult.
I debloated the system as much as I could, though many call removing system files that are not required for operation as debloating. Debloating is removing memory consuming apps, not system needed apps. Most all Google Apps are heavy bloaters, in generating cache and data, let alone are bloated within themselves. I tend to stay away from multi platform apks. Especially when there is no need to have ARM8a compatibility in a ARM7 environment. Either figurethane out that Google or stop with your fake and loosely based facts on your betterment of newer platforms. Geezo, my 4.4.2 tablet uses less storage than 5.1.1. And yet it was stated that newer Android is smaller and more efficient. Right? BS... the true facts are right here in my hands
Enough rants... here are the facts. System partition has about 60MB free. Why leave over 500MB free and unused as empty storage? So now you have a maximized system storage for system apps that normally don't get updated. Leaving the updated or user installed apps to use internal or external storage.
Proof it will not cause issues, some custom ROMs will down size system partitions from 3GB to 1GB depending on how minimal the firmware foot print is. So instead of remapping the system partition, I just moved apps into the system.
I have about 900MB free on internal storage running a bunch of streaming apps and CoPilot. The biggest resource hogsite are Google play services, play store, and Samsung TTS with SVoice. Using Google TTS and Voice would greatly consume more valueable storage space.
The 16GB card is my backups and work space for rom stripping. I use a 64GB card for media and apps. There is a script to make External SD into Internal sdcard, so the storage is like what you would have with newer firmwares. Though it is not encrypted, but can be shared between other devices.
So I placed all the installed apps that are not or will never be updated in the system/app folder. Thus increasing my internal storage space by 60MB and more.
After a bit of testing, I found that Knox will keep private mode from functioning. So, some how during my tests, I must have finished my transfering system files after a fresh restore of stock firmware recovery. Thus a partially functioning personal mode. To me kids mode works fine, so if i shoud need to share, to someone who i dont trust with private data, i can give them kids mode all setup for them to never ask again. mwhahahaha! On the lighter side, you can just setup the guest profile and lockout photo apps and such.
tested my apps to sd script. all apps now allow moving to sd, as expected. YAY!
I released enough internal (sdcard) for 1.2gb free with curent unmoved apps installed. May balance it out further, if needed. Dont have much room to test with as my 64GB sd card has 54GB of music and another 8GB in other files. Will need to invest in a 128GB sd card for that.
Tweaked the build prop for faster responce... just a few wee edits actually. One is stupid simple, yet never seen anyone do it on small ram devices. will add a final additional set of tweaks for small enahancements.
This tablet is actually faster than the Note 8.0 it is replacing, though it is slower on cpu speed, and is not overclocked with a custom Boefla kernel.
still working on a small set of bugs... probably from my data from installs and configurations. Once I clear the internal data, it may recover properly, but i rather identify the issue, as I expect the restore file to be flashed dirty.
Gave up on testing systemUI swaps. Seems like samsung has made non adjustable ui schema on their platforms. I cant even drop or increase dpi on this tablet without breaking ui.
One thing i did like about A3 ui was its noticable zoom out feature with the lock screen image, and has different background, like the S5 phone.
Outside of that, once unlocked boom! Back to lockscreen with a ui crash.
Found one issue with A3/A5 settings... it has a different mapping for a sub menu item. Closes out, without allowing a setting. Seems like phone and tablets are perposely done so component features cannot be shared beteen them. Signature lock will show as an option but impossible to enable. To use face lock i must use a tab4 settings. It would be nice to combine all the features on the A3 settings ui to the tab4 setting ui, as it would alow so much more versatility. The tab 4 settings has audio pointing to a different audio schema which fc the setting ui once selected, since the devices do not share the same hardware. Also the motion section does it as well.
Most all the features are good between the two on our tablet. Not going back to original settings as it seems so limited.
Slowly making headway...
Found some nice mic and audio drivers... for the life of me, i thought it was cheap hardware making a bit of digital noise with stock system files and any oem or downloadable audio recorder. I went a head and scoured through build dates on stock driver files to find similarities with tab a stock, and any differences.
Because I only use the tab a to do file and os tests, as its the only thing i have, i cant keep backups or libraries of firmwares to gather what i need. Its mostly download search sort and copy what i need. Then delete and download another rom.
Out side of mystery system files, to patch the latest release for the 7.0 tab a6, i am pain stakingly playing with floating logcat, while launching and running apps.
Decided to remove some apks that i use for tools, and do some cleanup for a clean system build backup. It leaves around 400MB free for what ever you want to add to the system.
Found a nice option to try... once i do a backup, is to run virtual exposed. I dont like the modded xposed for samsung odex. It seems slow and a wee buggy.
I rooted this build with a passive kernel and the latest magisk.
I hope to have virtual xposed operational on this build as there are so many xposed modules available.
I did include the tools i use.. fake gps, os monitor, logcat extreme, termux, and csc features for samsung.
Still trying to sort out sip symbols staying active when more than one is listed, after initial touch on the symbol.
Voice note is also having one issue... will not type out words spoken when doing voice note dictation. I assume i am missing some system files outside of the lib folder location.
Will have to search for the proper firmware and find what differences are in the file structure and in vendor.
Have added smart selfie alarm for camera, and additional stylized images for bonus material.
As another bonus i included control screen, to keep the screen orientation proper on difficult apps. It has an option to stay in the notification pull down panel, and fits nicely. Just turn off samsung auto screen rotation before enabling the app.
One down two to go!
I found an Svoice that is fully functional on our tab a6 models. So, consider another bonus in the round of fixing wee issues.
This one allows the change of the wakeup command. It seems to work with any command you want to make it. Problem is if you bypass the initial setup, it defaults to Hi Galaxy. I think clearing out all the Svoice apks data and cache will allow changing the command, if you need to.
Still working on Voice Note not typing out text from voice input, and sip symbol key list staying on after initial touch.
It may be from a hidden accesibility function that is available with various setup ui apks.
Like there is another type of unlock scheme on some phones and th J3 version i am using. It very much like pattern unlock but more simpler. Also it can be setup to show direction, or not to show direction, to keep the lock screen blank. Also read out loud to where your direction has been entered.
Down to one last issue to correct
I figured out the main reason why voice note in the voice recorder fails to type out text during voice recording. The tab a6 does not have a proper audio mux and lpcm setup. I tried to configure media by seeing what can be done to add paths. I am not familiar with paths enough to compare and cross reference unknown values to replace from a different schema.
So, until someone who is following can do a proper patch to the media xml files in exec folder, the function will never happen.
I checked with SNote and it does allow all the importing functions, including video from rear camera.
While trying out the patch on my own, I did bump up the recording quality on the video encoding. At least i got something done out of the deal.
I also gave up on virtualxposed. I dont care to run a shell based setup, and most of the xposed modules i use do not play well with the shell.
So, it looks like i will devote my time into isolating the troubles with sip symbol shortcut overlay not clearing from the keyboard after initial symbol touch. It will clear on just a single symbol being shown, or if you touch away from the pop up symbol set.
One thing i did do is clear keyboard data and cache. I may have to reset the csc features xml additions i had set. I have other ideas, but i will tackle the simplest first.
I hope to post my dirty flash mod for peeps with the latest firmware to use on their Tab A6 7.0 tablets.
Since i had very little input on what most want or expect on a modded firmware, i made it for my needs, based on a full Samsung Experience, with minimal google bloat.
I will make a couple of scripts for peeps to run via terminal command or launch from smanager. Since my force installs to external sd card may get in the way of a clean flash with pushing restoration installations.
The scripts will enable or disable force to external sd, and toggle performance mode, and interactive mode (stock default).
All fixed!
Found my symbol key issue was with magnification gestures enabled.
Now that all correctable issues are resolved, I will finalize my small tweak options for user enabled optioms
All fixed!
Found my symbol key issue was with magnification gestures enabled.
Now that all correctable issues are resolved, I will finalize my small tweak options for user enabled options.
I will not have busybox installed, just Magisk rooted with passive kernel.
So, speed tweaks are user enabled after boot. Network tweaks are enabled via sysctl.conf within etc folier
All fixed!
Found my symbol key issue was with magnification gestures enabled.
Now that all correctable issues are resolved, I will finalize my small tweak options for user enabled options.
I will not have busybox installed, just Magisk rooted with passive kernel.
So, speed tweaks are user enabled after boot. Network tweaks are enabled via sysctl.conf within the system/etc folder.
Right now I am happy with over-riding system governor to Perfromance and WiFi congestion control to Reno. Both are the only options avaliable from what the kernel was built with.
There is a small battery increase, but mostly noticeable when comparing to low tasks and multi-tasking. Heavy usage and average use, will not show much difference. I have yet to see a reason to revert back.
This is a stock rom with as many features one can have for the hardware and what Samsung made available for cross compatibility. I have included a full featured accessibility package, along with voice and finger generated spen controls. Plus enabled internal editing of videos and photos. Plus I blocked media from scanning system media for images and songs.
There is too much to explain here, but I will try to compile a full list of features that are installed for a Samsung Experience.
Test image
Here is a TWRP backup of my system. It can be flashed dirty, though i recomend doing a backup of your system before flashing to revert back if needed.
Unzip the contents into your existing twrp backup folder. Run twrp to restore the image. Be sure to enable checking to gaurantee proper restore.
This has install to external set, and magisk root with permissive kernel (you may need to enable it with a utility or shell command). Minor tweaks are in build.prop, you can revert to original build.prop by renaming the backup by removal of the bk extension.
This is 98% completed... i have to update a few files and an app, as they were written over, by mistake.
You should have 200mb free in the system partition. Also a small handful of utiltiies that are no more than 25mb total. I removed google bloatware, and a few Samsung apps that are not required, or can be downloaded from Galaxy Apps or Google play.
Many will just say no need to change a thing... but before i post the final image, i will not bother with future maintanence. So, if any one finds something out side of known issues, given in my update history... (please read through carefully) i can attempt to make some additional changes before i finalize. Thank you.
https://mega.nz/#F!AzZB3SDT!HEtXvvWsk8F_SbgYz9BGzw
TWRP
I'm trying to flash a TWRP recovery image on my T280 using Odin 3.13 and twrp-3.2.3-0-_mone-gtexswifi.tar....but I keep getting a secure boot fail. What did you do to flash TWRP?
good morning
could you explain in detail how to install your rom?
the twrp backup folder where I find it? do i have to create it?
explain this passage to me please
gooberdude said:
Here is a TWRP backup of my system. It can be flashed dirty, though i recomend doing a backup of your system before flashing to revert back if needed.
Unzip the contents into your existing twrp backup folder. Run twrp to restore the image. Be sure to enable checking to gaurantee proper restore.
This has install to external set, and magisk root with permissive kernel (you may need to enable it with a utility or shell command). Minor tweaks are in build.prop, you can revert to original build.prop by renaming the backup by removal of the bk extension.
This is 98% completed... i have to update a few files and an app, as they were written over, by mistake.
You should have 200mb free in the system partition. Also a small handful of utiltiies that are no more than 25mb total. I removed google bloatware, and a few Samsung apps that are not required, or can be downloaded from Galaxy Apps or Google play.
Many will just say no need to change a thing... but before i post the final image, i will not bother with future maintanence. So, if any one finds something out side of known issues, given in my update history... (please read through carefully) i can attempt to make some additional changes before i finalize. Thank you.
https://mega.nz/#F!AzZB3SDT!HEtXvvWsk8F_SbgYz9BGzw
Click to expand...
Click to collapse
there are few stuff on your mega, including 2 finals , mod, and christmass rom. Which one to use?
it's people like you that make me love XDA
gooberdude said:
Here is a TWRP backup of my system. It can be flashed dirty, though i recomend doing a backup of your system before flashing to revert back if needed.
Unzip the contents into your existing twrp backup folder. Run twrp to restore the image. Be sure to enable checking to gaurantee proper restore.
This has install to external set, and magisk root with permissive kernel (you may need to enable it with a utility or shell command). Minor tweaks are in build.prop, you can revert to original build.prop by renaming the backup by removal of the bk extension.
This is 98% completed... i have to update a few files and an app, as they were written over, by mistake.
You should have 200mb free in the system partition. Also a small handful of utiltiies that are no more than 25mb total. I removed google bloatware, and a few Samsung apps that are not required, or can be downloaded from Galaxy Apps or Google play.
Many will just say no need to change a thing... but before i post the final image, i will not bother with future maintanence. So, if any one finds something out side of known issues, given in my update history... (please read through carefully) i can attempt to make some additional changes before i finalize. Thank you.
https://mega.nz/#F!AzZB3SDT!HEtXvvWsk8F_SbgYz9BGzw
Click to expand...
Click to collapse
Thank You!
Help to update - Some procedure to follow
EliteeSword said:
Thank You!
Click to expand...
Click to collapse
Hi! id like so much to update my Samsung A6 SM-T280 - 7 inches. I downloaded the files from Mega but i really dont know how to update Does anyone can help me with some procedure ?
I really appreciate the help!
Regards,
Daniel .
---------- Post added at 04:53 PM ---------- Previous post was at 04:49 PM ----------
Hi Gooberdude!
Id like so much to update my Samsung A6 SM-T280 - 7 inches. I downloaded the files from Mega but i really dont know how to update .Does anyone can help me with some procedure ?
I really appreciate the help!
Regards,
Daniel .