yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] roymustafa:
I loved new build 092112. Its faster than the previous builds...But after flashing Hydrocore kernel superuser permission denies..:)
[Galaxy Note GT-N7000 General] mb0108:
The current combination Which runs great is

- CM10 Nightlies

- Projekt LARD

- Hydracore 4.3b

All running on 213 dpi and Holo Launcher HD

Testing every day with that combination. Before I flash LARD and Hydracore I do check if CM10 alone is smooth enough but currently thats not the case.
[Galaxy Note GT-N7000 General] qazibasit:
I would likebto know about the official CM 10 rom for n7000. If its not xomking then why not make the already available unofficial rom the official one. I dont want to upgrade my note

To note 2 just because of jellybeans.
[Galaxy Note GT-N7000 General] JGPorteous:
SMS Issue

Hi everyone,

I'm trying to find the correct place to view and track known issues with CM 10 for Galaxy Note (N7000) - so if there is an official page I can post the issue, please let me know where it is.

I have an issue when sending an sms, the phone disconnects from the network, sometimes I have to enter pin again.

The sms never sends, it keeps re-trying and the network keeps disconnecting - to stop this I have to delete the sms.

Thanks,

Justin

Sunny South Africa
[Galaxy Note GT-N7000 General] sorcio46:
Flash and install SuperSU via CWM

Same Here ! :D
[Galaxy Note GT-N7000 General] StNickZA:
Yep same for me too. My daily procedure is:

CM10

Hydracore

SuperSU

LARD

Flashed a custom build this morning which included Entropys kernel tweaks from last night. However, the UI is still far too sluggish unfortunately.

Make sure you are aware of the risks with data integrity when using Hydracore but as far as I'm concerned, CM10 is frustratingly slow to use without it and it's well worth the risk for me.

And I have no idea whether its a placebo or not, but I'm pretty sure that LARD has helped too. My phone is running as fast as it ever has right now.
[Galaxy Note GT-N7000 General] NaveenKD:
Why there is no thread for official CM10 nightlies?

I mean in Dev section.
[Galaxy Note GT-N7000 General] Bilarn32:
I would like that too
[Galaxy Note GT-N7000 General] fordream:
Why install ROM CM10 S/N I changed.
[Galaxy Note GT-N7000 General] LordManhattan:
You'll have to be a little more specific than that.
[Galaxy Note GT-N7000 General] StNickZA:
I think he may be referring to a warning that I've seen before in Titanium Backup whereby it says that the phone ID has changed and then offers to restore it for you.

I usually let it go ahead and restore the old ID, and I've had no problems as yet.
[Galaxy Note GT-N7000 General] sturmavik:
Yeah, I was wondering about this too. Anyone know the deal?
[Galaxy Note GT-N7000 General] JGPorteous:
Anyone else have issues with SMS causing SIM card to disconnect?

or phone disconnecting from Network?

I think it might be a modem driver/rom issue, but that is my guess and have no idea what to try or how to determine what modem model I'm using.

J

---------- Post added at 11:50 AM ---------- Previous post was at 11:43 AM ----------

I'd also be interested in knowing where the thread for the CM10 nightlies are.
[Galaxy Note GT-N7000 General] mundano:
Same here... I'm using XXLRK modem with latest nightly.
[Galaxy Note GT-N7000 General] JGPorteous:
how do i see what modem is installed?
[Galaxy Note GT-N7000 General] Utacka:
Ive talked to Entropy512 about this issue, a quick fix is to either flash the old teamhacksung kernel which is dated 0727 i think and can be found on chasmodos kernel repository or flash a custom kernel.

Some user reports hat LPT modem fixes it and other dont see a difference between the modems. Then again majority of the user doesnt seem to be affected but many are and old teamhacksung or hydracore fixes this. Latest version of hydracore is confirmed by auther that fsync is enabled.

