yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] tvdpas:
Hi Bauner,

My Note 1 performed wonderfully for almost a week with your NightOwl 20151003 ROM.

However, today my phone crashed. (it was rebooting when I pulled it out of my pocket)

After the reboot everything seemed hunky dory again, but now I discovered that the wireless (WPA) keys are missing.

When I add a missing key for a wireless network, wireless start working again (for that network).

Apart from this my phone works well.

Does the problem with dropped WPA keys ring a bell for you?

Regards,

Toon.
[Galaxy Note GT-N7000 Android Development] bauner:
Do you know if it was a full or a soft reboot?

After a soft reboot there can be wifi ans sim card problems.

I have also 2 reports with missing wpa keys after a reboot in my current cm11 rom.

There it seems to come from the new wifi drivers but I can't reproduce it on my device.

I will do some more testing and maybe I will use different (the one from the 4412 kernel) wifi drivers in the next release
[Galaxy Note GT-N7000 Android Development] daffy2:
Bluetooth headset no-go -> SIM "crash"

First of all, thank you very much for providing this ROM!

I installed it (20151003) a couple of days ago on an N7000 (affected by the brickbug), after having repartitioned the phone. I also removed quite a few (Google) system apps (including the Google App).

Feedback:

I can reproduce a serious problem with a Bluetooth headset - there is no sound output on the Bluetooth headset (cannot tell right now for input ;)), the dialer app hangs, and the SIM card crashes ("no SIM card") after the call has completed. One out of three attempts to use the Bluetooth headset also caused a soft reboot.

Steps to set up:

- have N7000 with 20151003 release

- configure VoIP provider (in my case sipgate.de)

- make sure that phone will use SIM and VoIP provider for outgoing calls ("choose")

- add Bluetooth headset (Plantronics Voyager) to device

- turn off Bluetooth headset

- reboot phone (just to clean base)

//phone has now freshly booted, is online on WiFi, SIM is active

Steps to reproduce:

- turn on Bluetooth headset

//headset will connect to phone

- start dialer (click on "phone" symbol)

- dial 10005 (which is the Sipgate test number - free to call)

- choose Sipgate VoIP as the outgoing route

- headset indicates that a call is starting by emitting notification

- no sound to be heard (there would be a greeting saying "welcome")

- remote party disconnects

- SIM card dies

I have now other failure modes with/after that, too:

- dialer is totally unresponsive (CPU looping?)

- one soft reboot

- one hard reboot (back to square one = Galaxy Note + triangle boot screen)

So something is very, very fishy in that area.

By the looks of it, something in the kernel may be going wrong - possibly CPU looping on something? Memory scribbling? Stack overflow? (This is aside from the basic functional problem - Bluetooth headset not working)

I am happy to play, but cannot afford the time to rebuild the phone from scratch. Any updates would have to be very incremental and reasonably safe.

Hope this feedback helps a bit - at least for any "known problems" section ;)
[Galaxy Note GT-N7000 Android Development] nursoda:
Does anyone uses NightOwl WITH device encryption? There once were issues. Any experience on whether they should be fixed today?
[Galaxy Note GT-N7000 Android Development] daffy2:
TRIM support manually only?

The first post indicates that TRIM would have to be executed manually.

I believe on other devices / other custom ROMs, TRIM is executed automatically. Why is this not done on this device/ROM? Is this due to the brickbug (my N7000 is affected)?
[Galaxy Note GT-N7000 Android Development] tvdpas:
I don't know. How kan I find out?

The phone happened to be rebooting at the time I pulled it out of my pocket...
[Galaxy Note GT-N7000 Android Development] daedric:
TRIM is executed as part of Android's maintenance. The device enters maintenance when idle for sometime, but aparently ours isn't running TRIM while doing it.
[Galaxy Note GT-N7000 Android Development] bauner:
Did you see the reboot?

If it started with the n7000 logo it was a full reboot and if it started on the NightOwl bootanimation it was a soft reboot
[Galaxy Note GT-N7000 Android Development] tvdpas:
The reboot was already well underway when I pulled the phone out of my pocket.

