Hello,
a few minutes ago I made a phone call with the default phone app and detected a button. But I don't know what it does? It only appears while making a call and pressing it, seems to do nothing.
I'm using the newest Linage OS (Android 7.1) on the One Plus 3 with installed GApps Pico.
Can someone help me?
Related
Hi guys, i have a problem with navigation Button (Home and Option) after installing 7.1.3 global rom (i'm not sure about veraion), after 1 week after installing the rom they juat stop work... Work only a back button. I tries with clean installing 7.5.1 and they work normally for 4-5 days, and after that again stopped... I tries with update to last veraion on MIUI but no without success. Can someone help me?
Now this is the weirdest thing I've ever encountered! I have a Samsung Galaxy Note 8.0 tablet (n5110) which runs TWRP recovery and Resurrection-Remix-5.7.4 (CM13 based). Everything used to work beautifully until the end of July when an app called “EPB DVR Manager” (in the Play store) received an update. My tablet had to do a whole bunch of updates, so I gave it the “go” and Play Store started doing its thing, updating one app after the other.
At some point the tablet froze. Dead. Even the clock in the status bar stopped. I had to reset the device by pressing and holding power until it rebooted. The next thing was ... boot loop. It seemed to finish the boot animation and at the point when the main screen is supposed to show up it rebooted!
Tried to wipe dalvik & cache. No go, still boot loop. Had to format data to get the device back to life. From there it took me quite some hours of repeated tries of restoring 100+ apps and crashing the device all over until I figured out that it was this specific app - the “EPB DVR Manager”. After figuring out that this app causes the problem, I did two more attempts to confirm what is going on:
First, I did a wipe of dalvik, cache & data, reboot, android setup wizard (setup Google account). Then, as the first action at all, I tried to install the “EPB DVR Manager”. Boom - device messed up again.
Second, I reverted back to stock firmware (kitkat) and installed the “EPB DVR Manager” - no problem at all. So it has something to do with the Resurrection-Remix ROM, but here's the thing:
I have 3 different devices (a Moto G 3rd Gen, a LG GPAD 7.0 and that Samsung Note 8.0) and all three of them run Resurrection-Remix 5.7.4 and the Samsung is the only device which all in a sudden has these catastrophic problems with the latest version of this app (earlier versions installed/updated fine).
Now I understand that my devices run different kernels with different hardware drivers despite all of them running RR-5.7.4.
I would really like to get a clue about what the heck is going on here. Now before y'all are telling me that RR-5.7.4 is dead because it is based on CM13 - I know that. Still, RR-5.7.4 is a way better daily driver than the newer Nougat builds. So how should I try to get “live logs” because the problem always ends in a crashed installation and Android needs a full wipe to recover. I would like to find out what is going on to be able to let the app developer know about the problem (if the app's apk is at least partially to blame).
Even if it turns out that it is RR's fault (and therefore the bug will not be fixed because RR-5.7.4 is dead) I would still want to learn how such a simple transaction like installing an app can cause such a dramatic (and 100% reproducible) crash of Android's data partition.
Thanks for any suggestions on how to catch logging information for this kind of mystery.
Markus.
Until yesterday I had the MIUI ROM for my Redmi Note 4, however I wanted to send another two ROMS (Lineage and Resurrection Remix) to see if they would convince me.
(I clarify that I already knew the process to install Roms).
So I rebooted in Recovery mode, hize / wipe and then install Lineague, but automatically I realized that I was making an error, saying that the rom was for Mido and that my cell phone instead of mido was, literally, a point.
So I turned on the pc, use the xiaomiMiFlash tool to install a miui rom (of course, with the option of clean_all) and unpleasantly I was surprised that it restarted every 20 or 30 sec., Please I need help, because I've tried other roms and it's still the same, turn it on, exit the start menu and after a few seconds it restarts. Tell me what I can do.
What does this mean - "my cell phone instead of mido was, literally, a point"? What cellphone do you have?
rossarnie said:
What does this mean - "my cell phone instead of mido was, literally, a point"? What cellphone do you have?
Click to expand...
Click to collapse
I have a Redmi Note 4(Mido, the version with a Qualcomm CPU) and this restarts every 30 sec, I've even used MiFlash to flash the rom with the option to clean everything and even so it remains the same.
I already try with this guide: https://forum.xda-developers.com/redmi-note-4/how-to/how-to-fix-totally-dead-redmi-note-4-t3746465 and nothing, I get an error of "Sahara" with qfil
Treinor said:
Until yesterday I had the MIUI ROM for my Redmi Note 4, however I wanted to send another two ROMS (Lineage and Resurrection Remix) to see if they would convince me.
(I clarify that I already knew the process to install Roms).
So I rebooted in Recovery mode, hize / wipe and then install Lineague, but automatically I realized that I was making an error, saying that the rom was for Mido and that my cell phone instead of mido was, literally, a point.
So I turned on the pc, use the xiaomiMiFlash tool to install a miui rom (of course, with the option of clean_all) and unpleasantly I was surprised that it restarted every 20 or 30 sec., Please I need help, because I've tried other roms and it's still the same, turn it on, exit the start menu and after a few seconds it restarts. Tell me what I can do.
Click to expand...
Click to collapse
I guess you flashed a treble ROM using a non treble recovery. Use this recovery and try to flash lineage OS again.
https://drive.google.com/a/my.smccd.edu/uc?id=1I_EaHHPWERIaMyBasfGJldugLjadU13P&export=download
Hello, when using (D855) stock rom and stock based rom (Fulmics 8), the phone freezes extremely after the account and apps are installed, I can't take any action, The system is not responding, the home screen is not responding errors, also the phone is unavailable when I put a screen lock it becomes, the password cannot be entered (I don't think it's hardware related as it works very well when using Lineage OS) Used when Nova Launcher is installed (no screen lock), but when you open the notification panel, vibrate the phone, the phone becomes unusable when the settings are in overview. This only happens when using stock and stock-based rom (Fulmics 8). Is there a solution?
Help
Stunlyyy5 said:
Hello, when using (D855) stock rom and stock based rom (Fulmics 8), the phone freezes extremely after the account and apps are installed, I can't take any action, The system is not responding, the home screen is not responding errors, also the phone is unavailable when I put a screen lock it becomes, the password cannot be entered (I don't think it's hardware related as it works very well when using Lineage OS) Used when Nova Launcher is installed (no screen lock), but when you open the notification panel, vibrate the phone, the phone becomes unusable when the settings are in overview. This only happens when using stock and stock-based rom (Fulmics 8). Is there a solution?
Click to expand...
Click to collapse
Why you posting questions in development.
Sorry
Long story short, obtained said device from somewhere and decided to experiment on it, and to survey the modding scene a bit while at it. Yeesh. What happened after that, in summary:
Found XDA. Then found after_silence's roms. Downloaded them.
In the process, I learned how to setup adb and how to make Windows recognize this outdated device's drivers. Now I can do these with my eyes closed.
Flashed TWRP 2.3.2.3. Installed as's first mod with gapps package. But something was wrong, google apps showed only stupid ad-like results after every search. Wiped it and continued searching for other mods. Stumbled upon this. Downloaded the latest one. Flashed it. When I tried to install the gapps package there, twrp said not enough storage to install gapps package. I learned how to use gapps-config file. To no avail. Experimented with each one, including the aokp ones. They were stable, but main menu was like 5 fps. And most of the time, google play stopped. Clock stopped. Trebuchet stopped. Even if nothing stopped, something stopped, sooner or later.
At last, I installed these: cm11 20140419 and gapps lp 20141109. Google continued to show stupid results. Uninstalled google play updates, restarted, it updated itself. Now, all seems stable enough, only with the never before seen, ridiculously stupid glitch of all:
The device restarts if it goes to sleep. Yeah, the screen dims, dims... and restart. Pressing power button once directly reboots the device. There's no sleep - either the screen stays on until the battery drains, or restarts.
At this point I can gladly get on my knees to beg someone for a solution, or for someone to please tell me, "here, these are the latest and HASSLE-FREE android 5.x rom and suitable gapps package".
Please.
VerpinZal said:
At last, I installed these: cm11 20140419 and gapps lp 20141109. Google continued to show stupid results. Uninstalled google play updates, restarted, it updated itself. Now, all seems stable enough, only with the never before seen, ridiculously stupid glitch of all:
The device restarts if it goes to sleep. Yeah, the screen dims, dims... and restart. Pressing power button once directly reboots the device. There's no sleep - either the screen stays on until the battery drains, or restarts.
Click to expand...
Click to collapse
Hi @VerpinZal,
I installed that CM11 version as well, but without gapps (using F-Droid instead).
Cannot reproduce the restart instead of sleep. Screen dims, turns off ... and turns on again w/o any restart.
Cheers!
Edit:
After factory reset @ cwm recovery I was able to flash CM12.1 w/o any issues as well.
Instead of gapps I installed f-droid and aurora store.
A Logitech diNovo Mini helps me to overcome the broken touch function. It connects automatically to the Mediapad via BT after booting up.