Related
Hello everybody,
I´ve got a Rogers Captivate i896 with Firmware version 2.2 (stock Rogers firmware(Canada), flashed 1 year ago, upgrading from 2.1 stock)
Kernel version 2.6.32.9
Modem version UXJL1
Rooted, unlocked and 1 click Lagfix
I´m on Rogers network.
Problems:
1) Many applications stop working once updated. IM+ version 4.xx works, anything higher crashes on start. Same story happens with LOTS of apps from Playstore, so I´m forced to be careful when updating apps. This is becoming super-annoying.
2)Recently, installed DROIDVPN and TUN.KO installer to use Dell voice on an Unlimited Mobile Browsing plan(crippled data for WAP browsing). It worked beautifully for 1 day, now starting DROIDVPN or TUN.KO makes the phone restart.
3)I´d like to get rid of built-in garbage, most of which I do not use, to have more control over running apps, especially those that hang themselves into start-up.
4) I´d like to get better battery life. I use my phone more and more, I´ve got 2 batteries and and external charger, and yet i sometimes have trouble getting to the end of the day without my phone dying/I]
Solutions.
I imagine that the only explanation for apps that simply refuse to work is that they are designed for newer Android systems. This happened with Skype that didn´t work with Eclair, but does work with 2.2.
Should I upgrade to ICS?
I have some experience flashing, yet I´m far from an expert. What´s the most fail-safe plan of actions? Would the following work:
1)Backup everything using TitaniumBackup
2)Install custom bootloader that would allow me to flash install.zip from external SD card
3)Choose a custom ROM based on user feedbacks, like Cyanogen MOD.
4)Restore all the apps
5)Experiment with different modem firmware to see which gives me best performance
I no longer have time to tinker around in the dark, so I´d like to have a plan before I get started. Any input on the possible solutions to the problems I´m experiencing?
Thank you in advance.
All the info you need on how to flash (specific to Canadian / Rogers version of Captivate):
http://forum.xda-developers.com/showthread.php?t=1350266
Modems for specific region:
http://forum.xda-developers.com/showthread.php?t=1227717
Just a question: why haven't you upgraded to Rogers official GB?
And BTW, ICS is a massive improvement over 2.1, 2.2 and 2.3.
I have a great experience with this ICS Rom:
http://forum.xda-developers.com/showthread.php?t=1522881
But there are others that are just as good I'm sure.
My 2 cents:
Stay away from ICS. It has the ability to damage your SD card.
Use this post to upgrade to gingerbread. Then use the utility in my signature to get root and cwm. Then choose a GB based ROM that suits your needs. May I suggest Legend?
¨Use this post to upgrade to gingerbread. Then use the utility in my signature to get root and cwm¨
Wouldn´t it be wiser to get clockwork mod before any upgrading just in case things go bad? I vaguely remember using clockworkmod last time I dealt with flashing, isn´t it a loader that allows you to load install.zip from SD card? Or would flashing a new system wipe out the mod as well?
How exactly can ICS damage SD card. Are you talking about the external SD or the built-in SD storage in the phone?
I´ve read partially the threads on Legend and Android Open Kang Project - captivatemtd - Milestone 6. Both sound pretty good. As far as you guys know, which rom is known to give best battery life?
If you're going to upgrade to a custom rom that is Gingerbread or Higher, you will need the Gingerbread bootloaders. That is why I say to go to stock Gingerbread first.
ICS can cause the Encryption Unsuccessful bug as seen here. It will cause you to lose all access to the built-in SD storage. It doesn't happen to everyone, but when it does, you'll wish you had heeded my advice.
I am looking to flash my phone to ICS/Jelly Bean and have some questions.
1. Does updating to those ROMs impact multitasking? I wonder because they probably eat up a lot more RAM and when I use browsers, I tend to open a lot of tabs which is heavy on RAM usage
2. Is there a performance difference between JB and ICS on the Cappy?
3. Should I go with a built-in kernel or flash a separate one?
4. My phone has never had its kernel changed, same default filesystem, lag etc. etc., should I do anything extra before flashing?
5. I read on another post on the front page that the JB/ICS ROMs also use the internal SD card, mine is mostly full at the moment, how much space do the new ROMs take up?
Thanks for any help. Been considering flashing for a year but my phone recently got the lock screen button stuck problem and now I'm at a crossroads, either I buy a new phone entirely or maybe try to keep this one for a year until my contract runs out and deal with the lock screen problem.
skomes said:
I am looking to flash my phone to ICS/Jelly Bean and have some questions.
1. Does updating to those ROMs impact multitasking? I wonder because they probably eat up a lot more RAM and when I use browsers, I tend to open a lot of tabs which is heavy on RAM usage
2. Is there a performance difference between JB and ICS on the Cappy?
3. Should I go with a built-in kernel or flash a separate one?
4. My phone has never had its kernel changed, same default filesystem, lag etc. etc., should I do anything extra before flashing?
5. I read on another post on the front page that the JB/ICS ROMs also use the internal SD card, mine is mostly full at the moment, how much space do the new ROMs take up?
Thanks for any help. Been considering flashing for a year but my phone recently got the lock screen button stuck problem and now I'm at a crossroads, either I buy a new phone entirely or maybe try to keep this one for a year until my contract runs out and deal with the lock screen problem.
Click to expand...
Click to collapse
1. In my experience multitasking isn't a problem on either but I don't open a lot of tabs in my browser so could be different for you.
2. If you want good clean performance go with ICS. Jelly Bean roms are still more or less in beta.
3. As far as kernels go stick with the kernel built into the from unless it instructs you otherwise. Or if you are looking for some feature that one kernel offers that another doesn't.
4. Read, read, and then read the instructions again for whatever rom you are going to and follow them. Depending on where you are starting from you may have to do different things.
5. I've personally never paid attention to how much it uses the internal SD if at all. I do know that some ICS and Jelly Bean roms have potential to format your SD card during the flash so make sure you do a backup before moving forward.
When you say the lock screen are you talking about the power button? If yes be very careful moving forward with any flashing. I say that because the power button is used to put the phone into recovery. There are other methods to get into recovery but they don't work for everyone.
Sent from my SGH-I897 using xda app-developers app
m1batt1 said:
1. In my experience multitasking isn't a problem on either but I don't open a lot of tabs in my browser so could be different for you.
2. If you want good clean performance go with ICS. Jelly Bean roms are still more or less in beta.
3. As far as kernels go stick with the kernel built into the from unless it instructs you otherwise. Or if you are looking for some feature that one kernel offers that another doesn't.
4. Read, read, and then read the instructions again for whatever rom you are going to and follow them. Depending on where you are starting from you may have to do different things.
5. I've personally never paid attention to how much it uses the internal SD if at all. I do know that some ICS and Jelly Bean roms have potential to format your SD card during the flash so make sure you do a backup before moving forward.
When you say the lock screen are you talking about the power button? If yes be very careful moving forward with any flashing. I say that because the power button is used to put the phone into recovery. There are other methods to get into recovery but they don't work for everyone.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
I guess that is a good point. My lock screen buttons works but not 100% of the time. Originally the problem hit and it didn't work at all, now it works probably 70% of the time. I didn't remember that I would need it to get into recovery. Maybe I would need to buy a jig, but I guess I should flash now in case it stops working entirely down the line.
I'm also considering buying an S3 but it is quite expensive, at least $620 for it unlocked.
I had wanted to jump into JB because I was looking for decent performance and I don't think I'll be flashing a ton. I've got like 80 apps, tons of home screen stuff etc. that I don't want to restore many times. I just figured if JB is faster, I'd rather go with it.
Thanks for the helping me out.
A jig isn't the best bet because it forces it into download mode. If your button is currently working go for it. Jelly bean roms will eventually be the best thing out there but most of the roms for it haven't been perfected yet.
I have been on everything from 2.1 and up and I can tell you ICS is the best stable thing out there. At least in my opinion.
Sent from my SGH-I897 using xda app-developers app
skomes said:
I guess that is a good point. My lock screen buttons works but not 100% of the time. Originally the problem hit and it didn't work at all, now it works probably 70% of the time. I didn't remember that I would need it to get into recovery. Maybe I would need to buy a jig, but I guess I should flash now in case it stops working entirely down the line.
I'm also considering buying an S3 but it is quite expensive, at least $620 for it unlocked.
I had wanted to jump into JB because I was looking for decent performance and I don't think I'll be flashing a ton. I've got like 80 apps, tons of home screen stuff etc. that I don't want to restore many times. I just figured if JB is faster, I'd rather go with it.
Thanks for the helping me out.
Click to expand...
Click to collapse
I've run a rooted 2.2, a rooted 2.3.5, and a few different ROM's, I find that the easiest to use so far is JB, depending on the ROM itself you may run into a few issues with battery drain, but it's not horrible. Multitasking is fine, but I have OS monitor and a RAM booster for quick mem clearing. The only problems that I've ran into with JB ROM's is that you have make sure the internal memory card is backed up, otherwise you'll lose everything you have on it.
I too have thought about getting a SG3, but after flashing the JB ROM, I think I'm satiated until I absolutely have to upgrade my phone.... meaning I'm probably going to stick with this one for another year or so depending on if I'm able to keep it in decent enough shape. For the CM10 ROM's, they've removed the /datadata folder so that may affect slight performance. I got used to it after flashing a ROM that kept the /datadata folder and noticed that it wasn't giving me enough space to work my usual programs on a consistent basis. But overall I'm content with the ROM I chose and the performance so far.
You can always do adb reboot recovery
Sent from a jelly bean
korockinout13 said:
You can always do adb reboot recovery
Click to expand...
Click to collapse
That is true but adb wouldn't help him much if he's stuck in a boot loop. That's when a functioning power button is important.
Sent from my SGH-I897 using xda app-developers app
skomes said:
I am looking to flash my phone to ICS/Jelly Bean and have some questions.
1. Does updating to those ROMs impact multitasking? I wonder because they probably eat up a lot more RAM and when I use browsers, I tend to open a lot of tabs which is heavy on RAM usage
Click to expand...
Click to collapse
According to my expirience, ICS much better in multitasking, comparing with GB. ICS kernel consumes less RAM and more stable.
skomes said:
2. Is there a performance difference between JB and ICS on the Cappy?
Click to expand...
Click to collapse
JB for cappy is not stable yet.
skomes said:
3. Should I go with a built-in kernel or flash a separate one?
Click to expand...
Click to collapse
If you a going to install CM or AOKP, you defiantly have to install custom kernel. You will also have to install custom baseband (modem). I suppose, same goes to other roms.
skomes said:
4. My phone has never had its kernel changed, same default filesystem, lag etc. etc., should I do anything extra before flashing?
Click to expand...
Click to collapse
Yes. RTFM for the rom you are going to flash. You will have to wipe data and cache, and maybe update bootrom.
I am reading stuff, but a lot of guides say 'Coming from GB' BUT they DO NOT say 'coming from stock', so I wasn't sure if those guides were applicable.
Will CM10 wipe my SD card?
Thanks for all the help so far. Going to flash within a couple of days.
I was figuring Helly Bean but most of the JB roms want you to flash CM10 first anway, so I'll try that out.
^
See TRusselo's Flashin Guide for assistance... http://forum.xda-developers.com/showpost.php?p=19425513&postcount=1
Sent from my SAMSUNG-SGH-I777 using xda premium
Tried following that guide.
Heimdall links are all dead.
Opened Odin, downloaded speedmod kernel, figured I'd install it, then download the rom to SD card and go. I was pretty sure speedmod works with stock Captivate.
Flashed speedmod and now my phone is stuck on the Galaxy S boot screen.
So yeah...that sucked.
Now I'm trying to restore stock with Odin but the instructions don't even say how.
Yeah this is why I don't see myself flashing very often...
And that guide needs more detail.
Ok, well I managed to install CM9.
I'm going to stick with it for now because a couple of you guys warned me off of Jelly Bean.
skomes said:
Ok, well I managed to install CM9.
I'm going to stick with it for now because a couple of you guys warned me off of Jelly Bean.
Click to expand...
Click to collapse
I'm currently on the 8/13 nightly build of Helly Bean (http://forum.xda-developers.com/showthread.php?t=1783064)
I can say that this particular ROM is ready for use as a daily driver. I've been using it for about a week now and haven't experienced any problems.
With that said, it is important to note that as said before, JB roms are still in beta, including this one. Also it is important to say that I did a completely clean install of this particular ROM (Factory data reset, wiped cache, wiped dalvik cache, etc).
Just thought I let ya know that not all JB roms are scary right now. If you're interested in possibly flashing it, here's the official website: http://hellybean.site11.com/index.html
Don't forget to backup your /EFS folder though, recently some people have had problems with their imei being switched, but this is easily avoidable if you take the proper precautions. Other than that, this ROM is great.
Yeah, I actually mentioned Helly Bean on page 1, it was the JB rom I was considering because it was getting rave reviews.
I had a scare last night about my IMEI then I remembered my IMEI doesn't match my box because it was warranty replaced with a refurb for the shutdown issue, lol, I was freaking out but good thing is it made me backup the EFS folder.
Thanks for the support.
I'll give Helly Bean a try in a bit, I hear it is very snappy and I'm excited about that, coming from stock Gingerbread, I really appreciate an OS that doesn't run like crap!
Does Helly Bean wipe your internal SD card? I was searching for that and couldn't find anything, so I think that means no, but wanted to make sure!
skomes said:
Does Helly Bean wipe your internal SD card? I was searching for that and couldn't find anything, so I think that means no, but wanted to make sure!
Click to expand...
Click to collapse
As with any custom ROM there is a potential for odd things happening on one phone that doesn't happen on another. With that being said I flashed helly bean and it didn't format my SD card nor has it effected my efs folder like some people have had trouble with.
Your best bet is to backup everything important to you and the operation of your phone prior to flashing just to be safe.
Sent from my SGH-I897 using xda app-developers app
Backup your efs folder before flashing anything
A few questions before I try Helly Bean, I noted that the kernel is separately available on the download site, am I supposed to flash it separately or is it included with the ROM? The flashing guide doesn't say anything about flashing a kernel.
And I should be able to flash it directly from CM9, correct?
Also this ROM is a lot bigger than CM9, 180MB vs 300MB, does that mean I have far less internal SD space available?
skomes said:
A few questions before I try Helly Bean, I noted that the kernel is separately available on the download site, am I supposed to flash it separately or is it included with the ROM? The flashing guide doesn't say anything about flashing a kernel.
And I should be able to flash it directly from CM9, correct?
Also this ROM is a lot bigger than CM9, 180MB vs 300MB, does that mean I have far less internal SD space available?
Click to expand...
Click to collapse
Answering my own questions in case other people need help.
Yes
Yes
No
I installed Helly Bean but for me, it is laggier than CM9 so I am disappointed.
I just ordered a recertified Verizon 3G Xoom, and I didn't think about the implications of it being a Verizon device. This is NOT upgraded to 4G LTE -- will the "Stingray" builds of the various ROMS still work? Is there any way to apply WIFI-only ROMS (including stock) if I don't care about the 3G working? Given the age of the device I really want to get Jelly Bean on it.
I will need to cancel this order ASAP if the answers to these questions turn out to be "no"...
Same question from me.
Can we install the WiFi only version of ROMs (CM9 in particular) onto a Verizon 3G Xoom and have it work for everything EXCEPT the 3g? I could honestly care less about ever activating it on Verizonas long as WIFI works.
trunzoc said:
Same question from me.
Can we install the WiFi only version of ROMs (CM9 in particular) onto a Verizon 3G Xoom and have it work for everything EXCEPT the 3g? I could honestly care less about ever activating it on Verizonas long as WIFI works.
Click to expand...
Click to collapse
From reading a bit in the Development sub-forum, it looks like there's a JB leak for the VZW version, and either version (WIFI Only or VZW) of the EOS 3 ROM should work. I think I will keep my order.
magnafides said:
From reading a bit in the Development sub-forum, it looks like there's a JB leak for the VZW version, and either version (WIFI Only or VZW) of the EOS 3 ROM should work. I think I will keep my order.
Click to expand...
Click to collapse
Thanks. I'm placing my order as soon as Wife says OK. If you don't mind, and if you remember, please send me a PM of how it goes with the flashing once to get yours.
Would love to coordinate what we do since there doesn;t seem like a whole lot of certainty exists about what we are trying to do.
I'm probably just going to flash the EOS 3 WIFI Only version. According to one of the devs, it should work fine:
http://forum.xda-developers.com/showpost.php?p=28578030&postcount=8
But I will try to remember to let you know how it goes.
magnafides said:
I'm probably just going to flash the EOS 3 WIFI Only version. According to one of the devs, it should work fine:
http://forum.xda-developers.com/showpost.php?p=28578030&postcount=8
But I will try to remember to let you know how it goes.
Click to expand...
Click to collapse
Any luck? I also have a Xoom 3G MZ600 on the way and could careless about 3G...
hasnt eos got jellybean roms for all versions of the xoom? 3g should work imo
Sent from my Xoom using XDA Premium App
I'm in the same boat and curious to see if anybody has any words of wisdom. I love my refurbed Xoom 3G but am eager to get JB on it. Any help is greatly appreciated.
FWIW everything I have heard/read seems to indicate that it is possible to flash WiFi only ROMs on the 3G Xoom, and apparently everything will work fine except for the 3G (naturally). I haven't taken the plunge yet myself, still running stock ICS.
Is there any word on whether the Verizon 3G Xoom will get Jelly Bean?
It can be done....
I purchased a used 3g Xoom around Apr 2012. After initially unlocking / rooting and installing a ROM (EOS) on my 3g Xoom, the 3G radio wasn't working so I started fresh. I locked the device and SBF'd the original Xoom firmware, then used the official over the air (OTA) upgrades to get back to stock ICS. I thought this might fix the 3g issue; it did nothing.
EOS Roms overclock the GPU by default, which caused problems with my (and my wife's Wifi version) Xoom. My only requirements for a ROM are stability, no clutter from dumb carrier installed applications, compatibility, and of course root access. I found a pre-rooted stock Jellybean rom, but it was for the Wifi Xoom. It worked great on my wife's though; and heard rumors that it could work with mine.
*SO*...I took a leap of faith and installed it. It works great. No 3g radio of course, but I gave up on trying to get that to work anyway...so if you don't care about losing your 3g , this will probably work for you. I don't think my 3g will ever work, but I suspect this won't ruin yours if it is currently working. Don't hold me to that; this is a risk.
Random notes and refresher info:
-you will need an SD card. I'm pretty sure the following instructions will only work if you use one.
-If at any point you get the android guy with an orange exclamation point during boot...it is probably ok, just let it sit there for a couple minutes. it should continue to boot into whatever ROM you are currently on. Make sure you enable usb debugging in settings after boot.
-to access RSD, Recovery, or Fastboot mode, press and hold your power button to start the Xoom booting. When you see the Motorola logo, wait a second then press the volume down button. Then you can use volume down again to cycle through your options, and use volume up to choose one.
-the exact differences between RSD / Fastboot and Recovery modes are beyond the scope of this post (and me) so just know that your Xoom can be modified using software on your PC via USB with RSD and Fastboot modes, and stock recovery can be replaced with modified versions to add more functionality. Recovery is used to do all sorts of things...flash Roms, mount drives, format, cleanup caches, etc.
***
General instructions. Just guidelines; you will probably need some previous experience with computers / rooting etc.
(If you are already unlocked, rooted, and have a replacement recovery, skip to the last step.)
1.) Follow this guide to prep your Xoom: (unlocking, rooting, and install CWM recovery)
http://www.xoomforums.com/forum/motorola-xoom-development/15179-how-rookie-rooting-flashing-unrooting-under-one-roof.html
Note: you may have heard of Lord AOI tool; it is supposedly designed to simply the above process. I found it didn't work well and was more difficult to use than good ol' adb commands. I recommend skipping it.
2.) OPTIONAL: Next, I recommend using the latest Rogue recovery. Just use standard CWM recovery to flash it. It is nice because it allows you to use the touchscreen to manipulate instead of having to use the hardware buttons (volume buttons are kind of a pain). See here: http://forum.xda-developers.com/showthread.php?t=1235170
3.) Finally, flash the pre-rooted stock Jellybean ROM. See here: http://forum.xda-developers.com/showthread.php?t=1796335
(here's the direct ROM link for those not needing instructions or extra info: http://www.mediafire.com/?7w5w65l66hgggo8 )
Good luck and let us know your results...
So My old Atrix 2 got sold to my buddy for his mom. I got a new one and installed Leak #1, lapdock audio working great and lapdock battery options are available! Problem is I badly want to try some other ROMs to test lapdock audio. If I do a backup using bootstrap can I restore to it from say SCV7?
Jimbridgeman stated in one of my posts that devs can't add options that don't already exist in some form to custom ROMS. I'm still wondering what ever happened to the battery options I now have in leak #1 No other ROM I have tried, and I believe I tried all atrix 2 ROMs based on ICS and above, at least all available here.
Anyone on Leak #1 knows you can check your lapdock battery level and have options regarding whether it charges your phone or not.
I can take or leave the battery options, it's just why wouldn't you want them, my real deal is I want a better ROM but I do not want to lose lapdock audio again, and from what I understand it's best not to attempt to go back to the leak once another ROM is flashed.
I tried loading scv7 on system 2 last time (first phone/leak install) but had a low memory issue, not enough memory to install apps to internal memory.
Sorry for the long post, I just didn't know a shorter way to explain exactly what I want, which is, a safe way to try other ROMS without losing to option to use leak #1. I guess that's a shorter way lol.
So I can't do a full backup using recovery, flash another rom, then restore the leak #1 backup later right? There has to be a way to create a restore able backup image of my phone as is. Maybe it's time to learn more about development myself and create my own rom based on leak 1.
You can backup with Bootmenu Manager (BMM) and restore with either that or a CM10-based recovery (and vice-versa).
If you backup with the A2 Bootstrap, then ONLY use that to restore.
--DO NOT INSTALL BMM OR A2 BOOTSTRAP ON CM10-BASED RECOVERY (CM10, MagicMod, future ROMs)--
Also, if you are on leak#1 then you can always take the long route back by flashing the leak#1 fxz to GB, then update to leak#1 again... but I'm sure all the lapdock stuff works the same in leak#1 and the final OTA..
Sent from my phone's mind
alteredlikeness said:
You can backup with Bootmenu Manager (BMM) and restore with either that or a CM10-based recovery (and vice-versa).
If you backup with the A2 Bootstrap, then ONLY use that to restore.
--DO NOT INSTALL BMM OR A2 BOOTSTRAP ON CM10-BASED RECOVERY (CM10, MagicMod, future ROMs)--
Also, if you are on leak#1 then you can always take the long route back by flashing the leak#1 fxz to GB, then update to leak#1 again... but I'm sure all the lapdock stuff works the same in leak#1 and the final OTA..
Sent from my phone's mind
Click to expand...
Click to collapse
Thanks, so it's safe to restore a backup even if you aren't on the rom you were using when you created it. I did use bootstrap, so I should un install and then use safestrap to create another. Also, last time I fxz'ed to ota I didn't see the battery options and lost audio on the lapdock(but not non lapdock webtop via hdmi)
The first rom I tried after the leak was scv7 but had entitlement issue, which I fixed but somehow lost home button function, audio never worked again via lapdock, even after fxz to ota (necessitated by a bad Numa flash)
So, I'm buying this to replace my evo 4g and I was wondering how I would go about using a custom ROM for this and having the apns and data working correctly.
I plan to activate it on Ting.
To be a bit clearer, I want to use a custom ROM and I want to be sure that it'll work. So first, can anyone on Ting confirm that they're running a custom ROM (preferably KitKat) with no problems?
And I assume I'd have to activate the phone first, then install a custom ROM. Would I have any problems doing that? Would the apns be messed up? Or should everything be fine as long as I activate the phone and update everything on stock before installing a ROM? Reason I ask is because I know some Roms don't allow the *#*# thing needed to activate a phone on a new network.
Thanks!
I am using mine on Ting. I had used my first Q as unrooted stock JB, which worked pretty well for a year, but then it reached a near--bricked state where it wouldn't boot past the yellow Sprint screen. I couldn't resolve this in a timely fashion, so wound up buying a second Q which runs stock ICS, but failed to download the stock JB update.
In the meantime, I unlocked both phones' bootloaders, and tried a few kItkat ROMs on my original phone before settling on CM 10.2, which is a JB ROM. I then switched my Ting activation (back) to this phone. The lack of #*# commands isn't really a problem with respect to re-activation, but it is a problem with respect to PRLs and (perhaps) APNs. I recommend Ting activation and a PRL update prior to installing your custom ROM.
Like others, I would like to learn about a stable kitkat ROM where bluetooth, wifi, and phone data/sms/calling all work reliably. My other primary requirement is the ability to play DRM'd downloaded Amazon Prime Music, which didn't work on the kitkat ROMs I tried, but does work on my JB ROM.
Sent from my XT897 using Tapatalk