Jump to content

Google Home-Kit Kat for unsupported devices


MartialRanger23
 Share

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.

 Share

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Went to Rolling Loud NYC at Citi Field this weekend. Over 60,000 people in attendance. Verizon is a sponsor of the festival this year so naturally they had a ton of COWs set up at the festival. I counted at least 4. As a result, they were virtually the only carrier consistently able to provide a data connection. I didn't see any Verizon 5G, only LTE. T-Mobile on the other hand was a very interesting experience. I was seeing an eNB 331804 which I'm 99% sure is a COW. They also seems to be doing some sort of traffic management because I noticed that if I left my phone idle in my pocket, it would drop down to No Service/SOS or sometimes it would sit on EDGE. But the second that I needed to send a text, make a call, or even use Twitter my phone would switch over to LTE or 5G to complete the task. In an active data session, my phone would constantly flip between Band 2, Band 66, and Band 41. Sometimes, I'd catch myself on the COW and other times I'd get pushed over to eNB 875868, the relatively new Sprint conversion nearby. The network moved at a snails pace though. Where Verizon took about 15 seconds to load Twitter or send a pic, T-Mobile could take up to a minute to complete the same task. Here's some photos of the COWs I spotted. I think that the first two are Verizon and the one in the distance in the third pic is T-Mobile's single COW, not nearly enough for an event that size.  
    • @dkyeager has written up an article for The Wall on the Auction:   Robert
    • You need to have Wi-Fi Calling enabled and also have made at least one phone call over Wi-Fi Calling prior to using the inflight Wi-Fi.
    • See this page: https://www.sprint.com/en/support/in-flight-texting-wi-fi.html Also see the FAQ’s here: https://www.t-mobile.com/benefits/travel/in-flight-wifi “How do I access In-Flight Connection?”
  • Recently Browsing

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