Hello, Hopefully some one is still checking this forum that can help me. I got a DNA with CM 11 on it, while I wait for the first Verizon snapdragon 820 with SD card, as my LG G2 started failing miserably (dead spots in screen and no loger connects to Wi-Fi or Bluetooth)
I wanted to clear it out and to go to a 5.x.x ROM. so I made my backups and went to the 5.1 google play edition ROM and fastboot-ed the latest firmware as instructed in the post. at first the capacitive navigation buttons seem to work, but in about half a day they become flaky and sometimes work and sometimes don't. whatever app I am in at the time seems to work fine, just can't exit without the nav keys unless I reboot or force another app to open from the lock screen. I have also tried a 5.0.1 and and now on a stock ODEX debloat 4.4.2 all with the exact same issue. I use TWRP and do a factory reset in TWRP before each flash. How is this issue following the flashing of each ROM? Any one have any ideas for me to try?
Thank you
Related
I posted this in fascinate forums and haven't been able to get any help, so I figured I would post here as well. I have been running cm7 and installing the nightlies as they come out. When I flashed nightly #9, I lost complete use of my soft keys. Imagine how annoying it is to have to reboot to change screens. I installed a catlog to see if I could figure out what was going on, but I know absolutely nothing about programming. So, this is what I think I figured out. In the bootup, there's no device for "mice", says something about device not found, and then there's another error in system bootup about the"face" error. So I think I have lost something in the system bootup that runs my soft keys.
Does anyone else have issues with their soft keys? Before I lost them totally, my back button would activate all by itself until everything and I mean everything was closed.
I haven't been able to go back to stock to see if that works because I haven't had any computer access since this happened. I will be home tomorrow, so I can see if that helps.
If anyone has any other insight, I'd be really glad to know.
Thanks,
Mona
any solution yet to this my 4 soft keys wont work i dont know wat to do
No resolution for soft key fail
monac66 said:
I posted this in fascinate forums and haven't been able to get any help, so I figured I would post here as well. I have been running cm7 and installing the nightlies as they come out. When I flashed nightly #9, I lost complete use of my soft keys. Imagine how annoying it is to have to reboot to change screens. I installed a catlog to see if I could figure out what was going on, but I know absolutely nothing about programming. So, this is what I think I figured out. In the bootup, there's no device for "mice", says something about device not found, and then there's another error in system bootup about the"face" error. So I think I have lost something in the system bootup that runs my soft keys.
Does anyone else have issues with their soft keys? Before I lost them totally, my back button would activate all by itself until everything and I mean everything was closed.
I haven't been able to go back to stock to see if that works because I haven't had any computer access since this happened. I will be home tomorrow, so I can see if that helps.
If anyone has any other insight, I'd be really glad to know.
Thanks,
Mona
Click to expand...
Click to collapse
I had the same issue when I flashed to Paranoid Android, a jellybean based ROM. Everything worked fine for me with Cyanogenmod 7.2, then I flashed to Android 4.1 and lost the use of the soft keys. I still haven't resolved the issue.
For the record
Charcaroth said:
I had the same issue when I flashed to Paranoid Android, a jellybean based ROM. Everything worked fine for me with Cyanogenmod 7.2, then I flashed to Android 4.1 and lost the use of the soft keys. I still haven't resolved the issue.
Click to expand...
Click to collapse
In case anyone else has this issue, I tried flashing a stock Froyo ROM, a stock Gingerbread ROM, CM 7.2 again, and even stock GB with the latest Verizon Wireless update for GB and the softkey functions never returned. I've managed to put Paranoid Android 2+ back on the Fascinate, a Jellybean ROM, so I can mimic the buttons with onscreen controls, but it eats up a lot of screen real estate. It's a workaround, not a solution by a long shot.
Hi, I'm having a curious problem with my S3 and I've been unable to solve it. I watched the "noob" video and tried searching these forums as well as a google search with various combinations of the wording for my problem. Nothing matching my issue turned up, I hope I didn't miss anything.
I recently bought a S3 second hand (yes, i know, i should have known better). It was rooted and running some kind of custom ROM when I first turned it on, but I was willing to deal with it until I double checked the procedure for getting it back to stock and starting again myself (nothing against the original rooting and flashing, just like to know exactly what I'm running).
When I purchased the phone I obviously checked that all of the main things worked - calling, texts, mobile data, wi-fi etc. I get home and connect to my home wi-fi and start checking things out and setting stuff up. The phone randomly rebooted. I carry on after the reboot and about 10 mins later, another restart.
To cut a long story short, there is something wrong with the wi-fi. If I turn off wi-fi in the settings menu and reboot, everything works great. No crashes, no reboots. If however I enable the wi-fi about 50% of the time it will crash while wi-fi is activating. The other 50% of the time, it will crash as it goes into the screen lock (either via timeout or pressing the button).
I've re-flashed to it's stock version of Android (using the 'Samsung GS3 Toolkit and Odin), same problem. Anyone got any ideas?
Thanks in advance
You can try updating the modem and RIL to the right version for your country, search in general forum. If it still reboots then try with another wifi source - I've seen some routers cause problems on client machines.
If you do a factory reset when you flash the modem, plus you have the latest stock ROM on board, then any remaining problems are probably hardware.
Test it fully after the factory reset, before you add any apps etc.
boomboomer said:
You can try updating the modem and RIL to the right version for your country, search in general forum. If it still reboots then try with another wifi source - I've seen some routers cause problems on client machines.
If you do a factory reset when you flash the modem, plus you have the latest stock ROM on board, then any remaining problems are probably hardware.
Test it fully after the factory reset, before you add any apps etc.
Click to expand...
Click to collapse
After much experimentation and flashing of various files to my phone I have further narrowed the problem. I've still not solved it, but getting closer I feel.
After a clean ROM flash it works like a charm regardless of how much i use the wifi etc. It's only after the first reboot that the trouble starts. It will begin randomly restarting. If I perform a factory reset from recovery mode, it works again, but starts resetting again after a reboot.
Any ideas?
I buy a refurbished HOX+ from china and i have been use it for 4 days now...
First day it came no longer in original state which the seller already give some apps and its like he limit it, iam not sure about this limitation but iam curious why there is only like 15 language which only spoken in South East Asia.but when i hard reset more language available
It start restarting and even hang that causing another restart, i conclude its an software problem so i try to update the android version using OTA, its succesfully download it but when restarting and installed it take so long and seems no progress so i restart it manually,and after restart several time it could go into the android system and i doing a hard reset but problem still occur
Day 2 i tried to install another rom which i tried 2(CM 10.1 unofficial for HOX+ and CM 10 for HOX and Carbon Fibre that also for HOX+),problem still occur like the first issue, and here's the weird thing: when the lcd screen turn off automaticly or i press to turn off my lcd and left for a few minutes sometimes second, when i tried to press to turn it on again its no longer responding which i can't conclude its shutdown itself or the lcd is not responding.
But in TWRP this issue with lcd never show up, which i can turn it on again with no problem
Secondly when i change to custom rom in CM 10 for HOX i cant open playstore, the program is executed but i cant go to that window
In CM 10 for HOX+ which i have to flash gapps i can open play store but cant download(the progress bar static) but i still can search same issue happen in carbon rom
sometime when copying a file from pc to phone cant too the pc said it cannot copy
I also tried changing the firmware but still same
I change my old sim with new one still same
i also check for md5sum
now i tried to update the hboot and back to stock rom, i hope it could revive my problem
android details:
HTC_044
twrp 2.6.0.000
H boot ver 1.36
some details that i miss i would update later..
This issue really taking my time and patience..
One more thing i would ask is it possible if its an hardware issue
I will appreciate your help for this weird issue
Greetings,
I have been tinkering with my GF's 850f with the hopes that she will forget about those damn expensive Iphones and embrace the Android way... but so far the Alpha has been acting up. I will explain the issue:
Sometimes, seemingly at random, the phone will get stuck and get really slow. I think I managed to isolate the issue because it seems to happen after using an app that uses the microphone (Duolingo, Whatsapp). After she uses the microphone, the phone will remain stuck. You can get out of the app and close it, but it won't open again and the phone gets slow. Everything goes back to normal after I reboot the phone, but it invariably happens at least once a day. It doesn't happen everytime she uses microphone.
Things I've tried:
Upgraded to official Lollipop using the France image (Clean flash)
Installed custom recovery (First 2.8.0 and then 2.8.6)
Flashed Ozcan ROM (Clean flash again)
It didn't happen on KitKat, it actually began after flashing the Lollipop upgrade, but I'm iffy about downgrading from Lollipop. Anyone knows a way to debug, single out or fix something like this?
Thanks in advance!
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.