RM160++ including shipment. will work on any machine running Chrome browser.

nope. think CM is working on that.

it should not be difficult to make it work, you just need to run a steaming server in the phone (basically just a web server) and tell ChromeCast to stream from your phone. what it means is that you need an app to do it actually, that's the reason i bought this, wanna try develop some stuff for it.

that mean you have a (generally) better CPU. it usually means you can over clock higher and under volt lower.

nope. the CPU will not change by changing Kernel / rom. but some kernel may interpret the bin number differently. Stock kernel has the following numbering:



https://android.googlesource.com/kernel/msm...puclock-krait.h

Meaning, slow=0,nominal=1,fast=2,faster=3

This post has been edited by cowithgun: Oct 28 2013, 10:40 AM

Waiting for Kitkat? Here's something to cheer you up while waiting...

huh? where is the link to this comparison?

i have the old Samsung Galaxy W, iPhone 5 and Nexus 4 (main)... seem like same only... never really compare the reception though...

if you really wanna know:

"Anyhow, the Nexus 4 is a dramatic improvement. It includes the latest and greatest 28nm Qualcomm baseband (MDM9215M), their flagship transciever (WTR1605L) and includes full receive diversity on all WCDMA bands."

http://www.anandtech.com/show/6440/google-nexus-4-review/8

about iphone 4s snappier... hmm i have iPhone 5, tested before and after iOS 7...it's smooth, just as smooth as my nexus 4.... again, non-scientific testing...

comparing bar is a little too vague since apple tends to display higher bar compare to android although the signal strength (-dBm) is about the same.

http://www.metalev.org/2010/07/android-vs-...l-strength.html

next time when you wanna compare, try this:

iPhone:
call *3001#12345#*

that will show the signal in -dBm instead of bars... when you quit the field test app, it will revert back to bars

android:
setting, about phone, status

anyway, iPhone is not some cheap phone... i am admired by their hardware... so, even if their signal strength is better, i m not surprise... i just dont think it'll be a lot of different since nexus 4's MDM9215M should be quite good too.

If you plan to keep your data (and app) just make sure you don't run the flash-all.bat in the stock ROM to revert back to stock.

Do like this instead:

https://forum.lowyat.net/index.php?showtopi...&#entry63042233

Change the name of the file accordingly once u downloaded the stock 4.4.

I check 1 hour ago, only ROM code uploaded... i check again just now, even the Kernel code is uploaded!

ROM: https://android.googlesource.com/platform/b.../android-4.4_r1
Kernel: https://android.googlesource.com/kernel/msm/
(hmm not 3.6 kernel as speculated)

Will try compile it this weekend when free...

one interesting feature in the new Android kitkat 4.4...

zRAM... i remember i added this to my custom ROM for Galaxy W back then.

it's actually a RamDisk. so, most frequently used stuff can be stored here. it will allow faster access than reading from your flash memory.

but, in low RAM device such as Galaxy W, with only 512mb, allocating a RamDisk will even make available memory even less for OS and app.

the solution, zRAM. you compress the RamDisk. the trick is to use Zip algorithm that can unzip REALLY fast. we can forgo the compress time, it's ok to be slower because we only compress when we store something. what is really important is ACCESS time. which mean the decompression time. i used LZO algo back then.

nice to know some of this old stuff coming back to the new Android.

TLDR: custom ROM/kernel developer has been using some of these stuff in 4.4 wayyyyyy back ehhehe

This post has been edited by cowithgun: Nov 1 2013, 10:55 AM

Seem a lot with Power Button issue. May be I am one of those lucky enough to have no issue with the Power Button. I used it regularly. Not using any of those Swipe-to-wake stuff. The button work without issue.

*touch wood*

Been using it since Jan.

Have not got time to play with Kitkat source. One feature I like in Kitkat is the new Screen recording capability. I used to make video recording from another phone to show the smoothness of Nexus 4.

http://www.youtube.com/watch?v=G_OXPaZZqpM
http://www.youtube.com/watch?v=EdANiGGcJPE

I guess it's now possible to record those with just:



Read more: http://developer.android.com/about/versions/kitkat.html

Introducing Android ART

Another underlying feature of Android Kitkat is a new Android Runtime (ART). Since the dawn of time, Android has been using Dalvik to execute your APK. Your App, which normally in a form of APK, are essentially partial compiled code. Dalvik is responsible into unzipping and using Just-In-Time, compile it and execute it, it does this every time you start an App.

