How to activare Knock On? - Moto G 2015 Q&A, Help & Troubleshooting

Hello, i reality want to activate the LG function Knock on on my new motorola moto g 3.
How I can enable it? I'm on 5.1.1 stock lollipop because I've read that it works better than android 6, I read too that this function need an custom kernel, I prefer to keep my stock rom, is really working amazing, are a way to use this option without touch the kernel?
I want the real knock on, that works with the screen off like LG phones, I've tried some apps but they keep the screen on or the proximity sensor on and this drains the battery obviously, so that's not what I'm looking for, my device is rooted.
Thanks.

migueldvp said:
Hello, i reality want to activate the LG function Knock on on my new motorola moto g 3.
How I can enable it? I'm on 5.1.1 stock lollipop because I've read that it works better than android 6, I read too that this function need an custom kernel, I prefer to keep my stock rom, is really working amazing, are a way to use this option without touch the kernel?
I want the real knock on, that works with the screen off like LG phones, I've tried some apps but they keep the screen on or the proximity sensor on and this drains the battery obviously, so that's not what I'm looking for, my device is rooted.
Thanks.
Click to expand...
Click to collapse
You heard right, this requires a custom kernel that has DT2W (Double Tap to Wake) compiled into the kernel, then you have to use a tool like Kernel Aduitor to enable it on each boot since even kernels that have this feature usually have it disabled by default.
Not that this will increase drain battery anywhere from 1% to 3% per hour (usually on the lower end of that range though, depends on usage)

acejavelin said:
You heard right, this requires a custom kernel that has DT2W (Double Tap to Wake) compiled into the kernel, then you have to use a tool like Kernel Aduitor to enable it on each boot since even kernels that have this feature usually have it disabled by default.
Not that this will increase drain battery anywhere from 1% to 3% per hour (usually on the lower end of that range though, depends on usage)
Click to expand...
Click to collapse
Thanks for the full answer! Well looks very well 1 or 3% of battery for that option, you can say to me what kernel is recommended for this?

AGNi or Explosion kernel are the only two I know with DT2W still enabled... FireKernel used to have it, but it was removed a few versions ago.
Make sure to backup in TWRP before flashing a kernel, if you want to switch kernels after flashing a custom one to try something different, restore the boot partition, and boot fully before flashing a different custom kernel.

acejavelin said:
AGNi or Explosion kernel are the only two I know with DT2W still enabled... FireKernel used to have it, but it was removed a few versions ago.
Make sure to backup in TWRP before flashing a kernel, if you want to switch kernels after flashing a custom one to try something ​different, restore the boot partition, and boot fully before flashing a different custom kernel.
Click to expand...
Click to collapse
Really thank you for your help, now I have another question, do you know how to activate the option on camerafv5 for manual focus? It is possible? I've read that will work with the new camera2api included on lollipop but I dunno how's that.

migueldvp said:
Really thank you for your help, now I have another question, do you know how to activate the option on camerafv5 for manual focus? It is possible? I've read that will work with the new camera2api included on lollipop but I dunno how's that.
Click to expand...
Click to collapse
Pretty sure the G3 doesn't support Camera API2
Sent from my Motorola XT1575 using XDA Labs

Related

Double tap feature

