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.
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
How do I make Androidlost app factory-reset-proof? I'm pretty amazed that this serious issue hasn't been answered yet in all those threads I searched regarding Androidlost.
As I understood it's possible for any rooted device to put an app in system/app and it would survive a factory reset, but the question is about the setting of this particular app, and I would be very grateful if someone who managed to do this successfully will share this step-by-step.
Thanks
bump?
rrayden said:
bump?
Click to expand...
Click to collapse
bump!
WOW, not a single answer? This is amazing...
As you said, you need to be rooted for that.Apk file would need to be transferred to system/app folder.
There's no way you can do it if you're not rooted.
Sent from my HTC Wildfire S A510e using xda premium
Nightshadow931 said:
As you said, you need to be rooted for that.Apk file would need to be transferred to system/app folder.
There's no way you can do it if you're not rooted.
Sent from my HTC Wildfire S A510e using xda premium
Click to expand...
Click to collapse
I am rooted and I understood that.
I am asking if anyone has done this (or knows exactly how it is done), making Androidlost factory-reset-proof aka after a factory reset is this still working good? Aren't there any settings or any app data that also needs to be "saved" somehow to protect it in case of a factory-reset? I just put the apk in /system/app and all should be working perfectly??
LE: Come to think about it, it should be easy for me to test this... just make a nandroid backup first, right?
so has anyone been able to move an apk to /system/app AND find a way to make their settings for a particular app factory reset-proof? im trying to find a way to protect not just an app I have on my phone but also the settings
careenprokop85 said:
so has anyone been able to move an apk to /system/app AND find a way to make their settings for a particular app factory reset-proof? im trying to find a way to protect not just an app I have on my phone but also the settings
Click to expand...
Click to collapse
I am working on it.
So far I have managed to modify the kernel, to make it reinstall androidlost on every reboot. This would allow the app to survive any wipe, factory reset, firmware update, short of flashing the kernel itself!
The problem is the settings. I can easily add my own settings to my own custom kernel, but I doubt many people would want their phone to report to me. And asking everyone to modify the kernel themselves to store their own settings, is out of the question.
I have contacted the developer of androidlost to see if we can make it work so that it only needs to be configured once on a specific phone, and then it is tied to the IMEI. This way, the settings would survive anything, and would always get updated whenever the phone contacts androidlost servers.
ok, well what about building the apk and settings into a custom rom? such as, taking the stock rom (or mr robinson's root66 roms), installing the apk, set up the apk with whatever settings you want, then building a custom rom out of that? then, if you do a master reset, wouldnt the apk and settings be exactly as they were when u first made it? I hope that makes sense lol.
any news on this?
arman68 said:
I am working on it.
So far I have managed to modify the kernel, to make it reinstall androidlost on every reboot. This would allow the app to survive any wipe, factory reset, firmware update, short of flashing the kernel itself!
The problem is the settings. I can easily add my own settings to my own custom kernel, but I doubt many people would want their phone to report to me. And asking everyone to modify the kernel themselves to store their own settings, is out of the question.
I have contacted the developer of androidlost to see if we can make it work so that it only needs to be configured once on a specific phone, and then it is tied to the IMEI. This way, the settings would survive anything, and would always get updated whenever the phone contacts androidlost servers.
Click to expand...
Click to collapse
I'm very interested in learning how you modified your kernel to reinstall AndroidLost at every reboot AND how you put your own personal settings in the kernel so that they are applied to AndroidLost everytime!
If you wouldn't mind, could you possibly reply to this post, or send me a private message, explained how you modified the kernel and what I would need to do to input my own settings into my kernel? I'm fairly knowledgeable when it comes to rooting, flashing ROMs and kernel, and dabbling alittle in writing my own apps... So I shouldn't have too much trouble doing what you did if I could just get a little example and pointed in the right direction!
Thread moved.
Please post in the proper forum. Android inquiries belong in Android Q&A, Help & Troubleshooting.
bluegizmo83 said:
I'm very interested in learning how you modified your kernel to reinstall AndroidLost at every reboot AND how you put your own personal settings in the kernel so that they are applied to AndroidLost everytime!
If you wouldn't mind, could you possibly reply to this post, or send me a private message, explained how you modified the kernel and what I would need to do to input my own settings into my kernel? I'm fairly knowledgeable when it comes to rooting, flashing ROMs and kernel, and dabbling alittle in writing my own apps... So I shouldn't have too much trouble doing what you did if I could just get a little example and pointed in the right direction!
Click to expand...
Click to collapse
Me too I'm interested! Please PM
Alex
proofed by me
rrayden said:
How do I make Androidlost app factory-reset-proof? I'm pretty amazed that this serious issue hasn't been answered yet in all those threads I searched regarding Androidlost.
As I understood it's possible for any rooted device to put an app in system/app and it would survive a factory reset, but the question is about the setting of this particular app, and I would be very grateful if someone who managed to do this successfully will share this step-by-step.
Thanks
Click to expand...
Click to collapse
proof, i'm factory reset by me and android lost still there, in another case, my Samsung grand prime get some error and I bring to Samsung service center then my phone got factory reset with software update, and........ guess what ? android lost still there, bravo
but what about the settings? im interested on doing something like this for wheres my droid, so far the only app that does this succesfully is CERBERUS, i would like to take the wheres my droid and make it a system app (no problem there) but how to preserve the settings etc?
factory reset proof
I have been searching for a way to implement this and today i found this resource that you might find useful : (search) how to install any app as system app on android (addictivetips website) - sorry, i can't be allowed to post a link here.
I implemented one of those methods and i succeeded in making androidlost a system app in my phone. However, i havent tested whether it will still be useful after a factory reset due to loss of app settings (data).
This probably won't help but https://groups.google.com/forum/#!topic/cerberus-support-forum/0zH3VEu1H9w
Intro
I don't mean this to be a thread for any specific ROM or problem, but rather a general guide that essentially eliminates all doubt of machine or user error (we all make mistakes). This is generally geared towards the issues users are experiencing when flashing an AOSP ROM, but can also apply to Sense, and even other devices. This covers from downloading a ROM forward, and also making sure that everything gets properly installed with no corners cut, so that everybody can be on the same page when a problem arises. I'm not trying to say anybody's way of doing things is wrong, but I've see a lot of people asking different questions that end up getting solved with the same few answers. This isn't a "how to flash" thread, but rather how to ensure you're getting your device in a clean, fresh state so that everybody can be on the same page when it comes to bugs, otherwise nobody is going to want to help you if you don't try to help yourself first.
I know this is on the longer side, so key points are underlined, with a TL;DR at the bottom
Downloading
Checksums or hashes are a great way to make sure that the *.zip or any other file you're downloading is not only the right one, but that it hasn't been corrupted or tampered in transfer (uploads or downloads). You'll probably need to install something to work with chescksums- personally I like the open-source HashCheck for Windows. It adds a "Checksums" tab to the right-click > Properties dialog that automatically calculates MD5 (most common) and SHA-1 (more advanced) hashes. I encourage anyone posting a file to also post the MD5 with it, for everybody's sake, since it only takes a few extra seconds to eliminate all doubt of a bad upload or download. HashCheck even gives an option to create a *.MD5 file, just like the ones you might get from goo.im. If you're on Linux, Android, or presumably Mac you can check a file's md5 by opening terminal and simply typing "md5sum <filename>" without the quotes. If a file is posted without an MD5, you can download it twice and check it against itself, but just keep in mind you're going to be hitting somebody's server twice as hard, so only do it if necessary. Now that you're sure you have the right files...
Wiping/Flashing
Most people know dirty flashing is at your own risk, and if you have a problem, the first thing anybody's going to tell you is to do a clean flash. No really, just clean flash- that's what backups are for, but that's a whole different topic. Unfortunately, most people consider a clean flash to be just a factory reset, but that only wipes dalvik, cache, and data (except your sdcard), while leaving the system partition intact. To do a proper clean flash you want to go into advanced and make sure that system gets wiped in addition to dalvik, cache, and data. I can't say exactly what (sorry), but there's lots of miscellaneous things that can persist between flashes, especially when you're going to a different ROM. For us DNA owners, there's still a lot of activity in our CM device tree, meaning that even on the same ROM, some of our device files may change between versions which will necessitate a wipe of system. Maybe it's just me, but it seems things go out of line more often on 4.3 so I just always wipe system now.
If you're here, you probably know how to flash a ROM, but always double check the OP or first few posts and see what gapps/settings/etc are recommended. I'm also going to remind you that it takes just a few extra seconds to create a *.md5 file with HashCheck that you can push to your device along with the *.zip and TWRP (probably CWM too) will check the file against it's MD5 before flashing it. After using the Setup Wizard to log in to your Google account, make sure that you uncheck the box to restore settings and data to your phone, otherwise those can cause problems. Now you can be sure that whatever is on your device is clean as can be and as the developer intended, otherwise you're probably not going to get much help.
Narrowing down the problem
Now that you've got a brand spanking new and clean ROM is the best time to try and narrow down a problem, but before you post anything, try the golden rule of IT- "Have you tried rebooting it yet?" Also, you can try booting to recovery to clear just dalvik and cache and/or repair permissions. This is the first time you should consider making a post about your problem, but please, please, please don't make a post that just says something like "Settings FCs." Posts like that don't tell anybody anything- the best thing you can do is pull a log (more on that in a second), and create a post in the appropriate thread which you can determine as follows: Start by seeing if the problem occurs with nothing installed besides the ROM and recommended gapps- do not restore any backups, install any apps, or flash any kernels, even if the OP recommends it. If you're having problems with Settings or any Google app, there's likely a conflict with the gapps package that should go away if you reflash only the ROM, otherwise it's a bug in the ROM itself. Either way, if you can reproduce a problem at this point you should post in the ROM thread. If you want to flash a custom kernel, only do so after you've verified the problem isn't with the ROM or gapps. Flash only the kernel, and if there's any problems after that, post them in thread you got the kernel from, not the ROM thread.
If you're having a problem with an app, once you've completed the above steps, install only that app without restoring any data. If you can't replicate the problem, there's likely an incompatibility any corresponding data you may have restored, and sorry, but there's not really anything you can do about that. If the problem occurs with a freshly installed app, first check the Play Store to see if other users are experiencing the same problem- there may just be something wrong with the app. If it only seems to be you having this problem with a clean install, the ROM thread is the best place to post, although keep in mind other users may not be familiar with app.
Pulling and posting logs
Even now, nobody is obligated to help you (you flashed that ROM at your own risk, remember?), but once you're at this point, you'll have a better chance at getting help. Try to include as much information as possible like what else you were doing, what screen you were on, what button you tried to press, etc. and if you can, try to see if you can replicate it. Like I mentioned above, posting a log is the best way to get help, and they're really easy to get. Not everybody is going to understand every line, but if you know what you're looking for, occasionally the log can tell the developer exactly what the problem is, and bam- easy fix.
First make sure USB Debugging is enabled in Developer Options (if you don't see Developer Options, go into About Phone and tap on the Build Number line 7 times), and make sure that Root Access is set to both Apps and ADB. Now as far as gathering these logs, SysLog is by far one of the easiest ways- download it, open it, and press "Take Log." It pop up a toast message saying that your logs are in /sdcard/SysLog/<DATE_TIME>.zip and it'll even give you the option to share it via email, Dropbox, or anything else you might use. Post that and you'll have even better chances of getting help. For simplicity, I'm not going to details on manually pulling logs, however if you're stuck in a bootloop or something like that and can't run the app, use "adb pull /proc/last_kmsg" and post a link to that file.
TL;DR
Sh*t happens, learn to deal with it or go back to stock
Verify your download with an MD5 Checksum
Wipe system in addition to factory reset (dalvik, cache, & data)
Flash ROM and gapps without installing anything else or restoring any data
Pull a log, it's really easy
Now is the best time to make a post about your problem
Radio/Reception Problems on the DNA?
First things first- Double check your settings in Settings > More > Mobile networks. They should be as follows:
Data Enabled: Yes
Data Roaming: No (unless you're actually roaming)
National Data Roaming: Yes (otherwise you'll probably lose data; this won't get you any roaming fees)
Network Mode (Verizon): LTE/CDMA/EvDO (or Global, which is everything, I've never noticed any difference between the two)
Network Mode (GSM): GSM/WCDMA preferred (depending on the ROM, you may also need to flash the GSM patch courtesy of Flyhalf205 from the 2nd post in the original CM10.1 thread.)
System Select/CDMA Roaming: Automatic
CDMA Subscription: RUIM/SIM
GSM users may also need to manually enter APN settings for your carrier to get things like MMS functioning properly. I'm not going to compile a worldwide list, but if Google fails you, your carrier should have support documentation with these settings. Recently, I noticed this file in the android source lists tons of APNs, so try finding your carrier in there too.
Why do I have 0-1 bars? I got a lot more on Sense
Don't be alarmed if your reception looks low/non-existent. Sense "pads" the signal bar to get it to show bars more "accurately," but AOSP does not, so expect a drop in bars. To get an accurate assessment, you want to be looking at your actual signal in dB before trying to diagnose anything by going to Settings > Interface > Status Bar and changing Signal Status Style to Text, and your signal bars will be replaced with a negative number, therefore a value closer to zero indicates a stronger signal. If you don't like negative numbers, another way of thinking about this is as if the phone was telling you how far you are away from the nearest tower. What would normally be 5 bars on Sense equates to -70dB, and 1 bar equates to -115, but these are approximate values and depending on your location and environment, you might bee numbers outside this range.
I'm still having problems
Unfortunately, our phone is known to have problems with reading the SIM card. Some say it's purely software, some say its purely hardware, but I believe it can be either. I'd first suggest giving your SIM card a cleaning by popping it out and gently rubbing the contacts with a clean rubber eraser, another more risky option is a just drop of isopropyl alcohol on a cotton swab. If you have compressed air, you can give that a small blast into the SIM slot from a few inches away. If the phone is still having issues with reading the SIM after that, it might need to be replaced.
Another possibility is issues with the radio firmware. You can try updating the firmware by following the instructions in this post. Personally, I recommend the most recent version, 2.06.605.1. Some users, myself included, have reported that sometimes a full RUU back to 100% stock is necessary to restore proper radio function. Instructions for that can be found here, but be aware that this can be a lengthy, tedious process. You'll end up having to re-unlock and root your phone before you'll be able to flash anything else again, so I only recommend this as a last resort, but is nonetheless something to bear in mind.
Stickie this?
Sent from my HTC6435LVW using Tapatalk 4
I'm going to stick it for now, it's actually good basic info. But I am moving it to the Q&A forum.
Thank you. I debated where to post this, but since this mainly applies to those of us who are flashing away from Sense, I thought it would get more attention with the development section, but I respect your decision to move it.
pyroguysf said:
Thank you. I debated where to post this, but since this mainly applies to those of us who are flashing away from Sense, I thought it would get more attention with the development section, but I respect your decision to move it.
Click to expand...
Click to collapse
Yeah that makes sense, and I was hoping this would also cut down on unnecessary thread starts.
I think what I'll do is have this in both development forums as a sticky, hopefully this will help out some of the chefs.
If you edit one thread, be sure to edit the clone in the other forum.
I am going to let you clean this up as much as possible over the weekend, then maybe move it to the dev threads Monday as a polished product, see if you can get as much info as possible about GSM to include about the signal issues etc.
Part of the issue is that a lot of the users who are guilty of saying "this is broken, fix it" with no logcat and not having wiped or installing some app that is causing the issue don't read stickies, but it's a good resource to have.
You might add something about restoring apps from TI or MyBackup and apps causing issues, or installing some root app and then having issues, a solution might be to wipe, then boot, then try to reproduce the issue, or uninstalling the app.
Also if you flash a different kernel, do not then go into the ROM thread and start saying something doesn't work, having installed a kernel that did not even come with the ROM and confusing the chef.
orangekid said:
Part of the issue is that a lot of the users who are guilty of saying "this is broken, fix it" with no logcat and not having wiped or installing some app that is causing the issue don't read stickies, but it's a good resource to have.
Click to expand...
Click to collapse
I've noticed this, but I made this in hopes of giving people a place to link back to rather than having to waste time typing out the same things over and over, which is why I also put the link in my sig.
orangekid said:
You might add something about restoring apps from TI or MyBackup and apps causing issues, or installing some root app and then having issues, a solution might be to wipe, then boot, then try to reproduce the issue, or uninstalling the app.
Also if you flash a different kernel, do not then go into the ROM thread and start saying something doesn't work, having installed a kernel that did not even come with the ROM and confusing the chef.
Click to expand...
Click to collapse
Good ideas. I'll try to add a section for apps when I get a chance. I tried to briefly touch on the kernel situation by saying to read the OP for recommended settings, but I'll definitely expand on that.
OP edited for clarity/grammar and updated with information for apps and determining where to submit your post (e.g. ROM vs kernel thread). Second post updated with GSM info.
pyroguysf said:
OP edited for clarity/grammar and updated with information for apps and determining where to submit your post (e.g. ROM vs kernel thread). Second post updated with GSM info.
Click to expand...
Click to collapse
Sounds good.
Moved to dev forum.
If you want to go ahead and create the same thread and copy / paste the first 2 posts, I can sticky it.
Hey guys!
I have been using Omni ROM for a while. And yes, its a pretty stable KitKat ROM! Almost everything works fine without any issue. But the thing that bugged me was root. There wasn't root permission in the the ROM. So no link2sd and no other script works for expanding storage.
So basically, the only major problem in the ROM was ROOT.
So I worked it out and present before you an easy method.
Prerequisites:
Omni ROM
Root flashable zip
Method:
Download the required packages
Install Omni ROM (Refer installation from this)
Reboot
Now go back to recovery and flash root.zip
Reboot
Enjoy
NOTE:
You need to have atleast 3mb in /system
This zip is only for ARM based devices and won't work with x86 based devices
P.S. Personally this is the best ROM to use as daily driver
rhar**** said:
Hey guys!
I have been using Omni ROM for a while. And yes, its a pretty stable KitKat ROM! Almost everything works fine without any issue. But the thing that bugged me was root. There wasn't root permission in the the ROM. So no link2sd and no other script works for expanding storage.
So basically, the only major problem in the ROM was ROOT.
So I worked it out and present before you an easy method.
P.S. Personally this is the best ROM to use as daily driver
Click to expand...
Click to collapse
Congrats! Downloading and will give a try
Looks very much like a normal superuser or superSU install.
Very good that will work on other devices as well. I mean, ours would not have all the google apps on system. No room for one of them
The su binary is much smaller than cm-11's.
Comment, should probably go on xbin, be symlinked to bin.
Normally, superuser.apk is installed as a user app and would be updated as such from play. But may try it this way!
Great work.
Dovidhalevi said:
Looks very much like a normal superuser or superSU install.
Very good that will work on other devices as well. I mean, ours would not have all the google apps on system. No room for one of them
The su binary is much smaller than cm-11's.
Comment, should probably go on xbin, be symlinked to bin.
Normally, superuser.apk is installed as a user app and would be updated as such from play. But may try it this way!
Great work.
Click to expand...
Click to collapse
We can have Google apps on our phone as well. I have managed to do so, at least the important ones.
Gonna upload that too soon
rhar**** said:
We can have Google apps on our phone as well. I have managed to do so, at least the important ones.
Gonna upload that too soon
Click to expand...
Click to collapse
They should NOT be on system/app, especially on our phones. Install from Play as user apps, let link2sd symlink them.
Anyway, flash worked like a charm! Neatly got rid of CWM's superuser, installed superSU which I will leave as a system app for now.
Note that it behaves like what I tried, spawns multiple instances of su and daemonsu (should daemonsu be symlinked to su--why have two copies?).
Link2sd played immediately. Tasker took some time. Xposed almost did not make it. Finally, after a blank screen freeze, reboot, a few attempts, got the dialog! Talking a good ten minutes or aggrivation. What is unique about how this asks for root?
Dovidhalevi said:
They should NOT be on system/app, especially on our phones. Install from Play as user apps, let link2sd symlink them.
Anyway, flash worked like a charm! Neatly got rid of CWM's superuser, installed superSU which I will leave as a system app for now.
Note that it behaves like what I tried, spawns multiple instances of su and daemonsu (should daemonsu be symlinked to su--why have two copies?).
Link2sd played immediately. Tasker took some time. Xposed almost did not make it. Finally, after a blank screen freeze, reboot, a few attempts, got the dialog! Talking a good ten minutes or aggrivation. What is unique about how this asks for root?
Click to expand...
Click to collapse
Yes, it takes a bit of time sometimes. It's slow and can't help it .
So here's my suggestion, in settings, set default access to 'grant'. It's a bit faster this way
Sent from my LG-P500 using XDA Premium 4 mobile app
rhar**** said:
Yes, it takes a bit of time sometimes. It's slow and can't help it .
So here's my suggestion, in settings, set default access to 'grant'
Click to expand...
Click to collapse
The problem is unique to Xposed. Everything else comes either immediately to quickly enough. I will post to that dev thread about this.
Dovidhalevi said:
The problem is unique to Xposed. Everything else comes either immediately to quickly enough. I will post to that dev thread about this.
Click to expand...
Click to collapse
Worked fine for me.
Try again by giving root permissions by default
ROM is good.
However, after flash GAPPSLight. Root have gone. It should be not enough space in /system
z1022 said:
ROM is good.
However, after flash GAPPSLight. Root have gone. It should be not enough space in /system
Click to expand...
Click to collapse
Shouldn't happen if the OTA survival mode is present. But ya, the only problem may be the space in /system
z1022 said:
ROM is good.
However, after flash GAPPSLight. Root have gone. It should be not enough space in /system
Click to expand...
Click to collapse
MUST trim the ROM. Omni is no different here, maybe even bigger.
The superSU installation wil temporarily move some stuff to make room for the root install, then move it back. However, none of that stuff belongs on system. There is not enough room for even one of those gapps. GAPPSLight is trivial and should not fill you up. In other words, trim the ROM first.
---------- Post added at 12:36 AM ---------- Previous post was at 12:30 AM ----------
rhar**** said:
Yes, it takes a bit of time sometimes. It's slow and can't help it .
So here's my suggestion, in settings, set default access to 'grant'. It's a bit faster this way
Click to expand...
Click to collapse
First thing I tried (with my simple daemon start method). Never came up. But up and running now, all's well that ends well.
Question: SuperSU offers to make a backup script first time the UI is exercised. Promises to survive further flashes. Does this indeed work (and ... how)?
I will copy files and edit a version of the setup script from this zip and have them available on my sdcard just in case
Modded Omni Rom
@rhar****,
I have a request 4 u. Please make a modded OMNI rom 4 us. Yesterday I flashed the Jenkins 10th march version. I can't use for more than a while, 'cause i can't install any file manager or any .apk, moreover things went wrong after i flash gapps.. But I loved it and want to hav it as a daily driver. So, if u don't hv any project / busy schedule then pls.try. Anyway 2day i will flash this build.
sumansur2008 said:
@rhar****,
I have a request 4 u. Please make a modded OMNI rom 4 us. Yesterday I flashed the Jenkins 10th march version. I can't use for more than a while, 'cause i can't install any file manager or any .apk, moreover things went wrong after i flash gapps.. But I loved it and want to hav it as a daily driver. So, if u don't hv any project / busy schedule then pls.try. Anyway 2day i will flash this build.
Click to expand...
Click to collapse
Smell a rat! Trim that ROM first.
Omni has it own file manager called "Documents." The CMFileManage can be installed as a user app.
BUGs on Omni -- I still am using a daily driver, though:
1. Clock FC's. Widgets appear fine (I use Chronus) but no alarms, stopwatch, wordclocks, etc.
2. GPS apparently not functioning, though location services seem to work. Some apps dependent on GPS FC.
3. Long widget, background process startup times but much better than cm-11
4. About 10 meg worth of apps symlinked by link2sd will be un-symlinked (more probably dereferenced) on start up. Easily cleaned up every few starts. Make sure to recreate link2sd build scripts freshly, reboot after new flash or internal storage mishaps worse than this.
5. Will usually get a wait message on system on startup. Everything works anyway, just open home screen and dismiss.
Those dl builds are genuine "nightlies," scheduled, regardless of whether or not any changes made that will be noticed.
Dovidhalevi said:
Smell a rat! Trim that ROM first.
Omni has it own file manager called "Documents." The CMFileManage can be installed as a user app.
BUGs on Omni -- I still am using a daily driver, though:
1. Clock FC's. Widgets appear fine (I use Chronus) but no alarms, stopwatch, wordclocks, etc.
2. GPS apparently not functioning, though location services seem to work. Some apps dependent on GPS FC.
3. Long widget, background process startup times but much better than cm-11
4. About 10 meg worth of apps symlinked by link2sd will be un-symlinked (more probably dereferenced) on start up. Easily cleaned up every few starts. Make sure to recreate link2sd build scripts freshly, reboot after new flash or internal storage mishaps worse than this.
5. Will usually get a wait message on system on startup. Everything works anyway, just open home screen and dismiss.
Those dl builds are genuine "nightlies," scheduled, regardless of whether or not any changes made that will be noticed.
Click to expand...
Click to collapse
I saw a file manager namely"Documents", but i couldn't install any .apk from there, it said " the file can't be opened" or such that. I flash a file explorer but can't enter enter any subfolder in sdcard. But i will have a another go 2day.
sumansur2008 said:
@rhar****,
I have a request 4 u. Please make a modded OMNI rom 4 us. Yesterday I flashed the Jenkins 10th march version. I can't use for more than a while, 'cause i can't install any file manager or any .apk, moreover things went wrong after i flash gapps.. But I loved it and want to hav it as a daily driver. So, if u don't hv any project / busy schedule then pls.try. Anyway 2day i will flash this build.
Click to expand...
Click to collapse
Yea, I'll try to make a Trimmed ROM soon
sumansur2008 said:
I saw a file manager namely"Documents", but i couldn't install any .apk from there, it said " the file can't be opened" or such that. I flash a file explorer but can't enter enter any subfolder in sdcard. But i will have a another go 2day.
Click to expand...
Click to collapse
For time being, to install any apk, get a file manager. If you cant, then from Documents, navigate to the apk and hold on it. It will be highlighted. Now copy it and from documents' side panel (swipe from left) go to Downloads and paste it there. Now go to Downloads from app drawer and install from there.
The root is working pretty fine. I tried a lot of times. Sorry to say it now when maybe a week passed, but I forgot to comment. Omni seems to be a good project. And this is the first taste of omni and kit kat, so doble pleasure.
chalo99 said:
The root is working pretty fine. I tried a lot of times. Sorry to say it now when maybe a week passed, but I forgot to comment. Omni seems to be a good project. And this is the first taste of omni and kit kat, so doble pleasure.
Click to expand...
Click to collapse
Yeah. I too use it as a daily driver, and so am thinking of mading it a bit. Like Halo))) or multiwindow
But, unfortunately, not anytime soon
rhar**** said:
Yeah. I too use it as a daily driver, and so am thinking of mading it a bit. Like Halo))) or multiwindow
But, unfortunately, not anytime soon
Click to expand...
Click to collapse
Xposed Xhalo will work in cm-11 but not in omni! Omni takes the window's flag for ... its own multiwindow. So ... where is that?
Xposed multiwindow (its own UI) might work in omni or alongside halo or xhalo ... uses a different flag to avoid the conflict.
In any event, Xposed might be the best way to get these things.
Dovidhalevi said:
Xposed Xhalo will work in cm-11 but not in omni! Omni takes the window's flag for ... its own multiwindow. So ... where is that?
Xposed multiwindow (its own UI) might work in omni or alongside halo or xhalo ... uses a different flag to avoid the conflict.
In any event, Xposed might be the best way to get these things.
Click to expand...
Click to collapse
Yea, I was also wondering about multi-window
And never noticed the thing about HALO. Will try to get something done.
Hi rhar****,
I sucessfully flashed the root.zip into my device(Samsung Galaxy Tab2 10.1 GT-P5110, OMNI6.0.1 based on Android 6), but the SuperUser couldn’t work without a binary file.
The screenshot is in Chinese, it said that ‘The SU Binary file is not installed, and it can’t be downloaded and installed via SuperUser. If you just upgraded to Android 4.3, go to the forum and download the binary file, then install it manually. ’
Can you please offer me the binary file? Or give me an URL?
Followed all the steps in the detailed "[HOW-TO] Installing AOSP Android 7.0 "Nougat" Internally on the 16 GB Nook Tablet". During the process I was unable to install the suggested open_gapps-arm64-7.0. Tried several times, so right now I ended up with a mean and lean android system with 3 icons on the home screen. .
I'm a beginner doing this. So I attempted to copy superuser apk and the play store apk via usb connection to no avail. Don't even know where they ended up. I'm able to do a google search but it does not retain any bookmarks I'll be making, the reason being explained as I'll need an updated bookmark apk. (Which one??) and how do I install that?
Anyone out ther who can guide me in the right direction? Much appreciated. I do understand a little of the jargon being used in the forums here.
leenaud said:
Followed all the steps in the detailed "[HOW-TO] Installing AOSP Android 7.0 "Nougat" Internally on the 16 GB Nook Tablet". During the process I was unable to install the suggested open_gapps-arm64-7.0. Tried several times, so right now I ended up with a mean and lean android system with 3 icons on the home screen. .
I'm a beginner doing this. So I attempted to copy superuser apk and the play store apk via usb connection to no avail. Don't even know where they ended up. I'm able to do a google search but it does not retain any bookmarks I'll be making, the reason being explained as I'll need an updated bookmark apk. (Which one??) and how do I install that?
Anyone out ther who can guide me in the right direction? Much appreciated. I do understand a little of the jargon being used in the forums here.
Click to expand...
Click to collapse
I'm sorry to tell you that those are the wrong GApps for the hardware. I will update the original instructions. What you need are the arm GApps, not the arm64 (remember, this is OLD hardware). The filename of the zip I used is open_gapps-arm-7.0-pico-20170310.zip
At this point, having done some fooling with the system, it's best to start the entire process over. That will give you the most stable result. You cannot install the PlayStore and have it function without GApps, so just forget that part. The superuser file I mentioned is a must, once you get the PlayStore working.
The Bookmark provider apk is already on the device. Re-read the second post in the instructions. You just have to tap to install it, for some unknown reason.
Thank so much for your quick response. You were absolutely correct that I was installing the wrong gapps, so I started over again with the 7.0 stock (error message), the nano (same thing) and finally the pico and that one worked. By that time I hit the sack. I found that out shortly after I posted the message. I kept reading and reading the instructions and completely overlooked the GAPPS choices I had. Even a very cryptic error message popped up that said something about "incompatible" and "arm". Duhh. So what I'm going to do is wipe it clean again (3rd time) and reinstall everything so I can do it in my sleep.
Regards
leenaud said:
Thank so much for your quick response. You were absolutely correct that I was installing the wrong gapps, so I started over again with the 7.0 stock (error message), the nano (same thing) and finally the pico and that one worked. By that time I hit the sack. I found that out shortly after I posted the message. I kept reading and reading the instructions and completely overlooked the GAPPS choices I had. Even a very cryptic error message popped up that said something about "incompatible" and "arm". Duhh. So what I'm going to do is wipe it clean again (3rd time) and reinstall everything so I can do it in my sleep.
Regards
Click to expand...
Click to collapse
If you reformatted data as f2s, you might need to change it back to ext4 before you can do a successful wipe. Just a thought.
nmyshkin said:
If you reformatted data as f2s, you might need to change it back to ext4 before you can do a successful wipe. Just a thought.
Click to expand...
Click to collapse
I'm lost. All I did during the previous wipes, went into Advanced Wipes and cleaned out everything. Did.n't format. So are you saying I format first (ext4) and then do a complete wipe? The last time I booted it seemed to be very unstable. Looked like an invisible finger was touching the screen. Jumped all over the place.
leenaud said:
I'm lost. All I did during the previous wipes, went into Advanced Wipes and cleaned out everything. Did.n't format. So are you saying I format first (ext4) and then do a complete wipe? The last time I booted it seemed to be very unstable. Looked like an invisible finger was touching the screen. Jumped all over the place.
Click to expand...
Click to collapse
OK, I read your instructions again and think I know how to go about it. If all goe well during the installation ad it still seems unstable when booting I might ask for help again.
Thank you
leenaud said:
OK, I read your instructions again and think I know how to go about it. If all goe well during the installation ad it still seems unstable when booting I might ask for help again.
Thank you
Click to expand...
Click to collapse
Me again. Everyting installed without a problem. Was able to get a couple apk from google plastore. Having said that, I also installed ES filemanager thinking it would give me root access. (no go.) No option under the developers option either. So gave up on that. Also I noticed that depending what apk I loade, the response time was rather slow. Also for no reason at all it came randomy up with "shutting down" messages. And it seems to execute some stored touch screens as it was going all over the place. At this point I'm going to be looking for something else. Again thank you for your help
leenaud said:
Me again. Everyting installed without a problem. Was able to get a couple apk from google plastore. Having said that, I also installed ES filemanager thinking it would give me root access. (no go.) No option under the developers option either. So gave up on that. Also I noticed that depending what apk I loade, the response time was rather slow. Also for no reason at all it came randomy up with "shutting down" messages. And it seems to execute some stored touch screens as it was going all over the place. At this point I'm going to be looking for something else. Again thank you for your help
Click to expand...
Click to collapse
Sorry it didn't work out for you. It continues to perform very well for me. Seems like each piece of hardware has its own quirks.
Is this for the Nook 2016 or 2018 hardware versions, or does it work with both?
Goggles2114 said:
Is this for the Nook 2016 or 2018 hardware versions, or does it work with both?
Click to expand...
Click to collapse
Are you talking about the firmware upgrades for the original Nook Tablet or thinking about the various newer devices called by the same name?
This is for the OLD Nook Tablet BNTV250.