Database Develop

New Android Version! 4.4.2 KitKat OTA update received.

Hello, fellow XDA users! I just got an update notification from ASUS on my TF701T OTA. Here are a couple of pics as proof and basic version.
They have remade the UI completely, using their new ZenUI on the newer Transformers. I'm going to see what they've changed in further detail, but some older apps, like MyLibrary, are no longer supported. Also, this update is not on ASUS' website as of this moment. I'm not sure if they will upload it even... just like the last one.
If anyone else has this update, please post here and share if there is anything radically changed/fixed!

Giod news! Let me guess, TowelRoot not working anymore?

I've received the update as well. Towelroot does not seem to work after a short try.
Gesendet von meinem K00C mit Tapatalk

Changing to ZenUI may be the reason this took so long to happen. I'm still waiting to receive the update but I'm looking forward to it. Good to see they haven't abandoned the TF701!

Bittersweet. There is an update but root through towelroot is gone. I'm on the fence on this one.
TF701 / TF700 / NEXUS 7 (2013)

I hope sbdags can update CROMI-X with this...

Can somebody please try the different towelroot versions on the latest OTA? Please? Please?
TF701 / TF700 / NEXUS 7 (2013)

Devolution1x said:
I hope sbdags can update CROMI-X with this...
Click to expand...
Click to collapse
He will if they release the firmware...
Can someone grab the OTA file before installing it? It should be in some temp folder. Not sure where unfortunately..
What's the best/worst about the Zen UI?

Unbelievable... I thought for sure ASUS had abandoned us! This is great, unexpected news!
Yes -- someone *needs* to upload that OTA file so our devs can take advantage of the new build. In fact, the file should be thrown up on a repository for anyone to try!

Good news - looks like CROMi-X lives!! Version 7 as soon as I an get my hands on it

hitmancho said:
Hello, fellow XDA users! I just got an update notification from ASUS on my TF701T OTA. Here are a couple of pics as proof and basic version.
They have remade the UI completely, using their new ZenUI on the newer Transformers. I'm going to see what they've changed in further detail, but some older apps, like MyLibrary, are no longer supported. Also, this update is not on ASUS' website as of this moment. I'm not sure if they will upload it even... just like the last one.
If anyone else has this update, please post here and share if there is anything radically changed/fixed!
Click to expand...
Click to collapse
Can you please tel me if you are stil able to connect usb drive and read/write from that ???

aravindun said:
Can you please tel me if you are stil able to connect usb drive and read/write from that ???
Click to expand...
Click to collapse
I just tried it and it worked (I opened a video from a flash drive I have). But there is something peculiar now:
At first, I plugged the drive in the USB 3.0 port and I got a notification about inserted storage media. I opened it from there and it went into the stock ASUS File Manager. From there everything was a-OK. Then I tried opening it from ES File Explorer. The USBdisk1 was there and everything was as it should be but there was another "drive" below my flash drive. It was just a string of numbers. When I tried opening it, ES asked if I wanted it to be the default manager for this drive. I just said "yes" and then it blurted out an error that the drive couldn't be opened. From there on the USB flash drive just disappeared. A simple unplug and plug back in fixed that problem. Nothing was even damaged. The random-string-of numbers-drive was still there upon replug, though.
tl;dr: Everything works for me but there is SOMETHING ASUS might've changed around.
If your flash drives don't open, first try the tried method of plugging the docked tablet into power, turning it off, booting into recovery, unplugging for a short while so you can navigate the menu, going to the "cold-boot" option (middle button), pressing it and IMMEDIATELY plugging the power back in as it is cold booting. It usually fixes any dock ailments I might have (until I dock it in a few times ). If that doesn't help you, the most radical measure is to factory reset the tablet while it is docked and IN the power outlet. If all else fails, try your warranty...

berndblb said:
He will if they release the firmware...
Can someone grab the OTA file before installing it? It should be in some temp folder. Not sure where unfortunately..
Click to expand...
Click to collapse
I grabbed the OTA update file from cache folder.
Here is the link:
https://www.mediafire.com/?va5a4h3u4r60wju

