InfiniteSMS Android 2.2 (Froyo) SMS Limit Removal Fixed

In the newly released version 0.8 of InfiniteSMS, SMS limit removal in Android 2.2 (Froyo) has been fixed by porting over the working limit removal code from EliteBomb.  The update is available on the Android market right now, so if you don’t use EliteBomb and want to remove your SMS sending limitation on your rooted device, download the new version of InfiniteSMS now.

Automatic SMS Limit Removal WORKING on Android 2.2 (Froyo)!

I’ve been messing around with the SMS limit removal code in EliteBomb Plus on my rooted Android 2.2 device (Samsung Epic 4G, running the leaked ROM), and I just managed to get the SMS limit removed 100% automatically! This is very exciting, as this feature is the #1 request I get. In fact, this feature is so major, that I will be bumping the version number to 3.0 when I get it released to the Android market. I have not tested the code for backwards compatibility with devices with Android versions less than 2.2, but I don’t see any reason why it shouldn’t work. This feature will be released first in EliteBomb Plus, and it will be ported over into the free version of EliteBomb shortly afterwards (I like to reward my paying customers). Before I release this, I plan on doing some further testing to ensure that everything does in fact work properly, and it’s repeatable. Unfortunately this process involves removing the limit and resetting it to default several times to make sure that it works. There isn’t much I can do about that unfortunately. However, I’m really excited to finally have this working, and it’s great to be able to release this to make removing the SMS sending limit much easier. Once again, the version with the fixed limit removal will have a version number of 3.0. Look for it in the market very soon. I will also be updating InfiniteSMS, since it’s mostly the same code. Anyways, I should stop working on writing this, and get back to work. I’m just really excited to have this working! ;)

UPDATE: Version 3.0 of EliteBomb Plus is on the market right now! Check it out in the Android market! :) The free version of EliteBomb should have the fix available very soon. Keep an eye out for it…

UPDATE 2: The fix is now available for the free version of EliteBomb as well! If you don’t have it already, I highly recommend downloading it now.

Introducing FiOS WEP Calculator Mobile!

For all of you who don’t have an Android device, it’s been difficult to calculate a default FiOS WEP key using your mobile phone. Well not any more! Now if you visit the FiOS WEP Calculator website on any mobile device, as long as your device supports JavaScript, you can calculate a default WEP key (I’m also planning on porting the script to PHP, and using server-side calculations for devices that don’t support JavaScript in the future). The mobile optimized version is incredibly lightweight, with no CSS files (all styles are embedded in the main page) or images, what-so-ever, and all unnecessary formatting in the source code removed. On a 3G connection, the page should easily load in under 1 second almost every time (the entire page is less than 3kb). I believe that this new website will make it significantly easier for users of every mobile platform to use FiOS WEP calculator on the go. To check it out, visit goo.gl/D6P5x on your mobile phone, or scan the following QR code:

Google Adds Mobile Editing to Docs on Android and iOS Devices

This post is somewhat out of the ordinary, but this is just so cool, I couldn’t help myself from sharing it. Google just released a new feature in Google Docs that will let you edit your documents from any mobile phone running Android or iOS. Not only that, but you can also edit your document while others are editing it at the same time, with “near real-time” updates. This new feature will be available for all users on Android version 2.2 or iOS version 3.0 or greater. Users on Android can also write text using their voice. Check out the following video, it’s pretty cool.

EliteBomb High Resolution Application Icon Done

I just finished working on the new mandatory high resolution application icon for the free version of EliteBomb. It’s a real shame that the Android market compresses the images that you see on your mobile devices so much. In fact, because of the ridiculous compression, having a high resolution icon is somewhat pointless. I’m speculating that these high resolution icons will be used in a future Android product, most likely a tablet, as 512 x 512 images are much too large to be used on a phone. Anyways, I think the icon came out pretty well, but, as with all artwork, you can always judge that for yourself (click the image for full size):

Beginning Work on High Resolution Icons

The Android Market now requires developers to upload 512×512 high resolution icons for their applications without any alpha transparency. I’ve begun work creating and uploading logos for my applications, and I hope to have them done within the next few days, although I am awfully curious what Google plans to do with these new high resolution logos.

My Opinions On the Leaked Epic 4G Froyo ROM

