Very very briefly, you have 2 classes of ROMs for Android devices in general. One is based on stock ROMs for the device (TouchWiz in the case of Samsung), the other is based on Google's AOSP (Android Open Source Project).

TW (short for TouchWiz) based custom ROMs usually retain and ENHANCE the available stock apps, and give you some extra features like being able to control CPU speed, screen color values, switch DPI etc. They are also known as "cooked" ROMs, and the authors are called "chefs".

You usually get all the Samsung stuff available, unless it's a "slimmed" ROM where the chef has cut out what they feel is unnecessary.


AOSP ROMs, since they are from the freely available Google sources, can be recompiled by developers and features added, optimized or subtracted depending on the philosophy of the dev team. These are "compiled" ROMs and the developers are called developers, not chefs.

AOSP ROMS do not contain the Samsung specific features of TouchWiz like S-View or whatever "S-something" app bundled by Samsung, but since this is Android, there are either replacements or close equivalents of the same apps on the Play Store.

Note that even if you use AOSP, you DO NOT lose the S-pen function, only the S-applications that use it. Any other drawing app can still use the S-Pen.

It's all a personal preference and getting used to a specific ROM type's features. See post 9, the sifus there all use a wide variety of ROMs, and the "flashoholics" change ROMs as often as they, um, make their beds I suppose.

Choice is the key word of Android.

One thing to note, is the S-Note app. It is a fantastic piece of software from Samsung, but unfortunately it only works on the Note family. This is a form of lock in. To avoid this, I recommend HandyNote Pro or others here may recommend other S-pen note taking apps.

Ok hope that was a sufficient introduction.

alexng2208 or antt00 or noobi3 can provide you with more excruciating details of all the ROMs they've experienced.

Darn I wish someone would pay me......

Thanks ... $quid$ pro quo.........

I saw your other thread. You are a very smart person. Better root your own device. And you can implant some nanotech stuff in your bf to improve his performance.

Good to have EE person with embedded linux knowledge. There is another guy doing that here.

flashing is halal too right?

I think the dev is halal....just the produce of that region is decidedly not

ZoidbergFry he is in Penang. Are you also in Penang?


You're probably correct. Otherwise a parallel import set is fine at current prices.

Yes yes, forgot to post up. Nanti nanti.

Errr .... he enjoys Futurama, as do I, and it is full of risque references and intellectual comedy.

Then again, embedded device programmers are probably a male dominant discipline, more so than general EE I guess. You've been there and seen how it's like in Uni, so I think you shouldn't have a problem.

Maybe you could give us a quick enlightenment on embedded programming. Is it largely focused on sensor input? Booting and instructions should still be similar to general purpose computing right?

Put on your impenetrable diamond nanocoating !!!!

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

ycs your results added. New record leh !!

Dr Zoidberg:
http://en.wikipedia.org/wiki/Zoidberg

Philip Fry:
http://en.wikipedia.org/wiki/Philip_J._Fry

Both these characters are good comedy material. Have you ever watched Futurama? Far more cerebral and enjoyable than The Simpsons.

Ok go have fun with your Note 2 and prepare to root !!!

Amoi arrr....rooting doesn't change anything on your phone laaaa. It just adds SU and allows root access and rwrrx controls with chmod etc.

It's what you do AFTER rooting that may or may not have further impacts.

AOKP? With all the pink unicorns?

She said she wants pink unicorns laaa .... the "horny" horses...... oh well where's your Hello Kitty theme collection?

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

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?

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.

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.

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

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

How people tend to use social media