yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II N7105 Android Development] trJck:
First. Thank you and thanks to developers of LineageOS for the best rom for my old device. So far, so smooth and ultimate stable! ?

Second. My english is not good, but i hope you can understand me ? Sorry for it.

Third. Need some little fixes, please repair it, not only me, but especially for owners ? and please tell to developers, cause i can't find any contact with they.

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

Need FIX/ADD :

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

#1. ADD. S Pen cursor/pointer please. I need it so much, cause i like to draw and i think not only me. Only that cursor/pointer i need it so much!

P.S Overall S Pen works perfect ?

#2. FIX. 3G/LTE Mobile Data random off and don't connect again. I live in Uzbekistan, Carrier is Beeline UZ. Just need automatic reconnect. Sorry again for English. I use only 3G

P.S Overall i use plain mode reconnect for work it again, sometime that not work ?

#3. And in code view *#*#4636#*#* About Phone Mobile data use WCDMA Preferred. I change it every reboot to WCDMA only.

That's it! I hope that will be fixed/added.

P.S I can't use logcat e.t.c

I run without root.

Thanks again for da clean Android and user experience! ??????
[Galaxy Note II N7105 Android Development] aghamoosaraza:
3G/LTE not working

I seem to resolve the Lineage update issue myself.

But I have made some other blunder as well. My 3G/4G LTE IS NOT WORKING. 2G is working but not quite well. After installing lineage, my device was network locked displaying 'network sim unlock code'. After going through multiple threads on the same forum, I wiped my efs folder through *#197328640#. Though i made a backup of efs folder through 'Partitions Backup & Restore 2.0.1 apk by Wanam'. I dont have an IMEI number as well.

I dont know what to do now. Do I have to say good bye to my 3G/LTE on my phone? I am freaking out. Please HELP.

Phone is Samsung Galaxy Note II (t889)
[Galaxy Note II N7105 Android Development] Option58:
I might be able to kang a pointer from LineageOS for Galaxy Note 3. However I'm on vacation right now so in a few weeks.

You should never wipe EFS as it's device-specific. Luckily you have a backup. Search xda and find any way possible to restore it, can't tell you more about it.
[Galaxy Note II N7105 Android Development] Johnny1969:
Is wifi calling possible on this rom for cricket (AT&T prepaid)? This option ia available and working my iphone.
[Galaxy Note II N7105 Android Development] anderswien:
Whatsapp bluetooth prpblem

Now i noticed that bluetooth talking with whatsapp no function . Cant hear anything, but with phone only no problems. Normal calls with bluetooth no problems at all. Any suggestion to solve this?
[Galaxy Note II N7105 Android Development] papei:
Frequently not receiving calls

I have noticed that from time to time my devices is as if it was not online. It won't receive incoming calls. Generally a reboot will bring it back online when it does happen. I was wondering if anyone was experiencing anything similar.
[Galaxy Note II N7105 Android Development] dethan12:
YES FINALLY I INSTALL MY DREAM ROM THANKS TO THE DEVELOPERS ...BUT I HAVE A PROBLEM WITH THE DATA CONNECTION WHICH FAILS TO GO ON SOME TIMES AND I HAVE TO RESTART ....MAYBE THATS THE ONLY ISSUE I HABE SEEN SO FAR OTHERWISE CHEERS TO EVERYONE .....

AND HAPPY NEW YEAR MATES:good:

..SHV250S
[Galaxy Note II N7105 Android Development] Armantas:
As mentioned Option58 earlier, it is impossible to fix LTE, 3G connection bug at this time. It starts with LineageOS 14. Solution is to stay on 2G. Randomly reboots is not a big problem. Can live with that. By the way, after one of the nightly update, my phone became sim locked, which actually was unlocked variant. Annoying unlocking procedure solved it.

GT-N7105, N7105BVDMF2
[Galaxy Note II N7105 Android Development] Cyanogenmod 12:
New build up. 1/5
[Galaxy Note II N7105 Android Development] mangojack01:
I have edited the build.prop file to add more steps to sound volume control, from stock 14 steps to 30 for media and 20 for phone volume by adding the following lines.

ro.config.vc_call_vol_steps=20

ro.config.media_vol_steps=30

This does not increase the device maximum volume it only gives a more gradual volume increase/decrease especially at low volumes.

Is it possible to edit flashlight time on by this method?

If so, what would the correct command line be?

Flashlight works fine, always has. I just want a shorter auto off time.