I didn't watch it from the start, so I can't tell whether it started with the Samsung n7000 logo or not. :(
[Galaxy Note GT-N7000 Android Development] SoulSlayer69:
I can just answer about a couple of thing, so you have to wait for a bauner reply for the rest but... N7000 on NightOwl is brickbug free. Bauner fixed it long time ago so you can wipe and trim as many times as you wish.

As far as I know, this fix doesn't just disable MMC_CAP_ERASE command but really fix it. You can test it with any brickbug test app from GooglePlay. I did a tons of trim since the fix (and many others too), and Note still fighting, so...:D

About auto-trim, I can't see a clear reason to auto-trim (ie every night), I do trim just after an OTA update or a rom flash and I suppose it's enough, because can't see real improvements if I trim more and more.;)
[Galaxy Note GT-N7000 Android Development] aryanjain:
Please tell me steps of installing Old rom

Thanks for your reply. Please tell me which kernel i have to flash before flashing this rom and steps for installing the rom. Like you mention in HOW TO INSTALL SECTION.

:good:
[Galaxy Note GT-N7000 Android Development] daffy2:
"eMMC check" (https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check) claims that my device is insane - affected by the brick bug.

All I remember about the brick bug "back then" is that faulty non-upgradeable firmware in the eMMC controller chip was the root cause (long posting by entropy256). Fixing that would thus be a challenge.

That being said - I am not overly concerned about TRIM or the brick bug. Functionality-impaired Bluetooth, the SIM card getting lost, hard reboots. That is what I am really concerned about ;)
[Galaxy Note GT-N7000 Android Development] bauner:
The installation is the same as for the newer rom.

If you have currently running my latest version then you need to boot into recovery

Then go to "wipe and format options"-"clean to install a new rom"

After this you can install the 20150802 rom and the gapps.

If you are on a samsung stock rom you can follow the steps in the fist post but flash the 20150802 rom in step 8

There is no risk of a superbrick in the jellybean official samsung roms and almost all custom roms.

I have no bluetooth devices so I can't try to reproduce your problem.

For many users bluetooth headsets seems to work fine but there are also some reports of problems with it.

You wrote earlier

"I also removed quite a few (Google) system apps (including the Google App)."

Do you have installed the gapps zip and then removed the google apps yourself?

If yes this can also be the reason for your stability problems.

If you don't want the gapps you should not flash it.

There are also modular gapps packages to install only the needed apps
[Galaxy Note GT-N7000 Android Development] SoulSlayer69:
Yeah, I was wrong, long time passed since it was fixed, so I don't remember properly: you can't check with app if bug is fixed, just check if chip was capable to brick. But it was fixed long time ago, by [MENTION=4141005]Lanchon[/MENTION] I suppose, that's why we can trim without any issue. Ofc you don't trust me, so look here-->http://xdaforums.com/showpost.php?p=58170648&postcount=691 or https://wiki.cyanogenmod.org/w/EMMC_Bugs#Device_Workarounds

About BT I can't say nothing, about SIM card and reboots, well, you can have SIM card problems after a soft reboot, just reboot normally to fix them. If you are experiencing reboots, to be sure everything goes as intended, just wipe all and do a clean install, no one reported reboots here since a lot of builds.
[Galaxy Note GT-N7000 Android Development] daffy2:
Indeed, I flashed the gapps zip, then selectively removed a small number of Google apps - among them "Google", "Google+", "Hangout", "Play Games" - which I do not use. In particular the "Google App" with its provisioning of "Google Now" seems to be more of a nuisance than a value-add (on the N7000).

I still want to participate in the Google ecosystem, so Google Play, Play Services, Mail, Calendar etc are still installed.

I need some education on modular GApps; is http://xdaforums.com/android/software/tk-gapps-t3116347 a good, trustworthy resource? It seems to be current and actively maintained by people who have a long history.

---------- Post added at 08:15 PM ---------- Previous post was at 08:10 PM ----------

Aside from Bluetooth issues, I had one more reboot (do not know whether hard or soft) at the end of stressful writing to the microSD:

I was downloading about 2-3 GB of maps data for both "Maps.Me" and "HERE Maps" onto a fast microSD over a wireless network that gives me about 50 MBit/s net downstream. Rather towards the end, I surmise, unpacking takes place, and that in turn must have caused a (hard or soft) reboot (only noticed the NightOwl animation animating - I had left the device alone for the download).

That was before I "tuned" the scope of my Google Apps on the device.

---------- Post added at 08:21 PM ---------- Previous post was at 08:15 PM ----------

Lovely reference, thank you.

This removes worries on device treatment - which was one of the reasons that I had left the N7000 on the latest and last stock forever.
[Galaxy Note GT-N7000 Android Development] bauner:
The tk gapps should work. But don't use the full or stock package because they are to big for the system partition.

