yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Original Android Development] mobliefranz:
Hi there

Thanks for this great ROM!

Been using it for a few weeks and it's great!

Had that issue with the gps not working and solved it by installing a different boot.img as described in the thread.

I also have the problem with bt headsets, the mobile network is dropped when starting a call, as described earlier in the thread. Is there a solution to this as well?

Also, what is the preferred method to update to a newer version?

I installed the version from the first post, i.e. lineage-14.1-20170116-tilak-n7100.zip

Though my phone says I am on LineageOS version 14.1-20170130-tilak-n7100, which is not quite the same?? Delta update keeps reminding me there is a new version, but the update does not work.

Thanks for pointing me in the right direction! :)

Cheers
[Galaxy Note II Original Android Development] Stud12376:
download latest versions of the rom from here http://tilak.sergix44.ovh/n7100/

preferably download 0324 build ,because latest build has some bugs.

also for delta update ,keep the zip of you current version in internalstorage/open delta ,then check for update ,because delta update helps you save data and time.the new buid zip will be available in you internalstorage/open delta folder,you can flash it manually from there or let open delta do the work.
[Galaxy Note II Original Android Development] sven1981hn:
Does Someone have Problems with screenmirroring to a Smart TV (I have a Samsung). It connects, But connection is being closed showing no content. The streaming from The Youtube App is working.
[Galaxy Note II Original Android Development] ntvampire:
Yes, screen mirroring not works properly
[Galaxy Note II Original Android Development] mobliefranz:
Hi

Thanks!

The update worked, and most things seem to be working as before.

The gps also is still working.

for some strange reason, file explorer is gone, tough.

And the bt headset still does not work. Has anyone been able to solve that one?
[Galaxy Note II Original Android Development] ashokram343:
i had a Philips bt headset it works fine for me and even sound quality was good i don't know why bt has problem so many are talking abt it and am using bt speakers works good through bt
[Galaxy Note II Original Android Development] sven1981hn:
Is a fix planned?
[Galaxy Note II Original Android Development] mobliefranz:
When I start a call with the bt headset connected, I get the error message:

"Mobile network not available."

(And the network is actually dropped, it reconnects thereafter.)

This does not happen without the bt headsets, i.e. I can do 'normal' calls just fine.

It does happen also with a different bt headset (tested a jabra and a plantronics device).

Other bt devices (i.e. fitness arm band) work fine.

Someone else has described the exact same problem in this thread some time ago.
[Galaxy Note II Original Android Development] Stud12376:
the download app is the hidden file explorer, in can do the basic things.are you on 0417, because video making doesn't work, and please instead click the thanks button
[Galaxy Note II Original Android Development] mobliefranz:
I'm on 0324, as per your recommendation.

Can anyone confirm bt headsets did not work in/upto 0324 and now does in 0417?

Delta update now seems to work. I did not try because I would prefer staying on 0324 for now if there are bugs in 0417...
[Galaxy Note II Original Android Development] Stud12376:
delta is working
[Galaxy Note II Original Android Development] stunned:
Mi band 2 doesn't work correctly. It loses bt connection and can't reconnect. Music is fine with BT
[Galaxy Note II Original Android Development] Skull97:
I'm not sure, but my mi band 2 works very well...
[Galaxy Note II Original Android Development] oromay:
No comments yet. I would rephrase the question - is video recording failure a common issue or should I try to reflash the system? :confused:
[Galaxy Note II Original Android Development] h_maharaj:
It's a known issue in the latest build. In my case, battery life in the latest build was really poor as well. I would suggest rolling back to the 24 March build as that one is more stable.
[Galaxy Note II Original Android Development] PeteMcMull:
Hi I'm using this rom it is great. Working best, few problems but gets sorted after some time or after restart. But I'm unable to update rom, notification comes to show update available but does not updates. Unable to attach screen shot
[Galaxy Note II Original Android Development] clayteau:
I am having problems with my mi band 2 as well. My computer detects it but my phone with this rom can't.
[Galaxy Note II Original Android Development] ashokram343:
u need to place the zip file of your present ROM in open delta folder which is located in internal storage
[Galaxy Note II Original Android Development] eradicus:
Yeah, it will download the updates then it will patch the zip file on the OpenDelta directory.
[Galaxy Note II Original Android Development] eradicus:
Has anyone encountered an issue with Instagram when taking photos with the latest build?
[Galaxy Note II Original Android Development] convair990:
At camera app no issues (filming+ photos), but it didn't work with 3rd party apps recording videos/pictures such asInstagram, Boomerang and Loop
[Galaxy Note II Original Android Development] mobliefranz:
So I need to correct my previous statement. 0324 does not work for me.