Hi guys,
is there a way to have the double tap feature to wake up the phone?
I mean without install a new rom. Maybe installing a kernel that support the stock rom.
Thanks
sivlab said:
Hi guys,
is there a way to have the double tap feature to wake up the phone?
I mean without install a new rom. Maybe installing a kernel that support the stock rom.
Thanks
Click to expand...
Click to collapse
install blue spark kernel stock version
Thanks a lot for the reply. Could you give me extra informazions about that kernel?
Where I can find it and if it is possibile to restore the original kernel in the case I don't like this one.
Thanks you
EDIT:
I found the kernel. But int the last post the developer says that the kernel will not be updated anymore. Do you advise to install anyway?
Interested in this as well, haven't found specific info on installing the "blue spark kernel stock version" on the Moto G 2015 though?
EDIT - ah ok it's here http://forum.xda-developers.com/2015-moto-g/orig-development/kernel-t3207597 - going to read up!
EDIT2 - ah bit confused on what needs to be done to flash the kernel...(is it dt.img ?) TWRP needed (I have it since I rooted) ? Also someone mentions going back to stock kernel if need be here http://forum.xda-developers.com/201...ent/kernel-t3207597/post63208808#post63208808 but I can't say it's very clear to me
webvan said:
Interested in this as well, haven't found specific info on installing the "blue spark kernel stock version" on the Moto G 2015 though?
EDIT - ah ok it's here http://forum.xda-developers.com/2015-moto-g/orig-development/kernel-t3207597 - going to read up!
EDIT2 - ah bit confused on what needs to be done to flash the kernel...(is it dt.img ?) TWRP needed (I have it since I rooted) ? Also someone mentions going back to stock kernel if need be here http://forum.xda-developers.com/201...ent/kernel-t3207597/post63208808#post63208808 but I can't say it's very clear to me
Click to expand...
Click to collapse
If you want to install the blu_spark kernel you have to download a zip file from this page. If you come from example from the stock rom you have to download "blu_spark_r92-stock-5.1.1_osprey_1562e7b.zip". To flash the zip you have to go in recovery mode and install it.
About restoring stock kernel as far as I read from the message you linked you have to:
-First backup the boot partition from TWRP and save it somewhere
-Do something...
-If you want restore the stock kernel you have to restore the boot partition you have saved in the first step (do it always from TWRP)
Thanks, it's a bit more clear now, are you going to give that kernel a try? On top of the double tap I'd be interested in getting improved battery life as well.
Well, I'm quite uncertain.
First option: install a custom kernel
Pros:
Install a single zip file instead of flash a custom ROM (losing all data)
Maintain the stock ROM
Cons:
Development for blu_spark kernel is abandoned (like the developer said in the last post of the topic). Yeah, you would have the double tap feature but have a kernel with no support. An option could be install this kernel and as soon as possible change it with a new one with active support. What do you think about?
The other kernel (squid kernel) misses this features (double tap to wake up)
Second option: install a custom ROM (e.g. Cyanogenmod 13)
Pros:
Very good ROM (from my own experience with other devices like Nexus 7 and Huawei)
If I'm not mistaken Cyanogenmod has the double tap features as a default feature
Cons:
Losing all data flashing the new ROM (actually not a very problem)
Losing the stock ROM (this is a not very problem too)
Smart creen on off is the solution!
It's available on play store. No root needed.
Thanks for the reply.
How about the drain battery of an app (such as Smart Screen Off) compared to a built in kernel feature?
None of the apps I've seen works well with double tapping as they want you to double tap on the proximity sensor. One option I've seen that works ok is "waving" if you set it to 3 quick waves. Not as nice as double topping.
It seems that a new kernel has appeared. It has the double tap to wake and is currently supported.
There is only a small problem: it doesn't support the stock ROM, but the CM13 yes.
Not hw feature. Can use more battery
Sent from my MotoG3 using Tapatalk
Thanks for the heads up, no go for stock 5.1.1 though
Did you ever try the other kernel now abandoned? That one worked with stock apparently.

Back on Stock Nougat and very happy

