yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Android Development] wiijordends:
I just flashed the newly Android 12 LineageOS 19 build this morning.

It's currently a bit early to share my experience yet since I need some more time, but I already like to share my first impression.

First of all, I was surprised that I could just do a dirty flash over your current 18.1 dec build without any problems.

I did not perform a clean flash because I couldn't backup my Session messages, normally I always perform clean flashes.

I used TWPR 3.5.2 custom recovery to flash this ROM and only wiped Cache and Dalvik Cache/ART partition.

Everything went smooth. It didn't take too long for the first boot either.

Right after the first boot, just when it was booted, the phone rebooted.

After this reboot, I didn't encounter any random reboots yet.

Everything seems working smooth and snappy at the moment.

I can confirm that Magisk 23 is still working on this ROM. You just need to re-flash it after the first boot.

The only annoying thing I discovered is a blinking LED issue and the battery that last less longer, but that's maybe linked to the blinking LED issue.

Something I immediately noticed is that my notification LED is actually red now while charging and green when it hits 100%.

In previous 18.1 build, the LED always got a weird yellowish colour while charging.

Another thing that caught my eye was "Google Play System update" in settings.

I don't understands why it's there since it's supposed to be a degoogled ROM.

Google Play System updates is a part of the Google Play Services ecosystem.

I didn't install any GAPPS and this ROM didn't came with GAPPS pre installed.

Spoiler content hidden.

Spoiler content hidden.

Besides the blinking LED issue, I had a very good first impression.

I really don't mind that some gimmick features are not working.

I only have this ROM for a few hours, so please keep in mind that I need more time for extensive and more in-depth testing.

Maybe there are some critical problems that I still need to discover.

I just wanted to give a quick update.

@html6405

If there are some specific things you like to try or things I need to keep an eye on, please let me know.
[Galaxy Note II Android Development] html6405:
Thx for your report,

but it is really recommended to not dirty flash this ROM over an older build.

I don't know exactly what the LED binking issue is, maybe this happens because of your dirty flash, I'm not facing this on my other devices.

It should be yellow between this two stages, but I can't test it by myself,

maybe you could test a clean installation?

I think this point was already in previous android versions present, I guess this come's from aosp's sources and you can ignore it.

This also happens sometimes at the S3, I'm not sure yet why, but I will find out the reason sooner or later.
[Galaxy Note II Android Development] porcino:
It does work! I couldn't resist trying the future LOS19. The report has been moved into the new thread dedicated to this ROM...
[Galaxy Note II Android Development] html6405:
Update 06.01.2022:

Partly fixed USB mode selection, just reconnect the device to make it active or wait long enough

Fixed shutdown / reboot behaviour with installed magisk

Set swappiness to 60

Enabled software navbar and full gesture navigation as default (to disable you still can use my toggle_navbar script)

GPS is at the same state as it is on LOS19, maybe someone could confirm the functionality
[Galaxy Note II Android Development] html6405:
Update 07.01.2022:

new attempt to fix SIM PIN unlock issue, the problem is I can't test it by my own yet, maybe some has a spare sim card just for testing? Would be nice!
[Galaxy Note II Android Development] porcino:
GPS stopped working... It used to work in the earlier version I tested.

I don't have a SIM of this size to test, sorry.

This ROM in general seems to be a bit unstable. It rebooted at random while I was playing with settings, in particular when checking the camera for trackers and subsequently removing all its permissions and disabling it. I didn't have a single random reboot with your LOS19.0 ROM...
[Galaxy Note II Android Development] html6405:
Hmm this is weird, because I've created the GPS fix first for this ROM and overtook it 1 to 1 for LOS 19 where it seems to work.

It's a mess that I can't test it by my own, but there was also not a single donation so far, so I wont buy this device.

Would be great if you could do a last_kmsg when this happens, otherwise it's hard to say what's wrong.
[Galaxy Note II Android Development] porcino:
Fair point, although there was one ))... How much do you need to buy the hardware in your country?
[Galaxy Note II Android Development] html6405:
If it was from you and over the link in my signature, then I can't assign it to this project.

The link in the start post is an individual link so that I know for what.

But I guess you mean a donation from yesterday?

Then thanks for this and I will count it to the note 2 project :).

What I can find the working devices cost about 50€-70€.
[Galaxy Note II Android Development] porcino:
Here it goes, with gratitude!
[Galaxy Note II Android Development] html6405:
Thanks, maybe someone else will donate, then I will buy a device to test it for myself.

