Database Develop

[APP] 50% time without a signal fix - 2/2/2011

App: xtr50fix Android 2.1 only.
I made this app to try to help those with the 50% time without a signal issue. Learn more here ( http://forum.xda-developers.com/archive/index.php/t-647980.html)
The one trick that works with most 2.1 Eris ROMs is the airplane mode trick. All you do is put your phone in airplane mode for a little bit and turn airplane mode off and it fixes the issue.
Basically all this app does is upon boot, puts the phone in airplane mode then waits 12 seconds and then turns off airplane mode. Finally, it kills the service so it won't run again until the next reboot.
I know it's not elegant or anything, but it seems to do the job. There are no settings and there is no icon for the app. Just install the .apk and reboot your device.
Please let me know any feedback you might have... good or bad. Thanks!
2/2/2011 - v1 - Initial build. Seems to work fine on xtrROM and xtrSense.
Added some checks to make sure you are not already in airplane mode upon boot.

Sounds interesting, thanks! I just went back to xtrSENSE so this is perfect timing.

has anyone tried this app yet?

I went with this route and it helped me
[How-To] Better battery life, reduce Time Without Signal.
http://forum.xda-developers.com/showthread.php?t=651848
I read that some users report that the 'airplane trick' doesn't always work for them.

moos3y said:
I went with this route and it helped me
[How-To] Better battery life, reduce Time Without Signal.
http://forum.xda-developers.com/showthread.php?t=651848
I read that some users report that the 'airplane trick' doesn't always work for them.
Click to expand...
Click to collapse
Yes, that works as well, however, you still have to do that every time you boot up.

This seems to have worked on my optimus v. Thanks for your efforts!
Prior to this, I was constantly getting the 50% without signal mess...

Works perfectly on my Optimus V. Thanks so much for developing and sharing this fix.

Thank you lotus22! This has been included in the latest release of xtrSENSE http://forum.xda-developers.com/showthread.php?t=726467

Would this work on a Droid X? I get that bug and I'm rooted with stock 2.2.

chadw80 said:
Would this work on a Droid X? I get that bug and I'm rooted with stock 2.2.
Click to expand...
Click to collapse
I'm only replying so you don't feel ignored. No idea, myself, but can you do a nandroid on the X and try flashing this to see? You might be the first person to try, so you can let us know if it works!
For the record to everyone, this seems to work just fine with Gingerbread ROMs, too.

roirraW "edor" ehT said:
I'm only replying so you don't feel ignored. No idea, myself, but can you do a nandroid on the X and try flashing this to see? You might be the first person to try, so you can let us know if it works!
For the record to everyone, this seems to work just fine with Gingerbread ROMs, too.
Click to expand...
Click to collapse
Lol appreciate it! Unfortunately it didn't put my phone in airplane mode when it booted back up.

I don't have a Droid X to test on... however, I did compile the program with the Android 2.1 SDK so it should work on anything with >= Android 2.1
Note: Don't flash this program. Just install the .apk like normal.

zach.xtr said:
Thank you lotus22! This has been included in the latest release of xtrSENSE http://forum.xda-developers.com/showthread.php?t=726467
Click to expand...
Click to collapse
Thanks Zach! Glad you included it. I bought a Motorola Droid off my friend so I don't use an Eris for my main phone anymore. I'll have to test this out on my mom's Eris which uses xtrSense!

This app fixes the 3G drops with my Optimus V. If anyone is looking for automated reboots in order to automatically apply this fix every day, I use Phone Prioritizer.

Thanks for this. Hopefully my battery life increases.

Can someone tell me how to install the fix on an Optimus V? I tried downloading it directly and I get a message saying it is unsupported. I also tried installing it from gmail and it didn't work either.
I am about ready to return the phone if I can't get it to work.
Thanks,
Paul

Make sure in settings->Applications-> you turn on Installing Apps from Unknown Sources.

TWS/data drop fix
The fix50 app did fix the TWS problem on my optimus but didn't seem to do much for the battery or fix the data drop issue. I ran across this fix posted by greenmonster on an Android Central forum (http://forum.androidcentral.com/optimus-v/57943-excessive-battery-drain-even-standby.html):
To fix the issue, dial *#*#4636#*#* and it will load the testing screen. You do not have to press call. Select phone information.
My understanding of the bug is that even though the preferred network is set to "CDMA auto (PRL)", it is actually set to "GSM/CDMA auto (PRL)" because of a display bug.
The fix is to press Menu and then "Select radio band". The process will then force close. Go back to Phone info and select "CDMA only" and then select "CDMA auto (PRL)".
Click to expand...
Click to collapse
I'm going on day 3 now (no reboot) and have had a noticeable increase in battery life an no data drops that require an airplane mode toggle. Any way this might be made/incorporated into an app similar to fix50?

Data drop/TWS update
So I finally had a hiccup about 9:00 last night that caused a data drop- it was right after I lost a phone call & during a pretty serious storm, so don't know if that affected anything. I'm still pretty happy- I've never gone more than three or four hours without having to do the airplane mode toggle due to data drops- 60 hours without a drop is encouraging!
Time without signal also stayed in the single digits...

Installed and working on my Captivate running Froyo. Good stuff.
Sent from my Captivate

[Q] Need to wait a while for the screen to turn on

Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you

Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really

tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up

delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?

Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!

Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good

tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?

I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.

LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?

Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.

tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?

tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.

sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values

Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk

Xperia T Official 4.3 Update Bugs

There's an annoying bug in the 4.3 update,volume level doesn't appear when changing volume.
Tell me if you've discovered any other bugs

MetalDaRyl said:
There's an annoying bug in the 4.3 update,volume level doesn't appear when changing volume.
Tell me if you've discovered any other bugs
Click to expand...
Click to collapse
Try rebooting your device! Havent seen this issue

Try reflashing the ROM or flash the one from another region, sometimes it's region dependent, on one device it may have bugs, on another it may not
My phone is T. Xperia T.

MetalDaRyl said:
There's an annoying bug in the 4.3 update,volume level doesn't appear when changing volume.
Tell me if you've discovered any other bugs
Click to expand...
Click to collapse
I have exact same problem ; volume level animation was working well until i connected earphones

Xperia T 4.3 bugs
I have the same volume slider bug. I tried to do a clean install of the firmware and that resolved it for all of an hour then it's back to the black bar. My phone has also turned itself off while on the charger once. I recall this being a bug with the leaked firmware but assumed it would be resolved in the final release version

having same problem but whjen insatleed the update it was normal but in between i am also facing problem of no slider animation......
i have attached scrren shot...

The main problem
Its not the roms its the theme this bug only happens when changing the theme its expected really I assume the apk for that them isn't compatible with the t really causing the volume bar to look like that. its something sony need to work on when making these apks for all xperia 4.3 devices . maybe a dev can fix it or modify the apk

MetalDaRyl said:
There's an annoying bug in the 4.3 update,volume level doesn't appear when changing volume.
Tell me if you've discovered any other bugs
Click to expand...
Click to collapse
its only problem when you download theme and change

Thanks to all of you for your replies!

Select any pre-installed theme,reboot...will fix the problem

volume panel.problem
Dear members,
I m also facing the same volume panel problem in VODAFONE firmware. After installing CE1 firmware the is was rectified. Now dont have any issues.

MetalDaRyl said:
Select any pre-installed theme,reboot...will fix the problem
Click to expand...
Click to collapse
Thanks a lot. it works for me.

MetalDaRyl said:
Select any pre-installed theme,reboot...will fix the problem
Click to expand...
Click to collapse
Thanks. After playing around with it I've determined that my issue appears to have been related to the 'Tri Flat' theme. When I switch back to one of the pre-installed themes and reboot, everything seems to work fine. Shame really coz I really like that theme

Vodafone UK, wifi disables and have to switch in and out of aeroplane mode for it to re-enable

hi
MetalDaRyl said:
There's an annoying bug in the 4.3 update,volume level doesn't appear when changing volume.
Tell me if you've discovered any other bugs
Click to expand...
Click to collapse
hi am have the same issues

[Q] Does everyone face screen flickering 12.1.A.1.201

Hey guys just looking for a definitive answer here. As 4.1.2 has no screen flickering bug, and on 4.3 it comes up automatically... I can assume its a software glitch rather then hardware .. then why isnt everyone having that issue? and why cant sony fix it.
I just updated to 12.1.A.1.201 and although the flicker has reduce, its still there in greys/blacks. Going back to 4.1.2 again.

magicali said:
Hey guys just looking for a definitive answer here. As 4.1.2 has no screen flickering bug, and on 4.3 it comes up automatically... I can assume its a software glitch rather then hardware .. then why isnt everyone having that issue? and why cant sony fix it.
I just updated to 12.1.A.1.201 and although the flicker has reduce, its still there in greys/blacks. Going back to 4.1.2 again.
Click to expand...
Click to collapse
cause sony sucks!! we said that.. they have your money they dont care any more i think a 20% at least have this flickering..
edit: check my thread and check the pictures http://forum.xda-developers.com/showthread.php?p=51553670

I have flickering bug on 4.1.2 with backlight turned off and auto brightness on
Sent from my C5303 using Tapatalk

I don't have any screen flickering things. Everything's normal with .266

hmm sound good to leave something here while watch what others feel about the new firmware before upgrading. Give some review guys

Just updated (only 9MB?!?!?). I'm on global generic firmware and still get the flickering screen with greys and blacks.
I don't think its as prominent as it was, and I definitely didn't get it with 4.1.2 software.
My screen is set to auto adjust its brightness and I think it's more noticeable when changing now.
That aside, its less laggy now!

The flicker issue was resolved by disabling adaptive brightness for me and some others but not for everyone.

Simple step...
Select wallpaper from album using google+ ( using scroll wallpaper)
Done
Hit the home icon 2 or 3 times
Problem solved.... Works for me.....

ArunThazhathuveetil said:
Simple step...
Select wallpaper from album using google+ ( using scroll wallpaper)
Done
Hit the home icon 2 or 3 times
Problem solved.... Works for me.....
Click to expand...
Click to collapse
That seems like an unnatural fix :S .. you have faced the screen flicker issue on 4.3 or 4.1.2?

magicali said:
That seems like an unnatural fix :S .. you have faced the screen flicker issue on 4.3 or 4.1.2?
Click to expand...
Click to collapse
Ha ha I will not even try it

ParaSense. said:
Ha ha I will not even try it
Click to expand...
Click to collapse
Neither will I

Try these..
# developer options> check "disable HW overlays"
#Not working.. then also check "force gpu rendering"
Source: http://www.landoftechnology.com/2012/fix-for-the-screen-flickering-on-devices-running-android-4-2/
#Or.. Try pimp my rom app and do what it says here: http://forums.androidcentral.com/sa...ot-users-dreaded-screen-flickering-issue.html (need root).
**I don't have this issue, so I dunno whether these work. No harm trying these. Saw the video in YT, that flickering really sucks!

mrhnet said:
Try these..
# developer options> check "disable HW overlays"
#Not working.. then also check "force gpu rendering"
Source: http://www.landoftechnology.com/2012/fix-for-the-screen-flickering-on-devices-running-android-4-2/
#Or.. Try pimp my rom app and do what it says here: http://forums.androidcentral.com/sa...ot-users-dreaded-screen-flickering-issue.html (need root).
**I don't have this issue, so I dunno whether these work. No harm trying these. Saw the video in YT, that flickering really sucks!
Click to expand...
Click to collapse
Doesn't work for me Thanks for the tip though

mrhnet said:
Try these..
# developer options> check "disable HW overlays"
#Not working.. then also check "force gpu rendering"
Source: http://www.landoftechnology.com/2012/fix-for-the-screen-flickering-on-devices-running-android-4-2/
#Or.. Try pimp my rom app and do what it says here: http://forums.androidcentral.com/sa...ot-users-dreaded-screen-flickering-issue.html (need root).
**I don't have this issue, so I dunno whether these work. No harm trying these. Saw the video in YT, that flickering really sucks!
Click to expand...
Click to collapse
i have tried everything except pimp my rom... but i dont think it will solve this problem cause i have this flickering even in recovery (cwm,twrp) if 4.3 kernel is installed

ParaSense. said:
i have tried everything except pimp my rom... but i dont think it will solve this problem cause i have this flickering even in recovery (cwm,twrp) if 4.3 kernel is installed
Click to expand...
Click to collapse
Yes.. it looks like a issue at kernel level/gpu driver. But those workarounds worked for some. Maybe it could be another issue..
If you are still in 4.3, just type this in a terminal:
cat /d/clk/mdp_vsync_clk/enable
If it returns 0, type:
su
echo 1 > /d/clk/mdp_vsync_clk/enable
It fixed for some, but not sure whether it's the same "flickering" issue. Just a tip..

I have read this thread and (more other) and always wondering what are you people talking about??
Only flickering which I have seen on my sp was when I had auto brightnes on. But this is how auto brightness should work.
On 4.1 wasnt any flickering because auto brightnes didnt work on 4.1
On 4.3 work a little better, but not so good as for example in CM 11.
But when u turn off auto brightness there isnt any "flickering".

mrhnet said:
Yes.. it looks like a issue at kernel level/gpu driver. But those workarounds worked for some. Maybe it could be another issue..
If you are still in 4.3, just type this in a terminal:
cat /d/clk/mdp_vsync_clk/enable
If it returns 0, type:
su
echo 1 > /d/clk/mdp_vsync_clk/enable
It fixed for some, but not sure whether it's the same "flickering" issue. Just a tip..
Click to expand...
Click to collapse
I really dont want to install again 4.3 to try this (maybe it will work) not now at least.. but i will try it some time... thanks

Resurrection Remix (Exynos) Discussion Thread

This thread is for discussion of the Resurrection Remix build on the Exynos
The RR build is available for download here

After turning camera on for a few times this happens.
Also there's an icon for multiwindow in recently menu but it doesn't work and cannot be turned off, kind of bothers me.

Just wondering @dl12345 , so if we have any issues or we find a bug that related with RR but not lineage it won't get fixed, even if we provide logs? I'm kind of confused on how you phrased it when you said that you wouldn't deal with RR bugs but you would still update this after every lineage build release. Would the newer builds of RR that's based on the newer builds of lineage cause issues later on?

RetroSpect_17 said:
Just wondering @dl12345 , so if we have any issues or we find a bug that related with RR but not lineage it won't get fixed, even if we provide logs? I'm kind of confused on how you phrased it when you said that you wouldn't deal with RR bugs but you would still update this after every lineage build release. Would the newer builds of RR that's based on the newer builds of lineage cause issues later on?
Click to expand...
Click to collapse
I mean that if there is an RR specific bug then it won't get fixed until such times as the LineageOS build is fully stable. I'm already spending a lot of time getting the LineageOS build stable and I really don't have time to deal with two ROMs simultaneously. I released this RR build because quite a few people want it.
RR is based off LineageOS so actually compiling a build is not time consuming - I just point it to the same repository as my LineageOS build and tell it to build. This is why I am happy to release a RR build whenever I release a LineageOS build.

Thanks for this build, flashed now and all is working ok.

ROM faster and super smoothly.
In addition to the camera, which after some photos fails, there is the bug of the previous RR build, after a call all the audio are muted. Only rebooting or using Tasker to kill mediaserver after call audio work again.

Jc_Py said:
ROM faster and super smoothly.
In addition to the camera, which after some photos fails, there is the bug of the previous RR build, after a call all the audio are muted. Only rebooting or using Tasker to kill mediaserver after call audio work again.
Click to expand...
Click to collapse
You have any tips on how to use Tasker to kill media server after call?

DahakePL said:
You have any tips on how to use Tasker to kill media server after call?
Click to expand...
Click to collapse
This is my Tasker backup.
Install Tasker and restore this.
Basically Tasker will kill media server and play a beep after a call.

The run shell task must be root granted.

Jc_Py said:
ROM faster and super smoothly.
In addition to the camera, which after some photos fails, there is the bug of the previous RR build, after a call all the audio are muted. Only rebooting or using Tasker to kill mediaserver after call audio work again.
Click to expand...
Click to collapse
Try run /system/bin/unmute-call-audio after making a call.
This is the app I use to unmute the audio on boot up. Be interesting to see if it fixes the problem....

dl12345 said:
Try run /system/bin/unmute-call-audio after making a call.
This is the app I use to unmute the audio on boot up. Be interesting to see if it fixes the problem....
Click to expand...
Click to collapse
Only for testing, flashed ROM again and now after call audio works normally, without Tasker.
If the bug appears again I will try your suggestion.
Thanks

Has anyone noticed something with wrong with their accelerometer sensors? After awhile mine seems to stop working and don't change between the landscape and portrait modes.
I'll try to get logs for the next time it happens.
P.S. Do you guys have any suggestions for logging app for convenience?

webmanya said:
Has anyone noticed something with wrong with their accelerometer sensors? After awhile mine seems to stop working and don't change between the landscape and portrait modes.
I'll try to get logs for the next time it happens.
P.S. Do you guys have any suggestions for logging app for convenience?
Click to expand...
Click to collapse
From what I heard on the lineage thread try opening YouTube app and go back to the other application you were using. For some reason he said that it works.

RetroSpect_17 said:
From what I heard on the lineage thread try opening YouTube app and go back to the other application you were using. For some reason he said that it works.
Click to expand...
Click to collapse
Just do screen OFF/ON by power button and all works again...
Отправлено с моего SM-N910C через Tapatalk

best rom is ever used for n910c I think. Thank you so much for building this rom.

RetroSpect_17 said:
From what I heard on the lineage thread try opening YouTube app and go back to the other application you were using. For some reason he said that it works.
Click to expand...
Click to collapse
Yes this one works... But not always.
ukrbroker said:
Just do screen OFF/ON by power button and all works again...
Отправлено с моего SM-N910C через Tapatalk
Click to expand...
Click to collapse
I tried this but it doesn't work...

https://drive.google.com/open?id=1t3J78N0tqOMmQj2NDma6wf28MPPeryEh
If anyone is interested here's a RR boot animation which is normal sized since the one in the rom is really tiny (flashable)

I haven't find these mentioned yet but can someone confirm this isn't just me? Also I'm not sure if this is related to a WhatsApp bug or the ROM. Thanks in advance.
while you're using WhatsApp voice call it looks like screen closes but it continues to register touches even if you turn off the screen using the power button.
Also while listening to the voice messages of you cover the proximity sensor it turns off the screen and stops the playing message.

Hi guys, can I flash the stock Android 6.0 over this, or will it brick my phone?
I have TWRP and rooted with Magisk
thanks

Any way to fix the system apps keeps crashing? only factory reset solves the problem but after 1 hour the problem occurs but on different system app.
example
stock email app
Keeps closing when opening a mail
after factory reset
email works
contacts closing
email closing