Database Info

[FIX] --- EpicMTD CM7 Rotation Lag Fix! --- (Updated to preferred method)

Introduction
This is the optimal method for reducing and almost eliminating rotation lag in EpicMTD CM7. For those of you looking for the old method that involved hacking framework.jar, please see the second post in this thread, Deprecated (Old, Archaic) Rotation Lag Fix How-to
DISCLAIMER
I have personally used this method and know it works. Furthermore, many others have used this method and it seems pretty reliable. That said, should anything unpleasant happen, to include bugs being introduced, your phone bricking, or your firstborn child emerging as the anti-christ, well, it's not my fault. You did it.
Rotation Lag Eliminator Guide
If you have a ROM setup that you're fond of, or high-scores that you want to keep, I recommend doing some backups
Nandroid from ClockworkMod Recovery ("CWM") will backup your entire ROM, which you can restore after the fix and have your phone back to the state it was in before you made the backup. (Kentucky.)
Alternatively, after step 5 you can restore just the /data partition from a previously-created Nandroid backup.
Titanium Backup can back up & restore individual apps and settings, as well as restore from a previously created Nandroid backup.
Flash a GB ROM (not sure if it must be MTD, but I recommend it), I recommend toadlife's Clean-GB MTD
Go to [Settings] > [Display] > [Horizontal Calibration]
Calibrate. (Obvious, no?)
Flash your favorite EpicMTD CM7 Nightly, AKA the latest one. (You know I'm right!)
Think to yourself "That AmericanJedi001 just might be a genius. He damn sure knows how to fix rotation lag!"
Immediately follow that with the self-rebuttal "Yeah, but it's not like this required anything previously unknown in this community."
Caveats & Notes
Slight risks are involved in flashing ROMs and backing up and restoring Nandroids and individual apps.
This fix should persist across ROM flashes, and therefore Nightly flashes. There may be something that breaks it, but I haven't found it yet. (I'm not trying to break it, but I don't know where the calibration data is saved, therefore I don't know what mods will break it.) I suspect that either a) switching minor versions of Android, such as going from Froyo / 2.2 to Gingerbread / 2.3; or b) switching partition maps, such as going from BML to MTD, is what breaks it.
Thanks and Acknowledgements
Thanks to Decad3nce for pointing out that not everyone has had issues with rotation lag in EpicMTD CM7, which got me to thinking that the framework.jar hack might not be the optimal fix.
ISSUES / PROBLEMS / BUGS?
I'm reluctant to provide any active support for this fix because all of its steps are well-known and -documented elsewhere. That said, if you have any issues that you think are specific to rotation-lag elimination, post 'em here. If you post something in the vein of "I flashed blah-blah-blah and now my phone figuratively resembles a brick..." or "Why won't my backup restore?" I'm going to ignore you, because that's not specific to this fix. Those questions have been beaten like Jim Caviezel in Passion of the Christ, and like his character sometimes I wonder how they're not dead yet. Please use good judgement before you look for help here.

