yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] neel3788:
Help Needed :)

Hi Bauner,

Thank you for supporting the device which is quite old now :) .

I wanted to ask about the problems I am facing.

All the other members are saying that the ROM is very smooth, better than the cm13 build. But my experience is very opposite to this. The ROM performs poorly, from opening the apps to the animation speed. The animation performs in a very choppy way (like I haven't installed video drivers, this what happens in the case of windows desktop, same choppiness). I have tried to change the default animation speed from the developer's option but the result is still very bad. The experience is same for beta 3 and 4.

I have clean installed the ROM. I must have missed something, could please help/guide me how do iI get the ROM working right.

Thanks in advance.
[Galaxy Note GT-N7000 Android Development] D@rekills4:
I wanted to report a minor bug.

Just a slider switch with no label on it.
[Galaxy Note GT-N7000 Android Development] nurulhuda859:
About Custom ROM of GT-N7000

When you will release the stable version of Nougat for GT-N7000? I want to help you to find out bugs and any other help that you want.

Thanks in advance.
[Galaxy Note GT-N7000 Android Development] Panzukk:
i didn't but the rom installed normaly, without bootloop, but is very laggy. Do you think that clean install will work better?
[Galaxy Note GT-N7000 Android Development] bauner:
Currently not. Maybe later if I have more time...

There seems to be a toybox insmod problem.

I built the module myself and had the same problem.

Then I tested it in the recovery (with busybox) and there it will work.

I currently don't know the reason

1|root@n7000:/ # insmod /system/lib/modules/xt_HL.ko
insmod: failed to load /system/lib/modules/xt_HL.ko: Bad address
1|root@n7000:/ # reboot recovery
[bauner@pc modules]$ adb disconnect
disconnected everything
[bauner@pc modules]$ adb shell
~ # insmod /system/lib/modules/xt_HL.ko
~ # lsmod
Module Size Used by Not tainted
xt_HL 1491 0

Did you give it some time after the first boot?

For me it feels a bit faster as cm13.

Did you try if disabling the animations in the developer settings will make it faster

This seems to be a lineage or opengapps bug because I have the same on my oneplus device with lineage 14.1

Maybe it will work better with a complete clean install. But I don't know. I always do a complete clean install on a major version change
[Galaxy Note GT-N7000 Android Development] Vlxda:
Thank you for your time.

My xt_HL.ko gives an error in recovery mode.

Maybe you will give me your module for the test, please.

/sbin # insmod xt_HL.ko
insmod xt_HL.ko
insmod: can't insert 'xt_HL.ko': invalid module format
[Galaxy Note GT-N7000 Android Development] bauner:
I have attached it.

I have only tested it with the twrp recovery.

What is the vermagic of your builded module?

If it is not

3.0.31-Bauner-g38edc975 SMP preempt mod_unload ARMv7 p2v8

you could try to modify it with an hex editor
[Galaxy Note GT-N7000 Android Development] bauner:
I have attached a toybox which will not use finit_module which can insmod kernel modules in the rom.

I will also use it as default in the next rom
[Galaxy Note GT-N7000 Android Development] Vlxda:
Thaks! In TWRP recovery insmode OK!

/sdcard0 # [6nlsmod
lsmod
Module Size Used by Not tainted
xt_HL 1449 0

Attached toybox.zip if install in TWRP -- META-INF not found...... error

Ok! May be next NightOwl Beta You turn on "TTL" — target support? Thank you for your time.
[Galaxy Note GT-N7000 Android Development] bauner:
The toybox.zip is no installation zip file.

You need to extract it and copy it with adb or an root explorer to /system/bin/

Why do you need the ttl target?
[Galaxy Note GT-N7000 Android Development] Vlxda:
It's necessary for use iptables:

iptables -t mangle -A POSTROUTING -o rmnet+ -j TTL --ttl-set 64
[Galaxy Note GT-N7000 Android Development] bauner:
Yes I know, but I wanted to know the reason why you want to do it?
[Galaxy Note GT-N7000 Android Development] sriramsi:
I faced the same issue. Initially the ROM was very smooth. However, it progressively became slower and after around 3 weeks of usage it became very slow, there were freezes and applications would take very long to launch. I have now rolled back to the Marshmallow ROM and this is giving a steady performance without much lags.
[Galaxy Note GT-N7000 Android Development] NLJohn:
Same over here. First the ROM is fast.

Then the ROM slows down and after a few days it chrashed and automatic reboots and hangs while booting.

It happens for me for the 3th time after a full new install
[Galaxy Note GT-N7000 Android Development] Prinus:
I don't have these issues. I don't know if my late night auto trim helps.

I haven't had any crashes, reboots or hangs whilst using B4 (had some before but can't remember which version).

