Related
Why does it only show me 1.23GB available fresh out of the box?
I understand the OS itself takes up room, but I know it can't take up 2.5ishGB of it.
Do we really only have 1.5GB internal memory like the Desire Z despite the 4GB claimed on the T-Mobile and HTC websites?
Someone brought up that the space might be set aside for Gingerbread which drops later this year. Could be it.
ericc191 said:
Someone brought up that the space might be set aside for Gingerbread which drops later this year. Could be it.
Click to expand...
Click to collapse
As nice as that would be, they wouldn't do that and it'd be extra trouble on HTC's part to accomplish...nothing. Even if Gingerbread was a ridiculously major update, it wouldn't account for another 2.5gb of space...
I think the truth is, we got 1.5gb instead of the claimed 4gb.
Also, I have the full system dump on my PC, and it's only weighing in at 1.7GB (This includes the ~1.3GB userdata partition).
If anyone would like to see a screenshot, give me a shout and I'll upload one.
I was thinking that they may have partitioned off a FAT32 section which you could mount to. Vibrant and the Gentouch have done that. Though from a post on tmobiles board, it didn't look like the missing amount was mounted. Total for the partitions was 2169356.
Hmmm..
What do you see when you plug in your USB, just the SDCard, or do you get a notice about an internal memory as well?
-oldsk00lz
Perhaps someone with a G2 on hand could install ConnectBot and run the command
cat /proc/partitions
and post the result here
jashsu said:
Perhaps someone with a G2 on hand could install ConnectBot and run the command
cat /proc/partitions
and post the result here
Click to expand...
Click to collapse
major minor #blocks name
179 0 2203648 mmcb1k0
lord there's so many for me to type it'd be ridic, how do I take a screen shot with the phone so I can upload it? Basically though I go from 0 to 33 in that minor category.
I wonder why I have so many partitions (I'm assuming that's what these all are)
Not cool if it doesn't have the claimed 4GB.
If it doesn't have the claimed 4GB, then maybe someone can start a class action lawsuit?
I'm not upset enough that I'd push for a lawsuit, but I do feel kind of let down I don't even think I'll use the full 1.5gb, but I expected 4gb and didn't get what I expected.
Jorsher said:
I'm not upset enough that I'd push for a lawsuit, but I do feel kind of let down I don't even think I'll use the full 1.5gb, but I expected 4gb and didn't get what I expected.
Click to expand...
Click to collapse
They advertised it as 4GB, so it must have 4GB. If it doesn't then the class action lawsuit will come and you won't even have to do a thing other than reap a small reward. I feel confident that there is 4GB in there, even if it isn't user accessible.
keyl10 said:
They advertised it as 4GB, so it must have 4GB. If it doesn't then the class action lawsuit will come and you won't even have to do a thing other than reap a small reward. I feel confident that there is 4GB in there, even if it isn't user accessible.
Click to expand...
Click to collapse
Yeah, I understand it would come and I'd expect it to, just saying that personally I don't think it's that big of a deal.
Honestly I don't see why they'd make it inaccessible, at least not 2.5gb of it. I'm thinking it's only 1.5gb to match the Desire Z hardware, since everything else is the same as far as hardware.
I could be wrong (I don't have a G2). On my vibrant the available space is saying 12.75GB under "Phone storage" but only 1.47 under "Application storage".
I suspect that there's a set application storage area in android up to maybe 1.5GB and then the rest is for the OS and other data (music, movies, files, etc). The Vibrant's storage is 16GB which translates to around 15.xx. Then Android is taking up 1 or so and pre-installed apps only a tiny fraction (50MB or less)...that's why I'm showing 12.75. It's the remainder of the 15-Android (1 or so GB maybe less)+App Space (1.5GB)
Yeah, maybe it's just hidden space that can be unlocked by a custom rom. If the Desire Z only has 1.5GB total, I just have a hard time seeing why they'd hide 2.5GB on the G2.
^ has anyone called HTC and asked why they might only be seeing such low memory when it was supposed to have 4gb? maybe they can give us an answer?
i agree about the not really caring on the lawsuit bit. but i'm curious to know where it is lol... we didn't buy these phones pre-order cuz it was cheap lol, so if you need the money get hit by a car. more money and easier just step in front... so suing a company like htc whom we like very much would not be cool... just my .02
crr127 said:
i agree about the not really caring on the lawsuit bit. but i'm curious to know where it is lol... we didn't buy these phones pre-order cuz it was cheap lol, so if you need the money get hit by a car. more money and easier just step in front... so suing a company like htc whom we like very much would not be cool... just my .02
Click to expand...
Click to collapse
errr - as "uncool" as advertising 4GB and not delivering it??
seriously, i suspect it's there, just locked or hidden for whatever purposes
i'm sure it is there also. it is a brand new phone, i'm sure it is hiding or waiting to be used for something
apps2sd? using it somehow?
I'm going with the missing space being taken up by all the bloat apps.
Sent from my T-Mobile G2.
Drakon911 said:
I'm going with the missing space being taken up by all the bloat apps.
Sent from my T-Mobile G2.
Click to expand...
Click to collapse
There are most definitely not 2.5gb of bloat apps.
If there was, it'd be impossible for the considerably-more-bloated Desire Z to cope with only 1.5gb of memory.
Title says it all,
Are the developers here moving to the new developer phone or no?
Can we please forget some of the setbacks for this device and realize what a gem we have? The amazing CPU doesn't miss a beat and I believe is more reliable then the hyped dual cores. (TOO MUCH HYPE !!) 16gb of ROM is plenty enough.
Pure Google is the way too go.
Ok...
16GB of ROM is nice... but are we able to EXT partition that and do the proper apps2sd instead of the stupid froyo based implementation of it the same as we could an SD card? Or does this not matter as it should be mounted automatically anyway? I'm not sure how all that works with built in memory.
lostinbeta said:
16GB of ROM is nice... but are we able to EXT partition that and do the proper apps2sd instead of the stupid froyo based implementation of it the same as we could an SD card? Or does this not matter as it should be mounted automatically anyway? I'm not sure how all that works with built in memory.
Click to expand...
Click to collapse
Same here. Does this mean all storage is available for apps ?
This is very interesting.
If the developers go to the Nexus S, that is where I will going. That is.. if it gets as many ROMs the Nexus One has.
xManMythLegend said:
Same here. Does this mean all storage is available for apps ?
Click to expand...
Click to collapse
I'm guessing that about 2GBS will be avaliable for apps. All I know is that it's enough and I REALLY can't wait much longer for this thing to come
I was wondering about that. Awesome. Still torn whether or not I want to retire my N1 yet....
Regarding apps2ext/sd. Why would that be needed if there is 1-2GB of app storage? The N1 has about 200mb. I still haven't filled that up.
El Daddy said:
I was wondering about that. Awesome. Still torn whether or not I want to retire my N1 yet....
Regarding apps2ext/sd. Why would that be needed if there is 1-2GB of app storage? The N1 has about 200mb. I still haven't filled that up.
Click to expand...
Click to collapse
If it's 1-2GB storage then I personally won't need EXT, but as it stands if your app storage goes below a certain amount you start to get irritating alerts and your text messages and such stop going through... and if I don't use EXT I reach that point and it's rather annoying.
I hear ya.
Wouldn't it be nice If the user was allowed to partition the remaining internal storage at first boot?
Lets say the nexus s has 14GB left over after /system, radio, etc. It would be cool to decide how much of that space you wanted allocated to apps.
It may be a stupid or impossible idea. I don't know haha.
El Daddy said:
I hear ya.
Wouldn't it be nice If the user was allowed to partition the remaining internal storage at first boot?
Lets say the nexus s has 14GB left over after /system, radio, etc. It would be cool to decide how much of that space you wanted allocated to apps.
It may be a stupid or impossible idea. I don't know haha.
Click to expand...
Click to collapse
That would be awesome lmfaoo..
I'm ready to retire anything for this.
Cyanogen?!?!
Any word yet on if he's going to make this *HIS* official device the way he did with the G1 and then the Nexus One? That'll be the biggest factor for me... Or does he only choose devices that end in 1/One?
So this is iphone stile no sd??
N1
fcisco13 said:
So this is iphone stile no sd??
N1
Click to expand...
Click to collapse
Yes, sucks. And there is no dual processors. Get a mt4g instead
Quick84 said:
Any word yet on if he's going to make this *HIS* official device the way he did with the G1 and then the Nexus One? That'll be the biggest factor for me... Or does he only choose devices that end in 1/One?
Click to expand...
Click to collapse
Look at the support the Evo is getting and its not HIS device. Cyanogen has plenty of love to go around
.... I hope
...
I know several other phones get support, but nothing like the G1 did or the Nexus One does... That's all I'm saying...
As for the MT4G, I HATE the MyTouch overlay on everything. It's not a genius button, it's a goofball button... I still will miss the trackball of the N1 and the color customization that comes with it.
he he
I was thinking, this great community has discovered and successfully enabled the hidden FM radio function on Nexus One.
Could there be a hidden SD slot on Nexus S?
I don't think the FM Radio wasn't hidden iirc, It was never programmed into the kernel or the phone. I guess we did learn as a community that the N1 had the right hardware just no software support.
Quick84 said:
I know several other phones get support, but nothing like the G1 did or the Nexus One does... That's all I'm saying...
As for the MT4G, I HATE the MyTouch overlay on everything. It's not a genius button, it's a goofball button... I still will miss the trackball of the N1 and the color customization that comes with it.
Click to expand...
Click to collapse
That's what custom roms are for. Look like ppl wit be losing more than trackball colors on the nexus s. I was gonna get it also, but after the specs, no thanks
for the memory issue, most likely the NS will follow the GS style of 2GB for apps and about 13GB as the "sd card"
As far as cyanogen goes, i sent him a couple messages on twitter asking his thoughts on the Nexus S and he ignored them. and he hasn't said anything about it on his own so IDK.
They have had MASSIVE issues getting CM to work on any of the samsung devices, but with this one being stock google and being the dev phone, it should be easier to get CM working.
Anyway I don't think Nexus S is enough to be a developer phone.
While most other Android phones have SD and trackball support, Nexus S has neither, how can it still be a developer phone? I thought developer phone should have everything that other phones have.
I think Nexus One is a wonderful developer phone, despite front-camera, there's nothing else that Nexus One is lack of.
http://www.androidpolice.com/2010/12/11/data2ext-hack-blows-benchmarks-out-of-the-water/
Pretty big news out of the XDA-Forums today – forum member and resident genius Ownhere has come up with a ‘data2ext’ hack that allows users to enhance the way Android handles OS-specific data and memory. Put simply, this hack allows users to change some partition settings in order to greatly increase performance.
Originally created for the HTC Desire, the hack delivers some outstanding performance improvements and is a must have if you own the device. For more technical information, you can click here. A word of warning, though: this hack is not for the feint of heart as it is fairly difficult.
Interesting..
Pretty nice...3000 points in Quadrant is huge. Maybe we can get something similar to our devices as well...Santa Claus is approaching
not today's but they are great...if the hack doesn't destabilize the device or harm safety...
http://forum.xda-developers.com/showthread.php?t=859419
Wow, I hope someone will implement this for Legend!
qzem said:
Wow, I hope someone will implement this for Legend!
Click to expand...
Click to collapse
Same here...
I read the post howto for desire and it looked sooooooooooo complicated...
This will be fairly easy to implement... but things could go very bad using this mod. Like for instance if you make a sudden power-off... filesystem may stay in such state that it cannot be mounted on the next boot and for novice users this could mean that wipe should be made to resolve this situation.
Sent from my HTC Legend
BlaY0 said:
This will be fairly easy to implement... but things could go very bad using this mod. Like for instance if you make a sudden power-off... filesystem may stay in such state that it cannot be mounted on the next boot and for novice users this could mean that wipe should be made to resolve this situation.
Sent from my HTC Legend
Click to expand...
Click to collapse
This problem should only be there if you really disable journaling. From the original post:
As you see, the best speed is: mount real ext4 device with loop option, disable journaling. The best balance of performance and safe is mount real ext4 device with loop option, enable journaling! We don't need a loopfile but just change mount option.
Click to expand...
Click to collapse
As long as journaling is enabled this should be quite safe. At least thats what journaling is for
If someone will implement this, it would require microSD card class >= 4, to use this hack. Am I right?
I just wondered, I'm not sure if this was ever brought up...
Lately, some of my friends have been passing all of their old phones such as Nexus S, Nex4g, HTC HD2, and SGS4G.
Well, I notice that the HTC HD2 and the Nexus S 4G can be partitioned or somehow manipulated that you can install endless apps on that partition. However, even though it is almost the same hardware as the Nexus S, nobody, or has had even tried to do what the Sprint S4G devs has done.
On the vibrant, it always shows that you got about 300 or less MB to install apps. But the problem is, when you overload that, your games/apps/etc., starts to just force close. I noticed that.
So, I searched the Vibrant threads and found nothing or no one has ever increased the amount of MB in their ROM.
ndwgs said:
I just wondered, I'm not sure if this was ever brought up...
Lately, some of my friends have been passing all of their old phones such as Nexus S, Nex4g, HTC HD2, and SGS4G.
Well, I notice that the HTC HD2 and the Nexus S 4G can be partitioned or somehow manipulated that you can install endless apps on that partition. However, even though it is almost the same hardware as the Nexus S, nobody, or has had even tried to do what the Sprint S4G devs has done.
On the vibrant, it always shows that you got about 300 or less MB to install apps. But the problem is, when you overload that, your games/apps/etc., starts to just force close. I noticed that.
So, I searched the Vibrant threads and found nothing or no one has ever increased the amount of MB in their ROM.
Click to expand...
Click to collapse
Use a Root capable file explorer and create a file in your /datadata folder named .nodatadata (the one on the root of your phone)
After you reboot, it will take much longer than usual, all your installs will move to that folder and you can then install as many apps as you have "Internal Storage".
If you somehow manage to fill this up you can move your largest apps to your Internal SDCARD
Raistline said:
Use a Root capable file explorer and create a file in your /datadata folder named .nodatadata (the one on the root of your phone)
After you reboot, it will take much longer than usual, all your installs will move to that folder and you can then install as many apps as you have "Internal Storage".
If you somehow manage to fill this up you can move your largest apps to your Internal SDCARD
Click to expand...
Click to collapse
But isn't it that you use the MicroSD card for this?
Let's make it clear, Internal SD is the Vibrant's and MicroSD is that small sd card.
And maybe I'm just looking at this aspect way to differently. I was under the impression when we do this, and I have done this, it pretty much the same concept as having Apps2SD, right? Or am I wrong still?
(Please, prove me wrong, and explain. No harm)
ndwgs said:
I just wondered, I'm not sure if this was ever brought up...
Lately, some of my friends have been passing all of their old phones such as Nexus S, Nex4g, HTC HD2, and SGS4G.
Well, I notice that the HTC HD2 and the Nexus S 4G can be partitioned or somehow manipulated that you can install endless apps on that partition. However, even though it is almost the same hardware as the Nexus S, nobody, or has had even tried to do what the Sprint S4G devs has done.
On the vibrant, it always shows that you got about 300 or less MB to install apps. But the problem is, when you overload that, your games/apps/etc., starts to just force close. I noticed that.
So, I searched the Vibrant threads and found nothing or no one has ever increased the amount of MB in their ROM.
Click to expand...
Click to collapse
You must not be using the stock ROM, because that's not a problem on stock. On ROMs where this is the case, however, it is the /datadata partition that's limited. Raistline's .nodatadata solution will work - I'm running that way myself - but you will lose the speed bonus given by using /datadata. The /datadata partition cannot be resized in the way you suggest. I was looking into this too, but apparently the boot process (at least in Passion, the ROM I use) looks for the partitions to be a certain size. If they're not, it has problems. So resizing is not an option. You can either have only ~300MB and have fast operations, or you can get more than that and things can be laggy. (Mind you, it's not very laggy, like I said I am using .nodatadata and everything seems fine.)
300 MB or less for apps? I have 2gb which is plenty
Sent from my SGH-T959 using XDA App
manus ferrera said:
300 MB or less for apps? I have 2gb which is plenty
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Certain custom ROMs have this restriction. Stock usually does not, and other custom ROMs might not.
woofiegrrl said:
You must not be using the stock ROM, because that's not a problem on stock. On ROMs where this is the case, however, it is the /datadata partition that's limited. Raistline's .nodatadata solution will work - I'm running that way myself - but you will lose the speed bonus given by using /datadata. The /datadata partition cannot be resized in the way you suggest. I was looking into this too, but apparently the boot process (at least in Passion, the ROM I use) looks for the partitions to be a certain size. If they're not, it has problems. So resizing is not an option. You can either have only ~300MB and have fast operations, or you can get more than that and things can be laggy. (Mind you, it's not very laggy, like I said I am using .nodatadata and everything seems fine.)
Click to expand...
Click to collapse
Ok, I see.
I just got done messing with ICS Neobuddy, odin'ed to stock, and now running MoPed's Jetpack v9. I don't think this port is stock, but it's as close to stock 2.3.5
Later this week, i'll try out Saurom by Dgr8, and it's 2.3.6.
How did you input .nodatadata on Passion, since it isn't a 'stock' rom?
You think this will be laggy on any Ginger?
It's just a matter of creating a blank file called .nodatadata within the /datadata folder. I did it in a terminal window with "touch .nodatadata" but other methods will work too. If you search for .nodatadata you will find various posts with instructions.
the .nodatadata method allows you to install more than 512MB of apps on the phone, it will allow you to use the full 1.8GB App storage that your phone has stock.
Anything beyond that you can use move the app to SDCARD, which is the phones Internal 16GB of storage. Not all apps are able to use SDCARD installs though.
woofiegrrl said:
It's just a matter of creating a blank file called .nodatadata within the /datadata folder. I did it in a terminal window with "touch .nodatadata" but other methods will work too. If you search for .nodatadata you will find various posts with instructions.
Click to expand...
Click to collapse
Oh yeh, i know how, i was just curious how it works or why it worked in Passion. Ok, im jumping ship and flashing Passion.
Raistline said:
the .nodatadata method allows you to install more than 512MB of apps on the phone, it will allow you to use the full 1.8GB App storage that your phone has stock.
Anything beyond that you can use move the app to SDCARD, which is the phones Internal 16GB of storage. Not all apps are able to use SDCARD installs though.
Click to expand...
Click to collapse
Thanks Raistline
Hey
I've recently got my NST and, after TouchNootering it, I reverted it back to stock and manually rooted & installed stuff on it. I managed to install latest busybox too (1.19.1), even better than what TouchNooter installs.
Anyways, I've been wondering if anybody here is up to the challenge of making a ROM for this device. Modifying the actual ROM is nice... but it's buggy and it feels sloppy at times, not to mention it semi-works. Some features do, some don't.
I think, that if we make it possible to run a basic Eclair ROM, we can move to Froyo and maybe then, with enough experience and all, get GB or ICS installed on it. I think it's -very- possible... it just needs to be put some work on
Anyone?
Two issues: Drivers and memory. Unless drivers are available for the version of Android you want to build, you're going to have a tough time. Unless B&N releases a newer version of Android for the NST, this is probably unlikely. I suspect we're stuck on 2.1 eclair.
The NST only has 256M of memory, so a lot of what works on other devices is going to have to trimmed down.
This isn't to say that it can't be done, but by the time you're done, it may not be so much better than what we've got. Anything is possible, of course, but I'm not aware of anything along the lines of CyanogenMod in the works for the NST. I'd be happy to be wrong.
In the meantime, there's no reason improved software can't be written to run on what we've got. At least rooting makes that possible.
bobstro said:
Two issues: Drivers and memory. Unless drivers are available for the version of Android you want to build, you're going to have a tough time. Unless B&N releases a newer version of Android for the NST, this is probably unlikely. I suspect we're stuck on 2.1 eclair.
The NST only has 256M of memory, so a lot of what works on other devices is going to have to trimmed down.
This isn't to say that it can't be done, but by the time you're done, it may not be so much better than what we've got. Anything is possible, of course, but I'm not aware of anything along the lines of CyanogenMod in the works for the NST. I'd be happy to be wrong.
In the meantime, there's no reason improved software can't be written to run on what we've got. At least rooting makes that possible.
Click to expand...
Click to collapse
Hey
Well, yes, there's the issue with drivers. Thing is, and I might be wrong at this, that a driver can be kept in newer versions and still be used. For example, in HTC Magic, the video driver hasn't been updated in *ages*, and the little device can even run ICS now. Froyo, Donut & Gingerbread both use almost the same driver versions and it hasn't had any issues so far. I'm using my own experience as base on this though.
About the memory, again experience, HTC Magic has like 512 Mb ROM and 256 Mb RAM. The NST has 256 MB RAM and 2GB ROM. I find it very possible.
Thing is, I'm not very satisfied with "what we've got". See, I bought it planning to use it as a tablet instead, since... I rarely read, lol. So far so good, I can VNC/TeamView to computers at work and my computer at home, take notes and even browse the web (well, kiiiinda...), but it's buggy as hell. I mean, the rooters we have are pretty good at what they do, but the OS itself, the way B&N built it, it's broken.
See, LatinIME doesn't work correctly or is almost impossible to use with Dolphin (or any other browser) because they also broke WebCore =/. Not to mention the colors are a bit off since it's all B&W and some texts are in the same color as the background (thanks to their Framework.res theme) so...
Taking that into account, I wanted to give a go at a ROM instead, since there isn't any ROM for this device yet, and considering we have CWM working, I find it very possible to compile a ROM and use it, or hell, at least have a pure Android OS booting.
I've made some research here:
http://elinux.org/Android_on_OMAP
http://www.omappedia.org/wiki/Android_Getting_Started#Video_Tutorials
https://docs.google.com/document/d/19f7Z1rxJHa5grNlNFSkh7hQ0LmDOuPdKMQUg8HFiyzs/edit?hl=en_US
http://wiki.cyanogenmod.com/wiki/Barnes_&_Noble_Nook_Color:_Compile_CyanogenMod_(Linux)
And I think it's very possible to build a ROM, using the first two links + the tutorial at google docs. Also, it seems that some procedures, tools or code made for the Nook Color are also able to be used for the NST, since they share almost the same exact hardware.
However, I'm confused on how to start. This is my first time building an Android ROM after some few failed attempts at an HTC Magic ROM, though the instructions seem to be waaaay easier than HTC's. Right now I'm downloading Ubuntu Server 11.10 x64 so I can set up a simple OpenBox environment and start pulling code... but it's confusing
I'm up for the challenge, and I'm trying to work on it, but I'm no genius and I feel that if there's more than one person working on this, we can take a ROM out which would be better than the stock ROM and would have better and cooler stuff, like USB Host Mode already included or the refresh rate fixed/faster. Hell, I even restored it to factory defaults and then rooted it manually and installed BusyBox 1.19.1 in it, something which isn't mentioned in any tutorial that I've found yet.
darkguy2008 said:
Hey
Well, yes, there's the issue with drivers. Thing is, and I might be wrong at this, that a driver can be kept in newer versions and still be used. For example, in HTC Magic, the video driver hasn't been updated in *ages*, and the little device can even run ICS now. Froyo, Donut & Gingerbread both use almost the same driver versions and it hasn't had any issues so far. I'm using my own experience as base on this though.
Click to expand...
Click to collapse
The issue with drivers isn't so much it being old, it's getting a driver for the E-Ink screen. It's like video cards; you can put any driver you want on any computer, but unless it's the right one, you'll be stuck at 640x480 (or in the case of Android, no display).
darkguy2008 said:
About the memory, again experience, HTC Magic has like 512 Mb ROM and 256 Mb RAM. The NST has 256 MB RAM and 2GB ROM. I find it very possible.
Click to expand...
Click to collapse
It's not ROM, it's flash storage or whatever the correct term. ROM (read-only-memory) cannot be written to, and the flash storage is just storage space.
darkguy2008 said:
See, LatinIME doesn't work correctly or is almost impossible to use with Dolphin (or any other browser) because they also broke WebCore =/. Not to mention the colors are a bit off since it's all B&W and some texts are in the same color as the background (thanks to their Framework.res theme) so...
Click to expand...
Click to collapse
WebKit could probably be fixed eventually, and fixing the framework-res.apk shouldn't be too difficult, just unpack the thing with apktool and grab notepad++ or something.
darkguy2008 said:
Taking that into account, I wanted to give a go at a ROM instead, since there isn't any ROM for this device yet, and considering we have CWM working, I find it very possible to compile a ROM and use it, or hell, at least have a pure Android OS booting.
Click to expand...
Click to collapse
If we had CWM working, would this thread exist? Yes, it's working on the Nook Color, but getting it to work on the NST would require removing so many things and so much more, and even when it does happen it'd probably be a hollow shell of what it normally is.
darkguy2008 said:
I'm up for the challenge, and I'm trying to work on it, but I'm no genius and I feel that if there's more than one person working on this, we can take a ROM out which would be better than the stock ROM and would have better and cooler stuff, like USB Host Mode already included or the refresh rate fixed/faster. Hell, I even restored it to factory defaults and then rooted it manually and installed BusyBox 1.19.1 in it, something which isn't mentioned in any tutorial that I've found yet.
Click to expand...
Click to collapse
I didn't mean to put you down by all this or flame you, so hey, good luck!
Googie2149 said:
The issue with drivers isn't so much it being old, it's getting a driver for the E-Ink screen. It's like video cards; you can put any driver you want on any computer, but unless it's the right one, you'll be stuck at 640x480 (or in the case of Android, no display).
Click to expand...
Click to collapse
Hmm, you're right. I have the idea of using Eclair's drivers included in the B&N update files (1.1.2), I dunno how to use them but if the .so file exists, there must be a way to invoke their methods, no? It's just a theory, I kinda suck at this thing of kernel drivers 'n stuff.
Googie2149 said:
It's not ROM, it's flash storage or whatever the correct term. ROM (read-only-memory) cannot be written to, and the flash storage is just storage space.
Click to expand...
Click to collapse
Oh okay, then I can't seem to find any official specs of how much RAM does the NST have =/. Pretty weird.
Googie2149 said:
WebKit could probably be fixed eventually, and fixing the framework-res.apk shouldn't be too difficult, just unpack the thing with apktool and grab notepad++ or something.
Click to expand...
Click to collapse
Yeah, I have an idea of trying to fix that APK, but I wanted something more... Android-ish xD.
Googie2149 said:
f we had CWM working, would this thread exist? Yes, it's working on the Nook Color, but getting it to work on the NST would require removing so many things and so much more, and even when it does happen it'd probably be a hollow shell of what it normally is.
Click to expand...
Click to collapse
Actually, we -have- CWM working in the NST, just look here -> http://forum.xda-developers.com/showthread.php?t=1360994 . If a recovery was made possible in NST, which means some ROM (or whatever) compiling to display and use the hardware buttons, I'm very sure it is possible to build an Android ROM the same way o.o...
Googie2149 said:
I didn't mean to put you down by all this or flame you, so hey, good luck!
Click to expand...
Click to collapse
Hehe, it's okay, didn't take it as that, so, thanks
---
On another news, I followed this tutorial: http://www.omappedia.org/wiki/Android_Getting_Started up to the "repo sync" stage. It says it should take an hour and all, but it doesn't. It takes like 5 seconds, no output, nada. I don't know what could be wrong
Any help?
darkguy2008 said:
I can't seem to find any official specs of how much RAM does the NST have =/.
Click to expand...
Click to collapse
> adb shell
$ busybox free -m
Learn to love the command line.
darkguy2008 said:
Actually, we -have- CWM working in the NST, just look here -> http://forum.xda-developers.com/showthread.php?t=1360994 . If a recovery was made possible in NST, which means some ROM (or whatever) compiling to display and use the hardware buttons, I'm very sure it is possible to build an Android ROM the same way o.o...
Click to expand...
Click to collapse
Derp, I thought you were talking about Cyanogenmod for some reason.
notriddle said:
> adb shell
$ busybox free -m
Learn to love the command line.
Click to expand...
Click to collapse
Hey, I love the command line I -have- to ... Anyways, didn't thought of that first, so thanks
According to this:
Code:
total used free shared buffers
Mem: 227 212 14 0 8
-/+ buffers: 204 23
Swap: 0 0 0
The device only has 256 Mb RAM? I find it enough up to ICS. My previous HTC Magic could run ICS quite happily even without hardware acceleration, Froyo ran as fast as the stock 1.5 ROM and Gingerbread ran pretty okay. I didn't have the chance to work on optimizing it because my Magic got stolen, but I bet it could've been made to work as fast as the stock ROM if correctly optimized. Taking that into account, I'm sure this device can withstand a greater android version .
Googie2149 said:
Derp, I thought you were talking about Cyanogenmod for some reason.
Click to expand...
Click to collapse
Lol, nah XD. It it would be cool if it worked but nah, those guys prefer the most powerful devices :/ sucks though.
Okay, according to this wiki: http://wiki.samat.org/Nook ... NST's source code is here (for 1.1):
http://images.barnesandnoble.com/PResources/download/Nook/source-code/nook2_1-1.tgz
Anybody have an idea on how to compile it though? it doesn't seem complete to me.
Look here : http://forum.xda-developers.com/showthread.php?t=1290524
mdall said:
Look here : http://forum.xda-developers.com/showthread.php?t=1290524
Click to expand...
Click to collapse
That doesn't make any sense, that's for compiling a Kernel... this source code is for a whole ROM (it seems)... it has the kernel, u-boot, x-loader and some android source.
---
EDIT:
Actually... it makes sense now (after reading the whole thread, of course)... I'll see what I can do. Thanks for the link
I think radical changes of the Android version is too much to expect.
There's not a lot of ram on the Nook.
However, I just read that one of the big differences between 2.1 and 2.2
is that big changes were made to the Dalvik VM which sped it up 2X to 5X.
I think that that would be a worthy goal.
Renate NST said:
There's not a lot of ram on the Nook.
Click to expand...
Click to collapse
We won't know if nobody tries. Besides, GB has been ported to phones with less. (HTC Magic, as he already mentioned)
However, I just read that one of the big differences between 2.1 and 2.2
is that big changes were made to the Dalvik VM which sped it up 2X to 5X.
I think that that would be a worthy goal.
Click to expand...
Click to collapse
That would be awesome for stock users, but what about those apps that break under the hackish stock ROM? (ColorNote Sync, for example) Or things like NoRefresh that could take advantage of the underlying system's knowledge.
I think working around CM sources, like someone already has posted about trying, is a good idea.
CM9 might be a bit much, but CM7 is well in the device's range.
After all, it runs a CPU like my Motorola Defy, which runs CM9 without hassle (now with HWUI). It has 512MB ram though.
Look here: http://forum.xda-developers.com/showthread.php?t=1684782
imachine said:
I think working around CM sources, like someone already has posted about trying, is a good idea.
CM9 might be a bit much, but CM7 is well in the device's range.
After all, it runs a CPU like my Motorola Defy, which runs CM9 without hassle (now with HWUI). It has 512MB ram though.
Look here: http://forum.xda-developers.com/showthread.php?t=1684782
Click to expand...
Click to collapse
This thread is over a month old, and the thread specifically about CM7 is about 3 days old. But either way, I think that the NST can handle CM. The screen refresh may make it seem slow, but it actually is a little powerful (but seeing as it was my first Android device, and my only other one is a Nook Color, it might actually be as terrible as others say).