Meet ART, this is a AOT (Ahead-of-Time) compiler. What it will do if you enable this option in Kitkat (developer option), it will recompile your APK into full machine language and keep it that way. Once in full machine language, your code should run at full speed. And without starting additional Dalvik VM overhead, you also freed up some memory.

Read more:

http://www.androidpolice.com/2013/11/06/me...buts-in-kitkat/

My personal take on this is that, with today's fast CPU, the gain is probably not as much as in the link above. However I suspect the best benefit is without Dalvik, you could free up some more RAM on low memory device. Don't really know for sure. Will test this out... if I am free.

This post has been edited by cowithgun: Nov 7 2013, 06:59 PM

awesome! first hand experience! thanks for sharing.

although i love performance... disabling f sync is 1 of those tweak i refuse to do on my phone.

what good is performance if the phone is not stable? chance of losing data? don't do it!

more about f-sync here:

http://forum.xda-developers.com/showthread.php?p=33381928

Dynamic F sync by faux123 is also not recommended (by me). it simply enable / disable f sync based on screen on/off.

if you benchmark a phone with f sync off, you should see increased in performance in IO benchmark. some benchmarking program (looking at Quadrant) put too much score in IO score. making it look like huge jump in performance.

in actual fact, the performance gain is not noticeable (by myself). especially when we have 4 core CPU and fast flash memory. on top of that, Android smart enough to cache app after they first used in memory. with 2gb, and if you do not explicitly close the app from task manager, there is almost 0 IO activity when you re-launch an app.

so, short answer, PLEASE don't DISABLE F-Sync.

i had to restart my phone the other day to upload a new kernel... but i capture my Up Time, just to share that, for a stable phone, you don't really need to reboot, etc. i have 547 hours of up time. (Setting, About phone, Status)



This post has been edited by cowithgun: Nov 11 2013, 11:03 AM

the delay of OTA 4.4 could be caused by dm-verity.

http://source.android.com/devices/tech/sec.../dm-verity.html

in the past few updates, Nexus OTA uses binary patch. so, the OTA you download only contain the differences (patch) in a binary form. so, the OTA is small. but the requirement is that the original file is required.

old file + patch = new file

so, for custom ROM/kernel, even if u just modify 1 byte in build.prop, the update will fail. you can do the bin patch yourself with OTA using this tool: http://www.daemonology.net/bsdiff/

the dm-verity, take things to the next level. the hash is calculated block by block (typical 4k size) instead of file by file.

any future updates (OTA) as advised by that link should use block update method. this kind of update is mostly for kernel/radio and should not affect end user app, which is not protected by dm-verity.

or... may be the delay simply caused by qualcomm or other manufacturer late in providing the update binary? (since source is up for sure)

RAGE!!!

first you don't support Galaxy Nexus!

now, no transparent bars!

http://phandroid.com/2013/11/12/nexus-7-10...er-with-kitkat/

i give Google -1 for these...

If you want to update your n4 to kitkat but not deleting your app/data (and keep your custom recovery):

0. Backup your phone (CWM / TWRP) and copy to your PC
1. Download Nexus 4 kitkat firmware https://dl.google.com/dl/android/aosp/occam...ry-75ccae7a.tgz
2. Extract the tgz (use 7zip)
3. Extract the image-occam-krt16o.zip
4. Use the following adb command:

adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot

it should work..

(standard disclaimer applied... i m not responsible for sheit if anything happen to your phone or you )

This post has been edited by cowithgun: Nov 15 2013, 11:00 AM

good idea... but i m lazy..

(in this case, the "Recovery" partition not used... except for step 0 which you need to backup your phone.)

taste of kitkat?



This post has been edited by cowithgun: Nov 15 2013, 10:58 AM

Good thing i NEVER use Titanium backup...

I am now using Hangout as my SMS manager cool

ignore the userdata.img, it just 100mb of NULL... placeholder...

So, I am still quite upset why the Transparent bars is not available for Nexus 4 in Kitkat... but i still want it...

So, I downloaded Nexus 5 firmware, extract the GoogleHome.apk and install it into my Nexus 4.



I also decoded the GoogleHome.apk, it's really just a stub that call the Google Experience in the new Google Search.

So, if you want this, update kitkat, update your Google Search and just install the GoogleHome.apk.

http://arstechnica.com/gadgets/2013/11/and...ughly-reviewed/

PS: exclusive my @ss... ┌∩┐(◣_◢)┌∩┐

This post has been edited by cowithgun: Nov 15 2013, 01:15 PM