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
Related
Installed cmod7 stable (7.2) and the gapps file (found in another link - the one on nookdevs doesn't work). On first boot, it is stuck at a screen that just has a bar that says "Setup Wizard". The bar doesn't appear to be tapable. Search forum, no threads found on this.
Thanks in advance!
Dave
rebooted, still problems
dweaton said:
Installed cmod7 stable (7.2) and the gapps file (found in another link - the one on nookdevs doesn't work). On first boot, it is stuck at a screen that just has a bar that says "Setup Wizard". The bar doesn't appear to be tapable. Search forum, no threads found on this.
Thanks in advance!
Dave
Click to expand...
Click to collapse
I powered off and then on so it would reboot - it went through the setup screens. I get aborts of android.process.media so it won't let me go through the google play icon. When I try to click on Nookreader for android while on barnes and noble web site, it aborts again. I had the latest daily on here 2 days ago and was getting the same abort, but only twice when android first started. Tapping on google play then said "server error" and would NEVER work. Tried through the web - said I needed to use google play app - hence a big loop of nothing working. That's when I went to the "stable" version of 7.20 encore. It doesn't appear to want to do anything right.
Any advice on getting this all to work would be greatly appreciated. Using clockwork with the nook 1.4.3 firmware is getting old just to get back to a device that works, albeit not with full android.
dweaton said:
I powered off and then on so it would reboot - it went through the setup screens. I get aborts of android.process.media so it won't let me go through the google play icon. When I try to click on Nookreader for android while on barnes and noble web site, it aborts again. I had the latest daily on here 2 days ago and was getting the same abort, but only twice when android first started. Tapping on google play then said "server error" and would NEVER work. Tried through the web - said I needed to use google play app - hence a big loop of nothing working. That's when I went to the "stable" version of 7.20 encore. It doesn't appear to want to do anything right.
Any advice on getting this all to work would be greatly appreciated. Using clockwork with the nook 1.4.3 firmware is getting old just to get back to a device that works, albeit not with full android.
Click to expand...
Click to collapse
Perform it in two steps... first flash CM7 alone... reboot it... set up wifi... let it settle... THEN flash gapps and set up google stuff.
still stuck - different place
DizzyDen said:
Perform it in two steps... first flash CM7 alone... reboot it... set up wifi... let it settle... THEN flash gapps and set up google stuff.
Click to expand...
Click to collapse
Thanks so much for the help! I really want this to work!
I installed just CM7 and booted up - got one message about the media thing again but only one. I then went to set up wifi and now I'm stuck at that screen - then n button doesn't pop up anything to let me go back to something - like home.
I don't know if it makes any difference - I did the format data/system reset option then the cm7 flash, but it is still remembering my wireless settings somewhere as it automatically connects and it's a wpa2 network. Is there another step for erasing/formatting something that I missed?
Sorry to sound so stupid - but I'm completely a noob (LOVE the video on the registration page!).
Thanks so much again!
Dave:
nope - still not working
Well, installed cm7 and set up wifi, checked it was working by going to the web. Let it sit a few minutes, then reboot with the microSD and installed the gapps. Rebooted, went through google setup, then tried the google play via the icon on the home screen - same thing. It repeats the android.media.application abort message 2 times and then aborts the google play before I even get anywhere.
So......I'm wondering about my google apps zip file -> it said it was google apps for android 2.x.x, whereas I thought the cm7 I installed was android 3. Does this make a diffference?
Thanks again!
Dave :fingers-crossed:
Click here for the correct Gapps file:
http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
still failing
I downloaded the cmod 7.0 file and the gapps (thanks Hoser88!!), created the microSD, booted, did the format data/system reset and installed cmod 7.0. Rebooted, got the same 2 error messages about "android.media.application" aborting, then checked wireless and it was running.
Rebooted with the microSD and installed gapps, removed microSD and rebooted, got the same 2 error messages. Tapped on "Market", it showed a screen with something circling in the middle VERY briefly, then that closed out and the same 2 error messages came up again.
I'm starting to get worried, as I *think* I'm doing what I'm supposed to yet it doesn't work for me. Any and all suggestions are greatly appreciated!
Just to see what happens, I'm going to try the latest nightly cmod7 and see what that does.
Thanks!
Dave
same problems........
I made the microSD with the latest nightly of cmod 7 and the gapps pointed to above. I flashed cmod 7 first, booted, checked wireless, etc.. Still get the same 2 aborts about android.process.media on startup. I then booted again with the microSD and installed the gapps, removed microSD and rebooted. Got the same 2 aborts on startup. Tapped "Market", you see another screen the says "loading" very briefly, then that screen goes away and the android.process.media abort shows and I have to tap force close (this happens twice). I have no idea what this media process is, but is there a way to disable it? I get the feeling it is contributing to my problems.
I'm really lost here. I want this SO bad. I want to have full Android, and have both the Nook and Kindle reader apps so I can keep all my books on 1 device.
Thanks in advance!
dave
Tried more, still fails
I tried a recent suggestion on the cyanogen nook color forum: format data/factory reset and format /system, then install. I did this using the latest nightly and gapps - still got the same abort twice. Found another note in the cyanogen forum saying to go to the rom app and run set permissions and then reboot. I did that - STILL get the aborts. Can't get to google play (shows as "Market") get the quick "Loading" screen followed by immediate close of that and 2 more aborts for adroid.process.media.
I know it remembered my wireless, etc. again. Is there something else I need to format so it completely forgets everything so I'm starting from a clean slate? What can be causing the adroid.process.media abort and how do I get rid of it? Sometimes I think it thinks it is running on a phone, and obviously it's not - do I need to something additional for that as well?
I'm feeling quite confused right now. I've done everything from here and from what I read in the cyanogen nook color forum, but I still can't get this to work. What's the use of running cmod 7 if I can't access the google app store? Please help!
Thank you,
Dave
It works!!
Don't know WHAT I did - I just completely re-downloaded everything - the clockwork image (16gb), the cmod 7.0, and the gapps. Before installing, I went in with the existing install that wasn't working as it should and turned off several apps and cleared their cache when available. I then booted the new microSD - format data/system reset, format /system, installed cmod 7 zip and gapps zip. Removed microSD and rebooted. No more message about android.process.media aborting! It also asked me to set up my Google stuff again, so that was a step in the right direction. I then tried "Market", and IT WORKED!! It still aborts occasionally but I just go right back in and keep going. I did run into something I don't understand - the Nook for Android app page puts a message at the top saying it's not compatible with my device!! Huh? Do I need to may install cmod7.2 stable since this part is working now?
Thanks for the help!! If anyone could help me through the rest of this (get Nook for Android app, getting Kindle for Android app) then I should be good to go from there. I can always download other apps I might want, but I just want to get those 2 working first.
Thanks again!
Dave
It works and I have Kindle and Nook apps!
I updated to 7.20 stable (least wise I hope I did it right - I just flashed from zip but didn't format anything first). After that update I was able to get the B&N Nook reader and the Kindle reader apps! Everything seems to be working fine now - no aborts, nothing!
So.....a BIG THANK YOU to everyone who helped me out!
Thanks SO much!!
Dave :good:
mark as solved?
Some of the other forums I'm on have a set of thread tools - one of which lets you mark the thread as solved. Is there a tool like that on this forum (haven't found it yet if there is) ?
dweaton said:
Some of the other forums I'm on have a set of thread tools - one of which lets you mark the thread as solved. Is there a tool like that on this forum (haven't found it yet if there is) ?
Click to expand...
Click to collapse
Just edit your first post and rename it to [SOLVED] installed cmod7, stuck at "Setup Wizard"
There is a way to get Marshmallow on the HTC ONE Sprint M7, it's called VanirAOSP ROM. This is a great in most ways, and it's now my daily driver, but be very careful, I almost bricked my phone a few times in setting things up. Here are some tips from what I learned.
Installation instructions (learned from this video, other sources, and hard work):
1) Unlock bootloader.
2) Install custom recovery like TRWP. If you have an old version of TWRP, upgrade it using TRWP Manager or Flashify.
3) Download latest nightly ROM from http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/m7spr/.
4) Download gapps. Biker57 suggests gapps from http://www.emccann.net/dho/5-Gapps/ as it's supposed to cause fewer force closes. I believe 60arm-DHO-GAPPs.zip is the correct file name.
5) Download SuperSU. Biker57 likes SuperSU v2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125.
6) Copy all 3 downloads (in .zip format) to the phone (internal storage, like the TWRP folder)
7) Enter bootloader (volume down and power button), then select bootloader.
8) Backup the current ROM, just in case things go bad like they did for me.
9) From TWRP, enter advanced wipe and select system, data, cache, and dalvik cache. Do not select internal storage as you will lose your current backup and other zips if you do (there is an exception to this, as I did it, but I nearly bricked my phone). Now slide to wipe.
10) Go to install, and first select the ROM's zip. Then choose add more zips and select the gapps zip you downloaded. Next select SuperSU. Now slide to install.
11) Be patient during install.
12) Wipe dalvik cache.
13) Reboot to system (aka phone).
14) Enable Developer Options (if you want), by going to Settings->About and hitting Build Number many times until it's enabled.
Known issues and workarounds:
-Camera app force closes after taking a picture - the picture saves, so just reload Camera app. I've also had good luck using Z Camera then viewing the preview before hitting back to reenter the camera app.
-Stock dialer FCs randomly - Install another dialer app, like True Phone.
-Facebook and Facebook Messenger force closes - use mobile website, which actually isn't too bad, or try the instructions listed here.
-Flashlight turns off after 3 seconds - use the cameras flash instead.
Known issues with no good workarounds:
-FM Radio doesn't work.
-Bluetooth audio doesn't work for phone calls most of the time.
-Switching the battery mode causes the brightness to change randomly - don't ever switch away from balanced mode
Other stuff
-You can find more about the updates made to Vanir ROM here.
-It's risky to play around with the radio, but if you want to try it they are listed here.
-Intersted in supporting Varin, you can donate here.
Please let me know if I missed anything. And feel free to copy freely if it helps others.
***disclaimer - follow at your own risk. I'm not responsible for what might happen to your phone. This is only a cheat sheet, and it's for reference purposes only.***
First off, good tutorial. :good:
Vanir is a great ROM but this Sprint ROM still has a lot of bugs in it. I've used the first Vanir Marshmallow ROM to the most recent and a plethora of bugs have been squashed. But this ROM is still not DD ready, the camera , torch, gapps, browser and settings are broken. I am not saying this ROM is bad, just that its not fully ready yet. Depending on the dev, this rom should be DD ready in 2-3 weeks, they've been releasing more often now. Thank the developer if you know him but if you're the developer, thank you.
We should try to get the dev to see if they can put up a Vanir thread with change logs and the whole shebang.
I'm glad this thread was started and the OP was done well. I've been using this ROM for a while and thought I'd pass along my thoughts and what works for me.
This rom has become my daily driver after learning how to fix a couple of issues. After the latest update of 2/18 the biggest issues of not having a cellular/data connection has been corrected. The only issues that remain for me at least are the camera and Facebook issues. Although the camera does force close it does so for me at least after the picture is taken and saved so it's all good for me. The Facebook issues are corrected by deleting a file in both the Facebook and Messenger file.
The following method works for me without boot loops or any other issues and hopefully will work for you too. I flash these all at the same time loaded in the order listed and don't forget to make a backup before you start just in case.
1 - Flash the 2/18 nightly just like you would any rom http://www.emccann.net/nuclearmistak...ghtlies/m7spr/
2 - flash the gapps found here http://www.emccann.net/dho/5-Gapps/ and select the 60arm file near the bottom.
3 - flash Super SU 2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125 There are new versions, but the 2.64 has continued to work for me.
4 - Reboot
As I said earlier this works for me and I've used this method with their roms successfully a number of times. Good Luck !!
Thank the developer if you know him but if you're the developer, thank you.
Click to expand...
Click to collapse
I'm not the developer, and I don't know the developer. But I would thank him or her if I could. I'm just interested in running Marshmallow on the M7. I will update the original post as I learn more so I can hopefully help others.
anotherfakeusername said:
I'm not the developer, and I don't know the developer. But I would thank him or her if I could. I'm just interested in running Marshmallow on the M7. I will update the original post as I learn more so I can hopefully help others.
Click to expand...
Click to collapse
If you need help with thread stuff I can help, we should start a new thread completely and give it more of a ROM thread look with known bugs, work a rounds and honest opinions on it.
biker57 said:
3 - flash Super SU 2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125
Click to expand...
Click to collapse
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
anotherfakeusername said:
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
Click to expand...
Click to collapse
I'm not the developer either... Just a happy ROM user
There have been some issues with certain SU not working correctly with 6.0. You can try that but I would advise you to try a proven SU version.
is Snapchat also broken
Sent from my HTC One using Tapatalk
SuperSU 2.65 through TWRP 3.0.0-0
anotherfakeusername said:
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
Click to expand...
Click to collapse
I didn't install it from the Play Store, I just flashed this version (2.65) through TWRP 3.0.0-0 and it's working as expected :good:
Hello,
Flashing SuperSU through recovery is a better way, atleast for Marshmallow ROMs now. I'm using latest beta version (SuperSU v2.67) without any issues. It can be found in official SuperSU thread here.
As of camera issues, you can use 3rd party camera apps like Camera FV-5, ProShot or etc. Of course they cost few bucks but worth it. Issue doesn't solve totally in this ROM but app doesn't force close, instead freezes for few sec and then works again.
This ROM is my DD and faced no major issues so far. What I'm mostly missing is fast charge feature in kernel otherwise normally it takes plenty of hours to fully charge.
Kindly note; you have to flash gapps provided by the ROM developer. Other gapps like open gapps will endup with FC.
Thanks...
Best Regards
CRACING said:
Kindly note; you have to flash gapps provided by the ROM developer. Other gapps like open gapps will endup with FC.
Click to expand...
Click to collapse
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
anotherfakeusername said:
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
Click to expand...
Click to collapse
Their list of gapps is rather long......which one did you use and did you flash it with the rom
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
anotherfakeusername said:
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
Click to expand...
Click to collapse
Correct, they have to be flashed with the rom as I mentioned in post 3.
anotherfakeusername said:
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
Click to expand...
Click to collapse
As of error "Unknown issue with Google Play service", go to Settings -> Apps -> Google Play service -> click 3 dot button in the corner -> Uninstall updates. This should solve the problem.
As of OTG, I didn't tested it but usb connection from TWRP to pc for file transfor works fine.
Btw; You are right, ROM is indeed fast.
biker57 said:
Their list of gapps is rather long......which one did you use and did you flash it with the rom
Click to expand...
Click to collapse
Use 60arm-DHO-GAPPs.zip
anotherfakeusername said:
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
Click to expand...
Click to collapse
Even if you install supersu from playstore, it ask to reboots to recovery to install supersu. But before you accept to reboot, you'll have to enable root access to apps in developer options. Otherwise supersu cannot reboot or go into recovery.
Anyhow, instead of going through all these, I simply flash supersu zip from recovery.
CRACING said:
As of error "Unknown issue with Google Play service", go to Settings -> Apps -> Google Play service -> click 3 dot button in the corner -> Uninstall updates. This should solve the problem.
Click to expand...
Click to collapse
Android won't let me uninstall the Google Play service update. I get blocked when trying. It claims the app is an active device administrator, but it's not listed when I click manage device administrator.
anotherfakeusername said:
Android won't let me uninstall the Google Play service update. I get blocked when trying. It claims the app is an active device administrator, but it's not listed when I click manage device administrator.
Click to expand...
Click to collapse
Deselect Android Device Manager. Later when you uninstall the update, reselect Android Device Manager.
Deselect Android Device Manager. Later when you uninstall the update, reselect Android Device Manager.
Click to expand...
Click to collapse
That worked to fix my calendar syncing issues! Thanks!
Is not updating Google Play service going to cause other problems?
anotherfakeusername said:
That worked to fix my calendar syncing issues! Thanks!
Is not updating Google Play service going to cause other problems?
Click to expand...
Click to collapse
No such problems noticed here. I use Google calendar but Android calendar also works fine.
May be you should try rebooting or wait for some time and try resync.
CRACING said:
No such problems noticed here. I use Google calendar but Android calendar also works fine.
May be you should try rebooting or wait for some time and try resync.
Click to expand...
Click to collapse
The problem isn't using Google calendar, the problem is syncing Google calendar. I tried waiting, rebooting, re-adding my account, and everything else, but that didn't help.
Only downgrading Google Play services worked, and then Google calendar synced right away.
Thanks for the suggestions. Hopefully as they update the ROM it'll get resolved more fully.
Hi,
After a clean flash I restored my user apps through Titanium backup v8.0.0.
The Play Store doesn't detect my installed apps: https://framapic.org/2B4BI8G6r2xU/KpoiIpq9ondr.png
I installed a new app from the Play Store and I can see it: https://framapic.org/9Kl35z8Hznx2/DBxvbshb27PB.png
I guess it's a TiBu issue. Do you know how I can fix it?
I already tried to clear app data of Google Play Store and Google framework and remove my Gmail account.
With or without Gapps, it's the same issue.
Thanks.
Google Play Store v7.5.08.M-all [0] [PR] 146162341
Primokorn said:
Hi,
After a clean flash I restored my user apps through Titanium backup v8.0.0.
The Play Store doesn't detect my installed apps: https://framapic.org/2B4BI8G6r2xU/KpoiIpq9ondr.png
I installed a new app from the Play Store and I can see it: https://framapic.org/9Kl35z8Hznx2/DBxvbshb27PB.png
I guess it's a TiBu issue. Do you know how I can fix it?
I already tried to clear app data of Google Play Store and Google framework and remove my Gmail account.
With or without Gapps, it's the same issue.
Thanks.
Google Play Store v7.5.08.M-all [0] [PR] 146162341
Click to expand...
Click to collapse
I had that issue too but i found a way arround i restored all the apps using my google account once all the apps were installed i used tt to restore data+apps again and it worked.
Arrowblue said:
I had that issue too but i found a way arround i restored all the apps using my google account once all the apps were installed i used tt to restore data+apps again and it worked.
Click to expand...
Click to collapse
I don't back up my apps to Google servers. I'll try with the previous version of TiBu.
EDIT: after restorting the previous version of TiBu, I can update my apps again from Google Play.
There's definitively something wrong with v8.0.0.
EDIT2: it was a coincidence. Same issue after a new clean flash with TB 7.6.1. Don't know what I have to do to fix this damned problem!
EDIT3: Solved. I flashed a new ROM with Gapps package and done several tests. I'm back on unofficial RR ROM with microG and everything works... Do not ask me what is the final solution...
Primokorn said:
EDIT3: Solved. I flashed a new ROM with Gapps package and done several tests. I'm back on unofficial RR ROM with microG and everything works... Do not ask me what is the final solution...
Click to expand...
Click to collapse
Strange to see this, as I just clean flashed yesterday and didn't have any issues with TiBu/Market. I'm on 8.0 too. The only thing that I can't see for some reason is the Menu button that should normally be in the upper right next to the paper w/ check on it. I have hardware buttons instead of NavBar (right now), so it is probably linked to that. Trying to get a new feel for the new phone and coming from the Shamu, it's taking me some time.
Something to look at though: take a peep under the Hide tags in my signature and check out the Android_ID link. After a clean flash, the very first thing I do is install Terminal and run that command to restore my AID.
Glad you got it sorted though. I am finding that this device is riddled with all sorts of gremlins.
Woody said:
Strange to see this, as I just clean flashed yesterday and didn't have any issues with TiBu/Market. I'm on 8.0 too. The only thing that I can't see for some reason is the Menu button that should normally be in the upper right next to the paper w/ check on it. I have hardware buttons instead of NavBar (right now), so it is probably linked to that. Trying to get a new feel for the new phone and coming from the Shamu, it's taking me some time.
Something to look at though: take a peep under the Hide tags in my signature and check out the Android_ID link. After a clean flash, the very first thing I do is install Terminal and run that command to restore my AID.
Glad you got it sorted though. I am finding that this device is riddled with all sorts of gremlins.
Click to expand...
Click to collapse
Yes, very strange. During my various tests I flashed OpenGapps pico package and I saw a blank line while setting up my Gmail account. This blank line (probably a bug) is near a storage icon and it was disabled...
A few days ago I also flashed an OpenGapps package (several microG users - and maybe Gapps users - had FCs with the Play Store so I wanted to test with a Gapps package). I don't remember but maybe I disabled the option at this moment.
So during this clean flash I enabled it. idk if it's related to this mess but I think that's the only thing that can explain that my problem is solved (TiBu v8.0.0).
As for your Menu button, I don't see which button you are talking about. I also use the hw buttons and I have never needed a Menu button.
Coming from the Nexus 5 I spent a lot of time reading the 3/3T forums. Filesystems, encryption, OnePlus specifications (WiFi modules, custom ROM/nandroid backups based on OOS firmwares for instance),... and everything is not fully clear lol. I have all my data backed up on Nextcloud so I can test again and again. It seems to be pretty hard to really brick this device. We just have to be careful while flashing files (a confusion between 3 and 3T could be easy, not all threads are unified, or clicking on the wrong link).
I'm used to installing custom ROMs without restoring the Android ID for more than a year. I doubt this could be related to my problem but I'll give it a try so it happens again, thanks.
27 devices gained access to my account during the last month lol
Good luck with your 3T, an awesome device despite all those headaches
Primokorn said:
Yes, very strange. During my various tests I flashed OpenGapps pico package and I saw a blank line while setting up my Gmail account. This blank line (probably a bug) is near a storage icon and it was disabled...
A few days ago I also flashed an OpenGapps package (several microG users - and maybe Gapps users - had FCs with the Play Store so I wanted to test with a Gapps package). I don't remember but maybe I disabled the option at this moment.
So during this clean flash I enabled it. idk if it's related to this mess but I think that's the only thing that can explain that my problem is solved (TiBu v8.0.0).
As for your Menu button, I don't see which button you are talking about. I also use the hw buttons and I have never needed a Menu button.
Coming from the Nexus 5 I spent a lot of time reading the 3/3T forums. Filesystems, encryption, OnePlus specifications (WiFi modules, custom ROM/nandroid backups based on OOS firmwares for instance),... and everything is not fully clear lol. I have all my data backed up on Nextcloud so I can test again and again. It seems to be pretty hard to really brick this device. We just have to be careful while flashing files (a confusion between 3 and 3T could be easy, not all threads are unified, or clicking on the wrong link).
I'm used to installing custom ROMs without restoring the Android ID for more than a year. I doubt this could be related to my problem but I'll give it a try so it happens again, thanks.
27 devices gained access to my account during the last month lol
Good luck with your 3T, an awesome device despite all those headaches
Click to expand...
Click to collapse
indeed A hell of device i chose 3t over S7.Mean while i just flashed cleaned Marshmallow Stock based rom and didnt restored any apps from google account ,Just installed tt and restore apps+data it seems to work for me no broken links to playstore every thing works fine the only thing i noticed is tt backup seems to take more time to restore apps+data that is all.
Arrowblue said:
indeed A hell of device i chose 3t over S7.Mean while i just flashed cleaned Marshmallow Stock based rom and didnt restored any apps from google account ,Just installed tt and restore apps+data it seems to work for me no broken links to playstore every thing works fine the only thing i noticed is tt backup seems to take more time to restore apps+data that is all.
Click to expand...
Click to collapse
Yeah but I don't want to do that for each clean flash
At the end I have this issue each time I clean flash.
Restoring the Android ID doesn't help.
I just wait a moment, clear app data, reboot then the Play Store detects my apps... and I use an addon.d script for dirty flash.
I had the Nook HD+ running CyanogenMod for a few years.
I changed nothing, but lately it stopped working, complaining about Trebuchet, so I changed the launcher and it worked again, but giving occasional errors about an app not starting.
In the last few days it also started sporadically rebooting itself. Plunging it in did not seem to change anything. Lowering the max CPU speed from 1.5GHz to 1.1 did not help.
Now, it would not start at all – it would always get stuck at the circling CyanogenMod boot screen. It would still shut down using a long press.
I can start the rescue fine, with no unwanted reboots.
I do have a small amount of data there that I would like to be able to take out, if possible.
I don't care for any specific OS version/mod.
What do you think is the cause of this issue?
How can I fix this? Can I get the Data out?
Btw, in the years it was working, it did have an issue of sometimes restarting instead of shutting down.
I never knew if it was a fault with my device or the with latest CM.
Kov8 said:
I had the Nook HD+ running CyanogenMod for a few years.
I changed nothing, but lately it stopped working, complaining about Trebuchet, so I changed the launcher and it worked again, but giving occasional errors about an app not starting.
In the last few days it also started sporadically rebooting itself. Plunging it in did not seem to change anything. Lowering the max CPU speed from 1.5GHz to 1.1 did not help.
Now, it would not start at all – it would always get stuck at the circling CyanogenMod boot screen. It would still shut down using a long press.
I can start the rescue fine, with no unwanted reboots.
I do have a small amount of data there that I would like to be able to take out, if possible.
I don't care for any specific OS version/mod.
What do you think is the cause of this issue?
How can I fix this? Can I get the Data out?
Click to expand...
Click to collapse
Hi Kov8.
I was running CM 11.1 for ovation and experienced the same thing. My solution was to install a newer version.
To save your data, set up an SD card (be sure you have enough extra room for your data) with the TWRP 3.0.1-0 version here:
https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778
Load TWRP and look for the File Manager. I think it's under "Advanced." You can use that to copy or move your data to the SD card.
After that, consider upgrading to AOSP or LNOS. I can install AOSP without much difficulty, but LNOS doesn't go well. More on that in a later post.
If you need more detailed information, look at this post and download the pdf at the end of the first post:
https://forum.xda-developers.com/nook-hd/general/install-cyanogenmod-12-1-barnes-noble-t3211119
Kov8 said:
Btw, in the years it was working, it did have an issue of sometimes restarting instead of shutting down.
I never knew if it was a fault with my device or the with latest CM.
Click to expand...
Click to collapse
Yes. I've been reading that all the recent ROMs do that.
The solution is to do a standard shutdown followed by a hard shutdown (by holding the power button for 8 seconds).
I suspect that going straight for the hard shutdown caused some file system errors that made installing new ROMs very difficult.
I'm OK now, though.
Thanks for the detailed reply! I will try.
The link for TWRP does not work. Can I install the latest, 3.2.1.0?
Kov8 said:
The link for TWRP does not work. Can I install the latest, 3.2.1.0?
Click to expand...
Click to collapse
That's funny. I just downloaded two copies from that link.
For version 3.2.1-0, it sounds like you're looking at the version from the team win website. I haven't tested that one thoroughly, but I have tried out their version 3.1.1-0. It works pretty well. It gave me some minor error messages here and there, but if I just repeated what resulted in the error, it generally went through on the second attempt without an error.
The link worked for me later. I managed to change to TWRP 3.0.1-0 only after removing the version identifier from the zip file. I later easily upgraded TWRP to the newest.
I also upgraded to the latest AOSP from the same source, without deleting, as I couldn't get the data from one app. I then installed ARM 7.1 pico gapps. Some apps kept crashing, but removing and reinstalling seems to have fixed that.
The only problem, is that now shut down never works, and restart always takes me to recovery. So I just hard shutdown there.
Kov8 said:
The link worked for me later. I managed to change to TWRP 3.0.1-0 only after removing the version identifier from the zip file. I later easily upgraded TWRP to the newest.
I also upgraded to the latest AOSP from the same source, without deleting, as I couldn't get the data from one app. I then installed ARM 7.1 pico gapps. Some apps kept crashing, but removing and reinstalling seems to have fixed that.
The only problem, is that now shut down never works, and restart always takes me to recovery. So I just hard shutdown there.
Click to expand...
Click to collapse
Mind telling how you managed to update twrp from 3.0 1 to the latest? I successfully installed 3.0.1 to my nook hd+, then flashed 3.2.1 img to recovery, now the device stuck at boot.
I simply downloaded to img file from their website (for ovation, my device), placed on the micro-sd, and installed it from TWRP itself. As simple as that.
Are you sure that you got the correct version for your device?
I also always verify the integrity of roms after writing them to a card. I've seen bad cards.
I installed Android 4.4.4 on my touchpad today. Everything went well. But the main problem is that Youtube, Chrome and Opera keep crashing. In Youtube when i tap to load a video the app freezes and then crashes. Is there a fix, is the android old and shoud i upgrade to a newer version. The apps are downloaded from Google Play store
Which version of 4.4.4 did you install?
I have two here that I just pulled out to check for you, and then was faced with the forced update of YT.
(thanks google...)
Took and hour but finally got through that BS but they are both working.
The version installed that was shown on play store was from Oct, 2019
Version 14.43.55 is what it has been updated to on both.
LineageOS 11-20180827-UNOFFICAL.
and JCS's CM11 on the other from waaay back in '15 or '16.
_mr
middle_road said:
Which version of 4.4.4 did you install?
I have two here that I just pulled out to check for you, and then was faced with the forced update of YT.
(thanks google...)
Took and hour but finally got through that BS but they are both working.
The version installed that was shown on play store was from Oct, 2019
Version 14.43.55 is what it has been updated to on both.
LineageOS 11-20180827-UNOFFICAL.
and JCS's CM11 on the other from waaay back in '15 or '16.
_mr
Click to expand...
Click to collapse
The ROM that i downloaded was called lineage-11-20201201-NIGHTLY-MLQ-tenderloin
the GAPPS is gapps-base-arm-4.4.4-20170902-1-signed
and the TWRP is update-TWRP-jcs-dm-tenderloin-20140612b
And I think that there is maybe a video playbach issue, because even in the stock browser in desktop mode the video starts, but then crashes the browser.
Also in Chrome when i search for something it loads, but the page is blank and when i try to swipe Chrome crashes. Tryed Opera - same outcome
BlackLight965 said:
The ROM that i downloaded was called lineage-11-20201201-NIGHTLY-MLQ-tenderloin
the GAPPS is gapps-base-arm-4.4.4-20170902-1-signed
and the TWRP is update-TWRP-jcs-dm-tenderloin-20140612b
And I think that there is maybe a video playbach issue, because even in the stock browser in desktop mode the video starts, but then crashes the browser.
Also in Chrome when i search for something it loads, but the page is blank and when i try to swipe Chrome crashes. Tryed Opera - same outcome
Click to expand...
Click to collapse
Well that's odd. usually Milaq's ROMs are GTG.
All your versions of GApps and TWRP are what I'm running.
Something is whacked since you can't bring it up in Chrome or Opera.
Perhaps try JCS's? That's what I've got on my 'Main' go-to TP.
Just tried YT on Opera and it functioned.
middle_road said:
Well that's odd. usually Milaq's ROMs are GTG.
All your versions of GApps and TWRP are what I'm running.
Something is whacked since you can't bring it up in Chrome or Opera.
Perhaps try JCS's? That's what I've got on my 'Main' go-to TP.
Just tried YT on Opera and it functioned.
Click to expand...
Click to collapse
The only thing i didnt do is to wipe the tablet. And before the install it said it needed to fix something, and then it mounted the media device. Shoud i wipe the whole thing and do a clean install with the same files or use different ones ?
BlackLight965 said:
The only thing i didnt do is to wipe the tablet. And before the install it said it needed to fix something, and then it mounted the media device. Shoud i wipe the whole thing and do a clean install with the same files or use different ones ?
Click to expand...
Click to collapse
Most assuredly. I always 'nuke' mine whenever I put a ROM on.
Do you by chance have the ol' WebOS still on it?
middle_road said:
Most assuredly. I always 'nuke' mine whenever I put a ROM on.
Do you by chance have the ol' WebOS still on it?
Click to expand...
Click to collapse
Yes i have it . Also when i got it the guy that gave me the tablet sayed that he installed android, and then reverted it back to WebOS.
BlackLight965 said:
Yes i have it . Also when i got it the guy that gave me the tablet sayed that he installed android, and then reverted it back to WebOS.
Click to expand...
Click to collapse
ah, I'd Nuke (wipe) it all.
I got rid of WebOS on my (5) TPs years ago.
In this section in the stickies above there are several excellent posts by @RolandDeschain79
Follow those, wipe the tablet.