yashsingh1/xdaforums huggingface dataset:
[Galaxy Note Pro 12.2 Android Development] thompatry:
Hey Guys,

I know it has been awhile since I have personally posted an updated. Life has been super busy for me. Working 60 hours a week, wrapping up this job, starting a new job and moving. Don't get me wrong, I ready everyone of your posts and work with [MENTION=7694560]DGT79[/MENTION] on posting solutions, looking at logs, and making this ROM better.

With the Exynos5420 Team having a build server "Jenkins", I will no longer being announcing builds. We are working on setting a final scheduling on builds but it is looking like weekly builds on Fridays. This week, we will run builds tomorrow due to Jenkins going down for some maintenance. You can find device changes on the Exynos5420's GitHub account. We are working on a change log server but that is a few months out. If you have any questions, about this please let me know.

So a new hot topic item is root. A lot of ROM teams are moving away from baking in root (no longer having the SU binary installed) into the ROM. There is multiple reasons behind this. Some apps just will not flat out work if it detects any form of the SU binary installed. For an example Pokemon Go or TV streaming apps. Also there is concern of identity theft with the SU binary being enabled. We, as a team (Exynos5420 Team), have decided to follow this path. It should be up to the user for this risk. It is easy for you to install the SU binary if you want it though. You just need to flash a root zip after flashing the ROM. From here, you can use whatever SU program you may want such as SuperSU. You can find the SU binaries here from Lineage. I will update OP to reflect this. You can find more information about why root was removed from the ROM here.

Another thing that you may have noticed on the downloads site is there is a new ROM the Exynos5420 team is developing. It is called LiquidDeathOS. It is a ROM based off of the Exynos SOC. We have plans to expand it to all Exynos SOCs in the future. We have a few builds out for Alpha testing and it is looking promising. It is very early in development and has a lot of bugs so please be patient. What we are trying to accomplish is to focus on speed, stability, and battery life. With this new ROM, we will be using AOSP code directly from Google. There will be no CAF code involved. (If you do not know what CAF is, please Google Code Aurora.) As soon as I feel comfortable releasing a build for public consumption I will. So hang in there. It is going to be fantastic and will blow Lineage out of the water.

I think that is all I have for right now for new updates. As always keep giving the great feedback and I will keep putting out the great work. Feel free to donate me a beer or two.
[Galaxy Note Pro 12.2 Android Development] thools60:
It's so inspiring to read your words [MENTION=4817899]thompatry[/MENTION] ! Makes me soo happy, I didn't sell my tablet last year. Your attitude and dedication gives me great hope for the future. Very interesting to hear about the new road you're taking. Looking forward to try it out. Just don't kill yourself with all work. Thanks a million Tom!

Edit: LOL, Just realized....Gotta change my avatar...:laugh:
[Galaxy Note Pro 12.2 Android Development] MarkyboyUK:
Hi

Just replaced the CM 13.1 build with the LineageOS 14.1 24th Jan build (performed full wipe). Is anyone else getting the error message "unfortunately, Browser has stopped responding"? I'm getting that error message every few minutes.

Thanks for providing these builds for our tablet.
[Galaxy Note Pro 12.2 Android Development] DGT79:
Hi [MENTION=5526857]MarkyboyUK[/MENTION]

I would suggest to you that you log back into recovery and you go into wipe, then advanced wipe and you clear out the cache (Dalvik/ART) and I believe there was one more option that should be chosen as well, but just cant remember right now (Brain freeze)

Once that is done, boot back up and then go into application settings, go into your browser, click on storage option and make sure all data clearing options are chosen.

If that does not work then your browser install has become corrupted, which is not unheard of and is annoying, but you may need to either wipe the system clean again or install another browser to use.

Cheers,

David.
[Galaxy Note Pro 12.2 Android Development] MarkyboyUK:
I will try that thanks. The strange thing is that I get that error message even when I'm not using the stock Browser. I can be in a completely different screen/app and that error message will pop up.

Thanks
[Galaxy Note Pro 12.2 Android Development] doctor_pan:
Same problem here with video playback. When in HD mode, it zooms in, gets magnified, something like that.

On YouTube for instance, I have to manually set it down to 480p resolution to be able to see the whole picture...

Some other issues... I get no sound when I plug it to indicate that's charging.

The s-pen works but without popping out its menu when detached.

And, when I want to turn up or down the media volume by pressing the side buttons, usually the ring volume bar pops up and I have to scroll down, find the media bar and adjust the volume afterwards.

