MATERIAL: LandscapeLayerCoords = 1
https://puu.sh/t9WMt/a2d12c6605.jpg
I have unchecked “Static Shadows” from the landscape, built lighting and all the time i’ve had a LightmassImportanceVolume in the scene surrounding the landscape. My directional light is set to STATIC. Still the white lines 
Hey walldiv,
So it almost looks like you are using displacement or world position offset, but from looking at your material that is not the case.
You could try checking the ‘Use Full Precision’ option within your material nested in the Mobile section. Let me know if you have additional questions.
Thanks,
Here’s what it looks like in Standalone, PIE & Mobile Previewer in Source Build 4.14.2 engine:
https://puu.sh/tbarR/2eeb83509a.jpg
Device i’m using is a Motorola Razr M (4.4.2 Android)… but this displays the same on my Galaxy Note S4 (yes i know older) as well a friends Galaxy S6 phone… same output to all devices (shown below).
FWIW - the scene is FPS template FirstPersonExampleMap - where i removed the static mesh walls/floor and added a landscape with the material you’ve previously seen. For S&G’s I created a new scene with just the landscape, directional light + skybox with the material applied to the landscape… same difference.
ALSO - I did try the USE FULL PRECISION option in the material - same outcome.
I just ran another test on two different Android devices and still did not get a repro. The devices I tested were a Galaxy s5 and a Galaxy Note 10.1 2014 Edition.
On both devices, I could not get my landscape to render as you are showing. Have you checked to make sure your project is set to Mobile/Tablet for the target hardware?
Could you possibly share with me the project you are testing so I can have an identical test case on my end?
Thank you,
Here’s the project - hopefully its everythign you need (Content/Config/Intermediate & .uproject file)
The project is 4.14.2 SOURCE BUILD - i have NO PLUGINS additional from the default.
YES the project is set to Mobile/Tablet for the target hardware - with display quality set to Scalable-3d/2d
https://drive.google.com/file/d/0B31RNNqAzu-CVU5BRHVrRXl3Ylk/view?usp=sharing
I tested your project on the Samsung Galaxy S5 and an Iconia 8 Tablet, both of which rendered the landscape correctly. Since I have tested three different devices and they have all shown the correct results.
Have you set up or modified your device profiles for the mobile devices you are testing?
Do you know the texture compression setting you are using when you package? (i.e. ETC1, DXT, ASTC)
Let me know if you have additional questions.
Thank you,
I always PACKAGE as Android-All profile… with the random ETC1 or ATC trial if i have android-all fail. All three produce the same white lines.
As for device profiles - no theyre not altered… engine defaults. how am I getting this result when you get different results on the same project?
Did you PACKAGE the project? What settings?
LAUNCH does the exact same thing - only black lines instead of white.
PIE/MobilePreviewer/Standalone all look perfectly fine in the editor.
I also am installing this onto my phone via USB cord and running the .bat file on my PC - is this different from your scenario?
I have tested the issue again on another device (Samsung Galaxy S6) on Android 6.0.1 by packaging for the ‘Android All’ platform and running the Windows Batch File, and it still rendering as expected
I would try either upgrading your Android SDK on your phone, or try a different device. I am really not sure how you are getting these lines, as it has not shown up on my end at all. I did not modify any of the packaging settings and kept everything at its defaults.
Let me know if you have additional questions.
Thanks,
Perhaps I am my own problem then… because the device I have is only upgradable to 4.4.2 on my phone… i’m looking at upgrading this phone anyways… which i’ll do tonight actually. Thanks for your support Andrew - i’ll update the ticket appropriately after getting home & deploying to new device!
Andrew - tested this on my new Galaxy S7 today - it was indeed the operating system Android Version being too old… Thanks for dropping that in that last message - it was what prompted me to think of the OS in the first place… otherwise i would have casually overlooked that aspect.
Glad I could help 
