Develop Bugs

[Port] Asus PadFoneX Stock Keyboard KitKat_4.4.2

Hello all,
[port/new] Asus PadFoneX Stock Keyboard KitKat_4.4.2 by Jazzespresso
First thing first; This is your Warning!:
WARNING: BEFORE YOU DO ANYTHING ELSE, MAKE SURE YOU DO FULL NANDROID BACKUP.
DO NOT COME CRYING TO ME IF SOMETHING GOES WRONG!!!
Let me be very clear: I am Not responsible if your device explodes, your dog runs away, your spouse leaves you for your dog, the shoe factory in a third world country shuts down and
you can't get your Nike's anymore or anything else that may or may not happen after using this port to your tablet. Please make a full BACKUP! BACKUP!..so you be warned..
Click to expand...
Click to collapse
As you may know or read from tech news, Asus recently start pushing KitKat 4.4.2 (introduced new ZenUI) update to some of newest Asus devices such as Asus Padfone 2/Padfone X, and MemoPad 7, etc, here I am giving you newest Asus stock keyboard KitKat, it looks very nice - in case you bored with dark AOSP keyboard or Google Keyboard, here you can try something new refreshing!
Download
[port/new] Asus PadFoneX Stock Keyboard KitKat_4.4.2 by Jazzespresso
Screenshot
- See the attached images
Tested device and ROM
- Nexus 7 (4.4.X) - Purity ROM
- May work with other ROMs that's on KitKat (4.4.X) - it is up to you if you are adventure enough to give a shot and test it!
Install Instruction
Steps:
Did you do FULL NANDROID backup?, if not, do it now!
Download New Asus PadFoneX Stock Keyboard KitKat_4.4.2.
[*]Copy it to your tablet and flash it thru recovery (I am using philz touch recovery!)
[*]Reboot your tablet.
[*]After the reboot, go to settings --> Language & Input, and select Asus Keyboard as default - you can also configure Asus keyboard as well.
Usage:
If you want to use it in your own ROM, you only have to give proper credits, just as a way of courtesy:angel:, and you do not need ask for permission,
but it would be nice if you let me know (and a link back to this thread) if you are using it your own ROM and adding proper credits in your OP posting.

Tried a few times. Each time I use i get "unfortunately Asus Keyboard has stopped" popup.
Using paranoid saberdroid with no other kernels, tweaks or options running.

Prof Peach said:
Tried a few times. Each time I use i get "unfortunately Asus Keyboard has stopped" popup.
Using paranoid saberdroid with no other kernels, tweaks or options running.
Click to expand...
Click to collapse
Like I said in OP, I tested on Nexus 7 (4.4.X) - Purity ROM, so different ROM it may or may not work. if I were you, what I would do is unzip the package and copy the files manually one by one (making sure giving the right permission), i know this would be pain in b...tt to do so..

I might give it a try later. I like the dedicated number keys on my asus tablet and would like them on the n7 too.
Plan on installing new all f2fs recovery,rom and kernel later. Will see what that comes with.
sent from my Samsung Galaxy S5

Problem in Emoji
how fix?

[ROM][4.4.4][OCT27] UNOFFICIAL CyanogenMod 11.0 BETA V0.3

UNOFFICIAL CyanogenMod 11.0 BETA V0.3
by MisjugdedTwat a.k.a. BangL
WHAT IS THIS?
This is an UNOFFICIAL build of CM-11.0 ( CyanogenMod 11.0 ) for Huawei Mate (hwmt1_u06)
I am basically just continuing the work of others by merging and compiling, so credit goes to surdupetru, joestone, asyan4ik, mrAlmid and all coders who contributed to CyanogenMod.
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
REMEMBER
If you choose to use my unofficial build, pls don't post your issues and/or request in the official CyanogenMod forums. My builds contain unofficial code and MAY affect the official debugging process.
I do this in my free time, for free. Never forget that
Take care and do backups before flashing!
FIRST INSTALLATION (of THIS rom)
!!! BACKUP EVERYTHING !!!
Make sure your bootloader is unlocked, and install TWRP 2.8.1.0
Download the ROM, and put it on your SD-card
Download Gapps, and put it on your SD-card (optional)
Boot into TWRP
Do a FULL WIPE (system, data, cache, dalvik) ! - you can try to keep data, but it will most likely fail booting.
Install the ROM, using TWRP
Install the Gapps, using TWRP (optional)
Reboot to system
UPDATE INSTALL (when you already have another version of this rom installed)
Download the ROM, and put it on your SD-card
Download Gapps, and put it on your SD-card (optional)
Boot to recovery
Wipe system
Install the ROM, using TWRP
Wipe cache & dalvik
Install the Gapps, using TWRP (optional)
Reboot to system
LATEST CHANGES
V0.3
V0.2
CM SOURCES MERGED UP TO:
Change 110843 - manifest: Remove vendor/cyngn repo
http://review.cyanogenmod.org/#/c/110843/
INCLUDED KERNEL
whirlwind.kernel
KNOWN BUGS
a2dp is not running perfect, but it runs. - sometimes.
Nfc is probably not working at all, not sure.
GPS acts a little weird sometimes.
Video compression results in pure trash.
Clock might get desynced
DOWNLOADS
Please note this build is for bug-hunting purposes only, yet! (Plain CM is boring anyways)
I am just starting to build for this device and with this build am currently trying to get a stable basis for other roms.
My goal is having a fully working code-base for any AOKP-based 4.4 ROM.
So PLEASE join the testing phase, try every ****ing functionality on your phone and report the results here, so i know whats done and what needs to be done. Thanks!
Rom
https://www.dropbox.com/sh/gd42e500zsrl7e0/AACjh4We8ZjULayjWFL7Y1lla?dl=0
Gapps
Use any "ARM - 4.4" package from open gapps (i recommend the nano variant)
Bootloader/Recovery
If you are still on a locked bootloader, having an unrooted stock rom, or an old twrp installed, use this updated unlock/recovery suite for windows and linux:
TWRP 2.8.1.0
SOURCE CODE
https://github.com/hwmt1-u06/android

