ehhh.. i've reverted to stock la... LOL
come KLCC, puasa month many spots to sit at

Pink unicorns is not a theme, its the ROM's logo

http://forum.xda-developers.com/showthread.php?t=2219021

that is not cute at all,i was thinking of cute cartoon pink unicorns

Ask *him* for his feminine, Hello Kitty theme collection.......

that will go well with my pink note2 im still thinking if i should root and flash it myself or let my dumb boyfriend do it

its so pink i get headaches

http://goo.im/devs/OpenRecovery/t03g/openr....6.0.0-t03g.zip

latest 2.6.0.0 TWRP for you guys

i cant try it out,still unrooted new pink note2

But you could use these, the latest maps for android .apk files

for 4.2.2 users

http://d-h.st/Lo4

for 4.1.x users

http://www.androidfilehost.com/?fid=23032113221600616

This post has been edited by alexng2208: Jul 10 2013, 04:31 PM

What are you waiting for, just root it. I think installing themes do not need root though.

Eh, I thought you would give Gwiyomiz the links to your Hello Kitty themes?

ok,i try to change the themes now,sorry new to android here,i was using the iphone before i got this cute pink note2

http://forum.xda-developers.com/showthread.php?t=1801752

go here only and only if you are on 4.2.2 (or rather CM10.1 with theme chooser)

so many themes, which is is hello kitty?

search HeKi 1.2!

crapple, the antithesis of choice.....you are now FREE to CHOOSE.

Remember, in the open source world ..... "if you break it you get to keep both parts" Nobody will sue you.

thank you,but only got some cute

i planing to root my device tonight,flash it some other day still want to play around with the samsung features

The Framaroot method is supposedly the easiest now, the other ones are more traditional. Anyway I've been rooted for so long I can't recall how it's done. You can check the links to dr. ketan's posts on XDA.

Do your rooting before midnight so that people here can help before they've gone to sleep.

You can even flash pre-rooted stock roms directly. Start your downloading now though if you want to do that, as it's about 1.2Gb in size.

Note, do not flash DME6 and/or DMF2 ROMs until Samsung has sorted the sh*t out.

ok thank you for the advice,will start to download the file when i reach home,1.2GB ? wonder if the download will finish by tonight

just saw a tweet from Google Malaysia. seems they are updating Google Maps to include turn-by-turn navigation. i'm assuming voice navigation...

nice if true... not able to check it now... data network having problems... *again* this u mobile really having issues the last few weeks...

It's true. A colleague of mine got the update. Voice navigation works. Can't wait for the update (lazy to install via APK haha)

This is wonderful.....but I use Waze more, since Google maps to date has not been very feature rich.

Maybe time to switch once you get the prompt to update?

I don't use Waze. Just relied on Google Maps if I don't know how to get to a certain place. The official voice navigation for Malaysia in the new update is a welcome plus as I have been waiting for it for a long time

i tested it from my office desk... loads kinda slow. will try this evening when i go back. but if it loads just as slow... i think i'm better off with waze.

still... both also google product la...

Some technical writeup on big.LITTLE on slashdot.

As always, reading slashdot is about reading the comments, some of which are thoughtful, some are rubbish, some are really funny.


hardware.slashdot.org/story/13/07/10/0237202/biglittle-arms-strategy-for-efficient-computing

2 comments:

Big/little is a lazy way out of the power problem... Because instead of investing in design and development and in fine grained power control in your processor, you make the design decision of, "Heck with this -- silicon is cheap!" and throw away a good chunk of silicon when the processor goes into a different power mode... You have no graceful scaling -- just a brute force throttle and a clunky interface for the Kernel.

So, not all ARM licensees have been convinced or seen the need to go to a big/little architecture because big/little has that big disadvantages of added complexity and wasted realestate (and cost) on the die. Unlike nVidea (Tegra) and Samsung (Exynos), Qualcomm has been able to thus far keep power under control in their Snapdragon designs without having to resort to a big/little and has thus been able to excel on the phone. So far, the Qualcomm strategy seems to be a winning one for phones in terms of both overall power savings and performance per miliwatt -- where on phones every extra hour of battery life is a cherished commodity. Such may not be true for tablets that can stand to have larger batteries and where performance at "some reasonable expectation" of battery life may be the more important.

================

The power difference between an A7 and an A15 is huge. There's really nothing that you could do to something like an A15 to get it close to the power consumption of the A7 without killing performance. They're entirely different pipeline structures (in-order, dual-issue-if-you're-luck vs out-of-order multi-issue). The first generation from Samsung had some bugs in cache coherency that made them painful for the OS, but the newer ones are much better: they allow you to have any combination of A7s and A15s powered at the same time, so if you have a single CPU-bound task you can give it an A15 to run on and put everything else on one or more A7s (depending on how many other processes you've got, running multiple A7s at a lower clock speed may be more efficient than running one at full speed). The OS is in a far better place to make these decisions than the CPU, because it can learn a lot about the prior behaviour of a process and about other processes spawned from the same program binary.

This post has been edited by joytest: Jul 10 2013, 05:42 PM