[Firmware][GT-N7000][4.2.1] CyanogenMod 10.1 unofficial builds // discussion thread

Search This thread
By:
Advanced…
prohexa

prohexa

Member
Feb 19, 2012
31
6
se1988 said:
Will there actually be more 10.1 nightlies? I thought that 10.2 had replaced 10.1 a couple days ago...
Click to expand...
Click to collapse

GeeckoDev said:
Woops, you are right. Switch straight to the latest CM10.2 or grab the latest CM10.1 and flash my kernel on top of it.
Click to expand...
Click to collapse

Thanks for the answers! But I'm a bit surprised that 10.1 didn't even make it to an M or an RC until it was dropped for 10.2... Haven't there been a lot of talk about Samsung sucking hard and foobar:ing the sources so much that the CM superdevs are thinking of abandoning future support for the Note? :confused:

What about the "slow" issue? Is that about the new hwcomposer that has recently been discussed in the 10.2 thread?

Regarding the kernel, what makes your kernel an better option than the "original" in CM10.2?

Thanks again!
 
E

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
prohexa said:
Thanks for the answers! But I'm a bit surprised that 10.1 didn't even make it to an M or an RC until it was dropped for 10.2... Haven't there been a lot of talk about Samsung sucking hard and foobar:ing the sources so much that the CM superdevs are thinking of abandoning future support for the Note? :confused:

What about the "slow" issue? Is that about the new hwcomposer that has recently been discussed in the 10.2 thread?

Regarding the kernel, what makes your kernel an better option than the "original" in CM10.2?

Thanks again!
Click to expand...
Click to collapse

The Note is no longer the primary device for anyone on the team, and hasn't been for months. It's basically surviving via inertia - fortunately, 10.2 didn't have any really significant changes in hardware support. But of the four main Exynos4 maintainers - I almost never touch my devices, plodey focuses on his find5 but pokes at exynos occasionally, same for codeworkx. Fortunately, all of the device-specific **** was worked out ages ago, so it's always generic common platform stuff. I don't think I've seen a Note or i777-specific commit in many months.
 
  • Like
Reactions: realalms, prohexa, User_99 and 7 others
ThaiDai

ThaiDai

Senior Member
May 28, 2011
2,561
2,588
Aachen/หนองบัวลำภู
Samsung Galaxy Note GT-N7000
Samsung Galaxy Tab S2
That's the type of clear statement I like. No soothing words but real life.

Many things that aren't working in way that could be possible (if Samsung would support it) won't come to the N7000 in CM (10.1 or 10.2) anymore.

For me the two most important:
1. Graphics (butter) will never be really smooth (as Entropy512 made clear some month ago in another statement).
2. In Android 4.3 there is a chance to reduce the typical lags with the TRIM command. Because of the eMMC bug we will not benefit from this.

And of course (but this isn't new) the lack of support for FM (I miss this really) and sPen (I don't know when I used it the last time).
 
Kortxero

Kortxero

Senior Member
Sep 10, 2008
616
651
It's not a problem: as the dedicated OEM we've always known, "Sam-dung" will marvel us with a 4.3 update for the Note in a timely manner (ok where's my grin smiley now?).
 
E

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
daedric said:
Anyone aware of this http://xdaforums.com/showpost.php?p=44746084&postcount=548

i know it's not related to the Note, but it might come around and harm us...
Click to expand...
Click to collapse

Goes way back. I won't specifically name people, but at least one of the exynos4 maintainers is now 90% retired from CM after one of the project leads was constantly trashtalking the exynos4 team. I became pretty demotivated myself. (I was already pretty demotivated due to being shamelessly lied to by Samsung repeatedly, but additional factors made things worse.)

There are some great people on the team, and there are unfortunately some massive assholes. It's funny how they ***** and moan about CM kangs when some of them (and their incredibly hostile attitude towards people they don't know) are the #1 reason for some of the kangs existing.

If it hadn't been for very positive experiences with atinm and codeworkx, I probably wouldn't be involved with the project, as some of my initial runins with certain members of the team were less than pleasant.
 
Last edited:
  • Like
Reactions: presola, qWantUS, realalms and 13 others
daedric

daedric

Senior Member
Dec 24, 2006
2,260
468
Porto
Goes way back. I won't specifically name people, but at least one of the exynos4 maintainers is now 90% retired from CM after one of the project leads was constantly trashtalking the exynos4 team. I became pretty demotivated myself.
Click to expand...
Click to collapse

I remember reading about alot of FUD related to the exynos ecostystem, maintainers "threating" to drop the devices because Samsung was evil and not releasing sources or releasing them severly cripled etc etc.

Let's hope this get's sorted out, i know that a "Advanced" menu is problably not the best solution, but at least it was a solution. I'm on CM10.2 and i miss setting my mDNIe settings... alas this whole Amoled type screen is rubish and the mDNIe just exist to atenuate the severe color unbalance, erroneous saturation, and severe drop to black just to make the device seem "brighter". But, it's what we have....