I dirty flashed B4 over the previous dirty flashes. My last clean install was Alpha6.

I'm not able to pinpoint what goes wrong where, just adding my 2 cents.
[Galaxy Note GT-N7000 Android Development] :
If you all are experiencing these crashes, check your RAM usage. It sounds like a memory leak and should be fine after a reboot, also trimming every two days should help.
[Galaxy Note GT-N7000 Android Development] waro470:
So, you trim every other day?
[Galaxy Note GT-N7000 Android Development] :
Nah, I use FSTrim to auto-trim for me. I usually set it at 3am and to do it every two days, so I don't have to touch it. It will give me a notification that trimming has been carried out successfully too.
[Galaxy Note GT-N7000 Android Development] Prinus:
Installed the TWRP update and tested a bit, not everything. Lost my theme, no big deal.

The rest seems to be working correctly for me, mainly tested backup,restore and install. To me they're the most important.

I did not dare to install the TWRP app yet, but that's me being a coward at this point. This is still my daily driver. Thanx to everyone involved, especially [MENTION=799465]bauner[/MENTION], for bringing this update to us.

Cheers
[Galaxy Note GT-N7000 Android Development] Prinus:
[MENTION=799465]bauner[/MENTION]

Had a full reboot this morning whilst listening FM radio via Spirit 2.

Screen was off, sound started stuttering en turned off, when i pulled the phone from my coat pocket I had the Samsung logo.

last_kmsg attached
[Galaxy Note GT-N7000 Android Development] :
Btw bauner, do you have the kernel-only zip for this or can I just use the one from Lineage 13?
[Galaxy Note GT-N7000 Android Development] bauner:
I did not make a seperate kernel zip for 14.1.

