[ROM][4.3][ CM 10.2.] Unofficial CM 10.2 for Galaxy Note II (N7100)

What DPI Should the ROM run at?


  • Total voters
    647
Search This thread

pulser_g2

Admin Emeritus / Senior Recognized Developer
Nov 27, 2009
19,537
11,595
It appears there is a new CM on the way... And it appeared it wasn't available for the Note 2... And that made me disappointed, so I set out to put that right.

4.3 is a small update from 4.2. Unfortunately, Google also decided to change almost everything about filesystem mounting. And Samsung exynos devices are a hotchpotch of everything...

Today, xplodwild and I carried out a war of attrition against the nasty Samsung devices. Firstly, there remains a battle-scar in the form of graphics, where we had to disable the ability of the device to screenshot itself. You'll see this in the lack of thumbnails for your long-press-home task switcher. #Blame-Samsung

Storage was a nightmare, but I have finally beaten it into submission. It should now work. Nicely. And properly. At least for now.

Because open source is wonderful, a VERY messy device tree (commits need squashed etc) - https://github.com/pulser/android_device_samsung_n7100/

I suggest a wipe before flashing, but I have tested from 4.2.2 and should be OK actually, maybe some apps will cry, but that's not my problem :)

Link: http://goo.im/devs/pulser/N7100/CM/cm-10.2-20130810-UNOFFICIAL-n7100.zip

Pretty much everything is working and tested - you shouldn't have any issues getting it to boot. The other version posted appears it may have issues booting, but I was not aware of its existence until just now. Actually, seems there's no link in the other thread, give this a shot, and see if it helps you. There's a lot of issues on Exynos devices when doing any kind of update... Sneeze and it might explode!

XDA:DevDB Information
Unofficial CM 10.2 for Galaxy Note II (N7100), a ROM for the Samsung Galaxy Note II

Contributors
pulser_g2, CM Team
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
Based On: CM 10.2

Version Information
Status: Alpha
Current Stable Version: N/A
Current Beta Version: 10 August
Beta Release Date: 2013-08-10

Created 2013-07-30
Last Updated 2013-08-10
 

_delice_doluca_

Senior Member
Apr 26, 2011
569
153
35
istanbul
Thanks,

Trying now and will report.

BTW (off-topic but... I believe necessary when it comes to AOSP and Exynos) When I click on your githup link the Audio recording fix is on top of the list for 6 months ago, which reminds me; we have never got the chance to see CM 10.1 recording audio properly on videos or sound record apps (not saying it is mono but the sound is terrible actually).. For now it seems the only thing that prevents me (and some others I guess) from using any AOSP ROM as a daily and "fully functional" driver is this problem. Any chance that we can see 10.2 have proper audio recording? Since our voice is recorded just fine on calls we can say the mic is working as it should on both at earspeaker and the loudspeaker. So, there is a software which can use the mics properly and I -with all my heart and never-ending hope- believe this software could be also used for good sounded video recording or help us not to shout too much for Google Now :)

Thanks for reading. And the ROM :)

---------- Post added at 01:06 AM ---------- Previous post was at 12:43 AM ----------

It boots just fine. So is everything so far.
 

Eric-Mod

Senior Member
Jun 26, 2012
765
662
Austria
Vivo X70 Pro+
Will try this new one tomorrow... Thanks!

BTW. Is anyone using GoBackup Pro or Titanium Backup? I had an issue on my Nexus 4 running 4.3 .

They didn't restored my Apps. Since the Note 2 uses a SD Card Slot, would it be the same issue?

Gesendet von meinem GT-N7100 mit Tapatalk HD
 

Mohammed779

Senior Member
Dec 28, 2012
1,260
553
Downloading and trying it right now :D I'll be giving a feedback :D

Sent from my GT-N7100
 
Last edited:

pulser_g2

Admin Emeritus / Senior Recognized Developer
Nov 27, 2009
19,537
11,595
Will try this new one tomorrow... Thanks!

BTW. Is anyone using GoBackup Pro or Titanium Backup? I had an issue on my Nexus 4 running 4.3 .

They didn't restored my Apps. Since the Note 2 uses a SD Card Slot, would it be the same issue?

Gesendet von meinem GT-N7100 mit Tapatalk HD

No issues, my testing process includes restoring from titanium backup, with data, from external SD
 

pulser_g2

Admin Emeritus / Senior Recognized Developer
Nov 27, 2009
19,537
11,595
Thanks,

Trying now and will report.