I hope we can keep the exynos dev team, our devices will probably not live to see the light of another major android distro, but withouth the team we won't see a stable 10.1/10.2. So kudos to you all for keeping up and helping the common people like me.
 
  • Like
Reactions: andyjyneo
I

i004909

Member
Jun 18, 2006
49
12
Bump - anyone else with erratic problems the last week?

Hi, sorry to disturb our quiet thread... but thought to ask before digging MUCH deeper...

Been on 20130813 nightly until last night... but since loading it something wasn't quite right with my ROM/Phone.

1. Black screen, twice
2. Rebooted, once
3. CyanDelta stopped picking up updates
4. Screen rotation stopped working

Last night I manually downloaded and applied 20130819 (via CyanDelta) and then...

1. Select Phone - got an 'App Isn't Installed' error message. I tried starting Phone from app drawer and it worked, so replaced icon on homescreen and seems OK... despite some frayed nerves ;) Is there something new in the 'Phone' app?

2. Android Keyboard (AOSP) which I've been happily using for some time... swiping shows my finger trace, but nothing appears as typed. Typing directly works. Switched to standard Android keyboard and swiping works.

3. Noticeably higher battery usage compared to the last few months. Media a big hog upfront as usual... but not much after initial load. Did notice a new 'status' message I think I've not seen before... 'updating media... something or other during the normal 'Android is upgrading' count through the apps on first boot after new ROM.

Just thought to ask... things have been fantasticly stable the last few months... but suddenly not so much (for me) and in core areas like rotation, phone and keyboard.

Is it just me? Do I need to do my full wife ;)
Thanks!
 
A

andyjyneo

Senior Member
Feb 23, 2011
52
15
Batu Pahat
Is there any site to down CM10.1 nightly builds? Get.cm have CM10.2 builds only currently.

Thanks!

Sent from my GT-N7000 using xda app-developers app
 
V

Vyrlokar

Member
Apr 9, 2011
29
3
Dear sirs

have a Galaxy Note (European model, GT-N7000) that I bought second hand. It has been SIM unlocked with the Galaxy S Unlock Tool by Helroz and works well under the stock 4.0 rom. However, when I install the last 10.1 nightly 20130813) it get SIM locked again, and the unlock tool doesn't work. Does anyone know a solution for this issue?