At the moment I'm testing with a t0lte, what doesn't make's it easy.
[Galaxy Note II Android Development] porcino:
I've sent you 70 to buy the device if you find one...
[Galaxy Note II Android Development] html6405:
Wow, I'm speechless, thousand thanks, I will organize a device this week and will be finally able to test GPS, RIL etc :).
[Galaxy Note II Android Development] multiwirth:
Hi everyone!

I just recently discovered this rom and so far i'm really impressed!

However i'm missing all the boeffla tweaks which could be accessed by tweaks.rc in /vendor/etc/init/

So i'd like to get my own build running, however on the github page i couldn't find a matching device_n7100 with lineage-18.1 branch.

So i wonder how did you built this rom?

I'd like to (try) reimplement the boeffla stuff into the kernel, aswell as getting rid of the on screen navigation gestures as i personally don't use them on a device with physical buttons.

And searching for the setprop command every time i need it, isn't that comfortable ;)

Unfortunately, i'm still pretty much a noob when it comes to development and stuff.

I was using a personal build of lineage 16.0 using chrono's i9300 build manifest (that covered all other devices aswell) and failed hard trying to bringup 17.1 or 18.1 even so this thread really is amazing to see ;)
[Galaxy Note II Android Development] multiwirth:
Good evening,

I had some time testing everything.

So far, i experienced random reboots from time to time (mostly when screen is off)

last_kmsg is invalid, shows only initial bootup but no crash messages. (may try again grabbing directly from twrp)

RIL works (data & calls)

Audio works, however i was unable to get Viper4Android up and running (works on i9300 18.1 by rINanDO) and missing boeffla sound (optional ofc but nice2have)

Camera takes pictures, video capture is crashing the media server (can´t connect to camera).

S Pen works, however the small cursor (circle) isn´t showing up onscreen.

NFC works

Bluetooth is enabled, shows avaiable devices. No further testing yet

Flashlight works

Auto brightness works

GPS, compass is broken

Orientation sensor doesn´t respond (auto rotation works though)

Magnetic sensor doesn´t respond.

All other sensors are fine

Built in recorder crashes when trying to record audio, maybe video capture has the same issue.

MTP doesn´t work, starts charging and asks for usb mode, by selecting file transfer everything greyed out and the usb notification never showed up again.

All animations are disabled in dev settings by default. (for a reason?)
[Galaxy Note II Android Development] html6405:
GitHub - html6405/android_device_samsung_n7100

Contribute to html6405/android_device_samsung_n7100 development by creating an account on GitHub.

github.com

Everything except boeffla audio is included in the kernel, I've reverted these things because of a real low audio volume and other issues.

Hmm if it's empty, then it may not be a kernel crash.

Because it's disabled by default in the settings, just enable it ;).

I will re-fix the microphone recording today, this fix got lost with my last sycn...

Yep:

a6010: overlay: disable all animations by default · html6405/android_device_samsung_smdk4412-common@a6e3fa7

Yeah, animations is expensive for our legacy device. Disable it by default to make phone significantly faster.

github.com

These things are kown, but thanks for your report.

I wasn't able to buy a device so far, so it's not easy to fix GPS, but it should work already on LOS 19.0.
[Galaxy Note II Android Development] html6405:
Update 19.01.2021:

re-fixed microphone recording
[Galaxy Note II Android Development] i5510:
Have a look here ;)

https://www.buyzoxs.de/kaufen/note-...-n7100-16gb-braun_B00BI2VL5M.html?condition=3
[Galaxy Note II Android Development] porcino:
There are a few n7100 on ebay.de. The prices are around 40 eur. There are cheaper options, but my German is non-existent to understand the nuance.

GPS somewhat works in LOS-18 (it found a satellite, but no fix), I reported this before. It was later when I tried LOS-19, I found that GPS works better with the old API set in the developer options and in GPStest app. So, try fiddling with the options and also try it outside.
[Galaxy Note II Android Development] html6405:
I'm searching in austria and try again to buy one, I will keep you updated.
[Galaxy Note II Android Development] porcino:
Sorry, Austria of course!
[Galaxy Note II Android Development] hongfuhainiu:
It's great!!!
[Galaxy Note II Android Development] html6405:
Update 26.01.2022:

Fixed compass and orientation sensor
[Galaxy Note II Android Development] html6405:
Update 02.02.2022:

Refixed GPS

Disabled always on display by default
[Galaxy Note II Android Development] AlexALXua:
So i switched to this ROM now from 12 android and here what i can tell so far:

- GPS & compass works, but after ~15 mins did lost satellites and only able to fix with reboot. Not sure yet if this happens constantly so will continue tests.

- camera for QR scan in Firefox exact same as in 12 android - not working and showing only first picture. Tried both - OPENGAPPS and BITGAPPS (with full wipe/reflash), nothing changed. So don't think its gapps related.

- still had various random crashes after installed some of my regular apps, will continue to monitor this.

- there is no cursor of spen, but itself hover works (i think this was reported already)

- tested screen cast using miracast, worked successfully

- there is no NFC option in "connected device" settings, but can turn on/off in main menu, while i'm not yet sure if it works at all - gpay says "touch payment not available", i do PASS all safetynet tests + have all possible GPAY fixes and even certified device in google play market, seems like it just cannot detect NFC module. I'll try to find a way to test NFC later - using some NFC marker so will know if it actually works in this ROM or it just do nothing, but i'm 100% sure it did worked in past on stock 4.4 android.

------

But in general - after 12 ROM, this 11 one is faster and more smooth visually. Thanks again for your work!

-----

EDIT: can't choose wallpaper using settings - it just reloads after selecting proper file in "my files", can setup those using gallery but then its same for lock & home screen. want to setup different ones. This thing worked just fine in 12 rom
[Galaxy Note II Android Development] html6405:
Since I can test GPS by my own, I've recognized the same behaviour.

Did you enable the s-pen hovering in the settings?

I've only tested to read and write nfc tags, which worked fine. I'm not sure what gpay exactly needs.

Someone reported a similar issue in an other thread (other device), this may be an issue which will be fixed with the next sync.
[Galaxy Note II Android Development] multiwirth:
GPay needs special functionality, called NFC-HCE or host based card emulation which in fact doesn´t work on most devices/ROMs as far as i know.

And gpay also requires SafetyNet to pass and SELinux enforcing aswell.

So it probably only works in stock, dunno if this is a requirement for official lineage but i think even officially supported devices may not support NFC-HCE while running lineage.

Btw. i couldn´t find any S-Pen related settings.

Where is it supposed to be located at?
[Galaxy Note II Android Development] html6405:
Thanks, never spend any time for gpay, because I'm not that guy who would use it.

SafetyNet would be the smallest problem in this case.

Did it work with previous LineageOS versions???

The S-Pen settings are located in:

Settings->System->Gestures->Touchscreen gestures
[Galaxy Note II Android Development] AlexALXua:
SafetyNet test and SELinux enforcing is not a problem at all, since i already can pass it. So yeah its something else...

Have no idea, because i did switch from stock 4.4.2 to this roms (12 and 11 now) after got most of apps not working because of outdated version.

Anyway, if gpay will never work anymore on this device - what to do) Only way is to buy new phone, while I don't like modern phones with super elongated screens + cutouts for cameras what looks awfully, but thats another story...

Hmm.. don't see option for enable cursor here. But thanks)
[Galaxy Note II Android Development] html6405:
Because this setting is in the language part.

Settings->Sytem->Languages and Input->Show icon when using stylus
[Galaxy Note II Android Development] AlexALXua:
Oh, works! Big thanks! But location of this settings is way deep to find it myself :D
[Galaxy Note II Android Development] html6405:
Update 08.02.2022:

Fixed GPS completely, 3D fix passes.
[Galaxy Note II Android Development] AlexALXua:
So after week os usage this rom i'm really still have like every 5-10 mins system crash when there is internet connected. Mostly its unusable for me when i'm turn on internet, as offline navigator or just cell phone it works fine. But those might happens because of app crash issue - crash reported crashing system for me (wrote on telegram already).

So here is list of issues what i have so far:

- If any app crashes, then creating crash report (this happens automatically) - whole system crashes.

- If try create/send crash report using dev options in system - also whole system crashes.

- There is no proper kernel panic log during this crashes, only can have adb logcat.

- There is no LED indicator when charging at all, did worked in 12 rom.

- Newer webview have issues with hardware acceleration or rendering (not sure), and 3d maps in browser are broken (wind speed, weawow etc - all have yellow background). But works fine if downgrade to 91.0.4472.114 manually.