And if you want to install it use the function "clean to install a new rom" in the recovery before you flash the rom and the new gapps to make sure that your old gapps will not be reinstalled from the backup script.

If you should have another reboot you can attach the file /proc/last_kmsg here before you do another reboot yourself.
[Galaxy Note GT-N7000 Android Development] AndreyGoo:
Ok, I tried 1003:

MMS now works great with a stock message app. Thanks a lot, bauner!

Torch still turns off due to time out.

Video upload to instagram don't work.
[Galaxy Note GT-N7000 Android Development] daffy2:
Attached - immediately after a hard reboot from trying the Bluetooth headset again.

I see two challenges (note that I am not at all good any more at reading Linux kernel diagnostics):

quite a few "unbalanced enable for IRQ" (and subsequent backtraces) with modules "dhd" and "Si4709_driver" linked into the kernel

two SELinux denied access for the droid.bluetooth process (https://wiki.gentoo.org/wiki/SELinux/Tutorials/Where_to_find_SELinux_permission_denial_details)

I cannot tell whether any of this is the root cause, or whether this is just the side-effect of, say, user mode doing something wrong.

I have to amend my original defect report, though: The Bluetooth headset itself seems to work, in a certain way.

Two observations:

normal calls via SIM / mobile network - i.e. _not_ via the Cynogenmod (Google?) VoIP - get audio output via the Bluetooth headset, and this does not appear to be causing any stability problems

audio recording for normal calls with the Bluetooth headset seems to be awfully bad, very choppy, very distorted (I need to look into this in more detail). Both phone and speakerphone recording are fine.

VoIP without Bluetooth headset seems to work.

So apparently there is a serious problem in the interaction between any / all of

dialog to choose phone account (i.e. VoIP / SIM switch)

VoIP _via Bluetooth_

For the record - I can reproduce this problem 100%
[Galaxy Note GT-N7000 Android Development] daffy2:
Bluetooth audio generally a problem

I just tried Bluetooth using csipsimple (https://play.google.com/store/apps/details?id=com.csipsimple) - does not work (on this specific device / ROM).

So - normal calls good, anything but normal calls, the Bluetooth headset will fail and can trigger very undesirable behaviour.
[Galaxy Note GT-N7000 Android Development] MARKHALID:
SHV-E160L entered

Hello Dev, i actually want to know if i can flash it over E160L(Korean Note)... if so what's the recovery,kernel,rom.. i should flash and a brief process that would be more than enough... quick response is much appreciated.... thanQ
[Galaxy Note GT-N7000 Android Development] nursoda:
Please don't full-quote.
[Galaxy Note GT-N7000 Android Development] MARKHALID:
Glad

it would be better if you answer my little quoted question.. thanks indeed.. hoping an answer for my q from u..
[Galaxy Note GT-N7000 Android Development] amr.fayz:
what about Marshmallow Any news and can we install it as secondary rom like this

http://xdaforums.com/google-nexus-5/development/rom-android-6-0-0-mra58k-flashable-zip-t3218315

Marshmallow Base Gapps

http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
[Galaxy Note GT-N7000 Android Development] :
That's a unwritten internet rule, don't quote such a huge page. It disrupts the viewing in here and does not help with anything.

You can't flash it into another note, this is specifically for the N7000.
[Galaxy Note GT-N7000 Android Development] MARKHALID:
Sorry

Sorry man if hurts u more.. i thought i would get help here but now it seems there are no much experts here... i gotta try it myself..:cyclops:
[Galaxy Note GT-N7000 Android Development] :
Ahhh, go ahead and try it out. Make sure you're using a 5.1.1 rom though, just flash through recovery, and let us know if it's successful.
[Galaxy Note GT-N7000 Android Development] MARKHALID:
am a bit outdated..

i have got 6.0.3.5 cwm recovery which would leave a status 7/9 error.. what can i do now!!! else i would have done a flash :cool:
[Galaxy Note GT-N7000 Android Development] bauner:
The unbalanced irq comes from my workaround for the thermal throttling and will not cause stability problems or reboots.

The selinux denials are currently only warnings because selinux is in permissive mode.

Your last_kmsg shows no kernel related reboot. Are you sure that it is a full reboot starting at the n7000 logo? Or will only android crash and it is starting with the nightowl bootanimation?

No it will not work on your device because the E160L has a complete different hardware as the n7000

First we have to wait that cyanogenmod has merged the android 6 changes.

Multirom is currently not supported
[Galaxy Note GT-N7000 Android Development] Spearman873:
Quick question, would this rom work on the Canadian Note 1 (telus) I717? I could only find the AT&T I717 so I assumed this would work.
[Galaxy Note GT-N7000 Android Development] Capodoglio:
Quick question by me, too:

In CM 11 (unofficial, I run it on an old gt-i9003) there's an interesting feature: since, like the n7000, has not led notification, the soft touch buttons light up when the screen turns off, so it's possible to know if there's something missing.

I don't know if it's possibile to enable this feature on this rom.

Little issue: sometimes I have troubles going back from browser to Google app. It freezes, black screen and then the phone asks if I want to wait or close. Sometimes waiting works, some others doesn't and the app stays freezed...

In any case, it's a great rom.
[Galaxy Note GT-N7000 Android Development] daffy2:
Many thanks for your response.

I can confirm that I get a hard reboot with the following controlled experiment:

- turn off bluetooth

- turn off bluetooth headset

- reboot phone (long-press power -> reboot)

//phone reboots through hard reboot screen with yellow triangle

//android boots through nightowl animation

- enter PIN in lock screen

- turn on bluetooth

- turn on bluetooth headset

//headset connects to phone

- press "dialer" shortcut

- context menu -> settings -> calls -> phone account settings -> make calls with (Kontextmenu -> Einstellungen -> Telefonkontoeinstellungen -> Make calls with): <the VoIP account at sipgate.de>

- back to dialer main screen

- open dial pad (bottom button)

- type 10005 number and dial (this is the sipgate test number)

// headset indicates that something is happening ("tee-dee-dup")

// phone connects to VoIP, but no audio audible

// connection time indicator increments, but is extremely choppy - might be massive, massive CPU consumption

...

and, wow, this is new and exciting:

- phone screen turns off (time out)

- phone shuts down TOTALLY hard, as in really effectively powers off to the battery indicator

Ok, lets continue:

- start phone

//phone starts at cold boot screen with yellow triangle

//nightowl animation comes up

- enter PIN in lock screen

- switch to apps

- start "Terminal Emulator" app

- Use ES Explorer to copy /proc/last_kmsg to /storage/sdcard0

- attach "last_kmsg" as "last_kmsg_hard_halt.txt" to this posting

Observations:

- I did not touch the power button ;)

- the chunkiness of the time counter might give away something; I suspect some kind of run-away thing, possibly scribbling somewhere, possibly doing stack funkiness somewhere; cannot tell.

I just started one more "experiment" where I did not slavishly follow the above; here the time counter counted smoothly, but hanging up does not seem to work correctly (this might be VoIP, though). I just also got some "not responding" for "com.android.phone", and the SIM disappeared.

Anyway, this puts a little hole into my 100% repro case.

The functional problem (no audio output into the headset) exists, still. Without audio output I cannot validate whether audio input did work (I would not be able to hear the loop back of the test number).

FWIW, I had the phone charging, in case you wonder.
[Galaxy Note GT-N7000 Android Development] -Jinx-:
Hey guys!

I have a question for you guys and especially [MENTION=799465]bauner[/MENTION].

I'm currently running Nightowl CM12.1 20150904 on my GNote N7000

The first Nightowl ROM I used was 20150802 ....Except for some minor bugs everything was fine (phone signal/GPS).

I then updated to 20151003 by doing "Clean to install a New ROM" followed by "wipe cache" and "wipe ART cache"

and installing from ZIP the updated ROM.

After this it seems all hell broke loose. My signal started dropping frequently for several seconds (my wifes Xiaomi mi4 has full signal at those times) and then I discovered the GPS in Google Maps was not working(taking very long to find position).

I rolled back to 20150904 using the exact same method( "Clean to install a New ROM" followed by "wipe cache" and "wipe ART cache") and now the GPS is working again but the signal is still dropping pretty frequently.

P.S. during "clean to install new ROM" i get following error(view attachment)

P.P.S during the install I haven't rebooted the phone at any point (clean/wipe cache/wipe ART/format sdcard0 as vfat<there where still folders inside sdcard0>/install rom from ZIP/install OpenGapps Pico from zip/Reboot)

I'm fairly new to the world of custom ROMS so I could really use some advice.
[Galaxy Note GT-N7000 Android Development] User_99:
No, this is N7000 thread and not i717 or E160L. Different device, no chance!

Not possible in N7000. This feature is called BLN and worked on some old 2.3.6 and 4.1.2 Roms and is a kernel feature. Newer kernel do not have this fewture any more.
[Galaxy Note GT-N7000 Android Development] daffy2:
... and I just got (again) into the choppy time counter situation on VoIP (promising something would break). This coincides with massive CPU consumption, as the phone becomes totally unresponsive.

Funny now: I get a soft reboot, but with an extremely slowly / choppy animated night owl. This, from my point of view, indicates that although the Android framework is rebooting, the kernel is still eating CPU like nothing. Android boot just worked out fine, by the way.

In case it matters: My (internal) network has both (router-NATed) IPv4 and (externally routable) IPv6 from my ISP, so the wlan0 interfaces has two addresses.
[Galaxy Note GT-N7000 Android Development] nursoda:
[MENTION=278852]Daffy[/MENTION]: do you ONLY encounter these issues using VoIP or on call calls also? (Just to narrow things down a bit)

[MENTION=6982764]-Jinx-[/MENTION]: When I have such issues, I do a clean install. For me, clean means to do a titanium backup of all apps and settings on the external sd. Then shut down the phone and remove that sd - no mistake can hurt your data now. Then *I* boot to recovery (you'll know the key combos by now) and head to custom format where I format system, cache, data, preload - and the internal sdcard. I never touched boot (which is accessible through recovery) and efs (which isn't). I then connect the phone to my PC (Win/Mac/Linux) which accesses my phone as MTP. I place the ROM on the internal sd and flash it. I usually boot into ROM only first to see what's in there (and take some notes which system apps I don't need; I maintain a 'clean' script that I always flash after flashing a ROM). I use it a while and test w/o Google services. If all looks stable, after a while I flash appropriate tiny or nano GApps. Test again. Start to set up things. Etc. Takes a while. The insert external sd (which is formatted vfat since this seems to cause least trouble). I only recover apps that I really want to use from titanium, mostly with data. I don't recover any system apps or settings. I prefer to set those anew. This takes time. I only do this about one or twice a year. Except when explicitely advised by the ROM maintainer, I install all minor updates "dirty", NightOwl updates were smooth all along that way. Only thing I shoul have done last time (but was too lazy): I shoud have tried the repartitioning. But that thread IS quite long and there seem to be quite some hurdles. I'm not sure if I'd dare if I were new to custom ROMs. Maybe someone that did it takes the time to do a proper *condensed* writeup. I'll do IF I repartiton. But up until now, my device is stable, and: never touch a running system...

