Database Info

[ROM] Mokee 5.1.1 STABLE (Daily Driver)

First Thing First : I'm not the developer of this ROM. Just Sharing "MY" experience
It's been a long time Mokee builds are available for Mi 4i. I've been using it since 2nd last build (more than 10 days) and currently on latest built i.e. 25th Jan 2016. And I can say that it's Stable.
What's Working :
Everything, except volume rocker keys on earphone.
Highlights:
DT2W
D2TS
Ambient Display
Not even a single FCs or Reboot since installation (more than 10 days now)
CoC is working fine
FB is working fine
More than 24 hours backup (With normal use, NO intensive gaming and ~4 hours SOT)
Installation Instruction (Which I followed, You can go with normal way):
1. Flash MIUI ROM 5.6.11 (I tried to install on 7.1.1, it keep on rebooting. Tried everything, but no luck)
2. Flash TWRP as permanent Recovery
3. Root using SuperSU
4. Wipe everything (but ROM & Gapps Folders)
5. Flash ROM
6. Reboot to System (No need to set-up anything, just do next next)
7. Go to Recovery, Flash Gapps
8. Reboot to system (Again no need to set-up anything, just do next next)
9. Factory Reset (From settings, NOT from recovery)
10. Set-up now
11. Enjoy and All the Best
I know it's painful the way I set-up ROM, but yes I'm not facing any problem at all (Fingers-crossed ). We three colleagues are using it. So it's tested now (you can say)
I've only one phone and I'm using it as a daily driver.
Downloads:
ROM
Gapps : pico version

Enjoy the New ROM guys

this rom is still stuck in LP. was hoping for MM already

ajaxcbcb said:
this rom is still stuck in LP. was hoping for MM already
Click to expand...
Click to collapse
You are very much correct my friend, but again it's a very good alternative for :
1. Those who don't wanna be on MIUI.
2. Struggling to find a CM daily driver.
//TM

good to know. I couldn't take the constant reboot from Remix ROM. Just installed Mokee yesterday. So far so good. Keep my fingers crossed.

getting very high wakelock on *alarms* on any mokee rom

Yeah this is the most stable custom rom for mi4i ...
- official
- update OTA almost every week ..

Can anyone verify if fast dormancy is present in the rom? either through wakelocks or logcat(it should say fast dormancy service or otherwise)

Is ambient display working on this rom?

Hey I am not able to do it. I tried it several times, but every time it says that ERROR IN UPDATER BINARY ZIP.......I am not able to flash it. Help me.

Rajat Naik said:
Is ambient display working on this rom?
Click to expand...
Click to collapse
Yes, Check OP.

xposed support?

lineoxkun said:
xposed support?
Click to expand...
Click to collapse
works, no problem!

imagine92 said:
works, no problem!
Click to expand...
Click to collapse
Nice! Definitely will try this ROM tonight! Thanks OP for sharing [emoji1]
Sent from my MI 4i using Tapatalk

What's your SOT on MIUI 7 with similar type of use?

not happening please help. i tried flashing mokee 5.1 on my mi4i but there are some errors occuring everytime i try to do it. help on this.

sik619 said:
not happening please help. i tried flashing mokee 5.1 on my mi4i but there are some errors occuring everytime i try to do it. help on this.
Click to expand...
Click to collapse
Use twrp 2.8.7
http://forum.xda-developers.com/showthread.php?t=3204594

Is it smooth as any other moto g mobile lolipop version...becoz i always get a feel that miui is laggy..i never install a custom rom before

hey i flashed mokee and the gapps as well...but now its rebooting repeatedly. there comes this screen with welcome and the language but cant click next option..i dont know why. help me

sik619 said:
hey i flashed mokee and the gapps as well...but now its rebooting repeatedly. there comes this screen with welcome and the language but cant click next option..i dont know why. help me
Click to expand...
Click to collapse
I suggest you to use miui 6.6.10.0 glob stable before flash mokee rom

Android os huge battery drain over night

I have a rooted s6 with custom recovery(TWRP) and custom rom(THE GRIFFIN) and my phone is draining really fast.
U can see in the picture that i attached below that at 1AM the phone was at 100% and i left it aside cz i went to sleep, i woke up at 7:40AM and the phone was at 53% and all the drain was because of ANDROID OS.
What should i do??

Try a clean flash of that ROM. (you will lose all data, so make a backup)
Also you can try Noble Nougat Experience... i'm experiencing 4,5h/5h screen on time & 3% battery drain over night.