Thanks
[Galaxy Note Pro 12.2 Android Development] DGT79:
Hi [MENTION=1299137]doctor_pan[/MENTION]

1. Yep it is a known problem, initially I detected it in the testing stages but it was thought to be my tablet due to certain problems I have with it, we now know it is a wide spread problem, basically the video is not being scaled when the resolution changes, so something has changed since moving over to the LineageOS and the dev team are working on it

2. So what you are saying is that if you plug in the charger you are loosing sound? What happens if you toggle the sound up and down, either via the buttons or the slider??

3. Yes the contextual pop-up menues is a TouchWiz related function, we no longer have that when there is a custom ROM installed as that cannot be ported over into a custom ROM, but the pen still works and there are applications you can get that will work with the pen quite well. In developer mode you can also set the setting so when the pen is released it will vibrate the tablet and also when you put it back in

4. OK in Nougat (7.1.1) and some earlier reeases the volume control button become page contextual, meaning if you had anything on the screen that was audio based and you used the volume control, then it would adjust the volume, but if you had nothing in the foreground playing then it would revert to the ringer or the alarm volume control. So it is really based on what is on the screen as to what will happen when you press the volume button... Yep it takes some getting used to! [emoji6]

You may also notice the following:

* Random lockups, you could be using the tablet and the screen will just lock up and all the lights come on and nothing will happen, you just have to turn the tablet off... These can happen at randoms times, either frequently or infrequently depending on what rogue applicaiton is causing it

* WiFi dropping in an out, this is typically due to not having the ability to go into advance settings anymore and changing the country/region you are in so only the right channels are used, in Android 7.X.X this all changed to auto detect, which is a right pain in the ass

* When you power the tablet down, it can take an exceptionally long time to power it back up, the trick is to make sure that the power cable is not connected, if you disconnect it and hold the power button down until you see the Samsung Logo, you are back in business pretty quickly

[MENTION=4817899]thompatry[/MENTION] is aware of the issues and he has been following the feedback that is provided on here, and I do what I can to reproduce issues to help with capturing the logs, sometimes it is just simply not easy to capture the info needed to resolve a problem and it can take a while.

Moving to this custom ROM will 100% give your tablet a new lease on life, but it will come at certain costs such as bugs and missing "Samsung Only" features, of which 98% of them I didnt use anyway.

Cheers,

David.
[Galaxy Note Pro 12.2 Android Development] doctor_pan:
Hey David, thank you for your answer.

I mean no sound identification/notification that it's charging... No big deal actually, but that way when I'm plugging it to get charged, I have to open the front cover and check if it's actually charging...

Another question, and forgive my ignorance, do I have to download the nightlies and where can I find the changes made in every one of them, or are you going to announce some build that has all the above solved?

Moreover, we stick to v1awifi, or we should get some build of the v2awifi?

Thanks in advance
[Galaxy Note Pro 12.2 Android Development] DGT79:
Hi [MENTION=1299137]doctor_pan[/MENTION]

Ahhh yes I actually forgot about this one, I will investigate and see if there is a setting for this, there might be one though I am not sure... Thanks for pointing it out, may need to suggest this as a feature for [MENTION=4817899]thompatry[/MENTION] to consider

You dont have to download the weeklies at all, if the build you are running is working stable and no problem, unless there is a pressing need to upgrade you should be just fine with the one you are operating.

However I like the idea of a release note, I will check and see if there are any, if not I will raise it with [MENTION=4817899]thompatry[/MENTION] as I like this idea [emoji2]

V1 is for the SM-P900 and V2 is for the SM-T900, There might be a V3 which will be for the SM-P901 & 902 which are slight variants to the SM-P900, though I am not entirely sure what the dev team is working on that front.

Hope this helps [emoji2]

Cheers,

David.
[Galaxy Note Pro 12.2 Android Development] rpoitras:
I can't find this setting at all. Any help on where I can? Thanks.
[Galaxy Note Pro 12.2 Android Development] Yemble:
Lineage OS Multi-Window Concurrent GPS Functionality

I have used multi-window support successfully on my Note Pro tablet on a number of different Android versions, both stock Samsung and experimental CyanogenMod. Stock Samsung always allowed me to open two GPS based apps, eg. AlpineQuest and OSMAND+, allowing both to track live using the GPS concurrently. The experimental CM 13 multi-window, when it worked, also allowed the same concurrent GPS functionality.