When I call someone, they can hear me allright but I hear nothing, not even the ringing.

So I went to 0147 through delta, same thing.

No prob, recover to 0130 from which I made a nandroid backup yesterday. Or so I thought.

But it does not work I still hear nothing!

Calls throught whatsapp work fine, though.

Has anyone made a similar experience, can anyone help?
[Galaxy Note II Original Android Development] cyclistefou:
A few days later but better late than never... OSS compositor seems for me to be the cause of significant trouble with my Firefox browser. Complete garbage on the screen in landscape mode, but when "tilted" a bit it may briefly flash with a correct rendering for a fraction of a second. Firefox was always perfect in previous builds.

Firefox in portrait mode 99.9% OK and most (all?) other apps OK.

Of course, using April 7.1.2 build.

---------- Post added at 06:43 PM ---------- Previous post was at 06:35 PM ----------

Again, late answer, but better than never - delay updates are not 100% binary same but they are functionally same. E.g. binaries downloaded are compressed zips bit zips generated by merge done by OpenDelta are not (or not fully) compressed - I guess to spare time, OpenDelta doesn't recompress the generated (patched) ROM, it uses zip format as container only i.e. no compression.

That's why MD5 are different.
[Galaxy Note II Original Android Development] nikkyAi:
works almost really well..

it seems like the SIM card is not detected

i tried rebooting, cleaning it enabling airplane mode and disabling it, etc
[Galaxy Note II Original Android Development] cyclistefou:
OK so I finally had time on Saturday to follow your very kind instructions. It didn't solve the problem completely (was constant Wi-Fi disconnects and most of the time, a reboot was needed to reconnect as fiddling with Wi-Fi settings often didn't help). At least now the Wi-Fi is much more stable, or at least the instability is graciously "hidden" by the fact that almost always it can reconnect automatically, like if there was a signal cut then restore.
[Galaxy Note II Original Android Development] mobliefranz:
With 0324 I installed open_gapps-arm-7...pico-20170423.

Now, just to try something, I reinstalled the older version I had before the call trouble started, open_gapps-arm7...pico-20170301.

Et voilà, calling works again!

This does not really make sense to me, since the nandroid restore should have restored that as well (right?, I flashed all the partitions).

I am posting this just in case anyone has a similar problem. I don't understand what's going on, I'm just happy I can do phone calls again. I think I won't touch the device anymore... (Except perhaps if somebody can confirm the bt call thing is *solved* by installing a newer version;))

Cheers
[Galaxy Note II Original Android Development] cyclistefou:
However I had a bootloop with the new BL which I could solve by restoring the BL that came from my 20170324 ROM full backup. Hence I am now using ROM 0417, with Baseband XXUFNG1, and for the BL I don't know how to get version from UI but if anybody asks I will check it in BL itself.

Regarding the Wi-Fi problem I am wondering if this could somehow be related to some power management cutting the Wi-Fi, the Android privacy feature of randomising MAC address and the Wi-Fi MAC filtering I have set at home. Will investigate further. I think it started occurring with first LineageOS build...
[Galaxy Note II Original Android Development] PeteMcMull:
Means I have to download it manually and put it in opendelta folder then run update?
[Galaxy Note II Original Android Development] mobliefranz:
Yes, except if you still have it on your device from when you flashed it, in which case you would just copy it (to /storage/emulated/0/OpenDelta)
[Galaxy Note II Original Android Development] convair990:
22-04-2017 new build version available at Tilak page:

tilak.sergix44.ovh/n7100/
[Galaxy Note II Original Android Development] logosA:
USE THIS TO SEE YOUR PHONE's details as BL, CP,CSC and BASEBAND.

https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl

BL, cannot be changed by restoring a backup, only with odin can be flashed in the phone and only with odin can be replaced too.

What you do change with restoring your backup, is your rom and with that you change your boot.img, the image that each rom uses to boot up.

