Related
MY FIRST WORK
This port is working on "SM-A500G" .. I Think it should work in all variants...
Just Flash it in Recovery
VERSION 3 ADDED!! With Some Improvements!
LINK : http://www.mediafire.com/download/mr265a555bum254/S6+System+UI+MM+Mode+v3+By+RijuZz.zip
TO HIDE S FINDER :
Use Wannam Xposed Module
OR
1 - Download ES FILE EXPLORER or a similar file explorer.
2 - (ES FILE EXPLORER) Open the app, slide from left to right, scroll down and enable Root Explorer, grant superuser permission.
3 - Go to " /system/etc/permissions/ "
4 - Find the file " com.sec.feature.findo.xml ", copy it to another folder and then delete the original.
5 - Reboot!
Enjoy
Thanks
works for A300FU as well...
doesnt seem to work with themes, but all the ports dont anyway.
thanks
Good work. ...
Please try to theme s finder n quick connect background too.....
How do you hide s finder and quick connect? Is there any such option?
pmaneeshp said:
Good work. ...
Please try to theme s finder n quick connect background too.....
Click to expand...
Click to collapse
I forget to theme s finder bg.. To hide s finder, use wannam xposed module
avigyan04 said:
How do you hide s finder and quick connect? Is there any such option?
Click to expand...
Click to collapse
Use Wannam Xposed Module
mikeloury said:
Thanks
Click to expand...
Click to collapse
Welcome
Version 2 added
Fixed S Finder Background
http://www.mediafire.com/download/x07epor7pmbayh0/S6+System+UI+MM+Mod+V2.zip
Screenshots please.
screenshots plzz ?
Nice work
Works on A500 FU, nice job
djosue1034 said:
Screenshots please.
Click to expand...
Click to collapse
Screenshot added
bilal_shaikh said:
screenshots plzz ?
Click to expand...
Click to collapse
Screenshot added
frumy said:
Works on A500 FU, nice job
Click to expand...
Click to collapse
Thankz mate
marcosge_ said:
Nice work
Click to expand...
Click to collapse
Thankz
Try to change the size of s finder bar....if it is done,it will be 100%.
To hide s finder & quick connect
Use Wannam Xposed Module
OR
1 - Download ES FILE EXPLORER or a similar file explorer.
2 - (ES FILE EXPLORER) Open the app, slide from left to right, scroll down and enable Root Explorer, grant superuser permission.
3 - Go to " /system/etc/permissions/ "
4 - Find the file " com.sec.feature.findo.xml ", copy it to another folder and then delete the original.
5 - Reboot!
pmaneeshp said:
Try to change the size of s finder bar....if it is done,it will be 100%.
Click to expand...
Click to collapse
Am not an developer bro.. Jst tried to theme system ui
TO HIDE S FINDER :
Use Wannam Xposed Module
OR
1 - Download ES FILE EXPLORER or a similar file explorer.
2 - (ES FILE EXPLORER) Open the app, slide from left to right, scroll down and enable Root Explorer, grant superuser permission.
3 - Go to " /system/etc/permissions/ "
4 - Find the file " com.sec.feature.findo.xml ", copy it to another folder and then delete the original.
5 - Reboot!
I recently activated the Google Assistant on my OnePlus 2. Its a little different than installing on other devices.anyways, lets get started!
**I am not responsible for any problems in your device, This is just the method I used to activate Google Assistant for Myself(and my friends,worked every time!)**
Prerequisites:
1. Installed TWRP or CWM(in recovered)
2.Rooted OP2
3.Installed ES File Explorer!
4.Installed Android 7.x ROM.
How to get started:
Download the files from here : https://www.androidfilehost.com/?w=files&flid=121914
Put All files in same folder in your phone internal memory.
Thanks to @FaserF
Now...
1.Boot to Recovery.
2.Flash the Zip GoogleAssistantVelvet.zip
3.Flash the ZipGoogleAssistantBuildProp.zip (this will install the "tweak.prop" into your build.prop)
Now boot to your device.
4.Open ES file explorer and Activate "Root Explorer".
5.Mount R/W in memory , /system directory.
Here you will find the file "build.prop"
6.Remove these lines :
ro.product.brand=OnePlus
ro.product.name=OnePlus2
7.In the place of removed lines, add this-
ro.product.model=Pixel XL
Now save the changes.
Clear Data of your Google App.
Reboot your device.(not that important)
Tap the home Button and your Google Assistant will POP UP!
Tap on Thanks if I helped you!
Does OK GOOGLE works everytime?
sushant20 said:
I recently activated the Google Assistant on my OnePlus 2. Its a little different than installing on other devices.anyways, lets get started!
**I am not responsible for any problems in your device, This is just the method I used to activate Google Assistant for Myself(and my friends,worked every time!)**
Prerequisites:
1. Installed TWRP or CWM(in recovered)
2.Rooted OP2
3.Installed ES File Explorer!
4.Installed Android 7.x ROM.
How to get started:
Download the files from here : https://www.androidfilehost.com/?w=files&flid=121914
Put All files in same folder in your phone internal memory.
Thanks to @FaserF
Now...
1.Boot to Recovery.
2.Flash the Zip GoogleAssistantVelvet.zip
3.Flash the ZipGoogleAssistantBuildProp.zip (this will install the "tweak.prop" into your build.prop)
Now boot to your device.
4.Open ES file explorer and Activate "Root Explorer".
5.Mount R/W in memory , /system directory.
Here you will find the file "build.prop"
6.Remove these lines :
ro.product.brand=OnePlus
ro.product.name=OnePlus2
7.In the place of removed lines, add this-
ro.product.model=Pixel XL
Now save the changes.
Clear Data of your Google App.
Reboot your device.(not that important)
Tap the home Button and your Google Assistant will POP UP!
Tap on Thanks if I helped you!
Click to expand...
Click to collapse
Does your camera work? I tried an other method and it messed up my camera, because it only saved a green picture.
Akilesh Akil said:
Does OK GOOGLE works everytime?
Click to expand...
Click to collapse
yes it does!
trapistasajt said:
Does your camera work? I tried an other method and it messed up my camera, because it only saved a green picture.
Click to expand...
Click to collapse
I am using FireHound 7.0 and nothing seems broken to me because of Google Assistant!
Beware if you're on AICP, this locked up my phone, had to restore my backup again. If you're on AICP, just use the other Google Assistant thread and add the entries to build.prop yourself.
I've tried flashing these two files on 3 different ROMs with pico gapps--- Official RR 6.0.1, Graraks CM14, Firehound OS 7.0 but every time, the phone gets struck at 1+ bootlogo. I don't know what's going wrong. Please help.
1 more thing, while flashing the 2nd zip, some Error 1 appears in twrp.
Edit: its working good. I just didn't downloaded that tweak.prop. Now it works flawlessly!
Thanks!✌
Does it work on marshmallow ROMs?
amitgudwill said:
Does it work on marshmallow ROMs?
Click to expand...
Click to collapse
do you even read the requirements?
Just my two cents: there's no need to do any of that really to get Google assistant to work on Android N builds.
Just make sure that you have the latest version of the Google search app, then add these two lines to your build.prop file and reboot. After that, just clear Google search's data and then open the assistant using the same shortcut that you've used to open now on tap before(long press home by default), when asked about setting up "ok Google" select "I'll do it later"(to avoid crashes).
That's it
sar12330 said:
Just my two cents: there's no need to do any of that really to get Google assistant to work on Android N builds.
Just make sure that you have the latest version of the Google search app, then add these two lines to your build.prop file and reboot. After that, just clear Google search's data and then open the assistant using the same shortcut that you've used to open now on tap before(long press home by default), when asked about setting up "ok Google" select "I'll do it later"(to avoid crashes).
That's it
Click to expand...
Click to collapse
can u please explain which two lines to add? There is just one single line which is to be added in the build.prop.
The lines are:
ro.product.model=Pixel XL
ro.opa.eligible_device=true
After putting these in the build.prop and rebooting, clear Google search's data and the assistant should work
not working on Halogen OS 7.0
Just wanted to comment on the OP.
Adding the two lines works. No need to flash anything or delete any lines. It works just as on any other device.
At least on CM14/.1
Tried to activate assistant by put these two lines into build.prop... Seems to be OK but every time I finish voice recognition setup for "OK Google" and want to try it, it starts the setup again...
Any solution?
well can anyone try to help me ?
Resolved
vergilbt said:
Tried to activate assistant by put these two lines into build.prop... Seems to be OK but every time I finish voice recognition setup for "OK Google" and want to try it, it starts the setup again...
Any solution?
Click to expand...
Click to collapse
It's normal, voice recognition isn't working with this method.
@casual_kikoo
Thanks a lot for your information... Could you point me to the right way? The way from op?
vergilbt said:
@casual_kikoo
Thanks a lot for your information... Could you point me to the right way? The way from op?
Click to expand...
Click to collapse
In fact, no way for now.
sushant20 said:
I recently activated the Google Assistant on my OnePlus 2. Its a little different than installing on other devices.anyways, lets get started!
**I am not responsible for any problems in your device, This is just the method I used to activate Google Assistant for Myself(and my friends,worked every time!)**
Prerequisites:
1. Installed TWRP or CWM(in recovered)
2.Rooted OP2
3.Installed ES File Explorer!
4.Installed Android 7.x ROM.
How to get started:
Download the files from here : https://www.androidfilehost.com/?w=files&flid=121914
Put All files in same folder in your phone internal memory.
Thanks to @FaserF
Now...
1.Boot to Recovery.
2.Flash the Zip GoogleAssistantVelvet.zip
3.Flash the ZipGoogleAssistantBuildProp.zip (this will install the "tweak.prop" into your build.prop)
Now boot to your device.
4.Open ES file explorer and Activate "Root Explorer".
5.Mount R/W in memory , /system directory.
Here you will find the file "build.prop"
6.Remove these lines :
ro.product.brand=OnePlus
ro.product.name=OnePlus2
7.In the place of removed lines, add this-
ro.product.model=Pixel XL
Now save the changes.
Clear Data of your Google App.
Reboot your device.(not that important)
Tap the home Button and your Google Assistant will POP UP!
Tap on Thanks if I helped you!
Click to expand...
Click to collapse
The build.prop uses UNIX endlines. Does es even support those?
is it possible to change dpi in miui without having weird icons .
Camlin3 said:
is it possible to change dpi in miui without having weird icons .
Click to expand...
Click to collapse
Use any file explorer like Es explorer etc.
Go to /system/build.prop
Add this line in the build.prop
ro.sf.lcd_density=the value you want.
Save the file and reboot
gulshanstrider said:
Use any file explorer like Es explorer etc.
Go to /system/build.prop
Add this line in the build.prop
ro.sf.lcd_density=the value you want.
Save the file and reboot
Click to expand...
Click to collapse
Done already cause icon got distorted like a small square protude seperate from whole icon.
Use easy dpi changer from playstore. Then add/modify ro.sf.lcd_density=x in build.prop in case the dpi change messes up icons and images in apps.
adizz4 said:
Use easy dpi changer from playstore. Then add/modify ro.sf.lcd_density=x in build.prop in case the dpi change messes up icons and images in apps.
Click to expand...
Click to collapse
Ok i will try again,but i ran into other problem in nougat roms ,i cant edit any txt file via es file explorer integrated text editor,pls have a look ,is it app bug ? Sorry screenshot not uploading .it says error occured while saving file and create a tmp file with same name in directory.
Camlin3 said:
Ok i will try again,but i ran into other problem in nougat roms ,i cant edit any txt file via es file explorer integrated text editor,pls have a look ,is it app bug ? Sorry screenshot not uploading .it says error occured while saving file and create a tmp file with same name in directory.
Click to expand...
Click to collapse
Flash latest supersu and try, someone else had the same problem.
I use root explorer and sr1 2.79 ssu and everything works fine.
(assuming you're trying to edit build.prop)
Use imgur or some other image host to share images, xda upload seems to be broken rn.
adizz4 said:
Flash latest supersu and try, someone else had the same problem.
I use root explorer and sr1 2.79 ssu and everything works fine.
(assuming you're trying to edit build.prop)
Use imgur or some other image host to share images, xda upload seems to be broken rn.
Click to expand...
Click to collapse
No ,its in nougat ,even a txt file in sdcard cant be edited with es file explorer.in mm ,it works fine.
Camlin3 said:
No ,its in nougat ,even a txt file in sdcard cant be edited with es file explorer.in mm ,it works fine.
Click to expand...
Click to collapse
That's really weird.
You could try a different app I guess.
adizz4 said:
That's really weird.
You could try a different app I guess.
Click to expand...
Click to collapse
Ya i know ,it seems like app bug,i used fx file explorer.
Camlin3 said:
No ,its in nougat ,even a txt file in sdcard cant be edited with es file explorer.in mm ,it works fine.
Click to expand...
Click to collapse
Use Kernel Auditor or Build prop editor app
gulshanstrider said:
Use Kernel Auditor or Build prop editor app
Click to expand...
Click to collapse
I am only enquiring abt es file explorer ,other goes well
Thanks for reply
here's a full youtube tutorial that doesn't affect icons
https://www.youtube.com/watch?v=btabIccFrHY
This is the all in one zip file with some extra functionality for honor 6x.
The file will give you some useful utilities like hw intelligent , call record , autorun, hp plugin, music with cutter, parent control.
REQUIREMENT:
1. ROOT , TWRP RECOVERY.
2. ANY ROOT EXPLORER.
STEPS:
1. OPEN ANY ROOT EXPLORER AND NAVIGATE TO SYSTEM/PRIV-APP/GOOGLE PACKAGE INSTALLER
2. DELETE THE FOLDER GOOGLE PACKAGE INSTALLER.
3. REBOOT TO RECOVERY , FLASH THE DOWNLOADED ZIP .
THATS IT , YOU HAVE DONE IT.
Download links below :
http://gestyy.com/wrLHXH
screenshots
http://gestyy.com/wrLGLz
Thanks
XDA:DevDB Information
EXTRA UTILITIES FOR HONOR 6X, Tool/Utility for the Honor 6X
Contributors
Khan ubaid
Version Information
Status: Testing
Created 2017-11-05
Last Updated 2017-11-05
It doesn't work on 6X BLN21, bootloop on start after flashed the zip !
MiPiMok said:
It doesn't work on 6X BLN21, bootloop on start after flashed the zip !
Click to expand...
Click to collapse
You can go for manual setup ,
1. Extract the zip file, you will get HwCallrecord, HwParent, HwIntelligent under system/app
and PackageInnstaller, HwMediacenter, HpPlugin under system/priv-app.
2. Copy these files in corresponding directory by using any root explorer under root/system/app and root/ystem/priv-app.
3. If you want package installer with autorun and backgroung run facility, you have to delete the GooglePackageInstaller under /root/system/priv-app/GooglePackageInstaller.
4.Give permission to the apk files as well as folders, How? go through screenshots.
5. Reboot, Enjoy
Any queries, you can ask....
Remember to give permission to every folders and files you place or replace...
MiPiMok said:
It doesn't work on 6X BLN21, bootloop on start after flashed the zip !
Click to expand...
Click to collapse
Permission to odex file also...
http://q.gs/Dx2KW
Done ! And it works, thanks.
Welcome buddy...
Hi, I've got problem with HwParent and HwIntelligent, how install them if they are not installed in the original ROM...because I can't install them normally...package corrupt it says me....
you cannot install them normally, they have to be placed in the system partition and changing the permission as i have already given the screenshots...
Thank you
Hey,
thank you for explaining the manual way - that helped me a lot and also fixed a second problem i have had.
The problem was, that after the update my FM Radio was gone.
I found the app here but i cant push files by ADB as root. So i just installed doing the same way:
i copied the apk to an own folder to /system/app/ , set permissions, rebbooted and it worked perfect.
all your apps are working too.
Except the parental controll - i didnt install it because nothing planned yet... ^^
starkeeper2018 said:
Hey,
thank you for explaining the manual way - that helped me a lot and also fixed a second problem i have had.
The problem was, that after the update my FM Radio was gone.
I found the app here but i cant push files by ADB as root. So i just installed doing the same way:
i copied the apk to an own folder to /system/app/ , set permissions, rebbooted and it worked perfect.
all your apps are working too.
Except the parental controll - i didnt install it because nothing planned yet... ^^
Click to expand...
Click to collapse
Thats good.... keep it up,,
and about parent control should work too, after installing by the given procedure is done,,, you will find it under setting/additional setting /student mode
Khan ubaid said:
you cannot install them normally, they have to be placed in the system partition and changing the permission as i have already given the screenshots...
Click to expand...
Click to collapse
OK sorry, it was badly asked... I did it as you explained and I succeed to install them but I can't find where to activate them... Now, I find the parent control in the advanced settings with the "student app" with the last post and it works but where I can find or activate the "intelligent" smart assistance app ? And about the package installer, I pasted it in the priv-app file but what happens now ?
MiPiMok said:
OK sorry, it was badly asked... I did it as you explained and I succeed to install them but I can't find where to activate them... Now, I find the parent control in the advanced settings with the "student app" with the last post and it works but where I can find or activate the "intelligent" smart assistance app ? And about the package installer, I pasted it in the priv-app file but what happens now ?
Click to expand...
Click to collapse
After you paste the package installer and gave permission , you have to delete( or cut to make a copy of ) google package installer,,, it will be activated when you remove google package installer folder in the same directory
link dead
Link dead need mirror for the same
.
does anybody have the apps from the link?
can someone reupload it?
Stock ROM has problem with bluetooth aptx codec. If bluetooth device supports both, aptx and aac, than aac preffered.
Solvetion is to disable aac codec for bluetooth connections in build.prop
If you have root, just add string to build.prop:
persist.bt.a2dp.aac_disable=true
Don't forget to set permissions to 755.
Than reboot.
Another not tested variant:
change persist.vendor.btstack.a2dp_offload_cap=sbc-aptx-aptxhd-aac
to persist.vendor.btstack.a2dp_offload_cap=sbc-aac-aptx-aptxhd
In this variant aac stay enabled
Hey! Could you explain it very simply? I have root and BuildProp Editor, but I have never used it, I do not have the lines you typed and I do not understand what is this 755?
figer said:
Hey! Could you explain it very simply? I have root and BuildProp Editor, but I have never used it, I do not have the lines you typed and I do not understand what is this 755?
Click to expand...
Click to collapse
Use buildprop editor, you should add if it is not there already and set permissio to rw- r-- r-- . Es file explorer has built in buildprop editor and ability to set required system files permission, or you can use any other app with similar function. Please find attachment to get better idea.
changed it and saved, but after restart buildprop file is as before edition.
Any idea?
I did this , it is not working unfortunately
figer said:
changed it and saved, but after restart buildprop file is as before edition.
Any idea?
Click to expand...
Click to collapse
Bronnel said:
I did this , it is not working unfortunately
Click to expand...
Click to collapse
You need to check that changes are saved in build.prop
And check the permissions of file, they should be 755
figer said:
Hey! Could you explain it very simply? I have root and BuildProp Editor, but I have never used it, I do not have the lines you typed and I do not understand what is this 755?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
No need to use permissions. Just add the line, save and reboot.
Sent from my LG-H932 using XDA Labs
---------- Post added at 09:23 AM ---------- Previous post was at 09:21 AM ----------
Aptahar said:
Stock ROM has problem with bluetooth aptx codec. If bluetooth device supports both, aptx and aac, than aac preffered.
Solvetion is to disable aac codec for bluetooth connections in build.prop
If you have root, just add string to build.prop:
persist.bt.a2dp.aac_disable=true
Don't forget to set permissions to 755.
Than reboot.
Click to expand...
Click to collapse
Might just be better to post this link,
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
tell people to copy
persist.bt.a2dp.aac_disable=true
And add it in the app. Save and reboot.
Sent from my LG-H932 using XDA Labs
Aptahar said:
You need to check that changes are saved in build.prop
And check the permissions of file, they should be 755
Click to expand...
Click to collapse
I change the 755, adds a row. I save everything.
Validating - for sure by opening the file again. A new row is added. The file has permission for execute - it is 755.
I restart the phone.
After reboot, the BuildProp file is 644 again, and the added row in it is not there !!!
As if the system was restoring the file before the changes during the system reboot.
I have root and changes I made in BuildProp Editor and a normal text editor, changing permissions to the file using Root Browser.
Each time after reboot the changes are reversed.
figer said:
I change to 755, adds a line "persist.bt.a2dp.aac_disable" with value=true . I save everything.
I check for certainty by opening the file. A new row is added. The file has permission for execute - it is 755.
I restart the phone.
After reboot, the BuildProp file is 644 again, and the added row in it is not there !!!
As if the system was restoring the file before the changes during the system reboot.
I have root and changes I made in BuildProp Editor and a normal text editor, changing permissions to the file using Root Browser.
Each time after reboot the changes are reversed.
Click to expand...
Click to collapse
Try to use Root Explorer, and when he asks to mount system as R/W, bump Yes.)
Root Explorer has built in text editor and permission changer.
Aptahar said:
You need to check that changes are saved in build.prop
And check the permissions of file, they should be 755
Click to expand...
Click to collapse
I already did this, still not working.
BROKEN1981 said:
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
No need to use permissions. Just add the line, save and reboot.
Sent from my LG-H932 using XDA Labs
---------- Post added at 09:23 AM ---------- Previous post was at 09:21 AM ----------
Might just be better to post this link,
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
tell people to copy
persist.bt.a2dp.aac_disable=true
And add it in the app. Save and reboot.
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
I tried this, it is not working, I even tried "persist.vendor.bt.a2dp.aac_disable=true" the same
Bronnel said:
I already did this, still not working.
I tried this, it is not working, I even tried "persist.vendor.bt.a2dp.aac_disable=true" the same
Click to expand...
Click to collapse
give me your build.prop
Aptahar said:
Try to use Root Explorer, and when he asks to mount system as R/W, bump Yes.)
Root Explorer has built in text editor and permission changer.
Click to expand...
Click to collapse
I made changes of permissions by Root Explorer - and then add the line by text editor build there - its wont save changes.
I copied buildprop file to sd card, edited, copied to system directory, changed permissions to 755, restarted and... file after restart is 644, and added line is gone. Recovered by something to default state
figer said:
I made changes of permissions by Root Explorer - and then add the line by text editor build there - its wont save changes.
I copied buildprop file to sd card, edited, copied to system directory, changed permissions to 755, restarted and... file after restart is 644, and added line is gone. Recovered by something to default state
Click to expand...
Click to collapse
That strange. What does Google says on it?
Aptahar said:
Try to use Root Explorer, and when he asks to mount system as R/W, bump Yes.)
Root Explorer has built in text editor and permission changer.
Click to expand...
Click to collapse
Yes, Root Explorer is the best.
I've used it for years.
Aptahar said:
give me your build.prop
Click to expand...
Click to collapse
sorry for my late reply , here is my unmodified build.prop
Bronnel said:
sorry for my late reply , here is my unmodified build.prop
Click to expand...
Click to collapse
Can you give cust.prop file from OP directory
Aptahar said:
Can you give cust.prop file from OP directory
Click to expand...
Click to collapse
here it is
Bronnel said:
here it is
Click to expand...
Click to collapse
Your files build.prop ans cust.prop doesn't contain any lines about aptx.
This codec supports on your device?
This trick with disabling AAC codec checked only on ROM for European devices
Aptahar said:
Your files build.prop ans cust.prop doesn't contain any lines about aptx.
This codec supports on your device?
This trick with disabling AAC codec checked only on ROM for European devices
Click to expand...
Click to collapse
Yes I definitely have aptx , I can select it in developer options