Also is it possible to disable the High Volume warning notification by editing build.prop?
[Galaxy Note II N7105 Android Development] rfrazier:
Me too, but on the teaching side. ;)

Best wishes,

Bob
[Galaxy Note II N7105 Android Development] Option58:
PoisonNinja do you know why LOS guys wouldn't allow us to remap buttons that way? I mean if you look at Galaxy S3 (official) device tree they did it the same way. Today I was trying to find alternative but it is really time consuming and I wonder why no-one else remapped it by changing settings defaults. It's not like there will be any security problem...Our device is five years old almost, we don't have to follow exact rules. We should also move keymapping to device tree as well.

Anyway I submitted a few patches to Ambient Display. I even decompiled CM13 ROM to find out exact brightness value because I know it was just perfect when I was using it earlier. :D It's ready to be merged (but test it still just in case). Regarding that line - it is present everywhere and none of these devices have doze sensor. It must have some function. If you really believe it has no funtion - you can later create a seperate commit that says 'remove unnecessary line' or something like that and then revert if it breaks...

Also added a line to allow t0ltektt since it worked for this guy.

Good job on that SELinux. :D
[Galaxy Note II N7105 Android Development] PoisonNinja:
See https://review.lineageos.org/#/c/163018/.

I forgot to cherry-pick the Ambient Display commit yesterday when I was building. I will test the commits either tonight or tomorrow.
[Galaxy Note II N7105 Android Development] Option58:
Yes I saw that. But I do not understand him. Did he say dad because it is illogical to call menu button recents or there is deeper reason (please forgive me if there is and I insulted someone becausr didn't know it).

Can you explain what should SELinux bring us :D Yes it is requirement for official, but are we more secure now?

---------- Post added at 22:13 ---------- Previous post was at 22:11 ----------

BTW this LineageOS for t0lte works miles better than my old CM13 built specifically for t0lteskt. I have dilemma right now - vibration or everything else literally. :D
[Galaxy Note II N7105 Android Development] PoisonNinja:
He is saying that the method we are using is a hack, and there is a better way to do this.

SELinux enhances security if the rules are properly written, and it blocks applications from doing malicious actions, even if it manages to escape the sandbox. It's like another layer of defense. For me, SELinux is just a PITA though.
[Galaxy Note II N7105 Android Development] Option58:
Thanks for clarifying that :) Of course it is a hack but not much developers are working on t0lte anymore. Do you really think other things aren't hacks? :) Aren't we better off investing our time into something better. Talking about that terminal rejects me trying to remap menu into recents the other way I was trying but...I think I got menu to go to split when holding and home to assistant when holding. But this just isn't accepted. Perhaps line should look a little bit different...
[Galaxy Note II N7105 Android Development] PoisonNinja:
TARGET_REQUIRES_SYNCHRONOUS_SETSURFACE prevents the flashing screen we had back on CM13. Besides, we already set that: https://github.com/LineageOS/android_device_samsung_t0lte/blob/cm-14.1/BoardCommonConfig.mk#L29.

