I have been running CM 14.1 20161219 since that date, with few problems. Sometimes I enable an cm automobile system profile in the settings menu so I can easily get on the phone while driving or otherwise.
Yesterday I turned it on and forgot about it, and today I rebooted my phone while charging and I get a black screen with the <| back button on the bottom and my notifications and quick settings visible on the top. I can receive calls and toggle wifi and what not, but I cant reach the settings menu to switch back to the default profile (or the launcher for that matter). I have rebooted to recovery fine, but I dont want to reflash unless its necessary as it messes up my Authenticator settings on Steam, google, etc. Usually I turn those off before flashing new ROMs.
Hopefully there is a simple fix I can do from fastboot or recovery...
Thank you for any help.
- b
cm14 is dead; find a different rom...
wase4711 said:
cm14 is dead; find a different rom...
Click to expand...
Click to collapse
Yeah. I installed it before it was dead, and when I installed it it was working fine for a month or more ... until today. I was waiting for a couple revisions before I installed Lineage OS.
Regardless, when upgrading ROMS there are several steps I take beforehand that would benefit from fixing this bug first.
* backing up apps via TB
* Turning off steam multifactor in steam app
* Turning off google authenticator 2 factor temporarily
* backing up some of my data, just in case
* Trying to upgrade to Lineage OS using experimental dirty flash method
* Upgrading TWRP via the app before flashing my next ROM
* others
I ended up trying to flash LIneage OS in the 2 part methon of i.) flash experimental ROM, ii.) flash Lineago OS nightly. That didnt fix the problem with the Launcher and settings not working. And I was unable to do any of my pre-upgrade checklist.
I think there was something was messing with the Pixel Launcher, and I ended up whiping and reflashing the normal way. This was a real problem because I lost the ability to use my phone 3 hours before requiring Navigation to meet family across town. Not to mention having phone call access. I hope I don't randomly have this same problem with LIneage OS now since I was unable to solve... I will stop using that system profiles feature for the time being.
Related
So i'm at a point where my wi-fi wont turn on, background syncing is having problems, cpu is running slow, and i've already restored my phone once.
so far how i managed to **** it up:
-tried editing framework-res.apk causing brick, 4 hours later i manage to restore to stock, reroot, and restore apps/settings through titanium backup
-download one power guard, sees phone is slowing down and it not helping much so remove it
-having issues with background sync, emails don't come in, calendar doesn't automatically update, smartwatch not receiving notifications
-flash a kernel 77.12.22 using the kernel changer on forums
-wi-fi doesnt turn on
-flash back to original kernel with wi-fi still not working
i'm wondering if anyone could point me to what i can do to fix it rather than reflash the stock OS and having to load the backup again
UPDATE: flashed to 77.12.17 and wifi is working again
I still cant figure out how to make the background sync work again for me, it's very frustrating
Was handing off my phone to my son, moving on to an LG G2, I let him test it out under my account, he added his account and phone was a little sluggish since the extra account was taking up more RAM, so he hands it to me while I was in bed and needs help, I factory reset it thinking it would just wipe out my personal data and allow him to enter his, well it did, but now he lost Root and I am stuck on the 1st nightly with memory leak...
Any method available to reroot this phone when in 5.0 so I can continue upgrading with nightlies? Or am I in a world of hurt now?
Justatechie replied in another thread, THANKS!!
Thats not going to work, it only works with the stock atrix hd 4.1.1
Cm12 can be rooted by going into developer options on the phone,
under root access (its disabled by default)
Just tap on it and allow apps or app and adb and it should be all set.
Other people prefer to flash supersu by going into recovery, just download the latest and put it where you will find it when you use the recovery.
I completely forgot about that, I had enabled developer mode, but nothing else, thought the reboot into advanced options was default, which it was not and slightly had a panic attack.. Thanks for the save...
Running apps stay running after a flash...
First thing odd I noticed, after giving him my phone and his adding his apps, is that when you click square to see running apps and click the 3 bars to turn them all off, they do not turn off, you have to swipe each one off now.
When I had the phone that process would end all apps I had started, now they stay on unless you swipe them off.
Also, after flashing the update to latest nightly, all the apps that were running before I flashed it and entered recovery to perform the flash, were running again upon a reboot. I have never seen this on any build, don't know if it is one of his apps causing this or what??
And I cleaned cache, cleaned dalvik, flashed both zips, cm12 and gapps, then cleaned cache again as instructed in the 5.0 threads.
I tried to see if it would happen again so I opened 3 apps, then performed a reboot, after phone rebooted, clicked the square and those same 3 apps were active...
What may have caused this?
Factory reset may have some bug as the phone was performing normally before I used that method to clear out my user data.
And if I ever decide to part with the phone I would expect that feature to work or I would be forced to keep it...
sobitthen said:
First thing odd I noticed, after giving him my phone and his adding his apps, is that when you click square to see running apps and click the 3 bars to turn them all off, they do not turn off, you have to swipe each one off now.
When I had the phone that process would end all apps I had started, now they stay on unless you swipe them off.
Also, after flashing the update to latest nightly, all the apps that were running before I flashed it and entered recovery to perform the flash, were running again upon a reboot. I have never seen this on any build, don't know if it is one of his apps causing this or what??
And I cleaned cache, cleaned dalvik, flashed both zips, cm12 and gapps, then cleaned cache again as instructed in the 5.0 threads.
I tried to see if it would happen again so I opened 3 apps, then performed a reboot, after phone rebooted, clicked the square and those same 3 apps were active...
What may have caused this?
Factory reset may have some bug as the phone was performing normally before I used that method to clear out my user data.
And if I ever decide to part with the phone I would expect that feature to work or I would be forced to keep it...
Click to expand...
Click to collapse
Apps will continue to run if you reboot. This is not a bug but a feature from Lollipop
This is CyanogenMod 12.1 (Lollipop (5.1.1 – LMY49F)) for ASUS’s Transformer Pad (TF701T – Macallan).
This thread is for device specific shakeout and bug fixing.
This is not a production build.
Please always supply a system log (logcat) and a kernel log (kmsg) when reporting an issue.
Please read through the entire blog post:
http://droidbasement.com/db-blog/?p=3765
Please take note of the 'Known Issues'.
Download: http://get.cm/?device=tf701t
Note:
SELinux is in Enforcing mode.
First one to answer!
At least! CM 12.1 for our beloved TF701!
And yesterday we got TWRP recovery after more than a year thinking that it was impossible.
New life for the best Asus Android Transformer. Thank you, pershoot.
Thanks so much for this. I'm very excited to get my 701 up to date.
I'm working on a clean installation (12.1-20150601)
Got to the screen where I select the apps to reinstall from a previous installation. After selecting the apps to reinstall the CANCEL/DONE buttons were difficult to select. It seemed to "take" after tapping around the "Done" button a bunch of times.
I have the new TWRP installed (in case that makes any difference).
david31262 said:
Thanks so much for this. I'm very excited to get my 701 up to date.
I'm working on a clean installation (12.1-20150601)
Got to the screen where I select the apps to reinstall from a previous installation. After selecting the apps to reinstall the CANCEL/DONE buttons were difficult to select. It seemed to "take" after tapping around the "Done" button a bunch of times.
I have the new TWRP installed (in case that makes any difference).
Click to expand...
Click to collapse
I noticed the same behaviour on one of my older BlissPop builds. It went away on my newest build. Something to keep track of now that I'm not the only person that was experiencing it.
david31262 said:
Thanks so much for this. I'm very excited to get my 701 up to date.
I'm working on a clean installation (12.1-20150601)
Got to the screen where I select the apps to reinstall from a previous installation. After selecting the apps to reinstall the CANCEL/DONE buttons were difficult to select. It seemed to "take" after tapping around the "Done" button a bunch of times.
I have the new TWRP installed (in case that makes any difference).
Click to expand...
Click to collapse
this is only shown in Play? Try dynamic dpi gapps build from banks (check droidbasement link) and see if that sorts it out.
pershoot said:
this is only shown in Play? Try dynamic dpi gapps build from banks (check droidbasement link) and see if that sorts it out.
Click to expand...
Click to collapse
I believe that is the file I'm running. I loaded:
BaNkS-dynamic-gapps-L-5-27-15.zip
Except for that one minor problem during initial startup & configuration (which only occurred on that one screen). You're load has been working great.
THANKS !!!!!
Been running for two days as a dirty flash update from your cm12.0. Simply works except for occasional slowdowns opening apps and with the apps drawer. This is also true on cm12.1 for my d2att do I don't know if it is a trebuchet issue or not. Either way excellent work as ever.
Matthew
Please snap a log the next time it happens. Thanks.
Calendar App trouble connecting to google account
When I tried to open the calendar, it asked me to log in to connect to my calendar.
When I put in the same google account I'd set-up the device with it said that the account already exists on the device.
Checking the account, the Calendar was not visible as a service that was syncing.
The calendar was blank, and trying to add a new event reported that I need to add an account first.
I went to the play store and downloaded the google calendar app. That opened fine and connected to my existing calendar. Returning to the Cyanogen calendar then connected and showed my events.
I'm getting a force close on the new Google Photos app. The app seems to be working fine on my other devices running CM12.1. (pershoot I'll send you a log shortly)
Also, every time I open the Play Store it seems like I have 15-20 apps that need to be updated. It feels like my updates are not sticking through a reboot, and I have to re-update some apps after a boot. Is anyone else seeing similar issues?
Try updating gapps (linked on DB) and update your 12.1 build (06/18).
Hmm, this is odd. The latest banks Gapps (6/17) got rid of the Play Store.
edit: Tried reinstalling the PA Gapps for 5.1, still don't have my Play Store back.
no issues with Play here and no issues with Google Photos as well.
on 6/18 12.1 (DB) and 6/17 Banks.
ariadnejro said:
First one to answer!
At least! CM 12.1 for our beloved TF701!
And yesterday we got TWRP recovery after more than a year thinking that it was impossible.
New life for the best Asus Android Transformer. Thank you, pershoot.
Click to expand...
Click to collapse
Could you send me the link to the TWRP Recovery page please?
mvd96 said:
Could you send me the link to the TWRP Recovery page please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3121989
Bad Dirty Flash of 6/20 & GApps 6-21-15
Hmmm,
Just dirty-flashed your 6/20 and BaNkS-dynamic-gapps-L-6-21-15. Am looking at a mostly blank home screen. The notification pull downs are there, and the 3 navigation buttons on the bottom, and nothing else. And, now a message "Couldn't add widget". I've tried to redownload and flash, but no change.
Suppose next step is either an earlier gapps, or reflash with full reset.
david31262 said:
Hmmm,
Just dirty-flashed your 6/20 and BaNkS-dynamic-gapps-L-6-21-15. Am looking at a mostly blank home screen. The notification pull downs are there, and the 3 navigation buttons on the bottom, and nothing else. And, now a message "Couldn't add widget". I've tried to redownload and flash, but no change.
Suppose next step is either an earlier gapps, or reflash with full reset.
Click to expand...
Click to collapse
no issues with 6/21 12.1 (DB) and 6/21 banks flashing over 6/18 12.1 (DB) and 6/17 Banks. Using CM Recovery to flash.
Got it back with a Full Wipe
pershoot said:
no issues with 6/21 12.1 (DB) and 6/21 banks flashing over 6/18 12.1 (DB) and 6/17 Banks. Using CM Recovery to flash.
Click to expand...
Click to collapse
Thanks for checking
I tried flashing over with these versions, but it didn't come back.
Ended up doing a full wipe and loaded these versions (still running TWRP).
Not sure what happened, but it's working fine now (maybe a TWRP problem).
Thanks.
Better than CM12
I would like to just give an update to how smooth lollipop 511 is running! I'm voice typing this and I did a full wipe from CM 12 then install CM 12.1 and selection of the options to restore from Google all of my apps and after about a half an hour all is just funky great! I have CWM 6. 0. 5. 1 installed. It seems a bit zippier but miracast or screen mirroring still does not function. Great job Pershoot!!!!!
Oh, one thing that it did not do was the stock browser did not sync my bookmarks.
K94U said:
I would like to just give an update to how smooth lollipop 511 is running! I'm voice typing this and I did a full wipe from CM 12 then install CM 12.1 and selection of the options to restore from Google all of my apps and after about a half an hour all is just funky great! I have CWM 6. 0. 5. 1 installed. It seems a bit zippier but miracast or screen mirroring still does not function. Great job Pershoot!!!!!
Oh, one thing that it did not do was the stock browser did not sync my bookmarks.
Click to expand...
Click to collapse
Try this for screen casting:
http://forum.xda-developers.com/nexus-7/general/guide-how-to-enable-chromecast-t2941155
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Bassem AbdullMonem said:
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Click to expand...
Click to collapse
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
bogarty said:
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Bassem AbdullMonem said:
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Click to expand...
Click to collapse
Truthfully, your best bet while you have your device up and running is to backup all your apps and data with something like Titanium Backup or even sync them with the Samsung Cloud. The cloud reinstalls everything and sets your device configuration back to the way it was. Then, if you have a custom rom installed, wipe it in TWRP and reinstall it. If you're running stock, then don't wipe. Just go to the Sammobile website, download the latest firmware for your specific device and reflash it to the device with Odin. This generally fixes all system problems with a device, while preserving your app data.
Alternately, you can also try searching XDA for kernels that are made for your device that have a higher performance and try installing one of those to see if anything improves. As far as the screen going off early too, you can always check in "Settings/Display/Screen Timeout" to see what it's set for and change it to the max screen on time. It really sounds like you may have broke something system wise with Xposed or an Xposed module though, which is very easy to do, so I would really recommend starting over fresh. If you're on stock especially, as you really have nothing(data wise) to lose.
Sent from my SM-N920T using Tapatalk
I don't get notifications working. Tried just about everything. Different stock roms, unlocked or locked bootloader, with or without twrp, with or without SuperSU/Magisk root...
In SafeCenter, and in later 3.5 Roms 'Security' app I disable all auto accelerate, anti spam, antivirus, auto cleanup. I white listed all apps/associated apps in autostart.
Enabled/disabled USB debugging.
Disabled all apps in Battery optimization
Sync on in account settings
In notifications settings everything enabled.
And still I don't get no freaking notifications! Only if open the app the notification appears..
Anything else I could try, and please don't tell me to use custom ROM! I want to get this fixed, it should be possible right?!
Edit;
Currently running 3.5.344ST/unlocked/twrp/supersu root
did u use a backup to restore apps or did u fresh install from store?
move app for /system/priv-app
Was it solved by moving into system/priv-app?
Did you get to the bottom of this ?
It makes a difference if you upgrade from very old ROM versions, or newer versions.
E.g. I started with ZUI 1.9xx (QFIL) and then OTA all the way up to the newest version (3.4xx)
Everything basically worked, but I had battery issues and some notification issues which I couldn't fix.
Then I tried to encrypt my device and it critically failed, so I had to switch to a new ROM anyway.
Then I took the newest possible full ROM for QFIL, I think it was ZUI 3.1xx and then OTA the short way up to the newest version.
Now Everything works, also encryption and with good battery life and notifications. But I feel the ROM is a little less snappy then before, maybe because of encryption.
Besides it still has 2 turn-downs:
- Some apps like Amazon Prime Video complain about an "uncompatible device ID" thus won't start
- Language is english and I can't manage to change the language permanently (not even with morelocale and ADB commands)
So our ZUK2 Pro's always have some funny behaviour... But I really feel the device is at its best now after ~1 Year in my pocket.
€dit: All with locked bootloader and without root