600 MHZ auction? Leave AT&T and Verizon

        While we know that the 600 MHZ auction won't be until 2015, it just feels right to say that the two of the biggest carriers in the US, AT&T and Verizon are both spectrum hogs. Don't believe me? AT&T has AWS spectrum to reach all of it's customers. Verizon had both block C and block A before selling block A to T-Mobile. It's not like T-Mobile can use this spectrum where they bought it, they can't because there is still a lot of T.V signals still being broadcasted there that will interfere with this spectrum.

         Right now, it seems as if AT&T and Verizon need to use more of their AWS and WRS (AT&T) spectrum before attempting to purchase any new spectrum. AT&T and Verizon have waited a long time to purchase spectrum to reach all of it's customers, but that is besides the point, while markets such as Washington DC still have capacity issues and it's been years since we've seen noticeable improvements from either carrier. These capacity issues have left me personally to switch to T-Mobile, but I'm not saying that anyone is perfect. Even with T-Mobile, I get very fast LTE with the trade off of having high speed data inside of buildings. But nonetheless, 600 MHZ for AT&T and Verizon will not give any benefits for coverage as their existing spectrum already tackled this issue.
         Leave your idea's and comments of who should be in the spectrum auction of 2015 for 600 MHZ.

Why you need AWS on T-Mobile

          So, after using leaving the incredible coverage and mediocre data performance of AT&T, I have decided to switch to T-Mobile. After using their LTE network, I can honestly say, that is consistent. Speeds with a decent signal have been over 10 Mbps, even during peak times. The area that I have done most of the speeds was in Washington DC and it's spread out suburbs of Arlington and Fairfax county Virginia. These speeds have been good, but if you intend on using T-Mobile, get an AWS capable handset.
   
          When I originally switched over from AT&T to T-Mobile, I was confident in the 1900 MHZ rollout with the AWS LTE. But, I quickly learned that AT&T is the exact opposite of T-Mobile, AT&T has great coverage with mediocre data performance, however T-Mobile has great data performance with mediocre coverage. This is due to the fact that T-Mobile uses 1900 MHZ and AWS for their network, while AT&T uses 700 MHZ for LTE, 850 MHZ for voice and data, 1900 MHZ for voice and data, and AWS for voice and data in some markets. But, don't confuse this as me bashing either carrier, if you want coverage, go with AT&T, if you want data performance, go with T-Mobile.
 
           But as I said before, you need AWS for HSPA(+) on T-Mobile for data. There is no getting around that, the 1900 MHZ rollout seems stopped in it's tracks and not every AWS/PCS cell has LTE. T-Mobile does have a frightening amount of LTE dead zones in residential parts of the city. Not suburbs, the residential sides. Normally, if you had an AWS handset, you would go down to HSPA(+) (Most likely DC-HSPA+) and not onto the ancient EDGE network. But, if you look at T-Mobile coverage maps, the pinkest areas are LTE/HSPA(+) and the darker pink areas are EDGE. T-Mobile does not show the frequency band of their HSPA(+) network on their coverage maps, and places such as Carmel, NY are excellent examples of non existent LTE coverage (Obviously, if it's nearest major city is 1 hr away), but still, the area is 100% AWS for HSPA(+). So, even if you don't travel, you may want to consider picking up an AWS handset and putting your T-Mobile SIM in it.

Android Flashaholics, A Google+ Community

         Android Flashaholics is a Google+ Community where Android users can come together to talk about Android! This community was made for users to talk about ROM setups, scripts, mods, recoveries, tips, and anything else! You can post your ROM and kernel setup for your device and speak about it, offer tips and work arounds for *features* in anything relating to Android. Speak about scripts that you maybe working on or speak about ROMs that you maybe using/making for a new ROM. Talk about stories and things that have happened to prevent bricking your device. Talk about how many times you have bricked your device and offer tips to on how to prevent a brick for other users. Please keep this community alive and keep it friendly. I will need users who will serve as "moderaters" to keep the community safe.

Lastly, happy posting to the Androd Flashaholics community.

       

Testing T-Mobile Signal, Speedtest, and Roaming

 These are just screenshots of speed test and service I was getting on T-Mobile. Also, yes, their is roaming on "Monthly 4G". Also, the second one is true, I did get GPRS speeds. Device used was a HTC One X(L). These Speedtest were taken all over America. Note: Used older Speedtest app to conserve data usage.