I'm going to create a Slack channel for this. Like I said before, we shouldn't clutter the forum thread. Can you PM your email so I can invite you to Slack?
[Galaxy Note II N7105 Android Development] Option58:
Alright looks like there really is a reason :D Sorry to you all haha
[Galaxy Note II N7105 Android Development] JoshuaDoes:
I'm looking to setup a raw daily build server specifically for the t0lte variation of LineageOS 14.1. In fact, I've already set everything up and am currently compiling the third build of it as we speak (it's at 43% and builds finish roughly anywhere from 30 minutes to 7 hours, 7 hours being if it has to compile the entirety of everything from scratch such as during the very first compile).

My only issue is that anything to do with the SIM card does not function, such as SMS/MMS, calling, and data. I read somewhere a little ways back on this thread that you cherry-picked from another version of the same hardware setup that makes this work again, but I can't seem to find that reply anymore and therefore am unable to try to identify the phone myself.

Any and all help would be appreciated, including any other cherry picks you have in your build environment that will make these builds function more properly. I've already applied the proprietary blobs from TheMuppets, and the only other difference that would currently be in place is the OTA update server location. In this case, that will point to my own OTA update server (which is setup using LineageOTA by julianxhokaxhiu) so that when a new build is completed each day by my buildbot I can begin the download as soon as my phone receives the notification for the update.

Thanks in advance,

Joshua Wickings
[Galaxy Note II N7105 Android Development] Option58:
Please check review.lineageos.org. PoisonNinja already merged RIL fix, it should work, it works for me. Also I believe your answers might be on page 2 in this thread. Did you set selinux to permissive?
[Galaxy Note II N7105 Android Development] PoisonNinja:
As Option58, you need to set SELinux to permissive. Open kernel/samsung/smdk4412/arch/arm/configs/lineageos_t0lte_defconfig and add androidboot.selinux=permissive to CONFIG_CMDLINE.

You should probably wait until we get RIL working with SELinux enforcing, as that means that you can directly build it with the buildbot automatically without having to patch the code manually.
[Galaxy Note II N7105 Android Development] JoshuaDoes:
Thank you! I'll definitely wait it out on that note. Also, will working RIL be pushed into one of the repos in the current manifest? Or will I have to re-setup my build environment and/or add a new repo to the manifest?
[Galaxy Note II N7105 Android Development] goofwear:
[MENTION=6299732]PoisonNinja[/MENTION] THANK YOU SO MUCH. This works on my I605 I have no problems. I do not have a cellular service/ a sim card on/in this phone so I cannot test that portion to see if it works.
[Galaxy Note II N7105 Android Development] PoisonNinja:
Everything I do is available at https://review.lineageos.org/#/q/project:LineageOS/android_device_samsung_t0lte.
[Galaxy Note II N7105 Android Development] Sryak:
delete by some reason.

Sorry for my ignorant!

I think this content is not suitable this thread.
[Galaxy Note II N7105 Android Development] PoisonNinja:
No no no don't do this. There is a reason why SELinux is enabled. There really is no reason to disable it, as properly written rules don't break anything that's legitimate.
[Galaxy Note II N7105 Android Development] Sryak:
OK, Thanks for notice.

but I use viper4android, so I need use this.

I need to make sure when people didnt need it, dont use.

ro delete...?

edit: I think delete is more better.

edit2: I'm Sorry dev. My misunderstanding because I did't understand clearly.
[Galaxy Note II N7105 Android Development] infinidee:
I just flashed this rom today and there's one problem I'm facing now. I can't turn on my wifi. And I think it's the wifi mac address coz it shows 02:00:00:00:00:00. Can someone help me with this?
[Galaxy Note II N7105 Android Development] Awais Bhatti:
Flashed the latest build Selinux = enforcing

No problem at all.

What is difference in enforcing and permissive?
[Galaxy Note II N7105 Android Development] rfrazier:
Here's the log from when I was trying to take a call. I'm afraid that I haven't learned how to parse the log, as I don't do android debugging.

Best wishes,

Bob
[Galaxy Note II N7105 Android Development] azharnugroho:
I currently have the 201715 build. And flashlight doesn't seem to be working. Anw, i have SHV250S.

Looking forward to the next build.
[Galaxy Note II N7105 Android Development] ramcadag:
I just flashed the lineage-14.1-20180105-nightly-t0lte-signed build. after successful intall, I cannot connect to my wifi network. It can see the wifi though and it tries to connect but it halts and just displays "saved" below the SSID. Any suggestions?
[Galaxy Note II N7105 Android Development] Option58:
For those unhappy about modem/calls:

OK, I promised to you guys that I'll let you know as soon as I get something. This is (another) attempt to fix RIL issues some of you have. :) Two different ones. I don't guarantee anything will be fixed. I can only make tryouts like these and hope. This is for those of you who are unhappy about our RIL and willing to spend some time testing something new. If anything proves to be good I'll eventually include in official builds.

WIP completely reworked RIL part that is open-sourced. The part that controls how calls and information from operator are handled. This one has to be seperate build and not a patch. So you'll need to clean flash to test this. Data still doesn't work on first boot I think.

https://www.androidfilehost.com/?w=files&flid=240546
[Galaxy Note II N7105 Android Development] peterhugelberg:
i'll try to test it out over the weekend (clean flash is always kind of a hassle ;) )
[Galaxy Note II N7105 Android Development] robjg63:
Wow thanks - Not sure when I can test this at the moment - but will see if/when I can.
[Galaxy Note II N7105 Android Development] Option58:
Np guys. ;) I now updated the post above with another patch.
[Galaxy Note II N7105 Android Development] nate121:
SMS doesn't seem to be working for me. Anyone else having this issue?
[Galaxy Note II N7105 Android Development] peterhugelberg:
Calls and SMS work for me, so far it looks good. However i had some wakelocks today which where unusual (but im guessing they were related to a magisk module i was trying out, so i removed them again and will keep an eye on it)

im using Version 1 (the second option was not available when i clean flashed)