NOTICE:
I removed the asound codecs, which increases the sound volume dramatically. I wanna enjoy my music loud, when i'm sitting in the bus!
This kinda ****s up the speaker, since its too loud now, which causes clipping.
I use the Equalizier in CM's DSP Manager to reduce the speaker volume (by turning all levels around -6db)
Having loud volume, and the ability to decrase it, is better than having silence and no ability to increase it, right? Thats like going to the hair stylist and wanting longer hair.

Cool, thanks for your effort!
Will give it a try when I feel I have enough time

UPDATE V0.2
CHANGES
Fixed rebooting to recovery
Changed some default system props related to adb and root
Thats it, any bugs?
Otherwise i will now focus on porting more aokp roms, building twrp and a maybe a kernel.

Hi,
is NFC functional in this ROM?
(In B331 is not.)
Stutter bluetooth audio sometimes?
(In B331 there is)

sijben said:
Hi,
is NFC functional in this ROM?
(In B331 is not.)
Stutter bluetooth audio sometimes?
(In B331 there is)
Click to expand...
Click to collapse
Its probably both messed up as well in this ROM, i don't have the hardware to test those functions. Maybe you can tell me

Misjudged, in your instructions I see a clear distinction between a "first time install" and an "update install".
What is the difference between the two?
I mean, I get an idea what it is about but do not feel confident to base a decision on.

SvenHee said:
Misjudged, in your instructions I see a clear distinction between a "first time install" and an "update install".
What is the difference between the two?
I mean, I get an idea what it is about but do not feel confident to base a decision on.
Click to expand...
Click to collapse
its meant like this:
- first install the first installation of THIS rom
- update install is when you already have this rom installed (e.g. v0.1) and you wanna update to another version of this rom (e.g. v0.2), and keep your apps, data and settings.
and remember to backup first!
EDIT: Updated instructions in first post

Very good, thanks!

Okay been giving this CM11 ROM a test drive this week on my Mate. My Mate is the 1 gig version and I have a bad case of call ? screen delay on this ROM. Is there a patch that can help with this? I will admit though that I probably expect too much from my poor little Mate because I have tons of apps on it
I must say though your ROM is the smoothest running ? CM11 ROM I've tried. Good job.
If I could only get rid of or just reduce the call screen delay I could run ? this as my daily driver. But this week I just missed too many calls due to the call ? screen delay.
Keep up the good work. You can depend on me to test any ROMs you put out. :thumbup:
sent from my MT1-U06 using Tapatalk 2

Flashed it on my P6, replaced the kernel with the AK cm kernel for P6 and switched to ART. Very smooth rom, havent seen any issues or bugs yet except the wifi dropping, which does not mean much as it instantly reconnects. Good job.
Edit: Don't know about the ascend Mate but on the P6 OTG is fully functional and stable.

after 24 hours of being my phone:
Bluetooth audio gave me a full cd instead of less than one song, gps works.
I only miss pie control, but that in not CM if I read correctly.
Keep up the good work!
Would love to try your version of carbon rom, if you get round to that

