yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Follow these:

2. Reboot into recovery. Flash emulated storage capable TWRP IsoRec (flash as Image to Recovery): i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img

3. Reboot recovery. Flash i9100-to-n7000 TWRP conversion: lanchon-twrp-patcher-20160417-n7000.zip

If you can make it until TWRP isorec then just follow the installation guide in first post from beginning. It should be fine then. The base requirement is you need to have a TWRP Isorec.

Error 7 is most probably due to device identification error. And as long as your device bootup shows GT-N7000 then everything should be compatible.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Build 20200809

Greetings folks. Here is a new build. Nothing special other than a minor update.

CHANGELOG

- general: upstream updates, ASB 2020-08-05

- frameworks/base: ColorFade fix for exynos mali

- device-related: merge lineage-17.1 changes from @rINanDO

This update mainly is to address the ColorFade issue that exists and crash your system when you set to non-lowram configuration, and also bring over the gralloc related fixes and other changes from lineage-17.1 branch that looks kinda interesting to me.

This is my first build after fomatting my laptop before school reopens, so hopefully it doesn't affect anything. I have tested with a dirtyflash.
[Galaxy Note GT-N7000 Android Development] :
Thanks for the information but TWRP Isorec was not causing the problem but the problem was coming from a partition error also I didn't properly understand the third reparation script and just repartitioned in Odin as with the first and second script it failed with error 1 both when flashing with USB otg or a SD card.

To fix this I just copied the file to the emulated storage and flashed it and then the ROM installed successfully.

I'm writing it on that phone.

Thanks,

Regards.
[Galaxy Note GT-N7000 Android Development] goodwu:
Thanks for the update.

Magisk in boot_magisk.img doesn't work in this version. It's OK in the last version.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Ah... forget to double check magisk boot image. Will test now and get back to you.

EDIT: yes indeed it's not working. I will check on it and recompile the kernel again. Will notify when fixed.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Hi folks, it's my mistake... mistake in procedure when creating the magisk patched bootimage. I did it when I just wakeup so is kinda blur during that time. Sorry folks xD

I also doubt how the magisk installation is successful although the steps are incorrect... nevertheless I have updated the boot_magisk.img

Magisk should work now. Sorry for the inconvenience! Thanks to [MENTION=9858965]goodwu[/MENTION] for pointing out.
[Galaxy Note GT-N7000 Android Development] :
Thanks for the update,

Can you make the always on display a bit darker and changing it's position after a certain period because I forgot to unplug my phone because of a personal issue and it actually burned the battery percentage on the screen very severely. Can you fix it in the next update.

