[Developers] AdMob SDK 4.10 Released - memory leak fixed hopefully - Xoom Themes and Apps

For those of you developers who are using Admob, they just released a new sdk 4.10, which has some stability improvements. The previous version used to be improperly holding long lived references (the webview is the culprit) to the activity after they were closed. This would easily cause out of memory exceptions to surface (remember that rotating the screen calls onDestroy on the currently run activity and then reruns it - in this scenario every screen rotation would cause the activity to get leaked - baaaaad). The new sdk includes a method in the AdView class called destroy(). You should be calling this in your activity's onDestroy() method to prevent memory leaks.
EDIT: You will have to change the namespace to /lib/res/com.google.ads if you are declaring it in XML as well.

Still leaks...
Hi,
I've tried to incorporate the new SDK and there is still an obvious leak.
I posted a question on stackoverflow.com with all the details and sample code, including a screenshot from HPROF that shows where the leak is (just look for "Android AdMob causes memory leak ?" on stackoverflow.com)
Am I missing something ?

I can now paste links to all the relevant data. Any help will be appreciated
http://stackoverflow.com/questions/6148812/android-admob-causes-memory-leak
https://groups.google.com/group/google-admob-ads-sdk/browse_thread/thread/f48ca3a9d99eba63
https://groups.google.com/forum/#!topic/google-admob-ads-sdk/XnU2K2Q18aA/discussion

