[ZenFone 2 Android Development] techn0_3nthus1ast:
- - - - - - - - - - - - - - - -

This is for the recent or repeated questions posted in the forum: (Answers)

» Split screen: yes it is available in this build but working only for apps that supports this feature. You will see what app is supported when dragging a running app from the recent tab to a designated screen area

» Flashing a root for the build: no need to flash a root for the downloaded and flashed build, each build has its own root (like Magisk and LineageOS)

» OTA: not available... Download updates via the official download site found at the first page first post of this forum

» Flashing Requirements: always check if the bootloader is unlocked and patched to its correct bootloader version and recovery (MM bootloader and TWRP 3.0.3); download and patch the latest build version (it can be either the Magisk or the LineageOS); Gapps (latest and always patch it Every time you patch a newer version of ROM)

» Recommended actions for flashing: Fresh system flash for optimal stability (works in some cases if system anomalies found); use stock kernel to avoid possible anomalies (if you want to use a custom kernel, ask the developers which kernel is currently supported); always use GAPPs Nano build (Full also works but for better stability use Nano)

---------- Post added 13th May 2017 at 12:36 AM ---------- Previous post was 12th May 2017 at 11:57 PM ----------

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

For those who want to know how to do system logs for a certain bugs, here's a guide that I found from the "Issues of Substratum report forum" in courtesy of nicholaschum.

This is an edited version of the guide from the said forum to fit the necessary support for this forum.

The original guide is provided in this Link: https://raw.githubusercontent.com/nathanchance/Android-Tools/master/Guides/Proper_Bug_Reporting.txt

" " "

# PROPER AOSP BUG REPORTING #

Many times when using a custom ROM or kernel, you may experience an issue.

The developer may want something called a logcat or dmesg to look into this but you may not know how to do that.

There are a couple of ways to do so and that is what I am going to explain now.

This is valid for themers, ROM developers, and kernel developers.

A logcat is useful for debugging crashes or other weird behaviors with apps or themes.

A dmesg is a kernel log, detailing what each subsystem is doing.

A ramoops is the previous dmesg, which will detail why a phone force restarted.

# 1. USING AN APP #

1. Getting a logcat:

a. Download a logcat app from the Play Store (I will be using Matlog for the rest of this tutorial).

b. Open the app and grant it root permissions (if you are not rooted and do not want to be, you will need to use ADB below).

c. Clear the buffer but clicking the three dot menu and hitting clear.

d. Click on the three dot menu, choose File, then Record.

e. Duplicate your crash/issue.

f. Go back into Matlog and hit the stop button in the lower righthand corner.

g. Send the generated file to your developer/themer following the etiquette below.

2. Getting a dmesg:

a. Either download a dmesg app and follow similar steps as above OR download a terminal emulator and continue on.

b. Open your terminal emulator and type su to enter as the root user.

c. Type dmesg > /sdcard/test.log d. Send the generated file (located in the head folder of your internal storage partition) to your developer, following the etiquette below.

3. Getting a ramoops:

a. Open a file manager and navigate to /sys/fs/pstore and copy the file named console-ramoops or console-ramoops1 to your sdcard folder.

b. Send that file to your kernel developer following the etiquette below.

# 2. USING ADB #

1. Download the latest tools from Google: https://dl.google.com/android/repository/platform-tools-latest-linux.zip https://dl.google.com/android/repository/platform-tools-latest-darwin.zip https://dl.google.com/android/repository/platform-tools-latest-windows.zip

2. Extract those to a folder and move into that folder: $ cd <folder_location>

3. Plug in your device and accept the debugging prompt (turn on ADB in Settings > Developer Options if you don't see it).

4. Verify your device is recognized. $ adb devices or $ ./adb devices

5. Clear the logcat buffer. $ adb logcat -c or $ ./adb logcat -c

6. Take your log: Logcat: $ adb logcat -d > test.log or $ ./adb logcat -d > test.log dmesg: $ adb shell dmesg > test.log or $ ./adb shell dmesg > test.log

7. Give that log to the appropriate party with a proper report, following the etiquette below.

# PROPER BUG REPORTING ETIQUETTE #

1. Write in clear, concise manner what the issue is with steps to reproduce

Bad: My phone is broken, help!

Good: Whenever I open YouTube after a clean flash, it force closes.

2. Explain what you have done as much as possible.

3. Provide any scenarios/ROMs where it did work (was it working in a previous update, etc.)

4. If you are technically inclined, provide commits that are either the issue or will resolve the issue. Developers love having a solution presented for them.

# # Copyright (C) 2016-2017 Nathan Chancellor # #

This program is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by

# the Free Software Foundation, either version 3 of the License, or #

(at your option) any later version.

# # This program is distributed in the hope that it will be useful,

# but WITHOUT ANY WARRANTY; without even the implied warranty of #

MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the

# GNU General Public License for more details. #

# You should have received a copy of the GNU General Public License # along with this program. If not, see <http://www.gnu.org/licenses/> #

" " "