After several weeks of battling terrible battery drain, lag and sluggish performance I am back on Stock Nougat, build number NPJS25.93-14-8. With moderate use, my battery is now averaging less than 2% per hour ( < 1% while sleeping), where on the custom ROM of choice it was running over 5% per hour, even while sleeping. I tried every trick and tweak I could find and Better Battery Stats didn't show anything that could account for the high drain. I even tried a different ROM to no avail. So I threw in the towel, returned to stock, and did the latest OTA updates. I am now running rooted with ElementalX kernel 1.04 and I couldn't be more pleases with the overall performance and battery life.
I am sure it was something I missed but I got tired of spending hours trying to get back to the original performance and battery life the custom ROM had several weeks ago. Sometimes you just gotta do what you gotta do.
While ota updates.......i brought to twrp only.... instead of installing latest security update.......... manually tried to install update...bt i can't..... gets an error... didn't u faced such problems
Harshseth said:
While ota updates.......i brought to twrp only.... instead of installing latest security update.......... manually tried to install update...bt i can't..... gets an error... didn't u faced such problems
Click to expand...
Click to collapse
None of STOCK ROM or OTA updates can be flashed/updated by TWRP, you need to be on stock recovery as well everything stock (unmodified system, boot and all).
I faced this problem too, but I fixed mostly of the battery drain tweaking the kernel with the ElementalX app to ~0,80/h. I had to set the little cores working like big cores do, because all little cores and one big were in use always; and applied LightingBlade profile.
Harshseth said:
While ota updates.......i brought to twrp only.... instead of installing latest security update.......... manually tried to install update...bt i can't..... gets an error... didn't u faced such problems
Click to expand...
Click to collapse
In order to use the OTA path you have to be on stock recovery, boot and kernel, not on TWRP. Otherwise you get the error that you experienced.
xAnkris said:
I faced this problem too, but I fixed mostly of the battery drain tweaking the kernel with the ElementalX app to ~0,80/h. I had to set the little cores working like big cores do, because all little cores and one big were in use always; and applied LightingBlade profile.
Click to expand...
Click to collapse
I went that path but it didn't seem to help much. Besides, I am happy with this stock setup. It is much better than when I was on Marshmallow stock and went over to custom ROMs. I can do anything I want to do and install any app I desire to use. Good performance, great battery life, and customizable as much as I want. No need to be on custom.
pastorbob62 said:
After several weeks of battling terrible battery drain, lag and sluggish performance I am back on Stock Nougat, build number NPJS25.93-14-8. With moderate use, my battery is now averaging less than 2% per hour ( < 1% while sleeping), where on the custom ROM of choice it was running over 5% per hour, even while sleeping. I tried every trick and tweak I could find and Better Battery Stats didn't show anything that could account for the high drain. I even tried a different ROM to no avail. So I threw in the towel, returned to stock, and did the latest OTA updates. I am now running rooted with ElementalX kernel 1.04 and I couldn't be more pleases with the overall performance and battery life.
I am sure it was something I missed but I got tired of spending hours trying to get back to the original performance and battery life the custom ROM had several weeks ago. Sometimes you just gotta do what you gotta do.
Click to expand...
Click to collapse
Are you able to root the stock nougat build npjs25 14-8.?
If yes how you rooted your phone. Plzz guide me. I also want to root my stock nougat
ADITYA_KUMAR said:
Are you able to root the stock nougat build npjs25 14-8.?
If yes how you rooted your phone. Plzz guide me. I also want to root my stock nougat
Click to expand...
Click to collapse
Before you can root stock Nougat you must first unlock you bootloader, install TWRP then flash Elemental X kernel 1.04 from TWRP.
pastorbob62 said:
Before you can root stock Nougat you must first unlock you bootloader, install TWRP then flash Elemental X kernel 1.04 from TWRP.
Click to expand...
Click to collapse
What is elemental x kernel. I have a unlocked bootloader.
ADITYA_KUMAR said:
What is elemental x kernel. I have a unlocked bootloader.
Click to expand...
Click to collapse
Instead of asking questions that have been answered numerous times (ad nauseam) you should try reading through the forums. I realize you are a raw noob, but if you wanted to learn Calculus, would you ask a bunch of questions without doing any reading and studying? It's no different when you are modifying your smart phone.
Here is a link to a thread that will guide you to rooting stock Nougat. It works for all versions of stock Nougat.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
But don't do anything until you have read through the procedures and fully understand. Above all, make a backup of your system from TWRP before you do anything else.
pastorbob62 said:
Instead of asking questions that have been answered numerous times (ad nauseam) you should try reading through the forums. I realize you are a raw noob, but if you wanted to learn Calculus, would you ask a bunch of questions without doing any reading and studying? It's no different when you are modifying your smart phone.
Here is a link to a thread that will guide you to rooting stock Nougat. It works for all versions of stock Nougat.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
But don't do anything until you have read through the procedures and fully understand. Above all, make a backup of your system from TWRP before you do anything else.
Click to expand...
Click to collapse
once I tried to root on stock nogut, so I installed TWRP and flashed SuperSu and my phone got bricked
pastorbob62 said:
After several weeks of battling terrible battery drain, lag and sluggish performance I am back on Stock Nougat, build number NPJS25.93-14-8. With moderate use, my battery is now averaging less than 2% per hour ( < 1% while sleeping), where on the custom ROM of choice it was running over 5% per hour, even while sleeping. I tried every trick and tweak I could find and Better Battery Stats didn't show anything that could account for the high drain. I even tried a different ROM to no avail. So I threw in the towel, returned to stock, and did the latest OTA updates. I am now running rooted with ElementalX kernel 1.04 and I couldn't be more pleases with the overall performance and battery life.
I am sure it was something I missed but I got tired of spending hours trying to get back to the original performance and battery life the custom ROM had several weeks ago. Sometimes you just gotta do what you gotta do.
Click to expand...
Click to collapse
Very true.
Also try LightningBlade tunables(v 1.2.3 ; the newer version does not work that well for me..).
Stock rom provides the best balance between Performance and Battery life.
siddhesh9146 said:
once I tried to root on stock nogut, so I installed TWRP and flashed SuperSu and my phone got bricked
Click to expand...
Click to collapse
If you're rooting on stock Nougat, you must have a custom kernel flashed (or used the temporary dm-verity disabler on the stock kernel) before you root. Else, without the mentioned modifications, you'll trip the anti-rooting protection built into the stock kernel, and you'll have bootloops unless you reflash your stock ROM as you experienced.
Easiest way, as per the guide is to:
Flash/boot TWRP.
Backup.
Flash ElementalX or vegito (any custom kernel will do, as these kernels do not have the anti-rooting protection).
Reboot to test.
Boot back to TWRP
Flash SuperSU v2.79 or newer, or magisk 13 or newer
Reboot.
You should be rooted, on stock, and if you've flashed magisk, Safetynet should be working It's working well on NPJS25.93-14-8 and it's stable. Granted, a few apps now seem to detect root/magisk (and fail to download/update from the Play Store, with an error 0), but nothing that a sideload from a legitimate source wouldn't solve...
champsp said:
Very true.
Also try LightningBlade tunables(v 1.2.3 ; the newer version does not work that well for me..).
Stock rom provides the best balance between Performance and Battery life.
Click to expand...
Click to collapse
True that! :good:
siddhesh9146 said:
once I tried to root on stock nogut, so I installed TWRP and flashed SuperSu and my phone got bricked
Click to expand...
Click to collapse
If you had followed the link I supplied you would have had your answer as to why you had problems and also how to fix it.
echo92 said:
If you're rooting on stock Nougat, you must have a custom kernel flashed (or used the temporary dm-verity disabler on the stock kernel) before you root.
Click to expand...
Click to collapse
Hi, sorry for ask, do you know where can i find the temporary dm-verity disabler?
I tried with a script named "no-verity-opt-encrypt-5.1" (this works for the G5 Plus 'Potter') but i haven't had any success. Even i unpacked the stock boot.img and i tried to manually patch it, but i failed here too.
Honestly i would like to test the stock kernel, because i never used it, i am always attached to flashing EX to get root access. Thank you in advance.
moonlightdrive said:
Hi, sorry for ask, do you know where can i find the temporary dm-verity disabler?
I tried with a script named "no-verity-opt-encrypt-5.1" (this works for the G5 Plus 'Potter') but i haven't had any success. Even i unpacked the stock boot.img and i tried to manually patch it, but i failed here too.
Honestly i would like to test the stock kernel, because i never used it, i am always attached to flashing EX to get root access. Thank you in advance.
Click to expand...
Click to collapse
I don't know if this will still work on later builds than the November/December 2016 builds, but here's the kernel with dm-verity disabled: https://forum.xda-developers.com/mo...t-how-to-root-n-firmware-npj25-93-11-t3532556 Seems to cause bootloops though on the later builds however
Strictly speaking, I misspoke - it's not really a dm-verity disabler, more a stock kernel with dm-verity disabled. I think EX kernel is still the more stable and more reliable option. It would be nice to be able to root the stock kernel though...
echo92 said:
I don't know if this will still work on later builds than the November/December 2016 builds, but here's the kernel with dm-verity disabled: https://forum.xda-developers.com/mo...t-how-to-root-n-firmware-npj25-93-11-t3532556 Seems to cause bootloops though on the later builds however
Strictly speaking, I misspoke - it's not really a dm-verity disabler, more a stock kernel with dm-verity disabled. I think EX kernel is still the more stable and more reliable option. It would be nice to be able to root the stock kernel though...
Click to expand...
Click to collapse
Oh, i see, thanks for your response. I'll look into it to see how he did to by-pass the dm verity, and try to modify the last boot.img that we have.
I mentioned earlier in this thread about getting Error 0 whilst updating apps in Google Play. As it turns out, thanks to this tip here https://forum.xda-developers.com/showpost.php?p=73552496&postcount=57 it appears to be an error with permissions on the /data/media partition.
I managed to fix it with osm0sis' script:
Download from here https://forum.xda-developers.com/showthread.php?t=2239421 the sdcard Fix Permissions script http://forum.xda-developers.com/attachment.php?attachmentid=3761904&d=1464187934
You may wish to back up your data with TWRP or ensure you have your photos and videos somewhere safe prior to flashing this.
Reboot to TWRP and backup your device.
Flash the above script.zip in TWRP and wait for it to complete. (it should be fixing the permissions in /data/media)
Reboot and you should be able to download/update apps again from Google Play afterwards. You may have to uninstall the app and re-install the app if it keeps failing.
I've got this working on a XT1642 running June 2017 stock ROM, rooted with magisk 13.3 and apps including Snapchat and Google Chrome update without issue now.
echo92 said:
I mentioned earlier in this thread about getting Error 0 whilst updating apps in Google Play. As it turns out, thanks to this tip here https://forum.xda-developers.com/showpost.php?p=73552496&postcount=57 it appears to be an error with permissions on the /data/media partition.
I managed to fix it with osm0sis' script:
Download from here https://forum.xda-developers.com/showthread.php?t=2239421 the sdcard Fix Permissions script http://forum.xda-developers.com/attachment.php?attachmentid=3761904&d=1464187934
Click to expand...
Click to collapse
Useful info, this happened to me a couple of days ago. I thought it was something related to the integrated Chrome WebView in conflict with the system WebView, because it only happened when i tried to update Chrome, or any of his variants (dev, beta, canary, etc). Thanks.

