yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] lee.wp14:
I haven't try out f2fs, I have been using ext4 since then.

Talu@xda has a lot of f2fs and other fs commits… i might create a new branch and bringover his f2fs commits. But for the time being I'm still monitoring/testing kernel changes. I've bringover los17 commits to our los16 trees. Also now due to the corona… college stuffs has been a huge mess now

As always, you all can see my github for my progress :)

Does f2fs has any improvements over ext4 when you use it on n7000?
[Galaxy Note GT-N7000 Android Development] tophechris:
Hello,

Thanks Lee.wp14 for developping this Rom !

I am using the 20200225 version for few days and it seems working quite well, except the SIM PIN that has to be disable in advance. Even GPS seems working, with a slower 1st connexion time.

I am however bothered by the very unstable WiFi connexion. Impossible to reliably use WiFi as it disconnects quickly and often only rebooting my phone allows WiFi to work again.

I have no idea how to solve this.

Other minor issues:

- the wallpaper app is not working

- I can’t make spirit2 radio app working. It tells me "Tuner API did not start, this device may need a kernel with a working FM driver"

Any advice on how to improve wifi stability?

Thanks again
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Hi there,

SIM PIN issue workaround has been tested ok and it will be solved on the next build.

I intentionally change the wallpaper app to the old one due to:

1. The new one from LineageOS is laggy because it loads all the wallpaper preview as actual image instead of thumbnails

2. The new one won't work if you didn't have internet connection

3. If you have a wallpaper with a very large size (like, 4k res), then the new one will crash

You can access the old wallpaper app from Settings -> Display -> Wallpapers, or any 3rd party launcher will work with it too.

For the spirit2, I will look into it when I have time. Strange, it should have worked since I've relocated the FM driver to where spirit2 looks for.

About Wifi stability, there could be a number of reasons.

1. Is it fine on other ROMs?

2. What is the first 3 groups of your wifi mac address ? For example, "50:cc:f8" of "50:cc:f8:xx:xx:xx"
[Galaxy Note GT-N7000 Android Development] tophechris:
Thanks for your quick answers and advices (found the wallpaper app in settings).

I was on Bauner' Android 7.1.2. Rom and WiFi works very well. I didn't notice any problem.

When I am connected on wifi I have mac 00:37:6d:6b:...
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Hi there,

I checked and your mac address OUI is in our macloader binary.

I've make some changes to the wifi configuration for the next release. As there's too much wifi channel overlapping at my area, I can't really properly test the wifi, even my other device also face connection issue. Maybe you can stick to 7.1.2 first until my next release.
[Galaxy Note GT-N7000 Android Development] tophechris:
I wiped cache and dalvik and flash again the rom.

Wifi stays connected longer but sometimes it disconects, and then it does not reconect automatically. Each time, I have to reconnect manually.

And sometimes wifi scanner doesn't look anymore for available wifi. I have then to reboot. Only my wifi channel where I live, no overlapping.

Thanks again for you investigation and answers !
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Hmm.. it shouldn't have disconnection issue, delayed auto connect is to be expected. This is kinda strange. I hope that your wifi antenna connection is well-contacted?

Maybe you can grab some logs from adb logcat or /proc/kmsg after the problems happened so I can look into it, if possible.

For my place, it is thanks to my local ISP providing TP-Link router which use 40MHz on 2.4GHz automatically, there's totally no usable wifi channel at my neighborhood. And their channel is auto by default, so it jumps forth and back every few days when they reboot their router.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
For the first behaviour, it looks exactly like what I was getting when I'm working on aosp 9.0 based rom (DotOS) for our n7000 a few weeks ago. However I solved it by removing a commit: https://github.com/leewp14/android_...mmit/d421297957bebd3fafe962ba12153d4bcb906d24

But it shouldn't be an issue on LOS16 because this commit does not exists in LOS16. Probably there's a problem communicating with the wifi module. Does bluetooth works well for you? Since Bluetooth and Wifi is the same chip.

This is interesting, as I never have this problem before. For me, my worst-case scenario is to just turn the wifi off and on when it scans no network.
[Galaxy Note GT-N7000 Android Development] tophechris:
Thanks for your feedback.

Bluetooth audio and files transfer work well, I didn't notice anything wrong on that side.

Since I re-flashed the ROM, Wifi connexion is more stable once connected, but getting the device to connect is still not easy. Sometimes turning off and on again trig out the scan again, but in most case it still doesn't connect automatically. And it happen often that the only solution to get wifi working again is to reboot. On reboot, wifi get always connected quickly and automatically.