- Flashlight turns off after few secs with keeping "flashlight" enabled in menu.

- Acrobat Reader crashes when select file from filesystem, looks same bug as wallpaper issue?

- Sometimes i have crash what leads black screen with blinking hardware led buttons, and nothing happens, needed to do full reboot.

Other issues what is exists same as in 12 rom, just writing list so maybe those will be fixed eventually (those was already reported).

- Firefox qr scanner not working properly with camera - only first frame shows, same behaviour happens in few other apps (banking etc), but in other it works fine.

- Maps.me if use sdcard as storage - maps are not working, guess there is issue with sdcard permissions or something.

- Wallpaper settings - crashing when choosing file from filesystem.

- Google Pay is not working - says no support for contactless paymens (missing NFC detection?), while pass safetynet tests and google play certificated.

-----

So conclusion so far - can't use phone anymore as main device in internet, since having every 5 mins crash is absolutely unusable. But if use as offline navigator - it works pretty good now with latest GPS fix, so good work on this one.

Anyway my 10 year old phone was my best friend during this years but right now can't use it anymore properly... :( And i can't roll back to stock 4.4.2 android since all apps already way outdated... Too sad... Anyway i'm not blame anyone, well, except maybe samsung since they never released android 5 for this phone)

-----

And just putting adb crash log from "create/send" crash action using dev options.
[Galaxy Note II Android Development] html6405:
Did you try a clean installation? Also did you try it without gapps, maybe with microG instead?

I was using this ROM the last week and was very satisfied.

I've also faced this problem sometimes, I was not able to debug it completely so far...

I'm really sorry for your troubles, but I've checked your log and as it seems, the sensorservice crashes:

02-19 12:44:37.261 11625 11759 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 11759 (SensorService), pid 11625 (system_server)

Do all your sensors work fine?

Something strange is happening there.
[Galaxy Note II Android Development] multiwirth:
Sensors are all working for me, however i also experienced random reboots and crashes (black screen) but wasn't able to get valid ksmg yet aswell as logcats as it randomly happens.

I had 4 crashes behind each other, then it ran fine for a hours until i decided to power it of as i'm not using it atm.

It's a little bit hit and miss :)
[Galaxy Note II Android Development] html6405:
I will use this device the next week and try to improve it a little bit.
[Galaxy Note II Android Development] Zero_Shadow:
Is the FM Radio functionality working by chance? Can assist with testing if needed.
[Galaxy Note II Android Development] multiwirth:
I think no, i didn't even know smdk4412 devices had built in radio until someone mentioned it a year ago.

So for me FM radio was never avaiable for i9300 or n7100, not even official CM and lineage builds (way back when)

Someone said he got fm working with a 3rd party app but dunno the app name.
[Galaxy Note II Android Development] Zero_Shadow:
I have it on my n7100 model I believe it's the international version. I currently have the old XenonHD 7.1.2 rom on it that has the FM functionality. For the FM radio I have an apk thats from Samsung as the interface.

I knew it might be a long shot but thought I'd ask also willing to provide any info if it would be helpful.

Edit: Here's the apk that I was mentioning from Samsung.
[Galaxy Note II Android Development] multiwirth:
Was XenonHD built from AOSP or was it an stock-based, themed ROM?

Back then there were a lot of modified, debloated and themed (hacked) ROMs based on stock touchwiz, which in fact ran stock kernel, stock firmware and due to this also had all stock features avaiable.

Best example is "JellyBlast" for my old Galaxy Ace S5830i, it was stock based android 2.3.7 but was modified to look like AOSP jelly bean aswell as spoofing android version to be 4.1 instead of 2.3.6.
[Galaxy Note II Android Development] Zero_Shadow:
https://xdaforums.com/t/official-eol-7-1-2_r29-n7100-xenonhd-7-1-3-nov-2017.3579771/

From the looks of it it was based off of LineageOs.
[Galaxy Note II Android Development] html6405:
Update 20.02.2022:

Fixed charging light
[Galaxy Note II Android Development] AlexALXua:
Just tested using https://xdaforums.com/t/spirit1-spirit2-real-fm-radio-general-thread.1059296/ app, and its working, but only in headphones, speaker output is not working. but still can confirm that fm radio itself works, just need to find proper app i guess.
[Galaxy Note II Android Development] html6405:
I will implement a radio app in the next build :).
[Galaxy Note II Android Development] Zero_Shadow:
Thanks to you both 😁.

