[ROM] [Unofficial] [N7.1.2] AICP 12.1

[sid2109]

While I haven't tested a Bluetooth speaker yet, there's no such deep sleep bug for me. It's always responsive and wakes up instantly after clicking the home/power button. Which root method are you using? Are you using xposed? Any specific magisk/xposed module or any specific app might be causing the problem

Good to know it works well for you. I am currently using Magisk 18.0 and xposed framework is not installed on my phone. I am not sure if any specific app is causing the issue though. Any tips on how to figure that out?

Bluetooth speaker issue is very specific to all nougat ROMs on the forum. For a week or so when I used Comico's Oreo, there was such problem at all.

Today I installed this rom and sadly it doesn't work with AA either.

This is what I get (after pressing AA icon on car screen):



The phone is locked (black screen with white AA message). I've tried multiple USB cables and none of them worked. Other phones work fine, e.g. I've tried Xiaomi Redmi 4, IPhone X.

hmm.. this is not the behaviour i see at all. When I connect first time , screen goes blank (black in colour). Then I need to exit the andriod auto app on my phone once and then re-launch it. It works flawlessly after that. I have a honda car btw. not sure if the type of car infotainment system would matter here.

 

[AndroX99]

Good to know it works well for you. I am currently using Magisk 18.0 and xposed framework is not installed on my phone. I am not sure if any specific app is causing the issue though. Any tips on how to figure that out?

Bluetooth speaker issue is very specific to all nougat ROMs on the forum. For a week or so when I used Comico's Oreo, there was such problem at all.

Enter safe mode and test the device for a while and check if you face the same deep sleep problem. Send logs right after you face the problem (after both disconnect and deep sleep issue). Also you must have nd3 or newer bootloader and baseband for a stable experience

 

[ComicoX]

Bluetooth speaker issue is very specific to all nougat ROMs on the forum. For a week or so when I used Comico's Oreo, there was such problem at all.

You had problems with BT on my Oreo? Because on that an on my RR BT works perfectly

 

[ishtiak02]

You had problems with BT on my Oreo? Because on that an on my RR BT works perfectly

I suppose he meant BT speaker not headphone. It was working properly for him in Oreo but not in any nougat ROMs(probably your RR too). Bt headphones work perfectly here and other nougat ROMs. I only have WiFi speakers, so can't test it myself

 

[ComicoX]

I suppose he meant BT speaker not headphone. It was working properly for him in Oreo but not in any nougat ROMs(probably your RR too). Bt headphones work perfectly here and other nougat ROMs. I only have WiFi speakers, so can't test it myself

BT speaker should work the same as headphones

 

[AndroX99]

BT speaker should work the same as headphones

While the working principles of BT headphones and speakers are almost similar, BT speakers does need a stronger and stabler connection since the signal is highly amplified simultaneously by the built-in amplifier of the speaker after being received. I don't have any issues with BT headphones but if there's any disconnect issue with speakers, something is breaking/weakening the connection.
I can't debug the issue myself owing to the fact I only have WiFi and wired speakers.

 

[sid2109]

Enter safe mode and test the device for a while and check if you face the same deep sleep problem. Send logs right after you face the problem (after both disconnect and deep sleep issue). Also you must have nd3 or newer bootloader and baseband for a stable experience

I had to wipe the phone and re-flash due to some issue. This time I haven't restored all my apps from titanium backup yet. I have restored 70% of the apps only till now and the issue hasn't resurfaced yet. The screen wakes up almost instantly and takes at the most 2 seconds sometimes. I am testing the screen wake up after every app I restore. If I hit upon the same issue, it will be easy to figure out which app caused it. I will let you know.

You had problems with BT on my Oreo? Because on that an on my RR BT works perfectly

No problems at all with your Oreo ROM. BT worked without any issues with speaker. But there was a weird BT problem with your ROM. When I connected to a bluetooth headphone, audio worked fine for all kind of media but when receiving a call, I couldn't hear the caller. Screen wakeup wasn't a problem either. This is why I was crossing my fingers that you squash all the remaining bugs on that ROM (I made a donation to your paypal account as well )

 

[ComicoX]

No problems at all with your Oreo ROM. BT worked without any issues with speaker. But there was a weird BT problem with your ROM. When I connected to a bluetooth headphone, audio worked fine for all kind of media but when receiving a call, I couldn't hear the caller. Screen wakeup wasn't a problem either. This is why I was crossing my fingers that you squash all the remaining bugs on that ROM (I made a donation to your paypal account as well )

I'm trying to find a way to fix BT headphones during the call. I've made Pie now and I've fixed some sensors on it

 

[Mythtr]

screen lag

hi AndroX99, in this romda full of signal level in the middle of the city but the line is self-breaking and the signal disappears from 30 to 40 maybe 60 sec. The signal comes back after max 60 or 90 sec. Pascua Hybrid v13 kernel fixes when it installs, but the SCREEN LAG issues are beginning to get this. The same problem I've tried in CRDROID is also happening there. How can you help? where are we making mistakes?
I use Bootloader: N7100XXSFQA
The Modem I'm Using: N7100XXUFOA1
Location: Turkey

 

[AndroX99]

hi AndroX99, in this romda full of signal level in the middle of the city but the line is self-breaking and the signal disappears from 30 to 40 maybe 60 sec. The signal comes back after max 60 or 90 sec. Pascua Hybrid v13 kernel fixes when it installs, but the SCREEN LAG issues are beginning to get this. The same problem I've tried in CRDROID is also happening there. How can you help? where are we making mistakes?
I use Bootloader: N7100XXSFQA
The Modem I'm Using: N7100XXUFOA1
Location: Turkey