niektk said:
Try a clean flash of that ROM. (you will lose all data, so make a backup)
Also you can try Noble Nougat Experience... i'm experiencing 4,5h/5h screen on time & 3% battery drain over night.
Click to expand...
Click to collapse
When i flashed the rom using twrp i made a clean flash (all data were wiped..). And nougat nouble experience is a good rom ( i had it before) but my question is xposed comoatible with it yet?
If yes i'm gonna switch back

@[email protected]@[email protected] said:
When i flashed the rom using twrp i made a clean flash (all data were wiped..). And nougat nouble experience is a good rom ( i had it before) but my question is xposed comoatible with it yet?
If yes i'm gonna switch back
Click to expand...
Click to collapse
Hmm, i dont know. You can ask in the telegram group.. (join it by clicking the link in the NNE post.)

I'm getting the same issue with stock nougat as well as noble nougat experience 3.0.

install wakelock detector or battery stats and check, what do not let your phone go into deep sleep

Bootloop with official LineageOS 14.1, but not with SultanROM

Dear ladies and gentlemen,
a couple of weeks ago I decided to switch from SultanROM (latest build from 30th April) to LineageOS 14.1 (nightly build from 5th June 2017). Due to some minor bugfixes I updated to the nightly build from 17th of July. My phone worked well, aside from 2-3 random reboots. But two days a go all of a sudden it hung up. I tried to get it up again with a hard reboot. After a while I realized I was in a bootloop. Of course I tried the first obvious steps to get rid of the bootloop:
Wipe cache (including ART/Dalvik cache)
Flashed the most recent nightly build (2017-07-31) + wipe cache
Factory reset
Updated TWRP from 3.0.2 to 3.1.1
But even then - no chance, I was still hanging in the bootloop. After a few more tries I flashed SultanROM and tried again. Surprise, surprise: it worked perfectly, the phone got almost immediately up!
I'd like to go back to LineageOS, but I don't have a clue how to avoid the bootloop when flashing it again. In the past I flashed other firmwares and images, too (i.e. the 44S and persist.img from this post: https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061). Could this be a problem?
Any help would be appreciated!

grshnckh said:
Dear ladies and gentlemen,
a couple of weeks ago I decided to switch from SultanROM (latest build from 30th April) to LineageOS 14.1 (nightly build from 5th June 2017). Due to some minor bugfixes I updated to the nightly build from 17th of July. My phone worked well, aside from 2-3 random reboots. But two days a go all of a sudden it hung up. I tried to get it up again with a hard reboot. After a while I realized I was in a bootloop. Of course I tried the first obvious steps to get rid of the bootloop:
Wipe cache (including ART/Dalvik cache)
Flashed the most recent nightly build (2017-07-31) + wipe cache
Factory reset
Updated TWRP from 3.0.2 to 3.1.1
But even then - no chance, I was still hanging in the bootloop. After a few more tries I flashed SultanROM and tried again. Surprise, surprise: it worked perfectly, the phone got almost immediately up!
I'd like to go back to LineageOS, but I don't have a clue how to avoid the bootloop when flashing it again. In the past I flashed other firmwares and images, too (i.e. the 44S and persist.img from this post: https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061). Could this be a problem?
Any help would be appreciated!
Click to expand...
Click to collapse
Known issue with latest update of Lineage Os.
Meanwhile you can try latest Unofficial Lineage Os from Sultan.

Mr.Ak said:
Known issue with latest update of Lineage Os.
Meanwhile you can try latest Unofficial Lineage Os from Sultan.
Click to expand...
Click to collapse
Very interesting, thanks! Is there any bugreport or anything else, on which I could track the status?

grshnckh said:
Very interesting, thanks! Is there any bugreport or anything else, on which I could track the status?
Click to expand...
Click to collapse
https://www.cmxlog.com/14.1/bacon/

Mr.Ak said:
https://www.cmxlog.com/14.1/bacon/
Click to expand...
Click to collapse
Thanks, but this is the general changelog for the bacon devices from which I can't say if the bug I'm affected by is already fixed or not. When the issue is a known one, I assume there is some sort of bugreport or discussion going on. Could you provide further information about this bug in particular? Would highly appreciate!