downloading now
i hope it speeds up the transformer, mines been lagging recently
and my dock is dodgy waiting for asus to approve rma, maybe this update will fix? lets see
any reviews on the update for those who installed it?

gg777 said:
I grabbed the OTA update file from cache folder.
Here is the link:
https://www.mediafire.com/?va5a4h3u4r60wju
Click to expand...
Click to collapse
How to install this file?

Rikodu said:
How to install this file?
Click to expand...
Click to collapse
You can't - it will attempt to patch the stock rom and will fail

sbdags said:
You can't - it will attempt to patch the stock rom and will fail
Click to expand...
Click to collapse
Thank you @sbdags that is exactly what I experienced... Cromix soon?

Quick launch asus apps are gone
Looks like they removed this stuff.... Not sure how I feel about it, on one hand, I never really used that stuff... On the other, removing features is never a situation that I applaud. Anyone know if you can re-enable the quick launch?

Rikodu said:
Thank you @sbdags that is exactly what I experienced... Cromix soon?
Click to expand...
Click to collapse
As soon as Asus put the full firmware on their site
I can't get the kernel otherwise - and too difficult to work out their patched ota system
---------- Post added at 10:00 PM ---------- Previous post was at 09:59 PM ----------
jordanmw said:
Looks like they removed this stuff.... Not sure how I feel about it, on one hand, I never really used that stuff... On the other, removing features is never a situation that I applaud. Anyone know if you can re-enable the quick launch?
Click to expand...
Click to collapse
Hmm in a way I'm glad.
You won't get it back though as it was built into their framework - presumably not part of their zenui.

Yeah, I am glad in a way too, makes one less button that I accidently press because I picked up my wife's tf700 and think I am pressing "back". Just like Asus to remove a feature with an update... anyone remember when you could adjust your hdmi output on tf700 to scale or zoom? I do... still weeping for my lost feature.

Dual Boot!!!

So A While Back I Made A Youtube Video ON DualBooting Any Samsung Vibrent Phone. The Process Worked on all Devices i Tried It My Self
((( I Did Not Make This Process)))
So Like Most i Had To Get My Hands On The S5 For Really No Reason.
As Soon As I Picked It Up Out Of The Box It Went Straight To Rooting
There Arent To Many Good AOSP Roms Out There For The S5 Just Yet But There Are Some Great TouchWiz ...
My Favorite Being
Echoe Rom http://forum.xda-developers.com/showthread.php?t=2719593
Echoe Rom Was One Of the Roms I Used For My Dual Boot On The S4 So I Decided I Was Going To Give The Exact Same Process A Chance On My S5 .....
And It WORKED!!
I Uninstalled It For Now Due To My Dissatisfaction With All AOSP Roms For Now But As Soon As I Find One I Like Im Defenatly Doin This.
Here Is a Link To My Video I Made On YouTube.
There Is a Link To The Original Thread There And All Of The Nessicary Files In The Discription
https://www.youtube.com/watch?v=IPGd4TPSB5w
none of this is my work just found out that it works
the original thread is here
http://forum.xda-developers.com/showthread.php?t=2447534
yeah its for the s4 and the app will say s4 but it worked for me and im an on the tmobile s5

If this is really working, then well done!

I just came from the S4 and used the same process for dual booting. I will try it out now and post my results. I'm assuming you used chenxiaolong's Dual Boot Patcher to patch the AOSP rom?
How did you patch your secondary ROM?

I'm going to have to try this!

Any update on this did it work? I want to dual boot pac-rom!

How come you can figure out dual booting but cant comprehend capital letters

OP use chenxiaolong's Dual Boot Patcher from this S4 thread:
http://forum.xda-developers.com/showthread.php?t=2447534
He didn't mentioned about it. Also Youtube tutorial is for Galaxy S4 and links to download doesn't work. I wouldn't risk trying to do that on S5 it sounds like a BS to me.

Download Links Down
Can you update your download links. The first and last one say file not found.

-PiLoT- said:
How come you can figure out dual booting but cant comprehend capital letters
Click to expand...
Click to collapse
haha :good:

brickman7713 said:
Can you update your download links. The first and last one say file not found.
Click to expand...
Click to collapse
http://d-h.st/4MR
you can use this sorry about that

Update
the dev changed a few things recently like the patcher and swticher app are now in one
the only app you need is the patcher
the download links have been changed on my site
the Patcher app will not make the dualboot file if it is on your sd card you would have to transfer to the device first
few aosp roms work with the app but you can still do it manually
Workin on it
im also working on making a video showing that this works but im procrastinating lol sorry

[email protected] said:
Update
the dev changed a few things recently like the patcher and swticher app are now in one
the only app you need is the patcher
the download links have been changed on my site
the Patcher app will not make the dualboot file if it is on your sd card you would have to transfer to the device first
few aosp roms work with the app but you can still do it manually
Workin on it
im also working on making a video showing that this works but im procrastinating lol sorry
Click to expand...
Click to collapse
So it should work if I dual boot CM 11 and Phoenix ROM?

candreva87 said:
So it should work if I dual boot CM 11 and Phoenix ROM?
Click to expand...
Click to collapse
yes sir im running cm11 and echeo righ now
but you would have to patch them manually wich is still very simple

Can you please link me a guide?

Have anyone except the op tried this?
Verstuurd vanaf mijn SM-G900F met Tapatalk

idk why but i would of never thought it would be possible with a phone

Lemosine said:
idk why but i would of never thought it would be possible with a phone
Click to expand...
Click to collapse
tried to patch the cyanogenmod nightlty and it says failed to patch file failed to patch ramdisk nontype object has no attribute content

I would try it, if someone can guarantee that this method works on G900F

Hey guys, I'm the author of the Galaxy S4 DualBootPatcher app.
I just want to point out that this is currently working purely by chance. ROMs with updater-scripts that refer to the named partitions (eg. "/dev/block/platform/msm_sdcc.1/by-name/boot") are safe to try, but any ROM that uses the partition numbers directly (eg. "/dev/block/platform/msm_sdcc.1/mmcblk0p16") have a chance of bricking the phone irrecoverably because the partition table does not match the Galaxy S4's.
In the next version of the patcher, I will be adding support for the S5 and the Note 3. Until then, I do not recommend dual booting

12650
Lemosine said:
idk why but i would of never thought it would be possible with a phone
Click to expand...
Click to collapse
And I've just been sitting here wondering why it wasn't yet.
Now if I could dual boot ubuntu and android.

The FCT's of coolpad

Hello every on !
Today I am here to share details of my research on the Coolpad Note 3 stock ROM method to implement fingerprint.
This is mainly targeted on fingerprint.
The thing coolpad has enabled new is "fct". I call it new because i haven't see any such in other device.
On close examining the factory_init.rc of the boot image, i have found a service to activate a file with name "fctd", which has been using to activate the libraries "fct_*" of the lib{,64} of the system mount point.
So, how actually is this factory_init.rc called, The coolpad note 3's ramdisk has a file with name multi_init in the sbin directory, which is again activated by "init". This init is obviously loaded by the bootloader initially.
So the fctd plays a major role in the fingerprint. Based on these , I have enabled fingerprint on custom ROMs of the coolpad. :angel:
The software team of coolpad wanted things to be seperated, so that if there exists any problem with any segment, they can fix them easily, that is the main reason they have implemented this fct's.
Any corrections to this are accepted
Hope fellow developers would gain some knowledge from what i shared, and also correct me if iam wrong

Good findings.
Keep up ?

kuberrocks96 said:
Good findings.
Keep up
Click to expand...
Click to collapse
Thanks
Few more things will be in the next update of the post

Is this yours? https://www.androidfilehost.com/?w=files&flid=134358&sort_by=date&sort_dir=DESC
Have you enabled FP for it?

ForgottenDude said:
Is this yours? https://www.androidfilehost.com/?w=files&flid=134358&sort_by=date&sort_dir=DESC
Have you enabled FP for it?
Click to expand...
Click to collapse
Yes. That is mine.
I don't recommend you tot use them unless you are well knowledged