Thanks for tests your reports, guys!
let's see..
SvenHee said:
after 24 hours of being my phone:
Bluetooth audio gave me a full cd instead of less than one song, gps works.
I only miss pie control, but that in not CM if I read correctly.
Keep up the good work!
Would love to try your version of carbon rom, if you get round to that
Click to expand...
Click to collapse
Wait.. what? Are you telling me a2dp is working perfectly fine? I did not expect that at all!
Yeah, i will port more ROMs, but first i had to have my own kernel (see below) :fingers-crossed:
blankulus said:
Okay been giving this CM11 ROM a test drive this week on my Mate. My Mate is the 1 gig version and I have a bad case of call ? screen delay on this ROM. Is there a patch that can help with this? I will admit though that I probably expect too much from my poor little Mate because I have tons of apps on it
I must say though your ROM is the smoothest running ? CM11 ROM I've tried. Good job.
If I could only get rid of or just reduce the call screen delay I could run ? this as my daily driver. But this week I just missed too many calls due to the call ? screen delay.
Keep up the good work. You can depend on me to test any ROMs you put out. :thumbup:
sent from my MT1-U06 using Tapatalk 2
Click to expand...
Click to collapse
ive already patched in a tweak to help that problem atleast a little, i am not sure if theres more i can do.
as far as i know it's a well known jb/kk-problem on devices with very low ram... i had an LG O2x, which hab like 500MB ram or something... it was pretty much ununsable when someone called. i remember something like they started to remove the incallUI from the permanently-open list - if you know what i mean. and that's why it's causing this problem.
i don't really have this problem at all, to be honest. so maybe you can help it by removing some service-apps.. or maybe theres some app to force another app to stay loaded? i don't know, just an idea.
tauio111 said:
Flashed it on my P6, replaced the kernel with the AK cm kernel for P6 and switched to ART. Very smooth rom, havent seen any issues or bugs yet except the wifi dropping, which does not mean much as it instantly reconnects. Good job.
Edit: Don't know about the ascend Mate but on the P6 OTG is fully functional and stable.
Click to expand...
Click to collapse
arg... P6? different kernel?
so your report doesnt really help me, since i dont even know what the exact differences between the MT1 and the P6 are, and most off the hardware related stuff is kernel related!
Good to see it's running well for you, though.
But thank you very much, srsly.
btw: you are having the wifi dropping too? thats weird, i was sure thats a kernel & /system/lib/modules thing.
...which is why i focused on kernel building for now. It seems like some people are smashing any modules they can find at their kernel until it works somehow. - this is a huge mistake. kernel modules in /system/lib/modules MUST be built against the exakt same kernel, they will be used on.
To be sure to have that clean, i felt like i need to get into that stuff as well. - and i actually just succeded like 30 minutes ago.
I will try out some things on this build, and when everything seems stable to me, i will even release my own kernel, which will always be shipped with the correct modules
But that will be HIGHLY experimental, and for the MT1 only!

Only had minor hiccups when browsing the internet at the same time.
Now testing the second session of music
Edit: A few more hiccups in one session, pretty good play a bit later. Very usable.

Installed and so far its very smooth

Maps thinks I am at a different road every now and then, causing strange new rout options. But this corrects quickly.
Can not get navigation started by clicking address in calendar appointment, then maps keeps restarting. Had the same thing with Mr. Amids carbon rom.
It does start from clicking icon and copy/paste the address.

SvenHee said:
Maps thinks I am at a different road every now and then, causing strange new rout options. But this corrects quickly.
Can not get navigation started by clicking address in calendar appointment, then maps keeps restarting. Had the same thing with Mr. Amids carbon rom.
It does start from clicking icon and copy/paste the address.
Click to expand...
Click to collapse
interesting.. is there any cm based rom, where you dont have that problem?

Carbon was the only 4.4.4 rom by Mr. Amid I got working, I know now (with your explanation) that I should have wiped data too when flashing a new rom.
I can not recall having the Maps problem with 4.2 roms.

UPDATE V0.3
CHANGES
Fixed /data/share paths in frameworks-base and system-core
System-props and init.rc script optimization
Using wpa_supplicant_8_ti instead of wpa_supplicant_8
Prebuilt B331 kernel and kernel-modules removed
Built whirlwind.kernel #2 from sources
Built wifi modules against whirlwind.kernel #2
Is a2dp, gps and wifi better with this build, or maybe even worse?

Will I be able to upload videos to instagram ?

[ROM] [6.0.x] Official CyanogenMod 13.0 Nightly Builds Oppo N3

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 13.0 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe system, data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Broken Features / Known Issues
- fingerprint sensor will likely never work in CM
- camera is less features than stock colorOS
- ?
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Please also provide instructions to reproduce your issue.
Downloads
CyanogenMod 13.0 for Oppo N3: ROM @http://get.cm/?device=n3
Recovery Links
TWRP
Google apps addon:
Recommend GAPPS but there's plenty of options here.
XDA:DevDB Information
Cyanogenmod 13.0 Oppo N3, ROM for the Oppo N3
Contributors
jrior001
Source Code: https://github.com/cyanogenmod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Current Beta Version: Nightly
Created 2016-02-22
Last Updated 2016-03-01