Edit: looks good so far, wakelocks (PowerManagerService, battery-monitor and mdm_hsic_pm0) are comparable with the official version (~7.5 hours total with an uptime of 45,6 hours, 2% battery per hour)

So far no lost Network connection or reboots.

Landscape Bug for Spen is also fixed, however i was not able to get it to show the stylus pointer icon.
[Galaxy Note II N7105 Android Development] dethan12:
same issue on the my shv250s:confused:
[Galaxy Note II N7105 Android Development] Porny:
I installed the 20180112 build but data doesn't work properly. The connection is very unstable and i get a lot of timeouts although the signal is really good and LTE / 4G is available.

Edit: Changing to flight mode and then back does sometimes work for a few hours.

But the alarm issue is fixed and my calls doesn't disconnect randomly anymore :)

Great work, Option58 and PoisonNinja
[Galaxy Note II N7105 Android Development] Option58:
Thanks for testing. It'd be the best if you notice that something specifically was broken on official and now it's fixed. eg. calls used to drop now they don't etc.

Shame about the pointer :p

Yeah, I'm starting to notice this on my e250s as well. It works but it stops working after some time. Fixes miraculusly by new flash.

Will fix it eventually when I have more time.

See the post above for the unhappy if you have problems with the ril. That's what we currently have.
[Galaxy Note II N7105 Android Development] peterhugelberg:
I never really experienced dropped calls, so i cant say if it got better with the new version.

I do however loose my connection far fewer times now, only on my daily train commute, but there it is due to a lack of phone towers. With the latest official i noticed loss of connection a couple of times a day.

It would probably be great if someone who suffered from dropped calls could also test it (as well as from a different country and or installed modem)
[Galaxy Note II N7105 Android Development] Option58:
I just gave you an example I meant anything that bothered you. Lose connection could be legit issue. Sounds good for now.
[Galaxy Note II N7105 Android Development] nate121:
Sorry for this noob question but i gotta ask anyways. I've never dirty flashed before so i'm wondering, do i have to also reflash the open gapps package after flashing the rom or just the rom alone is enough?
[Galaxy Note II N7105 Android Development] Option58:
You don't need to reflash gapps. Even no even need to reflash magisk. Just dirty flash the new rom build.

But nowadays no need to dirty flash anything anymore. Just make sure you use TWRP that is in the OP and you can OTA update via settings. About phone > LineageOS Updates.
[Galaxy Note II N7105 Android Development] nate121:
Ooh ok, good to know :). Hope the latest build fixes my sms and flashlight issues.

Flashlight is working now, didn't work until after a reboot for me but still issues with the sms. I'm able to receive but not send. It always says "Not sent. Tap to retry". Any ideas??
[Galaxy Note II N7105 Android Development] Option58:
On Oreo progress:

https://xdaforums.com/showpost.php?p=75240910&postcount=3969
[Galaxy Note II N7105 Android Development] Cyanogenmod 12:
If oreo update, I want to be your experimental phone.I awlays appericiate developers :)
[Galaxy Note II N7105 Android Development] LimWilliam65:
I really can't wait for it(Oreo ROM)
[Galaxy Note II N7105 Android Development] Kerann44:
Tried the new blobs also. Got data drops every 2 min too although LTE signal is good..

French carrier BouyguesTelecom.

Thanks option58 for trying to solve once again ! :)
[Galaxy Note II N7105 Android Development] peterhugelberg:
Just an update on the open source RIL experimental build:

I had to reboot my phone 3 times this week because i had no data connection after the phone slept for some time with wifi enabled. The indicator showed LTE and full reception (this even stayed after i enabled Airplane Mode) and data connections were only possible after a reboot and reentering of my pin.

I also had 2 random reboots this week which forced me to reenter my pin as well.

As these issues all occured without me noticing at first and while i was not at home i was not able to grab any logs.

I was also not able to reproduce them at home for a chance to grab a log.

All in all the new version is still more stable for me then the official version with the old blobs
[Galaxy Note II N7105 Android Development] Johnny1969:
I'm getting similar behavior with 1/19 build; no data connection after phone connect to wifi for several hours, hence no SMS. I had full reception but no LTE indicator, the only way to get LTE back is to reboot.
[Galaxy Note II N7105 Android Development] peterhugelberg:
interesting, so the culprit is probably something that got changed both in lineage-14.1-20180111-UNOFFICIAL-t0lte_test.zip and lineage-14.1-20180119-nightly-t0lte-signed.zip