pinnamanivenkat said:
Thanks
Few more things will be in the next update of the post
Click to expand...
Click to collapse
pinnamanivenkat said:
Hello every on !
Today I am here to share details of my research on the Coolpad Note 3 stock ROM method to implement fingerprint.
This is mainly targeted on fingerprint.
The thing coolpad has enabled new is "fct". I call it new because i haven't see any such in other device.
On close examining the factory_init.rc of the boot image, i have found a service to activate a file with name "fctd", which has been using to activate the libraries "fct_*" of the lib{,64} of the system mount point.
So, how actually is this factory_init.rc called, The coolpad note 3's ramdisk has a file with name multi_init in the sbin directory, which is again activated by "init". This init is obviously loaded by the bootloader initially.
So the fctd plays a major role in the fingerprint. Based on these , I have enabled fingerprint on custom ROMs of the coolpad. :angel:
The software team of coolpad wanted things to be seperated, so that if there exists any problem with any segment, they can fix them easily, that is the main reason they have implemented this fct's.
Any corrections to this are accepted
Hope fellow developers would gain some knowledge from what i shared, and also correct me if iam wrong
Click to expand...
Click to collapse
Bro plz provide the files to fix fp for coolpad note 3 lite also. Thanks for this.

Mmverma said:
Bro plz provide the files to fix fp for coolpad note 3 lite also. Thanks for this.
Click to expand...
Click to collapse
Presently, What every works on Note 3 should work on Note 3 lite also. So try the fix patch which i have provided and reply back if that works.
https://www.androidfilehost.com/?fid=529152257862701421

Nope its not working in cpn3l

pinnamanivenkat said:
Yes. That is mine.
I don't recommend you tot use them unless you are well knowledged
Click to expand...
Click to collapse
Thanks for the reply.
I'm familiar with rooting and flashing Custom ROMs. Currently have a Moto G 2014 rooted and with LineageOS 14.1, and a Redmi Note 4 with LineageOS 13.
What's working and what's not in your ROM?
Sent from my Redmi Note 4 using XDA Labs

How to use the fingerprint_fix ?

pinnamanivenkat said:
Presently, What every works on Note 3 should work on Note 3 lite also. So try the fix patch which i have provided and reply back if that works.
https://www.androidfilehost.com/?fid=529152257862701421
Click to expand...
Click to collapse
Will the fix work on Lineage OS unofficial 14.1 ?
What ROM are you using currently ?

About ur lineage os 7.1 zip.
I tried to flash it. It say something is unable to mount, ending up with error 7

It says invalid Zip
Can you please help me how to install the zip?

bro its not working i tried it..more you tell me.....bro i also compared one stock rom and custom rom...i also found fctd and fct_fingerprint like this new......i inserted them in the custom roms...fp still not works......
---------- Post added at 06:46 PM ---------- Previous post was at 06:37 PM ----------
shankydilse121 said:
Can you please help me how to install the zip?
Click to expand...
Click to collapse
Bro u need to add meta inf file to make it a flashable zip..........
Use This:good::good:
https://forum.xda-developers.com/showthread.php?t=1221003

Help Building Oreo Custom Rom for A6 Plus 2018 ( A605FN ) !!!

Hello guys. I'm trying to build custom rom based on stock rom using assayed kitchen. i prepared the files of stock firmware so they can be readed from kitchen. everything looks good but i have only one problem.
the app extracts the files, but i get the error FAILED TO GET [file_contexts]... I found file_contexts.bin into the fota.zip archive. but i dont know how to convert it to file_contexts text and then where to place it so the app can read it.
can anyone with more knowledge help with this?? thank you in advance!!

ariber14 said:
Hello guys. I'm trying to build custom rom based on stock rom using assayed kitchen. i prepared the files of stock firmware so they can be readed from kitchen. everything looks good but i have only one problem.
the app extracts the files, but i get the error FAILED TO GET [file_contexts]... I found file_contexts.bin into the fota.zip archive. but i dont know how to convert it to file_contexts text and then where to place it so the app can read it.
can anyone with more knowledge help with this?? thank you in advance!!
Click to expand...
Click to collapse
I can provide you with the tool to convert it, however SuperR kitchen can already do this.

