yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II N7105 Android Development] PoisonNinja:
1. I would like to keep this as close as possible to official LineageOS so it's easier to get it official. No official build has SU builtin, so I will not enable this. Not everyone wants root builtin. If you want root, flash Magisk.

2. Not sure what blur is, but I'll take a look at it

3. AFAIK, LineageOS officially does not use this option in the system.prop. Probably legal issues. I will not add this because again, not all users want this.

4. Ambient Display will be reenabled when everything else works. I'm prioritizing SELinux over everything else right now.

5.I remember that I didn't enable Doze on MM because the Note 2 didn't have the correct sensor, but I believe that N changed it to activating when the screen's off. I'll check this again. The Doze commits you linked are for SamsungDoze, which is similar to AmbientDisplay, not the actual Doze.

6. The key related commits look good, I will add them. Watch https://review.lineageos.org/#/q/project:LineageOS/android_device_samsung_t0lte for updates.

7. Will do.

Thanks for all your research!
[Galaxy Note II N7105 Android Development] PoisonNinja:
Originally, I was using the opensource RIL, but it completely broke RIL for me. I couldn't get any signal. For the i9305, try using the original proprietary blobs. If they don't work, you can maybe try t0lte blobs.
[Galaxy Note II N7105 Android Development] Option58:
At least I am not feature requesting you. I am trying to contribute.

Thank you for everything. Especially for How-to-build. I will now attempt to bring LOS to E250S which is my primary goal. Also love my personal builds with some non-official Lineage stuff. Please document any change you do on github or on xda.

I asked rgib to help us because I didnt know you will fix RIL.
[Galaxy Note II N7105 Android Development] rgib:
I use opensource ril and it works perfectly. That's why I asked. thanks
[Galaxy Note II N7105 Android Development] Michaelb04:
Anyone got magiskhide working? Its doesn't do anything apps still says my phone is rooted. And the saftyney check doesn't pass.
[Galaxy Note II N7105 Android Development] PoisonNinja:
Thanks. You don't know how many PMs I got that were like, "WHEN ARE YOU FIXING RIL????" and "WHEN WILL WE GET LINEAGEOS FOR OUR NOTE 2?". Your help is greatly appreciated, and I apologize if I sounded a little rude in my other post.

Most of my changes are on Gerrit or on my computer waiting to be pushed to Gerrit.
[Galaxy Note II N7105 Android Development] PoisonNinja:
Thanks for your work. I used a lot of your work on the i9305 for t0lte :D
[Galaxy Note II N7105 Android Development] Option58:
Ehhh...It is me who maybe sounded a little bit rude with 'do this do that', sorry. Now when I actually tried compiling LOS you have no idea how much more I respect all developers. :D Really appreciate RIL fix you know your stuff sir :D On top of that a lot of developers wouldn't even reply to me you are truly awesome...

N7100 did already a lot of work we can steal hehe :)

But do you have any idea where or how could your recent changes break wifi support on our devices (E250S)?? :confused::confused: I am looking at your commits but...a lot of code it could be anything...

Oh one more thing - I tried some i9305 tree stuff earlier that broke wifi as well...

Logcat attached
[Galaxy Note II N7105 Android Development] PoisonNinja:
I'm pretty sure that it's https://review.lineageos.org/#/c/161954/. I must have forgotten something. I'm going to revert that and build again.
[Galaxy Note II N7105 Android Development] PLHokus:
Hotspot don't work :/
[Galaxy Note II N7105 Android Development] chironfr:
Some more feedback.

My phone has been up since 26 hours. No reboot, the error message : "sim removed, please reboot" is gone.

Seems rock stable.

Very very good job! :) thank you so much.
[Galaxy Note II N7105 Android Development] silvertag:
Running it for the last two days and performances are solid.

Only issues so far are hotspot and audio via headphones. It does not have the necessary librairies for the SGH-i317m. Audio is garbled up. Had similar issues under CM13. Speaker works ok.
[Galaxy Note II N7105 Android Development] lalit1:
Means can not listen music with headphone? I alao have 317, CM used to work fine
[Galaxy Note II N7105 Android Development] PoisonNinja:
Are the headphones connected via Bluetooth or a wire?
[Galaxy Note II N7105 Android Development] kozmo21:
No, he has the 317m (Canadian version), regular i317 for AT&T works fine for audio.
[Galaxy Note II N7105 Android Development] silvertag:
Wire headphones only. Speaker or bluetooth headset works (not tested yet but always worked)
[Galaxy Note II N7105 Android Development] br54:
Odin a stock ROM that matches your bootloader

Nothing against this ROM.. But roll back to MM.

