• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

What you like or dislike in 4.4 Kitkat ???

Play Store still force closes if you're updating apps and try doing a search at the same time, and it also tends to silent-crash if you open it. still getting the toast alert of 'Internal Storage 1.30 MB left' and i think that's my Dalvik heap getting full. once it hits 1MB left the device auto-reboots. Please, Google, give us ART soon!

If using Nova Launcher Prime, hitting home or back to get out of Google Chrome after using it awhile causes a launcher redraw/restart issue. possibly due to full dalvik again. this issue is worst on my Nexus 10. not so much the 7 or my phone.
 
Nexus 10 FC again during an upgrade process "Google Play Store has stopped" right at the 'InternalStorageSpace 1MB left' alert. Google, Please bring ART soon!! sick of this crap. now it won't update until a reboot! Rebooting to fix issues should be a Windows-only problem!

Installing 200+ Apps/games causes the Dalvik to get seriously full on the 10. a fresh reboot gives it a mere 10MB of Dalvik heap available. not long after it starts crashing and auto-rebooting.
 
nickdalzell said:
Nexus 10 FC again during an upgrade process "Google Play Store has stopped" right at the 'InternalStorageSpace 1MB left' alert. Google, Please bring ART soon!! sick of this crap. now it won't update until a reboot! Rebooting to fix issues should be a Windows-only problem!

Installing 200+ Apps/games causes the Dalvik to get seriously full on the 10. a fresh reboot gives it a mere 10MB of Dalvik heap available. not long after it starts crashing and auto-rebooting.
Click to expand...

I thought you could switch to ART as it is hidden in 4.4. Or was that just for the Nex4?
 
nickdalzell said:
Nexus 10 FC again during an upgrade process "Google Play Store has stopped" right at the 'InternalStorageSpace 1MB left' alert. Google, Please bring ART soon!! sick of this crap. now it won't update until a reboot! Rebooting to fix issues should be a Windows-only problem!

Installing 200+ Apps/games causes the Dalvik to get seriously full on the 10. a fresh reboot gives it a mere 10MB of Dalvik heap available. not long after it starts crashing and auto-rebooting.
Click to expand...

I've got 240 apps, some HUGE, and never seen this issue at all. ART in fact only exacerbates storage space issues.
 
nickdalzell said:
Installing 200+ Apps/games causes the Dalvik to get seriously full on the 10. a fresh reboot gives it a mere 10MB of Dalvik heap available. not long after it starts crashing and auto-rebooting.
Click to expand...

How much internal space is left on your device? It sounds like you could be running out, and the problem wouldn't be dalvik related if that were the case
 
For those upset permission manager stopped working go to the play store and look up APPOPS...........
 
i actually have 16GB left. that toast alert i have found is referring to the partition used for the Dalvik cache. since i have far more apps/games on this device (mainly games, each over a half a gig or so) than any other, it has seriously filled up. if i reboot, it refreshes it and i got around 9-10MB of dalvik available. it seriously gets extremely crash-happy as it fills. that can be from just updates from Play Store or opening up one game.

If internal storage was at fault i'd be getting the notification 'Low space--Storage space is running low' and i wouldn't be able to install much less update anything. Play Store gives an 'Insufficient Storage Available' error if you try installing any app or such with less than 20MB left. this is not a low storage issue. it's a tiny dalvik heap that's all but used up.

