yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] StNickZA:
I use the vehicle dock, and one of the things that disappointed me the most when I bought it, was that call-audio when on speakerphone does not passthrough to the external audio output. It seems like a serious oversight on Samsung's part and one of the features I was looking forward to the most.

It has been suggested to me that this can be changed inside the kernel. Is this something that we're likely to see in CM9 at any point? Or, is there perhaps a kernel that I can use on top of CM9 which DOES support this feature?

Any tips / advice appreciated.
[Galaxy Note GT-N7000 General] Dazog:
Seems No matter how we explain it you don't understand if you look up GPL2 you can read what you HAVE to do in order to use the code PERIOD.
[Galaxy Note GT-N7000 General] joshua:
Guess i take ur advice to stick with CM9 to avoid any implications...lol
[Galaxy Note GT-N7000 General] lewisteo:
My Apologies

OK, I admit my understandings is mild so my apologies to anybody that I might had offended.

But I feel in a closed forum which requires you to minimally register to be in the family before any distribution could be presented to your eye deserves certain aspect of privacy.

Because somebody pointed to the place and made known to others whom are unaware previously.

And now this little private space had been target of finger pointing, I still don't feel very comfortable, Open Source is not like that :) IMO
[Galaxy Note GT-N7000 General] samarium:
So you should have stopped there, and done some reading to understand the GPL2 licence.

Everything else you posted is nice, but irrelevant given the licence, and just demonstrates that you didn't do the reading and don't understand the issue and are just posting an uninformed opinion about the world as you see it, but not the world as it exists.

The only reason that we are able to get updated kernels for our Android phones is because anyone who distributes a linux kernel is required to distribute to source too. If you are saying that this person should not have to comply with the licence and distribute the source, then you are also saying that Samsung can do the same, so no kernel source for developers to hack and fix and expand upon, so you are stuck with what Samsung distributes. Do some reading and think about it.

Seems to me that people should just leave this alone, me included, and that is the last I will be posting on it.
[Galaxy Note GT-N7000 General] be_vigilant:
SOD Further Info

Phone is still SOD and I have tried every variable to try and stop it nothing helps. This surely proves something in the kernel\CM9 rom doesnt like some galaxy notes.

Any how

This morning while working from home my phone SOD (wifi is not enabled but constant H+ data is)

The phone is unresponsive to any input form the buttons. I connect the phone to my windows 7 PC and ran ADB Devices. Nothing was listed.

I waiting 5 minutes then ran the command again. This time the device is listed. The phone however is still unresponsive.

I ran a

adb logcat > logcat.txt

so far the logcat.txt is 0 bytes and doesn't seem to be increasing :-(

anything else I can try to do while my phone is SOD but sort of contactable via ADB?
[Galaxy Note GT-N7000 General] Kings Lee:
please see http://xdaforums.com/showthread.php?t=1520508&highlight=last+kmsg

in short, use...

adb logcat > logcat.txt

adb shell dmesg > dmesg.txt

adb shell cat /proc/last_kmsg > kmsg.txt

tapatalk on cm9-nightly-n7000
[Galaxy Note GT-N7000 General] MR.change:
I started having the non responsive lock screen since the 29\5 nightly like some other people ,it just started yesterday for me.

I haven't been keeping up with the progress here since ,but I assume the cause is still unknown right?

it's got to be somewhere between the changes of 23\5 and 29\5 cause I didn't have it back then ,maybe the new wifi drivers? since the wifi is now very responsive and never hangs when turning on -off .
[Galaxy Note GT-N7000 General] samarium:
after you have got all you can thing off the device, you could try:

adb root

adb shell killall zygote

which is what I use to restart the android UI without rebooting the phone

not sure if it will be useful with the phone it SOD, but it probably can't hurt too much

this normally results in /etc/init restarting zygote which drags the android system up with it.

I'm running a home build somewhere around 0525, and I have lockscreen disabled. What I see is that if I pull down the notification bar it can take 30-60 sec to populate it. I can flick it up and down a few times before it is populated.
[Galaxy Note GT-N7000 General] Kings Lee:
Same here! And the ones that flickers are all the same - the keyboard I am currently using

tapatalk on cm9-nightly-n7000
[Galaxy Note GT-N7000 General] saMMuel'sky:
Hi all.