That would be wonderful. I will try the same procedure with SuperR!

ariber14 said:
That would be wonderful. I will try the same procedure with SuperR!
Click to expand...
Click to collapse
It depends whether you wish to work with Windows or preferably Linux?

ashyx said:
It depends whether you wish to work with Windows or preferably Linux?
Click to expand...
Click to collapse
Windows are easier.i'm not good with command lines etc:cyclops:

ariber14 said:
Windows are easier.i'm not good with command lines etc:cyclops:
Click to expand...
Click to collapse
I have used this tool in the past:
https://forum.xda-developers.com/tools/general/filecontexts-bin-converter-t3565910

ashyx said:
I have used this tool in the past:
https://forum.xda-developers.com/tools/general/filecontexts-bin-converter-t3565910
Click to expand...
Click to collapse
this converter not work for oreo unfortunately.

ariber14 said:
this converter not work for oreo unfortunately.
Click to expand...
Click to collapse
Read the thread there is an update for Oreo.

ashyx said:
Read the thread there is an update for Oreo.
Click to expand...
Click to collapse
i did bro. as i told you the links for oreo converter are dead

ariber14 said:
i did bro. as i told you the links for oreo converter are dead
Click to expand...
Click to collapse
Then all I can suggest is this for Linux. I don't do much of this stuff on Windows.
https://forum.xda-developers.com/android/general/cofface-filecontexts-bin-filecontexts-t3669824

ashyx said:
Then all I can suggest is this for Linux. I don't do much of this stuff on Windows.
https://forum.xda-developers.com/android/general/cofface-filecontexts-bin-filecontexts-t3669824
Click to expand...
Click to collapse
i dont have linux. so i cannot convert file_contexts.bin..... :crying:

ariber14 said:
i dont have linux. so i cannot convert file_contexts.bin..... :crying:
Click to expand...
Click to collapse
You can run Linux in a VM such as VIRTUAL BOX or VMWARE.
You could also use WSL, but personally have never used it.
https://docs.microsoft.com/en-us/windows/wsl/install-win10
Prebuilt VM images can be found below:
https://www.osboxes.org

ariber14 said:
i dont have linux. so i cannot convert file_contexts.bin..... :crying:
Click to expand...
Click to collapse
i'm successful deodex with superR kitchen with ubuntu 64 bit. very simple and now booted....but kinda laggy hahaha..
and first booting also maybe took around 20 mins i gezz

an-_-dro said:
i'm successful deodex with superR kitchen with ubuntu 64 bit. very simple and now booted....but kinda laggy hahaha..
and first booting also maybe took around 20 mins i gezz
Click to expand...
Click to collapse
Congratulations!! you'll find a way to make it faster.even with some tweakings to kernel.
i would like to know if there is a video on how to make a custom rom from stock oreo android. i've done it on nougat, but not oreo and why not even android pie. can't find e decent tutorial

ariber14 said:
Congratulations!! you'll find a way to make it faster.even with some tweakings to kernel.
i would like to know if there is a video on how to make a custom rom from stock oreo android. i've done it on nougat, but not oreo and why not even android pie. can't find e decent tutorial
Click to expand...
Click to collapse
i also have a plan to make custom and also my first mod deal with oreo, deodexed already booted and so far so good. the only problem is really laggy at the begining but more u use/open apps, restart and so on..the lag become decrease and now "almost" as normal/odexed speed..
for making custom rom i gez no different with previous android..find the right tool to deodex, then edit desired apk with desired mod then pack it

I was trying to build also a custom ROM with Assayed Kitchen , but same problem with context bin file .
Even with the stock firmware , with TWRP installed and rooted with magisk 18.0 , the first 3 or 4 boot takes longer , but i think there is something inside the new Oreo firmware which recognize that you delete some applications , and after few reboots , the phone is very fast and battery keeps more than 40-46 hours ... which for me it is a very satisfied,
I used Assayed Kitchen for SM-J730GM... SM-T585 ..SM-T560...SM-G900F ...SM-J710FN , and made for myself very fast and battery friendly ROM"S , but i will keep digging to find a way to build one for SM-A605FN ...
I will let you know if i will find something new .
And if you are willing to try a modified mixer_paths.xml in order to have a very nice and loud sound on speakers and Bluetooth i will attached for you .
You need to added in " / vendor / etc " folder and give 644 permission .
Please let me know your opinion , so maybe we can share it after !!!:good::good::good:

balanadi said:
I was trying to build also a custom ROM with Assayed Kitchen , but same problem with context bin file .
Even with the stock firmware , with TWRP installed and rooted with magisk 18.0 , the first 3 or 4 boot takes longer , but i think there is something inside the new Oreo firmware which recognize that you delete some applications , and after few reboots , the phone is very fast and battery keeps more than 40-46 hours ... which for me it is a very satisfied,
I used Assayed Kitchen for SM-J730GM... SM-T585 ..SM-T560...SM-G900F ...SM-J710FN , and made for myself very fast and battery friendly ROM"S , but i will keep digging to find a way to build one for SM-A605FN ...
I will let you know if i will find something new .
And if you are willing to try a modified mixer_paths.xml in order to have a very nice and loud sound on speakers and Bluetooth i will attached for you .
You need to added in "system / vendor / etc " folder and give 644 permission .
Please let me know your opinion , so maybe we can share it after !!!:good::good::good:
Click to expand...
Click to collapse
assayyed not working on oreo but superR kitchen on ubuntu 64bit very handy..less than 2 minutes to completely deodex 8.0.

an-_-dro said:
assayyed not working on oreo but superR kitchen on ubuntu 64bit very handy..less than 2 minutes to completely deodex 8.0.
Click to expand...
Click to collapse
Every time i make a custom rom and i deodex it,it says already deodexed next to each file. I wonder why?
I believe now we need someone to make a custom kernel with tweeks for battery and performance. 3500 battery and we could make it last much longer. I believe this is a must right now.
balanadi said:
And if you are willing to try a modified mixer_paths.xml in order to have a very nice and loud sound on speakers and Bluetooth i will attached for you .
You need to added in "system / vendor / etc " folder and give 644 permission .
Please let me know your opinion , so maybe we can share it after !!!:good::good::good:
Click to expand...
Click to collapse
I copyied your file to the directory you mentioned. There was already a file with the same name there. I suppose yours has some changes though i didn't notice anything in the sound. After the restart google services show error once in a while.... then i installed viper4android fx from magics modules. After restart my sim signal was lost. V4a showed at apps.i can open it but the driver wont work.i removed it and sim signal came back!! So we still need to make some tests till we find a working v4a....

I was wondering why you got the google service error and viper , so i doubled verify and the file should be in "/vendor/ etc" not in "/system/ / vendor / etc " . And i did modify very carefully each value from original 84 value to 90 in most cases and from 81 to 85 in some headphone values ...
I really apologize for the mistake i did regarding the place of the file where to add it .
You can try again to see if you see any difference .
You have attached some pictures about the place and modifications ..

ariber14 said:
Every time i make a custom rom and i deodex it,it says already deodexed next to each file. I wonder why?
....
Click to expand...
Click to collapse
probably your deodexer not compatible with oreo. i remember when using assayed kitchen i also experienced like that.
use superR

[CLOSED] Fix ambient display single tap and double tap to wake up

Sorry in advance if the thread is not the correct one and for my English.
I wanted to report that following the procedure to reactivate the "pocket mode" that you can find here, the ambient display and the double touch to wakes up, begin to be working always, even after several days that I enabled the function and without restarting the phone, it wakes up immediately.
I have no idea why Oneplus has disabled the "pocket mode" function, to avoid bugs and fix the problem with the ambient display and double touch, waiting for an official fix, I followed the procedure by reactivating the feature but I left the "pocket mode" off and, until now, everything works fine.
I have successfully tested the fix on my Oneplus 7 with Open Beta 15.
IMPORTANT: to carry out the reactivation of the "pocket mode" it is necessary to be rooted

