Jump to content

Google Home-Kit Kat for unsupported devices


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

    • I was just in Greenwich, CT doing some shopping and naturally also doing some recording of cell sites in the background on Cellmapper. Specifically I was along Greenwich Ave which is the most dense part of the city. Verizon: Literally didn't work most of the time. Even though their coverage shows the entire city blanketed in 5GUW you'll only be on their nationwide 5G network or LTE if you're anywhere south of Lewis St. Regular 5G (non C-band) didn't work at all. I don't mean it was slow, I mean it didn't pass any data at all. When I opened Instagram it told me "No connection". In a store I was in I even overheard someone asking another shopper if they had service in the store. I immediately knew they were on Verizon. Switching to LTE gave me data although it was slow. In most stores I'd get speeds in the low teens, outside it'd go up to 40Mbps. Above Lewis St. my phone finally connected to n77. On n77 I was seeing ~180Mbps. It seems like the issue isn't backhaul, it's just that Verizon doesn't have any remaining capacity on the LTE side.   AT&T: AT&T was slow but didn't suffer from the same "No data connection" issue that Verizon did. Speeds were in the low teens most of the time and peaked around 50Mbps. My phone hopped between AT&T's nationwide 5G and LTE frequently much like Verizon. Also just like Verizon, north of Lewis St. I suddenly connected to 5G+ which gave me speeds just over 100Mbps. AT&T also at least one small cell along Greenwich Ave for additional capacity and coverage and it's doing wonders for their network in the area. I'd go as far as saying it's probably the only reason they're not in the same situation as Verizon.   T-Mobile: Not to sound like an ad for the company but I was really blown away by T-Mobile's performance here. T-Mobile is collocated on the same towers as Verizon and AT&T in the region but they have an extra site in the steeple a church along Greenwich Ave that they've upgraded with n41. As a result, T-Mobile not only has the strongest signal indoors and outdoors, they also have the fastest speeds by a long shot. Nowhere along the commercial strip did I drop below 500Mbps. Indoors I was seeing over 300Mbps and outdoors I peaked at over 600Mbps. For the sake of testing I switched my phone to LTE and saw speeds of 180Mbps indoors.  
    • This site, along with T-Mobile eNB 307360, don't have B41 live, but do have n41 live. Seems like the latest T-Mobile convert sites don't broadcast B41 at all.
    • Sprint eNB 9493/5784 -> T-Mobile eNB 216213 Located at: 40.61611028489374, -74.01141959254353 Sprint eNB 6786 is converted but not live Located at: 40.647096399275, -73.97984672978991  
  • Recently Browsing

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