What exactly do you wan't to do?
[Galaxy Note GT-N7000 Android Development] :
Oops forgot to explain. I wanna try building the 14.1 kernel too, so I was thinking maybe it's possible to just replace it into the other zips.
[Galaxy Note GT-N7000 Android Development] bauner:
You can use your existing kernel zip file and replace the boot.img and /system/lib/modules/*

You also need to build the kernel with the ramdisk.cpio for 14.1

I have attached it
[Galaxy Note GT-N7000 Android Development] :
Yeah, thanks. I used the ramdisk for the cm12.1, are they the same? Since I'm building for cm11 to 14.1 right now.
[Galaxy Note GT-N7000 Android Development] wandro:
Beta 4: 5-10 minutes after [re]boot required until CPU calms down again

Seemingly very many apps are launched on boot, and it takes a very long time until the CPU calms down and short response times can be expected again.

You can improve the situation to some extent if you use a startup manager to prevent these many apps from being launched on boot.
[Galaxy Note GT-N7000 Android Development] bauner:
Each android version needs its own ramdisk.
[Galaxy Note GT-N7000 Android Development] :
Well this is embarrassing. You wouldn't happen to have ramdisks for the CM11 and Lineage13 do you?
[Galaxy Note GT-N7000 Android Development] bauner:
I have attached the ramdisk for lineage 13.

I don't have it for cm11.

To build your own you need to download the cm11 source and do a mka bootimage
[Galaxy Note GT-N7000 Android Development] :
Alright, thanks again
[Galaxy Note GT-N7000 Android Development] Mr.AndroidExperimental:
Random shutdowns

The ROM is working incredibly thx to [MENTION=799465]bauner[/MENTION], but i have been facing some issues lately

1) i am getting random shutdowns (or i think the phone is rebooting itself at random moments)

2) And after the rebooting is finished, sometimes the battery level weirdly lowers ( for an example it was 61% before reboot And is now 10%)

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

Hope u can help me but no rush :good:
[Galaxy Note GT-N7000 Android Development] geniezlife:
Are the random reloads and battery issues related to the android 7.1.1 issues because of which Google downgraded the Nexus phones back to 7.0? I know it is rather early for conjectures, just thought I'd bring it up. Thanks Bauner for all your wonderful work. Happy to wait for your analysis and updates :)
[Galaxy Note GT-N7000 Android Development] bauner:
Do you have screen flickering on low battery? If yes you should try to replace your battery.
[Galaxy Note GT-N7000 Android Development] Mr.AndroidExperimental:
Yes that happens when the batter is somewhere near 15% i will try to replace it
[Galaxy Note GT-N7000 Android Development] Panzukk:
I'm having some problems with the root access. Apps ask for it, i give the permision, but they doesn't what they suposed to do. Like es file explorer, i've tried to delete a file and it says that i can't
[Galaxy Note GT-N7000 Android Development] bauner:
Did you enable root for apps and adb in the developer settings?

Will you see the # symbol on top if an app is using root?
[Galaxy Note GT-N7000 Android Development] Panzukk:
i did only for apps, but, when i use a root app the # appears
[Galaxy Note GT-N7000 Android Development] bauner:
You can try if enabling root for apps and adb will make a difference.
[Galaxy Note GT-N7000 Android Development] shyvanna:
While using the pegasusq governor the phone turned sluggish while I was reading something(epub) and torrenting. That showed on no-frills and cpu-z. Side note: maybe it is related, some tests on vellamo on their multi-core tests turned up an error. That is when I used the performance governor. If I use ondemand or pegasusq, there are no errors.
[Galaxy Note GT-N7000 Android Development] bauner:
The pegasusq governor is optimized for quad cores and will have some problems with our cpu.

with the performance governor the cpu will run at the highest clock all the time without frequency scaling. This explains the behavior in your no frills screenshot.

And it seems that cpu-z will also not detect it correctly because both cores stopped is not possible.
[Galaxy Note GT-N7000 Android Development] bauner:
The LineageOS 14.1 Beta 5 is finish

Changes:

* Updated lineage sources

* March security patches

* Remove 800Mhz cpu step up limit

* New dark bootanimation (modified by Fix_ita)

* Toybox: fix loading of custom kernel modules

* Some kernel updates
[Galaxy Note GT-N7000 Android Development] Gaukler_Faun:
Thanks for the new update. I attach four flashable zip-files. I made them to save some time after an update and just want to share.

GF_Mod_keyboard.zip: contains a functional (except panorama mode) version of snap camera and libjni_latinimegoogle.so for swipe function on AOSP keyboard (necessary if you don't use any gapps).

GF_Mod_keyboard_gps.zip: same as above zip-file and additionally a modified gps.conf file for better gps support in Germany.

..._withoutSnap.zip: the same as above, but without SnapCamera.

If you want to use the the gps.conf file in your country, just download the second zip-file, unpack it and edit the gps.conf file in the "/system/etc" folder. Just change the "de" matching to your preferred country code.

[MENTION=7762545]Fix_ita[/MENTION]: Thanks for the new bootanimation!

Regards

Gaukler Faun
[Galaxy Note GT-N7000 Android Development] Panzukk:
for me, beta 5 is feeling a bit laggy
[Galaxy Note GT-N7000 Android Development] 52wiseson:
Hi Bauner, thank you so much.

I really like your dark bootanimation very much.

A request: please provide the picture as I wish to make into my lockscreen wallpaper.

Thank you.
[Galaxy Note GT-N7000 Android Development] bauner:
You can enable the developer settings and then go to settings-developer settings and disable the 3 animation settings.

The bootanimation is in /system/media/bootanimation.zip

Inside the zip file you will have each picture of the animation
[Galaxy Note GT-N7000 Android Development] shyvanna:
The bootanimation is in /system/media. It is a zip file that contains the pictures for the boot animation.
[Galaxy Note GT-N7000 Android Development] 52wiseson:
[MENTION=799465]bauner[/MENTION], very grateful for your reply. Thank you.
[Galaxy Note GT-N7000 Android Development] Capodoglio:
Hi all, and thanks Bauner for your work.

I didn't write for a long time because I had no problems with LineageOS 13.

I decided to give a try to beta4 and now beta5, and since then I experienced some issues with beta4: some random reboot, the last time the phone stuck for a while on the yellow triangle image and then shut off, then tried to reboot three or four times until it did. Then I downloaded Beta5 but there was no way to restart in recovery mode... I had to remove the battery and try to restart vol up + home + power. But then again it stucked in the first image with yellow triangle. I had to try 4 or five times to enter recovery, but then I managed to install beta5, and now I'm testing.

I'll let you know if something weird happens.

Anyway, thanks again! And keep on!
[Galaxy Note GT-N7000 Android Development] VAMET:
Dear bauner

First of all thank you for your great work and time. I have installed Beta 5, but I think my N7000 works much slower, performance is much worse, than in Beta 4. I'm testing Clash Royale game and in Beta 4 it's working smooth, but in Beta 5 it's not. I have even set highest performance in Settings>Battery and it's not helping.

EDIT

Yes, for me it's too.

Sincerely
[Galaxy Note GT-N7000 Android Development] marco2233:
Error E3004: Wrong model number

I had a second hand phone that showed GT-N7000 in the android info and even at the boot logo it says GT-N7000. So I tried to install this, and after wiping system

and trying to flash this rom it says:

"E3004: This package is for device: galaxynote, n7000, N7000, GT-N7000; This device is SGH-i717"

This is something I wasn't expecting, is there any way to install these ROMs, like manually modifying this model check?

The SGH-i717 is the same phone but US AT&T

Thanks a lot
[Galaxy Note GT-N7000 Android Development] Panzukk:
THIS! This is what's happening to me, in the roms was very smooth, but in beta 5, it isn't anymore. Whatsapp, instagram, chrome, even typing with swiftkey or gboard isn't smooth anymore
[Galaxy Note GT-N7000 Android Development] VAMET:
Dear Friends

I may only confirm your words... Beta 6 is needed ;)

Sincerely
[Galaxy Note GT-N7000 Android Development] D@rekills4:
I flashed it, but for some reason the MTP connection is not working. Windows detects the connection but I cannot see the device in File Explorer. It was working fine in the previous build of TWRP.

I tested with two different wires and Windows 10, (didn't test with Linux).

I am not facing any of these issues with beta 4 or beta 5.

Rather I had a 450 hour uptime with beta 4.

I felt the same but I am going to test for 2 more days before I jump to conclusions.

I will post my findings then.

However, I do feel this is more of a LineageOS related bug than device specific.
[Galaxy Note GT-N7000 Android Development] urabus6:
Hi. I have this problem. now, when I go to recovery there's a lineage os menu that doesn't let me do anything. It gives error when I try to flash from sdcard0, doesn´t recognize anything from sdcard1. Has anyone had this issue?

https://www.dropbox.com/s/il2nthfhi9f7p2m/20170322_103015.jpg?dl=0
[Galaxy Note GT-N7000 Android Development] bauner:
First you should take a loock on the sticker under the battery which device you realy have.

The i717 looks like the same device but it is not using the same hardware

I tested it only with linux and there it is working without problems.

Maybe you need a different driver because the device id is different

In the rom:

Bus 001 Device 005: ID 18d1:4ee7 Google Inc.

In the recovery

Bus 001 Device 008: ID 18d1:4ee2 Google Inc. Nexus Device (debug)

Maybe you flashed something for an other device? Or another kernel?

I have never released a rom/kernel/isorec with the lineage recovery.

You can try a complete clean install with the following way from the first post

The steps to install it from an stock samsung rom are:

and start with step2
[Galaxy Note GT-N7000 Android Development] marco2233:
Hi Bauner, thanks for the response! I did look at the sticker and it's a sticker for a Galaxy Note II- SM-N7100!

So obviously this phone has been messed with. It can't be a Note II because it has the body of a Note I (I checked)

I think it must be a GT-N7000 because the i717 has a different keyboard layout which mine does not have.

I would like to manually change the model number so I can install your ROM.
[Galaxy Note GT-N7000 Android Development] urabus6:
Maybe you flashed something for an other device? Or another kernel?

I have never released a rom/kernel/isorec with the lineage recovery.

You can try a complete clean install with the following way from the first post

The steps to install it from an stock samsung rom are:

and start with step2[/QUOTE]

I already clean installed three times from stock to nougat and the result is always the same. Tried with Beta1 and Beta5
[Galaxy Note GT-N7000 Android Development] Gaukler_Faun:
I already clean installed three times from stock to nougat and the result is always the same. Tried with Beta1 and Beta5[/QUOTE]

I had the problem also on an earlier Android version. There was a setting called "actualize cm recovery" or something like that. I checked it and the result was that during next flashing I got the default "cm recovery" which looked like your screenshot. With this recovery it was only possible to flash official update.zip files from Cyanogenmod.

Since I use a Linux desktop, the only possibility was to flash a new recovery image via heimdall to get a working recovery back.

I searched on the internet, but all cyanogenmod wiki sites are offline. I found a tuturial here:

http://jannecederberg.fi/2015/05/26/cyanogenmod-11-on-samsung-galaxy-note-gt-n7000/

Following this tutorial you should get a working CWM recovery back (but be careful: KitKat based). I attach also the img-file, which I used to get my CWM recovery back (I think that was the file, no warranty). If this is the right file you will get a Lollipop based CWM recovery and then you could flash the current rom like always.

And again: NO WARRANTY THAT THIS WILL WORK. While flashing kernels, recoveries and other stuff there's always the possibility to damage your phone.

Hope I could help.

Regards

Gaukler Faun
[Galaxy Note GT-N7000 Android Development] asto63:
Usb otg not working on beta 5 too.
[Galaxy Note GT-N7000 Android Development] bauner:
If you don't want to flash with heimdall you can also try the following.

Follow The steps to install it from an stock samsung rom are: again

And flash also a twrp isorec recovery (link in the first post) in step8 before you reboot your device
[Galaxy Note GT-N7000 Android Development] urabus6:
I had the problem also on an earlier Android version. There was a setting called "actualize cm recovery" or something like that. I checked it and the result was that during next flashing I got the default "cm recovery" which looked like your screenshot. With this recovery it was only possible to flash official update.zip files from Cyanogenmod.

Since I use a Linux desktop, the only possibility was to flash a new recovery image via heimdall to get a working recovery back.

I searched on the internet, but all cyanogenmod wiki sites are offline. I found a tuturial here:

http://jannecederberg.fi/2015/05/26/cyanogenmod-11-on-samsung-galaxy-note-gt-n7000/

Following this tutorial you should get a working CWM recovery back (but be careful: KitKat based). I attach also the img-file, which I used to get my CWM recovery back (I think that was the file, no warranty). If this is the right file you will get a Lollipop based CWM recovery and then you could flash the current rom like always.

And again: NO WARRANTY THAT THIS WILL WORK. While flashing kernels, recoveries and other stuff there's always the possibility to damage your phone.

Hope I could help.

Regards

Gaukler Faun[/QUOTE]

Thank you very much, I apreciate the help.

---------- Post added at 12:00 PM ---------- Previous post was at 11:51 AM ----------

Thank you for your reply. I had already done that and it worked. My only doubt is, if I reflash cwm will it continue with the problem?

I ask this because all the system images I have were made with cwm and I would like to use them.
[Galaxy Note GT-N7000 Android Development] marco2233:
How to disable model check?

Hi Bauner, Could you please tell me how to disable the model check in your ROM install scripts?

I desperately need to install this on a bricked GT-N7000 which has the wrong model number somewhere (i717)

I tried all ROMS for i717 do not work.

Thanx a lot!!!
[Galaxy Note GT-N7000 Android Development] bauner:
You mean that you have done your nandroid backups with cwm???

To go back to philz recovery (cwm based) you can flash the isorec disabler.

If you are on beta 5 it should (hopefully) not happen again because the recovery update should be disabled by this commit

https://github.com/bauner/cm-androi...mmit/705f55a9443b717630f3b33423afde4161c5e3b4

You can edit the file META-INF/com/google/android/updater-script

inside the rom zip file (if you use windows you need to do it with an editor which can handle linux text files correctly! like notepad++ https://notepad-plus-plus.org/download/v7.3.3.html)

and remove this line

assert(getprop("ro.product.device") == "galaxynote" || getprop("ro.build.product") == "galaxynote" || getprop("ro.product.device") == "n7000" || getprop("ro.build.product") == "n7000" || getprop("ro.product.device") == "N7000" || getprop("ro.build.product") == "N7000" || getprop("ro.product.device") == "GT-N7000" || getprop("ro.build.product") == "GT-N7000" || abort("E3004: This package is for device: galaxynote,n7000,N7000,GT-N7000; this device is " + getprop("ro.product.device") + "."););

But go sure that you really have a n7000 if you do this! If you have an other device this can hard brick it in the worst case!
[Galaxy Note GT-N7000 Android Development] AshleyJackson:
Continuous boot loop..

I installed beta 5 last night and it was working amazingly well. Absolutely no issues at all, and then I went and did something stupid.

In playing with my phone I had forgotten that there was a specific instruction to not install SuperSU. I installed it and I am now stuck in a continuous boot loop.

I can't get into recovery mode or download mode, and nothing is showing when using "adb devices".

Is there any solution to fix my screw up?

EDIT: I was forgetting to hold the home button :/

On a side note, I may have found a bug. I am receiving no Haptic feedback from the button. Is this an issue or is it disabled by default?

EDIT #2: Scratch that. I had power saving enabled.
[Galaxy Note GT-N7000 Android Development] philip_rhoades:
I just updated to Nightowl-lineage14.1-beta5-n7000.zip and the write problem to sdcard1 persists (I use the Ted Text Editor to try and save files) - is this problem because of the changes to android with later versions? Using AryaModV8_XXLTC.zip I had read / write access to both sdcards . .

Thanks,

Phil.
[Galaxy Note GT-N7000 Android Development] zhengqiming:
Hi Bauner,How about submitting your new device tree and kernel source to Lineageos Team? :)
[Galaxy Note GT-N7000 Android Development] bauner:
Yes it affects only newer android versions

The device tree would be possible but it would need some changes and cleanups to make it compatible with the existing lineage galaxys2-common tree.

I think the kernel would be an problem because all lineage exynos 4 devices are using the same smdk4412 kernel.