same happens to me on this ROM.
[Galaxy Note II N7105 Android Development] rfrazier:
I've had three problems in the last few days.

1. One random reboot.

2. One loss of all connectivity (phone and wifi). A soft boot didn't fix it, but a hard boot did.

3. A few times the home and recents buttons stopped working. Interestingly, the back button continued to work. A soft boot fixed this.

I don't know how to get the problems to repeat, so no logs.

Best wishes,

Bob
[Galaxy Note II N7105 Android Development] hedgecore44:
I was having Sim card issues on my U.S. AT&T t0lte Note 2 with 3/31 official here. So i decided to experiment and do a full wipe (with latest TWRP) and reinstall a known good MM Mokee ROM (MK60.1-t0lte-170112-RELEASEMokee) . . . I was very happy for a few hours, as the issue seemed to have disappeared.. but, of course, my SIM issue came back. Does the SIM issue carry over? I dont get it... Gonna see if it persists on the Mokee 7.1 build.. hmmm
[Galaxy Note II N7105 Android Development] br54:
I'm on octo m

It seems like if you don't do a full wipe

Internal memory as well.

There are some left over.

I think it's due to the emulated partitions.
[Galaxy Note II N7105 Android Development] kozmo21:
The SIM re-lock can, and did happen on CM13 also. So going backwards to that, isn't going to solve that problem. There was only a very small # of people that had that happen, probably less than 2%, so if it happened to you, you were just unlucky.
[Galaxy Note II N7105 Android Development] PoisonNinja:
If there is a problem with the SIM even on MM, then I would assume that something is wrong with the hardware. You can try flashing the stock ROM with Odin, but generally speaking problems involving RIL do not persist between different ROMs. TWRP wipes really do wipe the partition.

I was flashing a RR build (kozmo21 might remember this) that didn't have working RIL yet, and when I flashed back to CM 14.1, it still wasn't working. Turns out I forgot a couple sepolicies.

TLDR; try flashing a stock ROM with Odin. If it still persists, then something is wrong with the SIM card or the SIM tray.
[Galaxy Note II N7105 Android Development] PoisonNinja:
Hey guys, I have a build using the RIL with blobs, but with the latest Lineage changes. If you don't need this as your daily driver, can you try this? https://www.androidfilehost.com/?fid=817550096634759878.

Let me know if it helps with the call issues and random reboots.
[Galaxy Note II N7105 Android Development] br54:
Seems so... No problems persist on mm

Then MM it is, enjoy!
[Galaxy Note II N7105 Android Development] agovinoveritas:
Although it could be a SIM issue for some, it is definitely not for me. It seems that the issue does in fact carry over and I only started having it after flashing one of the experimental ROMs that was put forth here.

I backed up and all of the sudden I get the same errors on other ROMs. But only Nougat ROMS since, if I do a full and total backup from an MM ROM I have as backup, I have no problems whatsoever.

That backup includes everything. (modem, boot, etc)

If I were to wager a guess I would think the problem is with RIL or some library/dependency.

Since after the SIM fails, I figure out that com.android.phone stops as well.
[Galaxy Note II N7105 Android Development] peter58ha:
Good morning kozmo21

I try the steps from this thread: https://xdaforums.com/showthread.php?t=2014982

When I enter the code

*#197328640# nothing happens...

I checked with *#06# and IMEI shows up

.

I have NO sim card plugged to the cellphone...

Any other advice what I can do in this case?

And sorry, will use the search function from now on FIRST..

Thx for your patience

Best regards

Peter
[Galaxy Note II N7105 Android Development] lalit1:
His will not work in Custom latest ROM, you will have to go to old stock rom
[Galaxy Note II N7105 Android Development] nldasha:
I am on latest official build. The first time I tried to use bluetooth audio in my car it did not work. After I set my preferred music player (MediaMonkey) as the default to open Supported links it did work. Something worth trying
[Galaxy Note II N7105 Android Development] rfrazier:
One of the things I've been happiest about with 7.1 is audio combined with bluetooth (headphones). I don't know whether there have been substantial changes to the audio stack, but it is working much better.

I have Logitech media server running on the house server and some squeeze clients on various devices (house server, desktops and Raspberry PIs). This gives whole house syncronized music.

I added the Note to this system using the Squeeze Player app. I was playing some Joan Baez (shows my age) on the Note 2 over bluetooth headphones when out in garden doing some landscaping work. To my surprise and delight, when I came into the house and took off the headphones, I found it was in perfect sync with the music in the house.

Best wishes,