Skickat från min GT-N7000 via Tapatalk 2
[Galaxy Note GT-N7000 General] kchris:
agrred. CM10 is frustrating laggish without HydraCore v4.3b. But with it it it's perfect. Hourly energy consumption on standby is below 1%. The other drawback is the memory leak. When you switch the device on, and see that the widgets are reloading then you should reboot it because it's low on memory.
[Galaxy Note GT-N7000 General] saturax555:
kind of sod

whatever the build (cm10 nighties, utaka, pa...) and the kernel (cm10, hydracore), i still have a very annoying issue with cm10: about one time on five or ten, the device is difficult to unlock: the screen flashes a short time, then remains black with the capacitive button on. usually, I solve this by pressing several times the power button and after a few cycles like this it unlocks.

with slide unclock, without unlock, with different I/O, with WIFI always ON, with various modem (I am on XLT now) and even in plane mode, without fastdormancy and rescan media... I fix permission, 3 wipes too...

I do not have other idea, the issue remains :confused:

is it a kind of sod?

do you have the same kind of issue too or it may be related to one specific app I have ? Is there a mean to identify the problem or it is a known issue?

thanks!
[Galaxy Note GT-N7000 General] _breez_:
Same problem here. Sometimes it won't come out of standby. After aproximately 10 tries and several short screen flashes it finally gets out of standby

Verstuurd van mijn GT-N7000 met Tapatalk
[Galaxy Note GT-N7000 General] Utacka:
Use the power button instead of home button when that happens and spam power button 4-5 times very fast. It usually helps me when that happens.

Skickat från min GT-N7000 via Tapatalk 2
[Galaxy Note GT-N7000 General] mundano:
Anyone can use the live effects in camera (big eyes, big nose, etc..)?

I can see the preview, but once I start recording the camera app just hangs, and then crashes...
[Galaxy Note GT-N7000 General] MrDSL:
Same issue here also.
[Galaxy Note GT-N7000 General] toxicthunder:
Well I think it is frustrating for the devs too and Samsung doesn't particularly seem interested in making things easier.

Their updates are sparse and way too late and documentation too is nothing short of a treasure hunt.

And now with Sony pushing so hard on the aosp front, releasing sources and working towards helping the developer community, it won't be any surprise if your next device turns out to be an xperia.

Unless of course, if Google decides on a 'true' high end nexus device. :)
[Galaxy Note GT-N7000 General] JGPorteous:
where does one download LARD from?

J
[Galaxy Note GT-N7000 General] trell959:
http://xdaforums.com/showthread.php?p=31166187
[Galaxy Note GT-N7000 General] fordream:
good rom in the world
[Galaxy Note GT-N7000 General] roymustafa:
i was on PA ROM. I first wiped factory data, the wiped cashe and dalvik cashe. then flashed CM10 and GAPPS. Then i wiped factory data and wiped cashe and dalvik cashe. After reboot i flashed the same build of CM10 again with only wiping cashe and dalvik cashe... Did i do something wrong? THANX A LOT!
[Galaxy Note GT-N7000 General] JGPorteous:
Thank you for your reply, do you have any url's I could use to find them kernels to try?

I've read online that one can get rom's for modems, is there a definitive list of them out there for the n7000?

J
[Galaxy Note GT-N7000 General] LoVeRice:
Hey guys, is it possible to put the audio quality of CM9 here on CM10?

Via Xda-Dev Elite App
[Galaxy Note GT-N7000 General] joshua:
I guess the custom ringing tone only ring once still not solved in CM10?
[Galaxy Note GT-N7000 General] mauronedj:
Anyone is reproducing a force close anytime the new Aphex Launcher is opened?
[Galaxy Note GT-N7000 General] toxicthunder:
Yeah latest release is at fault and the developer has been informed. I think he is already out with a couple of betas.

---------- Post added at 08:51 PM ---------- Previous post was at 08:48 PM ----------

--------------------------------------------------------------

Sorry, but just couldn't resist ^^
[Galaxy Note GT-N7000 General] Entropy512:
A branch got mis-pushed when moving to source-built Superuser. It was fixed yesterday.