Maybe my old N7000 is tired after 8 years of being used daily!
[Galaxy Note GT-N7000 Android Development] bro55her:
Battery Drain After Reboot Problem

I am on buid 20200225 lastest buid but if I reboot my device battery drains insanely like 87 to 15 but if I power off and boot after it there is no drain problem thx for this awesome rom btw I started using my n7000 more often because of this awesome rom.

Do you plan Android 10 for this device? That would be pretty cool :D Thank you and other developers working on this device for all the effort.

Is DOT OS release near?
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Hi there,

Our device has MAX17042 fuel gauge, it does not depend on current for battery level sensing. The battery level reading on our device wouldn't be 100% accurate for some cases - it is designed such that it converges towards truth overtime. You can read these posts for more information:

https://xdaforums.com/showpost.php?p=18677485&postcount=31

https://xdaforums.com/showpost.php?p=30520238&postcount=13

Battery level drops is to be expected when there is high load while the battery fuel gauge initializes. Especially for now our device is actually in an "underpowered" state.

Android 10... yes I hope to see it on our device too. For now I will focus on pie first. After i9100 (galaxy s2) has a fully stable pie build, I will work on it. Rest assured, our n7000 device sources are 90% Android 10-ready already!

You can have a look at the i9100 forums for Android 10 development, n7000 sources depends on i9100. i9100 developer rINanDO has done a lot of work for a working Android 10 bringup!

About DotOS, it has no updates already (they are preparing for Android 10), their last update is end of 2019. I will focus solely on LOS only.
[Galaxy Note GT-N7000 Android Development] llawarta:
Hey

Great work, mate just tested for a few days and here's some feedback:

Coming from stock JB, working fine, no issues.

1. Wifi is buggy, after auto screen off wifi becomes faulty, does not autoconnect again need to go to wifi settings and manually reconnect, but not always work at first try. I don't have channel pollution at my house and router signal is good.

2. Netflix content has issues, green bars and diagonal lines blinking while playing stuff (check attachment).

3. No hdmi, I use a lot my n7000 as tvbox to watch Netflix and movies.

4. General lag on the UI, after some days and restarts this does not change.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Hi there, thanks for your feedback.

1. Recently I did experienced wifi droupout issue on my side but with 5GHz AP, for me 2.4GHz never disconnect on its own. Are you using 2.4GHz?

2. This looks like a funny bug :D However may I know how to get Netflix work? I couldn't get it work on my side. What I can say is that, the player might be using software decoding (CPU decode). Software decoding is not ok on our device, you will see artifacts (like what you see), and also you can't play HD content well. I think playback should be no problem if the player is using Hardware decoding.

3. Yes... the mhl/hdmi sources are closed-source (means no way to utilize it) and is not supported since CM10, so is LineageOS. If this is an important feature, I'm sorry but I'm afraid your best choice is to stay on stock ROM.

4. Yes... our 2D and 3D processing unit is slow (maximum 267MHz). Now Android animations and transitions are very complicated compare to before so our device is lacking the capability to process graphic contents. As per my testing, we need at least 400MHz (to be 100% smooth, 600MHz actually) to achieve a smooth UI. However overclocking up to 400MHz is way too much beyond the stock 267MHz so I will just leave it as it is. Normal scrolling shouldn't be an issue right?
[Galaxy Note GT-N7000 Android Development] lee.wp14:
CHANGELOG:

- n7000: update GPS configuration

- n7000: update build fingerprint

- n7000/kernel: add TriangleAway support

- galaxys2-common: reconfigure wifi configuration

- galaxys2-common: user configurable SWAP

- galaxys2-common: actually fix in-call audio control

- galaxys2-common: kernel modules to system

- galaxys2-common: add Magisk build support (credits to @rINanDO)

- galaxys2-common/kernel: bring over LOS 17.1 commits (credits to @rINanDO)

- kernel: implement charge current control (credits to @TALUAtXDA)

- kernel: prevent LCD lock busfreq

- kernel: reconfigure ASV/DVFS for BUS/GPU

- kernel: remove inbuilt recovery

- kernel: bring back PegasusQ, adapted from Perseus-S3 (credits to @AndreiLux)

- kernel: raised safefreq to 1.4GHz

- kernel: bluetooth stack update (credits to @TALUAtXDA)

Installation Notes:

Install as per normal update. However, please flash lanchon-twrp-patcher-20160417-n7000.zip (under n7000/misc/recovery/patch) beforehand if you haven't do so.