Unofficial LineageOS 13.0 for Vodafone Smart Ultra 6

Disclaimer
I'm am not responsible for bricked devices, flashing custom ROM's/Recovery's is done so at YOUR OWN RISK!
Information
This is a standard Lineage build without any extras & compiled with stock SU6 6.0.1 kernel
Download
http://www.mediafire.com/file/n55eth5yidbos5c/lineage-13.0-20171007-UNOFFICIAL-p839v55.zip
Installation
I recommend doing a full wipe before flashing!
Flash ROM using TWRP
Flash GAPPS 6.0 arm package of your choice
Reboot & wait for Android to boot
Version Information
Status Beta
ROM OS 6.0.1 Marshmallow
ROM Kernel 3.10.49
Created 2017-08-24
Updated 2017-10-07
Thanks goes out to @wbrambley for his involvement in testing & helping to solve / fix bugs!
I noticed that "mm-pp-daemon" was stopping the CPU from going in to sleep state and keeping it at full clocks but after killing the process it reloaded and was fine.
@nutsda, I've tried to pm this but its not working. Probably some spell check safety net
You should post a link here. http://www.modaco.com/forums/forum/796-vodafone-smart-ultra-6/
the SU6 has its own device forum on Modaco and I'm sure it would create some interest.
I've pushed(?) a change that enables the NFC and also put up my overlay folders. There's some stuff in there you might like.
The sensors (Accelerometer, Magnetic field and Rotation vector) are still causing grief.
How fast is your phone to "wake up" from sleep? My buttons light up but screen on takes about 5 seconds. (could be the sensor hal cal firing up but im not 100% sure.)
wbrambley said:
@nutsda, I've tried to pm this but its not working. Probably some spell check safety net
You should post a link here. http://www.modaco.com/forums/forum/796-vodafone-smart-ultra-6/
the SU6 has its own device forum on Modaco and I'm sure it would create some interest.
I've pushed(?) a change that enables the NFC and also put up my overlay folders. There's some stuff in there you might like.
The sensors (Accelerometer, Magnetic field and Rotation vector) are still causing grief.
How fast is your phone to "wake up" from sleep? My buttons light up but screen on takes about 5 seconds. (could be the sensor hal cal firing up but im not 100% sure.)
Click to expand...
Click to collapse
I have merged the commit you made to github & can confirm NFC now enables for me.
Update has been uploaded http://www.mediafire.com/file/7bjnwaaupm4ejf0/lineage-13.0-20170903-UNOFFICIAL-p839v55.zip, first post link also updated.
Camera now working & NFC now enables thanks to @wbrambley
How do I get this rom installed? I already failed rooting my phone to install TWRP. I tried to get temporary Root with KingRoot but that doesn´t work. I´ve Stock Marshmallow Rom on my phone. Can someone help me?
coolbook1 said:
How do I get this rom installed? I already failed rooting my phone to install TWRP. I tried to get temporary Root with KingRoot but that doesn´t work. I´ve Stock Marshmallow Rom on my phone. Can someone help me?
Click to expand...
Click to collapse
Use recovery to flash a 5.1 stock ROM, then you can get temporary root. I'm guessing you've found a guide for this. After that I recommend flashing stock MM from TWRP. There's one with edited uodater-script around that will work.
Hint: look at the forum I posted earlier.
Sent from my HUAWEI GRA-L09
Thanks for your rom
I Wonder when will sensors be fixed?
Update uploaded http://www.mediafire.com/file/v5m8keoadkwkaz2/lineage-13.0-20170906-UNOFFICIAL-p839v55.zip
Sensors now working properly, also improved boot up time.
Waiting For Your Stable Version
Sensors now working properly, also improved boot up time.[/QUOTE]
thanks Nutsda I'm Waiting For Your Stable Version...
lineage-13.0-20170906
Auto rotate screen is broken in this build.
thanks
When will we see an update of your work? Keep it up.
Okay here is an updated build http://www.mediafire.com/file/wedlnkhzk4e5o81/lineage-13.0-20170925-UNOFFICIAL-p839v55.zip, playstore should now work properly & improvements to sensors (but probably still require more work).
Thank you. Market now works. Still can't install nova but overall very good. Looking forward for the first stable release
New update uploaded http://www.mediafire.com/file/n55eth5yidbos5c/lineage-13.0-20171007-UNOFFICIAL-p839v55.zip
Improved audio volume,
All sensors now working - thanks to @wbrambley,
Lineage updated to 6.0.1_r80.
i didn't tried this rom but
can u tell me why any custom rom for this phone is laggy as hell...?
DR.iTACHi said:
i didn't tried this rom but
can u tell me why any custom rom for this phone is laggy as hell...?
Click to expand...
Click to collapse
I haven't tried the other custom roms but I believe it will be because most of them are ported from another phone rather than specifically built for this phone.
nutsda said:
I haven't tried the other custom roms but I believe it will be because most of them are ported from another phone rather than specifically built for this phone.
Click to expand...
Click to collapse
i tried your cm 12.1
that built specially for this phone laggy as hell too!
is this rom is laggy too?
i flashed your rom it's stable and not laggy like others but how to root it?
DR.iTACHi said:
i flashed your rom it's stable and not laggy like others but how to root it?
Click to expand...
Click to collapse
You have to download SuperSU to get root access as Lineage doesn't have root access built in.