grshnckh said:
Thanks, but this is the general changelog for the bacon devices from which I can't say if the bug I'm affected by is already fixed or not. When the issue is a known one, I assume there is some sort of bugreport or discussion going on. Could you provide further information about this bug in particular? Would highly appreciate!
Click to expand...
Click to collapse
Maybe follow the lineage os discussion thread:https://www.google.co.in/amp/s/foru...iscussion-lineageos-cyanogenmod-t3526394/amp/

Mr.Ak said:
Maybe follow the lineage os discussion thread:https://www.google.co.in/amp/s/foru...iscussion-lineageos-cyanogenmod-t3526394/amp/
Click to expand...
Click to collapse
Are you refering to this one: https://forum.xda-developers.com/showpost.php?p=72344415&postcount=942?

grshnckh said:
Are you refering to this one: https://forum.xda-developers.com/showpost.php?p=72344415&postcount=942?
Click to expand...
Click to collapse
Yes but the whole thread not just a single post.

Mr.Ak said:
Yes but the whole thread not just a single post.
Click to expand...
Click to collapse
Most of the outlined problems are about random reboots and a crashing camera (I read back to page 93). But my problem is: LineageOS 14.1 doesn't even start anymore - after wiping everything, flashing the newest nightly and doing a factory reset.

grshnckh said:
Most of the outlined problems are about random reboots and a crashing camera (I read back to page 93). But my problem is: LineageOS 14.1 doesn't even start anymore - after wiping everything, flashing the newest nightly and doing a factory reset.
Click to expand...
Click to collapse
Well,you can post your issues there or move on to unofficial lineage os by @idprophecy or sultan.
Sent from my A0001 using Tapatalk

I am too facing this issue. Did you get it working @grshnckh ?

CedArctic said:
I am too facing this issue. Did you get it working @grshnckh ?
Click to expand...
Click to collapse
Unfortunately not. I still stick to SultanROM as a temporarily solution, altough I'd prefer to use LineageOS 14.1 again. Which build have you tried?

grshnckh said:
Unfortunately not. I still stick to SultanROM as a temporarily solution, altough I'd prefer to use LineageOS 14.1 again. Which build have you tried?
Click to expand...
Click to collapse
I flashed various builds with no success. What did seem to work is sultanized ROMs, I flashed Sultanized RR and it booted up fine and it was actually pretty good. Just a bit ago I went on a flashing adventure to go and flash AOSPA 7.2.1 but that ended up badly with a bootloop and a broken recovery. I was forced to download WugFresh's toolkit and fix the softbrick (lost all data in the process beware), I am currently on stock CM12.1 and I'm going to flash to AOSPA probably after the boot has finished up.

CedArctic said:
I flashed various builds with no success. What did seem to work is sultanized ROMs, I flashed Sultanized RR and it booted up fine and it was actually pretty good. Just a bit ago I went on a flashing adventure to go and flash AOSPA 7.2.1 but that ended up badly with a bootloop and a broken recovery. I was forced to download WugFresh's toolkit and fix the softbrick (lost all data in the process beware), I am currently on stock CM12.1 and I'm going to flash to AOSPA probably after the boot has finished up.
Click to expand...
Click to collapse
So WugFresh's toolkit did the trick for you? Do you intent to flash LineageOS afterwards again?

grshnckh said:
So WugFresh's toolkit did the trick for you? Do you intent to flash LineageOS afterwards again?
Click to expand...
Click to collapse
Don't think I'm going back to Lineage, RR for me is better (Sultanized or not version). For now I think I'm going to stay on AOSPA. If you try WugFresh's stock flashing tool I urge you to backup all your data.

CedArctic said:
Don't think I'm going back to Lineage, RR for me is better (Sultanized or not version). For now I think I'm going to stay on AOSPA. If you try WugFresh's stock flashing tool I urge you to backup all your data.
Click to expand...
Click to collapse
Thanks for your advice. I already lost everything while trying to get back to LineageOS the last time. Fortunately I had up to date backups.
Have you flashed any ROMs or other stuff before that could cause the problems?

