Related
Throughout the forums there seem to be fairly conflicting reports about CM7 for the Touchpad, it crashes a lot, it mostly works, lots of apps don't work, most common apps do work.
Basically, how reliable is CM7?
I don't use too many apps, so for me it would mainly be for:
- Browser
- Gmail
- Google Docs
- Facebook
- Twitter
- Spotify
- Swiftkey (does the tablet version work?)
Oh, and the official Touchpad Bluetooth Keyboard.
Would I get a good experience out of the current build?
Some answers after 5 days using CM:
-in my case, no SOD, but it seems to vary
- dolphin hd (browser) works nicely
- SwiftKey x tablet also good
- 2 random reboots in 5 days
- facebook ok if you use fake gps to Set up your location (otherwise it crashes)
Sent from my HTC Desire using XDA App
I have the official hp touchpad keyboard. It works really well once you get it paired. When it ask for the code on the tp put in 0000 then hit ok. As soon as your done hit 0000 on the the keyboard then hit enter. You have to do this really fast while the tp is running the ring on the screen getting ready to pair it. Good luck
Sent from my SENSaYtion.
I have had no reboots no SOD no crashes with Facebook no WiFi drop. For me its working great no problem.
Sent from my PG86100 using xda premium
Luda305 said:
I have had no reboots no SOD no crashes with Facebook no WiFi drop. For me its working great no problem.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
+1 with the alpha 2.1, I don't even notice these so called crashes they said with it being an alpha.
Cube1701 said:
Throughout the forums there seem to be fairly conflicting reports about CM7 for the Touchpad, it crashes a lot, it mostly works, lots of apps don't work, most common apps do work.
Basically, how reliable is CM7?
I don't use too many apps, so for me it would mainly be for:
- Browser
- Gmail
- Google Docs
- Facebook
- Twitter
- Spotify
- Swiftkey (does the tablet version work?)
Oh, and the official Touchpad Bluetooth Keyboard.
Would I get a good experience out of the current build?
Click to expand...
Click to collapse
One of the most stable "alphas" I've seen, more of a beta. Running Alpha2, a couple times a day I might have to cycle Airplane mode to get wifi back. This seems more frequent if hopping multiple APs. A couple apps you listed have issues;
- Google Docs - current version FCs, had to sideload old version 1.0.4r (search the forum, there are discussions on this)
- Facebook - FCs unless you run a fake gps app first
This morning I had to power cycle it to get touchscreen back, but even so I feel no urge to reboot into WebOS.
Sent from my HP Touchpad using xda premium
No problems here
Sent from my HP Touchpad cm7 using xda premium
I have been running 2.1 alpha since it was released. The only issue I have had is the common wifi issue. Occasional disconnects but otherwise stable enough to run as a daily driver.
Sent from my HP Touchpad using Tapatalk
I received my touchpad the morning of Oct.17. I have been using cm7 exclusively since that evening. No.need for Web OS.
HTC Vision(G2), meXdroidmod Ghost Chili AIO ROM/ICS CM7 theme.
The Google Docs App force closed on me today when i downloaded/installed it.
Camera doesnt seem to work, it also force closes.
Had a few SODth but saw a thread earlier today about installing an ap (softlocker) and its helped thus far.
No random reboots for me. Ive been running CM7 alpha2 since last Thurs
Everything except wifi is fairly reliable. I only have secured networks, so wifi constantly crashes for me. I'd wait for the next release if it was important to you.
--
Sent from my Droid Bionic.
As for me,
1. Market sometimes FC when installing (not a big deal)
2. Wifi drops occasionally and need manual reconnecting
3. Battery drain during sleep, at the rate of around 2 to 3% per hour
4. Scrolling a bit jerky for a dual core 1.5GHz device
5. Facebook FC without FakeGPS
Otherwise everything is working so far. But then I haven't tested everything.
stupidchicken03 said:
The Google Docs App force closed on me today when i downloaded/installed it.
Camera doesnt seem to work, it also force closes.
Had a few SODth but saw a thread earlier today about installing an ap (softlocker) and its helped thus far.
No random reboots for me. Ive been running CM7 alpha2 since last Thurs
Click to expand...
Click to collapse
New version 1.0.30 of Google Docs came out today, works great now.
Sent from my HP Touchpad using xda premium
Im waiting for alpha 3. I ended up removing it from my pad since mine wouldn't stay connected to WiFi for longer then 30 seconds at a time.
Sent from my SGH-I897 using xda premium
I only got mine last night and got CM7 loaded within minutes of opening it. I had some problems with wireless until I switched mine to channel 6 from channel 11. It ran solid as a rock for a few hours until I shut it down for the night.
Renders all my various size and density photos (all JPG) quickly and very crisply.
Netflix ran good.
Youtube was okay.
My mp4s encoded for my Nook Color were all messed up (played but video was whacky, striped accross the screen, these play great on webOS)
Plays my MP3 without issue (need to move my album art over from my Nook Color)
Quadrant scores are pretty low (low 2000's) only due to the FPS graphics not being optimized (GPU acceleration probably is not finished.)
Cube1701 said:
Throughout the forums there seem to be fairly conflicting reports about CM7 for the Touchpad, it crashes a lot, it mostly works, lots of apps don't work, most common apps do work.
Basically, how reliable is CM7?
I don't use too many apps, so for me it would mainly be for:
- Browser
- Gmail
- Google Docs
- Facebook
- Twitter
- Spotify
- Swiftkey (does the tablet version work?)
Oh, and the official Touchpad Bluetooth Keyboard.
Would I get a good experience out of the current build?
Click to expand...
Click to collapse
Browser is meh. But 3rd party Opera is fantastic. Nearly as smooth as safari on ipad.
Gmail is fantastic.
Google Docs is great.
Facebook sucks if you don't install a fakegps app or the older 1.5.2 apk that didn't need GPS.
Twitter's great..
Thats all I know. But I do know that the camera doesn't work (on EITHER of my CM Touchpads) and that each of mine have also had a random shutdown and refused to wake up (without me long pressing the power/home buttons repeatedly)... but that being said... very sweet stable for an Alpha. In fact, I think it's more stable than my phone, also on CM. And more importantly, it's better than WebOS if only for the app selection.
Compared to web os its 100% better some bugs but I haven't booted into web os since the first alpha.
Sent from my HP Touchpad using Tapatalk
have SOD's despite the fact that i've tried every work around i could find... actually the last one was probably due to the fact that the work around drained the battery... between that and the wifi i've pretty much given up on it until a more stable for me release. it is in very good shape though. i liked having a netflix tablet for a bit. wish HP had made it 16:9 but oh well.
anyway since you can dual boot i really dont' see any reason for people not to put it on there. Pulse newsreader is so damn cool on a tablet
Nomedias said:
New version 1.0.30 of Google Docs came out today, works great now.
Sent from my HP Touchpad using xda premium
Click to expand...
Click to collapse
oooo ill have to check it out. Thanks
Just installed yesterday and very impressed for an alpha build. Only get FCs for market and Facebook but realised that i need the fake gps. Did have to reboot the first time as apps wouldn't install saying i had no space. On the whole i like it and especially adobe reader as its miles more quicker and better quality than the WebOS version. But i do miss the WebOS interface so i can see what apps i'm running and throwing the cards away to close the app.
An update to Google Maps was released in the last couple of days. After updating, when I open the app it crashes after a few seconds and reboots my tablet. Is anyone else seeing this behavior?
I'm on the cm9-p4wifi-20120511.zip ROM. Prior to this issue, the ROM had been completely stable for me. I wasn't planning on changing ROMs until an IC or JB ROM had a working camera, but now I'm thinking I might experiment just to get Maps working again.
Before I do that however, does anyone have any suggestions on getting Maps stable so I don't have to flash just yet?
Thank you.
Same here, Maps 6.10.0 crash few seconds after been loaded w/CM9 aug 15
You should do a wipe cache, erase data from settings >> app >> maps or probably you should change you kernel flashing a new one
I have also the same problem. Wiping cache changes nothing. I use cm9-p4-20120814.zip ROM.
Sent from my GT-P7500 using xda app-developers app
Same issue here on Ganbarou CM9.
isthisagoose said:
I'm on the cm9-p4wifi-20120511.zip ROM. Prior to this issue, the ROM had been completely stable for me. I wasn't planning on changing ROMs until an IC or JB ROM had a working camera, but now I'm thinking I might experiment just to get Maps working again.
Click to expand...
Click to collapse
I updated to the latest CM9 nightly last night, cm-9-20120819-NIGHTLY-p4wifi, and Maps is still crashing.
6.10 is buggy. I only updated it on my Sensation and it causes reboots when I use it, and causes reboots for Rezound users as well. Guess we all have to roll back or wait for an update.
Can anyone post the previous .apk? I haven't been good about keeping Titanium Backups, I admit.
Here's version 6.9.2 - http://goo.gl/4p2O9
thank you, 6.9.2 is OK, no crash.
new google maps 6.11 = same crashes.
back to 6.9.2.
p4wifi, update Maps to 6.11.1. Same problem. The crash occurs each time I enter an area that is cached for offline use, or when I try to modify the offline settings.... or after just a few seconds. Not only the app crashes (that would report the issue to Google, which could be useful), but it directly crashes the tablet (possibly a kernel panic, I have no console so no clue).
I'm having this issue with maps crashing my Samsung tab 10.1 AOKP milestone 6 and my Sensation running cyanogen 9 and when I flashed revolutionary rom with sense. I noticed on the sensation in location settings the GPS source was not checked off (cyanogen). After I chose internal source the problem stopped. There is not this option on the tablet AOKP so it still crashes. Not sure if anyone else is seeing this issue.
oopewan said:
I'm having this issue with maps crashing my Samsung tab 10.1 AOKP milestone 6 and my Sensation running cyanogen 9 and when I flashed revolutionary rom with sense. I noticed on the sensation in location settings the GPS source was not checked off (cyanogen). After I chose internal source the problem stopped. There is not this option on the tablet AOKP so it still crashes. Not sure if anyone else is seeing this issue.
Click to expand...
Click to collapse
Same problem here, with Galaxy Tab 10.1 P7500 on latest Ganbarou ROM. Current GMaps reboots the tablet after few seconds. I looked for GPS Source setting and it's present on Ganbarou ROM. However, it is correctly checked and problem still persists. Looks more like a kernel/driver bug invoked by GMaps, putting tablet into kernel panic.
galaxy tab cm9 maps crashes
I have this issue as well. Its a version conflict. You need to install v6? Or something like that. Anyone have the link? Its somewhere on droid basement i just havent found it
isthisagoose said:
An update to Google Maps was released in the last couple of days. After updating, when I open the app it crashes after a few seconds and reboots my tablet. Is anyone else seeing this behavior?
I'm on the cm9-p4wifi-20120511.zip ROM. Prior to this issue, the ROM had been completely stable for me. I wasn't planning on changing ROMs until an IC or JB ROM had a working camera, but now I'm thinking I might experiment just to get Maps working again.
Before I do that however, does anyone have any suggestions on getting Maps stable so I don't have to flash just yet?
Thank you.
Click to expand...
Click to collapse
Hi - My post count is not high enough to ask this question in the CM10.1 thread.
I've installed cm-10.1-20130304-EXPERIMENTAL-fireball-M2.zip and gapps-jb-20130301-signed.zip successfully and most everything seems to be working well except for Google Navigation.
After selecting a destination, it correctly shows my location, determines the route, draws the map and shows route. However, as soon as I begin to drive it freezes and the app stops responding requiring force close.
I don't think it's the GPS since GPS Status, Zillow, c:Geo and even Google Maps all work OK tracking me while I drive.
All I've tried so far is to uninstall/reinstall Google Maps and cold boot.
Any suggestions?
Thanks
I just noticed you said your running the experimental M build. I'm running the nightly from that sane date and nav works just fine.
Sent from my Incredible 4G LTE using Tapatalk 2
MJL99 said:
I just noticed you said your running the experimental M build. I'm running the nightly from that sane date and nav works just fine.
Sent from my Incredible 4G LTE using Tapatalk 2
Click to expand...
Click to collapse
i'm running the m snapshot and GPS works fine.also there is a new gapps package available, which you have I see
I can definitely attest to experiencing this problem on multiple occasions. I haven't put a whole lot of thought or effort into troubleshooting it yet, as I was more inclined to restart my phone and restart navigation so that I don't miss my turn as opposed to sitting there and trying to test various scenarios to see what causes the issue. Without any serious level of troubleshooting, i think the only helpful information that I can bring to the table is that I have only noticed it while the phone is charging in the car. It doesn't happen every time (maybe 20% of the time), but when it does happen, the screen freezes immediately upon the screen flying into the proper position on the map.
smtrekkers said:
Hi - My post count is not high enough to ask this question in the CM10.1 thread.
I've installed cm-10.1-20130304-EXPERIMENTAL-fireball-M2.zip and gapps-jb-20130301-signed.zip successfully and most everything seems to be working well except for Google Navigation.
After selecting a destination, it correctly shows my location, determines the route, draws the map and shows route. However, as soon as I begin to drive it freezes and the app stops responding requiring force close.
I don't think it's the GPS since GPS Status, Zillow, c:Geo and even Google Maps all work OK tracking me while I drive.
All I've tried so far is to uninstall/reinstall Google Maps and cold boot.
Any suggestions?
Thanks
Click to expand...
Click to collapse
read the OP IN development cm 10,1 workarounds, gps fix is there
Shot in the dark. Did you try force closing the maps app and clearing the data and cache of the app then restarting it. I've had this fix problems for apps in the past. Worth a shot.
Sent from my Nexus 7 using xda app-developers app
Thanks for all the suggestions. I'll try a nightly build to see if that fixes it. I'll also try running it while not charging - so far it's also been on the car charger. As I mentioned, the GPS works fine, so the GPS workaround didn't seem to be needed. I did try the force close and clear data/cache.
I did find a working workaround by googling the issue. Apparently it's not uncommon across various phones and Adnroid versions. I couldn't find a fix though.
The work around that works is to set Nav to use 'North Up'. You do that by hitting the little compass symbol on the top left while in nav. It was tricky to hit it quick enough before freezing, but I got it. Thankfully that setting sticks for future nav requests. I get no crashes/freezes when I use it North up. As soon as I switch it back, it freezes. Odd. At least I can use it, but would still be good to find the cause and fix.
somerandomname1 said:
Shot in the dark. Did you try force closing the maps app and clearing the data and cache of the app then restarting it. I've had this fix problems for apps in the past. Worth a shot.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yeah I'd recommend just using a different nightly. I could not replicate this problem with and without a charger on Thursday.
Sent from my Incredible 4G LTE using Tapatalk 2
Same problem. I have wiped, reflashed a dozen different nightlies, and still have the same problem. It works fine in every other rom I try, either Viper or stock. Every cm10.1 causes this problem. I am using the workaround posted above(north up), but it is annoying.
Waze works well, also.
My wife has the same phone, same setup, and hers works fine.
I have yet to experience this issue with CM10.1 and I regularly flash the "sudo" nightly builds posted by mdmower on goo.im.
That said, for those experiencing this issue:
- Did you a full wipe/facotory reset before flashing to the new rom?
- Did you make sure that all your location services were turned on before flashing to the new rom?
-- If you didn't enable all location services before flashing the new rom, I strongly encourage you to flash to a sense rom and follow the instructions provided by mdmower on the CM10.1 thread in the development section.
Good luck!
retrostudd said:
I have yet to experience this issue with CM10.1 and I regularly flash the "sudo" nightly builds posted by mdmower on goo.im.
That said, for those experiencing this issue:
- Did you a full wipe/facotory reset before flashing to the new rom?
- Did you make sure that all your location services were turned on before flashing to the new rom?
-- If you didn't enable all location services before flashing the new rom, I strongly encourage you to flash to a sense rom and follow the instructions provided by mdmower on the CM10.1 thread in the development section.
Good luck!
Click to expand...
Click to collapse
Yes, full wipe and factory reset.
Yes, all 3 location services are on.
GPS locks fine. It works with north up in Maps, and with Waze, and with any other rom. Just not cm10.1
smtrekkers said:
Hi - My post count is not high enough to ask this question in the CM10.1 thread.
I've installed cm-10.1-20130304-EXPERIMENTAL-fireball-M2.zip and gapps-jb-20130301-signed.zip successfully and most everything seems to be working well except for Google Navigation.
After selecting a destination, it correctly shows my location, determines the route, draws the map and shows route. However, as soon as I begin to drive it freezes and the app stops responding requiring force close.
I don't think it's the GPS since GPS Status, Zillow, c:Geo and even Google Maps all work OK tracking me while I drive.
All I've tried so far is to uninstall/reinstall Google Maps and cold boot.
Any suggestions?
Thanks
Click to expand...
Click to collapse
Why are you using such an old nightly? Step up from M2 to the RC. The only issue I've had with the RC is a minor audio problem that has a workaround in place.
Sum Dumb Guy said:
Why are you using such an old nightly? Step up from M2 to the RC. The only issue I've had with the RC is a minor audio problem that has a workaround in place.
Click to expand...
Click to collapse
It's with every nightly, including M2 and RC1.
scottyb96 said:
It's with every nightly, including M2 and RC1.
Click to expand...
Click to collapse
I've been using mdmower's unoficial CM10 releases for a couple weeks and haven't had any google issues. Where have you downloaded your zips?
http://goo.im/devs/mdmower/fireball-cyanogenmod-oc
Sum Dumb Guy said:
Why are you using such an old nightly? Step up from M2 to the RC. The only issue I've had with the RC is a minor audio problem that has a workaround in place.
Click to expand...
Click to collapse
That post was from March when that nightly was current. The later versions didn't fix it either. The issue still exists for me, and I've just been living with the North Up workaround. I suspect it's not something CM10.1 specifically, but that was a contributing factor as it worked before the ROM switch. I think there have even been Google Maps app updates since the issue started that didn't fix it.
With the new kernel version of cm10.1 becoming available, I did a full wipe and fresh install with the 7/1 nightly, and I still have the maps issue. Living with the North Up fix for now.
scottyb96 said:
With the new kernel version of cm10.1 becoming available, I did a full wipe and fresh install with the 7/1 nightly, and I still have the maps issue. Living with the North Up fix for now.
Click to expand...
Click to collapse
cm10.2 from mdmower fixed this problem for me. Navigation works flawlessly now. Reverting back to 10.1 reproduces the issue.
Hey all, wondering if anyone can shed some insight for me on this. HTC Rezound running CM 10.1.1 downloaded the .apk file to install the latest and "greatest" google maps v7.0 and I was having some issues the first day and uninstalled/reinstalled a few times. Just took this video (sorry for awkward quality never videoed myself on another phone before =P) of me just moving the screen around and how it's tearing etc. I also went to the settings menu and it was tearing as well. This also happens on the navigation portion as well, just in the time being (at work) just threw this together real quick.
Any insight would be great! Maybe others are having this annoying problem too =/
Thanks
Video Link
UPDATE (7/11 - 2:36pm): Enabled "Force GPU rendering" in developer options and still have disable HW overlays, haven't had as much of a problem as I did in the video above. Will keep testing it though. I feel that the gpu rendering option did help a tremendous amount as well. I also set my CPU governer to "interactive" instead of "ondemand" and raised the max to 1620MHz up from 1512MHz. Will update if I don't experience anymore issues or do =P
Update (7/11 - 3:42): still having the issue app can be restarted and sometimes work right but will soon stop working properly again...
This just makes me want to NOT update right now... on Infection 2.8.1 (CM 10.1 based), think I will wait and keep using the older version until the bugs are fixed, or switch to Waze again like the last time the Rezound has Maps issues.
Omg. I hate the new version. I'm can't come to grips with loosomg built in latitude either. Any heros out there care to post the last non 7 version here?
Sent from my ADR6425LVW using xda premium
Just Google "Google Maps 6.14.4 apk" and you will find tons of places to download it, it is all over the web on almost every APK repository.
Google is working on it, http://www.xda-developers.com/andro...rs/ShsH+(xda-developers)&utm_content=FaceBook
gleggie said:
Google is working on it, http://www.xda-developers.com/andro...rs/ShsH+(xda-developers)&utm_content=FaceBook
Click to expand...
Click to collapse
cool, thanks.
When I'm Navigating, the "Turn right in 5 miles" panel keeps flickering every time the map center updates, and each time the panel flickers off, the map panel expands to compensate, then shrinks back when the panel reappears. Sometimes when this happens, the map panel has artifacting, and it gets pretty hard to navigate certain roads I've never been on before.
The flickering rate appears to be about 2-3 times a second.
acejavelin said:
This just makes me want to NOT update right now... on Infection 2.8.1 (CM 10.1 based), think I will wait and keep using the older version until the bugs are fixed, or switch to Waze again like the last time the Rezound has Maps issues.
Click to expand...
Click to collapse
Waze works great still.. just saying.
Same problem on the HTC Desire HD with CM10.1, Jellytime or CodefireX rom.
Hangouts with sms is great along with the other updated apps, but damn I love the Google Experience launcher. Way less options than nova or apex, but the always-on hotword detection on homescreens is great. Just wondering if anyone else here is trying them out?
somerandomname1 said:
Hangouts with sms is great along with the other updated apps, but damn I love the Google Experience launcher. Way less options than nova or apex, but the always-on hotword detection on homescreens is great. Just wondering if anyone else here is trying them out?
Click to expand...
Click to collapse
i think i installed 90% of them, so far so good. i cant wait for our phone to have it.
Apparently CM will continue to focus on 4.3 builds, so I don't expect a CM11 anytime soon. Knowing our luck with this device, we'll probably have issues with kit kat builds anyway. Still, the launcher and hangouts are pretty badass. It's just a shame there's no official support for icon packs with stock launchers. I have to use an xposed module to use my icon pack of choice on this new launcher and I sometimes feel like it slightly slows the device down.
Sent from my Incredible 4G LTE using xda app-developers app
They're over seas right now at the Oppo factory. Steve is normally the one that merges the new source. Give it a few months, well see test builds.
Sent from my iPhone 5 using Tapatalk 4
I had most of the 4.4 .APKs (including the launcher and Google Now) installed on my cm10.2 build for the past day or so, but today I experienced the crash/bootloop scenario that's been plaguing the nightly builds lately; after a forced reboot, all the 4.4 apps were gone, and since I had frozen Trebuchet in TiBU, I was without a launcher and had to restore a NAND backup. Was I supposed to lock all the 4.4 apps into the system folder or something?
natemup said:
I had most of the 4.4 .APKs (including the launcher and Google Now) installed on my cm10.2 build for the past day or so, but today I experienced the crash/bootloop scenario that's been plaguing the nightly builds lately; after a forced reboot, all the 4.4 apps were gone, and since I had frozen Trebuchet in TiBU, I was without a launcher and had to restore a NAND backup. Was I supposed to lock all the 4.4 apps into the system folder or something?
Click to expand...
Click to collapse
I don't know why they would disappear but you could have enabled trebuchet without restoring. You could have accessed the settings through quick settings, went to the apps section, found trebuchet and hit enable. Also, there's no reason to freeze it. Once you switch to a different launcher and reboot, none of your other installed launchers will run. Just for future reference.
Sent from my Incredible 4G LTE using xda app-developers app
somerandomname1 said:
I don't know why they would disappear but you could have enabled trebuchet without restoring. You could have accessed the settings through quick settings, went to the apps section, found trebuchet and hit enable. Also, there's no reason to freeze it. Once you switch to a different launcher and reboot, none of your other installed launchers will run. Just for future reference.
Sent from my Incredible 4G LTE using xda app-developers app
Click to expand...
Click to collapse
Settings was even crashing upon opening; it was incredibly odd. As for the freezing, I and many others who installed the 4.4 launcher were experiencing the default launcher setting not sticking even after setting it to the 4.4 launcher; freezing Trebuchet (the only other one I had installed) fixed this. But that obviously didn't work out so well for me...
Which thread are you getting the apk files from?
Anyone installed the new launcher from this thread http://forum.xda-developers.com/showthread.php?t=2506488
j13smiley said:
Which thread are you getting the apk files from?
Anyone installed the new launcher from this thread http://forum.xda-developers.com/showthread.php?t=2506488
Click to expand...
Click to collapse
I browse /r/Android on reddit often, and people were going nuts posting links to all the apks. I'm sure they're all over the internet by now.
But yes, that's the launcher I'm running. It's so limited in features compared to others, but it really does everything I need. Some people don't seem to like the google now to the left of the main homescreen, but I'm digging it.
I'm really hoping for kit kat to make it's way to our device though. I saw there's a CM11 branch, but who knows what kind of code needs updating and/or compatibility issues.
Do you need to be rooted to do this I keep getting a parsing error
Sent from my ADR6410LVW using xda app-developers app
Checking it out myself, thanks to your thread, however after installing the apks I somehow seem to have broken the "okay Google" feature. Google search updated itself and all after installation but even if I choose search manually now it still won't respond to the command.
Your right tho, the launcher is simple but works well. The only thing I don't care for is the constant Google search box on the home screen especially when all you have to do is say the command and it goes straight there.
nexus 5/ kit kat is tits guys
Linch89 said:
nexus 5/ kit kat is tits guys
Click to expand...
Click to collapse
I'm rocking the moto x for the last couple weeks. Really a great phone and updated to kit Kat on Verizon so damn fast was really a shocker.
Sent from my XT1060 using xda app-developers app
CM11 Alpha for the INC4G
You've got to check out Cyanogenmod 11 for our device. http://forum.xda-developers.com/showthread.php?t=2552150 I had to flash the updated Recovery but I have had no issues so far. There's a fair bit in 4.4 that you don't get from the base Kit Kat apps that you can install for 4.1 and up.
CM 11 nightly
I've been using the nightly from 12-26 and it is 4.4.2 I have had no issues at all, and it seems to be running smooth. Battery is draining pretty well, but it does in any rom due to the lack of signal from my house. I'm at the office now, running wifi and it seems to be draining less.