Related
I have three problems that I've found in MZ601 CM 11 Kitkat Build : 20140503 so far :
1. First, network connection often disconnected, almost twice a day. The only solution is by restarting my device.
2. The feature doubletap2wake always disabled (reset to : 0) automatically after restarting my device. I have to activate it manually if I want it back.
3. Lockscreen is always displayed in Landscape mode if I set LOCK ROTATION in Potrait. It will be Potrait if I set AUTO-ROTATION.
Are these problems related to bugs in this build? Is there any possibilites that I con do to fix these problems?
Many thanks for your attention.
elqodir said:
I have three problems that I've found in MZ601 CM 11 Kitkat Build : 20140503 so far :
1. First, network connection often disconnected, almost twice a day. The only solution is by restarting my device.
2. The feature doubletap2wake always disabled (reset to : 0) automatically after restarting my device. I have to activate it manually if I want it back.
3. Lockscreen is always displayed in Landscape mode if I set LOCK ROTATION in Potrait. It will be Potrait if I set AUTO-ROTATION.
Are these problems related to bugs in this build? Is there any possibilites that I con do to fix these problems?
Many thanks for your attention.
Click to expand...
Click to collapse
1. Yes i experience this too even before this build. Whenever it happens, the icon in the status bar turns into sim card logo, meaning as if there is no sim card inside. Thus reboot is required. Never happens in omni though
2. Do you use trickster mod?
I don't know
superbay said:
1. Yes i experience this too even before this build. Whenever it happens, the icon in the status bar turns into sim card logo, meaning as if there is no sim card inside. Thus reboot is required. Never happens in omni though
2. Do you use trickster mod?
Click to expand...
Click to collapse
What's trickster Mod?
elqodir said:
What's trickster Mod?
Click to expand...
Click to collapse
Its an app to maximize and utilize the feature of your kernel. You can set in on boot so that you can lock the features like dt2w or s2w so it will always be on whenever you turn on the device. Find it in google play
Q&A for [ROM™ 4.4.4][DUAL] N5 Experience R10.0 - CM11 Based - [7th October]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
systemUI FC loop
flashed this rom yesterday. almost everything was fine till mid night. when i woke up phone was off. turned on the device and found systemUI FC loop. i am tired of this. going back to stock. is there any ROM out there without this any issue which ran at least 1 week. please let me know.
incoming call display problem
i have been using this rom since the begining and its the best available for moto g (xt1033). i have only faced one issue and that is ; upon an incoming call, the phone rings and vibrates as it should timely, but the display remains black for around 8-10 seconds and then the contact info pops up. i have tried multiple setting changes but the problem is still there. hope any body knows the answer to it.
sim not detected
it is unable to detect sim on my moto g dual (xt1033)
sandysan said:
flashed this rom yesterday. almost everything was fine till mid night. when i woke up phone was off. turned on the device and found systemUI FC loop. i am tired of this. going back to stock. is there any ROM out there without this any issue which ran at least 1 week. please let me know.
Click to expand...
Click to collapse
you need to flash aosp kernel without d2w after this rom and your problem will be gone
Pocket Mode not fully working?
Does anyone else have a problem where pocket mode doesn't turn off the screen when put back in pocket?
latest built 10.3 have any issue? xt1033
Juwelrana said:
latest built 10.3 have any issue? xt1033
Click to expand...
Click to collapse
Make a backup of your current ROM. Try. And if something going bad, return with the backup. [emoji41]
I'm going to install this version on multirom.
I think 10.3 don't have good battery backup..if they include battery saver mode it will be great.
Incoming call not displayed
Installed and found this issue.
the erased everything and installed fresh just to see that the problem persists on a fresh install as well.
I like the ROM and have found a usable solution to keep it but would prefer to have it working as it should.
I read a lot that this is a common problem on Original Nexus 5 phones, so maybe it is ported together with the ROM.
When screen is on and incoming call is made the melody is playing, phone is vibrating (if set to do so) and in the notification bar is a notice of incoming call. if pulled down there is an option to answer or deny the call in the notification drawer.
When screen is off and incoming call is made after ca 1-2 seconds of melody playing dialer screen appears with number or contact name and option to answer or decline the call. As it normally should be.
After trying many setting changes the closest to usable solution i have come is to enable Heads Up.
If you want to try that you need to follow this route: Setings > Notification Drawer > Heads Up. I set it to ON and it shows incoming call in a pop up when the screen is on. when the screen is OFF the incoming call appears as normal.
my phone is moto g 16gb with dual sim.
---------- Post added at 09:50 AM ---------- Previous post was at 09:44 AM ----------
And another issue that i have come across in a fresh install is that Android File transfer on my macbook does not detect my Moto G when Developer options and Android debuggin (in developer options) is set to off.
Even the phone displays a notification that it is connected as a media device and in usb connectin settings i can switch between media device and camera. When i selct camera mode my mac detects the phone and opens camera/gallery window. as soon i change that to media device it disconnects
With stock rom it connected every time i plugged it in.
Am i missing somethin or is there a bug or that is the way it should be in this ROM ??
What exactly does the iPhone 5 and Halfbreed color profile? Because I don't see any differences in colors, when enabling one of them
Sent from xt1032 / Odoslané z xt1032
2hipso said:
What exactly does the iPhone 5 and Halfbreed color profile? Because I don't see any differences in colors, when enabling one of them
Sent from xt1032 / Odoslané z xt1032
Click to expand...
Click to collapse
I have same conditions.
Awesome work!
lock screen freezes! what should i do??
Smooth and stable!A
Good ROM! Any possibilty for OTA? =D
thx
I just quiet this rom because of battery drain so fast....and nxcm 10 version never freeze when play video then press volume button but latest version I got this issue.
xt1033
i like this rom so much but, in every notification is coming my lockscreen always freezed. i was flashed use TWRP and do instruction installation well. with other rom i didn't have problem like this.please give some solustion.thx
magnusy6 said:
lock screen freezes! what should i do??
Click to expand...
Click to collapse
flash this kernel, bro
http://corte.us/457636
!! but you will loose double-tap to wake (also known as D2W or DT2W) and swype to wake (S2W) features
link source: http://n5x.mobi/motog
The pocket mode problem persists. It detects fine when the phone is taken out of the pocket but when put back the screen remains as it is. Anyway this ROM is the beat for motog ,so I can work with the faulty pocket mode.
Dark theme like aosp
Hello,
I love dark themes. Any chance to add the dark theme in your build as aosp roms on this rom. I would not change this rom but I would like to have the option to change it to black theme, or do you know of any other alternative?
Thank you
[NOTE] - This behavior is exactly the same on both global (Pie 9.0) and stable (Oreo 8.0) version. I´ve checked this, so "Stable" Oreo is also buggy.
Report > http://en.miui.com/forum.php?mod=viewthread&tid=4190948&extra=
This bug still remains in latest build (8.10.11). in miui per/app notifications option, notifications are activated by default,
BUT you can see a few options below each app notification page switch: Sound, vibration, show on lockscreen, show headup....
By default, I seem to remember only vibration option is activated, so here (and on each conversation you got a notification in the case of telegram)
You have to activate all options you want: sound, show on lockscreen....
After a while, all this activated options will be resetted by the system (we dont know why) and will switch back to its defaults >> "only vibrate and dont show on lock screen" combination.
So I want to collect information about this bug, wich remains after months, and its a very important thing wich need more atention.
THIS IS A G-FORM WHERE YOU CAN SIMPLY TELL IF IT WORKS OR NOT FOR YOU, SO WE CAN SEE HOW MUCH PEOPLE IS AFFECTED OR NOT BY THIS BUG
GOOGLE FORM LINKS
(stable releases) > https://goo.gl/forms/CAnQy4Q3nm8Hegzm1 SEE THE RESULTS >> https://goo.gl/affGbh
(dev releases) > https://goo.gl/forms/8VqaS3ByOcIVyILU2 SEE THE RESULTS >> https://goo.gl/MyqHm3
4 responses was deleted due to form changes, so its restarted
This is a Pie issue. Early versions of Pie GSI ROMs had the same issue, but they were eventually fixed. I don't think that MIU is using that fixed Pie ROM as its base.
napes22 said:
This is a Pie issue. Early versions of Pie GSI ROMs had the same issue, but they were eventually fixed. I don't think that MIU is using that fixed Pie ROM as its base.
Click to expand...
Click to collapse
Maybe is a Pie issue, but also miui10 oreo (stable right now) is having this bug
This is what happen (video)
https://goo.gl/m4M3nd
Is it only behaving like this with this app ?
I will receive my phone Tomorrow, don't want to keep it if notifications are broken.
(Like on my current Huawei phone)
mchtt said:
Is it only behaving like this with this app ?
I will receive my phone Tomorrow, don't want to keep it if notifications are broken.
(Like on my current Huawei phone)
Click to expand...
Click to collapse
Same with WhatsApp vs. GBWhatsapp and sure more apps. Its a system issue on how it manage defaul values depending on preset or non preset apps
I have sent my device back ?
Disappointed by this and also the screen is not that good in my opinion. (Colors and Resolution compared to others)
Performance were great and gesture mode perfect.
Updated forms:
One to stables > with V10.0.3.0PDGMIFH lets try..... (I got the update vía ota, "PDGMIFH" means PIE?)
And one to developer > 8.10.11 right now.
I´ve tested new V10.0.3.0 very excited, but sadly I have to say this issue remains there.
Some of you maybe say "oh, Im not having this issue... my notifications are working well". Yes, but maybe it default is to play sound, vibration and so... but try to uncheck sound or anything, clean recents, and wait to get a notification for these certain contact. Probably your unchecked options will reactivate again.
I have the same issue on Dev Global M10. No notifications whatsoever for Hangouts, Android Messages, Discord, and Snapchat. Gmail works fine though.
On all custom Roms I've tried so far (and they've been a few), there's an ongoing problem while using Android Auto connected to the car's built-in display. Basically, if you plug in your phone and start using AA, after a while the bottom bar on the car's display will disappear, and although you can keep driving and AA will keep working, once you stop and unplug the phone from the car, the phone will lock you out and it's screen will start to flicker and go crazy, giving you no other option but to force reboot the phone.
This issue was present on MIUI Oreo roms as well, but since they updated to Pie last month, it was addressed and a fix was found (seems it was related to the devices default display drivers). For custom Roms, there's a temporary workaround, which is to disable hardware overlays in developer settings, but you need to do this every time you reboot your phone since these settings don't stick permanently.
I've posted and mentioned this issue on several different custom ROM threads, but as far as I know, none of the devs has acknowledged the issue nor has tried to find a solution. So, the question is; how many of you have the same problem?
Please provide your feedback, as it would be good to let the devs know this is not unimportant or isolated.
krilok said:
On all custom Roms I've tried so far (and they've been a few), there's an ongoing problem while using Android Auto connected to the car's built-in display. Basically, if you plug in your phone and start using AA, after a while the bottom bar on the car's display will disappear, and although you can keep driving and AA will keep working, once you stop and unplug the phone from the car, the phone will lock you out and it's screen will start to flicker and go crazy, giving you no other option but to force reboot the phone.
This issue was present on MIUI Oreo roms as well, but since they updated to Pie last month, it was addressed and a fix was found (seems it was related to the devices default display drivers). For custom Roms, there's a temporary workaround, which is to disable hardware overlays in developer settings, but you need to do this every time you reboot your phone since these settings don't stick permanently.
I've posted and mentioned this issue on several different custom ROM threads, but as far as I know, none of the devs has acknowledged the issue nor has tried to find a solution. So, the question is; how many of you have the same problem?
Please provide your feedback, as it would be good to let the devs know this is not unimportant or isolated.
Click to expand...
Click to collapse
On which MIUI Version are you having that problem?
Which car display with which software version are you using?
For me with MIUI 8.12.27 weekly EU version and Skoda Bolero display I'm not having the issue you describe.
MikelFuchs said:
On which MIUI Version are you having that problem?
Which car display with which software version are you using?
For me with MIUI 8.12.27 weekly EU version and Skoda Bolero display I'm not having the issue you describe.
Click to expand...
Click to collapse
Please read the title: on custom roms, not miui...
You wrote on Oreo stock ROM it was present to.
oiseau1201 said:
You wrote on Oreo stock ROM it was present to.
Click to expand...
Click to collapse
Yes, and it was (plenty of comments on MIUI forums and over the net, if you want to take a look...) They fixed it on Pie, and if you're still running Oreo and don't have issues, then I guess they fixed it there, too.
This poll, topic and thread is for the issues still affecting Aosp based custom roms, such as Crdroid, PE, Lineage, etc.
Even I would like to know the result of this poll. I am on the verge of trying out a custom ROM (since i am done with the bugs in MIUI). But if AA doesn't work on custom ROM, it is a showstopper for me.
Hi,
I have a different issue with Android Auto.
My problem is that when I connect to Android Auto, after a couple of minutes (1-2, 2-3 minutes) the screen on the car's display seems to be stuck, and from then on it doesn't follow my progress on the way. The screen itself is not frozen, because e.g. I can make a reroute but after it is done it goes back to the "original" state of my route when it stopped progressing. The screen remains responsive regarding the controls because I can even change to Google Maps on the car's AA display, and it works flawlessly.
Anyone else had this issue?
I'm using xiaomi.eu rom 9.1.17 beta
aghilvr said:
Even I would like to know the result of this poll. I am on the verge of trying out a custom ROM (since i am done with the bugs in MIUI). But if AA doesn't work on custom ROM, it is a showstopper for me.
Click to expand...
Click to collapse
I'm currently on Crdroid, and in my opinion it's the one that works best. As for the AA issue, it's present on all custom roms, but for the time being, I'm using the workaround I mentioned on OP and can use AA fully.
rn74 said:
Hi,
I have a different issue with Android Auto.
My problem is that when I connect to Android Auto, after a couple of minutes (1-2, 2-3 minutes) the screen on the car's display seems to be stuck, and from then on it doesn't follow my progress on the way. The screen itself is not frozen, because e.g. I can make a reroute but after it is done it goes back to the "original" state of my route when it stopped progressing. The screen remains responsive regarding the controls because I can even change to Google Maps on the car's AA display, and it works flawlessly.
Anyone else had this issue?
I'm using xiaomi.eu rom 9.1.17 beta
Click to expand...
Click to collapse
Strange, I tried an EU rom about a couple of weeks ago for a few days and AA worked out of the box. Didn't like the MIUI stuff, though, so reverted back to Crdroid.
I however remember I flashed the full MIUI rom completely, wiping everything and starting from scratch, so if you want to stick with MIUI, maybe you should do a fresh install...
krilok said:
Strange, I tried an EU rom about a couple of weeks ago for a few days and AA worked out of the box. Didn't like the MIUI stuff, though, so reverted back to Crdroid.
I however remember I flashed the full MIUI rom completely, wiping everything and starting from scratch, so if you want to stick with MIUI, maybe you should do a fresh install...
Click to expand...
Click to collapse
Edit: just noticed. Are you using Waze for navigation? If you are, there's an ongoing location issue with the app running on MIUI...
Having the same issue running PIxelExperience and it's driving me nuts.
krilok said:
, there's a temporary workaround, which is to disable hardware overlays in developer settings, but you need to do this every time you reboot your phone since these settings don't stick permanently.
Click to expand...
Click to collapse
I did not know that, thanks for the tip .
Update: you can automate disabling the hardware overlays using Tasker and the Secure Settings plugin
bob*nwk said:
Having the same issue running PIxelExperience and it's driving me nuts.
I did not know that, thanks for the tip .
Update: you can automate disabling the hardware overlays using Tasker and the Secure Settings plugin
Click to expand...
Click to collapse
Thanks, I had read you could use tasker for that, but it's a paid app and I wouldn't be using it for anything else at the moment. I'm fine with remembering to disable it manually. Still, I believe the issue has to be addressed at some point by the devs...
One General question:
The only thing keeping me away from custom roms is the AA issue. Nice to hear that at least we have a workaround.
At the moment i am on MIUI Android pie and using a VW in build AA Display. The issue i'm having is that WhatsApp notifications are not shown on the Display. I can send WhatsApp Messages via Ok Google but not able to hear received messages.
Do you guys have the same issue?
gella1992 said:
One General question:
The only thing keeping me away from custom roms is the AA issue. Nice to hear that at least we have a workaround.
At the moment i am on MIUI Android pie and using a VW in build AA Display. The issue i'm having is that WhatsApp notifications are not shown on the Display. I can send WhatsApp Messages via Ok Google but not able to hear received messages.
Do you guys have the same issue?
Click to expand...
Click to collapse
Wouldn't be able to confirm that, although I did read somewhere that if you're using any Dual apps on MIUI, AA won't work correctly. Are you using two WhatsApp accounts by any chance...?
I can tell you though that on the current rom I'm using (crdroid), they do work and appear on the cars screen, although most of the time there's no notification ringtone whenever they arrive. Since that was happening on my previous phones too, be it on nougat, oreo and pie, I guess that's a problem with AA itself...
Thanks for your quick reply.
Happy to hear that it is generally working.
Not using dual Apps. Will try to flash a custom Rom in the next days
krilok said:
Thanks, I had read you could use tasker for that, but it's a paid app and I wouldn't be using it for anything else at the moment. I'm fine with remembering to disable it manually. Still, I believe the issue has to be addressed at some point by the devs...
Click to expand...
Click to collapse
If you buy it, I guarantee you will be using it for a lot more than just that...
papete said:
If you buy it, I guarantee you will be using it for a lot more than just that...
Click to expand...
Click to collapse
I can confirm this. Best $5,- I spent on an app ever.
papete said:
If you buy it, I guarantee you will be using it for a lot more than just that...
Click to expand...
Click to collapse
I understand and appreciate the recommendation, but I've already got Macrodroid for other automation functions...
I don't get the menu on the bottom visible with disabling HW Overlay, tested Nitrogen,CRdroid, Liquid Remix,LOS
using: beryllium-9.1.24-9.0-vendor-firmware
mf76130 said:
I don't get the menu on the bottom visible with disabling HW Overlay, tested Nitrogen,CRdroid, Liquid Remix,LOS
using: beryllium-9.1.24-9.0-vendor-firmware
Click to expand...
Click to collapse
Works for me and others as well, although someone did mention on another thread he couldn't get this workaround to work either...
This is my setup:
USB debugging on and hardware overlays disabled.
In AA developer options, enable 720, 1080, unknown sources.
If it still won't work, then Im guessing it could maybe be due to different screen panels or something...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Resurrection Remix Q
BY : @[COLOR=red]Ahmed Shaikh[/COLOR]
Code:
[SIZE="4"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.
Make sure you have a custom recovery installed(TWRP is the preferred recovery)
Download the latest Resurrection Remix Rom & the latest GApps package
Boot into recovery
Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
Flash ResurrectionRemix Rom
Flash Google Apps package(Optional)
Flash Magisk Root(Optional)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
AICP
Crdroid
AOSIP
DU
Xtended
Evolution X
Bliss
Omni Team
And Of Course To All The Supporters, Donators And Users
Join our Telegram channel : https://t.me/resurrectionremixchat
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.
XDA:DevDB Information
Resurrection Remix , ROM for the Asus Zenfone Max Pro M2
Contributors
ahmedshaikh, varund7726, SonalSingh18
Source Code: https://github.com/ResurrectionRemix
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 8.6.5
Stable Release Date: 2020-12-10
Created 2020-08-15
Last Updated 2020-10-08
If you like my work, you can buy me a coffee or a pizza...
Paypal :- https://paypal.me/ahmedsk69
UPI :- [email protected]
thanks for the amazing rom. its working smoothly
anyone facing this issue? first i set it in permissive, then after a reboot in zenparts, it shows permissive but actually its in enfocing status. it not working man....
Great Rom.. Good Work Dev ??
Scrolling and Fingerprint is laggy
Good Rom, But Scrolling and Fingerprint is laggy
Double tap does not work after reboot. You have to turn it off / on again in the settings.
Can I wake up the screen with a gesture (letter)? Other ROMs have it.
DT2W not work me too after reboot, always need to reenable it. Maybe not rom specific, same on crDroid. Anyway, it is one of the best rom, many many thanks devs!
fantastic rom. only issue is that most of the times DT2W doesnot work. All other seem to work pretty awesome.
smart buddy said:
fantastic rom. only issue is that most of the times DT2W doesnot work. All other seem to work pretty awesome.
Click to expand...
Click to collapse
It's for lockscreen and status bar only works file
ahmedshaikh said:
It's for lockscreen and status bar only works file
Click to expand...
Click to collapse
Nope, sir. it barely works on lockscreen. And also there is location bug. Please have a look.
Incoming calls not showing up and Camera flash out-of-sync
I have been testing this rom since 3 or 4 releases up until the 8.6.0-20200918 release and it's surprising that no one has talked about the incoming calls not being shown until the calls end. This is a major breaking bug. I can guess that probably no one has used the rom without gapps like me (I don't use gapps, I use microg and f-droid) so maybe it's a bug with the default aosp dialer but I can confirm that the default aosp dialer works fine on other Q roms like crdroid, carbonrom. So I'm asking @ahmedshaikh to please look into this bug. It's a basic feature of a phone to receive incoming calls. I appreciate your work and love the fact that you are maintaining RR for our device which has been one of my favourite roms since more than 5 years now.
Details of what is happening when there is an incoming call:
1. If the device is locked or display is turned off, the display does not turn on though you can manually turn on display but then there is no notification heads-up or any full screen indication that there is an incoming call.
2. If the device is already unlocked and display is on and there is an incoming call, then there is still no heads-up or any indication of incoming calls.
3. But the phone rings and you can silent the ring by pressing volume buttons. This stands for all the cases (whether display is on/off).
4. After waiting till the ring ends you finally get a heads-up showing an incoming call, but nothing happens when you press Answer or Reject buttons. The heads-up stays for a couple of seconds until it goes away and you get a notification that there is a missed call.
5. Also the home button/gesture is unusable while the there is an incoming call, only back and recent buttons/gestures work.
So that sums up the situation. I have tested this multiple times.
Ok, and now I come to camera. I think it would be better to ship the rom with open camera (if possible) or at least default lineageos camera (snap) as the pre-installed google camera go does not work well with flash. I could not capture a single photo with flash turned on. But open camera worked fine (with camera2api turned on which is the default setting).
Please do tell me if there is anything else I can help you with. I really wish to keep this rom alive for as long as possible.
SayanChakroborty said:
I have been testing this rom since 3 or 4 releases up until the 8.6.0-20200918 release and it's surprising that no one has talked about the incoming calls not being shown until the calls end. This is a major breaking bug. I can guess that probably no one has used the rom without gapps like me (I don't use gapps, I use microg and f-droid) so maybe it's a bug with the default aosp dialer but I can confirm that the default aosp dialer works fine on other Q roms like crdroid, carbonrom. So I'm asking @ahmedshaikh to please look into this bug. It's a basic feature of a phone to receive incoming calls. I appreciate your work and love the fact that you are maintaining RR for our device which has been one of my favourite roms since more than 5 years now.
Details of what is happening when there is an incoming call:
1. If the device is locked or display is turned off, the display does not turn on though you can manually turn on display but then there is no notification heads-up or any full screen indication that there is an incoming call.
2. If the device is already unlocked and display is on and there is an incoming call, then there is still no heads-up or any indication of incoming calls.
3. But the phone rings and you can silent the ring by pressing volume buttons. This stands for all the cases (whether display is on/off).
4. After waiting till the ring ends you finally get a heads-up showing an incoming call, but nothing happens when you press Answer or Reject buttons. The heads-up stays for a couple of seconds until it goes away and you get a notification that there is a missed call.
5. Also the home button/gesture is unusable while the there is an incoming call, only back and recent buttons/gestures work.
So that sums up the situation. I have tested this multiple times.
Ok, and now I come to camera. I think it would be better to ship the rom with open camera (if possible) or at least default lineageos camera (snap) as the pre-installed google camera go does not work well with flash. I could not capture a single photo with flash turned on. But open camera worked fine (with camera2api turned on which is the default setting).
Please do tell me if there is anything else I can help you with. I really wish to keep this rom alive for as long as possible.
Click to expand...
Click to collapse
Set ur phone app as ur default app for call
ahmedshaikh said:
Set ur phone app as ur default app for call
Click to expand...
Click to collapse
The AOSP Dialer app is the only Phone app and set as default already, though I still have manually selected the Phone app as default as that was the first thing that crossed my mind. So, no effect. Can you try reproducing the issue on your device? Just don't flash anything (gapps or magisk or microg) except the rom and try to receive an incoming call. Best of Luck.
SayanChakroborty said:
The AOSP Dialer app is the only Phone app and set as default already, though I still have manually selected the Phone app as default as that was the first thing that crossed my mind. So, no effect. Can you try reproducing the issue on your device? Just don't flash anything (gapps or magisk or microg) except the rom and try to receive an incoming call. Best of Luck.
Click to expand...
Click to collapse
Since it's not some crash or reboot issue, I think you can get logcat easily. It may help dev with understanding the issue.
Auto Rotate Feature Not Working
Auto rotate is not working in any app, tried using other apps as well nothing works for that.
How to activate 'Settings - System - Gestures - Touchscreen Gestures'?
I'm enabling it, but it not working??
Please help...
---------- Post added at 10:08 AM ---------- Previous post was at 09:52 AM ----------
kalo3567882 said:
Auto rotate is not working in any app, tried using other apps as well nothing works for that.
Click to expand...
Click to collapse
It's working fine for me, try checking sensors settings, maybe you have disabled sensors...:good:
Found the culprit
ahmedshaikh said:
Set ur phone app as ur default app for call
Click to expand...
Click to collapse
TBC6 said:
Since it's not some crash or reboot issue, I think you can get logcat easily. It may help dev with understanding the issue.
Click to expand...
Click to collapse
Strangely enough it's been working fine since I disabled the app "Sounds" that enables Google Pixel Sounds as ringtones and alert tones. I have tested with and without the Sounds app enabled and I can confirm that app is causing this incoming call issue.
Unpopular opinion: Please don't ship Google apps as system apps in RR rom. Both google apps (Google Camera Go and Sounds) are problematic and causes serious regressions. When you ship these google apps pre-installed you are basically limiting the rom to users who use gapps. There are many users who don't use gapps and actually prefer the default LineageOS apps instead. So I'm requesting OP to not ship any google apps as system apps. Yes I know I can disable those apps or better remove using magisk, but you know, users could also install those apps if they wanted with gapps. Thanks for understanding.
SayanChakroborty said:
Strangely enough it's been working fine since I disabled the app "Sounds" that enables Google Pixel Sounds as ringtones and alert tones. I have tested with and without the Sounds app enabled and I can confirm that app is causing this incoming call issue.
Unpopular opinion: Please don't ship Google apps as system apps in RR rom. Both google apps (Google Camera Go and Sounds) are problematic and causes serious regressions. When you ship these google apps pre-installed you are basically limiting the rom to users who use gapps. There are many users who don't use gapps and actually prefer the default LineageOS apps instead. So I'm requesting OP to not ship any google apps as system apps. Yes I know I can disable those apps or better remove using magisk, but you know, users could also install those apps if they wanted with gapps. Thanks for understanding.
Click to expand...
Click to collapse
Report ur problem to RR team
ahmedshaikh said:
Report ur problem to RR team
Click to expand...
Click to collapse
Wouldn't it be easier for you to report to RR team as you are officially maintaining the device? I don't know where to report.