I want to say that I love this ROM, but today I found one bugg, and I would like to know if there is something wrong with my Note or is the problem in ROM. I have my phone on the desk here, and it is constantly turning on now. The display is flashing now for about 10 minutes. I rebooted it, but no success. I left it alone, didn't touch it, but then I just saw that it is unlocking by it self. Display turns on (like I would press power or Home button to unlock it), and turns off, and again on, etc etc...

Hope that you understand what my problem is, and will help me what could be wrong.

Thanks all!
[Galaxy Note GT-N7000 General] joshua:
U sure u r alone???

jokes aside... sorry but didnt encounter this before from build 1 till latest nightlies...
[Galaxy Note GT-N7000 General] MR.change:
Some malicious apps can do that ,that would prevent the phone from entering deep sleep and give you horrible battery life .

Uninstall any suspicious apps and check with better battery status .
[Galaxy Note GT-N7000 General] saMMuel'sky:
Haha, I'm not alone here on the work, you're right. But I'm alone here at my desk. :D

Hmmm, I also found that I got sometimes in the status bar a star or something, and it writes that I have to click on it, if I want to make my battery better etc. Are those signs of virus or something? I also thought that I might caught a virus or something like that.

Here is my installed app list:

Applanet, Barcode Scanner, Color Note, Dual File Manager, Flash Player, GO SMS Pro, imo, Heart Rate, Parking Challenge 3D (game), Skype, Sound Hound, Tune in Radio, Download all files and YouTube Downloader. All of them are from Play Store, not from Applanet.

From yesterday I'm on version 30.5.2012 of this ROM, but as I remember I also recognize this once before when I was listening to the music via head phones. But first time reboot "fix" it.

But battery is not that bad, it is not that good as on Stock GB ROM, but still not that bad...
[Galaxy Note GT-N7000 General] Kings Lee:
sounds like a new app updated is doing this... try wipe and install one by one, or try uninstall one by one

tapatalk on cm9-nightly-n7000
[Galaxy Note GT-N7000 General] --Rob--:
Just installed thor's kernel on CM9 for testing.