BTW (off-topic but... I believe necessary when it comes to AOSP and Exynos) When I click on your githup link the Audio recording fix is on top of the list for 6 months ago, which reminds me; we have never got the chance to see CM 10.1 recording audio properly on videos or sound record apps (not saying it is mono but the sound is terrible actually).. For now it seems the only thing that prevents me (and some others I guess) from using any AOSP ROM as a daily and "fully functional" driver is this problem. Any chance that we can see 10.2 have proper audio recording? Since our voice is recorded just fine on calls we can say the mic is working as it should on both at earspeaker and the loudspeaker. So, there is a software which can use the mics properly and I -with all my heart and never-ending hope- believe this software could be also used for good sounded video recording or help us not to shout too much for Google Now :)

Thanks for reading. And the ROM :)

---------- Post added at 01:06 AM ---------- Previous post was at 12:43 AM ----------

It boots just fine. So is everything so far.

This sounds like something more for the guys that did the work on the audio HAL. I've not looked into the solution, but audio on these devices is a dirty hack with tinyhal
 
  • Like
Reactions: Volvomarques

lolmensch

Senior Member
Jul 14, 2009
1,374
304
FarFarAway
there are some occasional rendering glitches with the stock browser while loading a page and scrolling through. nothing majorly bad but still visible at times. :p
(independent of the webpages i visited)

despite that I didn't come across any other bugs. once again great job :good:
 

jcrompton

Senior Member
Nov 30, 2004
4,256
751
61
Hurricane, WV
Google Pixel 5
Re 4.3 in general

I have been testing 4.3 on an "old" device , my Nexus S, the last couple of days. Interestingly, the device was much smoother than 4.2 based ROMs, at least on that limited processor device.
Once this all gets ironed out is there reason to believe that 4.3 will be better for our Note 2's?

Thanks for your work !
 
  • Like
Reactions: LaM00Na

pulser_g2

Admin Emeritus / Senior Recognized Developer
Nov 27, 2009
19,537
11,595
I have been testing 4.3 on an "old" device , my Nexus S, the last couple of days. Interestingly, the device was much smoother than 4.2 based ROMs, at least on that limited processor device.
Once this all gets ironed out is there reason to believe that 4.3 will be better for our Note 2's?

Thanks for your work !

It really depends on your use cases...

I can make the fastest and most cutting edge android phone lag like crazy without installing anything silly...

I just need to type at my full speed on SwiftKey for about a minute and it will be lagging pretty horrendously. That's a bad app - SwiftKey is very poor lately for performance.

Why do I mention this? Well, your definition of better or smoother will really depend on what you are doing. Android is a horrendously complex operating system. It is ridiculously inefficient in many ways such as how data is presented to the user.

As such there are many badly written apps which will slow down your device. I reckon unless Google considers using native code for drawing the screens, we will never reach the true smoothness the hardware is capable of.

At the end of the day, a particular apple phone is available with lesser processor, graphics and RAM. Yet it offers smoother in-use performance because of its use of native code where possible, rather than a virtual machine based language like java.

I don't think it seems significantly faster than 4.2, but I probably am hard to please. I simply despair as I look at the code in android... All the nasty object orientation and strange ways to to things... Each and every time it happens, the java virtual machine must run instructions.

I reckon if you reduced the number of lines of code used to achieve simple tasks like show the settings menu (which is horrendous with resources in countless files and java classes), performance would be vastly superior.

Probably not much of an answer, but if anyone else is irritated by the horrendously inefficient code in android, I've finally found someone else who sees it!
 

jcrompton

Senior Member
Nov 30, 2004
4,256
751
61
Hurricane, WV
Google Pixel 5
That actually helps a lot. I think the processor and the device makes a difference too with the Nexus S being a "Google" device and the Note 2 being Samsung.

I just notice that when browsing Tapatalk that seems to be my main gauge - the scrolling seemed pretty smooth even on the Nexus S.

I read in the Nexus thread that the 4.3 code was written to run with less sytem resources but I wasn't sure of the source of that comment.

---------- Post added at 09:11 PM ---------- Previous post was at 08:45 PM ----------

IF YOU LOSE ROOT WHEN INSTALLING 4.3


I lose root when I install this ROM but if you will flash the newest update from Chainfire you will re gain

http://download.chainfire.eu/344/SuperSU/UPDATE-SuperSU-v1.50.zip
 
Last edited:

alexng2208

Senior Member
Nov 2, 2012
59
13
That's amazing!!! great help and flashing now! :)

update: AOSP keyboard having FC
everything else within expectations. no problem with using the ROM so far!