WIFI mac adress, as BT mac αdress, cannot be changed as its a unique, hard-cored serial Nr that the chip has and cannt be change. This is why wifi mac filtering is the strongest method to secure your wifi router. The IP adress can be masquerade in order to not be easily traced (not impossible yet), but not MAC αdress.

Usually in our phones, WIFI and BT MAC ADRESSES have only one letter difference. So take a look and see in your routers filtering, if there is a mistyping that could cause you troubles.

What I have also noticed in the latest updates of all the Lineage based roms, is that wifi ''sleeps'' when screen is off and when screen is back on, all notifications and connections start again. This may have to be connected to doze and power saving methods, but its left to be seen in some time of further use , in order to establish whats happening.
[Galaxy Note II Original Android Development] cyclistefou:
Hi LogosA, well I am not sure for this specific ROM but I am quite positive MAC addresses CAN be changed by the system in 99% of devices. Indeed most devices have a stored MAC address flashed at manufacturing and used as default MAC address, but with appropriate privileges one can either craft packets with custom MAC address or simply instruct the Ethernet/WiFi controller to use another one by default, with iwconfig/ifconfig for example.

See this: https://arstechnica.com/security/20...talkers-is-hard-android-is-failing-miserably/

---------- Post added at 09:24 PM ---------- Previous post was at 09:17 PM ----------

But you're right I must have restored something else than BL as it can't be done via TWRP... Was a small partition between 6 and 9 MB don't remember which :)

Anyway on my working config BL is: XXSFQA5
[Galaxy Note II Original Android Development] PeteMcMull:
Thanx

Great help buddy...
[Galaxy Note II Original Android Development] logosA:
EFS maybe (IMEI, modem etc)

THANKS for the HEADS UP about MAC ADRESS, I really didnt knew that.

BL that you have now, is one of the latest available for european phones, so you are up to date.

I think you can reach even android O with that one!

good work :)

edit: SORRY, I cannt thank you properly, I have reached my daily limits for today. I will owe you one
[Galaxy Note II Original Android Development] cyclistefou:
:) thanks to you too :)
[Galaxy Note II Original Android Development] yamsu:
Just updated to 20170422. My observations so far:

+ Opendelta update route worked

+ Root access and permissions working through developer menu

- Edit status bar shortcuts is partly broken, unable to scroll with a shortcut from the lower section to the top status bar, to make it active. This problem was there in the previous version also; however, it worked in 201701XX ROM version

= MTP close error on launch of Download, hidden file manager persists.

+ GPS continues to work

+ Bluetooth continues to seems stable

Battery drains will take some more time to evaluate. What was the intended focus for the new 20170422 update?
[Galaxy Note II Original Android Development] Stud12376:
please check if videos can be made on not, live display is working?
[Galaxy Note II Original Android Development] yamsu:
For 20170422 ROM

+ Live display is working, screen redness increases automatically based on time of day.

+ Video can be captured from the inbuilt camera app.

+ No noticeable delay on phone wake or during call

= Battery drains seems to remain, can someone else also confirm this, thanks.

Overall this seems like a stable ROM version
[Galaxy Note II Original Android Development] tilaksidduram:
New build has been released. This build is not using the OOS hardware composer commits as it was causing many issues. Since it still work in progress, will keep testing it separately until we can make is fully workable.

Now all of the issue seen in the last build has been resolved with this new and updated build. Would recommend all to update to this new build either using Delta or by manually downloading the full zip and flashing it via the recovery.
[Galaxy Note II Original Android Development] dev_0905:
Updated to the latest 24/4 build via delta late last night. Got into a bootloop after the flashing process completed..:(.Tried wiping cache but to no avail..the boot stuck at initial screen only. Currently reverted to another Rom(which i had on my sd) as this is my only phone and i need to keep it working. Also i did not have previous lineage complete versions on my sd card..(stopped doing that since delta:))

Did not have much time to investigate as it was already late at night.please do try updating and let me know what results you have.Just keep pervious versions ready just in case...will try flashing again tonight.

Cheers..
[Galaxy Note II Original Android Development] SumeetCh:
Hi Everyone,

I , who got constant BootLoop for 20170417 build , have been able to update successfully​ to this new 20170422 build.

I did not take the Delta Update route as I anyway wanted a clean flash.

TWRP : 3.0.2 Official

GAPPS : Open Gapps Stock ( I go with Stock because I find Google Camera works flawlessly with Stock Gapps)