Unfortunately can't enable wifi anymore... But must admit, rest is running good and smooth
[Galaxy Note GT-N7000 General] saMMuel'sky:
Will try. How do you mean wipe, just delete them, or what?
[Galaxy Note GT-N7000 General] be_vigilant:
Although the ADB Devices does report back it can see my phone. When I try to run any of your commands they run but generate empty text files :(

thanks though
[Galaxy Note GT-N7000 General] eikiel:
Uninstall your apps one by one until it stops OR go into CWM recovery and do a factory reset and start installing them
[Galaxy Note GT-N7000 General] MR.change:
bingo ,just as I expected ,you have push ads notifications!! I had those too back on my S2 with over 300 apps installed (crazy I know).

go to market and search for apps named: air push detector ,ad free ,and others that scan for ads but whcih names I can't remember .

install as many of those as you can (check their ratings first) then let them scan your system and then remove violating apps and viola your clean again.

it's not a virus ,but rather a lowly infamous push ads system that was badly criticized because of it being sneaky and running without your approval.
[Galaxy Note GT-N7000 General] blackjoker1024:
hi guys. why dont try to wipe cache and delvik before and after you install the update zip. cus i do that every time and i had the lockscreen bug only 2 times on a day on build 27 and 29. everything else work well. and i have owners info, weather and lockscreen shorcut on. one more thing wifi on at home maybe 98% of the time.
[Galaxy Note GT-N7000 General] joshua:
Go in recovery mode wipe cache n dalvik if i understand correctly
[Galaxy Note GT-N7000 General] samarium:
Becasue I'm unconvinced that it actually accomplishes anything.

What is in /cache? /cache/dalvik-cache

What do you wipe when you wipe dalvik-cache? /cache/dalvik-cache and /data/dalvik-cache.

What gets rebuilt on reboot "Optimizing Apps" after I install a new build? /cache/dalvik-cache for system apps and /data/dalvik-cache for other apps.

Try running an adb logcat after rebooting your phone with a new build, you can see it happening.

I only wipe dalvik-cache after changing ROM, which I've done a few times, or as a last resort, which I've done twice in two years of 3 phones. YMMV however, as your usage patterns may be such that it makes a difference for you. I'm not a promiscuous ROM user, nor do I flash every nightly, and I have a fairly stable and small app collection, which in most cases I've migrated across all 3 phones using Titanium.
[Galaxy Note GT-N7000 General] joshua:
Well thats good to hear that...

hmmm...i guess i kinda wanna play safe...seriously IDK wats in cache n dalvik but to me..i mean juz me...no harm clearing the both of them since it normally took less than 30secs to do that... Peace of mind...:p
[Galaxy Note GT-N7000 General] Metheny:
Knocking on wood here, but so far with nightly 31 no screen delay on wake.
[Galaxy Note GT-N7000 General] joshua:
Tried with wifi on?
[Galaxy Note GT-N7000 General] Entropy512:
Try searching before posting next time. It IS XDA rule #1

If you had bothered to even read this thread you'd know the cause and the status of the fix.

Thor is a pirate - a GPL-violating kangbanger. He was effectively banned from XDA for multiple GPL violations.

To put things shortly:

For the kernel, the GPL REQUIRES you to provide source to anyone you provide a binary to.

For userspace stuff, the Apache license allows you to withhold source, however those who do so with CM9 code will be effectively shunned from the community for being a douchebag.

My OTG cable arrived last night - I found the fix and it's in the review process now. At the same time, I finally had time to make our storage configuration match that of I777/I9100 - You'll see internal/external SD cards swap when it merges. (Recovery will now correctly be using the internal SD when it says internal...)

Protocol 0x886c in the captures.

Yup. See above.

Nope, nothing to do with the kernel. The dock audio code is in userspace, most of it in frameworks/base - Unfortunately Samsung's dock audio architecture is such that supporting Samsung docks without breaking other devices has proven very difficult. Going any further with dock audio is probably going to require ripping out all of the current support and moving it into a separate APK in a similar manner to the Motorola Lapdock support at https://github.com/CyanogenMod/android_packages_apps_DockAudio/ (which really should be called MotDockAudio)

You assume wrong. Seriously, read. I don't know how many times I've posted the goddamned gerrit link to the candidate fix.
[Galaxy Note GT-N7000 General] samarium:
Thanks. That was one I was awaiting. Looks like it was mostly power related. Pity it is dependent on the MMC patch, but ... such is life.

Looking at complexity of the patch, and the possible implications with eMMC, I can see why it is still in pending, and am happy for it to sit there while it gets further tested.

However, does firewalling MMC_CAP_ERASE mean that CWM erase is a NOP? Or does it just do an equivalent of dd if=/dev/zero, or maybe logically if=/dev/ffff ? What do I have to to for a reliable erase? Do I have to do it manually?
[Galaxy Note GT-N7000 General] albireox:
Entropy, you're great and I appreciate what you're doing here, but the lockscreen problem is present and critical in my opinion. And it's somewhat frustrating that after everybody knows about it you tell people to read hundreds of posts behind and to see what? That there's no easy fix. Why don't you write about it in the OP/FAQ/whatever so that there will be no more "stupid" questions?
[Galaxy Note GT-N7000 General] lewisteo:
my wifi works out of the box, fyi only.
[Galaxy Note GT-N7000 General] Entropy512:
Technically it's not dependent, but there's no way to mark two patches in the same branch as "independent".

Firewalling MMC_CAP_ERASE means that CWM wipe/erase/format behaves the same as Gingerbread - The partition is formatted and effectively "blank" for the purposes of flashaholics, but if you want it REALLY wiped for the purposes of privacy (such as if you're selling the device to someone) - you need to do dd if=/dev/zero or /dev/random or /dev/urandom or whatever your preference is depending on how paranoid you are. :)

And yeah - the OTG fix in the kernel was all power stuff that became obvious when N7000 source dropped - it's just that there was too much ELSE going on with the N7000 official ICS release (like the Superbrick fiasco) to get to this until now. It needed device tree fixes too - but these were long overdue to pull in from the I9100. I expect there will be *****ing and whining for a few days since some apps don't behave well as far as having their storage configuration switched out from under them - but I was honestly surprised that nightlies were kicked off without this change.
[Galaxy Note GT-N7000 General] joshua:
+1
[Galaxy Note GT-N7000 General] ahalford:
Thanks for the clarification about the Thor. I will remove this rom from my phone and will post proper info at my forum.
[Galaxy Note GT-N7000 General] Entropy512:
Oh, you think we tried hard to erase it?

Let's see you put it back in to an AOSP firmware.

We didn't "erase" anything - we've been working our asses off for months to get even standard AOSP functionality to work correctly when Samsung keeps on changing **** around so that it doesn't follow Android standards without documenting their changes.

S-Memo, etc. depend on undocumented proprietary **** in Samsung's framework that they keep to themselves. Reverse engineering this and implementing compatibility would be a major undertaking at best and might get the Cyanogenmod team sued by Samsung at the worst. (Samsung, of course, doesn't want their apps running on non-Samsung devices - which would be possible if the compatibility layer were added to CM.) As it is, reverse engineering more basic functionality is a ****ing pain in the ass.

You guys are lucky - the N7000 is extremely similar to the I9100 for many aspects of its functionality, and as a result, even the first N7000 builds were quite robust. If you want to see a fun time - look at the history of CM9 on the I9100 for the past 5-6 months. codeworkx, xplodwild, espenfjo, and company fixed a LOT of stuff before N7000 work kicked off.

As an example - it took me a good part of a weekend afternoon to figure out why GPS satellite status wasn't reporting properly. Samsung added an extra field to gps.h of their internal builds and never documented this fact anywhere. This breakage of Android standards meant that any software expecting the "standard" interface didn't work right. It took a lot of debugging and code instrumentation to figure out what they changed and work around it. This was on I9100/I777 - but our GPS library has the same standards-breaking change.

Apparently you think MHL is easy - if you think it's so easy, why don't you implement it yourself? Prove it's easy - DO IT.

If you're unhappy about S-Pen apps not working in CM9 - go whine to Samsung. Android 4.0 has a standard pen/stylus input API, but Samsung chose to reinvent the wheel and create something nonstandard. If they had used the standard Android APIs, they would've been working from the very first of xplod's experimental builds (because we DO support the standard Android 4.0 stylus API - we didn't even have to put any effort into it - other than getting the kernel driver to build and fixing one config file to handle rotation, the core Android code automagically handled it.)
[Galaxy Note GT-N7000 General] samarium:
Useful to know, thanks, I might cherry pick it after the w/e, when I have more time to tolerate a cantankerous phone.