amazing amazing effort and feels like 95% finished product!
 
Last edited:
  • Like
Reactions: aegeuss

gamesz2

Senior Member
Dec 10, 2010
770
169
29
holland
I want 2 try this but i read someone lose the root of his phone... Some other people also that problem?



Sent from my Galaxy Note II using xda app-developers app
 

Mohammed779

Senior Member
Dec 28, 2012
1,260
553
I want 2 try this but i read someone lose the root of his phone... Some other people also that problem?



Sent from my Galaxy Note II using xda app-developers app

You loss the root, HOWEVER, If you read that guy's post, he Said flash that file and you'll get root..

Im other words,

1. Flash CM10.2
2. Flash Gapps
3. Flash the file from the previous post

Sent from my GT-N7100
 

alexng2208

Senior Member
Nov 2, 2012
59
13
You loss the root, HOWEVER, If you read that guy's post, he Said flash that file and you'll get root..

Im other words,

1. Flash CM10.2
2. Flash Gapps
3. Flash the file from the previous post

Sent from my GT-N7100

thanks! i flashed the 10.2 with the older official gapps... nothing seems to be wrong with it and everything is working

do you know what is new with the latest GApps as attached a few posts above?
 

Eric-Mod

Senior Member
Jun 26, 2012
765
662
Austria
Vivo X70 Pro+
Flashed it, and it's working good. For the 1st Build it's working quite fine. But the camera (app?) isn't working properly. I took one pic, the camera froze, and when I launched the camera again, it said "No connection to camera".

It's the first build so yeah.. this can happen of course :D
 