[ROM] [Experimental] [LineageOS 15.1] [8.1] [Build 2018-07-05] [Oppo R7f]

First off, huge thanks to all the LineageOS developers. Specially MikeNG for his continuous work on OPPO devices.
Lineage 15.1 is finally here!
Device(s) Supported:
R7f *ONLY*
Don't flash this rom to any other R7 variant
What's working:
* Boot (Much better than not booting obviously)
* RIL (Calls,Text,Data)
* WiFi
* Bluetooth
* Camera
* Audio
* Sensors
* Flashlight
* Notification LED
What's not working:
* Double tap screen to lock/unlock. Unlock not working
From Stock (ColorOS) Installation:
*Charge battery near full, DISCONNECT usb cable
Having the USB cable connected in this process causes hard to get out of bootloop after installation
1. Boot phone in fastboot mode: Press and hold both Power + Volume Up buttons.
2. Unlock boot loader with command: fastboot oem unlock
3. Flash recovery with command: fastboot flash recovery name.recovery.img
4. Reboot phone into recovery mode using command "fastboot reboot-bootloader" and press and hold Volume Down button.
5. Full wipe of device. Place ROM and Gapps on external SDcard or use ADB to transfer them to the (now wiped) internal Data partition.
6. Install ROM and GApps.
7. Reboot phone and wait (first boot will take quite a bit of time)
* If you don't have any previous experience with rooting, custom roms & recoveries. Please follow the more 'newbie' friendly in-depth tutorials
XDA forums has plenty of well done easy to follow tutorials!
From Lineage 14.1 :
*Charge battery near full, DISCONNECT USB cable before reboot into recovery
Having the USB cable connected in this process causes a hard to get out of bootloop after installation
*Make sure you have the latest TWRP recovery installed before continuing
1. Wipe device, perform a clean install
Downloads :
[ROM] Unofficial R7f LineageOS 15.1
Archive must be unpacked! Contains flash-able zip & md5 checksum
[Gapps -> ARM -> 8.1]
*Don't select the Aroma variant. TWRP doesn't like it
[TWRP Recovery for R7f] (twrp-3.2.2-0)
NOTES:
*This is bat country! You are on your own when something goes bad, I can't help you in case of bricked device
*Precaution: Charge battery atleast 80%
*Advisable: Make Nandroid backup before flashing
*Precaution: Due to a weird device specific bug
Don't (re)boot into Recovery nor flash the R7 with the USB cable still attached. Could result in a bootloop which is rather hard to get out off
Bootloop trick: When finally powered off, leave the device off for at least a hour Take a walk or something!
No idea why but this seems to do the trick, after a prolonged period of being turned off, it boots normally into LineageOS
And will continue to reboot just fine! Maybe disconnect usb cable before rebooting out of precausion tho
Great work once again!
I assume this will be without the "project tremble" hardware separation layer introduced in Android Oreo, no?
With the differences in Android versions compared to stock, I do start to wonder, what are the drawbacks with this ROM? I mean in terms of performance, size, etc. Do you know of any?
Forage81 said:
Great work once again!
I assume this will be without the "project tremble" hardware separation layer introduced in Android Oreo, no?
With the differences in Android versions compared to stock, I do start to wonder, what are the drawbacks with this ROM? I mean in terms of performance, size, etc. Do you know of any?
Click to expand...
Click to collapse
Thank you!
Concerning Tremble, can't have 8.1 without but seems to be using legacy & updated vendor blobs.
Not sure what you mean with "stock" Stock AOSP 8.1 builds or the stock ColorOS?
Compared to stock ColorOS 4.4. too many differences to name. Compared to AOSP, I'd suggest reading into LineageOS features
Drawbacks to using this rom I can't think of one. Till now everything seems to be working just fine
Performance seems to be great, Battery life seems better than LineageOS 14.1 and concerning size it's smaller than stock ColorOS
I believe tremble is mandatory for new phones and optional for existing that update to 8.1.
You would have known you are using Tremble if you are the one who created the port for this phone.
I don't believe you can just use existing blobs for a change like that and it would require help from Oppo, who had never offered even the slightest for our phone.
I meant Lineage OS 15.1 compared to stock Oppo/ColorOS. I know the differences OS/functionality wise. With such a big jump I would have expected at least performance issues since non of the blobs have been touched anymore. Decreased compatibility seems likely to me in such a case.
Good to hear you do not experience this.
I am hesitant to take the risk using this ROM though. For the same reasons mentioned above.
Have you been using the phone in real life without (too many) glitches for a bit by now?
I really hope
I already test this rom.
It's really good.
I found the bug
1. Charging slow. Take 1 hour 45 mnite to full
2. Double tap to wake not work
I'm back to your previous rom 14.1
In Los 14.1 your build. Fast charging like vooc dan double tap to wake work.
Can u fix it?
Thanks somuch for great work.
Ravhinzy said:
I already test this rom.
It's really good.
I found the bug
1. Charging slow. Take 1 hour 45 mnite to full
2. Double tap to wake not work
I'm back to your previous rom 14.1
In Los 14.1 your build. Fast charging like vooc dan double tap to wake work.
Can u fix it?
Thanks somuch for great work.
Click to expand...
Click to collapse
Both work fine in this 15.1 build
VOOC charging, and double tap @ statusbar/lockscreen
Must be something on your end. did you perform a clean install?
Wipe system,data,cache dalvik etc
But out of precaution I'll test it further in the coming days. More charging and more tapping on my screen
Forage81 said:
I believe tremble is mandatory for new phones and optional for existing that update to 8.1.
You would have known you are using Tremble if you are the one who created the port for this phone.
I don't believe you can just use existing blobs for a change like that and it would require help from Oppo, who had never offered even the slightest for our phone.
I meant Lineage OS 15.1 compared to stock Oppo/ColorOS. I know the differences OS/functionality wise. With such a big jump I would have expected at least performance issues since non of the blobs have been touched anymore. Decreased compatibility seems likely to me in such a case.
Good to hear you do not experience this.
I am hesitant to take the risk using this ROM though. For the same reasons mentioned above.
Have you been using the phone in real life without (too many) glitches for a bit by now?
Click to expand...
Click to collapse
Concerning your last question
Haven't turned my phone off since 7-5 while running this 15.1 build
Works great so far. Haven't found issues/glitches as of yet. No weird things happening with my daily usage thus far
-Oops things went a bit wrong-
JJRT said:
Both work fine in this 15.1 build
VOOC charging, and double tap @ statusbar/lockscreen
Must be something on your end. did you perform a clean install?
Wipe system,data,cache dalvik etc
But out of precaution I'll test it further in the coming days. More charging and more tapping on my screen
Click to expand...
Click to collapse
Thanks for ur answers.
Oh. I will try it again. I always clean install like u said.
Double tap to sleep work fine in status bar or home botton. But to wake, all screen i taping, the phone not wake. Any ideas the problem?
I back to Los 14.1. all fine.
I really like u work on los 15.1. i want to use it
Ravhinzy said:
Thanks for ur answers.
Oh. I will try it again. I always clean install like u said.
Double tap to sleep work fine in status bar or home botton. But to wake, all screen i taping, the phone not wake. Any ideas the problem?
I back to Los 14.1. all fine.
I really like u work on los 15.1. i want to use it
Click to expand...
Click to collapse
Ah indeed, the waking up using double tab isn't working atm.
I will look into that. The 15.1 build is perfectly usable otherwise.
But yeah you can roll back to 14.1 in the meantime if you really need the double tap option
JJRT said:
Ah indeed, the waking up using double tab isn't working atm.
I will look into that. The 15.1 build is perfectly usable otherwise.
But yeah you can roll back to 14.1 in the meantime if you really need the double tap option
Click to expand...
Click to collapse
Yes. I wait until the problem fix. And plis check charging time
Ravhinzy said:
Yes. I wait until the problem fix. And plis check charging time
Click to expand...
Click to collapse
The charging time should not be impacted in any way as it is hardware based. Unless a ROM or app is using extreme resources while charging, draining the battery at the same time you are charging it, charging times should be the same in both 14.1 and 15.1.
Please double check if it has really changed.
Forage81 said:
The charging time should not be impacted in any way as it is hardware based. Unless a ROM or app is using extreme resources while charging, draining the battery at the same time you are charging it, charging times should be the same in both 14.1 and 15.1.
Please double check if it has really changed.
Click to expand...
Click to collapse
Ok, thank you. I have returned to los 14.1. how to fix or replace double tap to wake to work? I want to try again. I will check it again
Wow amazing work!
I have checked that charging times are the same as los 14.1 as opposed to claims by Ravhinzy.
However, the issue of double tap to unlock is also present for all other screen off gestures (drawing O, M, V etc. when screen is off). Other than that, the roms seems stable enough. (so are u planning to make r7f rom official on lineage os?)
In any case, keep up the good work and thanks for sharing this rom!
ph03nae said:
Wow amazing work!
I have checked that charging times are the same as los 14.1 as opposed to claims by Ravhinzy.
However, the issue of double tap to unlock is also present for all other screen off gestures (drawing O, M, V etc. when screen is off). Other than that, the roms seems stable enough. (so are u planning to make r7f rom official on lineage os?)
In any case, keep up the good work and thanks for sharing this rom!
Click to expand...
Click to collapse
do you know how to fix dt2w?
eg with flash module or update.zip to fix it.
I've been looking for ways on google how to fix it still has not worked.
I really hope to get this cusrom. fell in love when first tried it.
ph03nae said:
Wow amazing work!
I have checked that charging times are the same as los 14.1 as opposed to claims by Ravhinzy.
However, the issue of double tap to unlock is also present for all other screen off gestures (drawing O, M, V etc. when screen is off). Other than that, the roms seems stable enough. (so are u planning to make r7f rom official on lineage os?)
In any case, keep up the good work and thanks for sharing this rom!
Click to expand...
Click to collapse
Thank you
Yeah I can't replicate the charging issue as well. I have 2 R7f's laying around.
VOOC is working fine on both of them with my 15.1 build. Drained them both multiple times and recharged.
Still haven't figured out what the deal is with tap 2 wake.
The r7f will never get official lineageOS builds sadly because of the weird USB-attached on (re)boot bootloop bug
The link for the OS takes me to something called mega.nz but nothing loads, then it times out.
MrFlibble23123 said:
The link for the OS takes me to something called mega.nz but nothing loads, then it times out.
Click to expand...
Click to collapse
This rom is not for the r7plusf.
kishd said:
This rom is not for the r7plusf.
Click to expand...
Click to collapse
Good job I couldnt download it then, I'd have been scratching my head. The official Lineage page has a 15.1 nightly build but I can't get WiFi working on the device using it so have gone with 14.1
Ravhinzy said:
do you know how to fix dt2w?
eg with flash module or update.zip to fix it.
I've been looking for ways on google how to fix it still has not worked.
I really hope to get this cusrom. fell in love when first tried it.
Click to expand...
Click to collapse
New release, tape 2 wake should be functioning correctly now (I have tested it)

