Related
Development has been integrated with the new rootfs.
Please see the thread here:
http://forum.xda-developers.com/showthread.php?t=584707
New version coming soon:
Version 2.3 info:
-Newer simplified setup, whether you use a partition or not you will use the same files;
- fixed copying issues that were stopping some Donut builds from working. All builds should now work file.
-there are no additional files unlike previous builds.
- support for a data partition as well.
- supports all phones that the rootfs is supporting, kaiser vogue diamond etc.
Version 2.2 info;
updated for better data file backup naming.
updated to support donut
updated to support wifi (thanks enate for this)
Version 2 info;
On boot it will prompt you to boot the new recovery image, if you press a key it will load the recovery image, (the first boot you must do this to install the system) if not it will boot as normal.
If you have a system.sqsh on your sd card it will prompt you to install to your ext2 partition
- after installing the system it will move it to /sdcard/installedsystem/installedsystem.sqsh
- it will move your data file to /sdcard/datafilebackup/data$date
and create a new one. After the inital boot you can reboot and copy back your data file again.
There is one caveat that was pointed out to me today. Do not change systems twice in one day unless you don't care about your data. Because it creates the data file based on date it will overwright the old one.
Why not data to? Well our current data.img solution is awesome for backing it up.
What's coming;
Native support for update.zip's from the dream themes forum.
Menu support with several different usefull options for setting up android (this is proving to be tough but I'm working on it)
here it is!
http://code.google.com/p/vogue-andr...name=recoverfiles2.2.rar&can=2&q=#makechanges
mssmison said:
Hey guys, I've got something new coming for vogue android, I need 2 people with VOGUES's only to test something for me.
Requirements; linux install, vogue only, be able to provide bug reports, be serious!
pm me; I'm hoping to have testing ready by the end of the day.
Click to expand...
Click to collapse
sure
have linux and vogue pmed you. dang, guess i didnt pm you in time...
I don't know what this is, but you've sure got me curious as hell.
If you need another tester, let me know.
Well looks like I'm not in the closed beta, but I'm looking forward to this with great excitement. With the loss of Zen, it's good to have you back and active on this stuff again. This wouldn't happen to be Android running natively on our little wonder-units would it?
stickus said:
Well looks like I'm not in the closed beta, but I'm looking forward to this with great excitement. With the loss of Zen, it's good to have you back and active on this stuff again. This wouldn't happen to be Android running natively on our little wonder-units would it?
Click to expand...
Click to collapse
Technically, Android doesnt run "native" on any device. You don't have to port a device to android..just the linux kernel to get api's to work. I know your refering to booting android on our faster but much smaller enternal flash but the speed difference would be minimal and we would be confinded to smaller builds. I think it has to do with a memory limitation in android from the dalvik vm it uses. I'm not 100% sure on what im talking about but this is the impression ive had for android for a while. Please enlighten me if I have missed something..
posting in epic thread
stickus said:
Well looks like I'm not in the closed beta, but I'm looking forward to this with great excitement. With the loss of Zen, it's good to have you back and active on this stuff again. This wouldn't happen to be Android running natively on our little wonder-units would it?
Click to expand...
Click to collapse
It's been stated before and I'll state it again, the speed of the nand (internal memory) on the vogue is very slow. Making android boot from the nand would be a step backwards... What I'm hoping I've got it a step forwards
mssmison said:
It's been stated before and I'll state it again, the speed of the nand (internal memory) on the vogue is very slow. Making android boot from the nand would be a step backwards... What I'm hoping I've got it a step forwards
Click to expand...
Click to collapse
Interesting.
I really don't understand why the internal NAND is so slow. Windows Mobile runs just fine from NAND, so why would running Android from it be any different?
Alternatively, it seems that a flashable Android would be much more convenient, and permanent.
I'm very curious to know what you're working on, mssmison.
Shidell said:
Interesting.
I really don't understand why the internal NAND is so slow. Windows Mobile runs just fine from NAND, so why would running Android from it be any different?
Alternatively, it seems that a flashable Android would be much more convenient, and permanent.
I'm very curious to know what you're working on, mssmison.
Click to expand...
Click to collapse
Duel booting would a better option in my opinion..wm is just a better mini PC OS(Windows) and Android is a better phone/internet OS . This makes our devices even more versitle then phones just running android. I dont get how just having android would makes things better..since we just manually boot android instead of it booting once the phones is turned on...how about a linux bootloader that launches before wm does..and a graphical UI to choose from the two OS's
ajclai08 said:
Duel booting would a better option in my opinion..wm is just a better mini PC OS(Windows) and Android is a better phone/internet OS . This makes our devices even more versitle then phones just running android. I dont get how just having android would makes things better..since we just manually boot android instead of it booting once the phones is turned on...how about a linux bootloader that launches before wm does..and a graphical UI to choose from the two OS's
Click to expand...
Click to collapse
My understanding is that there isn't enough room to dual-boot both WinMo and Android from the NAND on the Vogue.
You could possibly put the bootloader in NAND and run WinMo and Android from storage, but that sorta defeats the purpose.
mssmison said:
It's been stated before and I'll state it again, the speed of the nand (internal memory) on the vogue is very slow. Making android boot from the nand would be a step backwards... What I'm hoping I've got it a step forwards
Click to expand...
Click to collapse
Sounds delicious.
UHHHHHH
Well this sounds cool, Nice to see that you are back......CANT WAIT......
DROID FOR LIFE
Freezell said:
Well this sounds cool, Nice to see that you are back......CANT WAIT......
DROID FOR LIFE
Click to expand...
Click to collapse
I never left.. I was just working in the background
what's the harm in saying what's being worked on?
bug666 said:
what's the harm in saying what's being worked on?
Click to expand...
Click to collapse
Suspense is just too much fun....?
If all goes well I should have something tomorrow night for everyone.
hintttttttttttt lol
mssmison said:
If all goes well I should have something tomorrow night for everyone.
Click to expand...
Click to collapse
Is it gonna require serious work to do, like flashing a rom? Or still just files on an SDCard, just in a different way?
TheKartus said:
Is it gonna require serious work to do, like flashing a rom? Or still just files on an SDCard, just in a different way?
Click to expand...
Click to collapse
..............
lol, i've been working on stuff in the background too. haha.
but anyways, i was like wtf, this is a total bs thread, then i saw your name everywhere. haha. so i guess it's not.
good to see a vogue developer still around!!
I'm working on getting another one so I can mess with the vogue again. it's a fun phone.
I want to ask if we can get wm7 in HD2
after week, month
Please can you answer me Is it possible to run wm7 in HD2
And when we can get
and What is the difficulty of it
Thank you
m_mansour2 said:
I want to ask if we can get wm7 in HD2
after week, month
Please can you answer me Is it possible to run wm7 in HD2
And when we can get
and What is the difficulty of it
Thank you
Click to expand...
Click to collapse
Unfortunately not and probably not for the foreseable future. Everyone is still waiting for NAND Android which appartantly was beleived that a fully working NAND ROM would be released near the end of September. Looks as tho its taking alot longer than they thought it would. However Android seem to be the main focus and not much is known about the development of WP7 on the HD2 apart from somebody has done it but it can't be released yet probably not much is working on it so just keep looking out every week or so as It won't be out anytime soon
why would you want it? it is inferior to WinMo 6.5 in most key areas
1. tethering (while it does support it, most of if not all of the harware is locked so the functionality is not exposed)
2. copy paste (yeah yeah we hear it's coming but it should have been there from the get go)
3. functionality as removable storage is not present nor is it supported by wp7 if you hack it to work (requires a hack on eacj host PC you connect the phone to)
4. UI customizing (WTF were they thinking?)
5. multi tasking for third party apps (they have appearantly reversed decisions on this)
6. BT functionality is limited.
No.
*
anhyeuemmaimai said:
why would you want it? it is inferior to WinMo 6.5 in most key areas
Click to expand...
Click to collapse
for me, cause i want a fast and stable system (sense isnt this rock stable and standard ui gives me not enough informations)...
anhyeuemmaimai said:
1. tethering (while it does support it, most of if not all of the harware is locked so the functionality is not exposed)
Click to expand...
Click to collapse
never needed
anhyeuemmaimai said:
2. copy paste (yeah yeah we hear it's coming but it should have been there from the get go)
Click to expand...
Click to collapse
i used it a couple of times and it was always hard bull
anhyeuemmaimai said:
3. functionality as removable storage is not present nor is it supported by wp7 if you hack it to work (requires a hack on eacj host PC you connect the phone to)
Click to expand...
Click to collapse
pain in the ass...realy, hope ms will support this in future....but the main thing i need this, the media player didnt support playback my folder structure...so i dont care
anhyeuemmaimai said:
4. UI customizing (WTF were they thinking?)
Click to expand...
Click to collapse
dont care
anhyeuemmaimai said:
5. multi tasking for third party apps (they have appearantly reversed decisions on this)
Click to expand...
Click to collapse
dont care
anhyeuemmaimai said:
6. BT functionality is limited.
Click to expand...
Click to collapse
dont care
0711 said:
for me, cause i want a fast and stable system (sense isnt this rock stable and standard ui gives me not enough informations)...
never needed
i used it a couple of times and it was always hard bull
pain in the ass...realy, hope ms will support this in future....but the main thing i need this, the media player didnt support playback my folder structure...so i dont care
dont care
dont care
dont care
Click to expand...
Click to collapse
tHUS,
We DONT CARE
0711 said:
for me, cause i want a fast and stable system (sense isnt this rock stable and standard ui gives me not enough informations)...
never needed
i used it a couple of times and it was always hard bull
pain in the ass...realy, hope ms will support this in future....but the main thing i need this, the media player didnt support playback my folder structure...so i dont care
dont care
dont care
dont care
Click to expand...
Click to collapse
Firstly visit www.htc.com and make sure you're running the latest ROM.
Then install SPB Mobile Shell 3.5, it's available via the MS market place as a free trial.
Also install S2P, it's a great music player which you can direct to monitor specific folders rather than adding every mp3 on your phone. Also re-size or replace your album art to 480x480 as it can take advantage of this.
I've done the above and have a fast, efficient and most importantly, stable Leo.
You can give it a go for no more than what? 30 minutes of your life? Do it next time you're sat on the toilet.
0711 said:
for me, cause i want a fast and stable system (sense isnt this rock stable and standard ui gives me not enough informations)...
never needed
i used it a couple of times and it was always hard bull
pain in the ass...realy, hope ms will support this in future....but the main thing i need this, the media player didnt support playback my folder structure...so i dont care
dont care
dont care
dont care
Click to expand...
Click to collapse
fast stable OS? rally? reports are wp7 is slower at launching apps than it's predcessor....
just because you don't need it does not mean it is not a significant shortcoming
you have issues if you can't use copy and paste (you know something that has been a staple of windows since it's inception over 25 years ago)
no way to change the UI to your liking? YAY! I get the same crappy look as everyone else..
Multitasking is essential unless you love having those long delays in WP7 when launching apps over and over again because you are using an app and you get a ph call.... better hope your developer wrote that app correctly so it saves your state......
BT file transfer something from your friend's phone to yours? Opps you are SOL.....
anhyeuemmaimai said:
fast stable OS? rally? reports are wp7 is slower at launching apps than it's predcessor....
Click to expand...
Click to collapse
Seriously, forget any report or review you read. Play with it yourself. I was VERY skeptical about WP7 and was utterly overwhelmed by it when I had a go with a HD7 recently. Seriously, it really is the smoothest and fastest UI I've ever seen, and it all makes sense when you're actually using it and not just watching a video.
anhyeuemmaimai said:
Multitasking is essential unless you love having those long delays in WP7 when launching apps over and over again because you are using an app and you get a ph call.... better hope your developer wrote that app correctly so it saves your state......
Click to expand...
Click to collapse
That's exactly the point... it's down to the developers to correctly code their apps to save state when required. That means Microsoft have put in place a way to handle multiple applications being used asynchronously.
I cant wait for WP7 to work properly on the HD2 because I really want to start playing the xbox live games on it. But I doubt itll be fast and stable lol, I imagine it will be quite slow and crappy. + very ugly
anhyeuemmaimai said:
why would you want it? it is inferior to WinMo 6.5 in most key areas
1. tethering (while it does support it, most of if not all of the harware is locked so the functionality is not exposed)
2. copy paste (yeah yeah we hear it's coming but it should have been there from the get go)
3. functionality as removable storage is not present nor is it supported by wp7 if you hack it to work (requires a hack on eacj host PC you connect the phone to)
4. UI customizing (WTF were they thinking?)
5. multi tasking for third party apps (they have appearantly reversed decisions on this)
6. BT functionality is limited.
Click to expand...
Click to collapse
7. It will rape your SD card. WP7 actually uses the "secure" in secure digital.
Callumpy said:
I cant wait for WP7 to work properly on the HD2 because I really want to start playing the xbox live games on it. But I doubt itll be fast and stable lol, I imagine it will be quite slow and crappy. + very ugly
Click to expand...
Click to collapse
Don't hold your breath for any of those features seen as WP7 has a private key which bonds the hardware and software so i can't see the HD2 ever accessing any of the main features of WP7 (online anyway).
johncmolyneux said:
Seriously, forget any report or review you read. Play with it yourself. I was VERY skeptical about WP7 and was utterly overwhelmed by it when I had a go with a HD7 recently. Seriously, it really is the smoothest and fastest UI I've ever seen, and it all makes sense when you're actually using it and not just watching a video.
Click to expand...
Click to collapse
I've posted about it before, I wouldn't say I found it slow, more long winded.
Rather than opening the apps instantly it seemed to want to make a song and dance about everything when really I just wanted to get going.
The HTC hub and weather for instance takes it to the extreme (not recomended for people who suffer travel sickness!)
Ok it's not "go away and make a cuppa" time (or go away and read War and Peace like when a BB reboots), but I did find it frustrating. It may indeed be quicker than on the HD2, but it certainly didn't feel it.
I kept wanting to open task manager to see how many apps were running and slowing it down.
xaccers said:
I've posted about it before, I wouldn't say I found it slow, more long winded.
Rather than opening the apps instantly it seemed to want to make a song and dance about everything when really I just wanted to get going.
The HTC hub and weather for instance takes it to the extreme (not recomended for people who suffer travel sickness!)
Ok it's not "go away and make a cuppa" time (or go away and read War and Peace like when a BB reboots), but I did find it frustrating. It may indeed be quicker than on the HD2, but it certainly didn't feel it.
I kept wanting to open task manager to see how many apps were running and slowing it down.
Click to expand...
Click to collapse
Yeah, I do agree that a lot goes on when you run something. There's always some transition or other taking place, and I can see that this would annoy some people instantly, and everyone else eventually. I didn't dig around looking for any customisation options for the UI, so I don't know if it can be tidied up in any way (like Android's animation options in display settings).
The HTC stuff was way more excessive than just regular apps though. Totally!
H3ALY said:
Don't hold your breath for any of those features seen as WP7 has a private key which bonds the hardware and software so i can't see the HD2 ever accessing any of the main features of WP7 (online anyway).
Click to expand...
Click to collapse
Holy crap, that sucks. Time to save up for a HD7 then.
This thread makes good points. I can now say I can wait for WP7.
Sent from my HTC HD2 using XDA App
H3ALY said:
Don't hold your breath for any of those features seen as WP7 has a private key which bonds the hardware and software so i can't see the HD2 ever accessing any of the main features of WP7 (online anyway).
Click to expand...
Click to collapse
If you can jailbreak an iphone something similar will appear for this. I have high hopes for the future of this but probably won't have picked up enough for me to want it until next december when my contract finally ends lol
Jammie_1989 said:
If you can jailbreak an iphone something similar will appear for this. I have high hopes for the future of this but probably won't have picked up enough for me to want it until next december when my contract finally ends lol
Click to expand...
Click to collapse
Think of it like xbox live on the 360 with the hacked firmwares. The chefs can do as much as they like to keep spoofing the phones so users will be able to use Zune, Windows Live, Xbox Live and other cloud services but either way Microsoft are not stupid and will keep putting a stop to it it will be short lived attempts. I would like WP7 on my HD2 myself but you have to be realistic MS have worked on a new OS and they will want to protect their new investment. IF WP7 is ported i'm pretty sure we wont have the online features for long and if anything WP7 on the HD2 will be more of a ZUNE player (offline). Don't compare the iPhone to the HD2 the iPhone is jailbroken to make use of the features it "has" this is a totally different kettle of fish porting an OS then expecting full features.
about the online cloud service, i think it is too early to say it can not be unlocked.
MS always do not want other people to crack the system. but, as you can see, windows 7 has been cracked perfectly.
just give developers more time to do their work. time will come
vista1984 said:
about the online cloud service, i think it is too early to say it can not be unlocked.
MS always do not want other people to crack the system. but, as you can see, windows 7 has been cracked perfectly.
just give developers more time to do their work. time will come
Click to expand...
Click to collapse
How is a desktop/Laptop/Netbook/Tablet operating system anything like an OS for a smartphone that is locked to hardware and tied with a private key to the software. I've not said they won't get it running no doubt they will get the OS to run but the key features probally not be something that will be avaliable (online).
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).
There's no hardware keys to press on the OUYA to get it to boot into fastboot/recovery mode. They seem to think it is a tiny minority that they shouldn't have to care about, but I don't especially feel like bricking my device. I figured I'd try to drum up a little more support on XDA.
Make your voice heard here: http://forums.ouya.tv/discussion/1380/recovery-mode/p1
TopherBarnett said:
There's no hardware keys to press on the OUYA to get it to boot into fastboot/recovery mode. They seem to think it is a tiny minority that they shouldn't have to care about, but I don't especially feel like bricking my device. I figured I'd try to drum up a little more support on XDA.
Make your voice heard here: http://forums.ouya.tv/discussion/1380/recovery-mode/p1
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2326377
Let OUYA know we want custom ROMs supported
Sent from my GT-P3113 using Tapatalk 4 Beta
TadeoNYC said:
http://forum.xda-developers.com/showthread.php?t=2326377
Let OUYA know we want custom ROMs supported
Sent from my GT-P3113 using Tapatalk 4 Beta
Click to expand...
Click to collapse
+1
You just use a USB keyboard for the hardware keys.
Or download a Reboot into recovery app.
I'm not sure how Ouya could resolve this unless you are requesting a feature set on the next wave of hardware.
As far as I know there are already several custom ROMs and recovery solutions?
Sent from my Nexus 7 using XDA Premium HD app
Thanks for the links. Didn't realize that thread was about the same thing because the title was a bit misleading.
player911 said:
You just use a USB keyboard for the hardware keys.
Or download a Reboot into recovery app.
I'm not sure how Ouya could resolve this unless you are requesting a feature set on the next wave of hardware.
As far as I know there are already several custom ROMs and recovery solutions?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
From what I understand, the USB keyboard can only be used to crash the startup into recovery using the sysreq key trick, but if it can't get past the init.d file, you're stuck in NVflash mode without the Secure Boot Key, essentially bricking your device. So now our only real hope is that OUYA changes their mind and gives us the SBK, or some sympathetic dev from their camp leaks them.
Ahhh. I didn't know it basically crashes your system.
Oddly the Ouya is the only device I don't want to hack. I don't see anything advantageous about flashing anything.
I'd be curious to know what Ouya says. They're box is hackable but I'm not sure if they would like people flashing to other ROMs that doesn't use their market.
Sent from my Galaxy Nexus using xda premium
you guys do know that some apps like quickboot (https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot&hl=en) can boot your Ouya into recovery mode? What I would like to see is getting the SBK like TopherBarnett suggested so that at least we can all be guaranteed our Ouya won't get bricked permanently because the android community is innately tinkerers when it comes to android softmods and customization.
player911 said:
Ahhh. I didn't know it basically crashes your system.
Oddly the Ouya is the only device I don't want to hack. I don't see anything advantageous about flashing anything.
Click to expand...
Click to collapse
How about bugfixes? How about a way to continue using the device three years down as a media player even after OUYA 2017 is out and the first revision of the console is increasingly abandoned? How about a way to back up your games and saves? Maybe even just a Link2SD type solution for the increasingly meager seeming 8GB internal storage?
Look, I'm in the same boat as you--the OUYA is the first Android device that I've owned where I haven't really felt a burning need to root and install a custom rom on it as soon as I could. Most of my Android devices haven't lasted a week before I had them rooted, using a custom recovery and a custom rom without the OEM crapware infested sludge slowing me down. The OUYA is the only one where I've actually used the defaults and said to myself, "Yeah, I could learn to really like this..."
Only there are some outstanding bugs that simply don't seem to be a priority and aren't getting fixed. The OUYA team has demonstrated an unwillingness to openness and an inability to communicate to its users. In the past whenever I had these types of issues, it was the community which solved most of my issues, long after the manufacturer had moved on to seek new dollars. The only reason I bought the OUYA was because of the promised openness of the console and the ability to use it with custom firmwares.
So, despite being mostly happy with my purchase I still want the promised openness that I bought the OUYA for in the first place, even if I do like the current looks of the software and want to stay as stock as possible. Otherwise there will be many who like myself will simply not bother with the next iteration of the console and no one will need to worry about what the 2017 edition OUYA looks like because there won't be one.
--bornagainpenguin
I agree but I feel this article is being a little too harsh. Ouya people aren't stupid. They know whats up with the hardcore guys like us. It's not even been out a month (July 4th or something). I'm sure they are balls to the wall with getting devs on board and bug fixes and just making the thing run properly for the 95% of people who use it the way it was intended.
Once they get their crap together and things start to begin flowing naturally and they find a little free time, they might think up something.
Has anyone tried Rom Manager or anything? There has to be some way to Reboot into Recovery other then a hardware solution.
But I just don't get it. There IS a way to hack this thing... but people are complaining that it's a little dicey. Try hacking a Xbox by taking the whole thing apart and flashing a firmware to the disc drive which requires a special PC adapter. BrickCentral if something were to go wrong. Killing your device is a taken risk when you do anything done here.
I really can't see Ouya doing anything about this. If they go out of their way to make it easy to run stock android, then it might turn Ouya devs off. Perhaps once the unit is EOL, they'll provide a final rom with some extra recovery options.
player911 said:
Has anyone tried Rom Manager or anything? There has to be some way to Reboot into Recovery other then a hardware solution.
Click to expand...
Click to collapse
There are a number of ways to boot into recovery: adb, third party apps like Quick Boot, terminal emulators. But there is currently no way to do it through hardware.
Essentially, we're missing the equivalent of "volume up+power" most of us are familiar with from rooting other devices. This makes soft bricks pretty much the same as hard bricks. And that's the problem.
Sent from my M470BSA using xda app-developers app
player911 said:
Has anyone tried Rom Manager or anything? There has to be some way to Reboot into Recovery other then a hardware solution.
Click to expand...
Click to collapse
Like Oscar_david pointed out... these are all software solutions to a hardware problem....
IF, for example, you flash an improper kernel or something goes haywire enough to cause it not to boot far enough in to atleast enable adb... you have a softbrick that can NOT be fixed by any software solution.
Sadly the real solution is one we probably will never get... and that's via unlocked bootloader or the keys so we can flash from bootrom recovery
It's mad that the OUYA guys omitted a hardware key from their design - I can't think of any other Android arm SoC based mini computer that doesn't have a pin hole button to enter recovery. All the mini stick computers like the mk802 and Google TV boxes like Pivos have this feature...
That's the thing--I could have bought a Pivos, but didn't because I wanted to have the best of both worlds and play games as well as videos. I thought the OUYA would offer that to me, but the longer it takes to fix things the less hopeful I become.
Sent from my One V using Tapatalk 2
Just wondering if it can be done with android or damn small Linux or linspire, mini xp. If so how can we get this going thought it be a cool project. I can be a tester on this end we would be hacking the firmware as we would be to any cellphone any smart tv could connect to it. Right...
Ok Admin I guess no one likes my thread. Guess we can delete my post here. It was just a thought.
jaymzway said:
Just wondering if it can be done with android or damn small Linux or linspire, mini xp. If so how can we get this going thought it be a cool project. I can be a tester on this end we would be hacking the firmware as we would be to any cellphone any smart tv could connect to it. Right...
Click to expand...
Click to collapse
Having USB at back won't make your router hardware to support android or any damn Linux..[emoji44] [emoji14]
Sent from my ara using XDA-Developers Legacy app
yoAeroA00 said:
Having USB at back won't make your router hardware to support android or any damn Linux..[emoji44] [emoji14]
Sent from my ara using XDA-Developers Legacy app
Click to expand...
Click to collapse
I never said just because it had a USB that is what's going to make it support any OS
It's all about modding and porting the firmware over to it that will support it, just as we are doing with these phones, tablets, ext.... Love how we just read the title and assume without reading the post inside before posting.
jaymzway said:
I never said just because it had a USB that is what's going to make it support any OS
It's all about modding and porting the firmware over to it that will support it, just as we are doing with these phones, tablets, ext.... Love how we just read the title and assume without reading the post inside before posting.
Click to expand...
Click to collapse
Yaa but it will need a high end CPU and Ram too support those OS'es..
Damn small linux can support a P1 PII processor which is only a 300dx - 900mhz processor which supports maybe up to 4mb - 1gig ram. Thats not really high end.
Its not gonna be a super pc.
Im sure something in the gingerbread can be modded to work on it.
verizons mobo specs processor and on board ram
https://wiki.openwrt.org/toh/actiontec/gt784wnv
For some reason it wont allow me to upload pictures it shows they been uploaded but when i save it here they disappear
damn small linux supports
https://www.pendrivelinux.com/all-in-one-usb-dsl/
If blood dawn was able to get a m890 samsung phone to get overclocked from an 890 mhz to 1400 than why not a 320mhz running some form of an os on a usb to boot from mount keyboard, mouse, hdrive to a usb hub. Its just a thought. Of course the hardest part would be a video output of some sort.
jaymzway said:
verizons mobo specs processor and on board ram
https://wiki.openwrt.org/toh/actiontec/gt784wnv
For some reason it wont allow me to upload pictures it shows they been uploaded but when i save it here they disappear
damn small linux supports
https://www.pendrivelinux.com/all-in-one-usb-dsl/
If blood dawn was able to get a m890 samsung phone to get overclocked from an 890 mhz to 1400 than why not a 320mhz running some form of an os on a usb to boot from mount keyboard, mouse, hdrive to a usb hub. Its just a thought. Of course the hardest part would be a video output of some sort.
Click to expand...
Click to collapse
I think it would Need a lot of time and professional skills to do this..
Sent from my ara using XDA-Developers Legacy app
I think thats the main reason why we have all the good peeps here at xda to help cut the time in half such as we have for the phones.
jaymzway said:
I think thats the main reason why we have all the good peeps here at xda to help cut the time in half such as we have for the phones.
Click to expand...
Click to collapse
[emoji14]
Sent from my ara using XDA-Developers Legacy app
Well bro it just makes me wonder as to why this was never done. Its all guess i will find out.
As im sure everyone laughed at web Tv back in the day. And long behold android comes along and makes it a hot seller things always has to start somewhere.
I will quote myself here on this 1 i know for fact what im after is not going to be a hot seller nor anything like that. However iam after is something that i would be able to modify and make work.
Im sure i will find use for it 1 day rather then a desk weight.
jaymzway said:
Well bro it just makes me wonder as to why this was never done. Its all guess i will find out.
As im sure everyone laughed at web Tv back in the day. And long behold android comes along and makes it a hot seller things always has to start somewhere.
I will quote myself here on this 1 i know for fact what im after is not going to be a hot seller nor anything like that. However iam after is something that i would be able to modify and make work.
Im sure i will find use for it 1 day rather then a desk weight.
Click to expand...
Click to collapse
Ya..[emoji106]
Sent from my ara using XDA-Developers Legacy app
OMG THIS HAS TO BE THE BEST THREAD EVER, ON XDA!!?!
The OP brings up an excellent point, I too am scratching my head..?? (Not bcuz it itches)
Things that just make you go hmmm....???