Related
Looks like 1.1 is confirmed for January and will allow you to sideload apps on the NC in development mode. Not certain when Froyo 2.2 will be available, probably when they launch the store front in Q1, maybe it's in 1.1?
connect.nookdeveloper.com/t5/General-Discussion/Nook-Color-Rooting/td-p/901
Also mention of sideloading apps.
connect.nookdeveloper.com/t5/General-Discussion/Can-you-test-your-apps-on-a-real-hardware-now/m-p/47#M18
Good news!
Josh
I guess I'm the grinch who steals the joy from this news...we can already sideload (heck we have a working Market), and based on the original post I seriously doubt Froyo is coming for the ride with the 1.1 update. I think Froyo is much bigger news, and will get it's own announcement.
Not sure what development mode adds, since rooted users already have the goodies. Tell me I missed something...
-Matt
If that is all they added in the update ill be disappointed. Sounds like all they are gonna do is enable adb. Which is easy enough to enable anyways.
Send from my NookColor
Of course it's not big news here!!! You have to consider that it is for those who haven't rooted their unit. You knew it was coming, so why all the negativity?
Cheers,
kev
No negativity here. I probably should have added a few smiles and winks to make it clear that I was (mostly) teasing (i.e,. the grinch comment). I'm a pretty happy owner, and will gobble up whatever news I can find. I think recent developments with Bluetooth and Nookie Froyo are definitely things to celebrate. Maybe 1.1 has something special that we don't see yet.
-Matt
Yeah, apart from froyo, most of the news from B&N will likely not be as exciting as anything from the developers here.
I am curious what this 1.1 update means for the integrity of my currently nootered NC. Should I be concerned when B&N pushes this update my way?
Kev
It's good news to see sideloading for those that do not wish to root..
-CC
Question regarding upcoming Froyo update (packed with v1.1, or otherwise):
If B&N officially updates to 2.2, they open up development mode for app sideloading, and they also allow for the unrestricted use of normal Froyo home screens (and launchers?), will there be any reason remaining to actually "root" the device at that point?
Or, is B&N talking about a severely restricted "development mode" when they say they're going to open it up?
I'm confused...
(I'm new to Android rooting, so please forgive me if this is a dumb question...)
I haven't rooted... yet. Holding out to see what happens w/ 1.1. I'd prefer not to root and just get some basic apps on the device and not lose access to the B&N store. If I can side load a few key apps w/ 1.1, that will hold me off until the B&N Market place is launched Q1. Otherwise I will most likely root.
Am I missing something? I didn't see them say January anywhere in those threads. All I saw was them saying Q1 of 2011.
And this quote makes it sound like the update won't be useful to the average user.
"Within NOOKcolor 1.1 update, we have added "Developer Mode". This enabled approved 3rd party developers to use the Android SDK to test and develop applications on their NOOKcolor devices."
Approved 3rd Party Develepors. Sounds like the only people side loading apps may be those that are approved by B&N.
supersoulfly said:
"Within NOOKcolor 1.1 update, we have added "Developer Mode". This enabled approved 3rd party developers to use the Android SDK to test and develop applications on their NOOKcolor devices."
Approved 3rd Party Develepors. Sounds like the only people side loading apps may be those that are approved by B&N.
Click to expand...
Click to collapse
And us.
12345678
I must have missed it but where in that thread is there any mention or confirmation that 1.1 is this month?
I see nothing of the sort.
In regards to January, it looks like Ted_Patrick went back and edited his original response.
Re: Nook Color Rooting[ Edited ] 01-05-2011 10:24 AM - last edited on 01-05-2011 07:12 PM
It originally read:
"Within NOOKcolor 1.1. update(January), we have added...."
Now other responses on the subject of 1.1 by him have an "official" response of
"We cannot comment on OS update features or framework support at this time. When we have information to share, we will be very clear and set expectations clearly."
Looks like he may of spilled the beans a bit or been more forth coming w/ info than B&N liked.
jwigginton said:
I haven't rooted... yet. Holding out to see what happens w/ 1.1. I'd prefer not to root and just get some basic apps on the device and not lose access to the B&N store. If I can side load a few key apps w/ 1.1, that will hold me off until the B&N Market place is launched Q1. Otherwise I will most likely root.
Click to expand...
Click to collapse
I don't know who's been scaring you with witchcraft and vodoo, but here are a few facts:
(1) Rooting is very easy. If you're the kind of person who is OK with opening a command prompt and doing things like "listing directories" and "renaming/moving files" it's quick and painless. It also takes less than 5 minutes (probably about 2) to take your device back to stock.
(2) Rooting does very little to the device. The key is that it allows the user to change system files, something that B&N would prefer we didn't do. Several users root their NookColor (NC) and then scratch their heads because they see no obvious change.
(3) Package mods like autonooter only make a few system changes (aside from the several nice system apps they add), in particular, they allow you to sideload apps. Once you do that, you can reorganize the way your NC looks and performs, so that it handles like a vanilla Android device.
(4) Most importantly, ROOTING DOES VIRTUALLY NOTHING TO CHANGE THE B&N INTERFACE. All--I repeat--ALL the things your NC does out of the box, it still does after rooting. Same eReader. Same storefront. Same file browser. Same everything. And I'm all but certain the NC doesn't phone home and complain that it's been rooted. And if it did--since the bootloader isn't locked--I seriously doubt B&N would try to deny you a service. (The more likely scenario is that an OTA update would try to remove root.)
EDIT: several rooted users have lost access to 1-hour free reading in-store (http://forum.xda-developers.com/showthread.php?t=860830). So it's not true that nothing is lost. Sorry for overgeneralizing.
I can all but guarantee you that you'll be disappointed by the B&N store. I predict it will have very few developers, and very few "good" free apps. A better way of saying it is this: within 1 or 2 weeks of the B&N app store launching, most users will look at the Android Market, and say "Forget it, I want apps from the Market, not B&N."
-Matt
gadgetrants said:
I don't know who's been scaring you with witchcraft and vodoo, but here are a few facts:
(1) Rooting is very easy. If you're the kind of person who is OK with opening a command prompt and doing things like "listing directories" and "renaming/moving files" it's quick and painless. It also takes less than 5 minutes (probably about 2) to take your device back to stock.
(2) Rooting does very little to the device. The key is that it allows the user to change system files, something that B&N would prefer we didn't do. Several users root their NookColor (NC) and then scratch their heads because they see no obvious change.
(3) Package mods like autonooter only make a few system changes (aside from the several nice system apps they add), in particular, they allow you to sideload apps. Once you do that, you can reorganize the way your NC looks and performs, so that it handles like a vanilla Android device.
(4) Most importantly, ROOTING DOES VIRTUALLY NOTHING TO CHANGE THE B&N INTERFACE. All--I repeat--ALL the things your NC does out of the box, it still does after rooting. Same eReader. Same storefront. Same file browser. Same everything. And I'm all but certain the NC doesn't phone home and complain that it's been rooted. And if it did--since the bootloader isn't locked--I seriously doubt B&N would try to deny you a service. (The more likely scenario
is that an OTA update would try to remove root.)
I can all but guarantee you that you'll be disappointed by the B&N store. I predict it will have very few developers, and very few "good" free apps. A better way of saying it is this: within 1 or 2 weeks of the B&N app store launching, most users will look at the Android Market, and say "Forget it, I want apps from the Market, not B&N."
-Matt
Click to expand...
Click to collapse
Still, if you aren't comfortable then don't root. Things can still go wrong. Things can be fixed but you have to have the patience and not freak out when your device goes into a bootloop or just freezes, which I'm not saying it will but there is always that chance.
lopezpm said:
Still, if you aren't comfortable then don't root. Things can still go wrong. Things can be fixed but you have to have the patience and not freak out when your device goes into a bootloop or just freezes.
Click to expand...
Click to collapse
You know, I'm sorry for taking a bull-in-the-china-shop approach. Clearly I would never make it at a technical help desk. You're absolutely right and I should have noted that there's a minimum comfort level...the subtle comment about "OK with command-line editing" probably didn't get the point across.
-Matt
Not everything it does out of the box works after rooting...
gadgetrants said:
I don't know who's been scaring you with witchcraft and vodoo, but here are a few facts:
(1) Rooting is very easy. If you're the kind of person who is OK with opening a command prompt and doing things like "listing directories" and "renaming/moving files" it's quick and painless. It also takes less than 5 minutes (probably about 2) to take your device back to stock.
(2) Rooting does very little to the device. The key is that it allows the user to change system files, something that B&N would prefer we didn't do. Several users root their NookColor (NC) and then scratch their heads because they see no obvious change.
(3) Package mods like autonooter only make a few system changes (aside from the several nice system apps they add), in particular, they allow you to sideload apps. Once you do that, you can reorganize the way your NC looks and performs, so that it handles like a vanilla Android device.
(4) Most importantly, ROOTING DOES VIRTUALLY NOTHING TO CHANGE THE B&N INTERFACE. All--I repeat--ALL the things your NC does out of the box, it still does after rooting. Same eReader. Same storefront. Same file browser. Same everything. And I'm all but certain the NC doesn't phone home and complain that it's been rooted. And if it did--since the bootloader isn't locked--I seriously doubt B&N would try to deny you a service. (The more likely scenario
is that an OTA update would try to remove root.)
I can all but guarantee you that you'll be disappointed by the B&N store. I predict it will have very few developers, and very few "good" free apps. A better way of saying it is this: within 1 or 2 weeks of the B&N app store launching, most users will look at the Android Market, and say "Forget it, I want apps from the Market, not B&N."
-Matt
Click to expand...
Click to collapse
The entire reason I have waited to root at this point is the loss of the 1 hour free reading in store, and the instore promotions. None of these are available after you root.
It also seems as if only a couple of people are actively trying to address this, so I continue to wait to root.
rlkelley said:
The entire reason I have waited to root at this point is the loss of the 1 hour free reading in store, and the instore promotions. None of these are available after you root.
It also seems as if only a couple of people are actively trying to address this, so I continue to wait to root.
Click to expand...
Click to collapse
Thanks for the pointer. Didn't know that (will revise my post). My wife may kill me.
I read the first 4 pages of the thread (http://forum.xda-developers.com/showthread.php?t=860830), then skipped to the last. My naive impression is it affecting about 6 out of 10 owners. There are definitely several who are rooted, and not having a problem. I can totally understand not wanting to take the risk.
-Matt
notinterested said:
I must have missed it but where in that thread is there any mention or confirmation that 1.1 is this month?
I see nothing of the sort.
Click to expand...
Click to collapse
He tweeted about January as well (@__ted__):
"A serious bug in WiFi, a memory leak in browser, and overall tune-ups. 1.1 is coming up later in Jan! "
It was my understanding that you could not buy from the B&N store via your B&N account post-rooting. I'm not sure if I would be authorized to read the books I've purchased due to DRM on them. I've purchased some expensive reference books and don't want to lose access to them, or access to buy more.
I'm also uncertain these things work post-root:
Sharing, Quotes, etc
Lending books.
I'm may root at some point, very comfortable technically. No fear of rooting, just my preference at this point. If I had a microsd and reader, I'd probably done it by now just to experiment.
From reading through the threads, in regards to loading all the "extra stuff" it seems like a lot of... this works, but you need to go an change this or that, change the pixel density to display properly, youtube working, not working, gmail contacts syncing not syncing, this works, but.... you need to use this and then edit this, etc... maybe not everyone's user experience, but defintely some.
So to me, the device is working fine and not having to fiddle with anything to get it working properly. I know myself and if I root, I'll be loading launchers, applications, troubleshooting why this or that doesn't work properly and sounds a bit time consuming and hacking around a bit. I'm not looking for a new "hobby" of figuring out how to get things to run properly and smoothly as I expect from a finished product. I'm using a e-reader and would like some extra social, productivity, and games to pass the time.
Rooting, not rooting... not wrong, just different.
Greetings,
This is my first post here, so forgive me for posting in the general forum and not in the dev forums (I have to accumulate 10 posts to use the dev forums). I have a very important and worthwhile project that I'm hoping will interest a few devs here.
I am attempting to build a proof-of-concept for a very large educational institution that is considering implementation of ebook readers. Obviously, stock ebook readers are not up to what we need, and more robust tablets like the Galaxy Tab are cost prohibitive given the goal of distribution of these devices to tens of thousands of K-12 students. I don't want to be stuck with a single book distribution method, so I am looking for some standard Android flavor rather than a Nook-like interface.
So, here's my challenge to you. I would like to use the Nook Color (the $250 price point is perfect) to build a proof-of-concept low-end, semi-restricted Android tablet. I am looking for:
- Android 2.2
- Flash Support
- Ability to run:
- Dolphin Browser
- Regular Nook Android App
- Kindle App
- Google Book Reader App
- Adobe Reader App
- Some (undefined) Calculator App
- Stock Android Calendar App
- Stock Android Mail App
- Google Maps App
- Google Earth App
- Stock Android Gallery App or Equivalent
- Some (undefined) File Manager App
- Some (undefined) Note Taking App
I would also like the ability to load APK files (that we write) without the use of the Android Market. And . . . I need the final installation to *NOT* have root capability.
Anyone have a ROM to start this?
Also, while I'm somewhat familiar with rooting other Android devices, I'm not a developer and not a linux expert. I employ developers that have written a few Android apps, so they can handle the installation if necessary.
Any takers?
You can contact me off-list if you like at Dwayne at leeschools.net.
Thanks,
Dwayne
Wouldn't a $200 netbook be a far more usable tool to a student?
good thing you didn't post this in development.
once nook is updated to 2.2 this will basically all be possible with just root.
supposed to be released soon....
if you want a custom rom those will be around soon as well.
--edit--
i see you want this all without root. i don't believe that is possible. good luck though
There are specific reasons we are not considering netbooks for this project, beyond the scope of this discussion. For the purpose of this POC, we are only looking at touch-based slates.
I can't think of a way to fully disable root without someone being able to add it back. With that said would you be able to just delete the marketplace to make it "locked down" after installing everything? Possible disable super-level access as well?
I've not seen any confirmation that they are going to update to 2.2. I've only seen rumors to that effect. Do you have evidence to the contrary, because that would be great.
Additionally, the reason I'd like to involve the devs is because it is highly unlikely that B&N will release it with anything close to a stock 2.2 install. It will likely still require quite a bit of work to function normally. Hopefully I'm wrong on that account, but based on B&N's business model, I anticipate that they will do their best to prevent it from being used as a full tablet. They want to sell books. I don't think they want to sell devices without books. Not enough margin in the devices.
Perhaps I'm wrong related to their business model. I have approached B&N and requested an NDA to work with the Nook product team to see if they are interested in working together with us on a customized version. My feeling is that if they make very little on the device (with the goal of making the majority of their profit from content), they'll decline this offer.
MattJ951 said:
I can't think of a way to fully disable root without someone being able to add it back. With that said would you be able to just delete the marketplace to make it "locked down" after installing everything? Possible disable super-level access as well?
Click to expand...
Click to collapse
We could remove super user, but I'd also like to prevent users from killing services. I anticipate that we'll need some additional security apps that need to run full-time. One of our big challenges is that, by law, whenever we provide an Internet-capable device for students to take home, we are required to filter Internet. That's a huge task. On a PC, we an lock it down and force traffic through our filters from outside. From an Android device, we don't know how to handle that yet. We have a few approaches. I'm in discussion with M86 regarding an Android equivalent to their mobile client.
But . . . we have a lot more experience locking down a Windows or Mac PC than a phone OS. Most phone OSes are built from the perspective of a consumer, where the user is free to add/remove apps. We need a way to deal with that. Haven't gotten that far yet. The first order of business was to see if we can build our base functionality in a $250 device.
DwayneA said:
I've not seen any confirmation that they are going to update to 2.2. I've only seen rumors to that effect. Do you have evidence to the contrary, because that would be great.
Additionally, the reason I'd like to involve the devs is because it is highly unlikely that B&N will release it with anything close to a stock 2.2 install. It will likely still require quite a bit of work to function normally. Hopefully I'm wrong on that account, but based on B&N's business model, I anticipate that they will do their best to prevent it from being used as a full tablet. They want to sell books. I don't think they want to sell devices without books. Not enough margin in the devices.
Perhaps I'm wrong related to their business model. I have approached B&N and requested an NDA to work with the Nook product team to see if they are interested in working together with us on a customized version. My feeling is that if they make very little on the device (with the goal of making the majority of their profit from content), they'll decline this offer.
Click to expand...
Click to collapse
Dude, all of those hings are capable. Have you done any reading in this forum. Just get a nookie froyo 2.2 card set one up the way you want. uninstall super user and market. make lotsa copies of card and stick it in nook. If you really want you can also trash the firmware on the internal memory so it will not even book the stock nook firmware.
enjoy!
Consideration should be taken that rooting technically voids the manufacturer's warranty. Other than that, using the NookColor as a tablet is still a gamble in terms of getting a rock-solid and reliable device. Supporting the devices may be problematic.
Fortunately, the devs here are doing great work and I fully expect (hope) that it will be a rock-solid reliable device very soon.
You will probably also want to avoid booting from the microsd because they are easy to remove.
Filtering could be done with a VPN.
to avoid removal of micro sd, just put a little sugra on the break where the nook opens for the micro sd, sort of lieka warrenty sticker
If you need help. Let me know.
The Nook Color already has a Froyo image that can be installed. DSP currently doesn't work. That is responsible for video decoding not only for local files, but for Flash video as well.
Other than that, Flash will still run, but not on all occasions, and the rest of your requirements have already been accomplished (ie. apks can be installed and already exist on the Market or from the Internet).
You can install the Froyo image (it consists of a boot image and a system image) to your Nook easily, and afterward install all of the "G" apps with a quick copying of a folder.
Check here: http://forum.xda-developers.com/forumdisplay.php?f=864
- Do a little reading
- Possibly try installing Froyo on your memory card first.
- PM me if you need any guidance. I'm feeling pretty PRO at this after using adb all weekend to work with my Nook.
FYI: You can completely hose your internal installation and still be good (As long as you don't actually corrupt your memory physically). The Nook can always be booted off of a microSD card and restored to a fresh installation.
Edit: I just read some of your other posts. Just a thought: You could uninstall or disable the browser by default, thus not having to worry about Internet filtering. Later, users could still install apks from the sdcard (All that you have to do is tick a box in "Settings"). You can also do all of this without touching the stock rom. Of course you'd want to disable that from booting ever, so... after you were booted into your microSD card OS you could use adb to delete the content of the mmcblk0p1 (boot) partition. But I think that still might go against BN's warranty rules.
I understand the reasoning of wanting to lock it back down but if your students are capable of finding XDA (I'd imagine 1 or 2 of them is, at least) then that person would probably root the systems for anyone who was so inclined. I mean, B&N wasn't able to stop it, it's not likely that you would (without some sort of remote supervision app that could monitor and detect rooting).
gallahad2000 said:
I understand the reasoning of wanting to lock it back down but if your students are capable of finding XDA (I'd imagine 1 or 2 of them is, at least) then that person would probably root the systems for anyone who was so inclined. I mean, B&N wasn't able to stop it, it's not likely that you would (without some sort of remote supervision app that could monitor and detect rooting).
Click to expand...
Click to collapse
that was going to be my 2cts. A student would just have to pop in an sd card. And it would be a little unfair not giving student that right? And even then, they could always push something over via adb.
Have you looked at other options like the Archos line of Android tablets?
Otherwise, the SD Card install of Froyo works well - just superglue the opening
Why would any school district buy tablets with no warranty? Doesn't seem that feasible to me.
blackderbyhat said:
Why would any school district buy tablets with no warranty? Doesn't seem that feasible to me.
Click to expand...
Click to collapse
He's only looking for a proof of concept right now, and is trying to work with Barnes and Noble directly.
I forsee many broken nooks in our future.
Search as I might, I've found nothing to go by that is close to being up-to-date; either on the XDA forums or elsewhere. I am attempting to figure out how best to root my NC to get the most functionality out of it. So far, I believe CM7 may be the way to go with it but I'm wanting to be sure before rerooting. Is there been any chart compiled with information about the different available roms specifically geared for the NC with the pros/cons/comparisons of the attributes specific to each rom? I'm also looking at finding any rom "Gotchas" as well. And please, before it even begins... I am not asking for opinions/favorites. I am looking for the facts and nothing beyond that. I want to push my NC to its limits but stability is still part of the end goal.
Thanks!
To my knowledge, no, there is no such comparison, primarily because of the intensity of CM7 development for the NC. There are forked variants of CM7, mainly Phiremod and MIUI (I believe the only version for the NC is the one built on CM7), but otherwise there are only far less robust options (Honeycomb preview/test builds) and outright obsolete ones (Nookie Froyo).
The other option is to root stock with ManualNooter, which some people do prefer.
All of the above are having issues with the Market right now, requiring some rather annoying temporary workarounds (setting dpi to 160 and frequently clearing Market data). Another "gotcha" if you use B&N content is that the Nook app's Search button is unresponsive in CM7, meaning you have to set up a Search softkey in order to use it.
The last stable release of CM7 is also a bit out of date, and you would probably be better served by a recent nightly (I've seen issues reported with 177, but 176 is solid), incorporating features like deep sleep, a built-in boot menu, fastboot, compatibility with the Nook Tweaks app (overclocking, voltage stepping, enhanced audio gain, and USB host) and kernel updates from B&N's last update, among other things.
Appreciate the input... I've been reading a lot lately and your observations fall inline with most everything that I'm reading. I had been using ManualNooter but I wanted to gut the B&N ROM altogether. I've loaded CM7 and it is working well. Couple market glitches (Version not supported, No Netflix showing in market, etc.) but mostly its working well so I'll keep plugging away. I had to do the LCD Density change in order to get Kindle to install but; ahhh, the joy of modding.
Again, thanks for your help!
Netflix does work just fine if you google up an apk.
Taosaur said:
Netflix does work just fine if you google up an apk.
Click to expand...
Click to collapse
I didn't say that Netflix wasn't working, simply that it won't update from the market from my early Netflix version. I am able to use the older one but it keeps crying about wanting to update upon loading. I cancel and then watch movies. I've not watched a full movie yet in this way so I can't say yet if there are any issues beyond the "won't update via market" issue.
treat me like an idiot if these are obvious..
I want to put Samsung stock nougat on my rooted SM-T810, and I have some general questions. if all this info is gathered somewhere else, please point me there. maybe I used bad search terms?
1) for US, I use the XNZ country code, correct?
if there's an update thread already, consider this an apology for wasting your time. please stop reading now and point me to it. otherwise:
2) Use Odin 3.12, correct?
3) Can I just use twrp to update?
4) will I lose root?
5) if yes to above, could you please point me to a rooting guide (SM T810)
6) other than the ROM itself, what do I need?
yeah - so i'm an idiot. I see the 'no questions' posting now. guess I jumped the gun
Is your current s2 Tab working smoothly? If so, why risking an update?
why not? I like to play around and keep current. Besides, IMHO, Android s**** as an OS, still unable to do things Windows was doing in the early 90s. I keep hoping someday it will grow up... I know Android and Windows have different purposes, but until I can network at the OS rather than app level (built in), and until it is fully 'self-contained' and doesn't require a PC for changing OS versions (w/o 3rd party apps), etc., I'm going to consider it 'not ready for prime time'. Just my opinion.
"Keep it current" what does this mean?
You do realize that the lastest software versions often come with the most current bugs and issues at hand.
If you need to network, install Kali Linux, I'd suggest.
'keep it current' = keep all apps and the os to the most recent version possible
bugs: yeah, but it also comes with the latest features
Linux: on the tablet? there's a version? but that's sort of beside the point - Android lacks a functionality that's been in every other OS on the planet since at least the early 90s. it may be by intent, but it still ain't there, and it would sure make my life easier if I could map a drive from my nas and have it's contents available to all apps: music player, movie player, ebook reader. for work, I've used it to process data in the field using Octave. Getting the data on and off is always a pain - better if I could map a share and go from there.
not trying to argue - you asked, i'm elaborating. too much, maybe.
Keep all apps and the os to the most recent version possible. But what for?
Why trying desperately to fix a working car?
Updates eat storage and in most cases performance. Worse, introduce new bugs and so on.
I do not get this: update mania. Sure, it certainly assures that the Superclass can easily spy on every single user but besides that.. it makes no sense IMO.
Certainly, Android is Linux based after all. So yes, you could root your Tab and install Linux.
Drive access. That's already possible. You can connect an external SSD drive or HD drive via USB. Or NAS,
http://www.techrepublic.com/google-...o-help-you-connect-to-network-storage/?espv=1
I feel you. No arguing here either, just trying to understand your viewpoint.
just want a fully functional 'computer' where I can access files without having to use one app to copy the files over from the nas and another to use them. step one is the OS's responsibility, IMO. want access to network drives and otg drives to be identical to access I get on the internal memory.
and if you really want to get me going, start up on selinux, the "god i'm so afraid to go outside" solution. yeah - let's punish everyone because that guy over there is being bad. and lack of automatic root access? these are children's toys? unfortunately, my favorite ebook reader is only on android. as is the best music player I've found.
fun discussion, but I gotta get some work done
Msamp said:
just want a fully functional 'computer' where I can access files without having to use one app to copy the files over from the nas and another to use them. step one is the OS's responsibility, IMO. want access to network drives and otg drives to be identical to access I get on the internal memory.
and if you really want to get me going, start up on selinux, the "god i'm so afraid to go outside" solution. yeah - let's punish everyone because that guy over there is being bad. and lack of automatic root access? these are children's toys? unfortunately, my favorite ebook reader is only on android. as is the best music player I've found.
fun discussion, but I gotta get some work done
Click to expand...
Click to collapse
I guess you are not really understanding the role smartphones and tablets play in the computing world. They are more communications terminals designed to be usable without mice and keyboards rather than stand alone computers. Your recurring references to what computers could do in 1990 is a little off. All you had (at most) was windows 3.0. That did not include networking out of the box, but relied on device-specific drivers and utilities (i.e. Novell) to access a thin-net ethernet coax cable or IBM token ring network. If you want to get online, be prepared to use a serial terminal and a But I digress...
Android is not Windows. It is a cut down and specialized version Linux. Linux/Android is not a single monolithic OS like Windows. It does not do SMB out of the box, but needs a Samba client to do SMB to your windows-ish NAS. It does not try to be all things to all people, but rather gives you the basics and lets you, Joe User, add on the things to make it do what you want. In short they don't bloat it down with stuff only 10% of users will want to use.
To access your NAS, there are Samba (SMB) and ftp clients that let you do it. In fact I have a couple Android streamer boxes on my TVs around the house. They connect directly to my NAS video libraries and pull movies and other videos directly from there using a variety of protocols. Do I need to do that on my phone? No, but hey, I can install KODI on that phone and do just that. I can also put KODI on my windows box and do the same thing. But if I want to disconnect, I can copy these movies to my Tablet/Phone and play them any time I want off line. This is all things I would challenge you to do using Windows 3.0 in 1990 (don't even think of doing full touch screen support with Windows 3.x).
But well, if you really want your phone or tablet to work like Windows, you should run Windows on it
not '1990' - 'early nineties'. big difference. Win 3.1 (or WFW?) had an add-on, but still OS level tcp/ip stack
paragraph 2: I don't count real networking as an option. I should be able to access my ebooks on my nas usung ebookdroid, not have to move trhem to the tab using ESfilemanager THEN read them. I have a HUGE library of pdfs, movies, music, more than will fit on my 128 gig sd card (or a 256 g card for that matter), and i'd like access to the WHOLE THING from any appropriate app I choose. all the smb apps suck green worms, by the way.
I don't want to have to install a freakin client - it should be part of the os. imho, of course
btw: this discussion has become pointless. I have my preferences, you have yours. that's the way it should be. and as far as their 'role' goes: give them a bigger one - they're capable.
'bye
I totally understand your gripe. And I do wholeheartedly agree there should be a *root* toggle in the **Developer Option**.
But here is the thing, how are greedy conglomerates, and the gov puppets, supposed to spy on each and every single citizen if they just uninstall all spyware?
Moreover, most consumers are just too *untechy* and they would probably lose all their bank account, credit card and online shopping data to third parties and eventually blame the OEM. I smell lawsuits of the retard.
Auto updates are there for a reason. Control.
For instance, Samsung's new high-tech TVs record audio 24/7. Same for all these assistant devices.. Amazon Echo, Google Home etc. Seriously, 1984 isn't that far away anymore.
Msamp said:
treat me like an idiot if these are obvious..
I want to put Samsung stock nougat on my rooted SM-T810, and I have some general questions. if all this info is gathered somewhere else, please point me there. maybe I used bad search terms?
1) for US, I use the XNZ country code, correct?
if there's an update thread already, consider this an apology for wasting your time. please stop reading now and point me to it. otherwise:
2) Use Odin 3.12, correct?
3) Can I just use twrp to update?
4) will I lose root?
5) if yes to above, could you please point me to a rooting guide (SM T810)
6) other than the ROM itself, what do I need?
Click to expand...
Click to collapse
Use Odin AND the rom... i think you will lose root but you can always go back in twrp to install supersu.
I did something similar, i used Samsung Smart Switch to do an emergency reset on mine and it installed the latest firmware (nougat).
That will unroot and remove twrp.
I wouldn't (and didn't) reflash TWRP and root because you lose OTA updates, and right now there's some bugs in Nougat that , for me, were fixed in an OTA update. But once you flash with Smart Switch, you could always re-install TWRP and root again if you want.
Don't mind Niii4, he ranted about the same things in my thread and to others too...
8-31-21: My report on the death of this app for the NST is a little premature. See post #5, etc., for a "fix". It worked for the poster and it worked for me. It might work for you.
Don't shoot the messenger...
Sometime in late 2020 or early 2021 it became impossible to negotiate an initial login with the Kindle app (yes, even with the OTP they email you). I've checked the security certificates and they are fine. I've tried installing the app on newer devices, going all the way to Oreo. Same behavior. A logcat on the NST shows a failed SSL negotiation so it looks like the server just won't talk to the old app any longer--at least for an initial authorization. That's the very bad news.
There is a tiny bit of good news for those who already have the Kindle app installed and authorized. At least on my three devices it continues to function completely. You can still check out Overdrive Kindle books and send them to your device and the same book on different devices appears to sync. You can also sideload .mobi books and read those. The clock is, however, probably ticking.
I mention this as a warning for anyone who has a legacy Kindle installation and is thinking of doing major work on their device. If you uninstall or wipe out the Kindle app, it's gone for good. It may be possible to use something like Titanium Backup to restore the app. I was able to find all this out after a reset and then restore my NookManager backup and the app worked fine.
Edit: I have done a little experimenting and the app authorization token appears to include a lot about the device and system. So it's not possible to use Titanium Backup. I tried this on a FW 1.2.1 installation with a working copy of Kindle. Then I updated and rooted FW 1.2.2, installed the Kindle app and then restored a Titanium backup from the same device (but with FW 1.2.1). It failed to initialize, asking to register again. I've had success only in restoring a NookManager backup from the same device with the same FW, etc., and in cloning a device from a NookManager backup. This is not something I would necessarily recommend, but you might have your reasons. However, when I tried to correct the MAC address, this threw off the Kindle app token and it reverted to asking for registration again. So there's very little wiggle room for preserving a working installation if you have to do any significant changing.
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
In the defense of the NST I must say that recently saw on YouTube video someone put Alpine Linux on Kindle PW3. What am I trying to say is that older generation of this kind of devices suffer from same illness regardless of brand manufacturer pushing people to just abandon the legacy software on them and create their own custom made one tailored for their devices and their intended way of use.
If the SSL layer is somewhere in Android oh boy that might be harder cookie to bake from my point of view.
SJT75 said:
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
In the defense of the NST I must say that recently saw on YouTube video someone put Alpine Linux on Kindle PW3. What am I trying to say is that older generation of this kind of devices suffer from same illness regardless of brand manufacturer pushing people to just abandon the legacy software on them and create their own custom made one tailored for their devices and their intended way of use.
I
Click to expand...
Click to collapse
SJT75 said:
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
Click to expand...
Click to collapse
My understanding of the issues is very limited. I once happened into a discussion where it was stated that apps which need to communicate with external servers contain their own SSL certificate which has an expiration date. If so, apps like that just die a "natural" death.
It's actually amazing that there are some apps requiring logins that still work on the NST. Two that come to mind are ancient versions of Pandora and TuneIn Radio. I use both and they still perform flawlessly. For now.
Until today I didn't know what Pandora is but I am familiar with TuneIn radio app. Good to know that some of those apps is still working. Well it just had to be complicated with SSL/TLS hidden somewhere in Android layer. I totally understand why people like Android user friendly UI and apps availability. Still gamble with Java seems that didn't paid of regarding promised platform crossing ability.
So either porting to a new Android version which probably will not be very new (low RAM) or making custom Linux which is anything but user friendly?
Edit: Scratch that question about Linux and the app OP mentioned! I just realize that there is no Linux Kindle app. It could be used through Wine and such witchcraft but that is stupid way of doing things on this device. Better option is to use it on PC and then pass it on to NST using Calibre IMHO. SSL/TLS although remains as weak spot for the time being. Oh well... If that issue with certificates get somehow fixed maybe Kindle cloud reader from browser could reclaim at least part of functions of dedicated Kindle app.
For what its worth I recently got a NST and managed to get the kindle app running this morning. I upgraded to FW 1.2.2, rooted with Nook Manager, and installed the app with adb. The sticking point for me was that I had to go into my Amazon account and disable two-factor authentication. When I tried to log in with the app it still gave the bad password error, and Amazon still sent a text message with an OTP, and that let me log in. This same process DID NOT work if I had two-factor auth turned on in my Amazon account.
I don't understand why they still sent an OTP when two-factor auth is turned off, but they did, and it worked.
wrexroad said:
For what its worth I recently got a NST and managed to get the kindle app running this morning. I upgraded to FW 1.2.2, rooted with Nook Manager, and installed the app with adb. The sticking point for me was that I had to go into my Amazon account and disable two-factor authentication. When I tried to log in with the app it still gave the bad password error, and Amazon still sent a text message with an OTP, and that let me log in. This same process DID NOT work if I had two-factor auth turned on in my Amazon account.
I don't understand why they still sent an OTP when two-factor auth is turned off, but they did, and it worked.
Click to expand...
Click to collapse
Wow! This is very good news. I'll give it a try tomorrow on a fresh system and see if I can get it to work.
Did you by any chance go back and turn on the two-factor login and see if the app still connected after first initializing it?
nmyshkin said:
Wow! This is very good news. I'll give it a try tomorrow on a fresh system and see if I can get it to work.
Did you by any chance go back and turn on the two-factor login and see if the app still connected after first initializing it?
Click to expand...
Click to collapse
Yes, I should have mentioned that. I re-enabled two-factor and downloaded a book to test, everything worked fine. I'm currently using this (https://forum.xda-developers.com/t/app-eink-friendly-amazon-kindle-3-2-0-35.2024062/) version of the app, but I don't think it should matter much.
wrexroad said:
Yes, I should have mentioned that. I re-enabled two-factor and downloaded a book to test, everything worked fine. I'm currently using this (https://forum.xda-developers.com/t/app-eink-friendly-amazon-kindle-3-2-0-35.2024062/) version of the app, but I don't think it should matter much.
Click to expand...
Click to collapse
Excellent. As I expected based on legacy installs continuing to work, once the credentials are on the device, you're good to go whether you use single or two factor login after.
I had a password issue with Amazon awhile back and I'll bet that's where the problem originated. When I changed my password, authentication must have gone to two-factor. I need to check that, but I'm pretty sure that's it. What great news! Back to seamless library book checkout and download, all on the device!
BTW, the version of the app you mention is the only one that works (again!) on the NST.
Something is weird on the Amazon side right now. Even though two factor was turned off, they still sent the OTP. The only difference is that it actually worked when two-factor was disabled, but didn't work when it was enabled. Very strange.
wrexroad said:
Something is weird on the Amazon side right now. Even though two factor was turned off, they still sent the OTP. The only difference is that it actually worked when two-factor was disabled, but didn't work when it was enabled. Very strange.
Click to expand...
Click to collapse
Mmm... I'm glad you posted this before I started testing. I have two NSTs with working Kindle apps right now and I don't want to trash those while tracking down the "solution". I need to think about how I'm going to approach this.
OK, I think my last message was a little unclear.
What I meant was that with two-factor enabled you are supposed to be able to log in with a legacy device, have it give you a password error, receive an OTP via text or email, then use the OTP to actually log in. However, this does not work when two-factor is enabled.
What does work is first disabling two-factor auth, then trying to log in. You will still get a password error, they will still send you an OTP and the OTP will now let you log in and register the device.
This is what I meant when I said something was weird, when two-factor is disabled they shouldn't even be sending you an OTP. It's like disabling two-factor makes it work correctly, rather than turning it off.
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
wrexroad said:
OK, I think my last message was a little unclear.
What I meant was that with two-factor enabled you are supposed to be able to log in with a legacy device, have it give you a password error, receive an OTP via text or email, then use the OTP to actually log in. However, this does not work when two-factor is enabled.
What does work is first disabling two-factor auth, then trying to log in. You will still get a password error, they will still send you an OTP and the OTP will now let you log in and register the device.
This is what I meant when I said something was weird, when two-factor is disabled they shouldn't even be sending you an OTP. It's like disabling two-factor makes it work correctly, rather than turning it off.
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
Click to expand...
Click to collapse
OK, that's what I had hoped for and expected since my two working installs were made before my auth. got changed to two-factor. With really old apps you never quite know how server negotiation is going to evolve.
I hope to give it a try later today.
wrexroad said:
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
Click to expand...
Click to collapse
When I went to my Amazon account it seemed like 2SV was not enabled, by which I mean that clicking on "edit" for the settings generated an email which contained a link that took me to a page with a button that said "Get Started".
I didn't pursue this. I didn't see anything about turning it off--or should I have gone farther along?
That's odd, it does sound like it's not turned on... If you didn't have other devices that you were worried about I would say that you should just turn it on then try to log in. If that doesn't work, turn it off and try again. I think the risk is minimal, but clearly there is something different about your account, so it's up to you.
wrexroad said:
That's odd, it does sound like it's not turned on... If you didn't have other devices that you were worried about I would say that you should just turn it on then try to log in. If that doesn't work, turn it off and try again. I think the risk is minimal, but clearly there is something different about your account, so it's up to you.
Click to expand...
Click to collapse
Yeah, this is not working for me. I looked at the 2SV stuff again this morning and thought, "well, I'll just set it up and then disable it". Except I don't own a mobile phone (no, truly, just an emergency ancient (non-text message) device I keep in my glove compartment), and the QR thingy woud do me no good with the NST. So I'm cooked.
Despite apparently not having 2SV set up, now I can't even generate an OTP email when I try to login with the Kindle app. But my two working installations continue to function. Puzzlement.
Edit: I had a friend with a mobile phone help me out. So I finally got to where I could "disable" 2SV. But it made no difference. Still can't log in or even generate an OTP email by trying to log in. I'm glad this worked for you and I'd like to think it might work for others, but alas my account appears to be "special".
Edit-Edit: Yeehaw! It took a lot of fumbling for me with the unwieldy password I had to recreate in the near past, but by clearing the dalvik cache and making sure that 2SV was actually listed as "disabled" at Amazon, I was finally able to log in a new installation!!! Now I don't have to run a "clone" of another device on this particular NST. Thank you, @wrexroad, for taking the time to look into this and communicate your findings. One big step back from the brink for the Kindle app
That's awesome, I'm glad you got it running! In the future, if you need to get a password via text, you can use a temporary number here: https://sms24.me/en/countries/us/
Hey folks,
I just stumbled into this NST world and want to share my experience with the Kindle app. I'm on FW 1.2.2, and used NookManager to root. I replaced the certs file as recommended in another thread. Once I was ready to login, I enabled 2fa on my Amazon account in a browser. The instructions there clarified that I would need to use PASSWORD+OTP when registering my device. Previously I had tried only the OTP, or only my normal passwrord, but those failed. Appending the OTP to my password, I was able to login.
Hope that helps anyone else who has reached this point.