Did you experience this with any other official Version before? I cant say for sure, because i think i skipped a few (i think i was still on the 20171229 build before flashing the experimental one)
[Galaxy Note II N7105 Android Development] Johnny1969:
I'm running 1/29 build, never used the "test" build.
[Galaxy Note II N7105 Android Development] fields_g:
I'm currently on 14.1.20180112-NIGHTLY-t0lte and am having the LTE drop till reboot issue. Additionally I have a problem with the phone Sleep-of-Death and cannot be restarted with power button. Interestingly, if I plug it in, it allows me to power it back on. Otherwise, I have to pull the battery. This is happening at least once a day. The most unique thing I have done with my phone is use the Magisk "Enable Doze for GMS v5" module, which is supposed to calm Google Play Services a bit and give better battery life.

I'll report in the upcoming days if 20180126 is still acting up.
[Galaxy Note II N7105 Android Development] Johnny1969:
Running 1/26 build and battery only charged to 82% overnight. Anyone else experiencing same behavior?
[Galaxy Note II N7105 Android Development] fields_g:
On 20180126 (formatted system, cache, and davik cache before installation):

SOD just happened again. Not able to start again until plugged into charger for a couple seconds (or battery pulled). Battery was still above 80%.

This Rom has always had MTP errors, but the description says only at while uninstalling a program. For me, this happens every time I go to a file manager program after a reboot. Do I have some crusty stuff in my /data or are others seeing this also?

No major radio issues yet (LTE/Wifi), they were infrequent before. I expect I just need to give it more time.
[Galaxy Note II N7105 Android Development] peterhugelberg:
Today i went back to the latest official.

The opensource experimental version seemed to get worse over time (no idea why, no new installed apps or any major changes). After i had 4 reboots in ~5 hours yesterday i decided to go back. I will keep an eye on the "no data after some sleep with wifi enabled" issue
[Galaxy Note II N7105 Android Development] Crike:
I'm on an N7105. After flashing lineage-14.1-20180105-nightly-t0lte-signed.zip and open_gapps-arm-7.1-micro-20180106.zip with twrp-3.2.1.0-t0lte.img, boot proceeds to the LineageOS splash. After a few minutes it shows the tripple-circle logo, then restarts the splash. It has now remained there for 30 minutes plus, with the key lights on.

What might be the issue?
[Galaxy Note II N7105 Android Development] Option58:
Try to wipe everything and flash again. If that doesn't work connect your phone to pc while it's bootlooping and give me 'adb logcat'.
[Galaxy Note II N7105 Android Development] Crike:
After wiping with TWRP and reflashing, LineageOS booted into the Setup Wizard but keeps spewing error messages.

If you'll want the logcat, just skip to the end.

First that the Clock has stopped, then a an endless stream about Google Services Framework. When I'm offered the choice to setup my phone, if I pick copy data\from the cloud it keeps hanging on Just a sec... while messages about Google Services Framework keep flashing, even if I setup the WiFi network in the settings drop-down. If I choose Setup as a new device, I get an error that the Wizard had crashed. The screen goes black and I'm returned to pick the language.

Should the LineageOS and Gapps versions I mentioned in my OP work with the N7105, or did I mess up?
[Galaxy Note II N7105 Android Development] Option58:
I've seen that. I suppose you're coming from TouchWiz?

Backup your data to PC (or MicroSD card) and wipe everything including your internal storage. Then try again.
[Galaxy Note II N7105 Android Development] Crike:
Yes.

Is that reversible? Can the Samsung stock image be restored with Odin, or is this a one way road?

---------- Post added at 11:07 PM ---------- Previous post was at 10:21 PM ----------

Tried, same result. Removed SD-Card, same result.

EDIT:

Tried again. It worked. Booted into the Wizard without any issues. No clear explanation why the last time was different.

All the same, thanks.
[Galaxy Note II N7105 Android Development] Johnny1969:
I'm experiencing some crazy random reboot with 1/26 build. Anyone experiencing similar behavior or it's just me.
[Galaxy Note II N7105 Android Development] Porny:
Disconnected call after some minutes + log

I recently flashed to the most recent build (20180126) and got very frequent phone & data disconnects.

Sometimes the phone reconnects after ~30 seconds, sometimes it doesn't.

If it doesn't, the phone application keeps trying to disconnect after hangig up, when i realize that the call disconnected with a short and dark beep.

My model is a N7105 with the N7105BUDMA1 Baseband and i attached the logcat file with the log between call, network drop and a removing of the battery.
[Galaxy Note II N7105 Android Development] br54:
Delete