Thank you for your information !
I made a magisk module for my device ( 7 Pro on OB15) to turn on the Pocket Mode option and everything worked !!

dijia1124 said:
Thank you for your information !
I made a magisk module for my device ( 7 Pro on OB15) to turn on the Pocket Mode option and everything worked !!
Click to expand...
Click to collapse
A simple solution solves a really annoying bug... :good:

dijia1124 said:
Thank you for your information !
I made a magisk module for my device ( 7 Pro on OB15) to turn on the Pocket Mode option and everything worked !!
Click to expand...
Click to collapse
Can share module? pls

Winstarshl said:
Can share module? pls
Click to expand...
Click to collapse
Only tested on 7Pro Open Beta 15, maybe the file should be modified again after several system updates

Winstarshl said:
Can share module? pls
Click to expand...
Click to collapse
dijia1124 said:
Only tested on 7Pro Open Beta 15, maybe the file should be modified again after several system updates
Click to expand...
Click to collapse
Caution, the feature_list file changes with the firmware release, I noticed that in firmware open beta 13, in beta 14 and in beta 15 it was different every time...

dijia1124 said:
Only tested on 7Pro Open Beta 15, maybe the file should be modified again after several system updates
Click to expand...
Click to collapse
I have too Beta 15 and module work perfect) Thanks you!

dianoandr said:
Caution, the feature_list file changes with the firmware release, I noticed that in firmware open beta 13, in beta 14 and in beta 15 it was different every time...
Click to expand...
Click to collapse
Winstarshl said:
I have too Beta 15 and module work perfect) Thanks you!
Click to expand...
Click to collapse
Better check the feature_list file before every system update or may cause problems

thanks for the info .. i dont have any problem with oos t2w and i dont know whats yours
but its not working so well in custom roms. any idea how to fix it in custom roms?

Dark Fear said:
thanks for the info .. i dont have any problem with oos t2w and i dont know whats yours
but its not working so well in custom roms. any idea how to fix it in custom roms?
Click to expand...
Click to collapse
I'm sorry but I have never used custom rom or aosp rom, currently I have a beta 15 firmware, debloted, with some magisk modules, I have always modded on oxygen os based firmware

dijia1124 said:
Only tested on 7Pro Open Beta 15, maybe the file should be modified again after several system updates
Click to expand...
Click to collapse
tried this one on a oneplus7 with OB15 and the phone didn't boot anymore, if it happens to someone else I just had to boot into twrp and manually delete the module under " /data/adb/modules/" then rebooted normally

Fixed in Open Beta 16

thedamnone said:
Fixed in Open Beta 16
Click to expand...
Click to collapse
This is how it is described in the beta 16 firmware changelog but it really doesn't seem to me that it still works as it should work ... the awakening is not always immediate.
For me, the fix proposed in this thread is still the best choice ... it's just a personal opinion

same issue once
lol i had the same issue with them , i had to turn off double tap to wakeup feature than only my ambient display would work so i guess O.O.S has some unresolved bugs.

GnyanadBhatt said:
lol i had the same issue with them , i had to turn off double tap to wakeup feature than only my ambient display would work so i guess O.O.S has some unresolved bugs.
Click to expand...
Click to collapse
Now I can say that with the two latest versions of the open beta firmware, it seems to work fine.
If you are still not satisfied with how it works, with the mod of the feature_list file, as reported in the first post, the situation improves a lot

I finally find myself sharing my bug! [emoji37] For several betas, stable EU and global that the double tap to wake up + facial does not work for me, which for me is the best way to activate the terminal.
I did not understand why with PIE it works perfectly? Pocket mode! [emoji3061] And I have tried everything like installing fastboot or msm Dowland versions, which is the closest thing to leaving the factory and at first clean it always works but when I install everything, it stops working ... [emoji2357]
With beta 18 it was animated and with b19 it works at 80% ...
I would like to activate with the line that is mentioned in the 1st post, xr I don't understand where it should be put? I suppose that with root and a file manager with permissions go to the path:
system/etc/feature_list*
And leave like this?
system/etc/featureName: OP_FEATURE_ENABLE_POCKETMODE_SWITCH
..... And leave the line like this?? I understand that .... then you can remove root and close bootloader without losing the line?
Cheers
Enviado desde mi GM1913 mediante Tapatalk