Deprecated (Old, Archaic) Rotation Lag Fix How-to
Introduction
This is the old, deprecated fix for minimizing rotation lag in EpicMTD CM7. It has been superceded by the method described in the OP above. Feel free to play with this hack, but know that I will not be supporting it, nor will I go any deeper into the how-to guide: this is a moderately broad overview, and the details of learning how to hack .jar files will be left to the reader to discover. I learned 95% of this hack by searching and reading what others had done, not by asking people to spoon-feed me instructions. Take that to heart!
DISCLAIMER
I have tested the framework.jar file and the flashable .zip on my own phone, with awesome results. However, I refuse to be held accountable for any issues you may have.
Installation
-- "framework.jar" Replacement Method
Delete or rename /system/framework/framework.jar (I recommend you simply rename it so that if you have issues you can easily switch back to your "stock" file
Copy framework.jar to /system/framework, then reboot.
???
Profit from the blazing rotation speed!*
-- Flashable .zip Method
Copy EpicMTD_CM7_Rotation_Lag_Eliminator.zip to the root of your SD card
Boot into CWM Recovery (or possibly ACS Recovery?)
Flash the "EpicMTD_CM7_Rotation_Lag_Eliminator.zip" file
Breakdance.
Reboot and enjoy a lag-free* experience!
-- Caveats
THIS METHOD IS DEPRECATED! USE THE METHOD IN THE OP TO FIX YOUR ROTATION LAG PERMANENTLY, RATHER THAN HAVING TO HACK framework.jar FOR EACH NEW RELEASE!
* At least one person has successfully replaced framework.jar, but was not impressed with the improvement in rotation speed
Users of previous versions of this fix reported their phones hanging during boot (I have never experienced this)
One person reported that menus were changed, but I suspect he flashed this fix (created specifically for CM7) on top of another ROM
For other GB ROMs the fix should be basically the same, though I would recommend using the framework.jar from that specific ROM. See the Resources section below if you're interested in learning the technical end of the fix.
Downloads
-- Standalone File
framework.jar - Pulled from CM7 Nightly-10 (4G Toggle in Notification Widgets)
-- Flashable .zip
EpicMTD_CM7_Rotation_Lag_Eliminator.zip - Pulled from CM7 Nightly-10 (4G Toggle in Notification Widgets)
-- Resources
my post in Chris41g's EF02 Rotation Lagfix topic
Chris41g's original fix for EF02
ISSUES / PROBLEMS / BUGS?
I will no longer support this hack. I have since learned of a much better method for almost eliminating rotation lag, a method that persists across ROM flashes and therefore does not require updating periodically when new versions of framework.jar accompany a new release of CM7. This is here simply because I can't delete the topic, and for historical interest.
Thanks and Acknowledgements
Thanks to Chris41g for the original fix, without stumbling upon that topic I would never have figured this out myself!
How-to Overview
With chris41g's original fix, here's what he had to say about it:
chris41g said:
...some framework edits will need to be made [to] \system\framework\framework1.jar.out\smali\android \view\WindowOrientationListener.smali
Code:
.prologue
.line 54
const/4 v0, 0x3
needs to be changed to
Code:
.prologue
.line 54
const/4 v0, 0x2
Click to expand...
Click to collapse
I pulled my "/system/framework/framework.jar", then pulled "classes.dex" from there and smali'd it, then browsed "...\classout\android\view\WindowOrientationListener.smali" in Eclipse. I found
Code:
.method public constructor <init>(Landroid/content/Context;)V
.registers 3
.parameter "context"
.prologue
.line 67
const/4 v0, 0x3
invoke-direct {p0, p1, v0}, Landroid/view/WindowOrientationListener;-><init>(Landroid/content/Context;I)V
.line 68
return-void
.end method
which is the closest to what chris41g posted for the original fix. I changed the "0x3" to read "0x0".
I then baksmali'd it into "classes.dex" and inserted that back into framework.jar, which is then copied into /system/framework, replacing the stock framework.jar. Done!
If anybody has any insight, tips, improvements, etc., send 'em! This is my first real contribution that involved any coding (not that I did much!) and I want to learn anything you Grand Masters have to share.

will this also have an effect on miui? not that the lag is bad or anything, but less is more in this case

FrankyFiggz27 said:
will this also have an effect on miui? not that the lag is bad or anything, but less is more in this case
Click to expand...
Click to collapse
As I stated above, I'm not an expert developer, so take this with a grain of salt... If you're experiencing rotation / orientation-change lag with MIUI on GB, first try using the"Horizontal Calibration" option in [Settings] > [Display]. You may have to apply it with your phone face-down, just hanging over the edge of the table/desk/counter so you can click the button to calibrate. If that doesn't work or is unavailable, try the"sensorcalibutil_yamaha" fix (you must be rooted for this):
Open a terminal emulator
Type "su" [Enter], then "/system/sensorcalibutil_yamaha" [Enter]
Follow the instructions to calibrate
If that doesn't work--and if you're using a GB ROM, I don't think it will--then the fix I posted above is your only other option. Should you decide to try it, I highly recommend you build your own "framework.jar" by pulling it from your ROM of choice and following the instructions provided by chris41g and me. If it works, let me know and I'll add it to the OP and change the title to reflect what ROMs we have framework.jars and/or flashable zips for. Good luck!
* FYI, I have no experience beyond CM7 with GB ROMs, & I've only used SRF ROMs & related kernels with Froyo.
AmericanJedi001

This can be fixed in the cyanogenmod framework source code

Good first attempt. There's a problem with your patch though. It messes up the homescreen menu and shutdown popup. if you are on homescreen and press menu, there is usually a tab that says "More" and has the unlock/lock desktop option, the patch changes this to "text from clipboard" also when you hold the power button and select shut down, the popup says reboot instead of power off. I think the problem is just a matter of line spacing being off in the Framework.jar or something, but this is an uneducated guess. Either way just wanted you to be aware. I think a better option would be to have it edit that one line of text in the framework.jar rather than replacing the .jar file completely. Good luck, happy coding.

AmericanJedi001 said:
...If that doesn't work or is unavailable, try the"sensorcalibutil_yamaha" fix...
Click to expand...
Click to collapse
sensorcalibutil_yamaha was pulled from gb...

counterfeit187 said:
Good first attempt. There's a problem with your patch though. It messes up the homescreen menu and shutdown popup. if you are on homescreen and press menu, there is usually a tab that says "More" and has the unlock/lock desktop option, the patch changes this to "text from clipboard" also when you hold the power button and select shut down, the popup says reboot instead of power off. I think the problem is just a matter of line spacing being off in the Framework.jar or something, but this is an uneducated guess. Either way just wanted you to be aware. I think a better option would be to have it edit that one line of text in the framework.jar rather than replacing the .jar file completely. Good luck, happy coding.
Click to expand...
Click to collapse
Editing a single line in a jar file isn't currently possible via CWM flash - this is the same reason themes and mods must often be combined, because they are modifications to the same file, and we can only replace files, not merge them
Sent from my SPH-D700 using XDA App

counterfeit187 said:
Good first attempt. There's a problem with your patch though. It messes up the homescreen menu and shutdown popup. if you are on homescreen and press menu, there is usually a tab that says "More" and has the unlock/lock desktop option, the patch changes this to "text from clipboard" also when you hold the power button and select shut down, the popup says reboot instead of power off. I think the problem is just a matter of line spacing being off in the Framework.jar or something, but this is an uneducated guess. Either way just wanted you to be aware. I think a better option would be to have it edit that one line of text in the framework.jar rather than replacing the .jar file completely. Good luck, happy coding.
Click to expand...
Click to collapse
styles420 said:
Editing a single line in a jar file isn't currently possible via CWM flash - this is the same reason themes and mods must often be combined, because they are modifications to the same file, and we can only replace files, not merge them
Click to expand...
Click to collapse
Styles420 is correct, that's why the fix (framework.jar or flashable.zip) replaces the "stock" CM7 framework.jar file. I assure you the only thing I changed was the digit after "0x", as in "0x1", then I recompiled/rebuilt everything. As far as I know, that shouldn't have far-reaching side-effects such as you're describing, but I'll look into it. Did you flash the file (any of the three) on the latest CM7 (10/22) , or another version of CM7, or another ROM entirely (if so, which)?
AmericanJedi001

noobnl said:
This can be fixed in the cyanogenmod framework source code
Click to expand...
Click to collapse
Sweet! BTW, where would I find the source for framework.jar? I know where the repo is, but I got lost searching thru all the different sections. Any specific directions?
bender beerman said:
sensorcalibutil_yamaha was pulled from gb...
Click to expand...
Click to collapse
Just as I suspected. I wonder if the fix chris41g found will be all we need for GB rotation / orientation-change lag? I hope so!
AmericanJedi001

Wow, out of 500+ views there have only been five other people post on here? Come on people, give me some kind of feedback! Does it work, are there issues, etc.?

I Installed on my phone and it got stuck at the samsung screen during boot up. Re flashed ROM and it was all better

couldn't get this to boot when on CM7. Froze at Sammy screen for me. tried this on MIUI Beta 3 just for giggles but no sucess there either. Too bad. Rotation lag is my mortal enemy. Lol.
Sent from my MIUI-ified Epic using XDA App

Aloth600 said:
I Installed on my phone and it got stuck at the samsung screen during boot up. Re flashed ROM and it was all better
Click to expand...
Click to collapse
After you reflashed the ROM (CM7?) did you try the fix again, or did you just not have rotation lag after the reflash?
sniperwitagun said:
couldn't get this to boot when on CM7. Froze at Sammy screen for me. tried this on MIUI Beta 3 just for giggles but no sucess there either. Too bad. Rotation lag is my mortal enemy. Lol.
Sent from my MIUI-ified Epic using XDA App
Click to expand...
Click to collapse
Were you on CM7 10/22 or an earlier release? I'm not surprised it didn't work for MIUI: the files I posted are the framework.jar and a flashable framework.jar from CM7, with only one digit difference from my stock framework.jar with CM7.
In other words, I will really be surprised if the files in the OP work for any ROMs besides CM7, and they may not work for anything besides CM7 10/22.
If you guys are using CM7 10/22, then you may want to follow the directions and pull your own framework.jar (rather than using the one I posted) and do the edit on your own file, then copy it back over. Let me know if you need any clarification on any of the steps.
I'm hoping that future builds of EpicCM will have this fix coded directly into the framework.jar--noobnl posted that it would be possible, so I'm hoping that it is on the to-do list.

were the ppl with the issues were running a modified framework.jar to facilitate an ext4 kernel?

AmericanJedi001 said:
After you reflashed the ROM (CM7?) did you try the fix again, or did you just not have rotation lag after the reflash?
I just re-flashed and didn't attempt again but, rotation lag is still there.
Click to expand...
Click to collapse

Aloth600 said:
I just re-flashed and didn't attempt again but, rotation lag is still there.
Click to expand...
Click to collapse
If you used the CWM flashable zip, try just replacing your framework.jar with the one I provided. Be sure to save your original (either rename or move to another location), copy the provided framework.jar over, then reboot. If *that* doesn't fix it, then you may need to manually do the hacking yourself, though I hope not--that's why I created this thread with the available files, to save people time!
bender beerman said:
were the ppl with the issues were running a modified framework.jar to facilitate an ext4 kernel?
Click to expand...
Click to collapse
This is a good point--if you're already running a framework.jar that's modified from the original provided with your ROM of choice (to use an EXT4 kernel, for example*), then you'll need to hack that framework.jar file. The framework.jar that's available here will probably only work with the RFS version of CM7, not any modified versions, nor other ROMs. Of course you folks are welcome to try it, but YMMS (Your Mileage May Suck)!
* I'm not sure that an EXT4 kernel will require a modified framework.jar, but you get the point.

I was on cm7 10/22. It still didn't work.
Sent from my SPH-D700 using XDA App

sniperwitagun said:
I was on cm7 10/22. It still didn't work.
Click to expand...
Click to collapse
Would you feel comfortable editing your own framework.jar file? If you're familiar with Smali/Baksmali, you should be able to follow the directions and hack up your own framework.jar to fix the rotation lag. If not, send it to me and I'll mess with it the next chance I get (no guarantees, it might be after Thanksgiving before you get it back!).
I feel ya, it's one of my pet peeves as well, thus the fix!

AmericanJedi001 said:
If you used the CWM flashable zip, try just replacing your framework.jar with the one I provided. Be sure to save your original (either rename or move to another location), copy the provided framework.jar over, then reboot. If *that* doesn't fix it, then you may need to manually do the hacking yourself, though I hope not--that's why I created this thread with the available files, to save people time!
Tried it and it locked up at the sammie screen.... flashing back now.
Click to expand...
Click to collapse

Add htc_ime back into stripped down ICS roms

hey, just testing out a few of the stripped down ICS 4.0.3 roms. theyre really great, but the devs always take out the htc_ime. i really like to have that cause of the language selection.
i know i saw somewhere a .zip to flash it back in, but i cant find it now that i need it! anyone know where it is??
thanks!

I heard that HTC_IME is not compatible with ICS...

It is compatible - im using it with no problems. Even HTC trace works fine.
What you need to do (sorry i cant make a flashable zip)
download the zip from HERE
Extract the zip file
Push the HTC_IME.apk (from app folder) to /system/app (I use ES file explorer) and change permissions to RW-R-R
Then push the libs (from lib folder) to /system/lib and change permission to RW-R-R - there should be 5 in total.
Then reboot. I also wiped cache & Dalvik cache just to be sure.
NOTE: if you are using virtuous inquision the lib files are already present. This is the rom im using and since it is based from the HTC leak, the dev has not removed the libs. So all you need is the HTC_IME.apk into /system/app and then you should be able to select the HTC touch input in the keyboard list.
I hope this helps

Doesn't work. Even after copying all the files to their proper folders, ensuring permissions are correct, and wiping cache and dalvik... It still force closes as soon as Touch Input is selected. Just tried it on CM7.
I'm going to try to investigate this problem and see what I can come up with. I know everybody used to say that Clicker.apk was needed. But if you look at most of the ROMs out there, you'll see that they somehow use the HTC_IME keyboard without having Clicker.apk. So what's missing?
Edit: I feel like I'm going to give myself a headache trying to figure this out. The logcat for the FC said (amongst other things) that there is a ClassNotFoundException for KeyboardSettings. There's also a lot of ActivityThread errors which don't really mean much to me. A Google search revealed that it may be related to the AndroidManifest.xml in the APK file, but unfortunately it's not a standard XML file (try opening it to see what I mean). Not to mention, the APK is obviously fine, because I pulled it right from the ROM.
So basically, we need to somehow figure out what other files are needed by HTC_IME.apk, besides the libraries mentioned already in this thread. I assume that it worked for beady_uk because the ROM he was using already had the rest of the required files without him knowing. I'm going to continue looking to see if I can find more information, but I would definitely appreciate if anybody has any technical input into this situation. I can provide logcat information if needed.

Gamesoul Master said:
Doesn't work. Even after copying all the files to their proper folders, ensuring permissions are correct, and wiping cache and dalvik... It still force closes as soon as Touch Input is selected. Just tried it on CM7.
I'm going to try to investigate this problem and see what I can come up with. I know everybody used to say that Clicker.apk was needed. But if you look at most of the ROMs out there, you'll see that they somehow use the HTC_IME keyboard without having Clicker.apk. So what's missing?
Edit: I feel like I'm going to give myself a headache trying to figure this out. The logcat for the FC said (amongst other things) that there is a ClassNotFoundException for KeyboardSettings. There's also a lot of ActivityThread errors which don't really mean much to me. A Google search revealed that it may be related to the AndroidManifest.xml in the APK file, but unfortunately it's not a standard XML file (try opening it to see what I mean). Not to mention, the APK is obviously fine, because I pulled it right from the ROM.
So basically, we need to somehow figure out what other files are needed by HTC_IME.apk, besides the libraries mentioned already in this thread. I assume that it worked for beady_uk because the ROM he was using already had the rest of the required files without him knowing. I'm going to continue looking to see if I can find more information, but I would definitely appreciate if anybody has any technical input into this situation. I can provide logcat information if needed.
Click to expand...
Click to collapse
I believe that you have mis-read the 1st post.
The OP asked how to re-add the HTC_IME to a stripped down rom that the dev had removed.
This is what i have done and it worked - possibly because the roms are sense-based framework.
You have tried to install this on CM7 with is CM based framework so i think you will need more 'files' but that is beyond my knowledge.
Sorry i cant help further

You are correct. I was in a deep search for anything revolving around installing it, so I missed that part. I saw your post (which is the only place I've seen anybody mention installing those lib files), and I guess that caused further oversight on my part.
I do imagine this may not work on all the stripped down ROMs though, if any of the cooks stripped their ROMs like I stripped my old Win98 PC that had a 1GB hard drive in it... that is to say, remove every possible file that wouldn't cause stability issues

[Q] How to add menu options UPDATED with new ?

I've been trying to figure out how to get NFC working on the stock ROM for a while now. In no way am I a DEV or experienced with Android coding, but I have learned a few things along the way. I know basic NFC functions are available in certain ROMS, but this is about getting it working on the stock ROM. I am also aware that Google Wallet will not work on these phones without a secure elemint (sp?). But with all of the interest in NFC (even though its uses are limited), I would think alot of people would like to have the option to enable it on the stock ROM.
Here is a few things a have discovered:
These phones already have the Nfc.apk and Nfc.Odex files included. They are very similar to the files on the Korean version of this phone that has working NFC.
The framework-res.apk xml already includes code for NFC operations. I have read where people have said that extra framework is needed, but from what I see (again limited knowledge) it already exists.
I also found (I can't remember where) more code for NFC that includes connection instructions and what it is supposed to do when a NFC signal is detected.
So I am thinking, maybe the only thing we need at this point is to have the option for NFC along with the toggle added to the "Wireless and Network" menu on the phone. Maybe it already exists and just needs to be activated.
Oddly enough, it seems very little information exists about trying to activate NFC on the SkyRocket I727 stock ROM. Alot of the information a got was from the regular Galaxy SII forum and it is obvious that phone isn't coded exactly as ours.
So, can any one tell me in which part of the coding is the "Menu options" enabled for the "Wireless and Network" settings? Maybe I am wrong about all of this, but if anyone knows anything more about it (not just guessing but actually knows something), please post it here so we can get the NFC function working on the stock ROM.
On a seperate note, the same place I found the coding about the NFC operations (like I said, I can't remember where it was but I will try to find it again) I also found additional mentioning of an"FM radio chip"???

OOOOKKKKKKK...can someone atleast point me in the right direction to find this out on my own?

You can edit setting.apk and enable nfc. Or just dload a rom that lets u use nfc.
scott14719 said:
I've been trying to figure out how to get NFC working on the stock ROM for a while now. In no way am I a DEV or experienced with Android coding, but I have learned a few things along the way. I know basic NFC functions are available in certain ROMS, but this is about getting it working on the stock ROM. I am also aware that Google Wallet will not work on these phones without a secure elemint (sp?). But with all of the interest in NFC (even though its uses are limited), I would think alot of people would like to have the option to enable it on the stock ROM.
Click to expand...
Click to collapse

appdroid said:
You can edit setting.apk and enable nfc. Or just dload a rom that lets u use nfc.
Click to expand...
Click to collapse
Thanks for the response, but what do I edit in settings.apk? I have read this more than a couple of times, but no one seems to be able to say what edits to make to the settings.apk. As far as the others ROMS go, I realize NFC works in other ROMS, but I'm trying to find an option to enable it in the Stock ROM. Any info you can provide would be great. Thanks.
Edit...I took a look at the setting.apk XML from a T-mobile phone that has NFC enabled and it seems to be the same as the settings.apk XML from the Skyrocket. This is the confusing part. Everyone seems to think the settings.apk app needs editing, but it is the same as ones in the versions of our phones that have working NFC. As a matter of fact, the NFC.apk apps are the same as well. This is why I am thinking it only needs the option added to the "Wireless an Netwok" menu in order for it to work (which is my original question on how to do so). Things just aren't adding up here?

OK, so I've been looking around some more and I found something interesting.
The T-Mobile (T989) version of the Skyrocket has an extra file located in the settings.apk that the I727 AT&T Skyrocket doesn't appear to have in it's settings.apk.
This file is named "smali". Most of the rest of the settings.apk on both phones appear to be very similar. There are about 9 extra lines of code in the "manifest.xml" in the I727 but they do not appear to be related to Nfc operations at all.
This "smali" file in the settings.apk on the T-mobile phone contains a folder called "com" and the "com" folder contains three more folders called "android", "broadcom", and "samsung". The "broadcom" and "samsung" folders appear to contain information (code) about bluetooth operations. The 'android" folder is the interesting one. It contains a "settings" folder that has many other folders in it. Again, most interesting is a file called "Nfc". It contains 5 smali files that all contain code about Nfc functions. I think this may be the actual file(s) that AT&T had Samsung leave off of this phone (I727) so Nfc is not enabled.
So finally, my new question(s) is..........
Can anyone confirm that the exclusion of the "smali" file in the settings.apk on the Skyrocket is the reason we can not use Nfc?
-and-
Would it be safe or even possible to insert the "smali" file contained in the T-mobile settings.apk into the settings.apk of the AT&T Skyrocket phone and see if it would properly activate Nfc on the AT&T Skyrocket? If so, could this be done on the "stock" AT&T 2.3.6 ROM without being DeOdexed?
I realize this is a lot to ask, but this is the only way we can get NFC working on the stock ROM like it should be in the first place. Maybe one of the Devs that works with the skyrocket can help to answer some of these questions. Thanks to anyone that can help.

This doesn't help u in your finally quest of enabling nfc, but the reason u see the smali folder in the decompiled system.apk for the T-Mobile apk is most likely because it is deodexed, and the apk that u are looking at from your skyrocket is not deodex. If u use apktool or something similar to apktool and decompile a non deodexed apk u will not see any smali file. The smali folder is basically the Java code that is in the system.odex file (layman's terms)
This is why most..or most ever apk edit is don't on an odex apk. Because without it being doedex u would have to edit both the apk and the odex file

To add
If can get your hands on a stock doedex sky rocket rom that's what u would want to use to compair the two with
Sent from my Galaxy Nexus using Tapatalk

runandhide05 said:
To add
If can get your hands on a stock doedex sky rocket rom that's what u would want to use to compair the two with
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I have compared the Stock SkyRocket ROM to both T-Mobiles ROM and the Superstock ROM. The SuperStock ROM is a DeOdexed AT&T version of what I have. The Stock ROM (on my phone) and the SuperStock ROM (DeOdexed) seem to be the same. I have not searched and compared every single file and line of code but the settings.apk and framework.apk and framework-res.apk files seem to be the same? The "smali"file folders that were located on the T-mobile ROM are not on the DeOdexed Stock ROM (atleast not that I have found. Unfortunately I have seem to come to the end of my abilities to do anything else. I just don't have the knowledge to go any further. Hopefully one of the DEVs around here could help out if they get the time. I know the effort would be appriciated, but it is up to them.. Most of them seem to be keeping pretty busy with updating their ROMS.
**edit** Ok, I spoke too soon. I found the "smali" files in the DeOdexed Superstock ROM. They are in the ".jar" files. The framework.jar file has the folder that has info about NFC in it. I just have no idea what to do with it from this point. I still think that everything that is needed for NFC to work is already in the Stock ROM, it just needs menu options to get to it.

[ROM][i577][CWM]Stock Deodexed Debloated Exhilarate ICS

Hey everybody -
Seems folks are wanting some sort of cwm recovery flashable twist on the i577 stock ICS rom that was first posted here, but is also discussed here and can be attained in an easy one-click odin fashion from here thanks to thomas.raines. Well, I think I managed to put one together. I don't know if I will tinker on this much, but you never know - I can't stop myself most of the time.
I AM IN NO WAY RESPONSIBLE FOR ANYTHING THAT HAPPENS (GOOD OR BAD) AS A RESULT OF FLASHING OR ATTEMPTING TO FLASH WHAT IS POSTED HERE!
The process to get here was rather simple (though the updater-script editing was rather annoying). After flashing via thomas.raines's handy dandy odin 1-click tool, I got a system dump. Originally I was just going to open up the system.img.ext4 and get what I needed from there, but I did it this way to figure out some permissions and symlink issues I was having with the updater-script. I then went through and deodexed, debloated, added in busybox, added in SuperSU, and made one small smali hack to Contacts.apk to stop a rather annoying insistence on checking AT&T subscriber crap every time you went into contacts. That's it - so this is not really all that "developed" or anything. All that is contained within the cwm zip is the same stuff that is contained in the one-click - it's just /system and boot.img (kernel) - nothing more (i.e. this does NOT change your modems). That all being said, let me know if things work, or if any oddities come up. Also feel free to comment on how this might improve or if I've gone about anything in a not-so-smart way.
Usual rules apply - make sure to wipe data/factory reset to avoid issues. Flash in CWM recovery.
CWM Installation instructions:
- Backup your current setup/data
- Download file and place on sdcard
- Boot into CWM recovery
- Recommended to wipe data/factory reset in CWM recovery
- Select and install the .zip you put on your sdcard
---DOWNLOAD LINKS - CWM---
Debloated deodexed rooted busybox-ed i577 stock rom and kernel
md5: 5645D032DA35923A9B00F15539D06AEA
---OTHER DOWNLOADS---
i577 ICS Deodexed System Apps
NOTE: This IS NOT CWM RECOVERY FLASHABLE!!!
md5: AC0171AD8010E54FDD7C25D33CA576B3
Empty SystemApp Flasher
NOTE: MUST place apks in the app folder within the system folder inside the zip file PRIOR to flashing
NOTE2: This is the same as what is linked in the Tweaked OP here - which is fine. This works on any blaze setup when using cwm recovery.
md5: F5B562DFCED08D8F55E5CF5EDF4DB444
Let me know if there are any problems! Also - it seems like general discussion should get pointed to here, as it's all the same thing really (read: I didn't think it warranted a new thread).

THANKS GO TO -
j3r3goss - initial letting folks know of i577 possibility and providing a link to a stock tar
2vivid and afoster1003 - bravely flashing said stock tar
thomas.raines - making things one-click easy, both to flash the rom and to return to gingerbread; helping with troubleshooting
2vivid and chjema - testing my attempts
erikmm - because I can
all of the folks in #teamfah-q
all of the folks in teamsbrissenmod, as I would know very little and be able to do even less if it weren't for them
-----------------------------
---CHANGELOG---
Final update - 10/2/12
- Somewhat fixed camera.apk
***** Viewer still appears upside down for rear camera, but all images/videos taken are correct orientation
- Changed stock boot animation
- Updated some apks
Initial Posting - 10/1/12
- Deodexed
- Took out lots of what I call bloat
***** If I took out something you wanted, use the links in the OP to get it back
***** If I left something you didn't want - let me know and I'll think about removing
- Added in SuperSU v0.96 by Chainfire (from here)
- Added busybox 1.19.4 (CM9)
- Edited Contacts.apk to avoid AT&T Subscriber checking when entering Contacts
- Added .bak to PowerOn.ogg in /system/etc/ to eliminate boot sound
-----------------------------
NOTES
Known issues:
1) Camera is upside-down
This only affects the rear-facing camera. The recent "fix" does not change the preview/viewer (the "live action" view of what the camera sees), but now all pictures or videos you take will be right-side up - so it's better than nothing I suppose
2) Softkeys/capacitive buttons no longer work
This seems to happen from time to time (though not very often by any means), in a way/manner that is as of yet predictable. That being said - all three times I have encountered this issue the below process has fixed it (thanks go to j3r3goss for providing the info needed for the solution):
- Open dialer/phone
- Type in the following in the dialer
*#*#2663#*#*
- Once the last * is entered, a new screen will show that has some information and (more importantly) two buttons. Press the BOTTOM buttom (the one that says "Touch key FW update"). Wait for this to complete (NOTE: This can take a LONG time, and you may have to reboot on your own if it hasn't said its completed its process after 10 or so minutes (my experience - no reasoning or logic behind it really, so be cautious)), then reboot the phone.
3) No WiFi Calling ability
Yep. It's an AT&T stock rom, and as they don't have the wifi calling capability, so too does this lack such fun functionality.

Reserved for something... not really sure what though. Figured I should grab it in case this little thing grows in the future - better safe than sorry I suppose.

confirmed flash good, no softkey issues
great job!

Good job man! Going to flash this tonight and make a 1 click for you with some Lightning Zap! goodies and modems (if it all works right...lol)...

saving this for later

Running great so far, definitely a lot snappier on first boot. No errors so far, glad the contact bug was fixed
There sure was a lot of bloat huh? I thought Tmo was bad lol.

Well I guess you beat me to it, way to go.
Sent from my SGH-T769 using xda app-developers app

I heard the radios were a little weak. Did you fix that in this file or is it the same?
Sent from my SGH-T769 using xda app-developers app

There are no radios included, so you keep whatever you had (and the blaze ones do seem a bit better than the exhilarate ones)

I just flashed, loving it btw, but my radios are a little weak? I factory reset, flashed the rom, factory reset again because it said to do so before reboot (idk I was a little paranoid lol) and then flashed system apps and boot.
Edit: i didnt realize earlier but all the bloat and such is remaining too? I'm gonna reflash in a bit and get back to you
Sent from my SAMSUNG-SGH-I577 using xda app-developers app

Push this apk to system to get weather working on lockscreen

WiFi calling should be able to be integrated into the ROM. It's not kernel specific, but might require some framework alterations. IMHO, it would be best to take this new ICS kernel and pair it with the OS from SGS2, that is made for T-mobile.
I haven't gotten a chance yet to look at the kernel to see if the flipped camera can be fixed there, or if just replacing it with the SGS2 camera app might do the trick.
Lots of opportunities for hacking together a great ROM from this.

Concerning the radios guys and gals!
It seems to be an ICS thing with the radios. We had the same issue on the SGS4G. They have to be padded in order to function properly since the SGS4G never got an official ICS update and we are still running on gb modem and kernel... Maybe Sammy will un-ass the update for us and all will be good...lol

thomas.raines said:
Concerning the radios guys and gals!
It seems to be an ICS thing with the radios. We had the same issue on the SGS4G. They have to be padded in order to function properly since the SGS4G never got an official ICS update and we are still running on gb modem and kernel... Maybe Sammy will un-ass the update for us and all will be good...lol
Click to expand...
Click to collapse
Yeah, I use to have a G2x with ICS and the developers always made it clear that the Radio issue is a problem with ICS 4.0.4 itself.
Sent from my SGH-T769 using xda premium

chjema said:
Push this apk to system to get weather working on lockscreen
Click to expand...
Click to collapse
how do you push it to the system? every time I try it just says it has failed

crazydrummer95 said:
how do you push it to the system? every time I try it just says it has failed
Click to expand...
Click to collapse
How are you trying to push, via root explorer (something alike) or adb?

thomas.raines said:
How are you trying to push, via root explorer (something alike) or adb?
Click to expand...
Click to collapse
Well, I tried using ES file explorer and it did not work. So I went into the root settings in the application, and I have everything checked, but when I try to mount the filesystem as writable, it says "failed to mount". I tried setting it as rw in adb, and it said it was a read-only file system

Es never worked for me with the root functions. Always has to use root explorer or adb
Sent from my SGH-T769 using xda app-developers app

skullreapper66 said:
Es never worked for me with the root functions. Always has to use root explorer or adb
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
But the problem is that everytime I try to push a file to /system in ADB it says that its a read-only file system

[Q] Moving dialer/phone app to stock rom (SOLVED)

I've been trying to take the phone apk and dialer from one rom and move it onto a stock rooted rom. I have accomplished this but when someone calls me the phone won't play a ringtone at all. So I have to run a nandroid restore on it. Can anyone tell me how to do this please? thank you in advance

Re: [Q] Moving dialer/phone app to stock rom
Which rom are you moving it from and to which rom?
sent from outer space.

Truckerglenn said:
Which rom are you moving it from and to which rom?
sent from outer space.
Click to expand...
Click to collapse
I am wanting the dialer and phone apk from the Aeon Rom and put it on my stock rooted rom found in xda-developers website thread here....
http://forum.xda-developers.com/showthread.php?t=1613523
************ OPTION C *************
I997UCLB3-CWM-root-deodex-extras.rar
Features in this version
- Entropy's Daily Driver kernel
- Red CWM recovery
- Rooted
- Deodexed
- Zipaligned
- Busybox
- AT&T and other bloatware removed
- Scrolling wallpaper fix
- CRT off animation
- 8 lock screens
- Extended power menu
- Accurate battery mod
- Get lidroid's 14 statusbar toggles HERE
Thank your for your time, effort and help in advance,
(Sorry for the edit) It might help and then again it may not. But I am using an AT&T Samsung Infuse 4g sgh-i997 rooted from gb 2.3.6 no modifications except what is found in option C above. and removing some stock libs.

oreo918 said:
I am wanting the dialer and phone apk from the Aeon Rom and put it on my stock rooted rom found in xda-developers website thread here....
http://forum.xda-developers.com/showthread.php?t=1613523
************ OPTION C *************
I997UCLB3-CWM-root-deodex-extras.rar
Features in this version
- Entropy's Daily Driver kernel
- Red CWM recovery
- Rooted
- Deodexed
- Zipaligned
- Busybox
- AT&T and other bloatware removed
- Scrolling wallpaper fix
- CRT off animation
- 8 lock screens
- Extended power menu
- Accurate battery mod
- Get lidroid's 14 statusbar toggles HERE
Thank your for your time, effort and help in advance,
(Sorry for the edit) It might help and then again it may not. But I am using an AT&T Samsung Infuse 4g sgh-i997 rooted from gb 2.3.6 no modifications except what is found in option C above. and removing some stock libs.
Click to expand...
Click to collapse
you may need dialer.apk, phone.apk and maybe contact.apk.
after you move them, set the correct permissions.
reboot.
if that doesn't work, may need to boot into cwm and wipe cache and dalvik.
alternate: you can try using titanium back up..remove those apk and then install the other apks from the myfiles

qkster said:
you may need dialer.apk, phone.apk and maybe contact.apk.
after you move them, set the correct permissions.
reboot.
if that doesn't work, may need to boot into cwm and wipe cache and dalvik.
alternate: you can try using titanium back up..remove those apk and then install the other apks from the myfiles
Click to expand...
Click to collapse
Ok. cool. But when i move them the phone starts to force close like crazy. I move them directly to /system/app/ and replacing the current apps. I didn't move just those apps tho. I also moved phone_Util.apk and PhoneSetupWizard.apk DialerTabActivity.apk and it worked but when someone would call me it wouldn't ring.
So my question is this. Do I just cut/past the ones you just described above to /system/app/ and then fix permissions ignoring FCs to rw-r-r. And reboot. Is that correct?
Thank you for your time. And quick response.

oreo918 said:
Ok. cool. But when i move them the phone starts to force close like crazy. I move them directly to /system/app/ and replacing the current apps. I didn't move just those apps tho. I also moved phone_Util.apk and PhoneSetupWizard.apk DialerTabActivity.apk and it worked but when someone would call me it wouldn't ring.
So my question is this. Do I just cut/past the ones you just described above to /system/app/ and then fix permissions ignoring FCs to rw-r-r. And reboot. Is that correct?
Thank you for your time. And quick response.
Click to expand...
Click to collapse
yeah..just work thru the FC's.
you can also use abd and have no fc issues.
if you are running a rom, you can make those changes to the rom before flashing...either way.
make sure you have a back up of your current set up...zen tool kit allows for a whole rom back up

qkster said:
yeah..just work thru the FC's.
you can also use abd and have no fc issues.
if you are running a rom, you can make those changes to the rom before flashing...either way.
make sure you have a back up of your current set up...zen tool kit allows for a whole rom back up
Click to expand...
Click to collapse
Well I did it like you said worked thru the force closing and changed the permissions of all 3 apks (Contacts.apk DialerTabActivity.apk, Phone.apk)
to rw- r-- r-- is how each apk's permission were then I rebooted the phone. The volume is up and the ringtone is set. But when I call my phone from a different phone it does not ring, and at the bottom of the screen will blink Unknown between the green and red answering/ignore button on screen., even though above that. The picture for the contact calling the cell phone shows up and so do the Name as inputted into phone contacts. I don't know what i'm doing wrong, please help me out if you know what I am doing wrong. Thank you for your time

oreo918 said:
Well I did it like you said worked thru the force closing and changed the permissions of all 3 apks (Contacts.apk DialerTabActivity.apk, Phone.apk)
to rw- r-- r-- is how each apk's permission were then I rebooted the phone. The volume is up and the ringtone is set. But when I call my phone from a different phone it does not ring, and at the bottom of the screen will blink Unknown between the green and red answering/ignore button on screen., even though above that. The picture for the contact calling the cell phone shows up and so do the Name as inputted into phone contacts. I don't know what i'm doing wrong, please help me out if you know what I am doing wrong. Thank you for your time
Click to expand...
Click to collapse
Explain to me what you are trying to do.
Which ROM are you currently running, kernel, root?, odex or deodex? Voodoo (ext4) or stock partition?
It is likely that if you are running simple root stock, with non-voodoo stock kernel, and adding a deodex apk to the mix, the stock kernel may not be able to use the deodex files. you may need to change kernel, or re-odex the apk you are trying to port. Remember, most apk's on the rooted stock has 2 file components.
You can try using the stock deodex base dman made as a base of work from there.
If you are only interested in the appearance of the rom, use 7zip and extract the png's from the apk you want and just paste it into the odex system files to get the same look.
In essence, I think you are trying to theme the stock rom or cook your own.
check here for themes
http://forum.xda-developers.com/forumdisplay.php?f=527

qkster said:
Explain to me what you are trying to do.
Which ROM are you currently running, kernel, root?, odex or deodex? Voodoo (ext4) or stock partition?
It is likely that if you are running simple root stock, with non-voodoo stock kernel, and adding a deodex apk to the mix, the stock kernel may not be able to use the deodex files. you may need to change kernel, or re-odex the apk you are trying to port. Remember, most apk's on the rooted stock has 2 file components.
You can try using the stock deodex base dman made as a base of work from there.
If you are only interested in the appearance of the rom, use 7zip and extract the png's from the apk you want and just paste it into the odex system files to get the same look.
In essence, I think you are trying to theme the stock rom or cook your own.
check here for themes
http://forum.xda-developers.com/forumdisplay.php?f=527
Click to expand...
Click to collapse
I used Odin to flash Option C found here
http://forum.xda-developers.com/showthread.php?t=1613523
Which is Deodexed / Rooted / With Entropy's Daily Driver Kernel. I don't much about the partition stuff yet. Just started to scratch that surface. But i haven't messed with it. I know I have voodoo lagfix in the RED CWM recovery and it did say something about partition when i flashed the rom I can never understand what the chick says tho. But I have not altered it from the file you can download from that thread above. Except for uninstalling a bunch of stock libs.
I am trying to to get the phone app or the dialer setup i guess you can say from the Aeon Rom 1.4 because I can't figure out how to save the Facebook sharing options. via gallery/share/facebook sharing photos and what not. So I went with the stock rom and flash the Lidroid 14 toggle mod. and removed the logsprovider.apk with the modded one found in the same thread with option c in matter of a fact.
Are you saying though that I can unzip Phone.apk and DialerTabActivity.apk here in my PC and take the png?? and paste them to where exactly? I'm sorry I am trying to learn this stuff and It can be very frustrating at times because I am still super new to putting my own rom together. I just want the AEON rom dialer because it has that convenient message tab next to the call tab in the dialer so I want that and the phone to actually ring when someone calls me too.
Thank you for your patience qkster. I still can't believe that you have replied to my thread yourself. I have followed your posts and threads and advice for a long time. I appreciate all your hard work and what not that make ideas likes this possible. YOU ARE THE MAN!!!! lol.
Thank you for your time I hope this was detailed enough for you to get the idea i'm trying to project.

oreo918 said:
I used Odin to flash Option C found here
http://forum.xda-developers.com/showthread.php?t=1613523
I am trying to to get the phone app or the dialer setup i guess you can say from the Aeon Rom 1.4 because I can't figure out how to save the Facebook sharing options. via gallery/share/facebook sharing photos and what not. So I went with the stock rom and flash the Lidroid 14 toggle mod. and removed the logsprovider.apk with the modded one found in the same thread with option c in matter of a fact.
Are you saying though that I can unzip Phone.apk and DialerTabActivity.apk here in my PC and take the png?? and paste them to where exactly? I'm sorry I am trying to learn this stuff and It can be very frustrating at times because I am still super new to putting my own rom together. I just want the AEON rom dialer because it has that convenient message tab next to the call tab in the dialer so I want that and the phone to actually ring when someone calls me too.
Click to expand...
Click to collapse
you are finding out what I consider theory, execution and practice.
in theory, it should work.
execution may not result as intended
practice makes perfect
Couple of issues:
1. you're running jesse's uclb3 rooted with extras. great. it's in an odin format, not a cwm. unfortunately it's not in cwm flashable zip.
you can create one if you google how to make a cwm flashable rom from stock leak.
if you can follow a complex set of instructions, go can try it here: http://forum.xda-developers.com/showthread.php?t=1484578
(Jesse also made this: http://forum.xda-developers.com/showthread.php?t=1711375
essentially the some odin option c you used. (he made that in odin for flash via download mode for borked phones)
his ethereal is essentially the same, meant to flash in RED cwm. except for his themes and sound options similar to sgs3.
the odin option c is essentially stock uclb3)
2. before you do anything, make a back up of your current desired setup with zen tool kit - so you can restore in event of boot loops.
3. have the apk with the icons you want on your pc desktop. use 7 zip. double click into the apk. go to res. go to drawable-hdpi. copies all the png. make a new temp folder on your desktop. call it what you want. paste the copied png into the temp folder and look at in windows, with thumbnail options. you will see the icons you want as it may appear in the rom.
4. pull out the apk of the rom you are running. put it on your desktop. look in it also. using 7zip, pull out the res/drawable-hdpi/ folder onto desktop. if you look in it, you will see the other png that you may no longer want. there are several ways to replace the ones you want but it's easier just to pull all the pngs you want into the drawable-hdpi on the desktop and bring the folder over into the apk or just paste them into the apk's /res/drawable-hdpi/
then flash the modded apk or push it into system
Use this for adb..it's easier to use
http://androidforums.com/esteem-all-things-root/517688-adb-android-commander.html
alternatively:
attached is a cwm-flashable shell...study it with 7zip. look at the updater-script. see what it does.
then put the modded apps into the /app folder and flash.
this can be use to flash framework apk/jar and/or system/app apk
test jesse's ethereal and aeon or any other. mix and match. with zen tool kit restore rom, you want play around and restore it back to where you left off
you can also try just pull the aeon apk into the shell and flash it again
remember too that each dev may have different setup or framework that may not let each apk interact correctly...until you have the right combo of files

qkster said:
you are finding out what I consider theory, execution and practice.
in theory, it should work.
execution may not result as intended
practice makes perfect
Click to expand...
Click to collapse
Thank you very much qkster. I really appreciate your help on this issue. I will be studying these threads and this Android Commander and getting to learn all I can about it. I have followed your posts for awhile and believe you are a very talented developer. I for one appreciate all of your hard work on the Samsung Infuse 4g and insight and advice that you offer.
I'm not gonna just jump right into it, I like to uderstand it all first. But I will definitely be looking this over and trying to absorb it all.
You have kept me busy for probably the next week with this one. Thank You again kind sir. I will let you know in the next day or so to be more realistic as to my progress and if I encounter any problems. Too Bad You don't have a | +1,000,000 THANKS | Button.

oreo918 said:
Thank you very much qkster. I really appreciate your help on this issue. I will be studying these threads and this Android Commander and getting to learn all I can about it.
I'm not gonna just jump right into it, I like to uderstand it all first. But I will definitely be looking this over and trying to absorb it all.
You have kept me busy for probably the next week with this one. Thank You again kind sir. I will let you know in the next day or so to be more realistic as to my progress and if I encounter any problems. | Button.
Click to expand...
Click to collapse
you're welcome.
(btw, i thank you for the compliment but i'm not a dev in the true sense. i can re-using and re-applying what is already out there.)
android commander is a graphic ui for adb..easier to use. you'll see that you can pull/push apks much easier, reboot, etc..
as far as learning ...read as much as your brain can handle and google what info you need...that's how most of us picked up this stuff..gl

Re: [Q] Moving dialer/phone app to stock rom
qkster said:
you're welcome.
(btw, i thank you for the compliment but i'm not a dev in the true sense. i can re-using and re-applying what is already out there.)
android commander is a graphic ui for adb..easier to use. you'll see that you can pull/push apks much easier, reboot, etc..
as far as learning ...read as much as your brain can handle and google what info you need...that's how most of us picked up this stuff..gl
Click to expand...
Click to collapse
I used that program you posted "android commander" and extracted a custom Rom to my PC and then using Android Commander I pushed phone.apk dialertab.apk and camera.apk over to my phone and everything it's working fine. Although I had to change permissions to rxw-rxw-r-x
Instead of rw,r r. But it's all doing fine so far. Phone will ring. Camera takes pictures with the power button and I got my dialer tab wanted. Thank you again man. I appreciate you for real.
Sent from my SAMSUNG-SGH-I997 using Tapatalk

Hey qkster,
I have one more question if you don't mind. Where would i find the File that contains the png's for the notification bar/toggles? I would like to change that stuff around as well and see if I can change the colors and toggle images? Just need to know where to find the file containing those png's

look in:
systemui
settings
frameworks-res
there are several areas...
check the main xda android theme sections
make a revert or backup..once you start playing with settings, systemui and framework-res, you might experience boot loops
use the cwm-shell i posted. put the original working files in the correct location..call it revert...put the experimental files in another shell copy, and call whatever..

Hey qkster ever since I moved those files. that i posted in my last post my text messaging has been acting up. Every once in awhile. I finally narrowed it down to the problem being if the text is too long it fails to send the text message is there a way to fix this while at the same time keeping my alterations I have made to the rom?

oreo918 said:
Hey qkster ever since I moved those files. that i posted in my last post my text messaging has been acting up. Every once in awhile. I finally narrowed it down to the problem being if the text is too long it fails to send the text message is there a way to fix this while at the same time keeping my alterations I have made to the rom?
Click to expand...
Click to collapse
prolly your modem..not your mods
http://forum.xda-developers.com/showthread.php?t=1342978

Re: [Q] Moving dialer/phone app to stock rom
qkster said:
prolly your modem..not your mods
http://forum.xda-developers.com/showthread.php?t=1342978
Click to expand...
Click to collapse
What do ya know ? You were right again. Lol. Thank bro your awesome.
Flashed uclb3 & that fixed. Thanks again
Sent from my SAMSUNG-SGH-I997 using Tapatalk