Been too busy to shut down the old threads and create new ones. Too much other **** to do. Blame Samsung and their lack of documentation/source that makes it an utter freaking nightmare to support these devices.

atinm burned out, codeworkx burned out (he's still supporting Exynos4210 a little bit but not significantly, and ditching 4412), plodey's doing a lot of Asus work these days, I'm approaching burnout.
[Galaxy Note GT-N7000 General] Macrint:
Really appreciate your work, would be a shame to lose you!

Maybe you could take a break and wait for a nice JB release/leak, possibly with source from Samsung... We're really gonna need you around once that shows up :)
[Galaxy Note GT-N7000 General] sorcio46:
I would give you my brain through cloud computing if it would be possible ;)
[Galaxy Note GT-N7000 General] smeddy:
Guys that's really sad, though I get the reasons why :(

If everyone is a bit burnt out, I'm finding these CM10 nightlies pretty pretty stable overall. Can we get to a stage where we could produce a stable 'M' release, and then maybe take a break from development for a month or so until some fresh goodies come along? Really would hate to lose all you devs from the Note! Much love
[Galaxy Note GT-N7000 General] Bilarn32:
Let's send the devs for a vacation :d
[Galaxy Note GT-N7000 General] Entropy512:
Pretty much, I intend to keep maintaining the devices I currently am working on throughout the life of CM10. Those are SGH-I777, GT-N7000, GT-N80xx. I also hope to get Infuse officially supported when I have the time, but Samsung's poor handling of Exynos has blackholed so much of my time I haven't been able to do as much as I wanted on Infuse. There's a 50/50 chance I'll pick up an AT&T Note2 since it should be easy to bring it up to the same standards as other Exynos 4412 devices with CM10.

However, depending on the nature of the next version of Android, and whether Samsung shapes up, my approach is likely going to be "time to buy a Nexus or maybe a Sony" for whatever CM11 may be, with a slight possibility of "when an Exynos 4412 device gets an official release with source, I'll start work".

At this point I'm sick of trying to do early bringups on devices with zero applicable reference source, and so are the rest of the Exynos device maintainers. With OMAP and Qcom devices, there is reference source usable for doing a reasonably good "early bringup" (omapzoom for OMAP, CAF for Qcom), as mentioned by codeworkx on the I9300 thread, the closest thing Samsung has is the Insignal repo, and it was minimally useful for ICS (because Samsung's handsets diverge significantly from the Insignal reference source), and is utterly useless crap with regard to Jellybean. The Insignal repos don't even remotely compare to the quality and up-to-dateness of the CAF and omapzoom repos. There's also zero documentation about the graphics-related "special function" subsystems of the chip (FIMC, FIMG2D, MFC, hardware JPEG).
[Galaxy Note GT-N7000 General] sorcio46:
Memory Leak is still present?

I cannot understand what is our main trouble, hwc or memory leak?

When my Note turns on (after unlocking the phone) I have 440-360MB of free RAM.

Some minutes later by doing NOTHING it drops down to 285-240MB of free RAM.

It seems a memory leak, isn't it?
[Galaxy Note GT-N7000 General] Entropy512:
both
[Galaxy Note GT-N7000 General] StNickZA:
Seems like the devs were extra-busy last night; there are a ton of changes merged since the last nightly build! Great to see.

Entropy, a question for you... If I understood correctly, you've said before that killing surface-flinger periodically resolves the slow-down caused by the memory-leak. Most of us just reboot upon signs of slowdown; what app do you personally use / recommend to kill surfaceflinger? Is it quicker than a reboot?

I've often wondered if there's a better, more visual way of seeing this memory leak in action... For me, the only signs of it are that my launcher appears to reload when exiting out of other apps (presumably because it was killed due to low mem).
[Galaxy Note GT-N7000 General] toxicthunder:
1. Open any icons or themes thread using xda app.

2. Press home button and open whatsapp to send a message to a loved one.

