Galaxy Note II Forum

[Pizentu]

That smart rotation sounds awesome. I read somewhere before that it was a feature but didnt bother reading what it does. I just clicked the link and like what it does.

One thing I have read that let me down is the "multi-tasking" feature shown in the Korean release video, wont be available on release. Looks like it got scrapped.

[Ads]

[Sardo Numspa]

just read that LG may be providing the next nexus. i have no idea whats going on, will it be HTC, will it be Sammy again, will it be LG? will they all be 5"+, will they be competitors to the note II?

[Astrix]

Galaxy Note 2 Root Tutorials! [Windows/Mac/Linux] Wonderful: HERE

[Pizentu]

Looks quick and easy. Is this one of the one click root methods that I always hear about? I thought those were bad.?

[Astrix]

That not superone click method...
Its "Odin", tool you need for Samsung devices.

Work similar to RSD Lite to flash SBF file on Xoom

[Astrix]

Motorola Nexus benchmark? http://www.theandroidsoul.com/androi...tu-benchmarks/

[Astrix]

Sad...for the future off AOKP, AOSP, PA which will base on CM Build for SN II

Just an FYI:

I not only have no interest in purchasing a device, but if you gave me a free one and offered $2000, I would say no.

I have better things to do than waste countless hours of my time fighting another non-Nexus Exynos.

xplodwild may be more receptive to continuing with Exynos, but at least in the case of myself and codeworkx, we are done. Our current devices are going to be our last Exynos devices unless Samsung makes major changes.

There's a difference between challenging, and utterly freaking impossible.

Challenging: Going through source and fixing bugs or adding new features. For example, for months I've wanted to try and rework the Exynos suspend/resume code to be more power efficient. (It locks cpufreq at 800 MHz and disables cpuidle for the entire suspend/resume cycle, which eats power. Also SOME interrupt service handler eats huge amounts of CPU on resume (the root cause of the classic Gingerbread "Android OS" bugs), and I'd like to figure out which one and see if it can be optimized.

Utterly freaking impossible: On a routine basis, figuring out what Samsung broke in their blobs and why it doesn't work the way it should. Trying to take totally broken nonfunctional source code and get it to work properly with zero documentation. See hwcomposer - unless a miracle happens, we will be continually stuck fighting blobs that Samsung gave us. Their blobs have some sort of significant magic not present in any reference source. The reference source creates a broken piece of **** that's almost indistinguishable from not having any hwc at all.

I've spent 10-20 hours or more per week of my spare time over the past three weeks fighting hwcomposer and making absolutely zero progress. I'm tired of flailing against a brick wall and getting nothing other than bloody knuckles.

No, porting CM10 won't be easy due to shared hardware with the S3. Have you noticed no Exynos device has M builds? Have you noticed that Exynos devices are almost always one of the last "flagship-class" devices to receive nightlies?

CM9 should never have been marked stable on Exynos devices - too many bugs remain and we lowered our standards for "stable" too much.
CM10 on Exynos is incredibly far from reaching M builds let alone a stable release and I don't think we have the manpower, motivation, or energy to take it to to the finish line, let alone the documentation needed to do so.

And what about CM11? The whole mess will just start all over again, if any maintainers are left on Exynos by then. Again, we'll be flailing against undocumented crap that didn't even quite work right with the Android version it was designed for, while those working on platforms that have proper documentation and reference source (OMAP and Qualcomm) will start moving ahead immediately. See JB on Qcoms - They took only a month or two to get ahead of where Exynos4 devices are NOW, 4-5 months after JB went live, and over half of the work those guys were doing was forward-merging CM customizations from CM9.

Thread: http://forum.xda-developers.com/show...php?p=32436753

[Sardo Numspa]

yeah, def not good for sammy phones.

maybe new nexus for me if devs are going to start jumping ship on exynos/sammy combos

[Astrix]

yeah, def not good for sammy phones.

SGN II is good...
But frankly I seldom use the SPen features
There are work around GNote for the SPen to run on non TW Base rom.

Maybe you can try SGN II..once next Nexus release if with better spec...can sell the SGN II

maybe new nexus for me if devs are going to start jumping ship on exynos/sammy combos

Nexus exynos still supported by CM as code easily available by Google not Sammy.

The issue of Nexus rumor...NO external SDCard same like iPhone sux

[Sardo Numspa]

Nexus exynos still supported by CM as code easily available by Google not Sammy.

thats why im going to wait and see what the next nexus is. only another month or so........