And maybe N times if I am worried about wear leveling and people reading bare flash chips :-)

I'm planning to rsync /sdcard/ and /emmc/ back and forth and then mark them before I flash the ROM with that patch.
[Galaxy Note GT-N7000 General] Entropy512:
Hundreds of posts? It's on every page. And you wouldn't have to read so far back if people didn't keep cluttering the page by posting without searching.

It's not exactly difficult to search for posts from me and xplodwild to see what we've stated in the past.

The lockscreen problem isn't critical - it's easy to work around. Turn the device on and off and it usually will work. That's a HELL of a lot less of a problem than permanent unrecoverable damage to your phone's eMMC chip - which is what will happen if I made a mistake in porting the N7000 MMC drivers (which is what seems to be fixing the lockscreen issues due to changes to SDIO power management code for I9100 SiyahKernel.)

So really, you want us to risk destroying multiple people's phones because your definition of "critical" is completely bogus?
[Galaxy Note GT-N7000 General] joshua:
+1

Totally agree with u...

OP is the most impt piece of information which include instructions and the dos n dont..
[Galaxy Note GT-N7000 General] MrDSL:
I kinda had this suspicion when you have to register to another board...All file links are hidden unless you register and he doesnt want anything posted elsewhere..

i knew he probably wasnt following GPL
[Galaxy Note GT-N7000 General] MR.change:
Believe it or not (I'm actually embarrassed to admit this ) but apparently I've read your gerrit link and its description ,but somehow it completely escaped my mind till you mentioned it to me!!

I actually can't even remember when I read it ,cause like I said I haven't been checking on the status here for the past couple of days , but I distinctly remember your argument about it being in the same branch as the mmc super brick cause, and thus it will be reviewed carefully .

Damn I forget things too quickly sometimes .

Sorry about my stupid post earlier ,you're still my favorite dev BTW :)

Have a nice day
[Galaxy Note GT-N7000 General] saMMuel'sky:
I really pressed that add when I first has it, because my friend told me that he is getting them all of the time, and he pressed on, when I first time got mine to show me, what it does. I installed Air push detector and AdFree as you told me, and hope it will help now.

Thank you many many times! :)
[Galaxy Note GT-N7000 General] marco2082:
Is the cm9 build safe now to wipe wipe and wipe?

maybe its something te make clear in the main post..

Thanks
[Galaxy Note GT-N7000 General] mauaus:
Its been safe since build 1 of the experimentals...
[Galaxy Note GT-N7000 General] emoriatov:
This cm9 was always safe to wipe