BTW: I did install Xposed now since I was missing one module, and it was a no-brainer. But I seem to have installed too many modules now, my device is significantly slower now. May also stem from having moved *many* Apps to SD...
[Galaxy Note GT-N7000 Android Development] bauner:
No it will not work because your device is using different hardware

The button backlight notification is not included in the kernel.

"sometimes I have troubles going back from browser to Google app"

What do you mean with google app? The google now launcher?

It is possible that you get this problem because it is running out of ram if you are using an ram intense launcher like the google launcher.

You can try if setting "Allocation" from 300 to 350 in /system/etc/init.d/02zram and then reboot will change anything

Your log shows no kernel related problems which could be the reason for.

It shows 1 normal shutdown and the other one stops like if you had removed the battery.

If you want you can try if the 20150913 kernel will change anything

The error with clean to install a new rom in the recovery is normal. It will work as it should.

If you want to update the rom you only need to flash the new rom and wipe the dalvik cache.

You only need "clean to install a new rom" if you want a complete clean installation or if you downgrade to a older version.

There are no other reports with gps problems since a long time ago.

Will your device vibrate if it is loosing the signal?

Will it work as before if you downgrade to the 20150802 rom?
[Galaxy Note GT-N7000 Android Development] -Jinx-:
[MENTION=799465]bauner[/MENTION]

My GPS problems have been fixed after downgrading to 20150904 so maybe that was just a coincidence or something else going on.

It doesn't vibrate....the signal just goes down until it goes to empty....after a few seconds it goes up again.

It did the same a few days ago when I was in another country and switched to a local carrier/sim card.

At the same time I lose internet connectivity.

I'll try to downgrade to 20150802 again and see if that works ok in terms of signal rece[tion....the problem is I'm on the road alot and atm this is my only device so I have to catch a day when I'm mostly free to do that.