Regards
[Galaxy Note GT-N7000 Android Development] lee.wp14:
The AOD has been configured with minimum brightness (you can notice that on minimum brightness there's no brightness change when transitioning to AOD). Currently that's the minimum achievable brightness on our device.

And actually burn in protection has been enabled also (if you check on it, the battery percentage and clock is not completely at the center of screen, there's a bit of shifting). So.... it's weird if it still burns. Actually burn-in protection is enabled system wide, like the status bar also.

For everything of the AOD is stock android behavior (except for the fact that I explicitly enabled the AOD feature). I'm not sure if we can further adjust it... need to check whether the framework overlay supports adjusting the shifting size. Might be better if you temporarily turn off AOD and turn on the Clock screensaver while plugged in, if you don't really need AOD to see notifications but just to check the clock while charging. I will check on the AOD on next update.
[Galaxy Note GT-N7000 Android Development] :
Thanks for reply. As I think the burn in might have caused by the degraded of the display in the last 8 years I owned the phone and my whole display is burned up like crazy because of a eBook. Regardless, I will just turn off AOD.

Sorry if I wasted your time.

---------- Post added at 12:30 PM ---------- Previous post was at 11:55 AM ----------

Hey Lee I have found a way to even lower the brightness. If you go to calibrate on screen colors option and then reduce RGB values to zero percentage for all colors then it will be perfect for an Always On display I hope it helps.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Nah... don't say yourself like that! I will reply to questions when I'm able to. Just that maybe I don't have much time.

That's so brilliant of you xD! I recalled of doing that when using the phone in bed during midnight last time haha..

As our device doesn't really supports AOD (there's no support on the kernel level) so.... actually hmmm maybe we can do something thru samsungdoze which I have abandoned in my builds in favor of stock AOD... not sure... need to experiment.
[Galaxy Note GT-N7000 Android Development] :
Sorry.
[Galaxy Note GT-N7000 Android Development] :
Hey [MENTION=4114553]lee.[/MENTION]wp14

Greetings.

Whenever I flash boot_magisk.img to the boot partition my phone always gets soft bricked. Can you help me with that because I want magisk support for my banking apps.

Please reply
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Well you don't have to say sorry anyway :)

Whenever you flash it softbrick.... I never met this before. Can you turn on adb first and grant adb access, afterwards only flash the boot_magisk and check adb logcat for logs... that's strange.
[Galaxy Note GT-N7000 Android Development] :
I say you sorry because your classes are going on and I can disturbed you in class that's why I always say you sorry.

I just flashed su removal and now using my phone without root access.

And all of my banking apps are working fine.

Thanks,

Sorry if I wasted your precious time.

And I hope your studies are going well
[Galaxy Note GT-N7000 Android Development] :
Hey lee.wp14

Greetings,

I have a question about a file system

Can i change the file system of /cache and/data to f2fs?
[Galaxy Note GT-N7000 Android Development] trinireddman:
There's a problem with rom lineage-16.0-20200809-UNOFFICIAL-n7000, no one can hear you on calls via mic or bluetooth headset but you can on lineage-16.0-20200614-UNOFFICIAL-n7000. Everything else is better on lineage-16.0-20200809-UNOFFICIAL-n7000.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Just reboot to twrp and change the filesystem under wipe menu. There's a f2fs option.

This is not good... i will test it out real soon.... I couldn't think of any changes affecting this.

EDIT: so it is totally not ok at all. the dialer enables speaker on call. Something is broken.

Ahh... forgive me for this problem.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
i have identified a fix for the in call handling issue of build 20200809. Kindly stay on build 20200614 should you depends on phone call functionality. A new build with the fix will be up in one week time (hopefully!)

For those who want to fix manually, refer to this (do this with computer, or you can manually edit the file if you know how to do it on phone with root):

1. For Magisk: enter adb shell -> su -> mount -o remount,rw /system

For non-Magisk (make sure enable adb root in developer options, you don't have to root): enter adb root -> adb remount -> adb shell

2. cd /vendor/etc/

3. cp audio_policy_configuration.xml audio_policy_configuration.xml.bak

4. nano audio_policy_configuration.xml

5. locate line 48 (use keyboard shortcut CTRL+SHIFT+HYPHEN)

6. Add this line below line 48: https://github.com/hikuii/android_d...f0cb#diff-533002e729ce3b0235a538482a33c920L49

<item>Earpiece</item>

Indentation is unnecessary, as long as the code is correct.

7. Save the file by pressing CTRL+X, then Y, then ENTER.

8. reboot.

9. Test your in call audio. It everything should work now.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Hi folks.

Build 20200821 has been uploaded as a hotfix update for the in-call audio handling issue. It is untested as I don't have time to test yet. Do test and let me know if it works. (Update: tested with dirty flash)

Apart from that, build 20200821 is identical to 20200809.

Thanks and have a nice day!
[Galaxy Note GT-N7000 Android Development] Gold Mix:
Awesome!

Great job dude as usual, thank you very much. I performed a dirty flash updated from 20200614, and it was very smooth and quick probably just 5 minutes, and everything seems fine so far :)

Actually, I didn’t know about these updates as I’m not watching this thread. I was wondering why the Telegram group has been silent since April. So I decided to check the thread, and was pleased to see things are still active :good:

Many thanks for sharing your hard work, and all the best in your studies :highfive:
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Sorry for that! It was quite long time ago since I last posted on the Telegram group. I think that it would be fine if everything is consolidated at just one place.

Yes definitely :D I find no reason to discontinue, it's fun having development progress on such an interesting handset.

You are welcomed, I'm glad it is useful to you all! And thanks! I gonna retain my high scores this semester :cool:

I was getting random reboots lately, I hope you guys didn't suffer from this. Mine is a Magisk + microG setup.
[Galaxy Note GT-N7000 Android Development] :
Will this rom will install on the Chinese galaxy note gt-19220?

---------- Post added at 10:41 AM ---------- Previous post was at 10:28 AM ----------

The random reboot may be causing by the eMMC module giving up the ghost I had a similar issue on a Lg nexus 4 which randomly rebooted at any given point. I have given a link of an app called got brickbug can you please download it from the link in the end of this post and tell what is you fwrew and chip date is maybe this can be cause of an issue. And i suggest you to not flash or format anything.

Gotbrickbug apk :- https://xdaforums.com/attachment.php?attachmentid=1303502&d=1346829980

Sorry if i wasted your precious time.

regards
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Whether will it install or not I'm not sure. Probably you need to remove the assert check in updater-script.

All galaxy notes that I have has this brickbug. But we are on a safe kernel, the bug is being fixed in smdk4412 kernel since cm13 thus there's nothing to worry about the brickbug anymore. I always perform dirty flashes and system modifications during testing, mixing stuffs up for testing. Thus it might be an issue of me if you guys didn't have this problem.

Or maybe the memory has started to wear out as I'm using the UMS partition as swap space.
[Galaxy Note GT-N7000 Android Development] :
The rom did install but ended up in a bootloop on a i9220 after removing the assert check.
[Galaxy Note GT-N7000 Android Development] Boganite:
Sorry if this question doesn't belong here.

I have found a GT-N7000B on Facebook marketplace for $50 AUD but they said it cannot make calls. My question is, do you think it is worth purchasing and would it be possible to fix the "No calls" problem with this rom?

...I know very little about this stuff.
[Galaxy Note GT-N7000 Android Development] Gold Mix:
In my opinion, the short answer is NO!

This a 2011 device with very low hardware specs (45nm chipset, 1GB RAM 16/32GB internal storage). It will really struggle to run current apps. Besides it has the no call issue. If this is due to hardware defect, then the rom won't fix it.

The only reason I would buy this phone in 2020, if I wanted to use it as a learning tool and experimentation.
[Galaxy Note GT-N7000 Android Development] :
Can you please dial *#06# in your phone and say your result if you get a number don't post it here.

Also $50 is too much for a gt-n7000B try to get it below $30.

If you can boot into stock recovery do you see a text like "error:failed to mount efs(invalid argument).
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Would you like to assist me in troubleshooting? As per wikipedia i9220 should be same but I'm not sure... I never face i9220 before. But china peoples are using roms from xda so I guess... well should be the same then. Unless they got international ones...

How is the bootloop, is it a hardbrick or softbrick?
[Galaxy Note GT-N7000 Android Development] :
It was a softbrick it recovered while reflashing in Odin. Also I got slimsaber ROM running but all of the newer ROMs seem to just bootloop.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Ah... sorry! I mean, it loops at the logo or bootanimation?

Pardon me... I am a bit blur xD
[Galaxy Note GT-N7000 Android Development] :
It got stuck on the lineage logo and constantly rebooted after every 2-3 minutes.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Hmm ok. If you want you may help me to get a logcat to check on it.
[Galaxy Note GT-N7000 Android Development] :
Can you also help me with the battery drain issue the battery drain's super fast in this ROM I can't get more than 2 hours of screen on time while on the stock ROM the battery is much better can you help me with this since this is my only phone and I can't use it such battery drain.

Regards.

---------- Post added at 07:03 AM ---------- Previous post was at 07:01 AM ----------

I currently don't have that phone it was my cousin's phone and she is not home. And also now she doesn't let me mess up with her phone.

So, sorry
[Galaxy Note GT-N7000 Android Development] lee.wp14:
I think you can try switch the cpu govenor to ondemand, that's more battery saving but it is not so responsive I would say. I already remove powerhal so you can just go ahead and switch the cpu governor.

Ah... haha xD Get your cousin a good rom then, something like nougat or lollipop would be better for ordinary users. like for my mom and sis, the most I have them use is nougat only.

EDIT: but how long SOT are you getting currently? With heavy usage mine is around 1.25 hours. I'm using interactive and I have tons of apps that now my n7000 is lag as hell most of the time. Wifi powered on whole day with 3G voice only.
[Galaxy Note GT-N7000 Android Development] :
I side loaded the magisk IMG file to the boot partition with ADB sideload on twrp and now magisk works.

---------- Post added at 07:22 AM ---------- Previous post was at 07:21 AM ----------

After a lot of work I flashed slimkat 4.4.4 on her phone at least it is usable now.

---------- Post added at 07:33 AM ---------- Previous post was at 07:22 AM ----------

I currently get around 2hrs of screen of time of continuous 720p YouTube playback with a new battery.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
I think that's the best we could squeeze out of our n7000 with Android 9. 2hrs SOT is what we should expect at least I would say.

There's too much load on the cpu unlike on stock rom since this is android 9, so definitely there's a price.
[Galaxy Note GT-N7000 Android Development] :
Also is there a way to reduce overheating because after just 20-30 mins my note gets hot like an oven and thermal throttle like crazy making it almost unusable.

Edit:- Sorry if I am wasting your time today is holiday of my online class and I have nothing to do.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
I already raised the thermal throttling threshold. If it is like previous, the throttle is too much. You can check the commit below and monitor the temperature of cpu.. the throttle kicks in too soon with old values, the kernel throttled the CPU before you even enter the android system, it's too soon.

Because it takes time to test so I just copied the values from gt-i9300 during last time which is first throttle to 1GHz at 80deg celcius.

https://github.com/hikuii/android_k...mmit/06468c05ff54bcfef26bae5fdaa3fb7ee404d9c2

I actually did test a bit but couldn't find a good value. Like when I put on 76 and off at 71, the throttle kicks in and out too frequent under load, like throttle to low frequency for 3 minutes then back to normal but then a few seconds later back to low frequency for 3 minutes and so on, so it just on and off and on and off repeatedly, very inconsistent although the load is the same. So i just went ahead to take the values from s3 which is higher and also the throttling is pretty consistent as tested.

But yeah, definitely will work on this next time when I'm back to development. I udnerstand the heat was like boiling :mad:
[Galaxy Note GT-N7000 Android Development] :
Thanks for this informative reply and changing the CPU governor to ondemand and underclocking the CPU to 1.2 GHz the phone does run somewhat cooler and doesn't become unusable just is a bit sluggish and I will soon try to apply thermal paste to the cpu which will help I tried it on my nexus 6p and it ran cooler maybe it will work on this too.

Thanks for keeping this decade old phone alive with Android 9.

Regards
[Galaxy Note GT-N7000 Android Development] lee.wp14:
You are welcomed. Yes, applying thermal paste is a good way.

Ah. PSA: Do not use thermal pads!!!!! You will break your motherboard because of the heat and the pressure of the thermal pads exerted on the chip. I break my note 1 last time because of using thermal pads. It didn't give any problems but after a period of time I removed all the pads and replace with thermal paste. After a few days the phone is dead.
[Galaxy Note GT-N7000 Android Development] :
Where did you apply the thermal pads you need to apply the paste/pad on the shield which has a square imprint on it and not on the chip near the power button that's the emmc and the display is exposed in that area.

Edit:- What is the I/O scheduler option it is currently on noop should I change it.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
I apply on all the big chips on the back, emmc, cpu, power and an unknown chip on top of the power chip. And also open up the metal shield and apply inside there too. But anyway using thermal pad is too thick, long term high heat usage will damage the bga balling so no one should consider thermal pads. That should be the cause of why my n7000 died after changing to thermal paste because of the difference in height exerted.

I did use electronic tape to cover exposed parts of the lcd. Highly recommended unless you want the paste to mess up with the tiny transistors and the small socket :p

About the i/o scheduler: why is it noop? shouldn't it should be zen? I have tested extensively and zen should be the best.
[Galaxy Note GT-N7000 Android Development] :
You only needed to apply on the cpu as this the hottest and the unknown chip was the ram you dont need to apply it there as there is a factory installed thermal pad and try to apply the perfect amount on the middle that will evenly spread outside the shield on the cpu as you will probably dont want thermal paste leaking inside other components and the emmc doesnt need thermal paste as is doesnt gets too hot.

Edit:- the unknown chip are you talking about does have a cage looking shield if it has one it is the ram.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Well the ram is a single package with the cpu. The chip on top of the power chip is definitely not a ram chip. The ram is stacked on top of the CPU. So the CPU is actually RAM+CPU.

https://electronics360.globalspec.c...-galaxy-note-gt-n7000-mobile-handset-teardown

You can see that it says PoP (Package on Package).

EDIT: so did some googling and the unknown chip is baseband chip.
[Galaxy Note GT-N7000 Android Development] :
Sorry my bad the chip with a cage looking shield got hot while usage and i just assumed it was the ram since i dont knew the ram was package on package.
[Galaxy Note GT-N7000 Android Development] tvfilo:
Reading mode seems not to work in 20200821 rom

Hello lee.wp14,

first thank you for the fantastic work.

Because i found an issue in the 20200821 rom i would like to ask.. is it possible to repair this.

It seems that the "Reading mode" (Grayscaled mode) doesn't work.

I tried to enable it over the system panel and also over settings-> live display with no success.

Thank you in advance.
[Galaxy Note GT-N7000 Android Development] Notlimcito:
I use version 20200417 and the grayscale does not work either, I have not yet tried new versions due to lack of time, however I want to thank once again the work of everyone in special that of lee.wp14 for maintaining this magnificent telephone with life.

P.S. With version 20200417 it has not had problems and with a new battery I have spent 3 hours of use with the screen and wifi on
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Currently on kernel side our board does not support the grayscale mode so it is not working.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Hi folks. Here is a minor kernel update:

- lower thermal threshold: 64, 59

- new cpu governor lionheart, default governor

https://github.com/hikuii/android_k...mmit/1ceb0497228aada6088ccf2edbce65edeb5d1b50

Under moderate usage, temperature should be around 60 celcius. Throttle kicks in at 65 which limits cpu to 1000MHz, and return to normal after temperature is less than 59 when load decreased (seems like a kernel bug?).

Please let me know if there's anything of concern.

If battery life is your priority, you might want to avoid from using this kernel as lionheart cpu governor tends to reside on high freqs, or manually adjust the cpu governor after flashing. Or maybe you can try it out also!

Thanks and have a nice day!
[Galaxy Note GT-N7000 Android Development] dudeistpriest:
This (not so) little phone is a miracle. I bought it back when it was released, I still have it, it still works like a charm, and with this ROM it's actually quite fast too. Thank you (and the other developers who work on this phone) for keeping this phone alive so many years after its release. It's been my go-to backup phone for years, it's practically built to last forever!
[Galaxy Note GT-N7000 Android Development] Wattsensi:
My N7000 was stolen when I was 14...I still miss it, it had CyanogenMod 10.1 and the AMOLED display and back texture were lovely, oh, and the S-Pen too. Curse the lowlifes who did that! This device showed me the pleasure of having a well supported, powerful (back then) and unique device after experiencing the hell of having an obscure Huawei Y210 stuck forever on Gingerbread, back then Huawei = absolute crap. If I remember correctly it had a single boot image for both kernel and recovery and it required repartitioning for newer ROMs...if we only had something like Project Treble back then!

btw, how does this millenia old device perform with newer ROMs? Is it still usable as a low end browsing machine? I find it impressive that this 2011 phone has Lollipop ROMs let alone Pie.
[Galaxy Note GT-N7000 Android Development] :
It is sad to hear that and which color you have I have the white one which stains extremely easily and isn't grippy at all.

And this ROM makes the device much better in performance it can also support most of the latest apps in this ROM I was even able to play PUBG mobile lite with lowest graphics possibe and it was totally playable at a frame rate of around 3-27 fps.
[Galaxy Note GT-N7000 Android Development] Wattsensi:
I had the black one with rugged back, it was so good
[Galaxy Note GT-N7000 Android Development] waro470:
Hi, Lee, hi everyone!

I'd like to try this fantastic ROM, but the URL for the repit file has expired. Now, I've found something similar on Google, but it's for the Galaxy SII (i9100) and I don't know whether or not that one'll work.

Could I have a working link towards for that repit file? Thanks in advance.

[UPDATE] Link got fixed! Thank you, Lee! You rock!