Related
I read a lot about android is running on this, and that.. lot of devices. Is there a possibility to run it on a T830? I don't know much about android, and it's hardware support, so this question might sound a bit lame
It have to be pda specific like windows mobile?
Android Kernel
Hello,
Well i think it is possible to compile a Android Kernel to boot on FSC T830. But the main problem is its hardware support. Well, FSC T830 has supported Processor and enough ROM and RAM to make Android fit in. I did not test it or did any work to compile such kernel but if you want to work on it then let me know . All we need are some basic info about the hardware to know if its worth trying or not.
k1dugar said:
Hello,
Well i think it is possible to compile a Android Kernel to boot on FSC T830. But the main problem is its hardware support. Well, FSC T830 has supported Processor and enough ROM and RAM to make Android fit in. I did not test it or did any work to compile such kernel but if you want to work on it then let me know . All we need are some basic info about the hardware to know if its worth trying or not.
Click to expand...
Click to collapse
What do we have to know about it?
Hardware Info.
Hi, Tookool
Well we need the chipset info about the GSM controller, mainboard, wlan, gps, bluetooth, display, touchscreen and keyboard.
We need the keyboard and display to work at the very first place else it would be impossible to do anything. I have read on the forum about dual booting from SD card using gnuharet.exe. So we can compile a kernel and boot it on SD memory. Well I'm going to take a look on the Android Kernel and try to compile it and run it over QEMU. Hope for the luck.
k1dugar said:
Hi, Tookool
Well we need the chipset info about the GSM controller, mainboard, wlan, gps, bluetooth, display, touchscreen and keyboard.
We need the keyboard and display to work at the very first place else it would be impossible to do anything. I have read on the forum about dual booting from SD card using gnuharet.exe. So we can compile a kernel and boot it on SD memory. Well I'm going to take a look on the Android Kernel and try to compile it and run it over QEMU. Hope for the luck.
Click to expand...
Click to collapse
Hi!
From where can I obtain these informations? I did a quick search on the net, but...
Hardware info.
CPU: Intel XScale PXA270 (ARMv5TE) :Supported
Display: 240 x 240 (1.7' x 1.7') :Unknown (Supported on other device)
Touch Screen: - :Unknown
Audio: AC97 (not sure) :Unknown
ROM: 128MB :Supported
RAM: 64MB :Supported
GSM: Ericsson EMP U250 :Supported
GPS: SiRFstarIII GSC3f/LP :Supported
Key: QWERTY (Keymap) :Supported
WiFi: Atheros AR6001 ROCm 802.11b/g :Supported
Bluetooth: Broadcom 2040 :Supported
USB: USB 1.1 :Supported
I am trying to build kernel with info i have about the hardware. Hope it will boot at least.
I'm looking for the infos you didn't find
wifi: WLAN 802.11b/g
bluetooth: Bluetooth 2.0
keyboard: QWERTZ
usb: client/host
I found these, but I don't know if this is good or not I'm not really into things liek this
Hi,
I'm using the WM6.1 on my FCS T830 right now, but running Android on it sure sounds like an even cooler idea.
I hope somebody manages to get this working!!!
k1dugar said:
CPU: Intel XScale PXA270 (ARMv5TE) :Supported
Display: 240 x 240 (1.7' x 1.7') :Unknown (Supported on other device)
Touch Screen: - :Unknown
Audio: AC97 (not sure) :Unknown
ROM: 128MB :Supported
RAM: 64MB :Supported
GSM: Ericsson EMP U250 :Supported
GPS: SiRFstarIII GSC3f/LP :Supported
Key: QWERTY (Keymap) :Supported
WiFi: Atheros AR6001 ROCm 802.11b/g :Supported
Bluetooth: Broadcom 2040 :Supported
USB: USB 1.1 :Supported
I am trying to build kernel with info i have about the hardware. Hope it will boot at least.
Click to expand...
Click to collapse
Hey!
Any news?
Well, is this project dead or what happened?
Donno, k1dugar isn't responding
Im sorry for late reply.
Hello,
I am sorry for late reply but somehow i lost the interest on building this image now bcoz of lack in features availability in Android which would make this image useless. I'm waiting for google to launch the full source code for it. I'm Working on making WM6.1 final rom where all feature will be working and stable.
Please carry on the work, i normally dont work in a way that i will do something and upload my final work. I like ppl to research themself and make it themself so they can learn and improve something on there way. Sure untile i think its stable and wont harm someone's hardware in anyway then i will upload the final work, until then just step by step guide.
Let me finsh WM6.1 with help of all you ppl and then we can work on Android, I personally Love *NIX system. I would be more then happy to make my phone run Linux.
A fully working wm 6.1 would be great Just keep up the work with that, android can wait Don't forget about the blue keyboard thing
Before to use Android, the first step must be to have a linux kernel working on T830.
I've tried to compile 2.6.28, but I haven't succes.
It isn't impossible, but it seems hard to make, because the kernel is strictly relate to hardware platform.
There is someone that want to try thiswith me ?
Let me now.
Thanks
tea4two
tea4two said:
Before to use Android, the first step must be to have a linux kernel working on T830.
I've tried to compile 2.6.28, but I haven't succes.
It isn't impossible, but it seems hard to make, because the kernel is strictly relate to hardware platform.
There is someone that want to try thiswith me ?
Let me now.
Thanks
tea4two
Click to expand...
Click to collapse
I would like to help with everything I can. The only thing is that I never made such things like building a kernel or so But if you can provide me with instructions and things like that it would be great!
Hi TooKooL,
First steps to compile the kernel are very easy.
I'm using Fedora 10 so what I write is related.
There is the need to have the right Chaintool to compile.
I've found this information: http://loox-linux.sourceforge.net/chaintool.html
, but I work different:
1 - yum install arm* (is not the rigth command to use, but you need to install all arm-* packages)
2 - Download linux Kernel (i've used latest 2.6.28)
3 - Unpack tha kernel: tax xvzf linux-2.6.28.tgz
4 - make a symbolic link ln -s linux-2.6.28 linux
5 - modify top level Makefile in this way:
ARCH ?= arm
CROSS_COMPILE ?= /usr/bin/arm-gp2x-linux-
6 - run: make menuconfig
7 - Setup the right value in the lernel (drivers, cpu, ecc..) THIS IS THE TRUE PROBLEM!!!!
8 - run: make zImage
To load linux kernel use HaRET.
Copy on root of SD-CARD:
HaRET.exe
zImage
startup.txt
the startup.txt contain olny one row with the word "boot" (without quote)
Run HaRET and linux start to load..... if kernel is compiled rigth..... (i'm not lucky)
Other useful link are:
http://sites.google.com/site/siteofhx/Home/android/android-porting-steps/english
http://loox-linux.sourceforge.net/
Let us know if you have some results...
Regards
tea4two said:
Hi TooKooL,
First steps to compile the kernel are very easy.
I'm using Fedora 10 so what I write is related.
There is the need to have the right Chaintool to compile.
I've found this information: http://loox-linux.sourceforge.net/chaintool.html
, but I work different:
1 - yum install arm* (is not the rigth command to use, but you need to install all arm-* packages)
2 - Download linux Kernel (i've used latest 2.6.28)
3 - Unpack tha kernel: tax xvzf linux-2.6.28.tgz
4 - make a symbolic link ln -s linux-2.6.28 linux
5 - modify top level Makefile in this way:
ARCH ?= arm
CROSS_COMPILE ?= /usr/bin/arm-gp2x-linux-
6 - run: make menuconfig
7 - Setup the right value in the lernel (drivers, cpu, ecc..) THIS IS THE TRUE PROBLEM!!!!
8 - run: make zImage
To load linux kernel use HaRET.
Copy on root of SD-CARD:
HaRET.exe
zImage
startup.txt
the startup.txt contain olny one row with the word "boot" (without quote)
Run HaRET and linux start to load..... if kernel is compiled rigth..... (i'm not lucky)
Other useful link are:
http://sites.google.com/site/siteofhx/Home/android/android-porting-steps/english
http://loox-linux.sourceforge.net/
Let us know if you have some results...
Regards
Click to expand...
Click to collapse
Hi!
So, if I understand I need that chaintool (can't find download link on the page), a kernel (simple desktop linux version???). First of all make these things clear please After that I think I have to work with that chaintool as you mentioned in point 1, 4 ... Right? Sorry, but I'm new to this, I never even used linux before. Edit: ok, I found the kernels you mentioned, what files do I need to download?
linux-2.6.28.tar.bz2
linux-2.6.28.tar.bz2.sign
linux-2.6.28.tar.gz
linux-2.6.28.tar.gz.sign
linux-2.6.28.tar.sign
These?
And what about that arm package installation? It's a shame I'm a novice and I want to make this, but I have to start learning somehow
I've found other informations about to use HaRet to boot linux.
http://www.handhelds.org/moin/moin.cgi/HowtoLinuxHaret
There is the need to partitioning the SD Card in two partitions, FAT16 and ETX3.
The FAT16 is used to boot linux (copy files: Haret.exe, zImage and startup.txt)
The Etx3 is usedt to save all Linux files (/boot, /usr, /bin, /var, and so on)
I've tried to start several kernel images without success.
Haret hang when on the screen appears "Jump to kernel...."
The device hang too, the only way to unlock it's a Factory Default server.
It seems only a Kenrel issue. I don't understand where I must start to compile a new kernel.
There are PDA similar T830 ? This maybe a good starting point.
I don't understand how to use sartup.txt
This file contains information for the boot sequence, I have only "boot" write in It, but other parameter are required (I think).
Surfing the nternet I've found the need to know GPIO, how must I use it ?
Tea4two.
WOW!!!
Little success.....
I've found this project about n560
http://www.elcom.pub.ro/~adrian.popa/n560-linux/
and Linux boot on T830 .... but hang suddenly....
I'm very happy, because this is a good starting point to port Android to T830
Attention!!! You MUST repartitioning SD-CARD before copy files on it to boot Linux.
Then Linux start, but hangs suddenly and the device vibrate endless.
The only way to stop is to remove the battery.....
then before to try: MAKE BACKUP OF YOUR DATA!!!!!
For Developers:
The good starting point is to download HandHeld kernel, running follow command:
cvs -d server:[email protected]:/cvs checkout -d linux-2.6.x-hh linux/kernel26
Then use looxn560_defconfig: make looxn560_defconfig
And after..... we need to understand how change kernel config to match T830 hardware.
We need to use in the rigth way GPIO's.
GPIO's are connected to various devices (led, keyboard, touchscreen, vibrate....), so wrong configuration hang the linux boot.
Good work...
Tea4two
tea4two said:
WOW!!!
Little success.....
I've found this project about n560
http://www.elcom.pub.ro/~adrian.popa/n560-linux/
and Linux boot on T830 .... but hang suddenly....
I'm very happy, because this is a good starting point to port Android to T830
Attention!!! You MUST repartitioning SD-CARD before copy files on it to boot Linux.
Then Linux start, but hangs suddenly and the device vibrate endless.
The only way to stop is to remove the battery.....
then before to try: MAKE BACKUP OF YOUR DATA!!!!!
For Developers:
The good starting point is to download HandHeld kernel, running follow command:
cvs -d server:[email protected]:/cvs checkout -d linux-2.6.x-hh linux/kernel26
Then use looxn560_defconfig: make looxn560_defconfig
And after..... we need to understand how change kernel config to match T830 hardware.
We need to use in the rigth way GPIO's.
GPIO's are connected to various devices (led, keyboard, touchscreen, vibrate....), so wrong configuration hang the linux boot.
Good work...
Tea4two
Click to expand...
Click to collapse
I'll definiately try this later today, and I'm looking for that boot info for haret too.
Android NBHCREATOR [v0.3] on Ubuntu. FROYO SUPPORT & ADVANCED SETTINGS [July-29-2010]
NBHCreator v 0.3
NBHCreator makes the nbh file for flashing android to nand.
This utility works for Vogue, Polaris and Kaiser.
Currently supporting Donut, Eclair and Froyo
Prerequisites:
1. you need to be running Ubuntu (other Debian distros may work, give it a try) NBHCreator v2.0 will be cross-platform
2. you need to have wine installed ( I am using v1.1.42)
Make sure to "Completely" uninstall previous versions before installing newer versions.
Directions as follows:
a. select the zImage you wish to make an nbh for... try one from here:Working Kaiser GPS!! or here:DZO
b. change parameters to your liking...
c. click on the "compile" button...
d. select output folder.
and Flash Away...
Please Search for how to flash if you don't know how.
that being said...
I welcome any and all criticisms of this program
and I would appreciate any advice, suggestions, questions or comments.
Version 0.3b
-Fixed Window issues.
-For now...do not save output to a FOLDER on the Desktop.
-DOES NOT WORK YET WITH 2.6.32 ZIMAGES
Version 0.3 (07-29-2010)
-Now Supporting Froyo
-New Advanced Settings for things like Clock speed and Memory.
-Added a Date Stamp option for output filename.
-Removed internal Error checking[/B]
-This version has window issues with the xfce desktop environment. fixed in 0.3b
Version 0.2b (07-01-2010)
-Fixed false errors when creating for Vogue and Polaris
Version 0.2 (06-15-2010)
- Added ability to select zImage with name extentions ie... "zImage-12-06-10"
- Output filename now refects device type ie... "VOGUIMG, POLAIMG and KAISIMG"
- Added some error checking to make sure nbh was built correctly
- misc internal code fixes.
-False Error messages are popping up for vogue and polaris. Resulting nbh should still be usable. Fixed in 0.2b.
Version 0.1 (06-09-2010)
- should work for Kaiser, Vogue and Polaris
- Device specific options
- Settings for hw3d (donut/eclair)
- Settings for Resolution 240x320, 320x428, 320x480
- Settings for Panel Type 1, 2, 3
- Settings for Battery Capacity
- Settings for ppp.nostart (Data)
- May not work with loser's editor (let me know...)
- more options to come
- NBHs are all being named KAISIMG.NBH will be fixed in v0.2
Honestly? I think it rocks, since I'm to lazy to build my own NBH's
I see the similarities, and also the differences, and I think you should continue development personally, it's a different approach, and I can see the possibility to add to it by being able to include boot splashes perhaps, or edited initrd/zimage combinations for instance.
So yeah, keep at it
Yep, sounds like a great idea. A nbh editor is good for beginners, but it would be nice to be able to build your own. Could open up a lot of opportunities for customization.
Just make a Windows and a Mac port as well, for the future.
ok....so far progress is going along very well. I have this functioning on my setup
but I still have to work out making it transferable to other computers.
while I work on this, are there any additions that you would like to see added.
I will see if I can squeeze any changes into the beta release.
What language and GUI toolkit are you using?
It would be fairly portable if written in Python with GTK or Tk.
I am using gambas2 in ubuntu.
I am still trying to port my visual basic knowledge to gambas. it doesn't all function the same.
I have minimal experience in Python. but if you know any good tips I am all open for suggestions.
Now available for testing
really???? no feedback at all???
I have to get around to install Ubuntu, and I don't have the hard disk space for it just yet. Been meaning to go buy a terabyte hard drive to dual boot.
got sources or anything like that so I can haz on gentoo?
currently attempting to break open the deb, will fall back to a vm in worst case.
Edit: As I expected, I found the solution right after posting. Run NBHCreator.gambas from /usr/bin
I'm fairly new to Ubuntu and I've never use Wine before so can't work out how to get this running
The package installed, along with it's dependencies. Now what? How do I run it?
Sorry if this is basic stuff...
richard.
Working ok here. Still need to flash it onto my Kaiser - will report back if I find any problems.
Thank - this is a handy little tool
Edit: Hmm, output file only 4.8K so something is not right. Probably down to me so I'll keep playing.
richard_s said:
Edit: As I expected, I found the solution right after posting. Run NBHCreator.gambas from /usr/bin
richard.
Click to expand...
Click to collapse
The install deb should have created a 'start menu' item under /Applications/Other/NBHCreator
that is confirmed under the default Ubuntu window manager 'Gnome'
however I have not tested it in KDE or any other non-gnome window manager.
what window manager are you using?
poly_poly-man said:
got sources or anything like that so I can haz on gentoo?
currently attempting to break open the deb, will fall back to a vm in worst case.
Click to expand...
Click to collapse
let me know if you get it. I don't have the source available at the moment. it's on my wife's computer.
richard_s said:
Working ok here. Still need to flash it onto my Kaiser - will report back if I find any problems.
Thank - this is a handy little tool
Edit: Hmm, output file only 4.8K so something is not right. Probably down to me so I'll keep playing.
Click to expand...
Click to collapse
the resulting nbh must be 3M
DON'T FLASH IF IT ISN'T 3M.
make sure the zImage file is named 'zImage' and not somthing like 'zImage-12-06-10'
I am fixing the next version to allow different names for zImage.
mnjm9b said:
the resulting nbh must be 3M
DON'T FLASH IF IT ISN'T 3M.
make sure the zImage file is named 'zImage' and not somthing like 'zImage-12-06-10'
I am fixing the next version to allow different names for zImage.
Click to expand...
Click to collapse
No - I won't be flashing it! The file name is definitely just 'zImage'. Oh well I'll wait for the next version and try again.
richard_s said:
No - I won't be flashing it! The file name is definitely just 'zImage'. Oh well I'll wait for the next version and try again.
Click to expand...
Click to collapse
I haven't built in a error log into the program but could you run
the NBHCreator.gambas in a terminal and post the output.
what device are you building for and what are your settings?
After restarting Ubuntu your program it is all working as expected. Sorry about that - I should have thought to try that first
yeah, had to throw it into a virtual machine. Nice tool, though.
If someone describes the process in great detail (including the binary formats and all that), I can make a slightly more portable version, if you'd like.
I will be releasing a more cross-platform version after I work out all the bugs.
Keeping it ubuntu for now keeps the distribution of a crappy program to a minimal.
on that note... V0.2 will be out very shortly.
this will address
-input filename variations ie.. 'zImage-12-06-10'
-output filename specific to correct device ie.. 'VOGUIMG,POLAIMG and KAISIMG'
-error checking
-misc fixes
Update:
Fixed kaiser and polaris version info for NBH
Fixed issue where if a source code pull failed, any later attempts would fail as well
Fixed issue with updating bootenv
It's my first meaningful contribution! I put together a couple of scripts and some other stuff to make it really easy for me to create a flashable NBH from the latest kaiser kernel sources.
Many thanks to dzo, JeckyllHavok, quitlahok, rzk333, -Arturo-, kallt_kaffe, the folks at www.codesourcery.com, poliva at the htc-flasher project on googlecode, and all the people who contribute to developing, testing, etc Android on HTC devices.
Note that none of the files these scripts download are mine. They were not created by me. They all belong to other people who have contributed much to the community.
The only things that I've made are:
- crnbh (which uses commands from scripts in the htc-flasher project)
- update-workspace
- everything under the patches and signatures directories
(just the patches, not the things they patch)
This requires an active internet connection to use. I don't plan on maintaining this but I thought I'd put it out there in the hopes that it could be put to good use or something.
Download the attached file
Extract to your home folder (important)
Read the README
If you want to change it, make it better, please do! Just mention me in the credits. Also please PM me so that I know it was helpful. Thanks!
Good luck!
May I ask what this does differently than my NBHCreator?
First off, sorry for stepping on your toes I didn't notice yours until I was halfway through making it, and I only posted it because I figured it might be something to look at for ideas or something... I don't know how to describe what's different so I'll just post what it does...
update-workspace:
Gets the latest kernel source code
Gets the latest tinboot source code
Patches tinboot.S so that it uses the zImage and initrd.gz that are built later
Gets the latest bootenv source code
Patches buildInitrd so that it is a little bit safer (maybe)
Gets Yang from the htc-flasher project on googlecode
Patches the htc-flasher makefiles so that they only build Yang and HTCFlasher and then install them locally (to avoid cluttering the user's system)
Gets the arm toolchain from codesourcery.com and extracts it to the android-ezb directory
Builds and installs Yang (to the android-ezb directory)
then crnbh:
Builds the kernel source code
Builds initrd
Builds tinboot
Uses nbhmerge to create the output.nb file
Uses Yang to create the NBH file for the device
LoveMyPhone said:
First off, sorry for stepping on your toes I didn't notice yours until I was halfway through making it, and I only posted it because I figured it might be something to look at for ideas or something... I don't know how to describe what's different so I'll just post what it does...
update-workspace:
Gets the latest kernel source code
Gets the latest tinboot source code
Patches tinboot.S so that it uses the zImage and initrd.gz that are built later
Gets the latest bootenv source code
Patches buildInitrd so that it is a little bit safer (maybe)
Gets Yang from the htc-flasher project on googlecode
Patches the htc-flasher makefiles so that they only build Yang and HTCFlasher and then install them locally (to avoid cluttering the user's system)
Gets the arm toolchain from codesourcery.com and extracts it to the android-ezb directory
Builds and installs Yang (to the android-ezb directory)
then crnbh:
Builds the kernel source code
Builds initrd
Builds tinboot
Uses nbhmerge to create the output.nb file
Uses Yang to create the NBH file for the device
Click to expand...
Click to collapse
NO...NO...NO...
Don't be sorry...
I don't care if you make your own and post it...
I was only wondering because your OP was lacking in information as to what this did.
Actually the same thing happened to me just before I released my nbhcreator, loserskater released his nbh editor.
Your creator does some things mine doesn't (YET)
like actually pulling tinboot etc...
things like that I was putting off as an option for a later release.
other than that I am building the output very similar.
Now that I am in this deep I wish I would have gone without the GUI.
Seems to be creating cross-platform issues.
Well, please feel free to integrate any of it into yours. The two files are just shell-scripts written for bash... nothing more
Hi,
Here is a "test" package for camera under android.
IMPORTANT : this thread will only deal with XDANDROID Rom. Cyanogen's mod or any else might not work if camera have not been enabled in userland (checkered camera screen).
Current working devices are :
-Diamond
-Rhodium
-Raphael
-Blackstone
-Topaz
This package allow camera to be used for picture but video will fail (bug fixed, will soon publish libs).
I need some people to test it (I've tested it but when you are working on something for a long time, you sometimes need external testers...because you know where it may bug and you don't really want that so you avoid those use cases...)
1/ MAKE A BACKUP of the system.ext2, rootfs.img and data.img files so that you can revert back to normal state if something goes wrong
2/ See intructions in the 22/01/2011 update.
3/ If you have a CMDA rhodium, add the following content to the startup.txt file :
Code:
board-htcrhodium.is_cdma=1
This is a quick hack to detect CDMA board till I make it as the other board do.
4/ Replace the kernel + modules with the ones provided in the latest update.
Any feedback is welcome. If you're experiencing problems, please attach a dmesg log and logcat log so that I can analyze them. If I don"t have those files, I probably won't be able to do anything to help you.
THIS THREAD IS FOR PEOPLE WHO KNOW HOW TO USE ANDROID AND ADB. Others, wait for the final release in the common tree.
Source tree : http://gitorious.org/~jbruneaux/linux-on-qualcomm-s-msm/linux-msm-home-work (lot of changes almost every days as used as a gateway between computers)
[23/02/2011] :
* New kernel for rhodium only. This is an attempt to fix the pink screen problem.
Link to the package : http://www.4shared.com/file/OMMJkB4Q/kernel_modules_02232011.html
[29/04/2011] :
* New libraries for camcorder to enable the hardware codecs for video recording.
These libraries will make camcorder use the hardware accelerated codecs for qualcomm hardware. That will make quite good quality videos (much more than the software codec actually used) and will also make sound recording work with video.
Link to the libraries : http://www.4shared.com/file/fLEiesLy/libomx_xdandroid.html
Please also patch your froyo.user.conf with those two lines :
Code:
mount --bind /sdcard/lib_camera/libOmxCore.so /system/lib/libOmxCore.so
mount --bind /sdcard/lib_camera/libmm-omxcore.so /system/lib/libmm-omxcore.so
Note that these libraries are to be used with the official xdandroid FROYO build (FRX05 or later) and the official kernel/modules.
Don't use the kernels / libraries (except the 29/04/2011 camcorder libs) from this thread, they are now included in the offical release.
Once again : if you have a crash or a bad behaviour, please make a dmesg log + logcat log ! I can't work without these files. Thanks
PLEASE, READ CAREFULLY BEFORE POSTING AND CHECK FOR ANSWERS IN THE POSTS !
IMPORTANT : If the camera does not work, first, try to find the solution by yourself in this thread, then send me dmesg log + logcat of the boot and camera start.
Thanks to bzo for its modified libGLES_qcom and its work on rhodium (working hard on camera). Thanks to everyone who helped me with testings and logs.
Awesome... I was hoping this would make its way out into the wild soon!
Hi,
before release, i wanted to make clocks working without rpc calls, that's why it took longer. Now, the code is "cleaner" and should work for any device (with small adjustments for amss and memories configuration).
Jerome
Testing on Fuze.
Edit: Does not work, Haret freezes on boot..
i encounter this when playing around with angry bird.
Code:
msm_proc_comm_wince: DEX Code not match! a2m[0x8a], m2a[0x0], a2m_num[0x7b5], m2a_num[0x7b5]
whooooopieee! trying it out
Haret does not boot with included kernel...
test diam100:
tried this on a donut version. Camera aint working. hehehe. but it has green crash on it.
Great one. works great. the bad thing is, hardware buttons wont work after sleep on diam100. I don't know why. can anyone with diam100 comfirm on this?
everything copies successfully except gralloc.msm7k.so. The folder is unwriteable through ssh. Any suggestions for getting it moved?
it says it's a read-only file system. do I need to be in a different mode other than through adb in order to mount the file as rw?
Great! I hopefully it will work on TP2 also
This is GREAT NEWS! Yes I hope once things are ironed out it will be easy to run it on my Rhod400!
Try sudo command.
u need to mount -o remount,rw /system to make it writable
Amazing ! ^^ It works fine for me !
lorikitty said:
everything copies successfully except gralloc.msm7k.so. The folder is unwriteable through ssh. Any suggestions for getting it moved?
it says it's a read-only file system. do I need to be in a different mode other than through adb in order to mount the file as rw?
Click to expand...
Click to collapse
The lib_inst.sh contains a line to enable read/write access to rootfs so that gralloc can be overwritten
Have your tied using this script ?
Testing on Fuze.
Click to expand...
Click to collapse
Package was not designed to run on fuze but should not make your system crash or freeze...
i encounter this when playing around with angry .
Click to expand...
Click to collapse
I don't know if it's related to my kernel. Can you send the full dmesg + logcat if you've got the problem again. Also, it might come from the modded libGLES_qcom.so. What device are you using ?
I'm currently modifying blackstone files. I will need someone to test it but he must be patient because it may fail a few times before it runs (memory layout is written in a more "tweakable" way, but it may need some adjustement.
Blackstone sensor is not the mt9t013 as in diamond but mt9p012. Anyway, liboemcamera.so seems to know this sensor and it should work. I'm also looking at the CDMA diamond to make it work with camera (mainly memory configuration to do).
Will try to put a package for theses devices before xmas.
im on blacstone.maybe i could help.i saw you modified gralloc that have dynamic memory allocation from standard pmem to 3D pmem.im using qcom library for OpenGL ES 1.1-CM GL_RENDERER Q3Dimension MSM7230 01.02.08 0 4.0.0.Im testing 3D library to get better fps
xUmaRix said:
im on blacstone.maybe i could help.i saw you modified gralloc that have dynamic memory allocation from standard pmem to 3D pmem.im using qcom library for OpenGL ES 1.1-CM GL_RENDERER Q3Dimension MSM7230 01.02.08 0 4.0.0.Im testing 3D library to get better fps
Click to expand...
Click to collapse
I've used libGLES_qcom from bzo, just some memory size stuff modded. For camera, right now, I don't care about fps, but I will care when camera will work for almost every devices. Winmo can use more than our 7 & 8 mb of gpu memories, so I think we can make linux to do the same.
-UPDATE-
Add support for Diamond CDMA, Raphael (all models) and blackstone. Need some (patient) testers.
See first post
cool upload the library i can help testing for blac100.Normal qcom library use MSM7500 OpenGL ES 1.0-CM same as in winmo.I could play HomeRun battle 3D smoothly using MSM7230 OpenGL ES 1.1-CM.maybe MSM7500 need opengl patch
So, this is post made by man with obsession.
I need help with idea.
I told myself i need Amiga emu faster than pocketuae.
Uae4all is kind of emu that could be perfect for porting, so i decided to give it a try.
Natural choice was use of gizmondo port(wince device, similar envinronement etc).
Giz port relies on 0.6.3 so it is old and not sophisticated, but just works for df0: games from a500, and it has minimal amount of tricks made by porters in further developement, that's the point of choice.
I am not a programmer, so you must realize word "desperation" in whole context.
So, i tried to compile sources under cygwin and winxp, after NUMEROUS woes with makefile, sdl libs, etc etc - it compiles with newest mamaich compiler with precompiled SDL set(used to making qemu - ONLY toolset that works for gizuae4all sources - that's interesting) with some warnings - mainly related to FAME m68 core, unfortunately :E, but no general errors.
GUI works, there is no touchscreen support, dpad works, hardenter chooses cursor chosen options, filemanager works fine.
Problems start after "Run":
- uae4all has LED info about df0: and df1: drives, and i can see that df0: is accesed, sectors are changing, i assume it works fine(40's sector boots properly), but emulator quits after few seconds(i see decrunching of rick dangerous 2 cracktro PROPERLY, for example, then it crashes),
- reboot without disc in df0: results in proper 3 color boot defaults of a500(with kick 13), and proper 1 colour(violet) 3.1 boot defaults, but it quits when "begging hand"(1.3) or disc(3.1) img should appear.
Assuming:
some Amiga generated data are displayed, other ones crashes emulator.
I am not sure, where problem lies.
Now:
- is there someone that compiled scummvm for wm/wince here, or have some experience with SDL? I can see it is getting forgotten method, but still useful, though.
(info from original makefile for giz, note SDL_mixer here;/):
SDL_BASE = C:/code/Gizmondo/GizSDL
LDFLAGS = -L$(SDL_BASE) -lSDL_mixer -lSDL -lzlib -static
I tried to compile libs(whole SDL, Mixer, zlib one after another) from sources, but NONE of them compiled properly. So i took easy way of using precompiled set + small modifications...well..there are no lib related errors at last, then..
- or maybe, if it is compiler/crosscompiler envinronment problem, is there someone, that could help me to set up tools properly?
Remember, compiling ends with exe, so i am not sure about this. Other thing i would try is using mingwce-gcc set, but i did not succedeed in proper set-up with that one.
I can provide sources, toolpack or whatever after FIRST response from anyone, that can help or is interested in idea.
upd: ahh, btw gizmondo exe is not working at all, it quits regardless of (wince/wm versions of)dlls replacement. Mainly for hardcoded file/path reasons.
<post written while listening to http://demovibes.de:8000/necta192.mp3 >
Screenshots(skip resolution and all, it just doesn't matter at this moment..i think, only that matters is 4rd one, crash moment, 3.1 kick bkg colour visible):