Bob
[Galaxy Note II N7105 Android Development] Naedean:
I tried this lineage os on note 2 shv-e250l korean but it doesn't work. I followed the instruction but when I flashed the rom, suddenly problems or errors appeared. Where did I get wrong? Please, instruct me.
[Galaxy Note II N7105 Android Development] fields_g:
I take it this is no longer available. I was using the last available release of CM13 (cm-13.0-20161219-NIGHTLY-t0lte) on my t0ltetmo and just tried out lineage-14.1-20170331-nightly-t0lte-signed. It seems the cellular reception is worse with Lineage version (no signal while I am at my desk now). I was thinking of trying the binary blob version to see if there was an improvement.
[Galaxy Note II N7105 Android Development] PoisonNinja:
SHV-E250L is not supported. Only N7105 variants (GT-N7105, SGH-I317(m), SGH-T889), t0lteskt (SHV-E250S) and t0ltektt (SHV-E250K) are supported.

I pulled it since it wasn't working at all. I guess too many changes occurred between the OSS RIL switch for the blobs to work anymore.
[Galaxy Note II N7105 Android Development] fields_g:
Actually.... There is very heavy rain right now. The after reverting back to CM13, it isn't doing any better. Perhaps I'll give it another go after the official gets updated again.
[Galaxy Note II N7105 Android Development] PoisonNinja:
Huh, never knew that rain could interfere with signal. TIL.
[Galaxy Note II N7105 Android Development] PoisonNinja:
The first post has been updated with a list of supported variants. Please, if you're device is not on the list (SHV-E250L, SPH-L900, SCH-i605 mainly), do NOT download any of the builds. They will not work.

A bug with the WiFI affecting some users has been fixed, so it will be in the next build this Friday.
[Galaxy Note II N7105 Android Development] Option58:
Actually, E250L should work as well. Flash t0lte TWRP recovery, and then t0ltektt build.

Only cdma part of it won't...which is why it isn't official. But GSM and LTE will.
[Galaxy Note II N7105 Android Development] PoisonNinja:
They can flash it, but they do so at their own risk. I will not offer support to users of those devices.
[Galaxy Note II N7105 Android Development] rfrazier:
I seemed to remember something from the old days when I was a radio operator (US Coast Guard). At microwave frequencies, you could get "rain fade".

https://en.m.wikipedia.org/wiki/Rain_fade

Satillite comms were sometimes affected, but, of course, not communications with morse code in the medium wave range. ;)

Cellular frequencies are probably too low to be affected, but the microwave connections between stations might be.

Best wishes,

Bob
[Galaxy Note II N7105 Android Development] :
I am using the t0ltektt here in Korea and it works great! I am also getting the MTP error, but overall no major issues. Small idiosyncracies I noticed:

Suddenly google fit doesn't track steps well at all even when gps is on. Tried cache clearing, restarting, reinstalling etc.

In facebook chat, photo taking option has no button to actually take the photo. Thought that was odd.

Not sure if these are app bugs, 7.1.1 bugs, or Lineage Os bugs but thought I would share in case others experienced something similar.

I should note I installed the gapps nano package.

Thanks for your hard work!
[Galaxy Note II N7105 Android Development] Option58:
I've talked to PoisonNinja. We are unifying Korean devices into 't0ltekor' builds which will support all three variants (E250S, E250K, E250L).

Expect the change from next week.

You'll also have to clean install that, sorry.
[Galaxy Note II N7105 Android Development] Naedean:
Thank you. I hope will work. :good:
[Galaxy Note II N7105 Android Development] fields_g:
Lineage-14.1-20170407-nightly-t0lte is now up.
[Galaxy Note II N7105 Android Development] fields_g:
The NEW "April 1st" mascot is the new boot animation on 20170407. Cute.
[Galaxy Note II N7105 Android Development] rfrazier:
So far, everything works, even system profiles. A production version. Cheers!

Best wishes,

Bob
[Galaxy Note II N7105 Android Development] TimmyL:
Unable to install latest ROM

My N7105 got 20170331 Nightlies ROM, and download the latest 20170407 Latest ROM and try to install it but failed. And Manual download it to the phone and install it.
[Galaxy Note II N7105 Android Development] paulosaints:
Same here! And i dont know where to find the downloaded file in the storage... i am using fx explorer.

The way to install is downloading the image to your laptop, connect the Note to the laptop, move file from laptop to Note 2... recovery, twrp, bla bla
[Galaxy Note II N7105 Android Development] rfrazier:
Downloading with the system updater puts the file in the following directory.

/data/data/org.lineageos.updater/app_updates

I just use the browser to download the zip file, which puts it in Download. Since Magisk is also in Download, it makes it pretty easy to update.

Best wishes,