3. Decide against it and press the home button again. Maybe you want to relax and listen to some music or watch a movie.

4. Open your media player. You were previously watching Inception - Director' Cut where the end is about to be explained. Suddenly everything closes or the phone reboots.

5. Welcome to Memory Leak Arena :p

---------- Post added at 02:42 PM ---------- Previous post was at 02:39 PM ----------

@Entropy

Why not try something different and work on Boot2Gecko? Looks promising from what I've seen. A couple of carriers have already agreed to ship it with their devices in 2013. :)
[Galaxy Note GT-N7000 General] Entropy512:
I don't know about signs of it... Once or twice I've seen my device just become highly unresponsive, often at the lockscreen.

Someone in the I9100 thread wrote a script to automate killing it from a launcher widget but I forget the details. For me it's usually a sign I need to rebuild/flash. :)
[Galaxy Note GT-N7000 General] NaveenKD:
Since we don't have the ability to build, we keep flashing whatever new builds come our way.

And pray with folded hands that it will work this time.
[Galaxy Note GT-N7000 General] dsana123:
Question for Entropy512

Hi Entropy512,

Thank you for your work on CM9 and CM10. I really appreciate the time and effort you have spent. For the last year I have been keeping a track of (and using) CyanogenMod on the Note and curiousity prompts me to ask a question of you if it's not too much trouble (or impertinent): what drives you (or any dev) to spend effort doing this? Is it for the challenge, the pleasure that you derive working on the kernel?

As a full-time software engineer myself (and also an Android app developer), sometimes the last thing I want to do when I get home is to check the bug reports and support emails. I have become wary of adding new features simply because of the time that gets eaten up. I am really curious about those who give of their free time to the community.

Thanks.
[Galaxy Note GT-N7000 General] sorcio46:
I am reading from i9100 CM10 thread that this build:

http://espen.mrfjo.org:81/cm-10-20120925-UNOFFICIAL-i9100.zip IS FOR i9100 (GALAXY S2) so don't flash it

It really gave a good boost in performance and reliability to SGS2, is this job gonna be pushed for us?
[Galaxy Note GT-N7000 General] toxicthunder:
Entropy has made a commit on gerrit and I think its related to this.
[Galaxy Note GT-N7000 General] Utacka:
Actually its http://review.cyanogenmod.com/#/c/23580/ that Espen has been working hard on that entropy512 changes reflect too. Fixed hwcomposer and memleak, I suppose. Still in review but no longer WIP as it was a week ago. Cherry-picking should work for those trying this, I guess.

Skickat från min GT-N7000 via Tapatalk 2
[Galaxy Note GT-N7000 General] jaiiscool:
Is this commit included in any of your builds?
[Galaxy Note GT-N7000 General] kitrax59:
I would be ecstatic if you cherry pick this and make it work on your next build!!! :D
[Galaxy Note GT-N7000 General] androidindian:
Just spoke to espenfjo, and memory leak + video graphical glitches are fixed, but as far as butter project hwcomposer goes.. this is what he mentioned: "There are stille some hwcomposer issues that is present. We will have to discuss what we should do."

so lets wait and see if the latest changes would be merged soon or if they will fix on the butter project and then merge. thanks a lot mate! :)
[Galaxy Note GT-N7000 General] toxicthunder:
yeah it'd probably require Entropy and other devs to be simultaneously online I guess, so that they can discuss these things out.
[Galaxy Note GT-N7000 General] ahalford:
Hwcomposer - may be, memory leak - I hardly beleive. Just a leaked I9305 (SGS3 LTE) GPU drivers. Anyway should be very good commit.
[Galaxy Note GT-N7000 General] sorcio46:
New Nighlty is out, does it contain that upgrades from S2?

http://get.cm/get/41X
[Galaxy Note GT-N7000 General] Utacka:
No