Hey there bud. Great to know that there's still people out there working for the N3. This is a hopeless device, not even Lollipop support from Oppo despite being a flagship device once, so thanks a lot.
I'm currently on CM12.1 although the camera doesn't perform as well as on ColorOS and the fingerprint sensor doesn't work either, although pressing the button on the sensor does brightness up the screen and turn the capacitive buttons' light on when pressed.
Anyway, I'd love to try CM 13.0, but I'd want to know the major bugs on this release from you. Also, do let me know if I can be of any help. This is a beast of a device, let down by the abysmal software from Oppo. Will surely give it a shot if the bugs are bearable Thanks again for working on the N3!

SufiSam said:
Hey there bud. Great to know that there's still people out there working for the N3. This is a hopeless device, not even Lollipop support from Oppo despite being a flagship device once, so thanks a lot.
I'm currently on CM12.1 although the camera doesn't perform as well as on ColorOS and the fingerprint sensor doesn't work either, although pressing the button on the sensor does brightness up the screen and turn the capacitive buttons' light on when pressed.
Anyway, I'd love to try CM 13.0, but I'd want to know the major bugs on this release from you. Also, do let me know if I can be of any help. This is a beast of a device, let down by the abysmal software from Oppo. Will surely give it a shot if the bugs are bearable Thanks again for working on the N3!
Click to expand...
Click to collapse
Fingerprint/camera are mostly the same issues from cm12.1. I have not attempted device encryption yet, and I doubt our available twrp build would be able to decrypt. Other than that this build is pretty much fully functional. I have had a few intermittent issues with audio and touchscreen wakeup but mid kernel rebase so that will all get cleaned up shortly. I've actually been running this for 2 months trying to get camera working (just fixed a few days ago).

jrior001 said:
Fingerprint/camera are mostly the same issues from cm12.1. I have not attempted device encryption yet, and I doubt our available twrp build would be able to decrypt. Other than that this build is pretty much fully functional. I have had a few intermittent issues with audio and touchscreen wakeup but mid kernel rebase so that will all get cleaned up shortly. I've actually been running this for 2 months trying to get camera working (just fixed a few days ago).
Click to expand...
Click to collapse
Okay, great to hear. I've done my bit of research on the N3's fingerprint sensor and I'm not sure if it would be helpful in trying to fix it or not, but do let me know if you'd want to hear about it

good to see that the device still gets cm13. Thanks for your great work.
you can check also the source for Lenovo ZUK Z1 they have the same processor and it has FS too.

How about the battery life? I am getting a worst battery life on CM 12.1
Sent from my m2 using Tapatalk

cheeze.keyk said:
good to see that the device still gets cm13. Thanks for your great work.
you can check also the source for Lenovo ZUK Z1 they have the same processor and it has FS too.
Click to expand...
Click to collapse
Both devices may have the same processor, but I doubt they use the same fingerprint sensor. The N3 uses the FPC1021, also used in the Gionee E8 and maybe the Lenovo Vibe X3 too. I wish we could somehow help OP in finding the sources/drivers for the FPC1021 fingerprint sensor

Okay, here's something very weird that happened yesterday. I started the camera by pressing the power button twice and the phone shut down by itself and then reboot. The phone was stuck in a bootloop. I could access TWRP, and I tried everything, right from factory resetting the phone to reflashing both, CM13 and CM12.1. Absolutely nothing helped, as the phone just couldn't go beyond the Oppo logo.
I had to install the stock Oppo recovery again in Fastboot mode, wipe the internal storage and reflash a boring ColorOS stock rom again. I'm still not sure what happened. 5 years of flashing experience and I've never known any simple system app function that could soft brick a phone so badly.
Looking forward to hearing from OP about this before I can get back to CM13, it would be great. Btw, CM13 was absolutely fantastic in the 20 minutes I could use it for before ending up with that vicious brick. Really looking forward to a more stable version. Keep up the great work, dev! Thanks!

SufiSam said:
Okay, here's something very weird that happened yesterday. I started the camera by pressing the power button twice and the phone shut down by itself and then reboot. The phone was stuck in a bootloop. I could access TWRP, and I tried everything, right from factory resetting the phone to reflashing both, CM13 and CM12.1. Absolutely nothing helped, as the phone just couldn't go beyond the Oppo logo.
I had to install the stock Oppo recovery again in Fastboot mode, wipe the internal storage and reflash a boring ColorOS stock rom again. I'm still not sure what happened. 5 years of flashing experience and I've never known any simple system app function that could soft brick a phone so badly.
Looking forward to hearing from OP about this before I can get back to CM13, it would be great. Btw, CM13 was absolutely fantastic in the 20 minutes I could use it for before ending up with that vicious brick. Really looking forward to a more stable version. Keep up the great work, dev! Thanks!
Click to expand...
Click to collapse
Not happy to hear this but I've also never experienced it. Please keep in mind we are working off a massive kernel rebase to support 6.0 and things may not be ideal at times. I have been running 6.0 on N3 for a few months now but only in the last week have I had the camera functional.
Also fwiw the stock colorOS rom should flash in the newer TWRP builds, I made sure that worked myself.
Without some kind of log I'm at a loss as to what happened here. If any randomish reboot happens I need /proc/last_kmsg to have any chance of deciphering why it rebooted.

