Related
[size=+3]Honeycomb SDK Port - The Return [/size]
1. Introduction
So, for quite some time, we have had the excellent work done by deeper-blue, in porting the preview SDK, which whet our appetites for more Honeycomb to come. But despite Google allowing companies to ship Honeycomb devices, we have not had a source drop. As such, i felt like taking on the challenge of making the full SDK work on the nook; and now, here we are. This is build off the SDK 11 (rather than 10), and should be compatible with all real Honeycomb apps. Lets proceed.
2. Thanks & Credits
Before i go ANY further, i want to say thanks to whose people's work enabled and inspired me.
deeper-blue - It was your original modifications to the preview SDK that allowed me to get a BIG start on converting the full SDK. Honestly, i don't know how you figured out to do most of what you did, but it works!
dc13 - Your Asus Transformer system dump provided all the nice extra apps that are in use on this rom, in addition to the update framework. Thank you for your hard work!. http://forum.sdx-developers.com/eee-pad-development/ti-x-transformer-pad-v1/
rookie1 -Your dual boot Honeycomb script provided a great basis for a non dual booting script. http://forum.xda-developers.com/showthread.php?t=959461
I admit, i put together what i could with what i could find; if anyone is unhappy with what was used, please let me know and we can rectify the issue.
3. Installation
Not a whole lot to this one. Installation requires at least CWM 3.0.1.0. I am using internal CWM, so I will only certify it with that. I guess some people use CWM SD cards, but i am not sure how well it works with them.
Load the included .zip file on the SD card, and flash.
THIS WILL WIPE YOUR SYSTEM
DO NOT install this without having a good backup of Froyo or CM7.
DO NOT FORMAT BOOT
DO NOT INSTALL THIS WITHOUT HAVING A GOOD NANDROID BACKUP
Install take a few minutes, but once you are up, you will be greeted with the setup screen. Be sure to have a good Wifi around, it makes it easier to set everything up. Also, be sure to give the system a minute or two to settle when it first boots. Once you are all setup, you will be greeted with the full Android experience. Which leads me to my last bit of info.
4. Issues
Not working
- DSP (i think i jumped the gun on this one)
- From time to time, the screen may seemingly partially lock up. If this happens, please try to get an ADB logcat and post it here ("adb shell logcat > aFileName.txt"). A reboot will fix this issue.
- SD Card - RIght now, this is the big one. Not sure what about the framework change killed hte SD card, but i dont seem to see mine any more. If anyone has any ideas,lemme know
Working
SU (thank you racks11479)
SetCPU (and all other root needing things)
Audio (thank you deeper-blue)
3D
WiFi
Market (thank you PatF, et al)
Calendar (thanks Rockwig)
Gmail
- To kill the flashing red box (thank you mazook98): http://forum.xda-developers.com/showpost.php?p=13504316&postcount=109
(and more)
5. Community
So, what to do from here? Well, i will keep doing what i can, but i am by no means an expert. I invite anyone and everyone whom could possibly help make this better. If you think you can get Root or Market working - dont even ask; grab the code and mod away. If you have any advice, please share it. Android is so amazing because of the community.. lets keep it that way!
6. Links & Releases
5/9/11[/b]
This link represents a new phase of the Honeycomb build. I have adapted the framework from the posted eee Pad V3 build (linked in section 2). I feel this is a huge step up in UI, and a good push towards a daily driver. The UI is still a bit laggy, but it isn't too bad. Again, it wont be perfectly fixable until we get the source, but for now, its coming along.
Honeycomb Hybrid - RC1
http://www.multiupload.com/71K84XF6BF
Updated ramdisk made by Racks11479, that will allow SD mounting
See: http://forum.xda-developers.com/showpost.php?p=13698333&postcount=483
http://www.multiupload.com/3D9WSPUAUZ
**** ARCHIVED: DO NOT USE *****
Honeycomb SDK - RC3
RC3 Brings in the Calandar fix (thanks Rockwig), and a new build.prop (thanks xboxexpert), as well as some cleanup.
http://www.mediafire.com/?z6a2x97hlr5ve8p
Honeycomb SDK - RC2 (thanks to declain for creating an updated rollup)
RC2 brings in the fixed SU, Market, and Audio, all in one neat package!
https://rapidshare.com/files/460775452/update-HC-rc2.zip
Honeycomb SDK - RC1
http://www.mediafire.com/?czghefkha5zetab
www.unvisible.org/files/update-HC-rc1.zip - Thanks luciferii!
Su to push to allow Superuser (thanks for the info racks11479):
http://forum.xda-developers.com/showthread.php?t=953110
**Note, if pushing to xbin does not work, push the file to bin, and also set the perms there. That got it working for me**
6a: Change Log
RC3 - 5/6/11
- Fixed Calendar
- Updated build.prop
- DPI set to 140
- Installer no longer wipes out data; all future revisions will leave user partitions alone
- Cleaned up some unneeded programs
RC2 - 5/5/11
- Fixed SU
- Fixed Sound
- Fixed Market
RC1 - Release
7. Questions and Answers
With the stock Market still being funky, what options do i have?
The system can still side load apps, so any APKs you can grab can be installed with adb. Additionally, because of this,you can install other 3rd party Markets such as Slide and Amazon, which will let you install more apps.
Can i use the HC overclocked kernel?
At this time no. I have tried using the last released HS OC kernel, and something about it causes the system to hang at the boot animation. I want to look into it further though, and see if i can discover the source of the issue.
As of RC1, the kernel shipping in this package, is the same one that is found in the "HC-v4-emmc-2nd-edition" released for the preview SDK.
What is different about this release, compared to the other SDK port
The previous port was based off of the preview SDK, which Google labeled as SDK 10. The actual release of Honeycomb however, was bumped to SDK 11. This port uses that code, which means that it should be compatible with all the new new Honeycomb apps (Google body, etc). Certain things, like the Gmail for tablets, do work, and show what Honeycomb is all about.
How much more can be done on this release?
From here, the big fixes would be:
- Getting the stock Honeycomb Market to work
- Getting audio working
- Getting newer OC kernels workin
- Smothing out the UI experience as much as possible.
How can i help?
All the source that i had available is in the .zip package. Because there is no freely available source, all the work involves modifying the released binaries and framework .jars. There is additional tweaking that can be done to the ramdisk and kernel. If you feel adventurous, all of these are in the update package, and can be tweaked at your leisure. If you think you have something, don't be shy - zip it up and let us test it!
Oh, make sure you are signed in your Google account. Reboot, check for market.
Sent from my Samsung-SPH-D700 using XDA App
marcusant said:
Oh, make sure you are signed in your Google account. Reboot, check for market.
Sent from my Samsung-SPH-D700 using XDA App
Click to expand...
Click to collapse
If not, adb push zeam and try flashing cm7 gapps.
Sent from my Samsung-SPH-D700 using XDA App
marcusant said:
If not, adb push zeam and try flashing cm7 gapps.
Sent from my Samsung-SPH-D700 using XDA App
Click to expand...
Click to collapse
Gave it a try - no go. Lots of force closes going on...
I am soooo looking forward to this. No matter how great the other roms are. I just love the Honeycomb UI. Downloading now and will play around with it and hopefully will be able to contribute in someway.
Thanks,
Racks
Thanks for working on this! Hopefully the issues can be fixed soon enough.
I will poke around with it also. I ran EMMC v2 for a long time and the HC UI was just so smooth.
Thanks Madcat for taking this on.
I know this was meant for EMMC. But I just prepped and installed this to my SDcard rom and boy do I loves me some honeycomb. I assume you are aware of the red border issue? Or might it be because i'm running it off an SDcard. Don't mean to throw things off with the SD install.
Thanks,
Racks
racks11479 said:
I know this was meant for EMMC. But I just prepped and installed this to my SDcard rom and boy do I loves me some honeycomb. I assume you are aware of the red border issue? Or might it be because i'm running it off an SDcard. Don't mean to throw things off with the SD install.
Thanks,
Racks
Click to expand...
Click to collapse
Aye - i am aware of the boarder, and didn't remember if there was a way to turn it off.. It was way too long since i messed with HC...
thanks dm for getting hc back into life, im sure there will be many people come out of the woodwork to help with this, it seems like youve got it mostly there. once it gets market i will be all over this
insaneturbo13 said:
thanks dm for getting hc back into life, im sure there will be many people come out of the woodwork to help with this, it seems like youve got it mostly there. once it gets market i will be all over this
Click to expand...
Click to collapse
Hey insaneturbo13 . Did realize you were a NC owner too .
@Divine_MadcatI'm hoping to come into some free time soon, and should be able to test and contribute where i can.
Thanks,
-h8
h8rift said:
Hey insaneturbo13 . Did realize you were a NC owner too .
@Divine_MadcatI'm hoping to come into some free time soon, and should be able to test and contribute where i can.
Thanks,
-h8
Click to expand...
Click to collapse
hey yea, im now a regular here, good to see a familiar face haha
owned one of these puppies for about a month now
OK, just flashed CM7 latest Gapps. Market shows up. Signed in. Can browse. Search. But unable to install any apps.
Error I'm receiving is Google Services Framework (process com.google.process.gapps) has stopped unexpectedly.
I can install backed up apps by pushing via ADB and through a File Manager
Awesome ROM! Many people will be happy to see HC development move forward.
I was able to flash this using the SD card I use to flash CM7. I had a few keyboard FCs that was stopped when I specially picked US english. Glad to see wireless working, and the SD card slot works. Nook encoded videos play poorly, but I can't tell if its the DSP or the lack of audio. Interesting to see the differences between the final SDK and the one we had previously.
Thanks again!!!
well im currently giving it a try. Like you said, market doesn't show up but i saw that in my notification bar it said that i had updates. I clicked on it and it took me to "my apps" and installed all my paid for apps just fine . I'm not able to get to the rest of the market though.
Thank you
Many thanks Divine , Have been waiting for this for a long time. love the widgets.
I am interested in this, carry on
The amazon app market works fine.
Just a random Q, but has anyone tried these?
http://nookdevs.com/Honeycomb_Google_Apps_and_Market
http://forum.xda-developers.com/showthread.php?t=941445
I will start this off with "...Accounts (process com.motorola.setup) has stopped unexpectedly. Please try again."
The above is my most common error lately. And, I've tried again, multiple different ways. Only once have I got a half-decent build - meaning I got through setup... and, I have no idea what I did differently that time.
I am on GB 2.3.6 Moto Edison (A2) - locked bootloader - and have been attempting an odexed rom (psuedo-rom, if you will, because of the bootloader thing..), trying to retain most of the moto-blur (stock launcher for sure) - but have added some other features.
As I said, I managed to do it once, but it had a different connection issue (with the moto server - suspect it had something to do with cheesecake and switching servers at one point (but that's another topic)) so, I ditched that version. Also, I have no problem logging into Google - it's the next setup that usually gets me...
I know it's kind of a vague post but I am wondering if anyone has encountered not being able to get past setup? And, any ideas on how to correct it? I have scoured the web and discussed it with folks in my local community to no avail..
Also, I figure this thread could also be used for others with common or reoccurring errors after a test run - so, feel free to post your issues!
Fixed everything.
It was a mismatched signature on my Settings.apk, I believe... causing it to not be recognized by my system. Do not mess with the AndroidManifest.xml unless you want to re-sign all other apks.
Also figured out my moto server connection error - it was cheesecake - must have been using the /etc/motorola folder from a backup or systemdump after changing from the default moto server with cheesecake - it changes a defaults.xml in there...
...But ICS is leaking all over the place - so gotta be checking Cheesecake!
Sent from my mind using XDA
So as a learning experience, I have been trying to build a ROM that hasn't been compiled for my device. I have already compiled CM10 as a trial run just to test an official build in my environment and make sure everything was set up correctly. Everything works as per the CM10 nightlies for my device. I was able to merge the CM device/kernel files into the other source and get it to compile after quite a few hours (days?) of figuring out and tracing bugs. I was then left with a build that was about 95% functional; device boots up, sound works, no real major problems that I could find. The only thing was that when trying to download certain apps from the play store, they would tell me my device wasn't compatible with the app. In other ROMs which my device is officially supported though, I have no problems with the play store.
I also noticed that my baseband was being reported as "unknown" in settings. Thinking that may have something to do with the play store, I began working on that; tracing down what in CM reports the baseband that just wasn't jiving with the ROM that I was building. After a while, I found the problem and fixed it. The new build now reported the baseband correctly, and magically the play store no longer was giving me errors. Since I now had a version where the major bugs were worked out, I wanted to change the output name of my build and change my kernel source to a different kernel. After changing that to my liking, I flashed that version onto my phone and noticed the play store was again telling me that certain apps weren't compatible with my device. Thinking maybe the kernel swap had busted my progress, I reverted the kernel changes and re-built. Still had the problem. I reverted my output name change (being the only difference now between the build that worked and now) and it was still incompatible. After flashing the new build; which should have been identical to the working build in every way, the play store was still not working correctly. I decided to flash the build that I knew was working... even the original in which all market apps could be downloaded was telling me apps weren't compatible and was acting just like every other build.
I have performed "make clean" after each build, each time I flashed my device I performed a factory reset and formatted dalvik and system. What am I missing? What does the play store use to determine compatibility? I've been told it goes by the ro.build.fingerprint in build.prop; I've tried the values used in CM10 official (which mine was in the first place, using the CM device files), CM9 official, ICS official, GB official... none of them make the play store change it's compatibility message. Also of interest, when telling me my phone is incompatible when surfing from my computer browser, it's listed the exact same as when I'm in a version of android which allows me to download.
What am I overlooking?
lordcheeto03 said:
So as a learning experience, I have been trying to build a ROM that hasn't been compiled for my device. I have already compiled CM10 as a trial run just to test an official build in my environment and make sure everything was set up correctly. Everything works as per the CM10 nightlies for my device. I was able to merge the CM device/kernel files into the other source and get it to compile after quite a few hours (days?) of figuring out and tracing bugs. I was then left with a build that was about 95% functional; device boots up, sound works, no real major problems that I could find. The only thing was that when trying to download certain apps from the play store, they would tell me my device wasn't compatible with the app. In other ROMs which my device is officially supported though, I have no problems with the play store.
I also noticed that my baseband was being reported as "unknown" in settings. Thinking that may have something to do with the play store, I began working on that; tracing down what in CM reports the baseband that just wasn't jiving with the ROM that I was building. After a while, I found the problem and fixed it. The new build now reported the baseband correctly, and magically the play store no longer was giving me errors. Since I now had a version where the major bugs were worked out, I wanted to change the output name of my build and change my kernel source to a different kernel. After changing that to my liking, I flashed that version onto my phone and noticed the play store was again telling me that certain apps weren't compatible with my device. Thinking maybe the kernel swap had busted my progress, I reverted the kernel changes and re-built. Still had the problem. I reverted my output name change (being the only difference now between the build that worked and now) and it was still incompatible. After flashing the new build; which should have been identical to the working build in every way, the play store was still not working correctly. I decided to flash the build that I knew was working... even the original in which all market apps could be downloaded was telling me apps weren't compatible and was acting just like every other build.
I have performed "make clean" after each build, each time I flashed my device I performed a factory reset and formatted dalvik and system. What am I missing? What does the play store use to determine compatibility? I've been told it goes by the ro.build.fingerprint in build.prop; I've tried the values used in CM10 official (which mine was in the first place, using the CM device files), CM9 official, ICS official, GB official... none of them make the play store change it's compatibility message. Also of interest, when telling me my phone is incompatible when surfing from my computer browser, it's listed the exact same as when I'm in a version of android which allows me to download.
What am I overlooking?
Click to expand...
Click to collapse
Hi guy.
I dev. a rom actually not supported by cyano.
And i had fixed the pb by add of permissions files in /system/etc/permissions and complete build.prop with parameters from another device who work well with market.
Fyi, i have take sgsi9000 to build my own build.prop file
I hope that will help you.
Bizcuite
Sent from my GT-N7100 using xda app-developers app
bizcuite said:
Hi guy.
I dev. a rom actually not supported by cyano.
And i had fixed the pb by add of permissions files in /system/etc/permissions and complete build.prop with parameters from another device who work well with market.
Fyi, i have take sgsi9000 to build my own build.prop file
I hope that will help you.
Bizcuite
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thank you for your input. I don't know how much of a change there will be using the /etc/permissions files from CM, though I will try it. As for the build.prop, I use the exact same build.prop in CM and the play store works 100%.
EDIT:
I looked at /etc/permissions and the only difference between CM and the one I'm working on right now is that CM has a file called com.cyanogenmod.android.xml. I don't believe that file is needed because I'm not building CM.
Hi guys.
Just started to build my own AOSP build from source. Im using Ubuntu 12.04 LTS and everything works great with repo sync and building the rom.
I flash the build and everything works great to. Time and date is correct. Google sync works. Google now works.
But when i reboot my phone the time resets to 1970 for about 15 seconds till it goes to current date and time. But i get like 10 notifications from all of my apps saying google sync error, Time error and WhatsApp says time error to. Goggle sync is stuck on sync. google now dont work and so on.
I have tried to build it over and over again without luck. I wiped everything before flashing the zip. I even did a fresh clean install of ubuntu and did everything from the begining but it still resets to 1970.
I tried to build CM11 rom also and everything works great. No time issues. So why is pure AOSP doing this?
Someone said something about qualcomm time daemon not storing time in data/system/time directory .
I have been trying to fix this for days without any luck.
bariz143 said:
Hi guys.
Just started to build my own AOSP build from source. Im using Ubuntu 12.04 LTS and everything works great with repo sync and building the rom.
I flash the build and everything works great to. Time and date is correct. Google sync works. Google now works.
But when i reboot my phone the time resets to 1970 for about 15 seconds till it goes to current date and time. But i get like 10 notifications from all of my apps saying google sync error, Time error and WhatsApp says time error to. Goggle sync is stuck on sync. google now dont work and so on.
I have tried to build it over and over again without luck. I wiped everything before flashing the zip. I even did a fresh clean install of ubuntu and did everything from the begining but it still resets to 1970.
I tried to build CM11 rom also and everything works great. No time issues. So why is pure AOSP doing this?
Someone said something about qualcomm time daemon not storing time in data/system/time directory .
I have been trying to fix this for days without any luck.
Click to expand...
Click to collapse
I'm not a dev (though I know how to compile, just not any coding) so don't have a fix for you, but found this as a potential work around until someone can help you sort the rest: http://software.techassistbox.com/datetime-1970-bug-aosp-workaround_136694.html
The time issue is solved thank you
Time to include Superuser to the build but i have no idea how to do that.
Someone want to help?
bariz143 said:
The time issue is solved thank you
Time to include Superuser to the build but i have no idea how to do that.
Someone want to help?
Click to expand...
Click to collapse
Out of curiosity, how did you resolve?
I was under the impression that you just have to add the SuperSU apk to /system/app and the SU binary to /system/bin, but not entirely sure on that part. If you are trying to bake it into the actual Settings app, not sure on that.
The Google binaries had some missing files so I pulled the binaries from stock factory image and it worked
I want the superuser baked in as the other roms out there
Still haven't found a guide or help from someone.
What happens to XDA soul where everyone helped each other back in the days. I have pm a lot of developers and no one answered back
Found some guides on how to add stuff AFTER it's been built, but not during the build itself.
I know a lot of the devs get bombarded with inane questions from random people so often ignore PMs. Not saying your question is, but most of them don't like to answer questions there that should be in the thread for their stuff so often just overlook the inbox.
Come to think of it, you aren't really adding SuperSU TO Settings, just enabling a shortcut in the Settings app that leads to the app.
http://developer.android.com/reference/android/provider/Settings.html
I'm wondering if this:
public static final String ACTION_APPLICATION_SETTINGS
Activity Action: Show settings to allow configuration of application-related settings.
In some cases, a matching Activity may not exist, so ensure you safeguard against this.
Input: Nothing.
Output: Nothing.
Constant Value: "android.settings.APPLICATION_SETTINGS"
Part isn't something to do with creating that link...? Just making an educated guess.
Info on adding stuff after it's built - might be helpful to see where things are at?
http://forum.xda-developers.com/showthread.php?t=2184207
http://forum.xda-developers.com/showthread.php?t=2341389
Also, check out this dev/thread: http://forum.xda-developers.com/nexus-4/themes-apps/mod-custom-options-settings-app-ops-t2593536 Maybe you can ask him or decompile his Settings.apk and see where he added the necessary coding in.
es0tericcha0s said:
Found some guides on how to add stuff AFTER it's been built, but not during the build itself.
I know a lot of the devs get bombarded with inane questions from random people so often ignore PMs. Not saying your question is, but most of them don't like to answer questions there that should be in the thread for their stuff so often just overlook the inbox.
Come to think of it, you aren't really adding SuperSU TO Settings, just enabling a shortcut in the Settings app that leads to the app.
http://developer.android.com/reference/android/provider/Settings.html
I'm wondering if this:
public static final String ACTION_APPLICATION_SETTINGS
Activity Action: Show settings to allow configuration of application-related settings.
In some cases, a matching Activity may not exist, so ensure you safeguard against this.
Input: Nothing.
Output: Nothing.
Constant Value: "android.settings.APPLICATION_SETTINGS"
Part isn't something to do with creating that link...? Just making an educated guess.
Info on adding stuff after it's built - might be helpful to see where things are at?
http://forum.xda-developers.com/showthread.php?t=2184207
http://forum.xda-developers.com/showthread.php?t=2341389
Also, check out this dev/thread: http://forum.xda-developers.com/nexus-4/themes-apps/mod-custom-options-settings-app-ops-t2593536 Maybe you can ask him or decompile his Settings.apk and see where he added the necessary coding in.
Click to expand...
Click to collapse
Holy sh!"¤%t. Thats alot to do. I have to study this for a month to maybe succed
Compiling the rom feels alot easier when reading this haha
bariz143 said:
Holy sh!"¤%t. Thats alot to do. I have to study this for a month to maybe succed
Compiling the rom feels alot easier when reading this haha
Click to expand...
Click to collapse
The more you learn, the more you realize you dunno.
es0tericcha0s said:
The more you learn, the more you realize you dunno.
Click to expand...
Click to collapse
Haha good answer. Man I don't know where to start. I will look in to it but not today.
deleted
Just noticed that my aosp build cant locate my location. And thats a huge setback. Really need help with this. Without gps there is no way i can use this this rom as a DD.
Downloaded gps status app and started it and it doesnt find even 1 satelite so something is wrong there.
See if you can grab the gps.conf file from a working rom for your phone. Or try this - which might be able to make the right one for you: https://play.google.com/store/apps/details?id=org.fastergps
es0tericcha0s said:
See if you can grab the gps.conf file from a working rom for your phone. Or try this - which might be able to make the right one for you: https://play.google.com/store/apps/details?id=org.fastergps
Click to expand...
Click to collapse
Tried that app. Nothing happend. Going to grab a gps.conf file from some rom.
EDIT: Just tried that without sucess. No gps lock at all. Think it has something to do with my binaries. Cant figur it out
EDIT2: FIXED:but GPS connection is very bad. Have to go outside to get a lock. Could get connection inside before
At least you are making progress. So the gps.confg file helped a bit? Now that it is working somewhat, maybe one of the GPS status apps can help make it stronger?
es0tericcha0s said:
At least you are making progress. So the gps.confg file helped a bit? Now that it is working somewhat, maybe one of the GPS status apps can help make it stronger?
Click to expand...
Click to collapse
Okey its not the gps.conf file. Just flashed a custom rom (No names) and it locates my location in a heartbeat inside my apartment. My build is much slower and don''t work inside.
Dropped development ATM. Need to fix gps. Dont know where to start. I tried with the binaries again without luck
bariz143 said:
Dropped development ATM. Need to fix gps. Dont know where to start. I tried with the binaries again without luck
Click to expand...
Click to collapse
Bariz I have the same time issues which bin files did you replace/add was time_daemon one of them?
kidkoala_uk said:
Bariz I have the same time issues which bin files did you replace/add was time_daemon one of them?
Click to expand...
Click to collapse
I just extracted all the binaries from stock rom and put them in my vendor if I remember it right. It was a long time ago since I developed. To much for me man
bariz143 said:
I just extracted all the binaries from stock rom and put them in my vendor if I remember it right. It was a long time ago since I developed. To much for me man
Click to expand...
Click to collapse
Cheers bro.
Edit: Issue now resolved the Google proprietary blobs are missing a number of files. Got the necessary files and added to my build.
AOSP build resetting time to 1971 after reboot in Airplane Mode
bariz143 said:
The Google binaries had some missing files so I pulled the binaries from stock factory image and it worked
I want the superuser baked in as the other roms out there
Still haven't found a guide or help from someone.
What happens to XDA soul where everyone helped each other back in the days. I have pm a lot of developers and no one answered back
Click to expand...
Click to collapse
We are having the same issue with a Nexus 5 (Hammerhead) where the date/time are not sticking after reboot when in Airplane Mode (no data connection, wifi off). Can you provide some more detail about how solved the problem? Which binaries and how did you pull them over? Thanks.
Updated and revised, 11-29-20
In this post I am presenting a way to slightly extend the practical range of the 8 gb Nook Tablet by using microG for Google Services Framework spoofing rather than the resource-hogging GApps. Although I have tested these ROMs thoroughly on the BNTV250a, they would all likely run just fine with GApps on the 16 gb model (I currently run AOSP 7.0 with microG on my 16 gb tablet), while only CM 11 runs acceptably on the 8 gb model with GApps. Let's get that simple setup out of the way first.
I selected the unofficial CM 11 ROM with the final security patches by Chris Hoffmann [https://www.mediafire.com/?gq1y21uz11lr1c0]. It is serviceable for me. The main drawback is the old WebView (which cannot be updated) resulting in the inability of browsers to display many sites properly, including the current default skin for XDA. Despite this, I've come to feel that it's perhaps the best option, with or without GApps. Installing this ROM is easy. Flash with the recovery listed in post #2, reboot, then flash a pico GApps package from Open GApps. To run the ROM without GApps, read on.
I made a quick tour of CM 12.1, CM 13, AOSP 6.0 and AOSP 7.0, and Lineage 14.1. In the following post I'll lay out some pros, cons and hints based on my experiences. I flashed each ROM several times, trying different things, building the system from scratch each time rather than restoring apps from backup. That gave me a chance to work with each OS and see how it would perform not only during setup, but also during a shakedown/tweaking phase. What I can say about all of these ROMs is that GApps effectively kills each and every one on the BNTV250a.
Life without GApps
I, of course, tried side-loading apps without GApps. Easy, right? I thought so until I came to a few that whined about requiring Google Play Services to run. Even mundane things like the NPR News app, my local newspaper and MX Player are "GSF dependent" (Google Services Framework). Then I tried another app that would not install at all. Turns out it did a license verification check (it's free!) and saw no Google anything, so forget it. This was sort of news to me I suppose because even my lowly NST had GApps installed once upon a time, so I never encountered this issue before. You can hunt around for apps elsewhere but if you pick up an app that happens to be featured in the PlayStore, you may be out of luck no matter where you got it from. Or maybe not.
There is a project called microG by XDA member @MaR-V-iN. It consists of a lightweight set of apps (two at minimum, a third if you want location services) which provide the needed authentication to Google servers and/or inquisitive apps. There is a catch: the ROM must support "signature spoofing".
These ROMs do not have that option. You can Google "signature spoofing" to read the pros and cons. This is just information. Caveat emptor, etc. There is an Xposed module called FakeGapps which enables signature spoofing. I tried this on a few ROMs and found it worked fine. At the time I started this there was no official Xposed update for Android 7.0 and as that was one of my targets, I started looking for something else [note: Xposed has since been updated to include Android 7.0 and beyond]. That led me to Tingle by XDA member @ale5000. This is a Python/ADB based method of automatically patching framework.jar to enable signature spoofing. This seemed to me a more direct and elegant approach. Although I was intimidated by it at first, I eventually just dove in. The only thing I didn't already have was Python and that was easy enough to install. The process is basically automatic once it gets going. Unfortunately it does not work for ROMs that are odexed or deodexed. The AOSP 7.0 ROM turned out to fall in that category. Xposed must be used there.
OK, what can all this do for you? It can get you a spoof of Google Services Framework without GApps. Period. There are a few simple additions to allow for location services. It used to be that you could also enable Calendar and Contacts syncing. No more. As for PlayStore access, this is possible running microG with CM 11, but not beyond. It's just too resource intensive. For ROMs beyond CM 11 I found the Aurora Store (F-Droid) to work OK, although not always in the same way. On some ROMs you can use the anonymous Aurora Store login, on others you need to supply a Google account (email). Trial and error.
The General Process
If you have never "flashed" anything before that you can talk about at work, then you need some basic instructions for creating an SD card that will allow you to try out these procedures. The excellent instructions by @digixmax here will get you started with the SD card. You need to follow steps 1-2 to prepare the card, although the version of TWRP you use will depend on the ROM you want to try out (see second post for links). Also, the ROM itself will vary (see second post for links) and you will not want GApps (unless you are just installing CM 11 with GApps). The remainder of the steps (3-10, skipping 9) also describe the general process of flashing a ROM (or other "flashable" files like Xposed, etc.) using the SD card.
1. Flash the ROM using an appropriate recovery (I have listed the ones I used in the following post)
2. First boot, enable root, USB debugging and ADB
EITHER
3. Connect tablet to PC via USB and access via ADB ("adb devices"--some of these ROMs require that you approve PC access to the tablet via ADB, so check the tablet screen to approve that option if needed)
4. Open a command window on the PC and navigate to your Python installation directory. Because I was not sure what I was doing I just dumped the entire contents of Tingle into the Python directory. That simplified path issues for me. Type "python main.py" and select option 1. Wait for the "all done", hit CTRL-c and kill ADB server. Disconnect tablet from USB and reboot.
OR
3. Flash appropriate Xposed for the OS; reboot
4. Install Xposed installer app and FakeGApps.apk; use Xposed installer app to enable FakeGapps (signature spoofing); reboot
5. Install root file manager of choice if desired (the CM stock file managers are totally capable of the following operations if given root access; the stock file explorers of the AOSP and Lineage ROMs may allow the same, although I have had mixed results. You can always install a root file manager via ADB before continuing if all else fails) A copy of ES File Explorer is attached below.
for CM 11 without GApps but with the PlayStore:
6. Move Phonesky.apk--i.e. the PlayStore-- (old, lightweight version from a KitKat ROM: http://www.mediafire.com/file/1c2f0n3k3cwsln7/Phonesky.apk/file) into /system/priv-app; set apk file permissions to rwx-r-r.
7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
8. Reboot
9. Check microG Settings to be sure spoofing is enabled and other permissions are given; set to enable Google device registration; add an account. This process can be slow. Be patient. If you end up at a black screen, reboot and try again or see if the account is already established.
10. Open the PlayStore. Do some searching. You want to give it time to auto-update (this process may be completely silent). Exit. Check Settings>Apps>Downloaded to see if PlayStore has shown up there. If it has, then it may be updated. You can check yourself to see if the version number is higher. If there is no update, access the PlayStore again and check again. Once you have an update, you're good to go.
OR, for ROMs beyond CM 11:
6. Use root file manager to create the folder "Phonesky" in /system/priv-app. Set folder permissions to rwx-rx-rx. Use root file manager to move "FakeStore" apk into /system/priv-app/Phonesky and set apk file permissions to rw-r-r.
7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
8. Reboot
9. Check microG Settings to be sure spoofing is enabled and other permissions are given.
It's a lot, but if I could do it many times over you could do it once
In the end you'll have a tablet spoofing Google Services Framework so most apps will run without whining, but without the crushing weight of the PlayStore or the full GApps.
Contacts and Location
Life without GApps doesn't mean you have to give up these services. Just keep in mind that running background services can compromise a system that is already on the edge.
I tested the instructions that follow on a BNTV250a, using the stock Contacts and Calendar apps.
1. Contacts
There are some places in "on-line land" that describe a method for enabling contacts sync. I have not found the various methods to work any longer. It is possible to sync Contacts using DavDroid. There is only one version that will run on CM 11 and the same app will run on the other ROMs as well (attached below). However, you are adding more overhead to a device that is already pushing the limits. In the end I opted to export my contacts in vcard format and read them in as a local file. The more socially active may find this unacceptable, but it works for me.
2. Location
To enable location you will need to install an app which coordinates WiFi triangulation (something usually handled by GApps). There are two possibilities. You can get a Unified NLP apk from the microG download page. After installing the app you can check your microG settings to see if everything is OK. Then you can check Settings>Location and set it up the way you want.
If you want to use Maps you will also need to flash a maps.zip file from microG. This contains a couple of library files for Maps. As far as the Maps app itself, I have never had good performance from any version of Google Maps on my devices--until now. That's because I went fishing for an older, less bloated version that would run on the BNTV250a. It works beautifully on all my devices from KitKat to Nougat and allows pre-cache of map areas which don't expire. I've attached a copy of the apk file below.
Email
The stock Email client works great (at least for GMail accounts) and looks a lot like GMail (no surprise there). If you have your heart set on GMail, version 4.5.2--from GApps for Jellybean--seems to run just fine with a footprint of about 11 MB. I've attached a copy below.
The ROMs
Updated and revised 2-5-23
Generally I disabled any stock stuff I could that I would not use. Anything past CM 11 has a maddening issue I call "peek-a-boo keyboard", most noticeable when using the browsers. The keyboard drops out while you are typing or simply refuses to open without a struggle. You can solve this problem in CM 12 and minimize it in CM 13 by installing Simple Keyboard.
CM 11 is beginning to show expired certificates and SSL issues. You can try replacing or adding new certificates, but it's not easy and you're left with warning artifacts in the status bar. Ditto with CM 12 and CM 13, but they are not nearly as bad--for now. The stock browsers, fortunately, allow you to "ignore" security warnings which makes browsing more pleasant. You may not feel that's a great idea, but the reality is that browsing is the Achilles Heel for all these ROMS, and it's worse the higher you go. The stock browsers may give the best overall performance, whatever their shortcomings.
Because of the SSL issues, I don't recommend CM 11 any longer unless you are not going to do much in the way of internet stuff.
Note: I have noticed that both my Nook Tablets (8 and 16 GB) run better if they've been on for a bit. If yours is cranky when it gets up in the morning, pouring coffee on it won't help, but a little siesta after boot may be just the thing
CM 11 (but with issues as described above)
https://www.mediafire.com/?gq1y21uz11lr1c0
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
This is arguably the best choice for the BNTV250a if you want something other than the stock B&N ROM. It runs smoothly enough that you could even keep the PlayStore app on it and it would still behave reasonably. It's even better without it. The only drawback with this ROM is that Android Webview cannot be updated. This means that some websites will not display properly or may simply crash, regardless of what browser you choose to use. I found the antique stock browser to be surprisingly good, but Via also works well. Also, the SSL is in need of updating, so you will run into issues with some websites and apps like OverDrive.
The lesson that this ROM taught me is that these tablets are for casual use. You can't just load them up with apps and expect them to run well. Think about what you really would like to use the tablet for. Consider older versions of apps that will probably still have more features than you will ever want but are less taxing to the system. You can see from the attached screenshot how I eventually pared my choices down. I should probably pare it down even more. Most of the apps are older versions and I've kept the total count low, certainly less than on my 16 GB tablet and other devices. You don't want to exceed about half of the internal storage capacity.
CM 12.1 (potential WiFi issue as described below)
http://www.mediafire.com/file/7zxc2e...K6-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
Edit 9-30-22: I recently booted this up to find that it would no longer connect to my fairly new ATT router. Puzzled, I took the tablet to my local library and had no difficulty connecting there (open network, though). Next I started restoring backups of each of the other ROMs in this list and each one had no trouble with WiFi at home. I installed a fresh copy of the CM 12.1 ROM. It also refused to connect to the router. I scrounged around the web and found two more versions of CM 12.1. Neither would connect to my router. So...I'm not sure if there is some additional security ATT has built into their WPA2 authentication or what, but I mention this just to alert you that this might be a problem. I was even able to connect to a mobile hotspot generated by my Windows 10 machine (password needed). Why this new(?) problem for the 12.1 ROM only, I have no idea.
Before you start installing apps the behavior is sprightly, even on the BNTV250a. As the internal space decreases and RAM use increases, it becomes a little less so. Even so, when running well I think it comes close to CM 11 (with GApps), albeit with more lag.
The stock browser seems like the best bet (I tried many), though it can be slow.
For me this ROM has two major issues. When it is unhappy, it will simply shut down the tablet, literally turning it off. This used to sometimes happen when I ran it on my 16 GB model, so it's not the fault of the BNTV250a. The other issue is problems for apps writing to the external SD card. For a tablet with precious little internal space, you just don't want apps downloading into internal space or storing lots of data there. There is an edit to the file /system/etc/permissions/platform.xml which corrects this issue for some apps. Find the section of platform.xml below and add the last line:
Code:
<permission name=”android.permission.WRITE_EXTERNAL_STORAGE” >
<group gid=”sdcard_r” />
<group gid=”sdcard_rw” />
<group gid=”media_rw” />
This change enabled OverDrive and Kodi, for example, to download files to the external SD card. It might work for others.
Not as fluid as CM 11, but WebView issues are gone and you can access most up-to-date content (if slowly).
CM 13
https://archive.org/download/cmarchive_snapshots/cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
Never having tried this ROM on my 16 GB tablet, I was actually pleasantly surprised by its behavior on the BNTV250a. There's a funny WiFi thing where if you leave WiFi on when you shut down and then boot up again, it will not automatically connect (unless the lockscreen has come on, which is pretty fast after booting, so no biggie). Otherwise it's pretty much like CM 12 although maybe a little more stable--if you don't overdo it. The Sound Recorder app is somehow broken on the CM 13 ROM. If this is something you'd like, you can replace the broken version in /system/app/SoundRecorder with the one attached below. Make sure the permissions are rw-r-r and reboot.
Some apps can't write to the SD card (as portable storage). Kodi is an example, I'm sorry to say. I've tried many "solutions" to this problem but the only one that worked for me is to edit /data/system/packages.xml, adding the permission for each specific app you want. This is a long file and I did this using the editor from the CM File Manager. There are probably easier ways. After locating the app you want in the xml file, add this line anywhere between the <perms> and </perms> tags:
Code:
<item name="android.permission.WRITE_MEDIA_STORAGE" granted="true" flags="0" />
This change will be overwritten if the app updates, so you might want to keep that in mind.
This is the ROM I've settled on for my BNTV250a (screenshot of home screen below)
AOSP 6.01 "Marshmallow"
Box
notredame.app.box.com
(you want aosp_acclaim-ota-MOB30Z.160820.zip)
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle
This is one of the ROMs built by @amaces. The AOSP builds are very lean compared to CM ROMs so I was hoping this might perform somewhat better than CM 13. But I don't think it does.
The first big hurdle is enabling root. My thanks to @digixmax for pointing out the right tool. After first boot (or maybe even before, but I did it after) you need to flash UPDATE-SuperSU-v2.46.zip. Works perfectly.
The stock launcher is, well, funky. I replaced it with Nova Launcher but after installing a few other apps it was clear the system was under great stress. Lots of black screens and crashes. Not a good option for the BNTV250a.
AOSP 7.0
https://www.mediafire.com/?5vcw8l603d3r5sc
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Xposed
This is another ROM by @amaces and what I run on my 16 GB tablet. On that device it is virtually flawless. I really wanted to say the same for the BNTV250a, but I can't.
Enabling root for the ROM is achieved with Magisk.
The ROM appears to be odexed to Tingle and so you must flash the correct Xposed (for 7.0 and Magisk) and install the installer app along with the FakeGapps app as described in the previous post.
The stock launcher is pitiful and you need to install a root file manager to get anything done. The system is laggy and video is not smooth. Not even a potential option for the BNTV250a.
Lineage 14.1
Box
notredame.app.box.com
(there are many versions of this ROM. The link takes you to the "obsolete" folder where you need to hunt down lnos_acclaim-ota-NJH47F.180211.zip. This seems to be the only version without the shut-down bug)
Edit 2-5-23: Well...no, it does not have the classic shut-down bug (tablet reboots right after it "shuts down"). Instead, it often shuts down just fine, but occasionally locks up during shut down and has to be forced off with the power button.
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle
This is a third ROM built by @amaces (his most recent for the NT). I didn't have much hope for this because if 7.0 was an issue, I didn't expect 7.1 to perform well.
The only native root capability is for ADB. To enable full root, you need to flash addonsu-14.1-arm.zip (attached below). I did that after first boot but perhaps it can be done along with the ROM.
Not surprisingly the ROM has the feel of CM. There appears to be a file manager but it is only a partial reflection of the native file explorer and is useless for the manipulations that need to be done, so you need to adb install a root file manager as described in the previous post.
The stock browser is complete rubbish. It looks to be Gello(?) but it is the most infuriating collection of electrons I have ever encountered. There are no navigational buttons, no bookmark button--no buttons at all! I really tried. I used gestures (some rude), I tried magic words (many of which do not appear in children's books). Nada. When I finally managed to reach my test site it was like wading through, well, Jello! So....attached below is the nice lightweight stock browser from AOSP 7.0. Navigate to /system/app/Browser and there you will find Browser2.apk. Rename it to something else and copy in the Browser2.apk attached below, setting file permissions to rwx-r-r. Reboot. If you are successful, you can delete the old, useless browser apk. To enable bookmarks, navigate to /system/app/BookmarkProvider and inside you will find the apk file. Tap to install. I don't know why this needs to be done, but it does even on AOSP 7.0. Reboot and you've got a functioning browser (rife with "peek-a-boo keyboard")
The ROM hates Kodi, crashing constantly. Video from other apps is not smooth. Not a viable choice for the BNTV250a.
For a lark I tried it on the 16 GB model and it's actually not bad, but then I saw that embedded browser videos (like YouTube, for example) were funky colors, so... It may be that later versions corrected this, but those likely have the shut-down bug. In any event, a terrible choice for the 8 GB model.
Took a bit of trial and error to get the perfect version of playstore to not give an error, but I got it working. Thank you a lot for this write-up!
Yes I am breathing life back into a BN Nook in 2020 (quarantine will do funny things to a guy). Thanks for the comprehensive guide. I had installed CM11 years ago and it kinda sucks as is, so looking forward to seeing how this shakes out. I have to re-educate myself on all the various steps like adb, installing root file manager etc, it has been a long while since I played around with android's innards!
denmalley said:
Yes I am breathing life back into a BN Nook in 2020 (quarantine will do funny things to a guy). Thanks for the comprehensive guide. I had installed CM11 years ago and it kinda sucks as is, so looking forward to seeing how this shakes out. I have to re-educate myself on all the various steps like adb, installing root file manager etc, it has been a long while since I played around with android's innards!
Click to expand...
Click to collapse
While you're becoming familiar again with the procedures, give me a day or two to update the post. I recently redid my BNTV250a with CM 13 to try some things and then finally went back to CM 11 using the MicroG components rather than GApps. I'm really happy with it, but I have to say that the tablet (just like my BNTV250 with AOSP 7) behaves better if it's been on for awhile. It can be really cranky if you try to start using it right after boot.
So I'll update the post title to include CM 11 and add some details about CM 11 to the second post in a few days.
Hey thanks for keeping up with this thread! I installed CM11 as suggested but hitting a snag with tingle. I just dumped the tingl directory into the python folder as you did and ran main.py. This was the output.
C:\Python27>python main.py
MENU
1 - Patch file from a device (adb)
2 - Patch file from the input folder
> 1 adb
ERROR: Missing adb => ['adb']
NOTE: Only one binary per type is required
ERROR CODE: 65
Not sure what I'm doing wrong
denmalley said:
Hey thanks for keeping up with this thread! I installed CM11 as suggested but hitting a snag with tingle. I just dumped the tingl directory into the python folder as you did and ran main.py. This was the output.
C:\Python27>python main.py
MENU
1 - Patch file from a device (adb)
2 - Patch file from the input folder
> 1 adb
ERROR: Missing adb => ['adb']
NOTE: Only one binary per type is required
ERROR CODE: 65
Not sure what I'm doing wrong
Click to expand...
Click to collapse
I don't remember seeing the "adb" after "> 1", but I may just not remember. So, just in case and to be really clear (in case I wasn't before):
1. I assume you have adb working on your PC or you wouldn't have gotten to the Python step. Did you ever set the PATH for adb? I confess I never bothered until I tried this procedure. But you have to be able to access adb from the Python folder for this to work. If you're not sure, just cd to the Python folder and try starting adb. If it doesn't work then the PATH needs to be set. Here's a good description for Windows (scroll down to "Step 2"): https://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
2. When I said I dumped the contents of Tingle into the Python folder, I meant that literally. There is no "Tingle" folder in my Python folder,but there are a bunch of extra files that are "Tingle". Just want to be sure.
Those are my only ideas at present. I hope one of them does the trick!
Ah yes path variable did the trick! On to the next steps, I'll keep you posted!
Ok, now i am at the play store step - keep getting error "unfortunately google play store has stopped." Over and over again when attempting to open. After reboot too.
denmalley said:
Ok, now i am at the play store step - keep getting error "unfortunately google play store has stopped." Over and over again when attempting to open. After reboot too.
Click to expand...
Click to collapse
Did you
1. Check microG settings to be sure everything is OK?
2. Sign in to your Google account from the microG settings (add account)?
3. Then try the PlayStore (check permissions on Phonesky folder and app)
One part I'm not clear on. I placed all of the apks where you say to (steps 6-8), once I reboot, is play store supposed to just appear? When I do self-check in microg everything is checked except playstore and the bottom two (location). I got the impression from your instructions that I'm supposed to wait for some background processes to appear.
denmalley said:
One part I'm not clear on. I placed all of the apks where you say to (steps 6-8), once I reboot, is play store supposed to just appear? When I do self-check in microg everything is checked except playstore and the bottom two (location). I got the impression from your instructions that I'm supposed to wait for some background processes to appear.
Click to expand...
Click to collapse
Yes, the PlayStore icon should appear--admittedly a very old and funky one with this old version.
The Playstore automatically updates. I wish it did not, but there is no way to stop it. But to have that happen you have to access the Playstore at least once, maybe even download an app, and leave wifi on awhile.
On my main microG settings screen I show Google device registration ON. On the self-check screen, everything is checked except the last box. I have the location stuff installed.
So if PlayStore is unchecked, something is not right. Perhaps the app got corrupted when I uploaded it. I am shut down right now but can reup tomorrow. Or you can just get another app from Apkpure or similar. I used to use something around 8.02 to get started.
I am very much stuck at this point (unless I guess I continue with regular gapps which goes against the whole point of this approach). I tried nuking and redoing the whole process with the same result. Attached screenshots of all relevant screens to show permissions/settings/etc.
Also I can't find a "phonesky.apk" anywhere, only full-blown google store apks which are much larger than the phonesky.apk you provided and so I must assume are not the correct thing.
denmalley said:
I am very much stuck at this point (unless I guess I continue with regular gapps which goes against the whole point of this approach). I tried nuking and redoing the whole process with the same result. Attached screenshots of all relevant screens to show permissions/settings/etc.
Also I can't find a "phonesky.apk" anywhere, only full-blown google store apks which are much larger than the phonesky.apk you provided and so I must assume are not the correct thing.
Click to expand...
Click to collapse
Phonesky=PlayStore, just renamed--microG expects to see Phonesky
Something is not right with the app. I have to run, but here is a link to v. 8.02 which I have used in the past:
https://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-8-0-23-release/
Rename to Phonesky before using. It will be a little more cranky but it will work to get you going. I hope.
Edit: or, if you prefer, go to OpenGapps and download a KitKat pico GApps. Extract from that zip the Phonesky app and use it.
Edit, Edit: yeah, I tried reupping a copy of the Phonesky app but when I downloaded it the file size did not match. So I changed the first post and inserted a link to a copy on my mediafire account. That downloads with the right file size.
Well, I think I'm giving up. I've redone the process three times now. I used your new Phonesky.apk this last time and I still can't get the play store to show up. Only other thing I can think to ask - if I add a google account through microg settings, is it supposed to change to indicate that account is now added? Because if I go in there it will still say "add acount" even though I can see in the regular settings under accounts that a google account is present.
edit
The only other thing I haven't yet tried is redownloading everything and maybe even using a different PC. Ah heck who am I kidding, like I've got anything better to do. I'll keep cracking at it.
denmalley said:
Well, I think I'm giving up. I've redone the process three times now. I used your new Phonesky.apk this last time and I still can't get the play store to show up. Only other thing I can think to ask - if I add a google account through microg settings, is it supposed to change to indicate that account is now added? Because if I go in there it will still say "add acount" even though I can see in the regular settings under accounts that a google account is present.
Click to expand...
Click to collapse
I'm really baffled by this behavior. When you add a Google account via microG nothing changes on the microG settings page, but the account should show up in the CM11 settings under "accounts".
When you prepare the system for flashing, do you do an Advanced Wipe? I'm a little AR about this sort of thing, especially as my devices have been flashed with different OS's many times. I start with an Advanced Wipe, clearing out everything except, of course, the microSD card, and then I follow that by a regular wipe. Then I start flashing.
If you are still having trouble, let me know and I'll wipe my current system (I have a backup) and start again from scratch, downloading copies of the files I have posted to see if I can duplicate what is happening to you. Maybe Google has changed something in the time since I did my newest configuration and the microG folks have not caught up with it yet. This appears to be true for Contacts because I cannot get them to sync up or even see my Google contacts. This was not the case in the past. There is chatter about it on the microG site, but none of the "solutions" go anything beyond what I have already related and some of the conclusions are like "and it just started working..."
I did not do the advanced wipe, so let me try that. I'm also going to redownload everything and give it another go. No need to wipe your device just yet - you've already done WAY more than I expected to help! I will do this over the next few days and keep you posted.
Well I tried six different ways, full wipe, change the "group" set for the group permissions to "root" (it had been set to sdcard), redownloaded every last bit of software used in this process, used a different computer, etc etc etc. Nothing is working. Still no play store. Everything else seems to be fine except that.
So anyway, I finally just did a full wipe, flashed the CM11 unofficial that you provided in second post, and grabbed a kk gapps package and flashed that. Switched from trebuchet to nova and I've got a tablet I can live with! Working much better then the cm10 rom I had on there before (like swipe to unlock screen, wait 5 seconds....touch app drawer, wait 5-10 seconds....touch an app, wait 30 seconds....slooooooow).
Thanks for pushing me along in this direction, before I started back into this process I had completely forgotten all the little intricacies which would have gotten me hung up and possibly bricked. And all the of the other guides out there have broken links, outdated info, etc. So I'm happy with where I landed and very much appreciate the help, even if we didn't quite get there with your proposed improvements! I now have a capable e-book, backup songbook for gigs, and a spare digital mixer controller that I can clean up the personal stuff from and hand off to an assistant.
denmalley said:
Thanks for pushing me along in this direction, before I started back into this process I had completely forgotten all the little intricacies which would have gotten me hung up and possibly bricked. And all the of the other guides out there have broken links, outdated info, etc. So I'm happy with where I landed and very much appreciate the help, even if we didn't quite get there with your proposed improvements! I now have a capable e-book, backup songbook for gigs, and a spare digital mixer controller that I can clean up the personal stuff from and hand off to an assistant.
Click to expand...
Click to collapse
I'm glad you reached a point where you feel good about the outcome but sorry that you had to waste so much time.
I will run through the procedure again in the next few days. Maybe there's something that got garbled in the updating of the post. In any case I'd feel better if my instructions actually achieved the intended result.
nmyshkin said:
I will run through the procedure again in the next few days. Maybe there's something that got garbled in the updating of the post. In any case I'd feel better if my instructions actually achieved the intended result.
Click to expand...
Click to collapse
Well.....I'm not sure how the error crept in, but it looks like the creation of the Phonesky folder was the issue. This is needed for ROMs beyond CM11, but there are no folders in /system/app or /system/priv-app for CM11. Thus for CM11 only, the files like Phonesky.apk are simply dropped into /system/priv-app and the permissions set as described, Then everything works as it should.
I've corrected the instructions. My apologies.