Skickat från min GT-N7000 via Tapatalk 2
[Galaxy Note GT-N7000 General] isquite:
But there are two changes (changelog from BBQ):
[Galaxy Note GT-N7000 General] sorcio46:
I think that these aren't related with our main problem.
[Galaxy Note GT-N7000 General] Entropy512:
It started as personal hacking just to tweak my own device, to some degree as a learning experience. Keeping my mind sharp, so to say. It's also a great software development learning experience. In my day job I'm a hardware guy/systems engineer although I work closely with embedded software developers - for me, a lot of this is about learning new hardware.

If I did this stuff for a living I'd probably hate it with a passion. (There's the answer, again, for those saying Samsung or Google should hire me.) To some degree I get bound by a sense of moral duty to stay with some devices I should just throw into a wall, but sometimes when you make a breakthrough with those it's exhilarating (like Bluetooth on Infuse).

That said I'm rapidly approaching burnout... I'm likely to easymode it on a Nexus doing minimal work, and/or returning to what I really wanted to do when I was hacking kernels, more highly experimental work. I've had a project (reducing suspend/resume power consumption cost) I haven't been able to even think about in months.

Yeah, and this is always a problem. Usually I'm heading to work when espenfjo and codeworkx are awake, and when I get home from work, they're sleeping.

Memleak - almost definitely fixed. Mali r2p4 drivers + gralloc leak like crazy on AOSP for some reason, r3p0 works far better. My build (only on my device right now...) and espen's are still using ics hwcomposer though, and it's highly likely we'll be stuck there. Opensource hwc has never worked quite correctly. This is really the root of codeworkx's anti-Exynos rant.

Correct. Those fix minor memleaks elsewhere, not the massive gralloc leak from hell.
[Galaxy Note GT-N7000 General] ahalford:
I like being corrected this way:cool: Thank you, sir:good:
[Galaxy Note GT-N7000 General] sorcio46:
For everyone that wants to know the status of this project

cm-10-20120926-NIGHTLY-n7000.zip + HydraCore v5.1 kernel

[YOUTUBE]SoIRin_E-_E[/YOUTUBE]
[Galaxy Note GT-N7000 General] Entropy512:
Um, no, that's not the status of this project at all. That contains NONE of the work that has been discussed on the past two pages.
[Galaxy Note GT-N7000 General] roymustafa:
The latest CM10 with HydraCore v5.3 kernel made my Note soooo faster and smooth...
[Galaxy Note GT-N7000 General] sorcio46:
I know but it has what I can download xD
[Galaxy Note GT-N7000 General] iLLuSi0ne:
What about the memory leak? Is it really solved?

※「POPPEL」 ※ con il suo inseparabile Galaxy Note | Sempre assetato di flash ※
[Galaxy Note GT-N7000 General] Bingoig11:
What about reading? Is it really hard?
[Galaxy Note GT-N7000 General] iLLuSi0ne:
No, it's not so difficult my teacher... But English isn't my first language and not ever I'm able to understand at 100%. But anyway... I've read on the changelog that the problem was fixed but a some friends of mine have noticed lags after 3h of intensive use. Is it normal? Many thanks

※「POPPEL」 ※ con il suo inseparabile Galaxy Note | Sempre assetato di flash ※
[Galaxy Note GT-N7000 General] toxicthunder:
Cheers to the days when there were no (over)smart phones and we happily lived with our monochrome nokias :rolleyes:
[Galaxy Note GT-N7000 General] smeddy:
I think people misread this post, think he just means its a walkthrough of where cm10 is on the Note right now.

Either way, other than a daily reset and occasional launcher resets, I love these builds :)
[Galaxy Note GT-N7000 General] sorcio46:
No further News about Espen and Entropy's last changes on Exynos 4210?

I still read good feedback from i9100 CM10 official thread.
[Galaxy Note GT-N7000 General] Utacka:
Never ask for eta, its ready when its ready.

On a side-note i tried cherry picking, 2 commits from smdk and 1 from galaxys2common and cant get it to boot. Seems like its not ready for the note but i might have done something wrong aswell.

Skickat från min GT-N7000 via Tapatalk 2
[Galaxy Note GT-N7000 General] StNickZA:
I tried similar.