Bob
[Galaxy Note II N7105 Android Development] PoisonNinja:
If you want OTA updates to work without manually installing the zip, you'll have to flash LineageOS's recovery. See my post below.

7.1.2 appears to not be working on Exynos 4412 devices, so for now Lineage will be stuck on 7.1.1 until the issues are resolved.
[Galaxy Note II N7105 Android Development] mireval:
How to flash LineageOS's recovery?
[Galaxy Note II N7105 Android Development] PoisonNinja:
Oops, Lineage doesn't have their own recoveries. Cyanogenmod did, but I guess Lineage doesn't have enough resources to build recoveries for every device.
[Galaxy Note II N7105 Android Development] mireval:
So we can't make OTAs working?
[Galaxy Note II N7105 Android Development] rhaneyjr:
I do believe that's what he is saying
[Galaxy Note II N7105 Android Development] deathgunxxx:
Kernel

Do i have to flash any kernel?
[Galaxy Note II N7105 Android Development] Thomas.A.A:
GT-N7105 with TWRP-3.1.0-0-t0lte

Lineage-14.1-20170331-nightly-t0lte-signed.zip and GAPPs

Root Manager Magisk

Hello and thanks for all the effort - I have SIM CONNECTION issues

The phone finds the mobile network but fails to connect

Also once it fails it is unable to find the mobile network again unless it gets rebooted

I am open to any suggestion and ready for any test. Thanks

PS: I did not wipe internal memory before installing the ROM
[Galaxy Note II N7105 Android Development] PoisonNinja:
No, the ROM includes one already.

SIM CONNECTION is incredibly vague. Is that an error message? Please provide a logcat. See the 3rd post for instructions on how to do so.
[Galaxy Note II N7105 Android Development] hedgecore44:
I had sim card errors too. Apparently if you do then you are part of the "unlucky 2%" and are screwed unless you provide logcat (whoops).

So what I have tried..

I flashed clean back to Res Remix MM and even a MOKEE MM ROM and could not believe I was getting the exact same SIM errors on ROMs that I know have been known goods in the past.. I even tried flashing various modems.. same thing. Weird.

So somebody else here said (10-20 pages back) to reflash to stock 4.1.1 with ODIN so i did that as well. seems to work ok on 4.1.1... ok.. so then i wiped and flashed to 7.1 ROM and was happy. Ran great for about 3 days.. Then.. SIM card errors (something like "could not connect to SIM, need to restart, etc") are back... I even tried same steps again and flashed with MOKEE 7.1 just in case... same thing..

So finally ODINed a 4.1.1 stock again and then (sadly) flashed W03 Slim 4.4.4 ROM and all is well. All my same apps work but I miss the 7.1 layout. but at least I am not wasting hours anymore.

Anyway. Let me know if you figure it out.. sorry i never provided log cat :/
[Galaxy Note II N7105 Android Development] Option58:
The main problem here is that not all Note 2 devices are 100% the same. That's why you may come up with errors.

But no one actually knows what happened there until logcat. That's just one app on Google Play. It's not anything hard or time consuming.
[Galaxy Note II N7105 Android Development] br54:
Same here.. My Sim disconnects and then relocks.. As much as I like nougat.. It just don't like me phone

But runs perfect on OctOs OctM.

As far as MM acting up.. It did with me too... Until I sanitized any nougat files left on my phone.

About a month with 0 issues

So who knows.
[Galaxy Note II N7105 Android Development] Option58:
t0lteskt and t0ltektt builds are stopped.

E250S, E250K and E250L are officialy unified under t0ltekor now. Expect new build tomorrow.

https://www.lineageoslog.com/14.1/t0ltekor
[Galaxy Note II N7105 Android Development] loulile:
Hi is it possible to include the eap sim fonction in the next build, im in france and it doesn't works thanks for your great job
[Galaxy Note II N7105 Android Development] PoisonNinja:
Did it work on stock, because I'm pretty sure the Note 2 didn't have that originally.
[Galaxy Note II N7105 Android Development] fields_g:
It's Friday. The new weekly "Nightly" is up. lineage-14.1-20170414-nightly-t0lte. Have at it.

This message isn't only to announce, but to mark the availability in the thread conversation.

If bug reports are made, please try to check against this version also.
[Galaxy Note II N7105 Android Development] saigarapati:
Plz change the boot animation
[Galaxy Note II N7105 Android Development] PoisonNinja:
That's out of my control. Why don't you change it yourself by flashing another bootanimation.zip or using Substratum?
[Galaxy Note II N7105 Android Development] fields_g:
Are you talking about 20170407? It was an April fool's prank that lasted a week (along with Br0zip). It was reverted in 20170414.
[Galaxy Note II N7105 Android Development] justin6162:
Hi I try to upgrade from 20170407 but it always gave me a error. I downloaded a couple of times and samething happened. Do I wiped cache before install it? Also did this nightly built fix drops from LTE connection all the time? I had to set network connection to 3g for temporary fix. Thanks for the hard work.
[Galaxy Note II N7105 Android Development] fields_g:
I just dirty flashed from 20170407 to 20170414. No problems.