Thanks a lot for your response, bud. The N3 is my daily driver, so I couldn't mess around too much. I waited for a bit, then flashed stock ColorOS right away, because I need the phone, especially on this busy weekend. I think I was using an older version of TWRP, so I'm not sure whether that could be a problem either. I'm going to try and get back on CM 13 sometime today, and see how it goes this time.
Once again, thanks a ton for working on this phone. I thought it was completely dead. Oppo are really bad at supporting any devices except the Find 7. Let me know if I can help in any way, I'd be more than happy to be of any help

This may be a silly question Jason, but I see all these new builds popping up on your website for the N3, but I can't seem to find any kind of a nightly changelog on either cmxlog.com or even review.cyanogenmod.org. Is there any way we could perhaps see what changes are being made?

SufiSam said:
This may be a silly question Jason, but I see all these new builds popping up on your website for the N3, but I can't seem to find any kind of a nightly changelog on either cmxlog.com or even review.cyanogenmod.org. Is there any way we could perhaps see what changes are being made?
Click to expand...
Click to collapse
Ah, I never updated the thread here. I got official nightlies turned on so fresh builds should be hitting http://get.cm/?device=n3 now. Change log will be back w/ota in the built in updater.

jrior001 said:
Ah, I never updated the thread here. I got official nightlies turned on so fresh builds should be hitting http://get.cm/?device=n3 now. Change log will be back w/ota in the built in updater.
Click to expand...
Click to collapse
Thanks for this, bud! You're the best!

SufiSam said:
the phone shut down by itself and then reboot. The phone was stuck in a bootloop.
Click to expand...
Click to collapse
Got the same problem here. There was CM12 before, and ColorOS. But after flashing CM13 and that error, i cant flash any AOSP roms. Just ColorOS. And got permanent wifi and proximity sensor issues. They doesn't work anymore, even after flashing stock clean chinese ColorOs rom. Don't even know, what to do...

Got the same problem, can't boot up now nor flashing cm 12.1 back, only coloros works now and without wifi. We need a fix as i can't stand the poor coloros.
---------- Post added at 01:22 PM ---------- Previous post was at 01:16 PM ----------
So guys I've found a temporary wifi fix, you need to copy some files from the coloros zip to the /persist folder using root Explorer, works for me, but still not a permanent fix.

Sounds good) What files?
And check please all sensors, such as proximity, light, and others. there are a lot of programms in google play for cheking that.

To get wifi working, follow these steps :
**YOU NEED A ROOT **
1. Extract this file to get the 4 needed files.
2. Using root Explorer , copy the extracted files to /persist folder in root directory.
3. Select all the files after copying and select permission.
4. Make the permissions as rw-r-r--
5. Try to switch on wifi multiple times until it works.
**IMPORTANT**
Rebooting the device will deletes the files from /persist folder and wifi will not work again until you repeat the steps , don't know why, but it is a temporary fix and works with no issues.

Man, you are the best! And what about sensors?
And where did you find this solution?

hussaination said:
To get wifi working, follow these steps :
**YOU NEED A ROOT **
1. Extract this file to get the 4 needed files.
2. Using root Explorer , copy the extracted files to /persist folder in root directory.
3. Select all the files after copying and select permission.
4. Make the permissions as rw-r-r--
5. Try to switch on wifi multiple times until it works.
**IMPORTANT**
Rebooting the device will deletes the files from /persist folder and wifi will not work again until you repeat the steps , don't know why, but it is a temporary fix and works with no issues.
Click to expand...
Click to collapse
Don.Archon said:
Man, you are the best! And what about sensors?
And where did you find this solution?
Click to expand...
Click to collapse
Are you guys saying wifi and sensors were not working for you? If so this is important and i need logs from a clean boot. These have always worked fine for me on these builds.

