Hi,
this might sound a very silly question to some of you, but the search function didn't yield any results (wrong keywords or VERY sill question maybe...)
Do you have to run android 2.1 on the nook or are other versions possible?
I'd like to load an app that doesn't run on 2.1
cheers
you have to use 2.1 untill somebody port the nook color roms into nst.
afaik if you need to run an app for higher api, you have to change minimum-sdk-version in android-manifest and change target api level of the app(for nst, API level 7), but im so noob about it and dunno will it work or even if its right.
http://forum.xda-developers.com/showthread.php?t=1684782
Ok thanks, that's what I feared, but the thread you gave me is a work in progress apparently, I'll just subscribe to the thread and be patient (and hope that the result is doable by a noob like myself)
Related
Come to think about is there any posibility
Android - I see a thread, but still work in progress
But how about Mac OS X on Shift
i checked on insanelymac, but still work in progress, perhaps this could be interesting alternative if i may say
OS X on Shift
I've tried to install different versions of OS X (Tiger, Leopard etc) on my shift but the main problem is the screen resolution in setup. The monitor on the Shift is only 800x480 pixels but OS X setup only detects 640x400 (if i remember correctly) and this is not enough to display setup properly. I've also tried different boot parametres to force 800x480 resolution, but without any luck.
Another problem is that the Shift CPU only supports SSE2 and the newer versions of OS X is optimized for SSE3 or better.
If you want to try it for yourself you need an external DVD-ROM and a modified OS X image file (search torrent sites for Kalyway/OSX86 etc.)
Let me know if you find a solution to the resolution problem.
Have you tried installing it when connected to an external monitor?
Regards,
Dave
Yes, I also tried installing it with an external monitor connected. The result was excactly the same. Greyscale and only 640x400 resolution...
I think the problem is that the internal display is detected regardless of if you have an external display connected, and this makes the installation program detect the highest resolution the internal display is capable of displaying.
Check out this forumthread:
Insanelymac
batghost said:
Come to think about is there any posibility
Android - I see a thread, but still work in progress
But how about Mac OS X on Shift
i checked on insanelymac, but still work in progress, perhaps this could be interesting alternative if i may say
Click to expand...
Click to collapse
After playing around the only Android phone for now (TMob G1), I found it is not exactly that enticing like having a WinMo device. In the case of WinMo, I could at least develop a lot of stuff easier and faster and the devices are restrictive. What I found in G1 is quite opposite, OS is open and ubiquitos, but the device is closed. A lot of heck is missing like having simple SIP.
HTC and TMob screwed Google and the Android community big time I believe. I love both Windows and Linux. I am totally disappointed with this. I feel Vista is not that restrictive than TMob G1, I know I am comparing wrong platforms here, but thats what I felt after spending good amount of time on G1. It is easy to develop stuff and deploy on Android and far better than iPhone deployment, but the device is restrictive not friendly like WinMo. I don't care for source code, I want to see a open machine like Wintels, and WinMos where I definately can break without bricking.
Thanks
--Ram--
OSX
Well I tried to start up an installation of OS X on my Shift but i failed. Same reason as above. No resolution.
BUT i've found this little neat thread http://forum.insanelymac.com/index.php?showtopic=115328 I will try to install OS X on friday with the mentioned patches in the thread.
Will keep you informed if it worked on friday!
carolusx said:
Well I tried to start up an installation of OS X on my Shift but i failed. Same reason as above. No resolution.
BUT i've found this little neat thread http://forum.insanelymac.com/index.php?showtopic=115328 I will try to install OS X on friday with the mentioned patches in the thread.
Will keep you informed if it worked on friday!
Click to expand...
Click to collapse
Any luck with the install when using the patches?
Nope.
Tried a lot of patches but no luck.
But Im continuing looking around to find a solution.
Do you have some instructions / Information howto is the general installation of Linux on A Windows Mobile ARM processor Side?
You leave the boot loader as is, or linux bring his own Boot loader ?
joy.d said:
Do you have some instructions / Information howto is the general installation of Linux on A Windows Mobile ARM processor Side?
You leave the boot loader as is, or linux bring his own Boot loader ?
Click to expand...
Click to collapse
I think we need to have SD-card support in SnapVue side to be able to use Haret and boot linux. There are several threads that are discussing the possibility to install linux on the SnapVue side.
Use the search function...
Hey Folks,
I was wondering if anyone knew if it was possible to use Jython instead of plane Java for android development? I don't know much about Java development but I'm with Python. I was figuring that this might ease me into it better. Any thoughts?
Thanks,
-=GB=-
Have you had a look at the Android scripting environment?
http://code.google.com/p/android-scripting/
http://google-opensource.blogspot.com/2009/06/introducing-android-scripting.html
http://code.google.com/p/android-scripting/wiki/PythonAndroidAPI
Regards,
Akshay
Thanks aksd,
I don't know how I didn't find that before. Perhaps I should have just searched for Python and Android as opposed to just Jython and androind.
Anyway, this is very cool for prototyping and simple scripting. However, the main thing I was hoping for was writing apps in Python (via Jython) that could then be distributed on the Marketplace. It's kind of to bad. It doesn't look like anyone is really trying to port Jython to Android because ASE is sort of Google's official response to the whole thing. On the whole, a really great thing for people who just want to script Android but not really for App development.
In all of this searching I did find some interesting information about how to link in C libs so you could code some of the hardcore speed sucking elements in C (like a game engine) and then make calls into it via Java. I didn't know that was even possible so... Pretty cool stuff.
Hey ngrava,
I'm not much into scripts, so dont really follow whats happening with scripting and Android.
If you wanted a bit of a performance gain you can use the NDK and call the JNI to execute native libraries or code. been there for awhile but few use them. Java is just so much easier than C .
Theres a lot of interesting stuff going on on the Android platform, Mono being ported to Android, Scala being ported to Android, I'm actually currently working on profiling the performance of scala code on android.
Regards,
Akshay
On the Google DevFest on Argentina, Google´s ingeneers afirmed that they are working to make more languages availeable on Gingerbread, they specifically mentioned Ruby. We just have to wait to see if this is true and if we are going to be able to ship apps of other languages to the market, and I´m not sure if they will be backwards compatible with earlier versions of android as well.
PD: Oops, sorry for reviving this old post, I just realised i clicked last page instead of next
First of all, lots of respect to the devs for all the work they have done so far. The last few weeks we've gone from almost nothing to one of the most complete android ports of all windows devices.
Now for the topic: I'm a (beginning) software developer and after a lot of development on the .net framework I started learning java last year, at university.
I was wondering what parts of android are actually written in java. I know that the linux kernel and stuff is written in low-level languages like C(++) or even assembler. On top of that, Android runs a java virtual machine (called drupal if I remember correctly).
Does the built-in software, like for example the standard camera software, run in java, or has it been written in low-level languages to improve speed? If it has been written in Java, can we actually edit that code from the roms that are commonly used?
If so, I think there are a lot of people that could look at stuff like fixing the video camera (by changing the button layout in that mode for example) and other small bugs that occur on higher software levels. I think there are a lot of people that know nothing about kernel development but do know stuff about java (or similar OO-languages like C#) that could help out with stuff like this.
Am I on to something here? Any people that can tell me more about this?
i dont relly know
up up !!
in XTarantula's ROM the Stock Video Camera works with sound.
his build is based on Android 2.1 (Eclair) update 1.
Model Number is Nexus One and is fully stock (even with Stock Launcher, no launcher pro preinstalled.)
its a great build, im just waiting for a Froyo Build with the same features.
hope this will help: http://developer.android.com/guide/topics/ui/ui-events.html
Hi everyone,
Just returning to the threads here to see how/if things have moved on. I've been running XDAndroidFRX05 and have just tried XDAndroidFRX06, I've also tried the FroyoXGinger build too from a while back.
My question is this, is there any build out there which supports Adobe flash which can run on the Blackstone? Or are there any other builds worth experimenting with (I'm currently having a go at CyanogenMod to see if that runs (ok CM7 not much works yet for Blackstone), now trying the XDAndroid GBX0A)?
I'll do my best to search for some more detail about Android on SD as I am well aware I don't have a clue how all the files interact so no doubt it will help to gain an understanding of it. If you know of a good guide then I would welcome a genital push in the right direction. [EDIT - I can't find anywhere which gives an explanation of what each file is and how it all fits together - I can probably guess but after some definite information if possible]
The NAND project is encouraging and hopefully it will allow android to run smoothly on our devices at some point, however for me the SDCard solution is much preferred as a dead/partly-working phone is no good for me.
I don't think Blackstone will ever run Flash because of the hardware limitations.
jeanfrederic said:
I don't think Blackstone will ever run Flash because of the hardware limitations.
Click to expand...
Click to collapse
I know full flash was apparently limited to CortexA8 processors and up, but was unsure of the lite version.
Also SkyFire and uZard browsers add 3rd party support for videos from within the browsers. I guess I expected some version of flash lite would be possible, afterall hardware limits are often ignored on here.
It seems like it could be doable but I don't expect it to work that well and I guess the HD is too old for all that effort now.
Thanks for your answer though.
Dunno about Android, but Flash Lite is working on my Blackstone.
I sometimes use FlashLIGHT (http://www.freewarepocketpc.net/ppc-download-flashlight.html ) application...
Bodisson said:
Dunno about Android, but Flash Lite is working on my Blackstone.
I sometimes use FlashLIGHT (http://www.freewarepocketpc.net/ppc-download-flashlight.html ) application...
Click to expand...
Click to collapse
Of course then you can always resort to your FleshLight afterwards.
As for hardware, I've seen other Arm11 devices claim Flash 10.1 support, but perhaps that is due to extra decoder chips maybe.
i don't know about uzard, but skyfire renders the pages on a central server and just sends you a "screenshot" of the page. that is why skyfire is the full browsing experience including flash, java, html5, ajax and whatever else you can find. actually,when i last tested skyfire on winmo, by going to ip and browser checking sites, i found, that i was running mozilla firefox with an american ip, which also allowed hulu. /OT
as stated before, i wouldn't count on the blackstone being capable of handling the full flash experience, but flash light might work, or, depending on what you actually need flash for, there might be another way around it.
Hi All,
I'm a software developer, reasonably comfortable with compiling apps in Linux, though still got more to learn on inner workings of the full system.
I've been thinking about following the Linux from Scratch book for a while - and also about converting my Nook e-reader into a useful device for developing on when out im the sun.
I guess there are some significant challenges here - device trees and commercial secrets, perhaps some crypto keys used for signing update images to boot (I'm familiar with these problems, but not solutions or good workarounds).
What I'd really like is a good understanding of:
- what tool chain I need to setup
- What has been tried already and what the problems were
- any further help/datasheets that can get me going
I'd have posted this in the 'android development' area as the closest forum for what l'm trying to do, but apparently I'm not allowed until I've got my post count up - so I'm being forced to post in 'general'. If someone agrees and can move it, that would be great.
P.s. I have searched the xda site, but I'm not finding what I'm looking for. I'm sure it must be here somewhere, so any pointers/links on where it is would be appreciated.
SimonSimpson said:
Hi All,
I'm a software developer, reasonably comfortable with compiling apps in Linux, though still got more to learn on inner workings of the full system.
I've been thinking about following the Linux from Scratch book for a while - and also about converting my Nook e-reader into a useful device for developing on when out im the sun.
I guess there are some significant challenges here - device trees and commercial secrets, perhaps some crypto keys used for signing update images to boot (I'm familiar with these problems, but not solutions or good workarounds).
What I'd really like is a good understanding of:
- what tool chain I need to setup
- What has been tried already and what the problems were
- any further help/datasheets that can get me going
I'd have posted this in the 'android development' area as the closest forum for what l'm trying to do, but apparently I'm not allowed until I've got my post count up - so I'm being forced to post in 'general'. If someone agrees and can move it, that would be great.
P.s. I have searched the xda site, but I'm not finding what I'm looking for. I'm sure it must be here somewhere, so any pointers/links on where it is would be appreciated.
Click to expand...
Click to collapse
I have tried to get info on such things three times over 2 years for different devices, no one every seems to point me in the right direction, the most i have been able to find out is how to make compile cm and a little bit of how to customize roms, not to be a downer but i think the process is often so different for ever device and difficulties usually happen that the only people that build roms are people that have either have experience I n some form from their job, just edit existing source for cm(updating to a new version, customizing roms ect...) or have screwed with the stuff for years till the point that they just figured out alot of problems themselves. Wish a could find a good guide myself to atleast get the basic dependencies required for a device to boot together, if i could get something to boot the rest of the issues could be worked out with trial and error, boot noone on xda, Android authority, Reddit or cm's own forums goes into enough depth to make that possible.
Hi jaykoerner,
Thanks for your reply - good to know I'm not alone with my echo!
I've discovered some useful links if anyone wants to begin getting to grips with all this...
1. XDA Devs has a wiki (not sure how to find from the forum links...?)
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch
2. There's a (atleast one) customized kernel (and probably a dev-tool chain) available on GitHub:
https://github.com/javifo/NST/tree/master/kernel -- including kernel compilation instructions
https://github.com/javifo/NST -- root of the repository.
3. Parallel to Raspberry Pi kernel compilation (so you may want to learn from that as it probably has more articles)
https://www.raspberrypi.org/documentation/linux/kernel/building.md
I'll post more when I next do something with the information (Still want to understand more on the android HAL)
Hope that helps someone!
SS.
SimonSimpson said:
Hi jaykoerner,
Thanks for your reply - good to know I'm not alone with my echo!
I've discovered some useful links if anyone wants to begin getting to grips with all this...
1. XDA Devs has a wiki (not sure how to find from the forum links...?)
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch
2. There's a (atleast one) customized kernel (and probably a dev-tool chain) available on GitHub:
https://github.com/javifo/NST/tree/master/kernel -- including kernel compilation instructions
https://github.com/javifo/NST -- root of the repository.
3. Parallel to Raspberry Pi kernel compilation (so you may want to learn from that as it probably has more articles)
https://www.raspberrypi.org/documentation/linux/kernel/building.md
I'll post more when I next do something with the information (Still want to understand more on the android HAL)
Hope that helps someone!
SS.
Click to expand...
Click to collapse
My initial thought was that toolchain should match the underlay Linux kernel of Eclair (2.6.x.y) for us to be sure it could be run on NST. This info that I still have to search through is certainly helpful. Thanks!
SimonSimpson said:
I guess there are some significant challenges here - device trees and commercial secrets, perhaps some crypto keys used for signing update images to boot...
Click to expand...
Click to collapse
Neither the NST or the newer glows use device trees.
In the Glows this is all handled by the custom ntxconfig which allows simple configuration.
For building Android apps, you use the straight Android SDK, possibly also the Android NDK (for native code).
You'd also use the NDK for building command line utilities.
I've never built a kernel from scratch, but I have binary modified/patched them.
There is the simpler bit of patching system image ramdisks which can be conviently handled by my imgutil.exe in the signature.
If you want to do audio, you really are better off with the Glow4 (7.8") which actually supports it.