Low Memory Nan-droid Backup

  Quite a lot of owners of Google's previous flagship smart phone (Nexus 4) have purchased the 8 GB version not knowing the little amount that was usable by the user. Well, throw in a few HD games and ROMs and your storage amount will go down very fast! While this smart phone is a Nexus, it can be "rooted", "ROMed", and modified to your hearts content. Now since we are in the age of ROMs becoming larger and larger and our micro SD cards becoming more and more useless for our smart phones, and knowing this a lot of users I know DO NOT use Nan-droid backups. I was shocked because if something were to go wrong while you were away from your PC, and you were without a ROM on your internal SD than you are sort of screwed. A Nan-droid backup is probably one of the most reliable ways to restore as it often can be compressed and customized to tailor different storage sizes.

  However, this solution does not come with any warranty what so ever, if you brick a device, you pay the price. Now on to my solution, which is to download a "Slim bean" ROM and place it on your SD card and flash the Gapps for your ROM. Then, flash the ROM as you would any other ROM and flash the Gapps and customize your device by putting only the necessary things like your contacts and applications you need everyday. Then, (I should have said you need to be on TWRP) do a Nan-droid backup with just the data checked, (it should be very small as it only contains things you need). Then, delete the Gapps and keep the the ROM on your device and all of this should be under 300 MB. The trick is to only do a backup of /data partition which should only contain the needed applications.

   The process of using this solution is quite simply, flash the "Slim Bean" ROM and reboot to the ROM (THIS IS NEEDED TO AVOID BOOTLOOPS) and reboot back into recovery. Then when in recovery, restore the Nan-droid that contains just the /data partition as this is only the needed partition for this to work as you have just flashed /system and then your device should boot up to just the way you had it. This solution will work on any device.
   
  1. Download a ROM. 2. Download Gapps. 3. Flash ROM and Gapps 4. Customize with only needed applications 5. Back up only /data partition 6. Delete Gapps .zip 7. Flash ROM 8. Reboot to recovery. 9. Restore Nan-droid with only /data partition. 10. PROFIT!

Why Applocking software isn't useful

I'm publishing this post to state a few points to say that on Android Applocking software should not be trusted. On Android versions 4.1+ Android features a feature called Safe-Mode that disables all third party applications that are on the device, to include KIK, GTA VC, Hulu Plus, and Applock. Even when the you grant Applock device administration you still can bypass Applock by simply booting into Safe-Mode and deactivating device administration, this is a problem because any Applocking software can be disabled!

Also, owners of devices with unlocked bootloaders can be at risk of all security measures before encryption can be disabled! Simply flashing the appropriate TWRP recovery for your device or by using a recovery or .zip with a file manager is at risk of data being stolen if lost or stolen. If you boot the device into recovery and navigate to data/system and delete locksettings.db and all files called locksettings and delete gesture.key and password.key or .db. Then reboot then you should have an unlocked device!

ALL MODIFICATIONS ARE DONE AT YOUR OWN RISK!

Keep in mind that I'm on an AOSP ROM so your steps may vary!

Why the Nexus 7 is the best 7" tablet.

  The Nexus 7 is described as powerful and the best bang for buck. Many users describe the Nexus 7 as being exactly that, a device with a budget price and having lots of SPEED and not to mention always having the latest major Android release.

  The Nexus 7 (2012) offers a nVidia Tegra 3 CPU which in 2012 the Tegra 3 chipset was arguably the most talked about chipset but without LTE it was a drawback to Qualcomm S4. I can't give my opinion to the Nexus 7 (2013) as I don't own this model but I do intend on upgrading only for the unlocked LTE, which by the way is making my mouth water and the HSPA+ with S4 Pro the icing on the cake. I do like tablet however, it has very poor NAND chips that frequently need TRIM to run on them to keep the buttery smooth performance. Also, I recommend Paranoid Android with the Franco Kernel for the best performance and battery life combo. While I still like my One XL I do think about getting a LTE Nexus 7 and use that because KIK is being used more often than the stock messaging app. Also, KIT KAT is going to be a tasty update that I believe should be given to the Nexus S as a bed for it to rest.