However, I don't think TWRP version​ or GAPPS version has to do anything with previous BootLoop issue.

Those few, who got BootLoop last time should go for the update now. I cannot confirm about the Delta Update but clean flash should work as it did for me.

I also thank [MENTION=5554397]logosA[/MENTION] for his instructions on updating the Bootloader. I did later update my Bootloader through his link by downloading 15 Some MB file. Though it did not solve the BootLoop issue, I still value his support and assistance. Please remain as supportive and informative you have been in past and ignore those negative comments.

I cannot say what changed from previous build as I have never been in previous build. I am just happy to see my Android Version as 7.1.2 :laugh:

Finally thanking [MENTION=539770]tilaksidduram[/MENTION] for the update. I don't know what you changed to fix BootLoop but whatever you did, it worked. :svetius:

Happy Flashing Guys !
[Galaxy Note II Original Android Development] tilaksidduram:
To all, nothing has changed in the device sources from the last working release 3/24 to this new release 4/22. The only change is in the lineage OS sources which has now been updated to 7.1.2.

Since I am not facing any boot loop it's making it difficult for me to debug. Have you all tried to replace the kernel/boot.img file from the working 3/24 build to see if that allow the room to boot?
[Galaxy Note II Original Android Development] sridhar_kkin:
Anyone facing wahat app video call issue? as i am facing the issue.what app videos call will not work??
[Galaxy Note II Original Android Development] cyclistefou:
For what it's worth I just flashed 20170422 over 20170417 and seems to work perfectly, no more display corruption issue with Firefox.

I didn't have any bootloop - I just used TWRP 3.1.0 to update in one go, ROM 20170417 to 20170422 and OpenGapps from 20170419 to 20170425, wiped cache & dalvik, kept data (no clean flash) and go! Did it from a full ROM download, no OpenDelta.

Seems we have a winner! Also the initial boot was shorter than usual despite the clean cache & dalvik, and my 70+ apps installed. Quite pleased. Thanks Tilak!
[Galaxy Note II Original Android Development] yamsu:
The Delta update worked for me last night. You may want to try to install the ROM manually. Might even consider a clean install as this is a very stable version, as mentioned by tilik
[Galaxy Note II Original Android Development] reis1996:
Why is the battery consumption so big in the last two updates. I'm sure it's not any external app but he ROM itself
[Galaxy Note II Original Android Development] ashokram343:
yep the rom itself consuming a lot for sure no 3rd party apps consume that much need optimisations
[Galaxy Note II Original Android Development] mbirkner:
Congrats!! The latest lineage 4/22 build fixed the bootloop problem. AWESOME!
[Galaxy Note II Original Android Development] Slippery Sam:
Had to go back to 3/24. But updated to 4/22, no problems.

Thanks Tilak. :)
[Galaxy Note II Original Android Development] Balaji Sriram:
Where is the new Rom link?
[Galaxy Note II Original Android Development] jaisulaiman.js:
go here if want full download

http://tilak.sergix44.ovh/n7100/
[Galaxy Note II Original Android Development] ishtiak02:
Downloading via delta seems to be very slow for me. I'm at 0324 downloading the 0422 one. The download speed seems to be 20kb/s. I did a few speed tests and the results were more than 20mb/s. Also downloaded some files normally and the speed was fine as well. What's the problem with Delta ?
[Galaxy Note II Original Android Development] newxdabie:
in lineage-14.1-20170422-tilak-n7100.zip everthing is ok? can someone tell me what is not working in this version?
[Galaxy Note II Original Android Development] yreham:
Well I updated today, at first I had problems with:

proximity sensor during call

Screenshots resize

All I did was to clear data for the phone app and clear cache & DALVIK and for now good...

Live display is ok

Video rec with the Google camera is ok haven't tried video from any browser or utube( video playback is good everywhere I tried)
[Galaxy Note II Original Android Development] Stud12376:
everything is normal as it was(at least no main bugs are reported till now),it is just that now it is 7.1.2 from 7.1.1,that is the only big change,
[Galaxy Note II Original Android Development] yreham:
I'll add that night mode wasn't coming on and at the same time I noticed that I didn't have vibration when I touch QS icon in the status bar.... So I go and check in settings /status bar vibration (it was on ) and has soon has I turned it off night mode kicked in and vibrate on Qs panel

