Hi!
I just moved from the old PAC-ROM to the new PAC Black-Power one, and I have some questions.
I still have a problem with my screen turning black when calling, also, I cant seem to find any paranoid android settings in this rom? I LOVED the old pac rom, but my screen turned black when calling, so that was the reason I tried chaning rom.
We don't officially support the Black-Power. You'll have to talk to your maintainer about that.
Sent from my SGH-I337M using Tapatalk
Related
I have tried several rom/kernel combinations on two Nexus 7's and noticed that while doing normal internet surfing or using basic applications that the screen will black out for second then come back on and resume where it was. I noticed some posts on this in the android development sections, yet no one seems to have a fix. Is this a software thing or a hardware thing?
I noticed this when I installed CM10 based PA, so I guess it's a ROM issue.
Its the surfaceflinger issue. They did something recently to it and im guessing dont realize its a bug.. but let me link you the fix it will work on any ROM.
surfaceflinger-fix.zip Flash in recovery and enjoy.
Everything was perfect when i was on Android 4.3, any skype calls working, video/audio doesn't matter.
But when i updated my wife's phone to kitkat, some skype calls making phone reboot(black screen, then its loading as usual).
It happens not always. And i have noticed that it crashes only while talking to people who have Windows XP installed(with latest version of skype, checked & updated myself).
When she talks to anyone on 7&8 Windows - everything is perfect.
I have tried all custom roms, original, rooted\not rooted, anything.
I gonna write this issue to Skype too.
Skype support asked that Skype not supporting KitKat yet.
Btw it only happens on Nexus 4, when i'm on my phone (XT910) on KitKat, it works and not hangs.
In my case occurs the same...I believe is maybe kit Kat by itself and usually happens when I leave a call in the background while I use another application. Unfortunately I haven't found any solution for that.
i have noticed that it crashes only while talking to people who have Windows XP installed(with latest version of skype, checked & updated myself).
Click to expand...
Click to collapse
Not really. The problem is a bit more serious: all ROMs (stock and custom) based on 4.3 or 4.4 are affected by this overly annoying camera bug. I obviously hope you're not, but if you end up as unlucky as I did, your camera and LED flash will soon become totally unusable (on all applications), fixable only by reverting to 4.2 or updating to L (I did and it's totally worth it)
Good luck :good:
Also another issue with Skype and N4 is that whrn listening to music and an image is being sent / received in the Skype chat window, fetching that image from the gallery/disk causes the audio system to crash. It's really annoying. Probably it's the same issue as the well-known audio stutters on changing connectivity and high cpu load.
Im using the Verizon G2 and running 4.4 2...xdabebb rom..i use skype a lot for business calls and havent come across this issue at all. On unrooted stock as well as custom. Ive also faced no issues on an S4 i9500...so it might not really be a kit kat issue but a nexus 4 specific...or an aosp based rom specific issue
Sent from my VS980 4G using Tapatalk
I have another kind of issue with my xiaomi Mi2 with MIUI Rom on kitkat 4.4.4. I have systematically a black screen when the communication is established on Skype also using test sound server. The sound is working but I can't do nothing with the phone until the end of communication decided by my correspondant.. Very annoying . I have post the question to Skype 5 days ago but no answer. Skype was working properly on my phone on miuiv5 android 4.1.2
Envoyé depuis mon Mi2 kitkat 4.4.4 Miui6
I'm having the exact same problem ... I was talking on Skype video call and the phone screen went black and I couldn't hear the other party.. I don't if they were able to hear me or not. I had to hold the power button and reboot my phone manually. I don't know what the problem is but its very annoying and it happened three times in a row. I have used multiple ROMs and it was happening on all of them and they were all 4.4.4. I don't flash kernels, I just use the kernels that come with ROM because they have obviously been tested and have been found compatible with the rom. So I know its not because of kernels. Currently I'm on Slimkat latest weekly and was thinking about going back to stock but someone said its also happening on stock ROM. I'm going to try CM11 and see if it happens there as well. Will report back soon. Hopefully it's just a 4.4.4 issue and not a phone issue.
Sent from my Nexus 4 using XDA Free mobile app
I'm using an LG G2, D801 Tmobile variant, and I've tried AOKP, OmniRom, Gummy, Paranoid Android, VanirAOSP, Hellfire, Carbon and even Cyanogen. Jellybean and KitKat based, they all have this touch screen issue with certain apps. I've used Robert Broglia's .emu emulators, Dead Space, 10000000, Retroarch, and a bunch of other apps, and they don't respond to the touch screen. Like the touch input just turns off while the screen stays on. the only way out of some of these apps is either backing out using the back button or hitting home. I keep coming back to Buckeye's rom or a stock based rom and those don't have this issue. I want to use AOSP roms, especially because KitKat is really nice, but a lot of these apps not working makes me come back to stock. If anyone knows about this issue or a fix for it, please let me know.
Hey guys,
actually this is a general aokp question but I don't know where such questions are posted. Since I installed aokp on my Nexus 4, I'm posting it here in the Nexus 4 board. A week ago I installed a new aokp version (based on Android 4.3). In my former aokp version (based on Android 4.2) I configured the LED to inform me about the charging state if the phone is plugged into some power outlet. So I could roughly guess the battery status by watching the LED color. Now in the new aokp version I want to activate this setting again but I can't find it. Probably it's at the same place as before but I don't know where it was. I checked out all the menus where I thought it could be but without success. I hope you can help me. Thx.
Hello, I'm a fresh member of this forum and recently upgraded my Galaxy Samsung S4 (i9505) from stock to AOSP Oreo. After the upgrade everything worked more or less as expected, the ROM is stable enough for daily use.
Unfortunately the S-view is not working like expected, if I open the (original) Samsung s-view cover the screen lights up and if I close the cover the screen goes off, but there is no clock in the display as before. Also with an incoming phone call the screen doesn't show up, or I can pick up the call by wiping over the cover window.
I installed the files below:
Unofficial TWRP recovery.img
JDCTeam-8.1.0-20171209-BETA.zip
open_gapps-arm-8.1-nano-20180119-UNOFFICIAL.zip
Kernel-B--B-PWR-CORE-AOSP-O-v3.2.zip
SR5-SuperSU-v2.82-SR5-20171001224502.zip
Also, I tried the 'S View Lite' app from play store. After closing the cover the screen is shown for a few milliseconds,but no sulution there. I also repeated the installation a few times (thanks for the nice youtube video's) to be sure I made no mistakes.
Because I miss the S-view functionality like it worked before, I post this question on the Q&A (my question on jdcteam-android-source-project-oreo-t3685231 did not get much response). Maybe someone can help me to get it going, tell me if it's working on her/his dvice or tell me I have to live with it like it is ?
there is no lineageOS rom with the Sview.
the Sview is based only on TW rom, so nothing newer more than a 5.0.1 TW rom.
and all Sview apps don't work correctly.
If you want S View, go back to TouchWiz.
If it's ever going to work on AOSP ROMs, it only does to lock the screen instead.
Sent from my Redmi Note 4 using XDA Labs