There are many changes that Samsung made to the leaked Android 2.2 (Froyo) ROM (link: [ROM] Froyo DJ29 leak, deodexed, zipaligned and pre-rooted v4.2 [11/12]) that I really dislike, and I hope that they change before the official release comes out. This is a list of the things that I noticed so far that significantly degrade the user experience, as well as changes that I absolutely love, and a few suggestions:

  • Samsung replaced the stock messaging application with their own custom one that isn’t nearly as good or as nice looking. This is actually my number one concern about the new firmware
    • They really need to stop trying to imitate the iPhone’slook and feel. If we wanted an iPhone, we would’ve bought one
      • Not only that, but they are also doing a terrible job at mimicking it. In fact, Samsung’s new messaging app feels worse than the one on the iPhone
    • The image viewer in the new messaging application is completely broken. It has no ability to zoom in, it shows a progression timer when displaying a still image, images are zoomed out by default, etc.
    • The best option is to just scrap their messaging app and go back to the stock messaging app, which works flawlessly, and has a very native and natural look and feel
  • The new way the applications are arranged in the app drawer is annoyingly unintuitive. Making the user manually rearrange them is not the right way to sell more devices. They were fine before when they were automatically arranged in alphabetical order, but it’s really annoying having to manually reposition the icons. There doesn’t even seem to be an automatic arrangement option.
    • Manual arrangement is fine, as long as the user can choose to have the icons arrange automatically.
    • The new application removal icons are also fine, but really, they should also exist on the pre-installed crapware, since nobody wants NASCAR and Sprint Football Live preloaded anyways.
  • The Internet browser feels incredibly slow and unresponsive now, especially with scrolling. I’m not sure what modifications Samsung made to the browser, but really it would be best to leave it stock, since the stock browser is known to have excellent performance compared to the one in Eclair.
    • Also, the new “Internet” icon looks terrible compared to the look and feel of the rest of the operating system. I really prefer the old one.
  • The new “News and Weather” application is great. It really is. I love how it automatically locates you via GPS and displays relevant weather information, and the tab scrolling at the top of the screen is wonderful.
  • The new colorful icons in the Settings menu feel very non-native to the platform, but I kind of like them. With less glossiness (I despise glossy icons) and saturation, I could actually become accustomed to them.
  • I really like the new voice recorder application they include in the new ROM. It’s very simple and easy to use, yet it looks great!
  • The Video Player application is also really good, but I experienced some issues with stopping a video that really ruin the user experience. When the back button is pressed, the video should be stopped, and I should be taken back to the list of videos on my device. There should be no need to press an additional on-screen button to stop playing the video. Also, video playback is laggy, and skipping to parts of the video reveals significant delays.
  • The Memo application is pretty good, but it should allow you to backup memos that you create, either on the device’s SD card, or to the cloud.
  • Getting a GPS position is still flawed. It takes way too long to get a lock on my position, especially considering how other, lower-end phones such as the Samsung Transform are able to get a quicker GPS location that a high-end device like the Samsung Epic 4G.
  • The new AllShare logo looks much better than the old one, but it looks a bit too glossy for my tastes.
  • It would be a great addition if Samsung would pre-install the latest version of Google’s Voice Search application, which comes with Voice Actions. Sure, users could install that themselves, but it integrates really well with the operating system, and works much better than the version that comes installed. Also, most users won’t know to install the version of Voice Search in the market.
  • I love the new Silent toggle in the notification bar, but really, it should let you put it in Silent, Vibrate, or Normal (Non-Silent) mode.
  • During calls, the proximity sensor sometimes doesn’t work correctly, leading to difficulty ending the call.
  • There are often glitches when entering the lock pattern.

I will update this list if I notice anything else that should be changed with the new firmware, but really, I’m overall impressed with the new firmware, and I will continue to use it on a day-to-day basis.

UPDATE: Very frequently, when pressing on the screen and dragging, the phone will think you let go early, even though you didn’t. This is far too common, especially with the lock pattern and Swype, and the problem is incredibly annoying and infuriating.

An Explanation of My Recent "Self Destruct" Application

Self Destruct” is simply an application I made for fun, as a proof of concept. This application demonstrates a way to create an application that is able to “destroy” itself, preventing it from running until it is uninstalled, and then reinstalled later. I’d like to personally thank HandlerExploit for giving me a hint about how to do this (he mentioned that he found the trick in the provisioning code). HandlerExploit uses a similar technique in his application, “iBrick Proof of Concept”. As soon as the user opens the application, it removes it’s main class from the Dalvik package manager, preventing itself from being able to run again. The only way to run the application again after opening it is to uninstall the application, and reinstall it. This application serves no real purpose other than to demonstrate an interesting trick, and it is not malicious in any way. Please note that after running the application, it’s icon will remain in the launcher, although you won’t be able to open it. Uninstalling the application will remove the icon. I’d release the entire source code for this application, but really, the only part that actually matters is the part that removes the class from Dalvik and prevents the application from running again. Interestingly, this application requires absolutely no permissions, at all in order to do this. In case you are interested in how I did this, here is the source code for the main class in the project:

package com.dylantaylor.selfdestruct;
import android.app.Activity;
import android.content.ComponentName;
import android.content.pm.PackageManager;
import android.os.Bundle;

public class Main extends Activity {
    /** Called when the activity is first created. */
    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.main);
        PackageManager pm = getPackageManager(); ComponentName name = new ComponentName(this, Main.class);
        pm.setComponentEnabledSetting(name, PackageManager.COMPONENT_ENABLED_STATE_DISABLED, 0);
    }
}

Yes, I realize that this application serves no real purpose, but it’s just something interesting that I made for fun. If you don’t want it, don’t download it. Otherwise, have fun! :)

P.S. Do whatever you want with that source code, it’s virtually worthless to me anyways.

Network Listing Coming Soon to FiOS WEP Calculator Lite

In order to give FiOS WEP Calculator Lite users a taste of the Pro version, and boost sales, I decided to allow users to preview the network selection feature, but not actually “select” the network unless it is remembered on the device. What this means is that they will get a listing of remembered and nearby access point listings,  but they will only be able to select and calculate WEP keys for ‘remembered’ access points automatically. They will still be able to view a listing of nearby access points, but they will not be able to select them. Having this feature will still improve the overall experience, while still giving users a reason to purchase FiOS WEP Calculator Pro.

UPDATE: I finished adding the new features to the lite version, and an update is available in the Android market. The new version of FiOS WEP Calculator brings the ability to view nearby and remembered FiOS networks, previously only available to pro users. In order to select nearby networks (not remembered ones) automatically, you need to upgrade to the pro version, but you can now view a list of nearby networks without paying for FiOS WEP Calculator Pro.

Wireless Network Selection Added!

I finished adding wireless network selection to the Pro version of FiOS WEP Calculator. This enhancement adds tons of value for those who already purchased FiOS WEP Calculator PRO, and adds an incentive for others to do so. Overall, I’m really excited to announce this new feature, and I look forward to receiving feedback about it. Enjoy! ;)

UPDATE: Version 2.1 fixes a minor annoying bug where the list of networks is reset when the keyboard is opened/closed or the screen is rotated.

UPDATE 2: Version 2.3  fixes a significant bug that resulted in a force close when selecting certain items in the network list.