Please send me a log right after the signal breaks. Use the stock kernel to avoid lags, it's tested to work fine (Can't say anything about the signal issue until I receive a logcat, works fine for me. Can anyone else confirm if it works fine or there's an issue ?)

 

[ishtiak02]

hi AndroX99, in this romda full of signal level in the middle of the city but the line is self-breaking and the signal disappears from 30 to 40 maybe 60 sec. The signal comes back after max 60 or 90 sec. Pascua Hybrid v13 kernel fixes when it installs, but the SCREEN LAG issues are beginning to get this. The same problem I've tried in CRDROID is also happening there. How can you help? where are we making mistakes?
I use Bootloader: N7100XXSFQA
The Modem I'm Using: N7100XXUFOA1
Location: Turkey

Please send me a log right after the signal breaks. Use the stock kernel to avoid lags, it's tested to work fine (Can't say anything about the signal issue until I receive a logcat, works fine for me. Can anyone else confirm if it works fine or there's an issue ?)

No signal breaks for me. It often occurred to me in other ROMs when I used old FNE1 modem. Never used an old modem with this ROM but it was fixed ever since I upgraded to FNG1 in the other ROMs

 

[Mythtr]

Please send me a log right after the signal breaks. Use the stock kernel to avoid lags, it's tested to work fine (Can't say anything about the signal issue until I receive a logcat, works fine for me. Can anyone else confirm if it works fine or there's an issue ?)

What file path will I receive from Log?

GT-N7100 cihazımdan Tapatalk kullanılarak gönderildi

---------- Post added at 04:23 PM ---------- Previous post was at 04:07 PM ----------

No signal breaks for me. It often occurred to me in other ROMs when I used old FNE1 modem. Never used an old modem with this ROM but it was fixed ever since I upgraded to FNG1 in the other ROMs

I'm using the BL N7100XXSFQA5, CP N7100XXUFOA1. You sent it to me. Should I use BL_N7100XXSFQE2, CP_N7100XXUFNG1?

GT-N7100 cihazımdan Tapatalk kullanılarak gönderildi

 

[ishtiak02]

What file path will I receive from Log?

GT-N7100 cihazımdan Tapatalk kullanılarak gönderildi

---------- Post added at 04:23 PM ---------- Previous post was at 04:07 PM ----------

I'm using the BL N7100XXSFQA5, CP N7100XXUFOA1. You sent it to me. Should I use BL_N7100XXSFQE2, CP_N7100XXUFNG1?

GT-N7100 cihazımdan Tapatalk kullanılarak gönderildi

You can try them. Backup your current modem first. Clean flash recommended after changing them. You can take logs with catlog app or do
logcat > /sdcard/x.log in terminal

 

[Mythtr]

You can try them. Backup your current modem first. Clean flash recommended after changing them. You can take logs with catlog app or do Ishtiak02:
Use catlog or do
logcat > /sdcard/x.log in terminal

This application?

GT-N7100 cihazımdan Tapatalk kullanılarak gönderildi

 

[ishtiak02]

This application?

GT-N7100 cihazımdan Tapatalk kullanılarak gönderildi

Yes, take the log after the problem occurs

 

[Mythtr]

Yes, take the log after the problem occurs

With TWRP restored, I returned to the original backup. I uploaded the BL and CP files you sent me with ODIN. I did cache and dalvik cache cleaning. I will continue to test. I'll send the logs if I have a problem

GT-N7100 cihazımdan Tapatalk kullanılarak gönderildi

 

[Mythtr]

You can try them. Backup your current modem first. Clean flash recommended after changing them. You can take logs with catlog app or do
logcat > /sdcard/x.log in terminal

Hi, I've been trying for two days, the conversation stopped. In addition, the screen came back after a very long time and the default wallpaper was pressed continuously. He had removed my wallpaper. I couldn't add the logs. Another file type from the image did not accept this place. I'm giving you a wetransfer link.

https://we.tl/t-xp6xHynPhi


GT-N7100 cihazımdan Tapatalk kullanılarak gönderildi

 

[ishtiak02]

Hi, I've been trying for two days, the conversation stopped. In addition, the screen came back after a very long time and the default wallpaper was pressed continuously. He had removed my wallpaper. I couldn't add the logs. Another file type from the image did not accept this place. I'm giving you a wetransfer link.

https://we.tl/t-xp6xHynPhi


GT-N7100 cihazımdan Tapatalk kullanılarak gönderildi

I guess you haven't done a clean flash after flashing new modem and bl. Some people have reported wierd issues including high battery drain after flashing a new modem or bl and not clean flashing afterwards. You should do one and hopefully it'll fix your problems

 

[AndroX99]

Hi, I've been trying for two days, the conversation stopped. In addition, the screen came back after a very long time and the default wallpaper was pressed continuously. He had removed my wallpaper. I couldn't add the logs. Another file type from the image did not accept this place. I'm giving you a wetransfer link.

https://we.tl/t-xp6xHynPhi


GT-N7100 cihazımdan Tapatalk kullanılarak gönderildi

Do a clean flash as suggested and if you face any more force stops, restore selinux contexts by running "restorecon -RF /data" and "restorecon -RF /data/media"

 

[Mythtr]

I guess you haven't done a clean flash after flashing new modem and bl. Some people have reported wierd issues including high battery drain after flashing a new modem or bl and not clean flashing afterwards. You should do one and hopefully it'll fix your problems

Do a clean flash as suggested and if you face any more force stops, restore selinux contexts by running "restorecon -RF /data" and "restorecon -RF /data/media"

You guys are great. Thank you so much. I'il do the practice and return the result.