LTE drops... I wasn't experiencing any before, so I cannot speak to anything being different.
[Galaxy Note II N7105 Android Development] PoisonNinja:
7.1.2 has been merged. Unfortunately it was merged right after t0lte builds started, so we will get 7.1.2 next Friday. I already built and tested it myself, no new bugs introduced (as far as I can tell).

As you probably know, t0lteskt and t0ltektt are now unified to t0ltekor thanks to [MENTION=4315222]Option58[/MENTION], and t0ltekor also includes support for t0ltelgt!
[Galaxy Note II N7105 Android Development] ascrackool:
did h/w composer ever get merged?
[Galaxy Note II N7105 Android Development] loulile:
yes eap sim on stock rom it on and work
[Galaxy Note II N7105 Android Development] PoisonNinja:
Not yet. I played with it a couple weeks back, and it's a lot smoother :) But, it still needs some work since sensors are broken with the new kernel we are using to get hwcomposer working.

I'll take a look at this, but I don't really know anything about EAP (it's not as common in the US I guess).
[Galaxy Note II N7105 Android Development] loulile:
bauner is a programmer from xda who include eap sim on his rom for n7000 it works like a charm because in cm is not native if you can have advice from him maybe
[Galaxy Note II N7105 Android Development] br54:
Bauner was awesome.

I had his night owl on mine

I miss that old phone.
[Galaxy Note II N7105 Android Development] loulile:
https://xdaforums.com/galaxy-note/development/rom-nightowl-preview-t3455847

link for his last built for n7000 in 7.1.1 if it help the eap sim is include on
[Galaxy Note II N7105 Android Development] PoisonNinja:
Thanks for the link, but that doesn't really help. N7100 is a completely different beast from N7105. I'm not sure whether we need blobs for this, because I see some devices need libwpa_qmi_eap_proxy.so, which N7105 lacks.
[Galaxy Note II N7105 Android Development] PoisonNinja:
What happens when you try to connect to a EAP secured network? Does the network not even show up at all? Or, do you get an error when connecting?
[Galaxy Note II N7105 Android Development] loulile:
I have an error of identification
[Galaxy Note II N7105 Android Development] PoisonNinja:
Please give me a logcat.
[Galaxy Note II N7105 Android Development] loulile:
The protocole sim is good but don't works, i try to modified wpa_supplicant.conf but useless
[Galaxy Note II N7105 Android Development] PoisonNinja:
Protocole SIM? Like I said before, I need logs before I can help you. See the third post if you don't know how to get a logcat.
[Galaxy Note II N7105 Android Development] Freddy1950:
Just installed t0ltekor on my Korean E250S, and I love it! Everything works and very smooth, and this is the first time I've managed to get vibration working since the original Samsung rom. Very nice.
[Galaxy Note II N7105 Android Development] :
Device: SHV-E250K

Build Date: Fri Apr 14 09:53:09 UTC 2017

Kernel Build Date: 3.0.101-lineage-ge31c37f@lineageos-build #1 Fri APr 14 09:57:17 UTC 2017

Logcat: https://pastebin.com/raw/3VUqXLfi

"download failed due to an unknown error."

Thank you for your hard work.
[Galaxy Note II N7105 Android Development] PoisonNinja:
FFS does no one ever read the post on "Reporting Bugs"? Please, I can't do anything without logs or a more detailed description (such as error message, anything that shows up on screen, etc.). This wastes my time and makes it much harder to debug. To those that do properly report logs, a big THANK YOU!

Anyways, I'm guessing that you're getting an error about sdcard or storage right?
[Galaxy Note II N7105 Android Development] :
Sorry, I have updated my post to follow protocol. I am not sure if the logcat is useful. I tried to cause the same error repeatedly when using logcat.
[Galaxy Note II N7105 Android Development] PoisonNinja:
Thanks for updating. I apologize if I seemed a little rude, it's been a long day for me. Unfortunately, your logcat isn't long enough. It should be much longer. How are you capturing the log?
[Galaxy Note II N7105 Android Development] :
No worries, I didn't follow instructions. I believe it didn't work because my phone isn't rooted (korean apps won't work on rooted devices). When I get a chance I will do a logcat through pc adb.