Enviado desde mi GT-N7000 usando Tapatalk 2
[Galaxy Note GT-N7000 General] GocaS6:
Just wanted to explain myself, i'm not a whiner or didn't came here to demand anything. At all.

Just needed few informations and i'm sure that all this is not easy work and it takes lots of time and nerves.

And Entropy your explanation was nice and decent and that's all that i wanted it.

Thank you for that.

Just these guys i called them "lawyers" this is what is actually annoying, who the hell asked you anything :mad:?

Yes if you wrote that we should all respect CM9 crew then we'll certainly listen to you, if you were not here who knows what could happened :cool:

Get your head out of Entropy's ass and stfu.
[Galaxy Note GT-N7000 General] ChodTheWacko:
It's probably worth noting that since installing the paranoid rom, which is based off of the 5/29 nightly, that I haven't had a single wifi lockup and/or SOD.

- Frank
[Galaxy Note GT-N7000 General] cdmackay:
Anyone wanting changes added to the FAQ, please note that it's a wiki, so you can easily do that yourself.

That's much better than updating the OP, since everyone can edit the FAQ...

I'd add it myself, but for some odd reason I'm seeing neither SoD nor the lockscreen issue, so don't quite feel comfortable describing them.

Perhaps a new FAQ generic entry:

"whatever problem you're having, it will almost surely go away when the devs merge the eMMC changes"

:)
[Galaxy Note GT-N7000 General] MR.change:
you're welcome ;)

oh and just installing these apps isn't enough ,as some of them will scan the apps and you should manually remove them.

on the other hand there is one app (ad stop or something like that) will just monitor and close any connection to airpush servers.

try them all for the best result .

yes cause they used new wifi drivers from samsung sources or something similar to that (apparently my memory is a bit fuzzy today so I don't want to make another statement lol)
[Galaxy Note GT-N7000 General] beckend:
Nice 500 pages, so meanwhile how do i install cm9 again im a newbie and i cannot find s memo, and this is safe sorry not so good english and lastly what is root
[Galaxy Note GT-N7000 General] nandihno:
OK can confirm that recorded a video on my note only one channel for volume the other is very weak so hopes that gets fix soon
[Galaxy Note GT-N7000 General] gedster314:
I don't think that is a good idea. It should be noted that it has been done and by how many people. I for one must have flashed the repack 5 or 6 times without issue. For the record, I went back to GB and rooted as suggested for this ROM. Maybe give infractions if someone suggests that it is ok to flash from a repack.

it is quite clearly mentioned in the first post and FAQ, only a hammer to the forehead would be more obvious. When you look for a download link you can't miss the warning.
[Galaxy Note GT-N7000 General] vjoom:
I see, I use a custom ringtones that might be too short. Thank for pointing that out.
[Galaxy Note GT-N7000 General] dkotoric:
does anyone know if build 3 is being worked on

Sent from my GT-N7000
[Galaxy Note GT-N7000 General] knightnz:
You don't honestly think that they'd give up completely already do you?

Plus, the answer is in the thread.
[Galaxy Note GT-N7000 General] dkotoric:
obviously not but can anyone post any progress or fixes we can expect really wish we can get the menu and back hapatic feedback fixed

Sent from my GT-N7000
[Galaxy Note GT-N7000 General] MrDSL:
come on man you've been here long enough to know thats not how it works...although you could maybe pay them out of pocket to speed things up?
[Galaxy Note GT-N7000 General] lcmazza:
Everything you need to know is in the OP and the thread.
[Galaxy Note GT-N7000 General] dkotoric:
guys relax i know we had allot of updatea on progress the first couple of days and it died down a little so thats why i was asking

Sent from my GT-N7000
[Galaxy Note GT-N7000 General] lcmazza:
I donated to Imilka and now I did for this project too (TeamHacksung). I hope Entropy512 and Explowild can benefit from this and other donations that may come. :) This is hard work and we all have to contribute to it.

2XA72820MY3632808

8 euros and I will donate more once the project evolves.
[Galaxy Note GT-N7000 General] Entropy512:
jesus ****ing christ, you haven't read this thread at all?

Well, maybe I'll go grab some beer instead of working on the battery driver if that's how you're going to be.

Both myself and xplod have posted multiple times here since build 2, but apparently you're too damn lazy to actually READ.

On another note: I have no clue how the hell this thing is charging at all considering that the charger driver doesn't seem to be loading.