No, not really. I had this issue (meaning that I couldn't change to another non Sultan ROM) for a while now but chose to ignore it. Today I flashed multirom on top of Sultanized RR but I don't think that made any difference, when I flashed to AOSPA everything went South.

CedArctic said:
No, not really. I had this issue (meaning that I couldn't change to another non Sultan ROM) for a while now but chose to ignore it. Today I flashed multirom on top of Sultanized RR but I don't think that made any difference, when I flashed to AOSPA everything went South.
Click to expand...
Click to collapse
I tried several modems a few weeks back, but I'm not sure if this could be the reason.

grshnckh said:
I tried several modems a few weeks back, but I'm not sure if this could be the reason.
Click to expand...
Click to collapse
I originally suspected the firmware as well, turns out that probably wasn't the case, but I am now also now suspecting that the ROMs I tried to flash weren't f2fs compatible and it wasn't sultan's fault after all.

CedArctic said:
I originally suspected the firmware as well, turns out that probably wasn't the case, but I am now also now suspecting that the ROMs I tried to flash weren't f2fs compatible and it wasn't sultan's fault after all.
Click to expand...
Click to collapse
I read about a similar issue: https://forum.xda-developers.com/showpost.php?p=69837921&postcount=3
Highly would appreciate when you keep us up to date here. Good luck!

Looking for good stock based rom with XZ1/XZs features

Hello Z5 Users,
Bought my Z5 3 days ago and I like this phone so much.So today I installed M-Rom with XZ1 features.All nice but phone even in idle keeps being hot and rom doesn't recognize sim card.Is there similiar rom that doesn't have that problems?
Cheers

Okey guys put this in another way.Has anyone facing with issues on 2.3 version M-Rom like:fingerprint sensor is inaccurate,phone lags when entering into battery settings and my phone is hot where is NFC logo on back of the phone even in idle.
Tried flashing again .54 fw than M-Rom,deleted bloatware from rom and still nothing.
Any help is appreciated by me.

Yanun said:
Okey guys put this in another way.Has anyone facing with issues on 2.3 version M-Rom like:fingerprint sensor is inaccurate,phone lags when entering into battery settings and my phone is hot where is NFC logo on back of the phone even in idle.
Tried flashing again .54 fw than M-Rom,deleted bloatware from rom and still nothing.
Any help is appreciated by me.
Click to expand...
Click to collapse
Hello bro this happened to me quite recently too with simcard problems as i too also got the phone quite recently and installed that rom i have it now working perfectly the only way i could fix it is by wiping the phone totally and installing stock rom. Then i install twrp then install the xz rom. Even though its a long process it works and to fix heat issues and improve battery life which my battery life is perfect download from these links
https://forum.xda-developers.com/xp...d-fsc-1-0-dont-sacrifice-performance-t3670586 by @korom42 now this may slow down your phone a bit but i am running all games with no lag so it isnt a problem for me and i game quite a lot i have installed fsc+ which helps with heat quite drastically especially with this rom, download 2.2 version even though its for stock it also works for non-stock is you read what he says in blue. And also download this https://forum.xda-developers.com/xp...-lxt-xperia-tweaks-legendary-battery-t3676698 also by @korom42 make sure you have rooted with magisk and you need to install busybox install it in system/bin not system/xbin and install kernel auditor and for all settings press apply on boot reply back to me for anything else

Quantumkk123 said:
Hello bro this happened to me quite recently too with simcard problems as i too also got the phone quite recently and installed that rom i have it now working perfectly the only way i could fix it is by wiping the phone totally and installing stock rom. Then i install twrp then install the xz rom. Even though its a long process it works and to fix heat issues and improve battery life which my battery life is perfect download from these links
https://forum.xda-developers.com/xp...d-fsc-1-0-dont-sacrifice-performance-t3670586 by @korom42 now this may slow down your phone a bit but i am running all games with no lag so it isnt a problem for me and i game quite a lot i have installed fsc+ which helps with heat quite drastically especially with this rom, download 2.2 version even though its for stock it also works for non-stock is you read what he says in blue. And also download this https://forum.xda-developers.com/xp...-lxt-xperia-tweaks-legendary-battery-t3676698 also by @korom42 make sure you have rooted with magisk and you need to install busybox install it in system/bin not system/xbin and install kernel auditor and for all settings press apply on boot reply back to me for anything else
Click to expand...
Click to collapse
Thanks bro for reply.I'll try it asap.

Yanun said:
Thanks bro for reply.I'll try it asap.
Click to expand...
Click to collapse
Np

Quantumkk123 said:
Np
Click to expand...
Click to collapse
In flashtool did you picked any options in wipe section and also on the start in aroma which option of wipe did you selected? First or second?

Yanun said:
In flashtool did you picked any options in wipe section and also on the start in aroma which option of wipe did you selected? First or second?
Click to expand...
Click to collapse
second but not sure about the first bro

[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)