Top Liked Posts

  • There are no posts matching your filters.
  • 509
    Alas, ladies and gents... The Cyanogenmod team have managed to surpass even themselves in misdirection and disorganisation. I honestly am surprised just how absurdly short-sighted they are. Seriously. In fact, I would like to suggest that anyone who feels strongly about this lets them know about it as loudly as they deem necessary.

    There is one individual, Ricardo Cerqueira (aka arcee), who seems to have single-handedly decided to go and remove huge sets of features from CM. Particularly device specific ones, under the auspices of "tidying up the settings menu". Sure, by all means have a go, but don't REMOVE functionality in the process... If you must do it, do it a step at a time - remove the features from "Advanced" as they are created into the new menu.

    By way of example, recent builds have removed the Advanced menu, offering you amongst other gems, the ability to change HSPA/HSDPA/HSUPA modes, as well as to disable the incredibly annoying button backlights on the soft keys on the note 2. Oh, and the ability to remove Samsung's garishly over-saturated colours of the AMOLED screen.

    All this comes from the same individual who denied Mako (nexus 4) users many advanced options, because of his own personal dislike of the "Advanced" menu. While I cannot find any public acknowledgement of this, Nexus 4 users were denied many features and tweaks due to his maintainership of the device, and there are countless occurences where his own dislike has emerged in private, hidden discussions, that you are being kept from... Such as, for example,

    him said:
    There's a difference between changing the devices, and putting DeviceParts in there. I hate the whole concept of DP, and will not deploy it into a device of mine; I am, however, willing to step down as mako's maintainer if that becomes a problem.

    and

    him said:
    It's no secret that I have a very strong dislike for our current concept of "device parts" apps

    Want some more proof? He was told about all these features on our devices.

    +Ricardo Cerqueira You should have a look at galaxys2-common/smdk4412-common DeviceParts. We have HSDPA settings, vibrator, mDNIE Mode/Scenario, touch sensitivity, audio dock, sensor calibration, and a few others.

    And here's his reply:

    him said:
    Heh. Almost all of those are a examples of why DeviceParts should die. Kitchen sink much? Touch sensititivy, really? Just because you can do something doesn't necessarily mean you should :p

    This was met with another reply from another sensible developer, pointing out the need for these features.

    I can vouch for touch sensitivity on Acer A700 though.
    1) Stock comes with it - being feature-complete
    2) The stock sensitivity setting sucks in some cases, I've added an kind-of-overclock "Very high" setting which helps, but we obviously don't want to ship with that as default.
    Galaxy S also has HSDPA setting which is known (or at least believed by users) to have substantial affect battery life. mDNIe because some users prefer screen post-processing on (stock Galaxy S) and some prefer them off (stock Nexus S).

    Ask yourself - why were users not made aware of this discussion? Why were these changes decided by one man on his own personal crusade? Why was there no consultation carried out before his own personal dislike was imposed upon us all?

    Alas though, these discussions take place in secret, behind closed doors, which you and I do not see, because we are not felt "worthy" to see what happens there. Have no fear though, for I shall expose each and every one of these things, including the upcoming commercialisation of CM.

    Yes, that's right... You heard me right - CM are attempting to now licence all new contributions as dual GPL and commercial licence. Why? To allow them to go on and sell the rights to the open source code to third parties. And one of their own "leads" even tried to strong-arm a valued contributor into re-licencing his work. I had to step in there, and point out they actually had no right to do so, as the contributor agreement doesn't cover that eventuality. Nonetheless, his attitude was frankly horrendous, TELLING the contributor it would be relicensed, not asking permission. That's gone quiet for now though. The reason they want to be able to licence the code commercially? To allow them to sell YOUR contributions to a third party, such as an OEM or carrier, who wants the features, but doesn't want to follow the open source licence of a GPL component.

    They're also selling out and going commercial - there's rumours around the internet, but a little bit of smart thinking will lead you to the answers.

    Unfortunately, due to CM now trying to be as secretive as possible, you probably won't see any of this elsewhere. They are making every effort to be as closed as possible in their structure, and decision making processes. That means you, the user, are running code where the changes are arbitrarily decided with no input by yourself, beyond the "false" pretence of their gerrit instance.

    There are significant contributions made to CM which bypass their gerrit code review (mainly upstream merges), but also other large pushes. There is also the "submit and +2" mentality from their leads, where their own contributions are beyond testing, and should be pushed immediately, often leading to breakages.

    There is a lot more going on, and I will expose more and more of it. Please encourage your beloved CM people to have a look at this. Also, let them know that their "secrets" are not safe, since they are ridiculously easy to find on the internet. So if they try to stop me finding things out, I will simply share more and more with the world. Fair is fair, right? The less open CM are, the more open I will be. When you're running code on your device, you expect the developers to be open, upfront, and honest with you, right? Is that happening?

    What does this all mean? Well, there won't be any new "upstream" builds for a while, until I resolve a few issues such as the major removal of important features, thus crippling CM from being usable. I need to figure out what to do, whether it's re-adding them, or rewriting the settings to work properly. It will be worth it in the long run though! Trust me on that ;) I might introduce some more #nicethings :)

    Finally, if any of the CM leads wish to engage in a dialogue about this, feel free. You can do so, in public, here because the public trust you in running your code, so why not trust them in return? Or is this a trustless relationship? Perhaps your users should stop trusting you?

    More to follow ;)
    129
    It appears there is a new CM on the way... And it appeared it wasn't available for the Note 2... And that made me disappointed, so I set out to put that right.

    4.3 is a small update from 4.2. Unfortunately, Google also decided to change almost everything about filesystem mounting. And Samsung exynos devices are a hotchpotch of everything...

    Today, xplodwild and I carried out a war of attrition against the nasty Samsung devices. Firstly, there remains a battle-scar in the form of graphics, where we had to disable the ability of the device to screenshot itself. You'll see this in the lack of thumbnails for your long-press-home task switcher. #Blame-Samsung

    Storage was a nightmare, but I have finally beaten it into submission. It should now work. Nicely. And properly. At least for now.

    Because open source is wonderful, a VERY messy device tree (commits need squashed etc) - https://github.com/pulser/android_device_samsung_n7100/

    I suggest a wipe before flashing, but I have tested from 4.2.2 and should be OK actually, maybe some apps will cry, but that's not my problem :)

    Link: http://goo.im/devs/pulser/N7100/CM/cm-10.2-20130810-UNOFFICIAL-n7100.zip

    Pretty much everything is working and tested - you shouldn't have any issues getting it to boot. The other version posted appears it may have issues booting, but I was not aware of its existence until just now. Actually, seems there's no link in the other thread, give this a shot, and see if it helps you. There's a lot of issues on Exynos devices when doing any kind of update... Sneeze and it might explode!

    XDA:DevDB Information
    Unofficial CM 10.2 for Galaxy Note II (N7100), a ROM for the Samsung Galaxy Note II

    Contributors
    pulser_g2, CM Team
    ROM OS Version: 4.3.x Jellybean
    ROM Kernel: Linux 3.0.x
    Based On: CM 10.2

    Version Information
    Status: Alpha
    Current Stable Version: N/A
    Current Beta Version: 10 August
    Beta Release Date: 2013-08-10

    Created 2013-07-30
    Last Updated 2013-08-10
    45
    @pulser_g2

    You know, I can't help but to think what would YOU or another moderator or XDA staff member say if this same exact post http://forum.xda-developers.com/showpost.php?p=44746084&postcount=548 was made by a junior member with less then 10 posts?

    I'm sure I would see replies like....

    Quit complaining you troll or If you don't like it, go make your own ROM or just straight up bashing.....OR maybe the entire post will just disappear and that member would get a warning/infraction....who knows!

    With that said, I also can't help but to see the hypocrisy that's taking place here!

    I've been on XDA for a while and I've seen similar posts like this made by several dozen members only to have them either removed or force that user to just say F it and remove it themselves because of the negative feedback that they got.

    BUT....here we are and you, an Admin and RD made a post just like those that were removed in the past YET you got 60+ thanks and NOT one person has dared to tell you to quit complaining or go make your own ROM.

    No sign of a moderator or a fellow Admin or NOTHING....

    I mean, believe it or not...CyanogenMod doesn't report to XDA.

    Is their ROM. If they want to remove everything and anything.....is their ROM! Simple as that!!

    BUT here's where the real problem lies...By you saying "I would like to suggest that anyone who feels strongly about this lets them know about it as loudly as they deem necessary" that's no better then someone trying to start drama by saying "If you don't agree with something, let's rate their thread 1 star and let them know" or whatever

    The way I'm seeing this and maybe others might of seen this but are afraid to say anything is that you're using your title and authority to get people to turn on CM, specifically Ricardo Cerqueira. That to me is BS! Especially since you're an Admin......you're suppose to know better!

    NOW, I ask you.....isn't that the total definition of being a hypocrite? You doing something that your staff punishes others for doing?

    How are you as an Admin suppose to issue infractions and come down on people for things that you yourself are doing?

    Maybe this post will get deleted or HELL....maybe I'm the one that will received the negative feedback but I'm tired of seeing this happen on XDA time after time after time!

    Is really just BS! You as an Admin, are able to speak out and actually start drama BUT if a junior member that NOBODY knows of was to do the same exact thing......he or she would get their ass torn up!

    I honestly think that as an Admin you should NOT be trying to start drama and getting people to turn on CyanogenMod just because you're unhappy with a decision that is made or going to be made in THEIR ROM....an open source ROM.

    Just my 2 cents....
    39
    Those decisions were probably met because those are hacks, not features. CM grew from a slob of hacks to a mature project.

    The trouble is, they're not hacks... Samsung includes MDNIE colour profiling in its own ROMs. Likewise they include a feature to disable the soft key lights or adjust the timeout (I personally hate them).

    But the whole idea is that even Samsung gives you the choice of what you want - there's no need for one person to select what he feels is the best - a default is picked and others simply adjust that setting.

    Personally, I intend to reintroduce this feature for colour calibration, but default to the most natural and accurate colour reproduction. Of course those who want the AMOLED colours can get them by picking an option. But colours viewed should be more life like, and accurately reproduced, out of the box.

    The point is user choice - there is a big trend of CM towards the "apple way" - someone else makes your decisions for you, and you're stuck with them...

    Is that why any of us are here on XDA?
    24
    there are countless occurences where his own dislike has emerged in private, hidden discussions, that you are being kept from...
    Ask yourself - why were users not made aware of this discussion?

    You mean like the moderators in the secret moderator forum, the developers in the hidden developer forum, and even the news writers in their secret news writers forum...all making decisions with little to no input from the every day users on XDA?

    Come on man, I get that you're pissed off here, but at least make a point that doesn't make you sound so...hypocritical.

    *You decide who gets banned and who doesn't in secret moderator forums where no average user has ever been. Why isn't anyone made privy to those discussions?

    *The countless development discussions in the secret developer forums that none of us normal people have EVER been a part of. You get mad at CM for having private, hidden discussions...then you have a whole hidden forum for your devs to do the exact same thing.

    *The XDA design decisions, rule decisions, etc are all done by like a maximum of 4-6 people.

    If you're going to sit there and try to tell all these people that you, yourself, aren't having hidden discussions with other XDA devs in the hidden dev forum about this very incident (and probably another one in the secret moderator forum for that matter) without letting everyone in on it, then forgive me for saying so, but you're full of crap dude. You guys plot behind closed doors more than most governments. Not to mention all the horrible things I've seen you people say about the average user on XDA (and everywhere else for that matter).

    I used to be behind those doors and the only thing I walked out of those doors feeling proud about was that I was the only person in any forum back there that put the 5.5 million people in these forums first and you guys didn't. Geez man, find another way to complain.