Hello. First of all in the FAQ it says update firmware. How do I do that? I'm running radon v 7 (the latest). Can anybody assist me please?
Wardoge said:
Hello. First of all in the FAQ it says update firmware. How do I do that? I'm running radon v 7 (the latest). Can anybody assist me please?
Click to expand...
Click to collapse
just flash updated firmware and youre good
No need to flash any firmware. Edit the status of persist.audio.fluence.voicecall in buildprop to 'false' and reboot your device.
Working solution
zeon321 said:
No need to flash any firmware. Edit the status of persist.audio.fluence.voicecall in buildprop to 'false' and reboot your device.
Click to expand...
Click to collapse
Worked for me! Thanks.
pratikbodkhe said:
Worked for me! Thanks.
Click to expand...
Click to collapse
try aosp extended rom.
zeon321 said:
No need to flash any firmware. Edit the status of persist.audio.fluence.voicecall in buildprop to 'false' and reboot your device.
Click to expand...
Click to collapse
Thanks!!! Solved my problem.
I too have similar problem in pure nexus ROM, i tried above thing it didnt work for me, also my ok google command is not working unless used with a headphone
zeon321 said:
No need to flash any firmware. Edit the status of persist.audio.fluence.voicecall in buildprop to 'false' and reboot your device.
Click to expand...
Click to collapse
Recently this issue started occurring and I used the given line to fix this issue.
Thanks
zeon321 said:
No need to flash any firmware. Edit the status of persist.audio.fluence.voicecall in buildprop to 'false' and reboot your device.
Click to expand...
Click to collapse
Could you explain what purpose does persist.audio.fluence.voicecall serve?
I see that changing it may solve the no-sound problem, but there's probably a reason it was initially set to "true". i'm curious because setting it to "false" may introduce problems somewhere else.
ninth4 said:
Could you explain what purpose does persist.audio.fluence.voicecall serve?
I see that changing it may solve the no-sound problem, but there's probably a reason it was initially set to "true". i'm curious because setting it to "false" may introduce problems somewhere else.
Click to expand...
Click to collapse
This line is for the noise cancellation in the device. But due to a bug, the device assumed all noise as background noise and blocked the sound. Setting it to false disables the noise cancellation.
Hi I just recently installed lineage os 16 and did change "true" to "false" but I still cannot hear from any voice calls
HirayaManawari said:
Hi I just recently installed lineage os 16 and did change "true" to "false" but I still cannot hear from any voice calls
Click to expand...
Click to collapse
same boat
makishart said:
same boat
Click to expand...
Click to collapse
Im still trying to figure out how to change it and also find the correct path for the file. My build.prop in system shows blank.
Edit: i found it under vendor but changing the values made no difference, my issue is i have sound on sim 1 but no sound on sim 2
zeon321 said:
No need to flash any firmware. Edit the status of persist.audio.fluence.voicecall in buildprop to 'false' and reboot your device.
Click to expand...
Click to collapse
Can I do the same in moto e5 plus with lineage os 18.1 and how?
What is the syntax in adb
Related
.
This is the place for Q&A, general discussions, and post-installation chat about JasmineROM. Please keep your personal issues that are not related to the development, such as themes and other stuff, here.
.
Looks great. Will drive it for a few days and report back if there's any issues.
Thanks for all of your hard work & our 1st ROM.
Will be a version for the D855 ?
drmspidi said:
Will be a version for the D855 ?
Click to expand...
Click to collapse
I don't have this device, but you may test it yourself. Make nandroid backup, clean flash & report me back! It doesn't flash any firmware images (kernel, modem, ... etc); so, it's safe to test on other devices. If you've any issues, you can restore your backup.
DPI Affect
Heard mention that the DPI change affects the quick circle case display......is this true, or would it affect this? If it does change, what can be done post flashing to regain quick circle proper display?
Thanks for the work, btw!!!
hsbadr said:
I don't have this device, but you may test it yourself. Make nandroid backup, clean flash & report me back! It doesn't flash any firmware images (kernel, modem, ... etc); so, it's safe to test on other devices. If you've any issues, you can restore your backup.
Click to expand...
Click to collapse
But isn' t only for Verizon ?
What kind of problem I may have ?
JasmineRom
drmspidi said:
But isn' t only for Verizon ?
What kind of problem I may have ?
Click to expand...
Click to collapse
Yes this Rom is for the Verizon VS985 variant but he just stated that it does not flash a kernel, modem, or recovery of any sort. So the worst thing that may happen is your device bootloops or you just may not have data, working WiFi or Bluetooth, or some other minor issue. It is relatively safe to flash on other devices to try so long as you have a Nandroid backup of a working or stock ROM.
willyjay said:
Heard mention that the DPI change affects the quick circle case display......is this true, or would it affect this? If it does change, what can be done post flashing to regain quick circle proper display?
Thanks for the work, btw!!!
Click to expand...
Click to collapse
It works fine for me, but I can create a flashable zip to revert to stock DPI, if needed.
drmspidi said:
But isn' t only for Verizon ?
Click to expand...
Click to collapse
Yes, some Verizon devices may work on other carriers.
drmspidi said:
What kind of problem I may have ?
Click to expand...
Click to collapse
Unpredictable, it may work perfect or with issues related to hardware drivers: mainly Mobile Data, WiFi, bluetooth, ... etc. It could be fixed though with a converter replacements (port).
acparker18 said:
Yes this Rom is for the Verizon VS985 variant but he just stated that it does not flash a kernel, modem, or recovery of any sort. So the worst thing that may happen is your device bootloops or you just may not have data, working WiFi or Bluetooth, or some other minor issue. It is relatively safe to flash on other devices to try so long as you have a Nandroid backup of a working or stock ROM.
Click to expand...
Click to collapse
Exactly.
add ons
Do you think you will be adding volume enhancements soon?
Loving the Rom. Just needs themes and home back up and restore enabled
Saw that you would be pushing 1.0.1 update for tether. Will this just be an update zip or will it require a full rom flash?
USB Debugging Doesn't Stick After Reboot
I attempted to get USB Debugging to stick after rebooting by adding this line to build.prop:
persist.service.adb.enable=1
I reset the permissions to rw-r-r after editing build.prop before I rebooted. No luck, still not remaining enabled after a reboot.
lawtalking said:
Saw that you would be pushing 1.0.1 update for tether. Will this just be an update zip or will it require a full rom flash?
Click to expand...
Click to collapse
1.01 or 1.1 will be an update zip to dirty flash...
The Great Dahli llama said:
I attempted to get USB Debugging to stick after rebooting by adding this line to build.prop:
persist.service.adb.enable=1
I reset the permissions to rw-r-r after editing build.prop before I rebooted. No luck, still not remaining enabled after a reboot.
Click to expand...
Click to collapse
I'm aware of this issues...
I hope you can get Aroma working later on. The only downside is the size of the rom for download. The only bloat I find useful on this phone is multi window, knock on, and the clipboard. I hope to see some kind of volume enhancement as well.
wes53177 said:
Do you think you will be adding volume enhancements soon?
Click to expand...
Click to collapse
jerbear2011 said:
Loving the Rom. Just needs themes and home back up and restore enabled
Click to expand...
Click to collapse
eraursls1984 said:
I hope you can get Aroma working later on. The only downside is the size of the rom for download. The only bloat I find useful on this phone is multi window, knock on, and the clipboard. I hope to see some kind of volume enhancement as well.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Sure, at some point a new release of JasmineROM will include all requested features
Oh also the Verizon variants messaging app doesn't allow you to choose vibe pattern if there's a way you could enable that it would be awesome.
Sent from my Bump'd VS985 4G
I've got the itch to do a bit of themeing. Do you guys use the G3 TweaksBox themes? Im considering building for that since it is cross ROM compatible.
It will be a black/grey/orange theme using the Numix Cinnamon theme as inspiration.
Would there be an issue if I change the DPI to the original value.
I don't like the one with the ROM, and I can't get used to it.
What would be the best way to go about it?
jerbear2011 said:
Oh also the Verizon variants messaging app doesn't allow you to choose vibe pattern if there's a way you could enable that it would be awesome.
Click to expand...
Click to collapse
will look into it...
PiousInquisitor said:
I've got the itch to do a bit of themeing. Do you guys use the G3 TweaksBox themes? Im considering building for that since it is cross ROM compatible.
It will be a black/grey/orange theme using the Numix Cinnamon theme as inspiration.
Click to expand...
Click to collapse
Most apps/themes should work with this ROM since it's deodexed, except carrier-related apps: messaging, *telephony*, ... etc. I'll make my own themes & a list of compatible themes later.
Umbrella Corp said:
Would there be an issue if I change the DPI to the original value.
I don't like the one with the ROM, and I can't get used to it.
What would be the best way to go about it?
Click to expand...
Click to collapse
1.0.1 includes what you want; http://forum.xda-developers.com/showpost.php?p=56028380&postcount=129
This ROM ROCKS!!!! Thx!!!!
I wrote this for myself but here it is in case anyone is also interested.
Google sets the wifi country code to whatever is in your sim card. If the country does not have a corresponding list of enabled 5GHz frequencies, then a lot of these frequencies get disabled. This mod simply sets the country code to US. There is no GUI or anything, just enable and restart and you're all set. Android marshmallow only. I tested it on my S7 edge and it's working fine.
Enjoy.
Edit: Added OREO 8.1 version. Testing working on Pixel 2 XL.
madmack said:
I wrote this for myself but here it is in case anyone is also interested.
Google sets the wifi country code to whatever is in your sim card. If the country does not have a corresponding list of enabled 5GHz frequencies, then a lot of these frequencies get disabled. This mod simply sets the country code to US. There is no GUI or anything, just enable and restart and you're all set. Android marshmallow only. I tested it on my S7 edge and it's working fine.
Enjoy.
Click to expand...
Click to collapse
android4.4 cannot open
madmack said:
I wrote this for myself but here it is in case anyone is also interested.
Google sets the wifi country code to whatever is in your sim card. If the country does not have a corresponding list of enabled 5GHz frequencies, then a lot of these frequencies get disabled. This mod simply sets the country code to US. There is no GUI or anything, just enable and restart and you're all set. Android marshmallow only. I tested it on my S7 edge and it's working fine.
Enjoy.
Click to expand...
Click to collapse
awesome thankx
我是一个卒 said:
android4.4 cannot open
Click to expand...
Click to collapse
did you read OP's post properly ?
There is no GUI or anything, just enable and restart and you're all set.
BytesReverser said:
did you read OP's post properly ?
There is no GUI or anything, just enable and restart and you're all set.
Click to expand...
Click to collapse
sorry,my english is poor
I've been trying to find a fix ever since i got this phone and your module fixed it with no hassle
Thank you very much
Can i have your permission to share this on Mi A1 forums and xiaomi subreddit?
berezker said:
I've been trying to find a fix ever since i got this phone and your module fixed it with no hassle
Thank you very much
Can i have your permission to share this on Mi A1 forums and xiaomi subreddit?
Click to expand...
Click to collapse
Sure thing. If I can ask you to please link to this post and not share the APK.
madmack said:
Sure thing. If I can ask you to please link to this post and not share the APK.
Click to expand...
Click to collapse
No problem
Thank you again so much
Hi!
Are you actively working on this still? and did you get around to testing it on a oneplus of any kind? I got the 5T, this does nothing on it sadly, and i'm desperate for a fix
thanks!
Amornik said:
Hi!
Are you actively working on this still? and did you get around to testing it on a oneplus of any kind? I got the 5T, this does nothing on it sadly, and i'm desperate for a fix
thanks!
Click to expand...
Click to collapse
I can't say I'm "working on it still" but whenever I have a need for it, I update it. I actually have the pixel 2 xl running latest oreo 8.1 and needed the added 5 GHz access points at work to have higher speeds (780 MBps beats 54 Mbps any day!)
Works fine here. Just make sure your xposed is working fine and that this module is loaded correctly. Reboot, profit. should work on all 8.1 ROMs given that I'm only modifying a simple framework method which should exist in all variants out there.
Hi,
thanks for the reply!
I have installed the latest Xposed, and your module (downloaded from there, not the file here) & rebooted. nothing happens. I do not see my 5GHZ when it's on the 148 and up band. When I switch it to the lower bands (38 and up) works just fine. this is driving me insane. Any chance you could help me out ?
In another post, someone offered me to replace a file, and that seemed to work for a bit, but now it has also stopped working
Link: https://forum.xda-developers.com/oneplus-5t/help/wifi-region-5ghz-question-5t-t3776003#post76220330
Thanks! appreciate any and all help.
Edit: Actually it would help to understand what it is exactly your addon is changing ? since the above file does have something that seems relevant. is this the same value being changed?
Amornik said:
Hi,
thanks for the reply!
I have installed the latest Xposed, and your module (downloaded from there, not the file here) & rebooted. nothing happens. I do not see my 5GHZ when it's on the 148 and up band. When I switch it to the lower bands (38 and up) works just fine. this is driving me insane. Any chance you could help me out ?
In another post, someone offered me to replace a file, and that seemed to work for a bit, but now it has also stopped working
Link: https://forum.xda-developers.com/oneplus-5t/help/wifi-region-5ghz-question-5t-t3776003#post76220330
Thanks! appreciate any and all help.
Edit: Actually it would help to understand what it is exactly your addon is changing ? since the above file does have something that seems relevant. is this the same value being changed?
Click to expand...
Click to collapse
Maybe use my file here instead? Not sure what's on the xposed modules repo.
madmack said:
Maybe use my file here instead? Not sure what's on the xposed modules repo.
Click to expand...
Click to collapse
Hi,
Thanks for the reply! I thought I had mentioned I already tried it, did not change anything.
Maybe if you told me which file this is editing and which value is being changed, I might be able to debug and see if it's actually changing the value it needs to.
Works fine on my xiaomi a1 !!! thx so much!!
madmack said:
I wrote this for myself but here it is in case anyone is also interested.
Google sets the wifi country code to whatever is in your sim card. If the country does not have a corresponding list of enabled 5GHz frequencies, then a lot of these frequencies get disabled. This mod simply sets the country code to US. There is no GUI or anything, just enable and restart and you're all set. Android marshmallow only. I tested it on my S7 edge and it's working fine.
Enjoy.
Edit: Added OREO 8.1 version. Testing working on Pixel 2 XL.
Click to expand...
Click to collapse
cleberjb said:
Works fine on my xiaomi a1 !!! thx so much!!
Click to expand...
Click to collapse
It would be great if you could specify which version of Android (8.0, 8.1) and which ROM (or stock).
thanks!
Amornik said:
It would be great if you could specify which version of Android (8.0, 8.1) and which ROM (or stock).
thanks!
Click to expand...
Click to collapse
Sorry my inconvenience. Works on Android 8.0 stock.
Amornik said:
Hi,
Thanks for the reply! I thought I had mentioned I already tried it, did not change anything.
Maybe if you told me which file this is editing and which value is being changed, I might be able to debug and see if it's actually changing the value it needs to.
Click to expand...
Click to collapse
Sure, editing method setCountryCode in com.android.server.wifi.WifiServiceImpl
Setting the parameter to US manually.
madmack said:
Sure, editing method setCountryCode in com.android.server.wifi.WifiServiceImpl
Setting the parameter to US manually.
Click to expand...
Click to collapse
Cool, thanks!
Just as a follow up..
1. is this com.android.server.wifi.wifiserviceimpl a file (.jar?)or db file?
2. where is it located?
3. does your fix change it every time on reboot? or is it a one time change? (meaning, does the phone update this from the SIM occasionally?)
thanks again!
Amornik said:
Cool, thanks!
Just as a follow up..
1. is this com.android.server.wifi.wifiserviceimpl a file (.jar?)or db file?
2. where is it located?
3. does your fix change it every time on reboot? or is it a one time change? (meaning, does the phone update this from the SIM occasionally?)
thanks again!
Click to expand...
Click to collapse
no man, it's a framework class that xposed can tap into and change the behavior. Take a look at the source code of Android AOSP for that class. it's not a simple file in /system that you modify. It is changed every time this method is invoked, it's how xposed works.
Lol, just goes to show how much I know about how rhis works, which is nothing
Its working with the update to 8.1 btw.
Thanks for all your work and patience!
I am currently on lineage os 14.1 latest build with franco kernel tried installing arise but lost incall sound for both sides can anyonehelp with installation process
Thank you in advanced.
When option comes to remove deep buffer, select No.
raviprakashji said:
When option comes to remove deep buffer, select No.
Click to expand...
Click to collapse
Volte working after ARISE?
skywalker9969 said:
Volte working after ARISE?
Click to expand...
Click to collapse
Yes
Recently updated to build 137 on my BLA-L09, but now every time I take a picture and try open it in the gallery it constantly shows 'Loading...' with the actual picture dimmed out in the background.
Anyone facing the same issue?
Any solutions?
I also realised the picture doesn't actually save in the DCIM folder, however only the thumbnail saves in the DCIM>cache folder as a .tmp file.
wisemanwizz said:
Recently updated to build 137 on my BLA-L09, but now every time I take a picture and try open it in the gallery it constantly shows 'Loading...' with the actual picture dimmed out in the background.
Anyone facing the same issue?
Any solutions?
Click to expand...
Click to collapse
Are you using a custom kernel?
I am using the following custom kernel...
https://forum.xda-developers.com/mate-10/development/kernel-mate-10-mate-10-pro-stock-t3744501
wisemanwizz said:
Recently updated to build 137 on my BLA-L09, but now every time I take a picture and try open it in the gallery it constantly shows 'Loading...' with the actual picture dimmed out in the background.
Anyone facing the same issue?
Any solutions?
Click to expand...
Click to collapse
ante0 said:
Are you using a custom kernel?
Click to expand...
Click to collapse
wisemanwizz said:
I am using the following custom kernel...
https://forum.xda-developers.com/mate-10/development/kernel-mate-10-mate-10-pro-stock-t3744501
Click to expand...
Click to collapse
Mm. Huawei did something in B137. I will rebrand back to C432 and check later.
thanks man, i hope its fixable, it's actually quite annoying
ante0 said:
Mm. Huawei did something in B137. I will rebrand back to C432 and check later.
Click to expand...
Click to collapse
wisemanwizz said:
thanks man, i hope its fixable, it's actually quite annoying
Click to expand...
Click to collapse
Are you using B137 from 03-29 or 04-04?
It seems the latter is some test build, because it has the required files for Face Unlock (which probably is not enabled in Settings?).
I only did a diff so far on the 2 different B137 builds, but will have to flash to find out if it can be fixable.
I'm using the 04-04 version of the B137 update.
ante0 said:
Mm. Huawei did something in B137. I will rebrand back to C432 and check later.
Click to expand...
Click to collapse
ante0 said:
Are you using B137 from 03-29 or 04-04?
It seems the latter is some test build, because it has the required files for Face Unlock (which probably is not enabled in Settings?).
I only did a diff so far on the 2 different B137 builds, but will have to flash to find out if it can be fixable.
Click to expand...
Click to collapse
wisemanwizz said:
I'm using the 04-04 version of the B137 update.
Click to expand...
Click to collapse
I'm getting the same, one way to get camera back is simply to reflash but use B137 from 03.29. I have only had time to check what camera does briefly. It can't write to /sdcard/DCIM/ for some reason.
Face Unlock works btw, just need to set prop
ro.config.face_recognition=true
Can be done in build.prop or using a Magisk Module to set it at boot.
wisemanwizz said:
I'm using the 04-04 version of the B137 update.
Click to expand...
Click to collapse
It's fixed now. I will release a fix for this version in a couple of hours.
Huawei built kernel using different sources (V10 source it seems), where it uses a new/different vcodec for images.
I compared kernel configs from 4/4 B137 kernel to 3/29 B137 and it's different.
I first tried using the config from 4/4 but it wouldn't build with BLA source (Missing codec).
Then I checked 4/4 B137 config to Honor V10 sources config (It was a little different but codec was there), then built kernel and tested.
Wifi, BT and Camera works now.
That's great! Thank you so much! I look forward to testing it! :angel::angel::angel:
ante0 said:
It's fixed now. I will release a fix for this version in a couple of hours.
Huawei built kernel using different sources (V10 source it seems), where it uses a new/different vcodec for images.
I compared kernel configs from 4/4 B137 kernel to 3/29 B137 and it's different.
I first tried using the config from 4/4 but it wouldn't build with BLA source (Missing codec).
Then I checked 4/4 B137 config to Honor V10 sources config (It was a little different but codec was there), then built kernel and tested.
Wifi, BT and Camera works now.
Click to expand...
Click to collapse
wisemanwizz said:
That's great! Thank you so much! I look forward to testing it! :angel::angel::angel:
Click to expand...
Click to collapse
Here it is: https://mega.nz/#!ZD43wBxa!qPWTiOgcuafWUX1DzZd2RFVU-eZdSn71LFFlJR3Z7Ac
This will probably break camera on other builds (I've not tested).
If you want Face Unlock root is required, you can flash this Magisk module (if you use Magisk) https://mega.nz/#!5e4VSS4L!4vbZr0Pyzm39k2Ltcxi10gcFg_bcSlj7iLosK6SLKtM
Or add the prop manually to /product/etc/prop/local.prop
ro.config.face_recognition=true
The kernel works like a charm! Thanks!
For face unlock I tried to manually edit prop & then restart the phone, I am rooted but it is not working (I do not have Magisk) maybe I am doing something wrong.
Is there any specific place I have to put the "ro.config.face_recognition=true" within the prop file - i.e. should i just paste it right at the bottom of the prop file? And also where will the facial recognition option appear once it is enabled so I can confirm?
Sorry (I'm kind of a noob) I will probably try later. :angel::angel:
ante0 said:
Here it is: https://mega.nz/#!ZD43wBxa!qPWTiOgcuafWUX1DzZd2RFVU-eZdSn71LFFlJR3Z7Ac
This will probably break camera on other builds (I've not tested).
If you want Face Unlock root is required, you can flash this Magisk module (if you use Magisk) https://mega.nz/#!5e4VSS4L!4vbZr0Pyzm39k2Ltcxi10gcFg_bcSlj7iLosK6SLKtM
Or add the prop manually to /product/etc/prop/local.prop
ro.config.face_recognition=true
Click to expand...
Click to collapse
wisemanwizz said:
The kernel works like a charm! Thanks!
For face unlock I tried to manually edit prop & then restart the phone, I am rooted but it is not working (I do not have Magisk) maybe I am doing something wrong.
Is there any specific place I have to put the "ro.config.face_recognition=true" within the prop file - i.e. should i just paste it right at the bottom of the prop file? And also where will the facial recognition option appear once it is enabled so I can confirm?
Sorry (I'm kind of a noob) I will probably try later. :angel::angel:
Click to expand...
Click to collapse
After setting that prop, doesn't mater where so just place it at the bottom, reboot and then got to Settings - Security & Privacy, you should have the Face Unlock option. If you enroll your face you can unlock phone by using the power button and looking at screen. It unlocks instantly in most cases.
Also I noticed I failed at setting a custom string to kernel that would show in Settings - About - Kernel. But it just says Unavailable now. Don't worry about it if you were wondering.
I know all of us (at least most!) hate the huge notch and the screen estate it destroys for the status bar to show complete time/notification icons.
MIUI now has a way to enable dual status bar, where date/time/icons all show in two rows instead of 1 row overflowing into the notch more often than not. I was trying to figure a way out of this for folks running non-MIUI ROMs, since I also mostly use non-MIUI ROMs and stumbled across a rather simple method.
This may need some specific ROM commits (ask your developer), but sharing this with the hope this helps a few folks.
Also, this is not the most aesthetic but functionally this wins because it creates a new option in the least!! :laugh:
Step 1: Download this tool called SetEdit[url]https://play.google.com/store/apps/details?id=by4a.setedit22&hl=en_IN[/URL].
Step 2: Fire up the app (it didn't ask me for root access, so assume this doesn't need root)
Step 3: In the selections on top, make sure you select "This Device" and "System Table"
Step 4: Scroll all the way down to the the entry that reads "statusbar_dual_row"
Step 5: The value against it will likely show "0". Select it, it will open a dialog box, select "Edit Value"
Step 6: Change value to 1, Save changes
Reboot, profit.
It looks like this didn't work for some. As an alternative,
1. try Adding a new setting.
2. It'll ask you for setting name. Type "statusbar_dual_row" (without inverted commas)
3. Save changes
4. Enter "1" in the next option for Value
5. Save changes
Reboot. Hope that can add a setting and it works. Just found out by more tinkering
For an example of how this looks on my screen, refer screenshot below. I managed to gt the clock and 4 different icons in 2 rows on the left side. Probably not the best implementation of dual rows, seeing as it affects only one side, but I am staying with this rather than no clock and 3 icons
PS: I am using Corvus OS (unofficial, 7.0 dated Jul 5)
Nothing here, running on PE+
deathhated said:
Nothing here, running on PE+
Click to expand...
Click to collapse
Read what author wrote bro. This is for device running miui and not custom rom.
Archit9169 said:
Read what author wrote bro. This is for device running miui and not custom rom.
Click to expand...
Click to collapse
He said he's running Corvus. That's why I checked too. Just might have lol
deathhated said:
He said he's running Corvus. That's why I checked too. Just might have lol
Click to expand...
Click to collapse
Bro he never mentioned Corvus in his entire post. Read it again there is not mention of it in his post.
Archit9169 said:
Bro he never mentioned Corvus in his entire post. Read it again there is not mention of it in his post.
Click to expand...
Click to collapse
Yeah, he stated MIUI has a way to enable it and those steps. Read the P.S. at the bottom. Does it say he's running MIUI or Corvus?
deathhated said:
Yeah, he stated MIUI has a way to enable it and those steps. Read the P.S. at the bottom. Does it say he's running MIUI or Corvus?
Click to expand...
Click to collapse
Thats not PS, thats his Signature telling us what his current config is. Just look at my signature where I list my previous works.
Archit9169 said:
Thats not PS, thats his Signature telling us what his current config is. Just look at my signature where I list my previous works.
Click to expand...
Click to collapse
Of course not, this is not signature it is a P.S... he is running on CORVUS...
-->
nandakalyan said:
PS: I am using Corvus OS (unofficial, 7.0 dated Jul 5)
Click to expand...
Click to collapse
and I'm running on MUI 11 and there is no such entry in the tab like "statusbar_dual_row"...
MiPiMok said:
Of course not, this is not signature it is a P.S... he is running on CORVUS...
-->
and I'm running on MUI 11 and there is no such entry in the tab like "statusbar_dual_row"...
Click to expand...
Click to collapse
Oh sorry about that. But that method works cause i am on miui 12 and that option is present there. Not sure about miui 11. And this method is exclusive to miui only and thus cannot be used on custom roms. This feature might be exclusive to china rom or maybe miui 12 exclusive, or maybe miui Eu exclusive.
hey guys, this works on MIUI for sure. For custom ROMS (like I am running Corvus), the developer needs to includes commits for the framework. I am not a technical guy, so if you let your developer know, they can cherry pick this commit or include the framework mod in the ROM, then you can enable it through the SetEdit tool
deathhated said:
Nothing here, running on PE+
Click to expand...
Click to collapse
Do check with your developer, are you getting the line for "statusbar_dual_row" in Set Edit? if not, the ROM does not have the code built in.
nandakalyan said:
Do check with your developer, are you getting the line for "statusbar_dual_row" in Set Edit? if not, the ROM does not have the code built in.
Click to expand...
Click to collapse
Don't have the line in PE+, was just curious tho on custom ROMs if there is. Thanks btw
MiPiMok said:
Of course not, this is not signature it is a P.S... he is running on CORVUS...
-->
and I'm running on MUI 11 and there is no such entry in the tab like "statusbar_dual_row"...
Click to expand...
Click to collapse
Apparently MIUI 11 has this feature, I saw it all over google, not sure if it is build specific (EU, GLobal etc) though. I am able to set this in Corvus ROM, CrDroid, Bliss etc.
deathhated said:
Don't have the line in PE+, was just curious tho on custom ROMs if there is. Thanks btw
Click to expand...
Click to collapse
Yes definitely in the 3 ROMs I tried (Corvus, CrDroid, Bliss), that is why my guess that the ROM developer needs to probably include the feature commits for us to enable it with this method
nandakalyan said:
Yes definitely in the 3 ROMs I tried (Corvus, CrDroid, Bliss), that is why my guess that the ROM developer needs to probably include the feature commits for us to enable it with this method
Click to expand...
Click to collapse
Which build of crDroid?
amn1987 said:
Which build of crDroid?
Click to expand...
Click to collapse
Tried on 18th Jul build
nandakalyan said:
Tried on 18th Jul build
Click to expand...
Click to collapse
OK. I am on an older build from June. The particular commit isn't present in it. I will update later. Thanks.
It looks like this didn't work for some. As an alternative,
1. try Adding a new setting.
2. It'll ask you for setting name. Type "statusbar_dual_row" (without inverted commas)
3. Save changes
4. Enter "1" in the next option for Value
5. Save changes
Reboot. Hope that can add a setting and it works. Just found out by more tinkering
Hi, just as an info..Not working on Global Stable rom. Tried to add a new setting, but not working also..
dreamdrake said:
Hi, just as an info..Not working on Global Stable rom. Tried to add a new setting, but not working also..
Click to expand...
Click to collapse
I have same issue