However, now that I have implemented Lineage OS 14.1 on my tablet, with its official Android 7.1.1 multi-window support, I have noticed that only one of the two apps (activated with a tap) can acquire a GPS signal. Tapping on the other app, disables the GPS on the current app. This makes multi-window pretty useless for navigational purposes.

I have tried this with several combinations of different apps using GPS and they all behave the same, ie. only one app can access the GPS at any given time. However, I have also proved that the second app is not "frozen", since I can run a uTube video in one window, whilst tracking with the GPS in the other!

Can you tell me whether this is expected behaviour for Android 7.1.1 multi-window, or whether it is more likely to be a bug in Lineage OS, or more specifically to this ROM?
[Galaxy Note Pro 12.2 Android Development] DGT79:
Hi [MENTION=4280035]rpoitras[/MENTION]

Bad advice on my part sorry :(

You need to download "CM SPen Add-on" from the play store, then you can do as much configuration as is allowable on this platform.

Sorry for the initial bad advice, I was getting things mixed up.

Cheers,

David.

---------- Post added at 11:56 AM ---------- Previous post was at 11:53 AM ----------

Hi [MENTION=5421340]Yemble[/MENTION]

I just did a test on my Nexus 6P which is running Nougat 7.1.1 and it would seem that this is the default nature of 7.X.X and it will only allow one application to access the GPS at a time... Hmmmm Makes me wonder if this was done on purpose to try and reduce battery drain?

Though I wonder if the LineageOS team can customise that themselves, I will ask the question next time I speak to [MENTION=4817899]thompatry[/MENTION] and see if this is something he can raise up wit the entire dev team.

Cheers,

David.
[Galaxy Note Pro 12.2 Android Development] Yemble:
Cheers David,

I feared as much. Seems to me that this is something that should be configurable under the covers. The "GPS Status" app does seem to have some level of access to the GPS when run in the secondary window, alongside Alpine Quest with GPS active in the primary window. At least it seems to be able to acquire satellites without disconnecting AQ from the GPS. So there is some hope, at least, that the Lineage guys may be able to fix this.

*** EDIT ***

After some experimentation with this I now believe that I understand the issue. AQ has a setting that allows it to keep the GPS active when operating in the secondary window. This setting is "Disable in background", which needs to be unchecked (ie. enabled). So, by inference, Android 7 multi-window must treat the app running in the secondary (inactive) window as a background app, which it seems, by default, will disable the GPS connection unless told otherwise by the app itself.

So AQ (and obviously GPS Status) can handle this scenario, but other GPS apps, such as OSMAND+, Google Maps, TomTom Go Mobile, etc. cannot, since they do not have an equivalent option to keep the GPS active in background. Interestingly, TT Go Mobile does have a "Run in background" setting, but unfortunately it does not allow TT to operate in the secondary window.

So for AQ and OSMAND+ to access the GPS simultaneously, OSMAND+ MUST be in the primary (active) window. Although a PITA, at least this gives 50% of the solution.
[Galaxy Note Pro 12.2 Android Development] Ludespeed:
Anyone know exactly where to find the changelog on Exynos5420's GitHub plz?
[Galaxy Note Pro 12.2 Android Development] DaveUK:
I'm having a problem with Livedisplay. It's set to automatic but it's not switching to night mode. Am I missing something or a setting elsewhere?

Thanks Dave
[Galaxy Note Pro 12.2 Android Development] DGT79:
Hi [MENTION=238006]DaveUK[/MENTION]

Nightmode was removed by Google in 7.1.X it is actually a current oustanding issues on the Google Developers Forum, to which I am a respondant on it as well, amongst other features they have removed and we are lobbying them to bring them back.

Cheers,

David.
[Galaxy Note Pro 12.2 Android Development] DaveUK:
Thanks for the reply David.....I'll have to remember to manually switch it on at night for now!
[Galaxy Note Pro 12.2 Android Development] Logan5:
Hello all,

I have upgraded to lineage-14.1-20170124-UNOFFICIAL-v1awifi.zip, from lineage-14.1-20170110-UNOFFICIAL-v1awifi.zip. In the process, it seems I have lost the root capability. Now (in 20170124) if I select "Root access" in "Developper options", I have only "Desactivated" and "ADB only" (in french since I have configured Lineage in my native language). Is this a feature or a bug ? Is this a french configuration bug ? How may I retreive "ADB + Apps" option ?
[Galaxy Note Pro 12.2 Android Development] DaveUK:
It was explained a few posts back. Lineage doesn't come with root anymore. Either flash supersu or the su file from the extras section on the LineageOS download page.
[Galaxy Note Pro 12.2 Android Development] Yemble:
I think that it would be helpful if either a copy of, or a link to, the Lineage SU installer was included on the release page for this ROM.
[Galaxy Note Pro 12.2 Android Development] FileCity:
The new nightly ( lineage-14.1-20170130-UNOFFICIAL-v1awifi ) doesn't boot to Android.

Acts like an empty system...

Am I the only one?
[Galaxy Note Pro 12.2 Android Development] DaveUK:
Nope my one is the same. Blank screen after Samsung screen.
[Galaxy Note Pro 12.2 Android Development] cavalier90:
same here. blank screen after the Samsung screen. going back to the 24th build...
[Galaxy Note Pro 12.2 Android Development] rhricik447:
Same here...even wiped system before the flash. Thank Fate that I did a TWRP backup right before the flash...
[Galaxy Note Pro 12.2 Android Development] DGT79:
Hi All,

Since I dont test the weeklies anymore this issue was not picked up by me but I am sure [MENTION=4817899]thompatry[/MENTION] is aware of this issue now and is reporting it to the group.

When they change to update schedules like this, I dont tend to upgrade all the time unless there is a changelog that tells me exactly what is in the upgrade, personally myself I would prefer a bi-weekly or monthly update cycle to allow full and proper testing schedules before it gets released, but I am not part of the development team, I was just a happy tester when [MENTION=4817899]thompatry[/MENTION] was controlling the release cycles.

The next time I will update is when they resolve the video scaling issue, and I would strongly advise that, due to the rapid release cycles you would be best suited to do a TWRP backup before each update, but making sure you delete the previous one as they can space hogs. I am fairly certain this wont be the last time that a release will have issues.

Cheers,

David.
[Galaxy Note Pro 12.2 Android Development] shonkin:
I've been playing with LineageOS 14.1 and downloaded the latest (1/30/2016). Noticed it is about 10m smaller than the previous version(s). And after install it hung -- never even displayed the initial logo. Went back to 1/24/2016 version, and it works great. (One addtl note... the video images are, as reported earlier in thread by others, mis-sized.)

Thanks so much.
[Galaxy Note Pro 12.2 Android Development] DGT79:
Hi [MENTION=4378134]tuipro[/MENTION]

I would highly recommend you dont.

The team to my understanding are working on a P901/P902 release as there are fundamental differences between each device, and thus the bae ROM requires certain drivers and other things to ensure that it will work.

However I have no clue as to when it will be available but I will ask the question and try and get [MENTION=4817899]thompatry[/MENTION] to advise accordingly on here.

Cheers,

David.
[Galaxy Note Pro 12.2 Android Development] tuipro:
Thanks for your reply, just wondering why P900 and P901 has the same hardware but P901 has 3G, so I think it may run same Rom without 3G. Just see Nougat on P900 , P905 not for P901 *jealous* . Wait for P901 CM14 :D :D Thank you so much.

(Not good at English so forgive me if I wrong)
[Galaxy Note Pro 12.2 Android Development] risant:
What's the solution when iam using my p900 while charging the battery level decreased instead of increasing..what will i do to make the battery level increase while charging the unit while using it ? Please help
[Galaxy Note Pro 12.2 Android Development] dwl99:
I've seen the same problem on another device (Oukitel K6000 Pro) due to a widely reported software bug but if nobody else has reported it with this device it's more likely to be a charging port problem. I suggest you look inside the charging port for foreign bodies and try a different charger & cable. If that doesn't work, do a TWRP backup & try a factory reset. If that doesn't work, try flashing a stock ROM. If that doesn't work, you need a new charging port.

---------- Post added at 06:47 AM ---------- Previous post was at 06:43 AM ----------

I'm getting fed up with the laggy stock Lollipop ROM and looking to try this one. How much lower than stock are the audio volumes? Can it be fixed with ViPER4Android_FX? Any other significant issue apart from the MHL out to TV not working?

Thanks
[Galaxy Note Pro 12.2 Android Development] Yemble:
You may have a broken pin within the charging cable. Try a different one.
[Galaxy Note Pro 12.2 Android Development] thools60:
I use Dolby Atmos. Sound is perfect.
[Galaxy Note Pro 12.2 Android Development] DGT79:
Hi [MENTION=7644677]risant[/MENTION]

I have the same problem, it is actually a well established and known issue with our tablets and is widely reported. In fact you may find that if you run your tablet down to 50% it might just randomly shut down and not power back up until you plug the charger back in.

The is with the charging port pins on the motherboard itself, sometimes replacing the battery helps, but mostly you may need someone with a fine-tip solder iron to resolder the wiring on the motherboard, it is a maufacturing fault with these tablets but it does not surface itself all the time.

If you are desperate you can go on ebay and buy a new battery, but changing it can be a challenge.

Cheers,

David.
[Galaxy Note Pro 12.2 Android Development] thompatry:
Hey all. I found a typo in some of the code that caused a bad build. I apologize and I new build will be coming out tomorrow from Jenkins.
[Galaxy Note Pro 12.2 Android Development] AEnknown:
I had twrp-3.0.2-1-v1awifi installed and tried to install lineage-14.1-20170130-UNOFFICIAL-v1awifi. It just boots up into a black screen and gets no further. So i figured maybe TWRP wasn't compatible or something. So i tried installing v1awifi-recovery then reinstalling lineage-14.1-20170130-UNOFFICIAL-v1awifi but i have the same problem. it just boots up into a black screen.

any ideas?
[Galaxy Note Pro 12.2 Android Development] thools60:
Haha! Man! Try read some previous posts:laugh:
[Galaxy Note Pro 12.2 Android Development] Yemble:
Smart response... but why has this release not been pulled since it is obviously shafted?
[Galaxy Note Pro 12.2 Android Development] AEnknown:
The response is fine. I did go back and read all 23 pages and found where i messed up and installed a previous version. And if it makes him feel better to say RTFM then I'm happy to be the whipping boy.

But to your point it would be nice if a known bad version was pulled so newbs like me don't spend an hour thinking we did something wrong.
[Galaxy Note Pro 12.2 Android Development] shonkin:
Agreed. It shouldn't be assumed every person considering downloading the rom has read all these pages. And as good as this rom is (the 1/24 version, of course) it would be a pity to chase folks off by posting a bad rom (1/30 version) as the last rom....
[Galaxy Note Pro 12.2 Android Development] dwl99:
New ROM (4 Feb) works fine. Remember to re-flash supersu to keep root. Or convert it to a system app with Titanium Backup.
[Galaxy Note Pro 12.2 Android Development] Yemble:
Confirmed, but ch.13 is still not available in the UK on the 2.4GHz WiFi band :(
[Galaxy Note Pro 12.2 Android Development] shonkin:
I dirty flashed the 2/4/17 rom over the 1/24/17 and didn't experience any problems. Flashed openapps pico version along with, also flashed the root file from link on first page.

What a nice version of Android! Right off the bat, pulled up youtube and played some old psychedlic Jesus rock (Out of Darkness). *Great* volume levels. I actually had to slightly turn it down... now there's a "problem" it is nice to have.

Massive thanks to all involved, esp. [MENTION=4817899]thompatry[/MENTION].

ps: If you haven't, install thompatry's custom TWRP. One of the coolest things it does is to activate MTP (Media Transfer Protocol), which means you can hook up to your windows machine w/ TWRP running and access all your files on the tablet. Think about that... if somehow the Android install itself goes bad, you can go to recovery and retrieve all your files. VERY cool.
[Galaxy Note Pro 12.2 Android Development] dwl99:
Got a link to the thompatry custom TWRP for v1awifi? I can only find the version for v2awifi.

EDIT - the TWRP 3.0.2-1 I'm using shows up as an MTP device so I must have the custom version already. I just needed to change the driver in device manager.
[Galaxy Note Pro 12.2 Android Development] Vdonsk:
Hello! I am here for the first time and wanted to ask for help. I have installed the rom from 01/24 and 02/04, and in both was the same, lost Google Play. I installed it through Lucky Patcher. thanks in advance.

Stable work only on 01/06
[Galaxy Note Pro 12.2 Android Development] dcarvil:
You have to install Open Gapps in addition to the ROM.

http://opengapps.org/ - Thanks to the OpenGapps team!

Use the 7.1 and Arm options when downloading.
[Galaxy Note Pro 12.2 Android Development] Vdonsk:
Earned half, I can not log into your account google play and Youtube!
[Galaxy Note Pro 12.2 Android Development] shonkin:
-deleted-

---------- Post added at 04:52 PM ---------- Previous post was at 04:47 PM ----------

Why not install it without Lucky Patcher? And remember to do the standard "wipe."