---------- Post added at 11:10 PM ---------- Previous post was at 11:02 PM ----------
dahool said:
Can someone point me to the official thread of cm10.2 nightly? (I just can't find it..)

Thank you
Click to expand...
Click to collapse

You can find it here.
 
  • Like
Reactions: dahool
NutZInTheHead

NutZInTheHead

Senior Member
Apr 9, 2012
109
12
really sorry if this was asked before.
I'm currently on cm10.1 and i know when going to different versions it's always good to wipe but has anyone gone to cm10.2 without wipe?
thanks.
 
B

baz77

Guest
NutZInTheHead said:
really sorry if this was asked before.
I'm currently on cm10.1 and i know when going to different versions it's always good to wipe but has anyone gone to cm10.2 without wipe?
thanks.
Click to expand...
Click to collapse

first post states to avoid issues to wipe ofc on save kernel. Cleanest is best. If you dont want to loose stuff, there ways to backup. But be carefull, I suggest you read first post of cm10.2 discussion here in general section and then thread.

Why dont you want to wipe?

Sent from my GT-N7000 using Tapatalk 2
 
NutZInTheHead

NutZInTheHead

Senior Member
Apr 9, 2012
109
12
baz77 said:
first post states to avoid issues to wipe ofc on save kernel. Cleanest is best. If you dont want to loose stuff, there ways to backup. But be carefull, I suggest you read first post of cm10.2 discussion here in general section and then thread.

Why don't you want to wipe?

Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse

It's not that I don't want to wipe. I just sometimes the setup and all after can be a hassle.
But if I do flash cm10.2 I'll wipe just in case.
Thanks for the reply.
 
You must log in or register to reply here.

Similar threads

XpLoDWilD
[NIGHTLIES] CyanogenMod 9 Discussion Thread
Replies
8K
Views
1M
Digital Zorro
Digital Zorro
dr.ketan
[STOCK ROMS] N7000 All stock ROMs + install + Root guide All at 1place,Latest 4.1.*
Replies
7K
Views
3M
S
SanyoL
meethere
CyanogenMod 10 JB Discussion/User Thread
Replies
2K
Views
347K
mosheg91
mosheg91
swiss420
[GT-N7000] [AOSPA 4.4] ParanoidAndroid 4+ (July 29th) Beerbong Discussion thread
Replies
2K
Views
268K
K
KlausN7
XpLoDWilD
[ROM][DISCUSSION][GT-N7000] CyanogenMod 10.2 Discussion Thread
Replies
850
Views
158K
A
AndroidSlave

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 88
    E
    Entropy512
    Text of original post shamelessly kanged from codeworkx and edited to be appropriate for N7000. Some links may still go to I9100 stuff. If you can't figure out replacements on your own for links that go the wrong place, you shouldn't be here.

    DO NOT POST UNTIL YOU HAVE READ THE FIRST FOUR POSTS OF THIS THREAD IN THEIR ENTIRETY.

    CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.2 (JB), which is designed to increase performance and reliability over stock Android for your device.

    Code: 
    #include 
/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 *
 * Submitting bug reports on nightly builds is the leading 
 * cause of male impotence.
 */

    CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.


    - There are bugs and we know them all. Don't try to report bugs or complain about. We'll blacklist you.
    - No, we don't accept feature request. We've enough work to do with fixing bugs.
    - Don't ask for changelogs!
    - Never ask for new builds!
    - Use it or leave it!
    - Don't create a ROM based upon this! Creating a ROM on a buggy and unstable base is a stupid idea!
    - kkthxbye


    - UI: Apps like NHK are broken
    - Audio: bugs, missing features
    - Camera: Recording partially broken
    - FM Radio: unsupported
    - TV Out: unsupported, not likely to ever work (there is small hope now but not much)
    - Lots of missing and yet unimplemented features
    - and a lot more



    First time installing CyanogenMod 10.1 to your Galaxy S II, or coming from another ROM:
    - Make sure you're NOT RUNNING A KERNEL WITH THE MMC-SUPERBRICK-BUG. If you're unsure, flash this ClockworkMod-Recovery using Odin/Heimdall.
    - Make sure you're running a proper working ClockworkMod-Recovery
    - Copy GApps and CM10.1 ZIPs to your internal SDCard
    - Boot into Recovery
    - Flash CM10.1 zip from internal SDCard
    - Flash GApps zip from internal SDCard
    - DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
    - Reboot
    - Don't restore system data using Titanium Backup!
    - Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!

    Upgrading from earlier version of CyanogenMod 10.1:
    - Copy CM10.1 ZIP to your internal SDCard
    - Boot into Recovery
    - Flash CM10.1 zip from internal SDCard
    - Reboot



    CM10.1 unofficial builds:

    20121212: http://d-h.st/u13

    Google Apps:
    http://goo.im/gapps


    Webchat: http://webchat.freenode.net/?channels=teamhacksung-support

    Server: chat.freenode.net
    Channel: #teamhacksung-support

    Don't expect any support if you:
    - are not running stock cm-kernel
    - have installed any mods
    - have modified system files


    If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
    This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
    Open-Source doesn't meant without respect!


    hePRLl.png
    ViHvOl.png

    qdBPyl.png
    QuLybl.png

    Screenshots kanged straight from codeworkx. Seriously, it's CM, the screenshots will look almost identical on all phones

    If you want to donate a few bucks for the work we're doing in our freetime, goto teamhacksung website and hit the big donate button.
    Thanks to all donators!
    View
    30
    E
    Entropy512
    Things definitely broken

    In addition to the stuff in OP from codeworkx:
    Wifi tethering doesn't work - Bluetooth tethering does
    HWComposer barely works - passes vsync and not much else. Run NHK World Live TV app and you'll see why it's broken
    Lots of core non-device specific CM features are not yet reimplemented. This includes stylus gesture support, palm rejection, and control of stylus hover icon.
    Camera doesn't appear on lockscreen - and it will not appear at all with many gapps packages
    Audio HAL isn't fully reimplemented - no dock audio, etc.
    Bluetooth SCO (calls) is busted and bluedroid spits out all sorts of bluetooth sleep control errors. We probably need to rework power management from the current mechanisms.
    View
    28
    E
    Entropy512
    Switchover should happen before tomorrow's nightlies, so tomorrow's nightly SHOULD be CM10.1 for N7000.
    View
    26
    E
    Entropy512
    Misc other stuff

    The holidays are coming up here in the USA. I have family visiting this weekend, and will be visiting my parents for a week the following week. I have a lot of preparation to do and my laptop can't build CM, so don't expect much to happen until the new year.
    View
    25
    E
    Entropy512
    cedouic said:
    I'm french and on the same carrier. This popup is due to an update of a specific application of "free mobile". The application is "messagerie visuelle" (specific access to answer machine).
    They've add an auto-configuration of this wifi network.
    This popup is launch by the application after the first reboot after the update and has nothing to do with CM.

    And the configuration of this EAP-SIM wifi network don't work because EAP-SIM authentification is not include in CM10 as it was in CM9...

    But pesonally I don't care lol

    I prefer devs to focus on the next magical kernel with super mali drivers :)
    (thanks by the way)

    Sent from my GT-N7000 using xda app-developers app
    Click to expand...
    Click to collapse
    Thanks for the detail. I'm starting to poke at mali. I attempted to get the latest N7105 blobs running on my N8013, end result was sprinklies. I ****ing hate sprinklies, I have yet to figure out why some blobs cause them and some don't.

    Once I can get something that works on n8013 I'll backport to n7000.

    I'm basically 95% done polishing CM10.0 to perfection on Xperia T (only things remaining are getting someone to merge a few outstanding patches, and fixing scaling of anamorphic videos on HDMI), once I finish that I'll poke at N7000 for a bit.
    View

New posts