Seems that they get rid of AsyncTask (http://code.google.com/mobile/ads/docs/rel-notes.html).
In my app new version of AdMob (4.1.1) doesn't leak memory anymore.

Mine still leaks (detected by leakcanary)
implementation 'com.google.android.gmslay-services-ads:12.0.0'

Related

[DEV][CM7] Compositor Bypass

Hi, I haven't posted 10 times yet, so hopefully somebody can move this to the Android Development section for me...
SurfaceFlinger has a mode called "COMPOSITION_BYPASS". This lets a fullscreen OpenGL window draw directly to the framebuffer, instead of SurfaceFlinger copying each frame to the framebuffer itself. It avoids a fullscreen copy and avoids a GPU context switch. It should be a major performance enhancement.
I haven't got it to work yet, but I've made some progress. Posting in case anybody has any good ideas to try...
The COMPOSITION_BYPASS mode is enabled in SF's Android.mk and the part that allocates the buffer for the client app is in Layer.cpp:387. I tried previously to enable COMPOSITION_BYPASS mode but got stuck because gralloc would not return a valid FD for any buffer allocated with GRALLOC_USAGE_HW_FB (i.e.: a framebuffer backbuffer).
I noticed in the new SGX drivers that gralloc.omap3.so has a constant string HALCompositionBypass. I *think* that adding a line like HALCompositionBypass=1 to /system/etc/powervr.ini might change the behavior of gralloc and give valid FDs out -- however, when I set it gralloc_open in FramebufferNativeWindow.cpp returns EFAULT!
Maybe some kernel poking is required...
Randall

[Q] Compilation in the cloud (really?)

Hello,
I have a simple question about the compilation in the cloud for wp8 apps. As detailed on the MS Blog post titled Compile in the Cloud with WP8, when a developer submits an WP8 (only) app to the store, the app is compiled in MDIL in order to optimize the subsequent execution.
Despite this, on my unlocked Samsung Ativ S I experienced that even in the case of wp8 app - and I mean, apps that target ONLY the WP8 platform - the DLLs are still in CIL and not MDIL, and so they can be easily decompiled with tool such as dotPeak.
My question is: where am I wrong?
Thanks,
Sandro.
.NET binaries have multiple pieces. One of them is the CIL, which is what something like dotPeek decompiles. There's also an area where JIT output can be stored, to speed up future execution. It sounds like what the Store is doing is JITing the apps for ARM processors, to reduce load time after installing (otherwise, JITing a large app on the phone can take a while; you can see this yourself if you ever sideload a large app). This slightly increases the size of the binaries, but improves performance. The CIL isn't removed though, either because they want to allow the phone to make different optimizations (for example, different amounts of CPU cache can effect when you would want to unroll loops or inline function calls vs. when you wouldn't) or just because the format of a .NET binary *expects* there to be CIL there.
GoodDayToDie said:
.NET binaries have multiple pieces. One of them is the CIL, which is what something like dotPeek decompiles. There's also an area where JIT output can be stored, to speed up future execution. It sounds like what the Store is doing is JITing the apps for ARM processors, to reduce load time after installing (otherwise, JITing a large app on the phone can take a while; you can see this yourself if you ever sideload a large app). This slightly increases the size of the binaries, but improves performance. The CIL isn't removed though, either because they want to allow the phone to make different optimizations (for example, different amounts of CPU cache can effect when you would want to unroll loops or inline function calls vs. when you wouldn't) or just because the format of a .NET binary *expects* there to be CIL there.
Click to expand...
Click to collapse
Can you please point me to any documentation that describes the .NET binaries format, in order to better understand the CIL and MDIL section and .NET binary structure in general ?
Thanks, Sandro
The ones I found were all pre-MDIL, I'm afraid. There's plenty of documentation of the general format of a PE binary - it's a public standard - but I'm not sure where the MDIL is stored, actually. I was mistaken about the normal JIT output; it's either stored in memory only for that process execution, or in an assembly cache (as when you run ngen.exe on a managed assembly).

[Q] Building CM11 from source / Running into error

I'm trying to learn a bit about android and ROMs and programming in general. I have limited experience but not a whole lot. I have my environment set up, CM11 source downloaded and my tf701t tree downloaded.
When I go to run 'brunch tf701t' I get a couple of minutes into the build and I run into the following error:
warning: [options] source value 1.5 is obsolete and will be removed in a future release
warning: [options] target value 1.5 is obsolete and will be removed in a future release
warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
libcore/luni/src/main/java/java/util/EnumMap.java:162: error: incompatible types: Object cannot be converted to E
return type.get(new MapEntry(enumMap.keys[prePosition],
^
where E is a type-variable:
E extends Object declared in class EnumMapIterator
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
3 warnings​
I'm using the Sun Java JDK jdk1.7.0_67. I fixed an earlier issue where I it was referencing the OpenJDK and killing the build almost right away. It COULD still be the JDK, there are so many damn versions out there.
I'm at a stopping point, not sure where to go on from here. Any help and suggestions are appreciated.
OK, I solved that error by uninstalling all JDKs, rebooting then installing Sun JDK 6.
Now it's on to the next problem.
Yes I was going to say I always drop to version 6 rather than 7 first if I get any java errors.
What is your next issue?
My next issue was missing proprietary files, specifically the icera ones. I'm also missing keystore.tegra.so.
I'm building on a VMWare 10 Ubuntu 14 virtual machine with 4GB alloted of ram and 75GB of cache on an aging HP QuadCore. Not even an i series, so it is slow going.
Sent from my K00C using XDA Premium HD app
I got past those errors by locating them and putting them in their proper locations.
The build process took about 8 hours. Zero hour arrived, I backed up my CROMBi-kk installation, loaded up my home cooked cm11 ROM, crossed my fingers and pressed the power button.
Success! Yay me! :laugh:
Everything booted up, wifi located and connected, signed into Google, CyangenMod and proceeded to restore my account.
It was pretty neat to see my name in the about section. :silly:
What I gained from this.
I need a new PC or at least I need to beef this one up a bit.. I bought the old girl in 2009.
I don't really like Ubuntu as a development environment. I don't like Unity, never have. I did install gnome-fallback, but I had issues with the minimal desktop, the dreadful screen blanking that I could just not turn off no matter how many settings and CLI tricks I used. I think I'm going to try Linux Mint next. IMHO it has lower overhead than Ubuntu and should, at least as a VM, give me some better performance.
My problem solving skills have not completely left me in my older years. I left IT some 15+ years to pursue a career in EMS and Firefighting, so my skills have been mostly backseat and hobby like. Being retired I've got the time to putz around and see what I can do. I was glued to Google remembering and dusting off my shell and CLI basics.
Now it is on to learning how to customize and tweak the ROM.

Any chance to gain root with Quadrooter?

I don't know anything about rooting phones was just curious if maybe someone could take this exploit and use it for good use and we would be able to root our phones. I used a program called Quadrooter By Checkpoint and we are vulnerable to CVE-2016-2059 (Elevation of privilege vulnerability in Qualcomm networking component) and CVE-2016-2504 (The Qualcomm GPU driver devices allows attackers to gain privileges via a crafted application, aka Android internal bug 28026365 and Qualcomm internal bug CR1002974.). I'm on Marshmallow with the latest updates.
The article is here
http://thehackernews.com/2016/08/hack-android-phone.html
That is interesting, im not a developer, so im no help, only to test if someone comes up with something. 5.0 OF3.
Quadrooter is a menace, yes, in short time, around 2 months, the gpu may be destroyed only installing unchevked apks.
They are doing a new kind of apk, that i am searching how to forbid these "new" apk model, named as multi dex system.
This is running binary codes inside the cache of the app.
For example:
The telegram.apk is all disabled, the system is capting that all relative to trlegram.apk, is not running.
When you never imagine, a notification, appears on the bar, showinh a new message, but, why?
The app is disabled, but the cached-dex no.
This is a serious menace, because these cached codes are "temporary".
If some "cached dex" is executing, the ram memory goes down, and the system, does not captures this dex running.
Imagine another worst thing:
Any cached dex is programmed to copy and send some victim's bank password for determinated site, in background, on where the system will never shows the relathive dex process at least the relative apk that created this dex.
Be carefull only with the apks thst you install, and never use if is multidex .
You can check if is multidex or not before installing, if haves zipped or jar classes , don't install.
Or the device may be burned.
That is all
Sent fro SomeFon

Converting TAB A SM-T280 to a SAMSUNG J500f

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 .

Categories

Resources