How to make this logs? i know nothing in programming (

Problems with Lineage OS

Hi, I'm not sure if it's the right section where to post such a thread but I didn't found a better one for my problem.
I flashed lineage-14.1-20170213-nightly-find7s-signed.zip on my rooted Find 7 (2k version so Find 7s) with TWRP following all the standard steps (full wipe, ROM and gapps install, wipe cache/dalvik and than reboot).
Than when the ROM flash was finished (it took not as much as I thought) I rebooted and my screen become white with a grey OPPO logo in the middle and purple "powered by android" at the bottom (the usual power up screen but with inverted colors) and when I touch the screen it makes quick flashes with flashing black horizontal lines and it keeps being stuck in that way for minutes (way too much and it keeps doing that also after many reboots). The only way to recover the phone is to flash again Color OS (Android 5.0).
So i was wondering what's the problem with that ROM? How can i upgrade my old Android 5.0 to a newer 6.x or 7.x? Is there any rock solid ROM compatible with my F7s that I can flas with no such problems ?
Thankyou all for help!

OmniROM 6 is a mature and solid daily driver with the option to try OmniROM 7 which is still being improved regularly. Arguably the best ROM for Find 7.

RobboW said:
OmniROM 6 is a mature and solid daily driver with the option to try OmniROM 7 which is still being improved regularly. Arguably the best ROM for Find 7.
Click to expand...
Click to collapse
It also has LVM support which allows you to merge your partitions so you will have more than 3gb of space for apps.
I've been running it for months, there are a few things that I miss from previous roms but is very stable and since this phone is getting old the ROM choices are getting slim. It's also the only one I can find that still supports LVM.

RobboW said:
OmniROM 6 is a mature and solid daily driver with the option to try OmniROM 7 which is still being improved regularly. Arguably the best ROM for Find 7.
Click to expand...
Click to collapse
_Clint-Beastwood_ said:
It also has LVM support which allows you to merge your partitions so you will have more than 3gb of space for apps.
I've been running it for months, there are a few things that I miss from previous roms but is very stable and since this phone is getting old the ROM choices are getting slim. It's also the only one I can find that still supports LVM.
Click to expand...
Click to collapse
Thankyou both for helping me I found a list of omnirom ROMs in this thread https://forum.xda-developers.com/find-7/orig-development/omni-testbuilds-7a-7s-t3237065 , can i choose one of the last 6.0.1 to be sure it will work or can I trust the 7.1.1 updates?

You can trust both! And im not a hyper flashholic....

Just another few questions, LVM means that i can unify partitions in order to have more than 3 GB on device memory, right? I found that thread https://forum.xda-developers.com/showpost.php?p=55187001&postcount=558 is it better to use the .iso or the .zip to apply LVM? And when do I have to apply the LVM setup, before or after flashing the new ROM/Gapps?
Thanks again

Frank_Z said:
Just another few questions, LVM means that i can unify partitions in order to have more than 3 GB on device memory, right? I found that thread https://forum.xda-developers.com/showpost.php?p=55187001&postcount=558 is it better to use the .iso or the .zip to apply LVM? And when do I have to apply the LVM setup, before or after flashing the new ROM/Gapps?
Thanks again
Click to expand...
Click to collapse
Flash the setuplvm zip file in twrp BEFORE flashing ROM and gapps

Guys, thanks to all of you! Really, you all made my day with all your advices
With past ROMs i was desperate because none of them worked but now i got rooted android 7.1.1 with merged partitions on my dear Find 7 so thanks again for helping me!

[TOOL] Fix Freezed Screen/Camera Issue With Unlocked Bootloader by nheolinkin

All THESE TOOLS ARE MADE BY ME FOR THE PURPOSE OF FIXING FREEZED SCREEN AND NOT WORKING CAMERA ISSUE BUT NOT SERVING ANYONE HERE. USE IT OR NOT, IT"S YOUR CHOICE.​
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in these TOOLs
* before using them! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
=====================
= FREEZED SCREEN ISSUE =
=====================​WARNING
Do not use Automatic Tool more than once for each kernel (boot image).
If you did that by accident and device can not boot. Just reflash original kernel then use the tool again.
HOW TO UNLOCK BOOTLOADER WITHOUT FREEZED SCREEN?
- Unlock Bootloader Tool (2 recommended options: 1-1-5 or 1-5-5)
- Root your device.
- Enable USB Debugging.
- Extract and run this tool (Download) - READ INSTRUCTION WHEN TOOL IS RUNNING.
- From your device, using any File Explorer to copy cmdline file from /sdcard to /d/osip
- Reboot device.
CHECK IF TWEAK IS APPLIED OR NOT
- Use any File Explorer to get into root folder
- Check if value in /proc/cmdline has "... intel_idle.max_cstate ..."
READ THIS OR I WILL NOT CARE WHATEVER YOU COMMENT HERE
- Who used my tool and get thing fixed, help the others if you can.
- If you tried all options of unlocking bootloader and applied tweak but your devices still get freezed and automaticly reboot, get last_kmsg by using Kernel Auditor (right after reboot) then post in the comment section.
- Just like above but if it's freezed without reboot then I'm sorry that I can't do anything for now.
OPTIONAL
- TWRP-3.0-B-5.0 flashable zip with tweak applied. Freezing is not occured much on TWRP but I still make this one for personal and for people wanna get rid of freezing when flashing something in TWRP. (Download)
Thanks to @X AnwarMov
- TWRP-3.1.1-0 fastboot image with tweak applied. (Download)
Thanks to @narueon
WORK UPDATE (05/09/2017)
05/09/2017
- Re-enable kernel watchdog
15/07/2017
- Tool now can be used in any rom.
09/07/2017
- Fix cmdline code.
- Remove init.d file since all issues are fixed by cmdline.
08/07/2017
- Remove "processor.max_cstate" parameter for battery issue
07/07/2017
- Just finished some works and tests
05/07/2017
- Add more boot options to cmdline.
- Try to complete the tool.
- Add 3.87 kernel for stock users.
- Out of data, may be no more update for while
04/07/2017
- Remove "disable_kernel_watchdog" parameter to kernel cmdlines.
- Add "acpi=off" boot option.
- Disable thermal charging limit.
30/06/2017
- Start testing in public
=========================
= CAMERA NOT FOUND ISSUE =
=========================​NOT FIXED YET
For anyone is facing this issue, I will keep asking for stuff here when I have any idea
Stay tuned for any update in this post
And also remember, I don't have device with this issue for test so don't ask why it takes so long to fix.
REQUEST
Get 2 different dmesg files then send me via private message or telegram.
- One right after boot
- And another after open any camera app
You can take dmesg file by using Lspeed, Kernel Auditor or any method that you've already known
TROUBLESHOOT
1. Module Problem
HM2056 module can not be used. This is one of camera modules.
Credits
@nheolinkin
@juyel92
@X AnwarMov
@narueon
And all testers.
MODIFYING THESE TOOLS IS DENIED / REDISTRIBUTING MY TOOLS AT OTHER FILE HOSTING SERVICES IS DENIED / REPOSTING THESE TOOLS AT OTHER WEBSITES WITHOUT PROPER CREDITS, BLOATED WITH ADS OR WITH DOWNLOAD PROTECTION/REGISTER-TO-DOWNLOAD IS DENIED / IF YOU IGNORE IT, I WILL ASK MODERATOR TO DELETE YOUR THREAD OR I WILL DO A FORMAL DMCA TAKEDOWN.
================
= INFORMATIONS =
================
[TOOL] Fix Freezed Screen/Camera Issue With Unlocked Bootloader for Zenfone 5
Contributors
@nheolinkin
Status: In Progress
Last updated: 2017/09/05

RESERVE

Wow, Thanks im really happy after reading this stuff, it helps me to understand why freezing happens and how fix part of this problem, you have my "thanks" anyway i have question, why unlock doesnt couse any problems on kitkat based firmware?

kihope12 said:
Wow, Thanks im really happy after reading this stuff, it helps me to understand why freezing happens and how fix part of this problem, you have my "thanks" anyway i have question, why unlock doesnt couse any problems on kitkat based firmware?
Click to expand...
Click to collapse
You mean "unlock" by unofficial tool or asus's app? If it's unofficial tool does not cause any problem in kitkat base but not lollipop then I need to talk to that "guy"

nheolinkin said:
You mean "unlock" by unofficial tool or asus's app? If it's unofficial tool does not cause any problem in kitkat base but not lollipop then I need to talk to that "guy"
Click to expand...
Click to collapse
Im sure for 99% unofficial unlock doesnt couse freezing on 4.4, i used official only one time, but unofficial is just flashing ifwi and dnx from officiall firmware.

kihope12 said:
Im sure for 99% unofficial unlock doesnt couse freezing on 4.4, i used official only one time, but unofficial is just flashing ifwi and dnx from officiall firmware.
Click to expand...
Click to collapse
The fact is that if unofficial unlock doesn't cause freezing on 4.4 then it won't cause freezing on any base.
And the official one, pretty the same except that it can detect your unsupported devices if you're using later kitkat rom.
For example, If anyone buy a new device with 2.20.40.13 manufactured rom, official tool will tell you exactly that your device is supported or not. But if you downgrade to any rom earlier than that then it won't, because it just simply can not realize your new device with new mainboard and stuff inside.

nheolinkin said:
The fact is that if unofficial unlock doesn't cause freezing on 4.4 then it won't cause freezing on any base.
And the official one, pretty the same except that it can detect your unsupported devices if you're using later kitkat rom.
For example, If anyone buy a new device with 2.20.40.13 manufactured rom, official tool will tell you exactly that your device is supported or not. But if you downgrade to any rom earlier than that then it won't, because it just simply can not realize your new device with new mainboard and stuff inside.
Click to expand...
Click to collapse
But why on 4.4 it doesnt freez, and on 5.0 up it does?

kihope12 said:
But why on 4.4 it doesnt freez, and on 5.0 up it does?
Click to expand...
Click to collapse
Which tool did you use? How long do you use kitkat to ensure that it won't freeze?

nheolinkin said:
Which tool did you use? How long do you use kitkat to ensure that it won't freeze?
Click to expand...
Click to collapse
I used both, official at first time then I used unofficial beacuse official doesnt works at .44, kitkat i use very long timw ago. Or only for while when i reflashing whole system.

kihope12 said:
I used both, official at first time then I used unofficial beacuse official doesnt works at .44, kitkat i use very long timw ago. Or only for while when i reflashing whole system.
Click to expand...
Click to collapse
My bad then, I forgot to mention fastboot of later base than 2.21.40.44 does not allow flasing ifwi so official tool's not supposed to work proberly.
And about your case that it's just freezed in 5.0 instead of kitkat, it's hard to say but it could be caused of 2 reason:
- not compatitive bootloader (dnx) version. Because after all if.bin file and also official tool are made for kitkat but not lollipop.
- if frequency of freezing is low, then it could be something else that I can not say for sure without logs.
Conclusion: Can unlock bootloader or not, it's based on the result we got from kitkat rom. That's why I do not mention 5.0 here.

thanks to you im so happy u made this thread..
anyway i had some question...
we know that disabling 2 cpu core will fix this freeze issue..but with a cost of performance and broken camera
and... "sometimes" if i play a game especially the heavy one,ex:vainglory... the freeze is gone
i wobder why that things can prevent the phone to freeze??

nheolinkin said:
My bad then, I forgot to mention fastboot of later base than 2.21.40.44 does not allow flasing ifwi so official tool's not supposed to work proberly.
And about your case that it's just freezed in 5.0 instead of kitkat, it's hard to say but it could be caused of 2 reason:
- not compatitive bootloader (dnx) version. Because after all if.bin file and also official tool are made for kitkat but not lollipop.
- if frequency of freezing is low, then it could be something else that I can not say for sure without logs.
Conclusion: Can unlock bootloader or not, it's based on the result we got from kitkat rom. That's why I do not mention 5.0 here.
Click to expand...
Click to collapse
I think it is first problem what you mentioned, anyway why asus didnt make if.bin for 5.0 it is impossiblle or it is beacuse they are lazy as moct of time?

andyfahri7 said:
thanks to you im so happy u made this thread..
anyway i had some question...
we know that disabling 2 cpu core will fix this freeze issue..but with a cost of performance and broken camera
and... "sometimes" if i play a game especially the heavy one,ex:vainglory... the freeze is gone
i wobder why that things can prevent the phone to freeze??
Click to expand...
Click to collapse
Disable 2 cores won't fix freeze issue but just decrease frequency of it. You don't need to throw away performance and camera for that.
And yes, some game will not cause freeze when you play. If I'm not wrong, how your figure touch the screen in game could be the reason. For clearly, it won't be freezed or least freeze when you play a game that one or more than one figure touch the screen continuously when playing.
VainGlory is an Moba game which is perhaps required 1 figure touching continously to move characters right?

kihope12 said:
I think it is first problem what you mentioned, anyway why asus didnt make if.bin for 5.0 it is impossiblle or it is beacuse they are lazy as moct of time?
Click to expand...
Click to collapse
They are not paid for doing that

nheolinkin said:
Disable 2 cores won't fix freeze issue but just decrease frequency of it. You don't need to throw away performance and camera for that.
And yes, some game will not cause freeze when you play. If I'm not wrong, how your figure touch the screen in game could be the reason. For clearly, it won't be freezed or least freeze when you play a game that one or more than one figure touch the screen continuously when playing.
VainGlory is an Moba game which is perhaps required 1 figure touching continously to move characters right?
Click to expand...
Click to collapse
yepp... ur right sir,now i understand why freeze happens more often on menus than when playing the match

andyfahri7 said:
yepp... ur right sir,now i understand why freeze happens more often on menus than when playing the match
Click to expand...
Click to collapse
my phone doesnt freez when i play games but it freez a lot when i watching youtube and doesnt touch touchscreen while..

AUTOMATIC TOOL WAS RELEASED
Take a look at the 2nd post for detail

nheolinkin said:
AUTOMATIC TOOL WAS RELEASED
Take a look at the 2nd post for detail
Click to expand...
Click to collapse
Hello there , saw about kernel panic . I too experience sometime reboot due to kernel panic . Then i disable kernel panic and everything is fine for me. You got any idea to fix ? And i am totally confident its bug in kernel not in bootloader

Boomshiva said:
Hello there , saw about kernel panic . I too experience sometime reboot due to kernel panic . Then i disable kernel panic and everything is fine for me. You got any idea to fix ? And i am totally confident its bug in kernel not in bootloader
Click to expand...
Click to collapse
It depends on last_kmsg you get after panic. There are quite a lot reason for kernel panic that I can not say for sure.

nheolinkin said:
AUTOMATIC TOOL WAS RELEASED
Take a look at the 2nd post for detail
Click to expand...
Click to collapse
What about kernels for 6.0 and 7.1.x cm and aosp based?