I have a new Nexus 7 flo since three days. Until now I tried CM, PAC, AOKP ( unofficial ) and PRANOID. I had PRANOID and AOKP running with the stock kernel and with the franco kernel. Every time before I flashed a ROM I did a fullwipe and a wipe of the cache / dalvik after flashing.
Actually all ROMs were running well, but I have a quite strange and very annoying problem with CM, PAC and AOKP: the "back" button in the navbar does not work. I can hear the clicking, but nothing happens. It doesn’t matter whether I use the portrait mode or landscape mode. So far I have no apps installed.
What I tried to solve the problem:
- It doesn’t help to put the button to a different location in the navbar, same problem
- In addition, the problem occurs not only in the navbar, but also when I use PIE at different locations on the touchscreen, so I doubt that it is a touchscreen bug
- Nevertheless I flashed the fixes for the touchscreen bug – no change
- Fixing permissions does not bring any change
Under Stock and PARANOID I did not have this problem. I would very much appreciate a tip for a solution. I liked Stock and PARANOID least of the ROMs tested, but unfortunately there is no way for me without the "back" button.
Thanks in advance for your help!
OK...so I'm not sure if I'm the only one experiencing this problem or not, but every cm ROM I have installed the speaker call volume is obnoxiously low...if I'm on a stock lollipop or stock marshmallow ROM whether its modded or not the volume is fine but on a cm ROM it sucks...its only the voice call speaker volume that is low. The bluetooth, media volume, etc... is fine. I have tried increasing the voice call speaker volume through the mixer paths XML file via es file explorer and it only gets distorted and I have tried many ways...turning it down from 66 to 64 (that makes it sound lower), turning it up from 66 to 68, 70 (that makes it sound distorted). Anyway is this a normal issue for cm ROMs for the speaker call volume to sound low or is there some kind of work around to enhance the volume...thanks
Friend, that sounds like it could be a modem issue. I've used CM-based ROMs for years and haven't had this issue. Currently on vanilla CM and my call/speaker volume is great (D850 variant).
Strange...well I don't reflash bootstacks if I'm already on the correct one but y would everything else work except speakerphone...should I try a modem all by itself? I'm on vs985 variant running resurrection remix (latest build)
matt1285 said:
Strange...well I don't reflash bootstacks if I'm already on the correct one but y would everything else work except speakerphone...should I try a modem all by itself? I'm on vs985 variant running resurrection remix (latest build)
Click to expand...
Click to collapse
Yes. Find a modem for your device and flash it through recovery. It's possible the solution could be that quick and easy. I have no idea why one thing would work and not the other, but personally I would start with the modem.
CM Roms ... The kernels have fauxsound support in kernel management... Have you tried adjusting those settings?
I have not but somebody has told me that when I put them on speakerphone they can hear themselves echoing back when they talk...I flashed to a stock based rom and they no longer hear the echo...I reflashed a custom Rom and now they hear the echo again...so...I flashed a couple more cm aosp rims and they hear the echo on those roms to...is the echo curse normal on custom aosp roms or is there something I'm missing???
I want to programmatically disable the backlight of the capacitive buttons on my Galaxy Tab S 8.4 T700 (klimtwifi). All previous ROMs I've used had this ability built-in and all it took was unchecking a box. My current ROM, Resurrection Remix 6.0.1_r43 - MOB30J, doesn't have this.
I am using GravityBox (MM) to accomplish this but would much rather be able to do it myself, manually, via file modification or some other programmatical method that doesn't involve installing an app to do it. I've done this in the past, on a different device, by changing the value to "0" in a file named "backlight_brightness", or some such. As I recall, the file was located in /sys, /proc, or /dev. I don't remember.
»»» EDIT: Apparently the file is "/sys/class/sec/sec_touchkey/brightness" but the change doesn't survive a reboot.
I can't figure out where to make change in this ROM, and I need your help.
Thank You
I'm also posting this in the Resurrection Remix forum
I was struggling with this for days on a Note 3, thinking, I *know* I did this before when I was on RR6 last.
Anyway, check here: Settings - Configurations - Button Controller - Backlight. No, I don't know why the icon is a gamepad. Hope this helps you and others!
jbradlee said:
I was struggling with this for days on a Note 3, thinking, I *know* I did this before when I was on RR6 last.
Anyway, check here: Settings - Configurations - Button Controller - Backlight. No, I don't know why the icon is a gamepad. Hope this helps you and others!
Click to expand...
Click to collapse
I've actually went back to different ROM. Thanks anyways.
Samsung Galaxy Tab S 8.4" klimtwifi (rooted)
Resurrection Remix 6.0.1
ResurrectionRemix-M-v5.6.9-20160602-chagallwifi
XenonHD ROM for Xiaomi Mi Mix 2
A Team Horizon ROM
Based on AOSP r36 7.1.2
This ROM has all the features XenonHD has to offer.
All hardware functions including:
NFC
Bluetooth Audio
Fingerprint Scanner
Doze & Wake-up Gestures (dtw works after the first reboot)
And...many more things.
Magisk is no longer built in, so you'll need to flash it when first installing, and after every dirty flash.
VoLTE doesn't work (at least on T-Mobile). I believe most of the pieces are in place, but there may be something in the firmware that's preventing it? If I could figure out how to tap into the stock cust files, I might be able to figure out how to get it working.
Proximity Sensor is working:
Notification Light:
I have slowed down the notification light so it isn't all amped up. To make it completely usable, go to:
Fixed default notification blinks for built-in apps so they are slowed down without needing to go to settings.
For use-installed apps, add them to custom notification list in settings > notifications > gear icon > notification light > + in upper right corner > select app. Apps added to that list will have slow notification blinks.
I simply cannot find a way to make user-installed app notifications behave the same as built-in apps. Grrr!!
I have also made the light sensor wait longer before dimming the screen. This helps with left-handed activities blocking the light sensor and almost immediately dimming the screen.
Reduced time to go back from dim to bright. Screen will dim after 5 seconds, returns to bright after 2 seconds.
I've remove configpanel & pocketmode...they did little to nothing, and may have caused more battery drain than I care for.
Required prior to installing:
Unlock Bootloader
Install custom recovery: https://www.androidfilehost.com/?fid=962021903579490303
HUGE thanks to IceMan for bringing this to Mix 2!
A quirk with this TWRP: This one looks for backups in TWRP/BACKUPS/MIX_2 folder. Normally, the MIX_2 folder is named after serial number of your device.
So, you existing backups won't be found until you rename the folder in BACKUPS to MIX_2.
Installation Instructions:
Dirty flash is now available with the above TWRP and 10-26-2017 rom.
Download the most recent build: https://www.androidfilehost.com/?fid=673791459329071426
Download Gapps (I use Open Gapps Mini) --> http://opengapps.org/
All versions from 10-24-2017 are now encryptable.
From TWRP Recovery:
IF COMING FROM MIUI-BASED ROM: FULL WIPE AND FORMAT DATA!!
If you encounter ERROR 7, during XenonHD install, install Global MIUI ROM, then do full wipe and data format again, then install XenonHD rom.
If coming from AOSP-based ROM:
- Full wipe (Cache, Davlik/ART Cache, System & Data)
- Flash ROM zip
- Flash Gapps zip
Huge thanks to Mokee for bringing this device up and making a great place to start.
Also a very HUGE thanks to @Arasthel for his work on proximity sensor and figuring out the bluetooth reboot stuff and other hints, suggestions and incalculable work.
I'd also like to thank all of you folks here for trying this ROM and providing constructive feedback.
In addition, I appreciate your patience when issues come up that need to be fixed. I am not a developer, and I have a full time job and a wife that takes precedence most of the time
Sources:
Vendor:
https://github.com/hondajohn88/android_vendor_xiaomi_msm8998-common
https://github.com/hondajohn88/android_vendor_xiaomi_chiron/tree/xenonhd
Kernel:
https://github.com/hondajohn88/android_kernel_xiaomi_msm8998/tree/xenonhd
Device:
https://github.com/hondajohn88/android_device_xiaomi_chiron/tree/xenonhd
https://github.com/hondajohn88/android_device_xiaomi_msm8998-common/tree/xenonhd
reserved
reserved 2
Does safety net pass with or without magisk?
subashchandran said:
Does safety net pass with or without magisk?
Click to expand...
Click to collapse
With magisk its working
Gesendet von meinem MI Mix 2 mit Tapatalk
THX for the ROM @hondajohn88 ,very much appreciated. :good:
Is this 1st release identical to the beta?
Just curious,as I tried to dirty flash over the beta & got the same errors as if coming from another ROM (wouldn't flash).
Is a full wipe (less formatting data) necessary if updating ?
I don't mind setting up from new again,even if just updating from the beta build.
However,wondering if incremental updates are going to be an option on future builds.
THX.
Sent from my MI Mix 2 using XDA Labs
Bluetooth seems to be working fine for audio/calls. Need to try video/youtube audio output on car (will do it on the drive back home)
ROM is slick, its been good so far (2 hours since i have set everything up)
KOLIOSIS said:
THX for the ROM @hondajohn88 ,very much appreciated. :good:
Is this 1st release identical to the beta?
Just curious,as I tried to dirty flash over the beta & got the same errors as if coming from another ROM (wouldn't flash).
Is a full wipe (less formatting data) necessary if updating ?
I don't mind setting up from new again,even if just updating from the beta build.
However,wondering if incremental updates are going to be an option on future builds.
THX.
Sent from my MI Mix 2 using XDA Labs
Click to expand...
Click to collapse
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.
subashchandran said:
Bluetooth seems to be working fine for audio/calls. Need to try video/youtube audio output on car (will do it on the drive back home)
ROM is slick, its been good so far (2 hours since i have set everything up)
Click to expand...
Click to collapse
Glad everything is working for you so far. Bluetooth audio in car should work (it does on mine), but I found the volume on the car set to zero so needed to turn that up. That was a brief "oh crap" moment that I thought it wasn't working lol
subashchandran said:
Does safety net pass with or without magisk?
Click to expand...
Click to collapse
I think it fails without it, but magisk is built in, so if have to remove it to find out for sure.
hondajohn88 said:
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.
Click to expand...
Click to collapse
IT'S ALL GOOD @hondajohn88 . :good:
This ROM is daily-driver material,every update from here on out is a bonus & very much appreciated. :good:
hondajohn88 said:
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.
Click to expand...
Click to collapse
It seems that we both have faced this issue. I just got A2DP working yesterday on Resurrection Remix by using sagit as base - without msm-8998 common and all that -, imagine my surprise when I saw you also did .
Anyway, I think the WiFi bug may be related to something going wrong in the build. When you build the ROM, kernel sources are used and you can see that the wlan.ko module is built. The problem is, wlan.ko is also a binary blob found in vendor. I believe that on the 2nd build, if dirty, one of these modules overwrites the other - which worked. Maybe you can test this idea, I will be doing it too on the next days.
Arasthel said:
It seems that we both have faced this issue. I just got A2DP working yesterday on Resurrection Remix by using sagit as base - without msm-8998 common and all that -, imagine my surprise when I saw you also did .
Anyway, I think the WiFi bug may be related to something going wrong in the build. When you build the ROM, kernel sources are used and you can see that the wlan.ko module is built. The problem is, wlan.ko is also a binary blob found in vendor. I believe that on the 2nd build, if dirty, one of these modules overwrites the other - which worked. Maybe you can test this idea, I will be doing it too on the next days.
Click to expand...
Click to collapse
That's cool you got the Bluetooth working on RR, knocking little things out one by one ?
Thanks for the idea on the Wi-Fi, I'll look into that this evening. Maybe there's a file I can delete before dirtybuilding. That would make testing things a lot faster! ??
By the way, does android auto work on your rr?
Everything except proximity sensor works and works as good as stock. I have installed custom font, black swift substratum OMS theme without any hiccups. The rom is buttery smooth and I've been getting a better battery drain trend on this compared to resurrection/mokee. I have naptime doze installed to see if i can ooze out more battery goodness to the levels of epic Rom(miui 9)
Overall this is super encouraging to see a daily driver rom this early for mi mix 2.
There is one edge case which might be a bug, when connected on car Bluetooth and watching something on YouTube.. And then you get a call, i pressed answer on the car knobs/buttons.. I couldn't hear the person talking.. Car was displaying "audio disabled message ”. But talking/call and video/music in isolation works just fine.
Android auto works for me. I'm on RR now. Might come to this if we can get Android auto working. How did you guys fix your Bluetooth audio on RR (we can move this to the RR thread if you prefer) @Arasthel
slyyke said:
Android auto works for me. I'm on RR now. Might come to this if we can get Android auto working. How did you guys fix your Bluetooth audio on RR (we can move this to the RR thread if you prefer) @Arasthel
Click to expand...
Click to collapse
Thanks for the info about android auto on RR. I'll take a look at their repo and see if I messed up a USB setting somehow.
As far as I'm concerned, other ROMs can be discussed here.
Open source should be crowd sourced for maximum problem resolution.
RR probably (?) Did the same as me... Mokee made a commit in qcom/audio that did the trick.
hondajohn88 said:
That's cool you got the Bluetooth working on RR, knocking little things out one by one
Thanks for the idea on the Wi-Fi, I'll look into that this evening. Maybe there's a file I can delete before dirtybuilding. That would make testing things a lot faster! ?
By the way, does android auto work on your rr?
Click to expand...
Click to collapse
Hi... Thank you again for the wlan.ko tip. I deleted all instances of that in my out folder, dirty built and it's all good. Sped up my test time considerably! Woohoo! :good:
Thanks op for adding this to to the mix. Much appreciated. I am not sure if I can leave Resurrection due to all the customization options. Does this room offer as many customization options? Thanks so much!
stu5797 said:
Thanks op for adding this to to the mix. Much appreciated. I am not sure if I can leave Resurrection due to all the customization options. Does this room offer as many customization options? Thanks so much!
Click to expand...
Click to collapse
I haven't used rr for this phone, but I think at this point rr probably has more options. This one has quite a few, and as son as I get most of this ROM straightened out, I'll try adding more options.
I'll add some screen shots of the settings to help people decide.
Thanks ?
Great work by a great Dev,
Thanks for putting in the work, smoothhhh rom~