Users with addonsu, kindly reflash addonsu after updating the ROM. OpenGAPPS users, gapps will be retained unless /system is wiped.

For Magisk support, flash boot_magisk.img after flashing the ROM. Then, install Magisk Manager in Android.

Notes:

1. FM Radio (Spirit2) should be working now (sorry guys! last few builds didn't make it to work as intended).

2. You can now configure your own SWAP configuration (physical/zRAM/none) in /system/vendor/etc/fstab.swap.smdk4210. Default is no SWAP.

3. TriangleAway is now supported. Set ro.mmc.mmcblk0boot0.force_ro to 0 in build.prop, reboot, and reset counter in TriangleAway. Remember to set back to 1 for safety reasons.

4. Magisk is now supported (thanks to @rINanDO). You do not need to flash Magisk ZIP. The boot_magisk.img is already a Magisk-patched kernel.

5. SafetyNet: Yes, you can pass SafetyNet with MagiskHide. However you need to toggle it on every boot, because MagiskHide is not working after every reboot.
[Galaxy Note GT-N7000 Android Development] llawarta:
I'm using 2.4 Ghz Wifi, public ssid WPA2. Another way to make the wifi issue happen is disable and enable the wifi connection while being used (by the top bar switch). Do not reconnect and shows a question mark (?) along the wifi signal icon. I don't know if matters but I have turned off bluetooth because I don't use it at all.

Latest versions of netflix does not install on the rom, but this one installs and work fine (I use this same version on another device flawlessly.):

https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-4-16-3-build-15172-release/

On stock rom Netflix runs smoothly (Netflix 3.16.3), yeah older version than the above.

I was hoping for some workaround for HDMI, but no problem.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
I will try the Netflix when I have time, thanks!

Sometimes the wifi module is not ready when turn on, if it is the case then the wifi scans no network (you can open and check), because the wifi module is not fully initialized. This happens when we (or the system) toggle the wifi module on/off too quick. A simple turn off - wait 3 seconds - turn on will do in normal cases.

On pie, question mark indicates that the device is not connected to any wifi networks, except if it says "No internet" beneath it.

EDIT: Today I spent some time to tinker around with the wifi settings and I solved my 5GHz wifi dropout issue on 7000 by setting the 5GHz channel width to 40/20MHz instead of 80MHz.... Btw my area has no 5GHz channel overlapping.
[Galaxy Note GT-N7000 Android Development] joam280:
it gives me an error when installing the latest version, is it necessary to delete everything?

Enviado desde mi Nexus 9 mediante Tapatalk
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Not really, I also have tried on two n7000 by applying on top of old build. Can you provide a screenshot or recovery log?
[Galaxy Note GT-N7000 Android Development] joam280:
This is the error [emoji24]

Enviado desde mi Nexus 9 mediante Tapatalk
[Galaxy Note GT-N7000 Android Development] lee.wp14:
I see… you haven't applied the twrp patch that I mentioned in the last update?

You can download it in my drive, it is lanchon twrp patcher.

Bevause we are using i9100 recovery, so we need to convert it to n7000. With this, I don't need to modify the zip file anymore to remove the assert check, which is safer.
[Galaxy Note GT-N7000 Android Development] joam280:
could you leave me a link I can't find it in the forum, thanks

Enviado desde mi SM-G973F mediante Tapatalk
[Galaxy Note GT-N7000 Android Development] lee.wp14:
https://drive.google.com/drive/folders/1D8-iWa4Y6WHU1j9gXHujCRONrJC8ioDd

Go to n7000 > misc > recovery > patch

Download lanchon-twrp-patcher-20160417-n7000.zip

Flash in twrp, then reboot recovery and try flash the rom zip again.

You only have to do this once, unless if you reflash the TWRP isorec recovery.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Did it work? I want to sleep already xD it's 5am here :33
[Galaxy Note GT-N7000 Android Development] joam280:
no new mistake sorry

Enviado desde mi Nexus 9 mediante Tapatalk
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Drop me a recovery log after the error

Edit: did you reboot recovery after patch?
[Galaxy Note GT-N7000 Android Development] joam280:
If I restart and nothing else error, thanks and go to sleep

Enviado desde mi Nexus 9 mediante Tapatalk
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Haha… you have to restart ma… xD

Have a nice day ahead!
[Galaxy Note GT-N7000 Android Development] joam280:
If I rebooted several times without success

Enviado desde mi Nexus 9 mediante Tapatalk
[Galaxy Note GT-N7000 Android Development] joam280:
Today I will try to do everything from stock rom, thank you very much for your help

Enviado desde mi SM-G973F mediante Tapatalk
[Galaxy Note GT-N7000 Android Development] joam280:
I can't get the new rom installed, always same error [emoji24]

Enviado desde mi Nexus 9 mediante Tapatalk
[Galaxy Note GT-N7000 Android Development] Digger_m:
Re-read the instructions . Make sure you did the partition resisting. What errors did you have?
[Galaxy Note GT-N7000 Android Development] joam280:
these are the instructions i follow:

This part is very important, please pay attention.

Starting from pie, (at least) for galaxys2 family devices, we have migrated to emulated storage. Which means, we no longer use a physical internal sdcard partition, we use emulated internal sdcard instead which is part of /data. This move is to fix problems related to storage on pie.

To prepare your device for pie builds, you need to repartition your n7000 and flash a emulated storage compatible recovery.

1. Backup your files. Your data(s) will be wiped throughout the process!

2. Make sure you have at least a working TWRP 3.x IsoRec on your device. If no, proceed to bauner's LOS13.0 thread for installation steps.

3. Flash this recovery by rINanDO: TWRP-3.1.0-EMU-MIGRATION-M-20170318-noassert.zip (under directory n7000/misc/recovery)

4. You will notice that in TWRP, your phone will show as a i9100 MTP device on your computer. This is correct, we are using an emulated storage compatible recovery from i9100. We will patch it to make it identify as n7000 since n7000 has identical hardware with i9100.

5. Flash this TWRP patcher: lanchon-twrp-patcher-20160417-n7000.zip (under directory n7000/misc/recovery/patch)

6. Reboot recovery. Your TWRP is now identified as n7000. Flash this repartition script (push to /tmp or flash from your external sdcard): lanchon-repit-20170115-system=1.5G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip (under directory n7000/misc/partitioning)

and this is the error:

Enviado desde mi Nexus 9 mediante Tapatalk
[Galaxy Note GT-N7000 Android Development] lee.wp14:
I don't understand, it shows the device assert error.

Attach me a recovery log after the error.
[Galaxy Note GT-N7000 Android Development] tophechris:
I have installed the latest version.

SIM PIN works again, thanks!

I agree that WiFi connexion on 2,4GHz looks more stable than 5GHz.

But I still have WiFi card problem.

In my case, after half a day or a full day of use of my mobile, I am not able anymore to turn on WiFi . I turn on, it indicates "Activating WiFi..." and after 2-3 seconds it turns off the WiFi card.

Reboot or wipe dalvik + cache doesn't solve it. Only reflashing the Rom on the current install allow WiFi to work again. To me it looks like resetting a counter.

:(
[Galaxy Note GT-N7000 Android Development] Digger_m:
What is the error
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Can you grab a logcat for me so that I can look into this?

It is weird because this is exactly the situation I faced when porting DotOS to n7000. And the conflicting commit does not exists in LOS.

The commit is something about the power state of WiFi, which says do not assume Wifi module is ready while it is not ready.

But you say that after full day use.... really... no idea...

I admit that the wifi is really horrible for some reasons. But problem is I can't replicate it ._. My two n7000 has a murata wifi chip. The only problem I get is the 5GHz problem. I'm lacking ideas TT

I'm sorry guys, I will try my best to look into this. I know wifi is quite important for every phone.

I'm in the midst of rushing assignment deadlines so probably won't look into this anytime soon, but I'm happy to assist if you guys can provide any logs, so I can see what's going on behind.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Ah... I think there might be a little confusion here. Somehow the xdadevdb updated the thread using the old information, the recovery in OP that you see is TWRP-3.1.0-EMU-MIGRATION-M-20170318-noassert.zip. Whereas, you should be using i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img.

Try i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img, and patch using lanchon patcher, then reflash the rom.
[Galaxy Note GT-N7000 Android Development] joam280:
that may be my mistake. I could pass direct download link I get lost in so many folders. Thank you

Enviado desde mi Nexus 9 mediante Tapatalk

---------- Post added at 07:51 PM ---------- Previous post was at 07:37 PM ----------

ok i found the correct recovery and already update to the latest version [emoji106]

Enviado desde mi Nexus 9 mediante Tapatalk
[Galaxy Note GT-N7000 Android Development] joam280:
I already have my galaxy note updated ;-p

Enviado desde mi GT-N7000 mediante Tapatalk
[Galaxy Note GT-N7000 Android Development] :
Kernel bug triggers hot reboot on 'ip route get'

Hi,

I've installed the most recent build to my n7000 today. Everything worked fine until the app Syncthing-Fork was installed. It turned out to be a kernel bug, could you please build with the fix? https://github.com/LineageOS/androi...ommit/f44b4b19da1541fce8440ffa1e59cdb722cf10b

Thank you.

Ref.: https://github.com/Catfriend1/syncthing-android/issues/505
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Yes, thanks! I will come up a build with the fix included in a few days.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Thank you very much for the logs.

Pretty much the same as per my DotOS logs. I double checked the kernel and found no changes on the wifi driver at all. Only changes is the wpa_supplicant configuration.

I found two results on google and one on xda:

https://community.nxp.com/thread/525085 - this one has no progress yet

https://www.reddit.com/r/LineageOS/comments/etj302/s5_g900t_klte_wifi_timeout/ - this one says is hardware problem

https://xdaforums.com/showpost.php?p=62176769&postcount=164 - hardware problem too

While we for sure don't want a hardware problem.... Just in case, does it occur on other ROM?

*do not downgrade to earlier version! will cause bootloop, only do a clean flash if you want to.

Or, you can also try the following

1. enable adb root in developer options

2. from your computer, run: adb root

3. adb shell

4. htop

5. F3 > type wpa, make sure it selects wpa_supplicant, then F9 > SIGKILL. By then, wifi will be turned off.

6. Repeat until no wpa_supplicant is running (in my case is 3 times). CTRL+C exit. run the following:

nohup /vendor/bin/hw/wpa_supplicant -Dnl80211 -iwlan0 -puse_p2p_group_interface=1p2p_device=1 -I/vendor/etc/wifi/wpa_supplicant_overlay.conf -m/vendor/etc/wifi/p2p_supplicant_overlay.conf -c/vendor/etc/wifi/wpa_supplicant.conf > /data/wifitest &

Ok. Then try and use the wifi without restart and see how it goes. If there's difference then hopefully it is just configuration error.

Additional Steps if the above one didn't work well:

I made some changes to the wpa_supplicant.conf previously. You can revert the changes:

1. adb root

2. adb remount

3. adb shell

4. cd /vendor/etc/wifi

5. cp wpa_supplicant_overlay.conf wpa_supplicant_overlay.conf.bak

6. nano wpa_supplicant_overlay.conf

7. Edit as per the following: https://github.com/leewp14/android_...8ea1fcf4a/configs/wpa_supplicant_overlay.conf

8. CTRL+X > press Y > press ENTER.

9. Ok. then you repeat the above steps to kill and restart the wpa_supplicant.

EDIT: no... seems like the wpa_supplicant file not the case.

The configuration is never actually used by wpa_supplicant before, as you can see over here:

https://github.com/leewp14/android_...b8e#diff-6e8b7e94a5c3683ae429f852e829e497L343

In fact, after using it, The phone likes to switch between 5GHz and 2.4GHz.

I see some i9100 users says that wifi on Android 10 is stable than Android 9. In Android 10 there's a legacy wifi hidl 1.0 and i9100 is using it. It is derived from wifi hidl 1.3.
[Galaxy Note GT-N7000 Android Development] DoktorImEinsatz:
I just installed the newest release (without GAPPS). Everything works as expected. I get a GPS fix. And WiFi 5GHz seems to work also. I'm happy! :)
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Glad it worked well for you! Can you share some screenshot of the GPS status? (just to have a look as it's been a long time I didn't get GPS fix on n7000, I missed the bars and numbers xD)
[Galaxy Note GT-N7000 Android Development] DoktorImEinsatz:
Here comes the bars and numbers :o

The first GPS fix took 256 seconds. It took several minutes for the Glonass satellite show up.

(The app I used is SatStat)
[Galaxy Note GT-N7000 Android Development] lee.wp14:
That's really nice, thanks!

I think even if the GPS works, the performance is not as per what we can achieve on older Android?
[Galaxy Note GT-N7000 Android Development] DoktorImEinsatz:
I can't remember the performance of the original Android. It's so long ago I used it. And I'm so used to my new device (OnePlus 6) which is very fast and very accurate.

It would be very nice if we could speed it up. But even in the current form it's sufficient for me.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Exactly... the GPS performance of phone nowadays are exceptional to me. Can get tons of signals instantly even in indoors. Fire up any GPS apps and the phone gets a fix in seconds.