Hey guys, I don't think this needs a huge explanation, I made a module that replaces your emojis, with the new Android Q emojis.
Just flash it in Magisk and your good.
The module was broken, I removed it and will reupload a working version in a sec
Edit: new version uploaded, should install fine now!
Thanks dude
Will try it. Thank you so much!
so are they still coming?
These emojis don't even look like the android Q emojis
([emoji3590]09-09-18[emoji813])
Emoji
Emoji are installed but they dont show up when searching on GBoard
They don't show is GBoard emoji section but show up when we search for Emojis
KhizarrShahidd said:
They don't show is GBoard emoji section but show up when we search for Emojis
Click to expand...
Click to collapse
Are you on a Samsung device
([emoji3590]09-09-18[emoji3590])
PoochyX said:
Are you on a Samsung device
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
Yes, but its on LineageOS 16 and all the other emoji sets appear to work just fine.
KhizarrShahidd said:
Yes, but its on LineageOS 16 and all the other emoji sets appear to work just fine.
Click to expand...
Click to collapse
Damn these modifications always don't go off without an hitch
([emoji3590]09-09-18[emoji3590])
PoochyX said:
Damn these modifications always don't go off without an hitch
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
True that!
How we can fix it to make it work on Gboard?, please any idea would be appreciated (at the moment I went to an emoji website and copied each one of them and add each one to my personal dictionary ? ? if you can watch them at least your phone can support Unicode 12) you can pick between add them manually, or ask a merciful developer that give us a hand( pretty pretty please ?I am on Android N 7.1.2 thanks in advance), I add them manually with the NotoColorEmoji.ttf of Android Q but even the older emojis still didn't showed up in the right ratio in the keyboard, maybe it's a thing about adding a bypass that allows us to see the new emojis on the gboard, please any idea, support, help is more than welcome, thanks in advance
marlycious said:
How we can fix it to make it work on Gboard?, please any idea would be appreciated (at the moment I went to an emoji website and copied each one of them and add each one to my personal dictionary ? ? if you can watch them at least your phone can support Unicode 12) you can pick between add them manually, or ask a merciful developer that give us a hand( pretty pretty please ?I am on Android N 7.1.2 thanks in advance), I add them manually with the NotoColorEmoji.ttf of Android Q but even the older emojis still didn't showed up in the right ratio in the keyboard, maybe it's a thing about adding a bypass that allows us to see the new emojis on the gboard, please any idea, support, help is more than welcome, thanks in advance
Click to expand...
Click to collapse
Hey, sorry for the late reply, you could try clearing Gboards data
PoochyX said:
Are you on a Samsung device
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
Is there a problem with samsung devices? I have a galaxy note 4. So it won't work for me?
ialeixop said:
Is there a problem with samsung devices? I have a galaxy note 4. So it won't work for me?
Click to expand...
Click to collapse
With some Samsung devices, I'm not really sure which so you can try
Related
Hi,
i am perfectly fine with stock ROM and only one thing i would like to have beside. And it is Google phone app with capability to do search nearby places right from the phone app and the capability to see who actually calling behind unknown number.
I see some apks on apkmirror, but latest nonnexus apk is from 2016. So i rather ask here first. Do you guys tried this app and can confirm it has all the features i would like to have? Is it possible to have this app on our phone?
Do you have link to app for our device?
Thank you
https://www.apkmirror.com/uploads/?q=google-phone
I pulled this from OpenGapps. Flash the following Google dialer framework in TWRP and install it from the playstore... All the features work for me.
atrac17 said:
I pulled this from OpenGapps. Flash the following Google dialer framework in TWRP and install it from the playstore... All the features work for me.
Click to expand...
Click to collapse
Tried this without success. Running lineageos 8.0.
edit2: actually it doesn't work. Givs me a device not supported error
HatchetJackk said:
Tried this without success. Running lineageos 8.0.
edit2: actually it doesn't work. Givs me a device not supported error
Click to expand...
Click to collapse
Possible operator error. Also, this isn't designed for Oreo to begin with.
atrac17 said:
Possible operator error. Also, this isn't designed for Oreo to begin with.
Click to expand...
Click to collapse
How is it possible user error if it wasn't designed for Oreo? you never mentioned what os it was meant for. In any case, it did not, in fact, work for Oreo. However I did successfully use it for 7. Thanks for your work.
HatchetJackk said:
How is it possible user error if it wasn't designed for Oreo? you never mentioned what os it was meant for. In any case, it did not, in fact, work for Oreo. However I did successfully use it for 7. Thanks for your work.
Click to expand...
Click to collapse
At first, I was saying it's an operator error because it does work. Of course it doesn't work for Oreo it clearly states the date when I pulled the framework in May. The OP was asking to use an updated dialer in stock. I provided him the framework with the ability to do so.... I wouldn't specify why because I was answering the OP.
atrac17 said:
At first, I was saying it's an operator error because it does work. Of course it doesn't work for Oreo it clearly states the date when I pulled the framework in May. The OP was asking to use an updated dialer in stock. I provided him the framework with the ability to do so.... I wouldn't specify why because I was answering the OP.
Click to expand...
Click to collapse
Understood. Hopefully you can understand my side, as well. Again, thanks for your work.
PumaPerez said:
Hi,
i am perfectly fine with stock ROM and only one thing i would like to have beside. And it is Google phone app with capability to do search nearby places right from the phone app and the capability to see who actually calling behind unknown number.
I see some apks on apkmirror, but latest nonnexus apk is from 2016. So i rather ask here first. Do you guys tried this app and can confirm it has all the features i would like to have? Is it possible to have this app on our phone?
Do you have link to app for our device?
Thank you
https://www.apkmirror.com/uploads/?q=google-phone
Click to expand...
Click to collapse
You can check my thread.. I've ported the google dialer to non rooted devices
https://forum.xda-developers.com/mo...-161735957-t3636608/post73025780#post73025780
abhishekiswithyou said:
You can check my thread.. I've ported the google dialer to non rooted devices
https://forum.xda-developers.com/mo...-161735957-t3636608/post73025780#post73025780
Click to expand...
Click to collapse
How do I use this app, if I've a rooted device, pls assist, thanks :good:
talk2indrajit said:
How do I use this app, if I've a rooted device, pls assist, thanks :good:
Click to expand...
Click to collapse
same procedure as non rooted devices, Install as normal apk
I can confirm that it works on Moto G5 Plus (Sanders), stock rom, rooted with Magisk. Installed the dialer framework from the post by @atrac17 above, then phone apk (v.11) from here. (Play Market installation was still showing as unavailable for my device.) Then all I needed to do was to change the default phone app to google phone rather than Moto. Thanks for your help, guys. Couldn't figure it out by myself.
So freaking annoying we have to do this!.. Why on earth do we need Moto's dialer?!
Noto Emoji with Blobs enabled
This repository is intended to continue the development of the Blob emojis which have been abandoned by the original creators in 2017.
My goal is to upgrade the Blob emojis with a fresh style which is consistent to other emoji vendors.
Another thing is that this emoji set includes some emojis and ZWJ-sequences which are not part of the current emoji standard (although some or most of them are about to be included in the upcoming Unicode-standard), which means it might be one of the biggest emoji sets currently available! NotoColorEmoji fonts are provided by C1710's project.
NOTICE
You should use latest Magisk Manager to install this module. If you meet any problem under installation from Magisk Manager, please try to install it from recovery.
https://github.com/Magisk-Modules-Repo/blobmoji
What program did you use to edit the Oreo emojis? I tried Emoji Tools but it doesn't work with the Oreo fonts.
InfiDim42 said:
What program did you use to edit the Oreo emojis? I tried Emoji Tools but it doesn't work with the Oreo fonts.
Click to expand...
Click to collapse
I don't change any fonts. Please read the source code of my module first.
Downgrade
Can I downgrade the module?
I updated recently and I don't like the new Android Oreo Emojis.
Cypher_01 said:
Can I downgrade the module?
I updated recently and I don't like the new Android Oreo Emojis.
Click to expand...
Click to collapse
Me too! So why not try this module?
Edit: ops I didn't understand. Sorry for my bad English.
That's the effect of my module. It prefers blob emojis in nougat than O emoji. So that we wouldn't meet fonts missing problem in other "replacing only" module.
If someone could blob-ify the new emojis manually, could they be added to this module? (or to a fork)
IganSchacht said:
If someone could blob-ify the new emojis manually, could they be added to this module? (or to a fork)
Click to expand...
Click to collapse
Sure. I will do anything possible for the person who would like to do that for community.
Here's an album I found on Reddit a while ago. It's impressive. https://imgur.com/a/yb13F
There should be a way to edit one of the .ttf files.
I'm not sure what you mean with blob or blob-ify, the emojis are just a font file.
Anyway, I decided to go a different way and used an app called Emoji Changer. It simply backups and replaces the font file using root. The downside compared to a Magisk module is, that the system partition needs to be changed. But this is no problem for me.
@simonsmh You maybe want to create more versions of your module, one for each emoji font (Android Nougat, Android Oreo, maybe more).
As I said, I installed the module and used and liked my Android Nougat emojis. Then an update arrived, I installed it, and had the Android Oreo emojis, which I don't like.
So, is it possible to downgrade a Magisk module in general?
Cypher_01 said:
I'm not sure what you mean with blob or blob-ify, the emojis are just a font file.
Anyway, I decided to go a different way and used an app called Emoji Changer. It simply backups and replaces the font file using root. The downside compared to a Magisk module is, that the system partition needs to be changed. But this is no problem for me.
@simonsmh You maybe want to create more versions of your module, one for each emoji font (Android Nougat, Android Oreo, maybe more).
As I said, I installed the module and used and liked my Android Nougat emojis. Then an update arrived, I installed it, and had the Android Oreo emojis, which I don't like.
So, is it possible to downgrade a Magisk module in general?
Click to expand...
Click to collapse
I can't generally understand your meaning. Now does your device have both two emoji like the screen shot I posted above or you just can't see any blob emoji (Android N emoji) and you can only see Android O emoji?
To test it, please visit https://emojipedia.org/emoji-4.0/ and you should see that there is showing up blob emoji. While in https://emojipedia.org/emoji-5.0/ you could see that all the emoji comes from Android O emoji. That's the normal effect that this module does.
There are huge amounts of fonts replacing module, already made by other developer, only if you don't need emoji compatibility.
IganSchacht said:
Here's an album I found on Reddit a while ago. It's impressive. https://imgur.com/a/yb13F
There should be a way to edit one of the .ttf files.
Click to expand...
Click to collapse
That is amazing!
BTW, @kcls said he would do that job, too.
simonsmh said:
I can't generally understand your meaning. Now does your device have both two emoji like the screen shot I posted above or you just can't see any blob emoji (Android N emoji) and you can only see Android O emoji?
To test it, please visit https://emojipedia.org/emoji-4.0/ and you should see that there is showing up blob emoji. While in https://emojipedia.org/emoji-5.0/ you could see that all the emoji comes from Android O emoji. That's the normal effect that this module does.
There are huge amounts of fonts replacing module, already made by other developer, only if you don't need emoji compatibility.
Click to expand...
Click to collapse
Sorry, I should have mentioned, that I'm on Android Marshmallow.
My situation is/was:
Especially when using Hangouts, on my Phone I have the old Marshmallow emojis, on my PC I have the new (obviously already old) Android Nougat emojis. I wanted them to match. So I installed your module, I think 1 or 2 months ago, then I had matching emojis (replaced, not added), great. The problem started with the last update of the module, I think about 2 weeks ago.
Let me get this right, that your module simply replaces NotoColorEmoji.ttf, correct? If yes, there's nothing to add, read my last post again.
Concerning this blob stuff, sorry, I don't understand this. I'm not experienced in fonts and emojis. I tried both links and I see emojis on the first link (emoji-4.0) and I don't see emojis on the second link (emoji-5.0).
HTH
Cypher_01 said:
Sorry, I should have mentioned, that I'm on Android Marshmallow.
My situation is/was:
Especially when using Hangouts, on my Phone I have the old Marshmallow emojis, on my PC I have the new (obviously already old) Android Nougat emojis. I wanted them to match. So I installed your module, I think 1 or 2 months ago, then I had matching emojis (replaced, not added), great. The problem started with the last update of the module, I think about 2 weeks ago.
Let me get this right, that your module simply replaces NotoColorEmoji.ttf, correct? If yes, there's nothing to add, read my last post again.
Concerning this blob stuff, sorry, I don't understand this. I'm not experienced in fonts and emojis. I tried both links and I see emojis on the first link (emoji-4.0) and I don't see emojis on the second link (emoji-5.0).
HTH
Click to expand...
Click to collapse
That is probably a bug. Please post up your /magisk/.core/fonts.xml
You should also consider mixing Nougat blobs with EmojiOne 3.1 (and later versions).
I feel like they fit the blobs well, even though they are not as flat as they used to be.
robotkoer said:
You should also consider mixing Nougat blobs with EmojiOne 3.1 (and later versions).
I feel like they fit the blobs well, even though they are not as flat as they used to be.
Click to expand...
Click to collapse
You could do that with replacing notocoloremoji-old.ttf in /magisk/notocoloremoji-replacer/system/fonts after installation by your self.
Hello. Id like to use this, but for some reason both phones I've tried it on bootloop eventually. I can't seem to find .core/fonts.xml and the one in the module's etc folder is 0 bytes.
One of those is probably the issue, guess i should mention I don't see a .core at all. I do have 'view hidden files' on.
Both phones are arm64. One is a Nexus 5x and the other is a Huawei Honor 8, U.S. versions.
BerserkLeon said:
Hello. Id like to use this, but for some reason both phones I've tried it on bootloop eventually. I can't seem to find .core/fonts.xml and the one in the module's etc folder is 0 bytes.
One of those is probably the issue, guess i should mention I don't see a .core at all. I do have 'view hidden files' on.
Both phones are arm64. One is a Nexus 5x and the other is a Huawei Honor 8, U.S. versions.
Click to expand...
Click to collapse
Remove magisk completely and try again should solve this problem. Also please upload fonts.xml
This is great, thanks. Replaced Samsung emojis with blobs on my A520F running 7.0 with Magisk v15.2, and I also have none blobs for the new 5.0 emojis.
Homemade NotoColorEmoji with Blobs finally comes in v3.0! Thanks @thayerfox!
Hey guys. I was faced with a problem where iOS devices get updated to new iOS versions extremely quickly and with these updates sometimes comes new emojis. In the latest iOS 12.1 beta 2 Apple added support for unicode 11 emojis and as soon as the update is out of beta and released publicly most iOS devices will have the latest unicode 11 emojis. Android devices on the other hand are stuck with whatever emoji set their device manufacture sets for them and have no option of changing them or even updating them to the latest unicode versions without rooting and replacing the file themselves.
In an attempt to be ready for when unicode 11 emojis roll out iOS devices, I have extracted the pngs from the latest AppleColorEmoji.ttc file and have built a font that works on Android.
Features:
Latest unicode 11 emojis
Latest emojis from iOS 12.1 Beta 2
Issues:
The biggest emoji size that was extracted from the file was 96x96 so emojis might be a little small
Download:
My module has been upload to the Magisk repo so you can install it through the Magisk app on your phone
or you can download the file and flash it manually through your custom recovery.
iOS 12.1 Beta 2 Emojis
Sources:
Magisk repo
This is incredible! Can you suggest the simpld keyboard which is support the unicode 11? Except the gboard, because before I use the gboard actually all the emojis from this module are visible, but the gboard makes my device slow. And now I using the xperia keyboard right now, but still missing some emojis from this module. Thanks
RagilWic said:
This is incredible! Can you suggest the simpld keyboard which is support the unicode 11? Except the gboard, because before I use the gboard actually all the emojis from this module are visible, but the gboard makes my device slow. And now I using the xperia keyboard right now, but still missing some emojis from this module. Thanks
Click to expand...
Click to collapse
I've heard that SwiftKey has updated their keyboard to support unicode 11 emojis but I can't be sure because I only use gboard. In time most keyboards should be updated to support unicode 11 emojis
Thank you!
[email protected]@!3Z said:
I've heard that SwiftKey has updated their keyboard to support unicode 11 emojis but I can't be sure because I only use gboard. In time most keyboards should be updated to support unicode 11 emojis
Click to expand...
Click to collapse
It's tru I'm using the magisk ios emojis on my SwiftKey keyboard [emoji3434][emoji3436]
[emoji3436] I Will Sacrifice For Those That I Love [emoji3434]
Will you be updating this when iOS 12.1 is released? I noticed that Apple has already updated the new bagel emoji and there might be some other changes from beta to release. Thanks for your work already though, the 12.1 beta emojis show up just fine for me on Gboard. Thanks again!
ahamling27 said:
Will you be updating this when iOS 12.1 is released? I noticed that Apple has already updated the new bagel emoji and there might be some other changes from beta to release. Thanks for your work already though, the 12.1 beta emojis show up just fine for me on Gboard. Thanks again!
Click to expand...
Click to collapse
Once iOS 12.1 has been fully released and I can find the AppleColorEmoji.ttc file with a list of changes Apple made then I'll update it, currently it's just too much effort to update all the images in the file when only some have been changed
[email protected]@!3Z said:
Once iOS 12.1 has been fully released and I can find the AppleColorEmoji.ttc file with a list of changes Apple made then I'll update it, currently it's just too much effort to update all the images in the file when only some have been changed
Click to expand...
Click to collapse
Thanks man! Keep up the good work.
PoochyX said:
It's tru I'm using the magisk ios emojis on my SwiftKey keyboard [emoji3434][emoji3436]
[emoji3436] I Will Sacrifice For Those That I Love [emoji3434]
Click to expand...
Click to collapse
What vesion of Swiftkey are you using? I dont see all the ios 11 emojis on the version that im on. swiftkey 7.1.5.23
[email protected]@!3Z said:
Hey guys. I was faced with a problem where iOS devices get updated to new iOS versions extremely quickly and with these updates sometimes comes new emojis. In the latest iOS 12.1 beta 2 Apple added support for unicode 11 emojis and as soon as the update is out of beta and released publicly most iOS devices will have the latest unicode 11 emojis. Android devices on the other hand are stuck with whatever emoji set their device manufacture sets for them and have no option of changing them or even updating them to the latest unicode versions without rooting and replacing the file themselves.
In an attempt to be ready for when unicode 11 emojis roll out iOS devices, I have extracted the pngs from the latest AppleColorEmoji.ttc file and have built a font that works on Android.
Features:
Latest unicode 11 emojis
Latest emojis from iOS 12.1 Beta 2
Issues:
The biggest emoji size that was extracted from the file was 96x96 so emojis might be a little small
Download:
My module has been upload to the Magisk repo so you can install it through the Magisk app on your phone
or you can download the file and flash it manually through your custom recovery.
iOS 12.1 Beta 2 Emojis
Sources:
Magisk repo
Click to expand...
Click to collapse
noob question.... does this change the system font or the font the gboard uses?
ogsho said:
noob question.... does this change the system font or the font the gboard uses?
Click to expand...
Click to collapse
No it won't, I haven't added the file which tells your device which font to use so everything should be the same as before just with your emojis changed to iOS 12.1
@[email protected]@!3Z
Can you explain me ?
Is there a difference between these two modules ?
BreckZeBoulay said:
@[email protected]@!3Z
Can you explain me ?
Is there a difference between these two modules ?
Click to expand...
Click to collapse
The one that isn't installed is the first module I uploaded, the one that you installed was originally iOS 11.1 emojis but I gave the creator of that module permission to use my file so anyone with his module just needs to update the module without installing a new module.
They are both essentially the same thing
I can't find your module in the magisk app ?
Mr.Jktra said:
I can't find your module in the magisk app ?
Click to expand...
Click to collapse
You need Magisk v17+, searching iOS should bring up 2 results And they are both the same so feel free to install either one
[email protected]@!3Z said:
You need Magisk v17+, searching iOS should bring up 2 results And they are both the same so feel free to install either one
Click to expand...
Click to collapse
Oh, I Don't know that I need v17 to find it in the download section thx m8
will this work with magisk v14.0 by flashing it through twrp?
MysteriousVoltz said:
will this work with magisk v14.0 by flashing it through twrp?
Click to expand...
Click to collapse
No it won't, it checks your magisk version and will tell you to install 17+
If you want to stay on magisk v14 and want the emojis then you're going to have to do it manually which means it won't be a module anymore.
To do it manually you have to download the file, extract it and navigate to system>font in the extracted file and copy the notocoloremoji.ttf from there to your system>font folder on your device and replace it. Then set the permission to 0644 and restart
Just got Magisk v17 today. It works perfectly, thank you! ?
it doesnt work on my device. it's android lollipop 5.1 by the way. i've tried to install it manually but it still doesnt work. it keeps showing square box with question mark. does anyone have solution to this? thank you
Hi guys! Did anybody make Good Lock and modules work on our device?
Did you try to install lucky patcher to patch the os?
[email protected] said:
Did you try to install lucky patcher to patch the os?
Click to expand...
Click to collapse
Me - no. What for is Lucky Patcher needed, concerning Good Lock? Plus I'm unrooted.
madmaxmoscow said:
Me - no. What for is Lucky Patcher needed, concerning Good Lock? Plus I'm unrooted.
Click to expand...
Click to collapse
Here's the steps to install Good Lock apps on the M20. Need to be rooted and install lucky patcher. Same can be applied to the M30s.
https://forum.xda-developers.com/galaxy-m20/themes/guide-how-to-install-lock-apps-t4001017
Credit to the devs of M20.
[email protected] said:
Here's a thread for the steps to install Good Lock apps on the M20. Need to be rooted and install lucky patcher.
https://forum.xda-developers.com/galaxy-m20/themes/guide-how-to-install-lock-apps-t4001017
Click to expand...
Click to collapse
Thanks buddy, but I still have hope, that the stuff would be available on our device without root. Especially, root for our device is bugfull at the moment
Only nicelock and onehand is working....
vinayak.etx said:
Only nicelock and onehand is working....
Click to expand...
Click to collapse
Hi, how did you make Onehand and Nicelock work?
Lazy_Pickachu said:
Hi, how did you make Onehand and Nicelock work?
Click to expand...
Click to collapse
the latest nicelock and onehand from galaxy store is working.... check out... there no need to do any trick...
vinayak.etx said:
the latest nicelock and onehand from galaxy store is working.... check out... there no need to do any trick...
Click to expand...
Click to collapse
I'm sorry, but I'm not able to find it on the Galaxy Store.
Edit: Nevermind. Turns out I'm not really good at searching things on the internet.
You can dowload it from apkmirror and sign it with apk-signer. Then install goodlock and the modules. But it don't change anything in M30s
I Hope it will Work with Android 10.
No it's not working on 10 either
Gane11601043 said:
No it's not working on 10 either
Click to expand...
Click to collapse
That is very disappointing.
I need a little help for M30. Few days ago samsung released AOD(Always On Display) update in galaxy store which was showing error during install (on M30 devices) and then suddenly Samsung pull that update back from store but the update worked for M30s devices and sideloading apk doesn't work for M30. Only apk released through galaxy store will install as update for AOD. I request if anyone M30s user here who got update of AOD recently through glalaxy store could make a backup of it with any apk backup app and share that apk here. It would be a big favor for us M30 users. Thanks in advance.
how to sign apks?
ninhthuanntnt said:
You can dowload it from apkmirror and sign it with apk-signer. Then install goodlock and the modules. But it don't change anything in M30s
Click to expand...
Click to collapse
I downloaded NiceLock and downloaded the modules, but when i try to install the modules, it simply says "app not installed". Does signing apk remove the restriction of the device or something? Can I know how its done?
you can install using apk signer..but apps doesn't work
thanks
Gane11601043 said:
you can install using apk signer..but apps doesn't work
Click to expand...
Click to collapse
oh, ok. I gave up anyway. and the thing i've noticed is that m series use one UI 2 core whereas the high end samsung phones use One UI 2 full(or something like that). so probably samsung gives only basic features of the One UI.
Any update in this issue...I'm a M31s user, story is the same in here. Any way to make it work (nice lock or good lock) ?
dionysos77 said:
Any update in this issue...I'm a M31s user, story is the same in here. Any way to make it work (nice lock or good lock) ?
Click to expand...
Click to collapse
One ui core version not support goodlock or nice lock
Good morning, i'm on the pixel experience rom on my mi 9, and i have enabled the Google assistant 2.0 by making Google thinking that i have a pixel 4 XL (by modifying the build.prop file). But it doesn't have any ui. Someone know how to get the transparent ui please? Thank you in advance
Bro how u do that? And i hope u fix the ui for google assistant
Asapakyou01 said:
Bro how u do that? And i hope u fix the ui for google assistant
Click to expand...
Click to collapse
Hi, if your phone is rooted and you have an aosp rom (like pixel experience), you can install a root file explorer, like root explorer. Then go to /system/build.prop and change cepheus by flame in device, name and product, Mi 9 by Pixel 4 XL in model, and Xiaomi by Google in brand and manufacturer. Then save and reboot. After that, clean the data of the Google app, then try to trigger the google assistant. You should see a download screen, then the google assistant 2.0 will be enabled.
Ithink i already do it. Thank u sir. How about the continue conversation do u make it work?
Asapakyou01 said:
Ithink i already do it. Thank u sir. How about the continue conversation do u make it work?
Click to expand...
Click to collapse
To enable continue conversation, you only need to go to the google app > settings > Google assistant, and in the assistant tab, you will find the continue conversation category, where you can enable it for your phone. I hope that this will help you. Have a great day sir.
boubougaming said:
To enable continue conversation, you only need to go to the google app > settings > Google assistant, and in the assistant tab, you will find the continue conversation category, where you can enable it for your phone. I hope that this will help you. Have a great day sir.
Click to expand...
Click to collapse
Theres no option to tick it on my phone. Only shared devices i can on to continued conversation
Asapakyou01 said:
Theres no option to tick it on my phone. Only shared devices i can on to continued conversation
Click to expand...
Click to collapse
And in the google assistant languages settings, do you have only English US? It's require to get the new google assistant.
boubougaming said:
And in the google assistant languages settings, do you have only English US? It's require to get the new google assistant.
Click to expand...
Click to collapse
Thanks bro its working now its pretty cool
Hi boubougaming, can you please Post your complete build.prop file? Thanks!
boubougaming said:
Hi, if your phone is rooted and you have an aosp rom (like pixel experience), you can install a root file explorer, like root explorer. Then go to /system/build.prop and change cepheus by flame in device, name and product, Mi 9 by Pixel 4 XL in model, and Xiaomi by Google in brand and manufacturer. Then save and reboot. After that, clean the data of the Google app, then try to trigger the google assistant. You should see a download screen, then the google assistant 2.0 will be enabled.
Click to expand...
Click to collapse
cj182 said:
Hi boubougaming, can you please Post your complete build.prop file? Thanks!
Click to expand...
Click to collapse
Of course, here you are. It's from the latest build of evolutionX rom, but it will ne the same thing for pixel experience or derpfest ....
boubougaming said:
Hi, if your phone is rooted and you have an aosp rom (like pixel experience), you can install a root file explorer, like root explorer. Then go to /system/build.prop and change cepheus by flame in device, name and product, Mi 9 by Pixel 4 XL in model, and Xiaomi by Google in brand and manufacturer. Then save and reboot. After that, clean the data of the Google app, then try to trigger the google assistant. You should see a download screen, then the google assistant 2.0 will be enabled.
Click to expand...
Click to collapse
Is that working with other Xiaomi device? I have redmi note 5 pro and i use derpfest.
milpapa23 said:
Is that working with other Xiaomi device? I have redmi note 5 pro and i use derpfest.
Click to expand...
Click to collapse
Yeah, I think that it may work on any Android device with an aosp rom.
boubougaming said:
Yeah, I think that it may work on any Android device with an aosp rom.
Click to expand...
Click to collapse
did any one get the new ui to work too .
Even I'm not getting the ui. Let me know if there's any fix
sahil shetty said:
Even I'm not getting the ui. Let me know if there's any fix
Click to expand...
Click to collapse
after 26/02/2020 if you try to this method it wont work and on the google assistent download will give you an error
edit : after rebooting the phone its working , still no ui do just thef features
AmineNrr said:
after 26/02/2020 if you try to this method it wont work and on the google assistent download will give you an error
edit : after rebooting the phone its working , still no ui do just thef features
Click to expand...
Click to collapse
Yeah, i think that the ui is somewhere in the pixel 4 rom, but i can't see anything in an android dump of this phone.
Yesteday i have spoke with argraur, a developer that has enabled the next gen google assistant in his rom: https://forum.xda-developers.com/mi-8/development/rom-google-pixelrom-v3-0sep-mi-8-t3843356.
He told me how he did, but sadly it didn't worked on the mi 9. I have tested his method on the derpfest rom and on the phhusson's gsi. So for the moment, i don't know what to do, except waiting that google release it for more phones.
boubougaming said:
Yesteday i have spoke with argraur, a developer that has enabled the next gen google assistant in his rom: https://forum.xda-developers.com/mi-8/development/rom-google-pixelrom-v3-0sep-mi-8-t3843356.
He told me how he did, but sadly it didn't worked on the mi 9. I have tested his method on the derpfest rom and on the phhusson's gsi. So for the moment, i don't know what to do, except waiting that google release it for more phones.
Click to expand...
Click to collapse
can you tell us how he did it
AmineNrr said:
can you tell us how he did it
Click to expand...
Click to collapse
Yeah, you must follow the steps described here: https://www.reddit.com/r/GooglePixe..._enable_new_google_assistant_for_older_pixel/.
Then, from a google flame dump: https://github.com/AndroidDumps/goo...-user-10-QQ1D.200205.002-6084393-release-keys,
take in the product directory priv-app/systemuiGoogle, usr/srec/, etc/sysconfig and push it in the same directories on the mi 9. Then reboot your phone and clear the google app data if needed. Then you should have the next gen assistant. If it's not the case, make sure you have only supported languages checked in the google assistant languages settings. So good luck, and i hope that someone will succeed to enable it with the new ui.
boubougaming said:
Yeah, you must follow the steps described here: https://www.reddit.com/r/GooglePixe..._enable_new_google_assistant_for_older_pixel/.
Then, from a google flame dump: https://github.com/AndroidDumps/goo...-user-10-QQ1D.200205.002-6084393-release-keys,
take in the product directory priv-app/systemuiGoogle, usr/srec/, etc/sysconfig and push it in the same directories on the mi 9. Then reboot your phone and clear the google app data if needed. Then you should have the next gen assistant. If it's not the case, make sure you have only supported languages checked in the google assistant languages settings. So good luck, and i hope that someone will succeed to enable it with the new ui.
Click to expand...
Click to collapse
with the method that we use before I have the new google assistent just not with the ui ( I try some test and everything is working like GA 2.0 ) we are chasing perfection right now hhhhhh , anyway I will try this new methode and report back if its work