Jump to content

Google Home-Kit Kat for unsupported devices


MartialRanger23

Recommended Posts

So recently I stumbled upon the APK files for Google's new Google Home Launcher, 4.4 Keyboard, and new Hangouts. (If you just want to skip to the APK file downloads, here you go:http://www.phonearena.com/news/How-to-install-the-new-Google-launcher-and-apps-from-Android-4.4-KitKat-keyboard-Hangouts-camera-wallpapers_id48969). I downloaded and installed these, knowing my year old Samsung Galaxy SIII wouldn't be receiving the Android 4.4 update [EVER], and after using my dad's Nexus 5 for a few minutes, I gotta say it looks pretty close. I love this launcher, and I can't figure out why Google won't release it on the Play Store anytime soon. It's brilliant! It works well and looks like Kit Kat. No extra launchers or themes necessary, just apply the launcher and you've got Kit Kat on your home screen. The new Keyboard is really neat, too. And the Hangouts with integrated SMS? I love it. For anyone who hasn't gotten the update yet or has a device that will never get it, I recommend this. Also, if you download the Jelly Bean Go Locker theme and the Go Locker app and it's dead on! Alright, I'm done. Now to go look up more useless things!

 

 

[uPDATE] 

 

 

New Hangouts and 4.4 Keyboard released on Google Play a couple days ago, though no update on the Google Home launcher. Will update when there's news!

  • Like 1
Link to comment
Share on other sites

Do you have to be rooted for it to work?

 

 

-Luis

No I don't think so just have to check allowed uknown source apps to install. If it dosent work there is a file you can try to replace in the system/lib folder on xda developers site but you have to be rooted to access system lib.

  • Like 1
Link to comment
Share on other sites

Do you have to be rooted for it to work?

 

 

-Luis

Nope, you don't have to be rooted. It will work on anything unless your device runs Android 2.3 or under, in which you must complete a few extra steps. It doesn't look like Kit Kat on a Nexus 7 2nd gen., so it doesn't work on that. I am going to try it on my Kyocera Echo and then my Motorola Droid 2. I'll update when done!

Link to comment
Share on other sites

  • 10 months later...

Even though this post is WAAAY old, I just wanted to point out that the Galaxy SIII HAS received the KitKat update (quite a while ago, actually) and some clever people have ported the S5's interface to rooted SIII's on KitKat. ;-)

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...