I cherry picked:

http://review.cyanogenmod.com/#/c/23580/

http://review.cyanogenmod.com/#/c/23924/

My build would not boot (black screen).

I am now trying again with Espenfjo's blobs from:

https://github.com/espenfjo/proprietary_vendor_samsung

But I think I am still missing one other patch ... Any ideas?
[Galaxy Note GT-N7000 General] BurekUSvemiru:
CM S-pen writing hand by Inf3rn0.nl

How about making setting in CM10 for spen calibration:
[Galaxy Note GT-N7000 General] sorcio46:
I wasn't asking for eta, but for some confirms, news, info by the DEVs
[Galaxy Note GT-N7000 General] zdzich:
I tried them as well. Snippet from lolcat:

E/ ( 2561): Device driver API mismatch
E/ ( 2561): Device driver API version: 14
E/ ( 2561): User space API version: 10
D/ ( 2561): mali: REVISION=Linux-r2p4-02rel0 BUILD_DATE=Thu Aug 23 10:54:04 KST 2012

I think this is the issue, but I don't know for sure. Apart from debugging stuff and 'killed surfaceflinger service' messages, etc. But Entropy said on gerrit, that he will post his experimental build with this changes today, so I will wait :fingers-crossed:
[Galaxy Note GT-N7000 General] StNickZA:
Ha!

Thanks dude, yeah I am giving up for now... I tried again using Espen's blobs, but this time it wouldn't boot beyond the "Samsung Galaxy Note" screen.
[Galaxy Note GT-N7000 General] Entropy512:
That's odd...

http://review.cyanogenmod.com/#/c/23580/

http://review.cyanogenmod.com/#/c/23924/

http://review.cyanogenmod.com/#/c/23797/

plus

https://github.com/espenfjo/proprie...mmit/a664c42a24fff565fd3b86fa5ef2c54c0636a7db

should do the trick, that's what I built with initially.

As an optional thing to play with:

http://review.cyanogenmod.com/#/c/19925/ plus removing hwcomposer from the blobs seems to work, but it doesn't make any improvement either. The fact that it totally fails on 4412 is one thing holding up merge, along with the general lack of confidence in it working properly.

Also, in those blobs, you can safely remove libsync - it's only a dependency of the 4412 hwcomposer blobs. If it's ever added as a dependency for the 4210 hwc source, it'll be built from source like it now is on 4412 devices.

I kicked off clean builds with the opensource hwc this morning, I'll start uploading them tonight. I may also put up builds without it for comparison.
[Galaxy Note GT-N7000 General] Entropy512:
Definitely wrong blobs. r2p4 mali libs will NOT boot with r3p0 kernel. :)
[Galaxy Note GT-N7000 General] zdzich:
Yeah, I thought so. Where can I download r3p0 blobs? I assumed, that Espenfjo I9100 build would have them, but that didn't work. Or maybe you will provide a new build soon? :P Thank you for your work, btw :)
[Galaxy Note GT-N7000 General] toxicthunder:
I got to build successfully after loads of trial and errors :p

To be honest I can hardly feel the difference. But that's just my personal usage that reflects it. A heavy user might be able to make a better assessment.

But I did have some difficulty in viewing videos, especially the high definition ones. It occasionally stutters and in case I switch to another app, say the browser, returning back to it without having to kill the media player and restarting it, has been a no go for me.
[Galaxy Note GT-N7000 General] Entropy512:
espen's build does have them, as does his github...

In some cases if you swap blobs but don't remove them from the existing build, they won't get pulled in. might need to nuke out/target/product/n7000

You can usually identify which Mali revision blobs are for:

grep r3p0 /system/lib/egl/*

will show you everything that's for r3p0 in the egl folder, and it should be obvious how to check for r2p4. :)

There's at least one other version-tied mali blob in /system/lib, and also might be something in /system/lib/hw
[Galaxy Note GT-N7000 General] sorcio46:
We love you man :D