Related
Hi folks, I spent a good part of my sunday (and friday night, let's be honest) to port UAE4All for Android. So here's UAE4Droid. Most games are working fine, don't expect killer framerates though (it should be faster on a Droid). I don't plan to actively support this app, so here's the catch:
-no sound
-physical controls only (that's why I post here, you can configure them btw)
-no save states (the original project does not implement them, and I'm no good at understand basics of the 68000 emulation)
-should be ok starting from Android 1.5 but I didn't test it (Dream on Cyanogen here).
You need to own a rom copy and some disks to use this legally, of course. If there's some good feedbacks, maybe I'll put it in the market (already done a couple of emulators there). Enjoy !
Edit 12/27 : Now with sound and touch controls on the Android Market
damn you did this in one day?
make it one and a half
It's a port, not that hard, once you got some Android knowledge, the basics of the SDK-NDK interaction, and the open source works from several people. And I left some parts (sound and touch controls), quite buggy/boring to code
Did you ever know that you were my hero? Seriously, great stuff! If you could add sound this would be the best thing I have on my phone!
Amazing. Superfrog works pretty well. If I could just insert all floppies at once it would be completely awesome.
If you're not planning on supporting this too much in the future would you consider making it open source?
It's completely fun to put android next to my old ami500, old 1200 and turn on superfrog on each
Oh wow...that's pretty impressive. Superfrog on my phone would be awesome! I'll have to try it.
Ok, hate to leave work unfinished so I added the sound and touch controls. Watch the Market, it should appear there soon.
btw to enable the sound on a HTC Dream makes the emulator a little more sluggish, well now at least you'll have the choice (or buy a 2nd gen Android device )
Not working properly. App asks me to force close when I'm pressing MENU button... Previous build (from first post) works properly. Can I please to fix this bug?
After all, great job
Damn, I didn't make that much changes, could you get me a log trace ?
Hmm It's weird... After a couple of restarts of phone, the app is working correctly... I will leave a post (and logcat) when this problem come back.
Sadly doesn't Install on Eclair.
adb install gives Error Message "INSTALL_FAILED_CPU_ABI_INCOMPATIBLE"
Kubax83 said:
Sadly doesn't Install on Eclair.
adb install gives Error Message "INSTALL_FAILED_CPU_ABI_INCOMPATIBLE"
Click to expand...
Click to collapse
looks like a modded ROM issue to me (this emulator is compiled for ARM, no doubt about it). Try the one from the market
Wow this works really well, playing Superfrog on it now Any plans to add save states to this?
I wonder how much better performance is on the droid. Superfrog plays perfectly on my G1 with frame skip disabled and sound off, having it on made it more jerky.
Also would it possible to have the escape key mapped to something, like the shutter button or as a menu item, i'm sure some games needed it to get into the menu.
Thanks for porting this!!
5 stars from me
works great, played with it a little. kickstarted 3.0 ROM, loaded game with no problems - but Hero's hardware isn't up to it. Maybe on my next android, with faster CPU and proper keyboard...
Only problem I have had is it doesn't seem to like some of my Kickstart rom files, it works fine with one of the 1.3 roms I had with WinUAE, but says Invalid for most of the others including 3.1, all of which work in WinUAE, any ideas?
what's the exact size of the non working roms ?
Non working rom size is as follows:
3.1 - 524,299 bytes
Just thinking could it be because it is a rom from Amiga Forever from Cloanto, do they use a keyfile for the rom?
No, because I thought every roms was 524288 bytes long. Will update the market version tonight
Blazing fast on a Droid/Milestone! Thanks a lot. Just the Mouse-Control is still a little buggy. For Disk-Activity you could use the green/red led! =)
how keyboard is emulated
Hi,
I have successfully set-up UAE4Droid, tried my favorite game, but it(Pinball Fantasies) needs alt or shift to control the game. I could not figure out how to play the game because of this. (Pressing alt or shift on the G1 does not work. )
Anybody know how to use these keys?
Thanks
Sandor
Or is it just my phone?
I originally thought it was just an Android thing; A minor inconvenience that I could get used too. After helping my brother flash his Droid X and seeing how fast it completes it's scan I have to ask, what makes our phones slower?
the problem is with the file system that samsung used for our phones, you need to install a kernel where it converts it from the rfs system they used to an optimized ext 4, most of the roms come with this feature or you could just use supercrucio's kernel (Voodoo) which works best for me
whirly said:
the problem is with the file system that samsung used for our phones, you need to install a kernel where it converts it from the rfs system they used to an optimized ext 4, most of the roms come with this feature or you could just use supercrucio's kernel (Voodoo) which works best for me
Click to expand...
Click to collapse
I should have mentioned that I almost always run a lagfix.
Maybe the Droid X is just that much faster with reads, and the Captivate isn't slow.
If you have root, you can d/l rescan media root and control all that nonsense.
Sent from my SAMSUNG-SGH-I897 using XDA App
Media scan is still horrid even under custom ROMs.
Admittedly I thought it was due to the large amount of data on the slow external SDCard I have (16gig).
I want to find something where I can just disable it and run it manually whenever I want it to update.
Found an app called Rescan Media and tried it for giggles.
"Disabled" using the application - and I have to say my phone rebooted seemingly much faster - Widgets loaded and ready to use faster then I've ever had to wait before.
The media scanner will still load on boot - but doesn't re-scan your entire cards during the bootup process. And if you hit the app it will cause the Media scanner to read your cards which doesn't take very long at all since your phone is already up and booted.
Have to use it for awhile and see if it screws anything up - but I think this app is a keeper!
avgjoegeek said:
Media scan is still horrid even under custom ROMs.
Admittedly I thought it was due to the large amount of data on the slow external SDCard I have (16gig).
I want to find something where I can just disable it and run it manually whenever I want it to update.
Click to expand...
Click to collapse
See the post above yours. I tried that solution a couple weeks ago and didn't really like it, but others seemed to. (edit: just saw your previous post)
It probably wouldn't be such a nuisance if it wasn't the first freaking thing it did after reboot. Media scanning should run after other startup items... like obtaining signal, loading widgets, launcher, etc.
Or even better, have it run only when you launch the music player or gallery. I'm not sure why we would need it any other time. Or even betterest, let us set up specific folders for media so we don't need the scanner at all.
Yup I agree - Samsung strikes again at being lazy just doing a blind scan at boot up.
Since all the processes are trying to startup at the same time of the scan - it's causing the perceived lag as they are both fighting each other (for lack of a better term) for resources and I/O and takes forever for them to figure it out.
It would be nice if a Dev could create a 3rd party app that takes control of the Media Scanner - then gives us the options of only scanning certain folders and have it scheduled to run like you mentions - i.e. when <x> app loads, or after you unplug your USB, or just run it manually.
The app I posted isn't that elegant a solution but it does seem to work. My bootup time is cut in half (This is from Power Up to Usable UI Interface with Widgets loaded.).
Just nice to have considering I STILL (i.e. will never) haven't gone to AT&T to exchange my phone due to the shutdown issues I've been having. At least it's not the up to 3 minutes!! I used to have to wait for me to be able to use the phone again.
LOL.. but coming from an Apple iPhone 3G I was used to it.
it truthfully is slow... i have a sd card for more memory so it takes about twice as long than the normal.. im running darky port 8.0 with voodoo but dont see a difference..
Put a file in your folders named ".nomedia" (without quotes) that contain things like rom zips, backups, etc and media scanner will stop spending time sifting through them searching for music and photos
edit....this will also eliminate unwanted images from showing up in the gallery if you have icons or png's that you use for other purposes
Teamhacksung just released CM9 Alpha (Build 15).
I am currently on Team ICSSGS RC3.1 release and very satisfied. I even managed to work out a known issue about the screen flashing for a split second after locking screen by flashing the Devil Kernel.
Is there anyone else in my shoes who's considering going over to teamhacksung's release? Anyone tried them both?
I would like to see how many soldiers each side has and compare opinions
It's like comparing apples to oranges.
cspiby said:
It's like comparing apples to oranges.
Click to expand...
Click to collapse
i ve read that same quote somewhere before and i dont get it.
they re both designed to bring ics to i9000, therefore to me they fall under the same category
(i dont care much about the code differences and the ideology that each has adopted, i just care for which one is the most stable ICS rom for my phone)
and btw, i dont mind comparing apples and oranges, i hate oranges, i love apples
use cm9.issues are less.won't bug really bug u anyway.very stable.plus if u want overclock there
are custom kernels as well.
senotrius said:
use cm9.issues are less.won't bug really bug u anyway.very stable.plus if u want overclock there
are custom kernels as well.
Click to expand...
Click to collapse
The custom kernels work fine on TEAMICS too...
Depends what you want, clean ICS (TEAMICS) or customized (CM9).
senotrius said:
use cm9.issues are less.won't bug really bug u anyway.very stable.plus if u want overclock there
are custom kernels as well.
Click to expand...
Click to collapse
are you sure about the less issues?
Known Issues for teamhacksung's release:
Camera does not support scene modes
FM Radio does not work.
Phone unnecessarily gets data connection on device encryption password enter screen.
Cannot format external SD *
Android OS battery usage display higher than normal.
Sometime wrong SMS selected for forwarding
Format internal instead of external SD when requested to format ext. SD
Transfer speed slows down when screen off
Gallery face glow FCs
Screenshot shutter sound
Camera crashes when changing resolution
TV Out using HW-decoding (probably won't be fixed)
Sim Toolkit (probably won't be fixed)
No camera focus mode setting
Back camera does not record geotagging
Compass doesn't work in Google Maps v6
Unable to dial "0001" in some regions
Regression in BUILD 15: Superuser application crashes
icssgs team's known issues:
Screen flashes for a split second after locking screen
Market will not allow you to purchase applications
Lockscreen occasionally does not react to touch
formatting external sd formats internal
face glow editing feature in gallery causes force close
effects in video mode do not work ( causes app to close)
cspiby said:
Depends what you want, clean ICS (TEAMICS) or customized (CM9).
Click to expand...
Click to collapse
i dont care much about costumization at this early point. if they were both stable it would a whole other story but now,
i prefer more stable over more customizable. however since build 15 is actually a cm9 alpha now,
i m wondering if it's stability is enough to worth the transition
c0rpse_grinder said:
are you sure about the less issues?
Known Issues for teamhacksung's release:
Camera does not support scene modes
FM Radio does not work.
Phone unnecessarily gets data connection on device encryption password enter screen.
Cannot format external SD *
Android OS battery usage display higher than normal.
Sometime wrong SMS selected for forwarding
Format internal instead of external SD when requested to format ext. SD
Transfer speed slows down when screen off
Gallery face glow FCs
Screenshot shutter sound
Camera crashes when changing resolution
TV Out using HW-decoding (probably won't be fixed)
Sim Toolkit (probably won't be fixed)
No camera focus mode setting
Back camera does not record geotagging
Compass doesn't work in Google Maps v6
Unable to dial "0001" in some regions
Regression in BUILD 15: Superuser application crashes
icssgs team's known issues:
Screen flashes for a split second after locking screen
Market will not allow you to purchase applications
Lockscreen occasionally does not react to touch
formatting external sd formats internal
face glow editing feature in gallery causes force close
effects in video mode do not work ( causes app to close)
Click to expand...
Click to collapse
this is the reason icssgs is the one for now for me ...
haven't tries ICSSGS yet... working on CM9 foe almost 2 weeks now and its pretty decent... stable too... one thing that bugs me is how little mods are available for CM9 at this point... however CM9 for SGS2 is littered with mods... some quite useful (like ANZO MOD)... whats it like for ICSSGS version?
c0rpse_grinder said:
are you sure about the less issues?
Known Issues for teamhacksung's release:
Camera does not support scene modes
FM Radio does not work.
Phone unnecessarily gets data connection on device encryption password enter screen.
Cannot format external SD *
Android OS battery usage display higher than normal.
Sometime wrong SMS selected for forwarding
Format internal instead of external SD when requested to format ext. SD
Transfer speed slows down when screen off
Gallery face glow FCs
Screenshot shutter sound
Camera crashes when changing resolution
TV Out using HW-decoding (probably won't be fixed)
Sim Toolkit (probably won't be fixed)
No camera focus mode setting
Back camera does not record geotagging
Compass doesn't work in Google Maps v6
Unable to dial "0001" in some regions
Regression in BUILD 15: Superuser application crashes
icssgs team's known issues:
Screen flashes for a split second after locking screen
Market will not allow you to purchase applications
Lockscreen occasionally does not react to touch
formatting external sd formats internal
face glow editing feature in gallery causes force close
effects in video mode do not work ( causes app to close)
Click to expand...
Click to collapse
Cm9 have more issue because it have more users, and I don't think those are only cm9 bugs, happend on onecosmic's as well
Sent from my GT-I9000 using Tapatalk
cspiby said:
It's like comparing apples to oranges.
Click to expand...
Click to collapse
All based on ICS 4.0.3 source, so why? Because another team ports it to the GS? I think still Apples to Apples and they both do a good job..
onecosmic's team doesn't release all all issue .
CM9 is better and stabler. I traid onecosmic's RC3 and RC3.1 for a while but no that not comparable to CM9.
I am on teamhacksung build 15 and not going back to Samsung ROM or any other ROM because it's stable, smooth and fast.
It has issues and so does others, I can live with it.
Sent from my GT-I9000 using xda premium
im using CM9 alpha RC0 (TH 15)
theres not many working options in the menus yet but ive been getting really good battery life and performance from lulzactive governor after flashing devil kernels. Seems good so far but disappointed that the battery indicator option in the menus didnt work to change the battery icon to percentage. Il probably stick with CM9, big userbase so should keep getting frequent updates
I'm using CM9 Build 15 with Devil Kernel
it works grat =)
I would at this point go for the Teamhacksungs myself. There are a number of reasons, both stability and feature wise.
1. They offer control over visualisations.
2. They have quick setting available on the drop down tray
3. The media duplicate issue has been sorted
4. It doesnt lag and lose stablity when more apps are installed
5. I am not sure this is an experience of others, but I have found Teamhacksungs battery life far superior. (not by a lot though! maybe my battery is failing generally)
There are still a few glitches... I tried to go back to Gingerbread... man, after 5 days on ICS, its not possible to go back. Believe me. ICS is almost perfect.
Reason why I have always went with RC3.1 Over CM9 is because CM9 the text always looks terrible and all pixelated
Does this happen for other people? or just me
My choise is Teamhacksungs CM9 because of its stability and other stuff it has. I am proud user of Teamhaksungs since build 6 and i will never switch to onecosmics and ICSSGS because ICSSGS is built ontop of onecosmic's and both do not display a full list of bugs and glitches they have by only showing "what works" while CM9 offers a full list of what it can and can't do.
CM9 teams doesn't go away if some trolls spam their tread... Cant say the same for Onecosmic..
As I need something I can rely for some time, I prefer to go to the ROM that gives me more guarantees that there will be an upgrade path for the coming weeks...
Other than this I cant compare because I'me using only Teamhacksung builds for some time..
tried both
c0rpse_grinder said:
are you sure about the less issues?
Known Issues for teamhacksung's release:
Camera does not support scene modes
FM Radio does not work.
Phone unnecessarily gets data connection on device encryption password enter screen.
Cannot format external SD *
Android OS battery usage display higher than normal.
Sometime wrong SMS selected for forwarding
Format internal instead of external SD when requested to format ext. SD
Transfer speed slows down when screen off
Gallery face glow FCs
Screenshot shutter sound
Camera crashes when changing resolution
TV Out using HW-decoding (probably won't be fixed)
Sim Toolkit (probably won't be fixed)
No camera focus mode setting
Back camera does not record geotagging
Compass doesn't work in Google Maps v6
Unable to dial "0001" in some regions
Regression in BUILD 15: Superuser application crashes
icssgs team's known issues:
Screen flashes for a split second after locking screen
Market will not allow you to purchase applications
Lockscreen occasionally does not react to touch
formatting external sd formats internal
face glow editing feature in gallery causes force close
effects in video mode do not work ( causes app to close)
Click to expand...
Click to collapse
Personally, I had more issues with onecosmic rc3.1 (only had it installed for 3 days tbf) - not to say I haven't had any issues with cm9 build15 and build14 for a week before that, but generally I prefer both the stability and customisations of cm9 (eg power widget bar)
The fact that they know of, and are bothered enough to release a list of, the bugs encourages me that they're working on it
Also, I miss pvz but that's down to app incompatability with ics in general...
SlimKat is a V4 (KitKat) ROM by SlimRoms. It's based on AOSP 4.4.4. Its latest release, build 9.0, was Dec-22 2014 with a 3.0.8 kernel.
Its disadvanatges are that it is no longer supported by the Slim dev team; no custom overclock kernels exist for it; no hand-wave for notifications lockscreen feature of the later 5.0+ versions; and there's no support for altpart Safestrap.
But that's where its downsides end and its upsides begin. With nearly any 3rd-party ROM it's a series of tradeoffs. What works and what doesn't, what do you need and what can you do without. Not so with SlimKat. Everything, and I mean everything, just... works. Flawlessly. Even HDMI. This ROM is feature-rich, yet still so lean you can run it with Slim's normal Gapps package on the stock slot. At 180MB, Slim's normal Gapps package is 15MB smaller than the OpenGapps nano package for 7.1.2. I've been running this as a daily driver for over a month and not a single thing has gone wrong with it. No force-closes. No hangs. No jitters. No crashes. No random reboots. This is as close to a stock ROM's stability and performance as anything I've ever used. It's fast and responsive and handles whatever you throw at it. All that and great battery life too - I typically get about 36-44 hours from a full charge.
Support for 4.4.4 is extensive throughout the app community and I have yet to find an app that doesn't work with it. Custom fonts are easily installed with iFont and there are extensive interface and navigation customizations available in the SlimCenter. Cyanogenmod/LineageOS 11 themes are available for it on the Play Store.
The stock SlimLauncher is extensively configurable, and supports gestures, desktop folders, grid size configuration, icon size configuration, hidden apps, hidden icon labels and much more. I prefer a horizontally paged interface for my app drawer, and this one works exactly as this should work, where you swipe left or right and each page of app icons disappears behind the next, rather than a continuous side-scroll. This is especially important on the Droid 4 because of its TFT screen's limitations that make things difficult to read when continuously scrolling against a dark background.
While most ROMs will let you disable some system apps, SlimKat has a SlimSizer app in the SlimCenter settings that lets you save or fully remove any included system app from a simple checklist. SU is integrated and the ROM is rooted out-of-the-box. Google Voice works seamlessly with it. Voice Search starts up quickly and doesn't hang or crash, and interactions with it are predictable. The built-in WiFi hotspot works flawlessly. It natively supports Face Unlock.
Its sole quirks are that the keyboard doesn't illuminate when you slide it open until you press a key, and direct reboot to recovery doesn't work (just do a standard reboot and activate SafeStrap recovery at startup).
Verdict: Hands down, the overall best 3rd party ROM I've tested for the Droid 4. Rock-solid, OEM-level reliability and performance in a compact yet feature-rich package with outstanding battery life. If you don't require a newer version of Android (5+) for app compatibility or features, and don't want the code-bloat of the later versions, you simply can't do better than SlimKat on the Droid 4.
Thank you for this!
I was hoping there were some posts like this, but it being 2018 I wasn't optimistic...
just picked up a droid 4 to have a backup phone and for a bit of nostalgia - I had an OG droid that I kind of miss using
Update: After six months with SlimKat, I'm moving on. There's only one real problem I've had with it, but it's been really annoying. Frequently it just won't wake up the screen - the soft buttons light up, but the screen stays blank. It can often take several attempts before it works, if at all - usually after the third try I just give up and wait it out until the next time I want to check it. This is especially frustrating when receiving a call, as I've often missed calls just waiting for it to wake up the screen so I can answer it. Never been able to track down the cause or figure out a solution.
There's also a strange problem in the file system that there are "ghost" files throughout. Blanks show up randomly throughout my gallery, and duplicates of music and videos also work their way in, confusing the database and making it difficult and sometimes impossible to play back these files. I tried clearing app data for the Gallery and rescanning, even moving files to new folders, but it would only fix it temporarily and eventually these would come back. My gallery would show I had 1200 pictures when I had at most 350, and my music library would also show five copies of the same song, only one of which would actually play. I thought maybe these were ghosts of deleted files, but could never be sure. I used an alternate gallery app, QuickPic, and it worked normally without the blanks.
The hotspot feature had issues as well. It would pass the traffic for the connected devices, but after a while it would stop working for the apps on the phone itself, until I shut it off.
I'm not sure if it's a possible problem in my phone either, so I'm trying something different.
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 .