3a, issues with Android System/Kernel killing battery?

Hello! Let me know if this is the wrong place but ever since I got my 3a a few weeks ago, I've been disappointed with the battery life. The stats are below. The "Averaged per complete charge" are completely inaccurate as I've never hit > 4 SOT, ever. I don't really know what to do at this point because I've tried cleaning out everything I could.
These stats are on a regular work day, light usage. Texting, 2 or 3 calls, etc.
battery stats
Any tips?
If you're on stock, then custom kernel should help. I'm quite happy with the battery benefits that EX kernel brought to my Pixel 3a. You can find it here - https://forum.xda-developers.com/pixel-3a/development/kernel-pixel-3a-xl-elementalx-1-01-t3931185
pasha_d said:
If you're on stock, then custom kernel should help. I'm quite happy with the battery benefits that EX kernel brought to my Pixel 3a. You can find it here - https://forum.xda-developers.com/pixel-3a/development/kernel-pixel-3a-xl-elementalx-1-01-t3931185
Click to expand...
Click to collapse
Thanks. A poster elsewhere recommended a system reset and flash the newest update and release basic apps for a few days to see how the battery does.
Can I flash a custom kernel without root?
sippinhenn said:
Thanks. A poster elsewhere recommended a system reset and flash the newest update and release basic apps for a few days to see how the battery does.
Can I flash a custom kernel without root?
Click to expand...
Click to collapse
In Android 9 you can use TWRP custom recovery to flash kernel ZIP without having root. If you're on 10 you still might be able to flash it without root in fastboot (or should I say in "fastbootd"), but I didn't try that.

Categories

Resources