Thanks
[Galaxy Note II Original Android Development] ritvikp:
One thing that I have been observing that when location settings are set to "battery saving", when WiFi is off, the phone does not get location based on GSM (that is, cell tower locations). It's only if GPS is on that phone gets the correct location. Can somebody check this and confirm.
[Galaxy Note II Original Android Development] cristobalite1983:
While trying to update to 7.1.2, is it necessary to flash gapps /bean gapps again?
[Galaxy Note II Original Android Development] yreham:
Hello, is night mode dependant of live display automatic mode?

Thank you
[Galaxy Note II Original Android Development] callahan.44:
Hi, you can also find useful information (and apps) with the following term: MAC spoof

An example of app is Pry-Fi, developed by chainfire, which is well known I think:

https://xdaforums.com/showthread.php?t=2631512
[Galaxy Note II Original Android Development] xda_joze:
I've also installed the latest version of the ROM 22/04/2017 (updated from January version w/o problems). I did the installation using TWRP 3.0.2-0 (t03g).

It works like a charm - I am very happy with the pefromance etc.. Thank you to the developers.

I have two questions

- how can I add keybaord that supports S-Pen (I've already installed SpenCommand)?

- in my case the SafetyNet/AndroidPay does not work (even before rooting). I've installed the AndroidPay using GApps Aroma (so I selected there AndroidPay).

MagiskManager says: CTS profile mismatch.

Could be problem the version of the TWRP receovery or the GApps?
[Galaxy Note II Original Android Development] Stud12376:
you are using magisk?if not the use isu,it is a simple app to hide root.https://xdaforums.com/android/apps-games/isu-simple-app-to-deactivate-activate-t3478348/page73
[Galaxy Note II Original Android Development] murtz1910:
Please bring back the customizations to the ROM .

Don't want to shift to RR just for the customization
[Galaxy Note II Original Android Development] xda_joze:
I've just reflashed my Note 2 w/ 22/04/2017 version of ROM, and w/ GAps Stock, and I did *NOT* root, but the Android Pay / SafteyNet (still) does not work.

So, it is not the problem of ROOT, but somewhere else. Maybe ROM, or how it is flashed .....
[Galaxy Note II Original Android Development] sinanaltintepe:
Incoming call

Incoming call counter starts from 10 seconds
[Galaxy Note II Original Android Development] Skull97:
The rom is pre-rooted, you can find it inside Developer Options. That means you should follow Stud12376, use isu to completely hide root.
[Galaxy Note II Original Android Development] h_maharaj:
The ROM cannot pass SafetyNet even with no root at all. Firstly, the kernel is set to permissive by default and it needs to be Enforcing to get a CTS match. Second, there are a number of prop values that need changing as well. Magisk does not work well with our device when it comes to passing SN - in all the ROMS for our device that came with Magisk, I have not seen anyone being able to pass SN. My suggestion is to completely uninstall Magisk if you have it and enable the built-in root for this ROM in Developer Options. Then download and install iSU. Open iSU and do the following: 1.) Under props tab scroll down to "Force set all known props" and select "Safe Value" 2) Under settings tab scroll down to SELinux and change "SELinux state when SU is activated" from Enforcing to Permissive. Make sure that "SELinux state when SU Deactivated" is set to Enforcing. Clear cache and data of google play store and google play services and reboot.
[Galaxy Note II Original Android Development] SumeetCh:
Try Google Handwriting Input from Playstore.

You can also set to Auto Keyboard Switch when S-Pen is out through SpenCommand
[Galaxy Note II Original Android Development] Black TH:
You may also try MyScript Stylus.

https://play.google.com/store/apps/details?id=com.visionobjects.stylusmobile.v3_2_store
[Galaxy Note II Original Android Development] stunned:
If you don't want Lineage don't install it. If you want something else, install something else.
[Galaxy Note II Original Android Development] murtz1910:
Can I change list view animation ? How to do it ?
[Galaxy Note II Original Android Development] convair990:
It's working smooth, no big issues.

And Netflix now work in Streaming :D
[Galaxy Note II Original Android Development] newxdabie:
how about camera? is it instagram, facebook camera works? video shots?:confused::confused::confused:
[Galaxy Note II Original Android Development] convair990:
Stock camera works perfectly.

Facebook and Instagram works for video and photo, but they are a bit laggy for stories.