kacarot said:
I finally find myself sharing my bug! [emoji37] For several betas, stable EU and global that the double tap to wake up + facial does not work for me, which for me is the best way to activate the terminal.
I did not understand why with PIE it works perfectly? Pocket mode! [emoji3061] And I have tried everything like installing fastboot or msm Dowland versions, which is the closest thing to leaving the factory and at first clean it always works but when I install everything, it stops working ... [emoji2357]
With beta 18 it was animated and with b19 it works at 80% ...
I would like to activate with the line that is mentioned in the 1st post, xr I don't understand where it should be put? I suppose that with root and a file manager with permissions go to the path:
system/etc/feature_list*
And leave like this?
system/etc/featureName: OP_FEATURE_ENABLE_POCKETMODE_SWITCH
..... And leave the line like this?? I understand that .... then you can remove root and close bootloader without losing the line?
Cheers
Enviado desde mi GM1913 mediante Tapatalk
Click to expand...
Click to collapse
You have to edit the feature_list file, I act at the end of the file by editing the text in this way,
from so:
},
{
"featureName": "OP_FEATURE_MM_ULTRASOUND"
}
]
to so:
},
{
"featureName": "OP_FEATURE_MM_ULTRASOUND"
},
{
"featureName": "OP_FEATURE_ENABLE_POCKETMODE_SWITCH"
}
]
Be careful to follow the correct syntax and spacing as per stock file!
To do this, you need root privileges, a file manager that allows you to act on system partitions and a text editor. I recommend extracting the file, editing it on the PC and then returning it to the smartphone, then replace the stock file and the correct permissions must be assigned.
Once your smartphone has restarted you should be done.
If once you have made the change, you lock the bootloader, the phone is wiped attention.
Honestly no idea if the change survives a reset, i never tried
Cheers

dianoandr said:
You have to edit the feature_list file, I act at the end of the file by editing the text in this way,
from so:
},
{
"featureName": "OP_FEATURE_MM_ULTRASOUND"
}
]
to so:
},
{
"featureName": "OP_FEATURE_MM_ULTRASOUND"
},
{
"featureName": "OP_FEATURE_ENABLE_POCKETMODE_SWITCH"
}
]
Be careful to follow the correct syntax and spacing as per stock file!
To do this, you need root privileges, a file manager that allows you to act on system partitions and a text editor. I recommend extracting the file, editing it on the PC and then returning it to the smartphone, then replace the stock file and the correct permissions must be assigned.
Once your smartphone has restarted you should be done.
If once you have made the change, you lock the bootloader, the phone is wiped attention.
Honestly no idea if the change survives a reset, i never tried
Cheers
Click to expand...
Click to collapse
Can you send your edited feature_list file sir

hungthanhMT said:
Can you send your edited feature_list file sir
Click to expand...
Click to collapse
Sure,
I am attaching the feature_list extracted from Oneplus 7 Pro OxygenOS Open Beta 19 firmware, modified by adding the string necessary to enable the "Pocket mode" feature.
It is important to know that this feature_list file changes with each firmware release so it is not possible to use it universally on all versions of OxygenOS, it is good that it is used as a reference to edit what you use on the your firmware.
I compressed the file to be able to upload it into the thread, IT IS NOT A FLASHABLE FILE, it must be extracted and copied manually, assigning the correct permissions to the file.
If you want to use the attached file, remember that it only works on Oneplus 7 Pro with Open Beta 19 firmware, if you want to add the "pocket mode" feature on other firmware, you have to extract your "feature_list" file and modify it as explained in the article and using my file as a template . I repeat this file is different on each firmware and is different in each Oneplus phone model (changes based on hardware features).
Don't forget that if the file is not edited correctly or you use a file extracted from a different firmware than the one you are using, you risk bootloop!
DO EVERYTHING AT YOUR OWN RISK!

Thread closed on request of OP @dianoandr as the OP doesn't possess the device any longer!