I look forward to testing that build.
[Galaxy Note II Android Development] AbdAbd10:
hi. i update to the last version from (08-02 to 20-02) but now apps that uses obb file cant detect obb
[Galaxy Note II Android Development] html6405:
Try if it really works with the previous version, there are in general access problems with android 11.

An app with installer permissions could grant it.

(Like X-plore for example)
[Galaxy Note II Android Development] AbdAbd10:
after i instell the rom the only way to access obb folder is from the recovery by the pc i tried many apps that i saw when i google it before i post the problem none worked x-plore one of them i go to the app info i see it read the obb file in the size of the date but i start the app it cant detect it and ask to download it again
[Galaxy Note II Android Development] html6405:
I'm sorry but I don't know how to solve this.
[Galaxy Note II Android Development] AbdAbd10:
no problem thnks for trying to help for your hard work
[Galaxy Note II Android Development] igloto:
Thank you for your excellent ROM. Besides the OBB files problem already detected, I have been working with GPS apps. In particular, with car driving apps, the GPS begins working very well, but stops working after few minutes. And, if you reboot the app, the problem comes again in few minutes.
[Windows 10, 8, 7, XP etc.] amir _miraki:
hey guys i have got my acer nitro i5 2021 model with intel i5 11gen gtx 1650 and 8gb ram and i relized 512gb storage is not enough and i found my old dead acer notebook from years ago and it a 1tb hard drive in it i took the drive out of it but the hdd has windows 10 os on it and is it good idea to put a hard drive with a os on it in my laptop or should i get a hdd tool and format the hdd and with the ram if i upgrade my ram do i need to reset the pc to get the ram working???
[Windows 10, 8, 7, XP etc.] Mastermanifestors:
Before u do that check the old HDD health first (u can use HD sentinel), if HDD health below 80% then better to leave it alone. And about the OS, formatting HDD is the best option in my opinion.
[Android Q&A, Help & Troubleshooting] Zeray:
I have a Lenovo A6000. Android version 5.0.2. It has an unlocked bootloader and twrp 3.1.1-0(not rooted). It can boot into Recovery and Fastboot mode. I flashed magisk using zip file method by renaming Magisk 23.0 apk as .zip and flashed it using twrp. For some reason, the Twrp was not able to see the files in internal storage then I used SD card to flash magisk. It was successful. But now while rebooting to system. It is stuck in this screen. I have connected my phone to anotger one using OTG cablr and the bugjaeger app is showing all the processes are running.Is this normal after flashing magisk for first time? It's been about 20 minutes yet no avail Please help.😢😢
[Android Q&A, Help & Troubleshooting] Zeray:
I fixed it guys. I just unistalled magisk using uninstall.zip. Sorry for the inconvenience caused by me
[Nubia Red Magic 6] ozkaya:
Hello guys, I am considering to buy Red Magic 6 Pro and was wondering if it comes default with Google Phone (Dialer)? I really enjoy Google Dialer in my current phone as it can block spam automatically and has nearby places etc.
[Nubia Red Magic 6] veedubsky:
Nope comes with their dialer. I downloaded Googler Dialer and it wouldn't ring for me anymore. I had to delete it to get the phone to ring again.
[Nubia Red Magic 6] ozkaya:
@veedubsky have you tried setting google dialer as default? or vice versa? by vice versa I mean keep the stock dialer as default, because sometimes setting Google dialer default also breaks things. you could also install Google dialer framework from Magisk modules if you are rooted.
[Nubia Red Magic 6] An Droid:
I've had the same issue with the RM5G since launch.

The Google Dialer on my 5G uses/sees notification sounds only instead of ringtones when you access its notification settings. It also defaults to silent. Contact ringtone settings also have no effect. I've tried multiple versions of the Google Dialer (on multiple stock ROM versions) without success - forced back to using the stock Dialer, unfortunately.

I'm inclined to think it's a ROM issue in terms of how ringtones/notification sounds are configured/defined.
[Nubia Red Magic 6] veedubsky:
Yup tried setting as default and then clearing default and leaving it alone. Either way the Google dialer wouldn't not produce a ringtone alert. I get the answer screen but no sound or vibe. Deleted it and stuck with the stock dialer.