As for ART being hidden, it should be under Developer Options under 'select runtime'. leave it to Google to leave that feature out of KitKat on the Nexus 7 and 10. :( Seriously, leave out the launcher, leave out the runtime, i mean what is the point of upgrading? it is just 4.3 with a new version number. all the good stuff is omitted.
 
As ART matures we will probably see it in an update. I am not sure it is optimized well enough for our systems let alone not just breaking apps. Another issue is I saw a few posts saying it really is meant for the Qualcom CPU's right now.

As far as transparencies I am hoping they can fix whatever the issue is. The fact we are at 2560x1600 though does not give me much hope. It is a lot of pixels to push around.

Back to the original point though, I too would love to see an optimized, and better compatible, ART out soon for us.................
 
I've run multiple benchmarks on ART vs Dalvik on the Nexus 10 on my Tempest ROM. There was no noticeable performance gain on the N10 using ART. That being said, App Permissions is in OmniROM :p
 
dibblebill said:
I've run multiple benchmarks on ART vs Dalvik on the Nexus 10 on my Tempest ROM. There was no noticeable performance gain on the N10 using ART. That being said, App Permissions is in OmniROM :p
Click to expand...

App permission is in the OTA just burried deeper than in 4.3. Appops reaches the new depth where permission manager doesn't.
 
I should say it's not really performance that's a problem with the 10, since it's the most powerful Nexus tablet so far, it seems to perform well enough. my issue currently is the Dalvik problem.

Performance however, is a problem with the Nexus 7. there is a big difference between what it does regarding smooth performance and what my Galaxy S3, which is even less spec than the 7, does. the Galaxy S3 in and of itself has increased considerably in how fluid it is and how smooth-as-an-iPhone it has become thanks to ART. it has not yet crashed or had any of the problems it had with Carbon ROM (which is still in beta). the Bluetooth is dead but i have found out it's a hardware problem and can find no solution online (it pairs ok, and my headset and radio in the car can communicate and send commands, but instead of the audio being routed through the headset or car stereo, it comes out the top microphone for some reason)
 
I absolutely HATE the changes to the phone app on my Moto X. It stunk before, but it's worse now. I don't know about its manifestations on other devices. Whereas before, it was quick and easy for me to open PHONE and select HISTORY or DIALPAD or CONTACTS icons. Now they're hidden more. Removing a phone contact still takes 5 clicks which is absurd. Earlier Android on my LG phone was much better, so it may be that the menu structure in just the Moto X sucks.
 
InWisconsin said:
I absolutely HATE the changes to the phone app on my Moto X. It stunk before, but it's worse now. I don't know about its manifestations on other devices. Whereas before, it was quick and easy for me to open PHONE and select HISTORY or DIALPAD or CONTACTS icons. Now they're hidden more. Removing a phone contact still takes 5 clicks which is absurd. Earlier Android on my LG phone was much better, so it may be that the menu structure in just the Moto X sucks.
Click to expand...

I agree. When I open my phone app, I just want the number pad. I thought that maybe I was just missing something and I had it set up wrong. But I guess not.
 
Honestly, I hate it. Razr M... bought it a year ago and it was amazing. Updated to KitKat and now everything about my crappy Droid Incredible has come back to haunt me...

I'll start from the beginning of my average day:
- The alarm goes off... instead of throwing my half-asleep hand on the large "snooze" button, I must swipe to snooze... AND I must make sure I swipe to the left, or else, if I swipe to the right, the alarm turn OFF. Once I successfully make the left-swipe snooze, the screen lights up very brightly. I'm not a morning person and this just annoys the **** out of me. With JB, I could just tap the screen and the screen would dim, understanding that I'm not ready to commit to the morning.
- Once I'm finally up, unplugging from charger causes the screen to come on. Being the non-morning person that I am, I am always in a rush... so I unplug the phone and throw it in my pocket. BUT, since now the screen wakes upon unplugging from charger, I must take the extra step of turning off the screen, since grabbing the phone in haste now usually triggers whatever stupid quick camera access BS they have implemented. So now I have an active camera in my pocket.
- Even if I don't accidentally trigger the lock screen camera quick access crap key, the battery still drains throughout the day, reminding me of the dreaded Droid Incredible days of charging twice a day. I'm now usually down 20% 2-hours into the day with no use... compared to the 2% I would be down with Jelly Bean.
- Texting... black text on white... how exciting. Reminds me of reading a Word Doc.
- The lock screen quick-mute switch is gone. Absolutely HATE that it is gone.
- Again I must mention the lock screen function... when you hold down on the lock screen and panels appear... sorry, I don't know the terminology for this feature. Somehow, by accidental swiping that happens by the normal practice of grabbing a phone off of a table, the clock has disappeared, leaving me with a blank lock screen.
- All apps lag... common apps hang/crash/load slowly on a now regular basis... whether on a strong 4g or wifi connection... kind of makes having a data plan worthless, if you ask me.

I hate to sound bitter, but I'm just giving my input. My RAZR M went from being the best phone I've ever had with Jelly Bean to the worst with KitKrap... with just one update... aesthetically and in performance. I spend every day at work on computers, so the last thing I want to do when I get off work is to screw around with my phone to try and improve its functionality... I just want it to work... So I can focus on living my life. The update has gotten so annoying that I googled "I hate Android KitKat" and this site was first to come up... So I apologize for throwing my b*tchfest out there... but again, I just want to give my input.:)
 
My Razor Maxx HD does not get the battery life it used too, 8 plus days, but I get 4-7 now. I find under times I have higher usage it drains much faster.
 
You must log in or register to reply here.
Back
Top Bottom