Related
I have owned several tablets, Augen ZT180, NC, GTAB etc.
Currently we have 2 NC in the house, one my wife has and uses 50% stock and the other 50% she boots off an SD card( shes not ready to commit)
the other is my son, his is a very happy 100% CM7
however, we just bought one for my mom (80+), mostly as an ereader, BUT with the ability to read emails and watch video of the boy and see pix.
Since it was a group by the rest of the family is not quite ready to let mom loose with Android, so its still stock 100%
However that being said there are somethings that I have been asked to do, to help prep it for Xmas that I dont have a clue on, and Im on a limited TIME budget.
I would love to install a file manager, for ease of navigation, no matter what I grab it either wont install or wont 'execute' (cant find it even though it says its installed).
Then of course there is the issue of installing ANYTHING else.
I LOVE XDA and have learned a GREAT deal here, so Im sure all my questions are SOMEWHERE but my searches havent found what I need. I guess most folks, boot from a card or go all in. Truth is with her arthritis my mom couldnt hold a card.
I REALLY like the NC, and think its a great device, if I "root" the NC will it boot as android or will it just be a 'rooted NC'? If I do have a rooted NC, what are the advantages?
I know most of you guys are busy writing new FW to make these tablets as awesome as they can be (and hats off), but if anyone can point me in the right direction I would be very greatful.
Thanks
J
The nook boots android whether you root it or not. Rooting just gives access to more of the features (a key one being market). I would probably set it to boot from the card and then load the apps and features you want her to use to the homescreen and maybe use parental controls to block the market, settings and anything else that she might get confused by.
You might consider MiUi from an SD card. It is a simple interface, reasonably large icons and runs well if you use a class 2 or 4 Sandisk card. It is an iPad-like interface, i.e. it doesn't use an app drawer. Everything is on the home screen(s).
I got my Geeksphone Peak a few days ago, and have already ran into some problems, that I believe some others may experience at some point in the future as well, when the device gets out to the public. I have therefore decided to make this thread to report issues and solutions, along with answering peoples questions about the phone.
First off, be aware of that the phone uses a standard size sim card, so if you plan to use it with a SIM card, you will have to get one of those old big SIM cards.
Second, you will without doubt want to debug your apps on the phone. The easiest way to do this, is by using the Firefox OS simulator v3, that allows you to push apps to the phone. To do this you will have to enable remote debugging on the phone, which was recently changed from enabled to disabled by default. Enable remote debugging by going to Settings -> Device information -> More information -> Developer. If you are using Linux, you will now have to add a value to the file /etc/udev/rules.d/51-android.rules: 'SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666", GROUP="plugdev"'. The idVendor ID is found using lsusb.
I do not know how to use remote debugging on Windows or Mac, and would be glad if someone would be able to contribute with this information. I will update this post when I discover more flaws and fixes
Hi, I wanted to know how the overall build quality is. I am thinking of ordering one myself.
chozyn said:
Hi, I wanted to know how the overall build quality is. I am thinking of ordering one myself.
Click to expand...
Click to collapse
I received mine yesterday. To me, the build quality is mediocre. The back is quite hard to remove to insert the battery and SIM card. When the back is removed, I saw "Engineered in Spain", "Made in P.R.C". The screen is average. Perhaps I'm pixel peeping, but I can feel the grid of pixels when viewing images on it. It's a developer phone, but I did expect a better build.
Certainly order one if you are a developer.
I got my Peak two days ago.
Materials and assembly is more or less what I expected. Clearly not a Sony but it is not so bad, in my view.
So far I have only connected via wifi, do not use the SIM yet. Once connected the first thing to do is upgrade. The process of downloading a 100MB and install the update was fast enough.
However, after using it for a couple of days I've noticed a lot of problems with connectivity. The worst is that sometimes fails to reconnect to wifi after unlock.
It is always very quick to complain lack of connection: is unable to access the sites for Mobile Twitter or Facebook, for example, as does access to regular Google. It's as if only Google respond fast enough to keep active navigation.
Well, this is a beta edition and it will sure get better, but today is all that I can bring on the Peak.
Regards!
Thanks songuke, Rackam el Roig. I appreciate the follow up!
t-mobile connectivity?
Either of you know how well this works on t-mobile? I see that t-mobile supports the 1900 band in my area, but I'm still not sure about how well tmo will work in general (as I do leave this city on occasion). I'd love to know. Also, it's a pity that it doesn't do HSPA+ so I'd like to know about the speed as well if possible. Thanks and you guys are lucky to have the phones. I've been watching the site like a hawk since day 1 and haven't managed to grab one.
Push to Device on Windows/Mac
I know on Windows, push to device is not supported in the simulator as of now, I am not 100% sure if it supported on Mac, but it is supported on Linux.
the simulator was just updated to version 3 and should have push to device for every OS now.
Impressed
I think that the hardware is pretty nice. It's super lightweight, almost too much so. The software is definitely beta quality - the email app doesn't automatically refresh, wifi turns off when the display turns off (to save power), no adjustable settings for still or video recording, etc.
I'm really enjoying it. No crashes or reboots in the day I've had it.
glystar said:
I think that the hardware is pretty nice. It's super lightweight, almost too much so. The software is definitely beta quality - the email app doesn't automatically refresh, wifi turns off when the display turns off (to save power), no adjustable settings for still or video recording, etc.
I'm really enjoying it. No crashes or reboots in the day I've had it.
Click to expand...
Click to collapse
And even when we need to reboot, it's fast enough on that.
I've been thinking of buying one, but it's always sold out.
Do you think it's usable as a lightweight daily driver? I was thinking of getting one for my parents, I could experiment a bit, and they just use phone calls / contacts / sms.
Hello, I have order the Geekshone Peak and it got the day also delivered. Unfortunately, I discovered that the Rear camera does not work. The Front Camera is working without problems.
Although it can be switched in the menu from the front camera to the rear camera, but the lens is then this is not activated.
Is this normal fault at the moment? If the Rear Camera not currently supported by the OS?
Thanks for answers und sorry for my bad english.
Best regards
not that mozilla is not a project to support, but i was wondering if there are some alternative os for this device ? gnu/linux or aosp based ?
Regards
rad30n said:
I've been thinking of buying one, but it's always sold out.
Do you think it's usable as a lightweight daily driver? I was thinking of getting one for my parents, I could experiment a bit, and they just use phone calls / contacts / sms.
Click to expand...
Click to collapse
I only own a Keon, but: These devices are for developers and geeks that don't get mad when something breaks, not your parents. Wait for a consumer device.
I have a Keon too, where I can find basic documentation to start hacking/upgrading my devices?
I am not a developer, only curious (maybe a bit geek too)... and I LOVE the Firefox OS paradigm!
android for peak ?
I was trying to find an android version that would run on it, but seems like the MSM8225 chip is not something you can get binaries for.
Any idea if its possible to compile an AOSP version that will run ?
:good::fingers-crossed:UPS just arrived with my new Geeksphone Peak :victory::victory::victory::victory:
_stefans_ said:
I was trying to find an android version that would run on it, but seems like the MSM8225 chip is not something you can get binaries for.
Any idea if its possible to compile an AOSP version that will run ?
Click to expand...
Click to collapse
It looks like the Peak is using the same chipset with HTC Desire X, which seems to have an alpha version of CM9:
http://forum.xda-developers.com/showthread.php?t=2265338
Can anyone enlighten me how to proceed from here?
That would be great to see CM9 or CM10 running on Peak as an alternative to the current Firefox OS build.
songuke said:
I received mine yesterday. To me, the build quality is mediocre. The back is quite hard to remove to insert the battery and SIM card. When the back is removed, I saw "Engineered in Spain", "Made in P.R.C". The screen is average. Perhaps I'm pixel peeping, but I can feel the grid of pixels when viewing images on it. It's a developer phone, but I did expect a better build.
Certainly order one if you are a developer.
Click to expand...
Click to collapse
Have you started working on an app yet? David Walsh (Mozilla) has written a really handy guide to runing any existing website into a Firefox Web App in just five minutes.
FYI, here are instructions on setting up the GeeksPhone for push to device on Windows/Linux/OSX: github.com/comoyo/Firefox-OS-training/blob/master/setup.md#pushing-to-geeksphone
Hi, I'm really sorry if this is considered cross posting, but I'm starting to get desperate here and really need help. I'm on a deadline and running out of time, I need to figure this out somehow and have been bashing away for almost 24 hours now.
My question is in this thread - and is the last post.
I am actively online and working on this. I'm starting to consider just reverting to stock from the recovery partition and then building everything from scratch, but if I can avoid that time vampire I would like to. Does anyone know what's going on, have some ideas, or anything?
Next step, I'm going to try the 1Gb 5Gb repartition that Dean originally developed. Though with my Nook broken already and my inability to restore it to a working state despite having a ton of perfectly fine Nan backups, I have doubts as to whether anything will change there.
I'll monitor both threads. Thanks in advance for any guidance/help.
Edit: Still plugging away, last steps mentioned above didn't work. Next steps: I'm reading Leaping Lar's partition fix thread and getting some ideas. am going to try:
Flash Partition > Boot to CWR
Format > Flash to CWR
Flash Dizzy Den's signed 4.1 zip > Boot to CWR
Flash my Registered Nan backup of Stock 4.1. > Boot to MMC, get a look around
I think I already did this, but left out the last step. Might work as it should restore my registration data instead of starting me from an unregistered account. If it seems worth trying at that stage, I will then flash my registered Nan of 1.4.2 and get a look at that.
Speculation: I just realized, I've been trying to restore a backup of a rooted 1.4.2 over an unregistered 1.4.1 - which is what I keep getting reverted to. I don't know if that matters, but my hope is if I flash my registered backup over what I'm reverted to, then build up to registered 1.4.2, that will help things... We'll see.
Failing all of this, I will try Leapin' Lar's partition repair.
I have finished reading the Partition thread I linked to above (where my original post is) and found that one other person reported my issue, almost to the T. His/Her user name is Blondie. Blondie seems to have quit without a fix, or if ever got a fix it was never posted. It was quite some time ago, but if any of those who helped him/her can remember if there was a fix would you let me know what it was?
Screw the original nook firmware. Go install CM7 Mirage ROM.
Rooting a stock nook is pointless. CM7 is better, faster, more efficient than stock and it comes rooted by default.
Now that your serial number is probably gone or corrupted in the /rom partition, you most likely cannot register your nook with the B&N servers, and that is probably why you can't install apps.
If you need a complete partition table wipe, follow this guide. http://forum.xda-developers.com/showthread.php?t=1759558
Next time you decide to mess around, be sure you backup your ROM and factory partition before doing anything.
sagirfahmid3 said:
Screw the original nook firmware. Go install CM7 Mirage ROM.
Rooting a stock nook is pointless. CM7 is better, faster, more efficient than stock and it comes rooted by default.
Now that your serial number is probably gone or corrupted in the /rom partition, you most likely cannot register your nook with the B&N servers, and that is probably why you can't install apps.
If you need a complete partition table wipe, follow this guide. http://forum.xda-developers.com/showthread.php?t=1759558
Next time you decide to mess around, be sure you backup your ROM and factory partition before doing anything.
Click to expand...
Click to collapse
I do have backups of everything. As I said above, they aren't wholly functional.
I never said I was completely unable to install apps, or that I couldn't register with B&N. I can register fine, and in some scenarios I can indeed download my apps just fine, just not if I try and restore a MN Nan backup. That is not because of a missing SN but because of a registration issue that can be caused by the MN process - otherwise I would not be able to download them at all in any scenario.
Also, if you know the MN process you know my factory partition is intact. Perhaps the partitioning messed with it a little, I'm not sure - but nowhere did I say I have yet tried to reset to stock from the factory partition, so we have no real way of knowing yet.
I understand that my OP is starting to get tl;dr because I don't want to double-post, but actually reading what has been done so far and reading the post at the original thread I linked to might be more useful in trying to give people advice. A little less snark would be useful too, I am not a n00b at this by a long shot and talking down to people tends to get hackles up instead of being productive - especially when you clearly haven't read their thread - as an example, if you had read it, you would have seen I already know about Leapin' Lar's partition fix and it's one of the next things I plan to try..
On the other hand, I may take your suggestion about installing CM7 Mirage. Honestly, I had my reasons for not doing that in the past, but those reasons are largely moot today. I will get a look at the thread. Thank you for the suggestion.
You're right, I apologize for not reading thoroughly. I had a derp moment.
No worries Sagirfahmid, I owe you an apology too. I'm sorry to have jumped on you, I am a little bit... stressed, and tired. Not that it's any great excuse. I need to take my own advice about talking to people. Sorry.
And fwiw, I believe you are right and the original partition did mess with the factory partitions, I've just been avoiding facing it. I really ought to get off the fence and run the repair and then follow Dean's guide to using fdisk on the emmc, but I'm getting OCD about trying every other thing first - even down to considering a flat reset to factory and rebuild from scratch. Stupid, I know.
Thing is, there is at least one other person out there who had this exact problem, and it didn't sound like her issue ended up being a corrupt partition as the partition repair didn't help her. Unless it was too corrupted. I know there were a lot of people running the same system as me, and it was very stable. Someone besides me and one other person has to know what this is and how to deal with it. That's what I'm hoping anyway. LOL
And seriously, thank you again for the reminder that there are other options out there that might better suit me now. The more I read the more I think if I can just reset the darned thing to a fully working state, I may well just do an SD CM10... or should I just stick with Mirage? Is there an advantage to Mirage over 10.2?
Yes definitely. It's faster--that's the most obvious advantage. (I disabled all the fancy animations and removed a lot of useless system apps like the phone, contacts, calendar, camera, and GPS app via adb).
Also, CM7 Mirage has USB host mode, so if you get a male microUSB to female standard USB port, it is very possible to use a keyboard or mouse, or a flashdrive or harddrive (if you get a powered hub). AFAIK, the max current it can supply without a powered hub is 100mA (enough for a flashdrive or keyboard/mouse that isn't too fancy--skip the ones with LEDs; each LED uses around 15mA).
Oh yeah, CM10 runs in phone UI (there's an extra bar on top taking up space).
In CM7, there's only 1 bar, so you have a bigger area on the screen. Of course, there is a patch to get CM10 into tablet mode, but I don't like all the hassle.
On CM7, you can overclock the CPU to 1.2GHz, but on CM10, it's limited to 1.1GHz AFAIK.
=====================================================
Right now, I'm hoping to get Debian ARM natively installed on the Nook Color. I've been making progress thanks to the devs and users here. Android is still required, but it will be on top (instead of the other way around, which is Android on top and Debian chrooted). SInce they'll be using the same kernel, I think I can get Debian to use the Nook Color's USB port to connect devices like printers or scanners (that would be so awesome...).
If you're interested in running full blown Debian on the NC, and assuming that you are able to fix yours, you can check out this thread: http://forum.xda-developers.com/showthread.php?t=2422518
Solved
Sorry for the double post. Need to separate this from the wall o text above. Problem is solved and since I never did find a spelled out definite answer while I was reading the last 2 days, I want to post it here where someone who might be looking in the future might easily find it.
To reiterate the problem concisely for those who don't have time for the diatribe above:
My device is a Green dot Nook Color:
* Running a stable Manual Nooter 5.08.20 over a Stock B&N 1.4.2 ROM, and using > This < method to block OTA Updates - basically use a SQLite Editor for Andriod to modify the fota mode in the nook's registry.
I recently started getting the Low Memory message asking me to please archive some of my apps to SD. Am about to go on a long trip abroad and I not only needed what apps I had but also need a couple more. Solution: Repartition the Data and Media partitions.
Full backups: have a whole slew of backed up NC B&N Update zips, Flashable updates created by several awesome people here, and step-by step Nan Backups of every single time I have re-rooted my device after a B&N Update - signed and registered stock configs, roots and final images, and finally a whole store of dated backups of my Tibu backups off of my SD card.
So, I repartition following steps exactly.
* At first reboot, CWR freezes on load. This makes me thing something went horribly wrong.
* Reboot again, everything seems to Format fine, reboot into Nook
* Unlike most people, my nook has reverted to an unregistered stock 1.4.1, no root.
* Flash my latest Nan-backup of my rooted NC, doesn't take properly and B&N is a mess because (duh) I didn't register it before flashing - But I shouldn't have needed to because all of those settings were in my Nan Backup. Okayyyy... weird.
* Flash back to a Registered stock NC nan backup of 1.4.2 since that was the last version I used. I was able to DL books and read them, and could DL apps - but my apps couldn't install at all and there were a couple of new B&N Apps that were stuck in a DL/Install loop too. Hm.
* Flash an earlier root Nan over that. Now my Nook can't download anything, I get an error message that it cannot execute. Lovely.
* Bash around in this fashion trying to make it work, occasionally trying different partition schemes in the process, while reading every thread I can find on the subject of what issues I'm having.
I begin to suspect that my partitions might be all messed up, especially considering the original freeze from CWR, but have no real way to check that and don't want to give up, so I post in the instruction thread and later here to see if anyone has any guidance or knows what this is.
A whole slew of people have endorsed this method and had no problems.
A few people had some problems, but only one user has reported exactly my problem off of the exact build I was running, no less. (1st link is that user's first post and 2nd is the page where her posts begin). However, that thread ended with no real answer - or so I thought.
At once point before the issue ended with no further response from the poster with the issues, Leapinlar (who had been assisting her, or at least trying to) tells her that if his Partition Repair didn't solve anything, then it likely wasn't the problem. If she cannot get her B&N Apps to DL & Install, then it's most likely the version of the B&N Stock that she is on and she needs to flash to the most recent - he even points her to a signed CWR Flashable one that he created for 1.4.3. She argues that can't be the issue - and I get that, because the apps installed and worked before in 1.4.1 right? So why all of a not now simply because she's back on 1.4.1 again?
I don't know why B&N would have made it so that you can't install any older apps on your device even though they installed on older ROM versions, forcing people to move up to 1.4.3, but it appears to me that this is exactly the case and Leapinlar is once again correct.
Took me a long time to internalize that and have it click. After running his Partition Repair with the same results as her, I left it on a registered 1.4.1 Stock, put the NC down and stepped away for a while to do other things. when I came back I was fixated on what Leapinlar said about flashing to a newer version of B&N Stock. So I did. And when that didn't really fix it I flashed up to the next ans last version, 1.4.3.
Hallelujah, problem solved!
For my own apps to download, I had to wait for a couple of new ones sent to Nooks from B&N for version 1.4.3 to download and install - and they were not able to do that on earlier versions. I propose that their inability to install was what was blocking my other apps. but it could be that the others were also made version specific once B&N stopped making NCs in favor of HD's and the Tablet, and released the final update.
Regardless, that is the final answer. If you are on MN and repartition, and then find when you boot you are taken to unregistered stock, and upon registering you can access your books but your apps will not install after downloading and you have a couple of new ones that seem stuck at dlownload and install, all you need to do is Update your NC to the final release, 1.4.3, and the re-root. I think you will need to re-root from scratch, unless maybe your last root backup was from 1.4.3 - which mine was not.
Next dilemma: Stick with root or start running a CM ROM from SD...
I'm a cheapskate, that's the truth. I am a geek, I want to do **** with my devices and I don't care if I end up bricking them so long as there are ways to recover. I also care about my privacy. I don't stick with the stock firmware because:
1. B&N wants you to REGISTER with your CREDIT CARD to be able to actually USE the Nook Color. Why the hell?
2. B&N possibly has BACK DOORS to your Nook Color. They might DRM lock apps or something. They can obviously force updates onto their users unless they root. They might also decide it's time to brick your tablet if they wanted, so you would go buy another one (yes, this is more of a conspiracy theory, but hey, if they can force updates, they surely can also do this).
3. B&N's custom Android is crippled unless you root. You can't use the 5GBs of space. Why the hell not?
etc etc...there are more reasons I don't stick with any stock firmware, be it for a tablet or phone.
(I use Debian on my computer most of the time now because Windows is a piece of crap. You can't do whatever you want on it, except game. Did I mention the useless startup services and apps you need, especially antivirus, for Windows to function without worries of getting a keylogger or some nasty virus? Valve has made Steam for Linux very usable, and I rarely use Windows for gaming now. Linux is tons faster, and I can do almost anything on it).
Have you ever used a T-Mobile smartphone? the apps that come installed are numerous! It makes me want to puke every time I use a stock Android phone from a phone company. I like and want my devices to only contain the apps I want. That means NO BACKDOORS, NO FISHY BACKGROUND PROCESSES, NO **** APPS, NO RESTRICTIONS.
======================================================
Backup the documents and whatever you have on your B&N firmware. Install CM7.2 Mirage onto INTERNAL SD card.
Stop being a wuss :silly: and start enjoying a better Android experience.
sagirfahmid3 said:
I'm a cheapskate, that's the truth. I am a geek, I want to do **** with my devices and I don't care if I end up bricking them so long as there are ways to recover. I also care about my privacy. I don't stick with the stock firmware because....
Click to expand...
Click to collapse
I completely understand! I have many of the same concerns and make workarounds and otherwise try to frustrate the usual 'Big Brother' tactic that are becoming so prevalent. I don't think you've gone into the realm of conspiracy theory at all, what you're talking about is a long term goal I think. Think of the marketing and capital profit possibilities of that kind of control over a still largely unregulated market - 'largely unregulated' because the technologies and the possibilities they allow are evolving so quickly.
I also am a 'computer geek', prefer control of my own devices and am very strict about personal security. So then why does B&N have my personal data? Largely because they had it far earlier than there was ever a blip on the tech radar of 'e-readers'. I'm also incredibly bookish and there haven't been a whole lot of B&N in my region, but I prefer their company as a book retailer, so I was a member that had begun ordering from them online as soon as they had a website to order from. So, it wasn't a huge loss for me to keep the stock and use it as intended. here are some things about this that do grate with me, yes, but they wouldn't have lost my data history anyway, so wth, I might as well get a really elegant e-reader interface from a company I mostly like and support. This is definitely not a situation that applies for everyone, I know.
I use windows on a secondary boot partition and funnily enough, largely for gaming. I also use it on a work laptop because I have to. I run Suse most of the time, myself.
As far as DRM, it' something we need to fight in the courts and through making our own backups for experimentation, and that's all I can really say.
When I bought my NC over two years ago, tablets were still pretty uncommon and e-ink readers all the rage. I splurged on this even though I was still using a flip phone because I felt it would serve multi needs well:
a) The need for an e-reader (I travel at least 1ce a year and I read a lot while traveling. Books are HEAVY! and I'm getting oilder...)
b) The desire for an e-reader that could read color and comics - so I could DL comics and fan creations and manga as well as books on the same device - and one that isn't an Apple (I dislike Apple as much as I dislike MS).
c) The desire to have a good interface in a size that is more readable than most phones on the market, to surf the web on or read the above during my long commutes.
d) The desire to have all of the above in one item that would also not tie me to a single seller - in other words I also wanted to run the Kindle App and Google books.
At the time, Kindle Fire had not been released and the next best machine (actually, tied as of the time I bought this nook) was an iPad. Other tablets out there were more expensive and glitchy and without that quality - some didn't even expect to ever update their android ROM. There was nothing on the market close to the NC in that price range - and I knew I could root it or otherwise replace the original ROM if I didn't like it, to do what I wanted, and essentially never brick it!
I chose MN over CM or Nightlies because I didn't have to mess with the factory partition at all or ever worry about replacing it, and it let me use my nook directly from system in a two-sided boot that had a tablet on one end and a Nook on the other. Very neat. I got the 3 yr warranty when I bought it because at that time they stated that you could return the NC within that time for a lower price on the next new thing. I plan to use that, so I wanted the original factory partition intact.
There are only two things today that would keep me from running a CM install or SD right now. The most important of those two is Battery Life.
The trip I'm about to go on is to India from the east coast of the US. We'll be gone about a month and my NC/Rooted or flashed tablet will be my ONLY mobile device. I need something stable, and that if I am not already familiar with it will be fairly intuitive, and most important - Good Battery Life. As far as I know, the CM ROMs for NC are energy hogs - is that still the case? We will have a lot of devices to try and keep charged, one plug adapter, and the NC will have a central role in our keeping in touch with family and friends. We we go for a day without a charge but with about 8 hours of use including wifi time on a MN root, I know I will still have enough charge the next day till we get to the next location where we can try and charge everything.
My other concern is more about running apps and what apps will work with the setup I'm planning - which I already know would work on my NC had I not hit the "Low Memory" wall and started all of this.
I am still interested in running CM, can you point me to info on these? For the second, I need to link to Canon Image Gateway wirelessly and also a Bloggie. I love that CM7 can run a USB interface! That's a huge advantage that I could use!
Even if I don't use it for this trip, I may change it when I get back to a CM7 sd boot to play with till I'm used to it. Also, I am rooting a NC for a Niece before I leave, and I think I'm going to change tactics and put CM on it instead.
As to smartphones... LOL. I still have a pay-as-you-go flip phone, wanna talk about being cheap and having security paranoia? XD Seriously, I spend a lot on my computers - which I prefer to build - and spent a lot on my tablet back when I bought it and when I replace it will consider carefully and spend on that again. =) Smartphones? I will get one eventually, it's a matter of time, but I'm holding out as long as I can. LOL
...I need something stable, and that if I am not already familiar with it will be fairly intuitive, and most important - Good Battery Life. As far as I know, the CM ROMs for NC are energy hogs - is that still the case?
Click to expand...
Click to collapse
Nah, CM ROMs have great battery life these days. I get 10 hours on my Nook Tablet (CM10, 4700mAH battery AFAIK); 8 hours on my Nook Color (CM7, 4000mAH battery. Obviously, it's going to have a slightly lower battery life). Also, keep in mind the li-ion battery is almost a year older than the Nook Tablet, so it has a decreased charge capacity. Li-ion's have a lifespan of 3 to 5 years--after than, you're gonna get crappy runtime on battery. Good news is li-ions are very recycle-able and non-toxic. I think most major electronics stores accept li-ions for free.
The only issue with stability is that, if you have wi-fi set to "always on" in CM7, sometimes you'll get a SOD (screen of death) after an extended period of sleep. Basically, your screen will fail to turn on--you must force power off and restart the NC. The guaranteed workaround is to set the wi-fi setting to "only when screen is on." You can safely overclock your CPU to 1GHz (+200MHz past stock 800MHz) guaranteed, and 1.2GHz almost guaranteed (I have mine at 1.2GHz, no freezes or crashes at all, and I run Debian chrooted in it currently, which takes a lot of power).
My other concern is more about running apps and what apps will work with the setup I'm planning - which I already know would work on my NC had I not hit the "Low Memory" wall and started all of this.
Click to expand...
Click to collapse
All CM builds can transfer apps' storage location to the external microSD if you wish. I have all my games and non-essential apps on my 32GB class 10 microSD, both on my NC and NT. Again, don't forget, the CM7 build for NC has USB host mode (so if you were really crazy, you could possibly plug in a 3TB+ mechanical harddrive, with a powered hub of course). Don't forget, the Nook Color also has bluetooth (which isn't there on B&N software). I have successfully transferred files between my netbook and my NC via bluetooth (but you have to be within 1 to 2 feet distance lol, unless you tear apart the NC and mod an antenna or something). You can also use an external bluetooth GPS receiver and bluetooth headset. Go look on the NC accessories thread if interested.
Even if I don't use it for this trip, I may change it when I get back to a CM7 sd boot to play with till I'm used to it. Also, I am rooting a NC for a Niece before I leave, and I think I'm going to change tactics and put CM on it instead.
Click to expand...
Click to collapse
Good idea. Install CM7 on your niece's NC (INTERNALLY :silly: ) and see how you like it. I guarantee you'll like it, and so will she. Since you messed with the partitions, I would suggest you visit the CM7.2 Mirage thread and post if the changes in partition sizes should make any problems with flashing.
Thank you for all this great info! I had read about the SOD issue, but I usually keep my wifi off when not using it, so I'm not too worried about that - it helps battery life some too. Interesting, I hadn't realized lion batts had that limited a lifespan. I haven't noticed a whole lot of change in my own NC's life, but to be honest I haven't looked either. I should.
Regardless, great to know CM is better at battery life.
sagirfahmid3 said:
I have all my games and non-essential apps on my 32GB class 10 microSD, both on my NC and NT.
Click to expand...
Click to collapse
Actually, that brings up the issue of class 2 vs class 10 cards and stability. There are a few threads that have benchmarked SD cards for running CM ROMS and have found the best and most stable - especially for large cards - is a 16 Gb Cl2 SanDisk... it looked by recent discussions that this is still the case, have you noticed this at all? My card is also Cl10, and as of now I think I would want to run CM off of an SD, at least until I'm used to it.
Turns out I didn't mess with my partitions after all. Gotta love computer systems! LOL Turns out the issue was version of stock I was running, and only that. I re-registered, updated to 4.3 stock and all is fine. You would think I would learn one day to read, step away and consider, instead of banging my head against a wall repeatedly. I should have figured it out much sooner, Leapinlar basically spelled it out for the other member who had this problem. And it completely explains the issues I had too. I may end up messing with them correctly again though.
I did not know the NC ended up having a blue tooth after all! I remember the speculation but the teardowns had only begun then and I never followed up on them. Now that IS interesting!
My Niece's on the other hand does have a corrupted partition, but from something she did to it. I think I will flash CM to the emmc, nice idea!
I posted a while ago about the GPS failing to find even a single satellite. I got no responses, just a redirect to this forum. Since then I have searched and searched but no one has a solution to this common problem. I watched a video about cleaning the antenna contacts and performed this cleaning - no help. I have tried numerous apps that are supposed to help - no help. I took the tablet out of its case - no help. I even set the tablet out in the backyard for 45 minutes with a GPS app running as was suggested by someone - no help. I can't find anything at all about updating or re-installing GPS drivers or firmware so i don't know if that is even an option, but if there is a way to do this I would sure like help trying that. I have Titanium backups from before the GPS outage but I don't know which ones control the GPS.
It is as though this is a taboo subject and no one wants to even talk about it, but I did see that LOTS of people are having the same problem. Doesn't anyone have a solid solution short of just buying a new tablet? The GPS worked on a flight from TX to TN last March but never worked again after that. Could something on that flight have jammed or disabled my GPS?
If anyone has a solid solution based on actual resolution of this same problem, a lot of people would appreciate knowing about it.
Thank you.
Oooh i luv a good conspiracy! xD
Although i don't think taboo has any thing to do with it, now, if we were talking about dwarf elephants,sodomy and juggling then that would be troubling! But i think the empire is too busy tripping over the trump disaster to jam your gps. xD
okay, start by cycling through your back ups and find the one that worked, though i don't know much about titanium backup. It would have been smarter to use an actual recovery to make you backups.
The reason most common for not finding an answer or even a lead to one is insufficient data.
I have a tab4 and gps doesn't work, is literally nothing to go on.
What OS and/or firmware were/are you running? Did you install a custom kernel? Did you modify your OS with questionable applications or modifications that came at a cost or broke something?
What tab 4 is your tab 4? there are about 11-16 of them. Specifying the 8.0 is still not good enough.
It is interesting that you got some function on a flight. That's definitely worth a ? . I don't think a "jamming device" would fry your gps though.
I would say that you should first restore your tab back to cherry, meaning the original state you purchased/recieved it in and walk your mod process forward. Take notes and get logs.
m
Moonbutt74, thanks for responding.
My Tab 4 8.0 is model SM-T330NU
It's rooted & has several of the nice apps that can be used on rooted devices. Nothing was added between the time the GPS worked and when I noticed it not working. I am ALMOST certain of that. If there were a way to check logs for changes maybe I could get a clue - hadn't thought of that 'till now. Do you know how to do that? I suppose restoration to original state may end up being necessary, but I would sure like to avoid that. Everything else works just as I like it except for the fact that Google is still spying on me. There's no stable custom ROM yet as far as I can tell.
Yes, GPS worked fine on several commercial flights. It's fun seeing things on the ground and seeing what they are on the map + knowing speed and ETA.
O,
okay that's the main question, in -flight i guess your "line of sight" to gps satellites is unhindered, if it's anything like satellite tv service, then what's you situation on ground? Meaning canopy, and cloud cover. Back up your full current rom through recovery to external sd card. And then revert your tab to it's factory state. If you haven't modified the contents of your system directory after rooting then after doing factory reset while in recovery should put you back to your initial state.
Logging,
if you don't know how to set up adb there are plenty of threads dedicated to the subject, get that set up.
once your tab is cherry, get it connected to your pc abd run adb shell
once in adb shell run logcat -c to clear your log
start a gps related function or app
run logcat without any arguments for a "live" logcat
You have a huge log to go through , but go through every line.
You'll get the idea of how to read the log as you go.
We know that as of the LP 5.1.1 update to the sm-t330nu that samsung tried to disable ir blaster, so who knows?
I didn't know the wifi variants had gps.
m
moonbutt74 said:
O,
okay that's the main question, in -flight i guess your "line of sight" to gps satellites is unhindered, if it's anything like satellite tv service, then what's you situation on ground? Meaning canopy, and cloud cover. Back up your full current rom through recovery to external sd card. And then revert your tab to it's factory state. If you haven't modified the contents of your system directory after rooting then after doing factory reset while in recovery should put you back to your initial state.
Logging,
if you don't know how to set up adb there are plenty of threads dedicated to the subject, get that set up.
once your tab is cherry, get it connected to your pc abd run adb shell
once in adb shell run logcat -c to clear your log
start a gps related function or app
run logcat without any arguments for a "live" logcat
You have a huge log to go through , but go through every line.
You'll get the idea of how to read the log as you go.
We know that as of the LP 5.1.1 update to the sm-t330nu that samsung tried to disable ir blaster, so who knows?
I didn't know the wifi variants had gps.
m
Click to expand...
Click to collapse
I have posted this in a new thread, but I'll tell you the short version: My Allow Mock Locations was disabled in Settings/General/Developer options/Allow mock locations...). When I enabled this my GPS started working. Such a simple thing but a total odyssey to find out about it. OB
I have what I needed, thanks!
Hi, I'm wondering if someone with a Le Pro3, either the CN or US model (or both) could please provide me with the output for dmesg and logcat.
Pre-requisites:
have adb installed and working for your device
Make sure adb debugging is on for your device, and your computer recognizes your device, and is authenticated for your device. (I don't know EUI, I've only ever dealt with western AOSP/CAF style roms, you'll have to understand and manage this all yourself).
PLEASE don't type the commands from memory, they have case sensitive options. Please copy and paste them. Thank you.
The following commands need to be executed shortly after reboots. Please don't run them if the device has been on longer than a minute. In fact, please don't stray far from the procedure, please.
Reboot device
Once booted run "adb shell dmesg > dmesg.txt"
Run "adb shell cat /proc/partitions > partitions.txt"
Run "adb shell df > df.txt"
Run "adb shell df -P > df-P.txt"
Run "adb shell mount > mount.txt"
Reboot the device and perform the next adb step once it's started to boot
run "adb logcat > logcat.txt"
Press "CTRL-C" to stop logging about 30 seconds after the device has settled and connected itself to the cellular network
Reboot the device and run the following once it's started booting back up
run "adb logcat -b radio > logcat-radio.txt"
Press "CTRL-C" to stop logging about 30 seconds after the device has settled and connected itself to the cellular network
Now, for some root-required tidbits (these commands could actually be dangerous!!! they will be running as root, please be very careful, you've been warned): You have two ways you can do this:
Run "adb root" to put adb in an automatic root mode (this requires that you have root and allow adb commands to be run as root)
Run "adb shell ls -la /dev/block/bootdevice/by-name > by-name.txt"
Run "adb shell ls -la /dev/block/bootdevice/by-num > by-num.txt"
Please check the files to verify that the contents are not an error. The other method, if switching adb to root mode doesn't work, would be to:
Run "adb shell"
Run "su" to put your shell into root mode, NOTE: BE VERY CAREFUL HERE (this requires that you have root and allow adb commands to be run as root)
Run "adb shell ls -la /dev/block/bootdevice/by-name" and then copy/paste the output into a file named "by-name.txt"
Run "adb shell ls -la /dev/block/bootdevice/by-num" and then copy/paste the output into a file named "by-num.txt"
Finally, if you are simply not able to achieve root on your device (either in general, or just for ADB), both of these tasks SHOULD be possible when you're booted into the TWRP recovery. If you don't have TWRP installed, then don't worry about it. I'm just assuming you do.
Note: None of these commands will produce empty files. If you get empty files, something went wrong. If only a few are empty and you can't seem to get them working properly, just send me what you do get.
Once you've done these things, zip up the files and send them to me in a private message. You don't want these posted here unless you want people knowing your phone number. The text files, especially for the logcat and radio output will be large, but they should compress down to something quite reasonable. Also, please make sure to include your model number so I know which I'm working with. Thanks much.
Thanks.
I can do that when I'm out from work in around 6 hours. For what exactly u need it? Just curious.
secXces_debaki said:
I can do that when I'm out from work in around 6 hours. For what exactly u need it? Just curious.
Click to expand...
Click to collapse
My own curiosity... Maybe put some of the info in Christmas cards, you know how it goes.
dr4stic said:
My own curiosity... Maybe put some of the info in Christmas cards, you know how it goes.
Click to expand...
Click to collapse
If my girl let me work on my phone I will send u a pm.
Was yesterday on the phone trying to build a rom, but always loose my baseband.. Lol. So she's a bit angry that I am to much on the phone ^^
I do my best sir.
secXces_debaki said:
If my girl let me work on my phone I will send u a pm.
Was yesterday on the phone trying to build a rom, but always loose my baseband.. Lol. So she's a bit angry that I am to much on the phone ^^
I do my best sir.
Click to expand...
Click to collapse
Well, don't get yourself into any trouble. I'm not in the business of ending relationships None of the commands modify anything, they just read information and dump it into a file. Other than rebooting, your device won't need to go offline. Also, if you HAVE modified your device in terms of ROM or whatever, please include a list of your mods or whatever in the message you send me with the text files zip.
PS> I've visited your area, or at least the one listed with your profile on XDA. It's a beautiful place. If I could get a visa worked out, it's on my list of places in europe I'd love to move to, possibly in retirement
U are planing to get one x720/7?
There are some way beautiful places around in Germany.
Can u maybe help me with my meta-inf?
secXces_debaki said:
U are planing to get one x720/7?
Click to expand...
Click to collapse
I'm giving it some very serious thought. I'm in the US and the x727 will be on sale on wednesday at US$300, which is very compelling for a device with an msm8996pro, even if the camera is average at best, the screen is less than impressive, and it's missing a headphone jack. My G2 is starting to act up and I need something cheap for the short term.
In any case, I'm doing my research now. I've downloaded the ROMs for 17s (both the stock CN version and the modified IT version). The kernel sources are released for x727, and I imagine the x720 kernel can likely be built from the same sources, in fact I wouldn't be surprised if everything about the kernel was the same. So I wanna see if I can get a kernel and rom building. I may attempt a TWRP build first, since I'd want that anyway, and it's simple enough to boot from fastboot and see if things work. But, I need help understanding the system. And that's where the information gathering in this post comes in.
secXces_debaki said:
Can u maybe help me with my meta-inf?
Click to expand...
Click to collapse
I have no idea what you're referring to with the meta-inf.
I guess my meta-inf breaked the baseband, is it even possible?, anywhere else then this my rom based on 17s booted and worked. That's why I asked, I don't have any knowledge for the meta-inf. That's to complicated for me.
When u own a x727 are u maybe able to help me? ^^
My personal thoughts about that device.. Are atm really good. The screen is for a fullhd device really good, better then my op3 or Xiaomi mi5/MI max. Also the glass feel much better in typing then any device i had since my Note 3 (nearly owned every Android device who was In any way popular)
The camera is good enough for fast pictures, but that's all, there are way better cameras outside.
The sot is for me atm way to low, if I would use it the whole day I would get around 10h sot or even more, but this device have with the .17 software a big battery drain. With 6h sot on 1 day I loose in deepsleep between 15-25%. The device isn't awake, also there is no wakelock or anything. Strange behavior.
The sound is awesome, u will love it. If u don't need much bass through the loudspeaker.
Finished my short OT ^^
U got a pm. Hope its good, logcat and logcat-radio was used after i write my pin. Or i need to make it earlier?
secXces_debaki said:
U got a pm. Hope its good, logcat and logcat-radio was used after i write my pin. Or i need to make it earlier?
Click to expand...
Click to collapse
I would really like the logcat and logcat-radio to be running from the moment just after the hardware logos on the screen start showing up, once EUI starts to boot. The logcat is circular and has a limited buffer. Once it reaches the end of it's buffer, it starts overwriting itself, therefore it only keeps a certain amount of the logs in memory before they're gone. Your logcats were therefore incomplete. In more basic terms, I don't see where the system started booting up, that part of the log had already been overwritten when you took the log.
I also sent you a response requesting additional information, and for you to re-run one of the other commands that also errored out.
I do appreciate the help, I really do, thank you
Kk I try to be as fast as possible to do the logcats at the moment my pc recognize my phone.
secXces_debaki said:
I guess my meta-inf breaked the baseband, is it even possible?, anywhere else then this my rom based on 17s booted and worked. That's why I asked, I don't have any knowledge for the meta-inf. That's to complicated for me.
When u own a x727 are u maybe able to help me? ^^
Click to expand...
Click to collapse
Yeah, that doesn't help at all. Meta-inf to me is a file included in a flashable zip. It isn't even a main file, and it isn't even particularly important. It certainly wouldn't damage the baseband. The baseband, otherwise known as the modem or radio, controls your phone. It's like the brain stem, it controls the most basic automatic responses. Generally if your radio was broken, your phone would be hard bricked, there would almost certainly be no recovering from that.
Did you flash a modified radio/firmware to your device?
secXces_debaki said:
My personal thoughts about that device.. Are atm really good. The screen is for a fullhd device really good, better then my op3 or Xiaomi mi5/MI max. Also the glass feel much better in typing then any device i had since my Note 3 (nearly owned every Android device who was In any way popular)
The camera is good enough for fast pictures, but that's all, there are way better cameras outside.
The sot is for me atm way to low, if I would use it the whole day I would get around 10h sot or even more, but this device have with the .17 software a big battery drain. With 6h sot on 1 day I loose in deepsleep between 15-25%. The device isn't awake, also there is no wakelock or anything. Strange behavior.
The sound is awesome, u will love it. If u don't need much bass through the loudspeaker.
Finished my short OT ^^
Click to expand...
Click to collapse
Heh, thanks
That actually lines up similarly to other things I've head about the device. Your assessment of the screen seems more positive than some, but then that sorta thing is a bit of personal preference. Frankly I don't game (much) to the point where I want a QHD or 4K display, and I don't intend to do VR. The reason I wanted a msm8996 is for the other advanced capabilities. The thing I'm looking forward to most is getting WiFi Calling working for T-Mobile, my reception isn't always great and that would be fantastic for me
As for the sound, I learned a long time ago to accept disappointment there. And I'm OK with that. I really wanted a headphone jack. Adapters tend to be bulky and/or break, and I don't like to be restricted to a single pair of headphones just because they have the right connector. You also can't easily share headphones with a CDLA connection. I have heard that the speaker output is nice, and I'm looking forward to that.
Mostly I'm excited that the kernel is not much modified from the CAF sources. Once I've verified that whatever it is I'm working on will actually boot, I will be able to upgrade to a newer revision of the kernel (with security fixes) and possibly even jump to the UM branch for the kernel, which is unifying for the Nougat release. I'm using the op3 as a template for my cm device and at the moment just gathering information. I don't even know if I'll buy the device yet or even make a rom. But it's what I'm looking into. This is a side project for me, and I desperately need to find a job, that takes priority.
secXces_debaki said:
Kk I try to be as fast as possible to do the logcats at the moment my pc recognize my phone.
Click to expand...
Click to collapse
I don't know how fast the phone boots, but usually I have the command already typed into the window, then I reboot and as soon as the first logo appears on the screen I hit enter. The command may not see the device immediately, and it'll say "awaiting device" and that's fine, it'll start logging as soon as the device appears. Then do CTRL+C 30 seconds after all the final connections to the cellular network are done
Managed to fix my standby drain..
U got a pm with the last logs. Hope it's good