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
Related
Time changes, and things go better and better.
This thread is dedicated to test the android and try to figure out where is the problem
[NEWS]
The NEW KERNEL ROCKS.. With double RAM.
And the new rootfs is cleaner than before.
I am going to release a new package (which I just did some small editing)
What can you do with this package?
Connect ADB (very important for debugging)
Put everything in a folder of your SDCard
Supply with NEW kernel and now you have more free RAM
Enjoy the cleaner rootfs (I have made some small modifications)
Download : http://www.mediafire.com/?1tbnyz2jmky
If any of you know how to enable chat in irc, please let me know.
BASICS:
Current Android boot from HARET which start from Windows Mobiles.
It consist of several components. Each of those is having unique functions.
1. STARTUP.TXT
Passing parameters to kernel which enable users to specify machine specific data
Current parameters including screen size, dpi, rotation, etc.
2. Kernel
The most important piece of code that enable everything to talk to the machine.
Developers here are most focus on this area as the other are greatly supported by google and other developers.
Kernel also determine what the hardware could do, and how it connects to other devices.
3. rootfs.img
This is the root of the linux, which initialize the OS. Especially running some startup scripts and mounting folder.
4. system.sqsf
The is the base Operating System of something call ANDROID. For others, you may considered them the basic environment of mobile Linux. For what we call CupCake / Donut / Eclair are stored here.
What we will be doing is to test out the features and bugs and locate the part of the about components affecting it.
Updated ADB howto:
Grab my base package.
Connect to computer before running Haret.
Wait until Android boot complete.
Install Google SDK USB drive for whatever device show up.
droid explorer or "adb device" to test.
If no device found, replug the usb cable.
This post would be updated with agenda drawing most concerns. We need your testing to see if you have any similar problems.
Agenda:
Top priority:
Device can't be wake.
Rear speaker always on.
This post would updates the testing items, and report the latest status.
Everything here are replaced with most recent findings and once more users confirmed, it moves up.
Do not believe everything in this post, but try falsify it. Reports in here would be presices to the level of component and versions.
So make sure you know what you are testing.
This post is a testing invitation, with trials and errors.
If someone raised an interesting phenomenon, we are going to invites members to test it. And the result format would be given as well.
This post may be changed from time to time to refect the new items needed to test (including the return format)
Now, let's kick start.
#1 To Test the base package in post 1
Return with following format.
Machine Type: BLAC100 (other devices are welcomed, but of course we are BLAC owners and would focus on it)
Test build: 2010.2.4
Radio: 1.17.25.09
WIFI ON: YES (WPA)
WIFI OFF: YES
Calendar / Gmail : BOTH OK
Google Voice: OK
Deep Sleep: YES (To test it, disable WIFI, Any USB, and press END KEY to sleep. If deep sleep is working, the system should not be up with key other than the power key)
Wake up: Crashed sometimes initially and get stablized later
ADB Connection: OK
Additional Package Installed: Facebook, dolphin
Suggestion: Replaced with kernel version xxxx would help to xxxxxxxxxxxxxx (if you found out how to make the build better)
#2 DEEP SLEEP AND WAKE
Please post your kernel version (or if you have no idea, the file name of the wifi module) if you found youself never had problem with sleep and wake (not yourself, but your blackstone android).
Lets begin this thread with a constructive approach to achieve our desired goal.
Will Post the feedback as requested.
Machine Type: BLAC100
Radio: Security unlocked 1.16.25.48 (Kovsky)
WIFI ON: YES (WPA)
WIFI OFF: YES
Calendar / Gmail : BOTH OK
Deep Sleep: YES but say after 10 minutes it wont wake-up.
Market: Working with downloads.
Additional Package: Facebook, Wifi toggle, Currency converter, Battery lite.
imtiyazee said:
Machine Type: BLAC100
Radio: Security unlocked 1.16.25.48 (Kovsky)
WIFI ON: YES (WPA)
WIFI OFF: YES
Calendar / Gmail : BOTH OK
Deep Sleep: YES but say after 10 minutes it wont wake-up.
Market: Working with downloads.
Additional Package: Facebook, Wifi toggle, Currency converter, Battery lite.
Click to expand...
Click to collapse
Thanks for your report. Developers is aware of the wake up issue of blackstone. It is however, seems still not fixed in the new kernel.
And Pierre-Hugues Husson would disable the deep sleep function (consume a little more battery) in up coming kernels, and we can try it on very soon.
mcdull said:
Thanks for your report. Developers is aware of the wake up issue of blackstone. It is however, seems still not fixed in the new kernel.
And Pierre-Hugues Husson would disable the deep sleep function (consume a little more battery) in up coming kernels, and we can try it on very soon.
Click to expand...
Click to collapse
Thanks for the update.
mcdull,
Brendan shanks has changed pid on kernel to "0c01", this should enable working with ADB without hacking the inf file.
This was deployed on Build: [email protected]_071547.
Let us know if this makes any difference for you, and whether HTC sync is now possible.
Thanks
It works perfect
hello,
I am using ANDROID_bLACKSTONE_TESTBUILD_20100125.ZIP & zImage-modules-20100129_022341 and it works perfect on my Blackstone till now.
Wi-Fi - OK
Synchronization with google account - OK
Sleep mode - OK
It is FAST
Call IN and OUT - OK
SMS - OK
this combination is best of the best till now what I tried.
eligius
Roadrunner100 said:
mcdull,
Brendan shanks has changed pid on kernel to "0c01", this should enable working with ADB without hacking the inf file.
This was deployed on Build: [email protected]_071547.
Let us know if this makes any difference for you, and whether HTC sync is now possible.
Thanks
Click to expand...
Click to collapse
AFAIK, HTC Sync will not work just yet. And I was not able to connect to ADB after the change. I need to test on some editing.
- Theory
As I already mentioned, the latest implementation of kernel prevent the proper installation of usb driver, and we need to fall back to old kernel to install the driver first (which the old kernel has 0c02 address).
Now, the modification has put the case into dead end. coz we can have no way to ask the computer to install a correct driver with 0c01 address.
In such case it is more difficult to modify the whole batch of driver setting then just the ini. I still have no go in using ADB.
The HTC Dream driver for windows seems works on ADB again.
As suggested by Brendan Shanks, you need to modify the "eclair.user.conf" (stored in the conf/ folder on your SD card), at the bottom, add this line to the custom_shells section:
echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch
And I have successfully to connect to ADB again.
mcdull said:
The HTC Dream driver for windows seems works on ADB again.
As suggested by Brendan Shanks, you need to modify the "eclair.user.conf" (stored in the conf/ folder on your SD card), at the bottom, add this line to the custom_shells section:
echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch
And I have successfully to connect to ADB again.
Click to expand...
Click to collapse
Thanks for that. I will try also.
Today, I started seeing the traffic animating 3G icon for the first time.
Great.!!
ADB working
Thank's mcdull ,using the Brendan Shanks method , ADB is working very well.
I'm using the 29-01 kernel and i changed the eclair.user.conf.
After that , the Droid explorer works well .
Bluetooth and GPS , the last frontier.
Regards.
cbolumar said:
Thank's mcdull ,using the Brendan Shanks method , ADB is working very well.
I'm using the 29-01 kernel and i changed the eclair.user.conf.
After that , the Droid explorer works well .
Bluetooth and GPS , the last frontier.
Regards.
Click to expand...
Click to collapse
Great. For others information, all needed changes and new kernel has been included in the latest package.
==REMOVED==
can some1 list what is working with this release of android and what isnt..thnx
WiFi don't go ON
In my blackston WiFi is not workng , anyone have some idea how i can solve this problem.
http://forum.xda-developers.com/showthread.php?t=630643
Check Out 7) (2nd post)
Hello everyone,
I am happy to inform all those folks who waited for a full Linux operating system on the HTC Kaiser PDA that today a little bit modified version of Zubuntu finally booted successfully on my HTC Kaiser.
It is a really in the alpha-state but it works, let's see what do we have:
TouchScreen: works perfectly with calibration
Screen: looks good. but programs doesn't support Kaiser's small resolution. You can fix this by using INTERPOLATION, but this makes picture quality a lot worse. To try it out edit the default.txt, find the mddi.height and mddi.weight values and change to for example 480 and 360.
Keyboard: works exactly as expected, some fine tuning with the keyboard map will be done
ScreenRotating
Not tested/not working:
WiFi (MY #1 ISSUE, TRYING TO FIX): I extracted the wifi section from an Android rootfs, successfully modprobed wlan.ko, dmesg shows that the driver is loaded OK, but:
Code:
iwconfig
tiwlan0: no wireless extensions
ifconfig tiwlan0 up
ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address
TI's WLAN_LOADER program didn't work either, so now I am moving to the other driver (wl12xx)
Bluetooth (Driver is there, no BT programs installed, couldn't test it)
3G
Cameras
Phone (NO dialer, nothing, however perhaps gsm-libs can help us firing it up)
Many many thanks goes for all these people form the #htc-linux IRC channel: randomblame, Markinus, ali1234, Ondalf and bombenbach for their outstanding support and help!
I would like to say thank you especially to phh for his awesome help and patience with me!
Click on the image for more pictures!
Stay tuned for: hopefully working WiFi, screnshots, YouTube-demonstration.
If you are interested, want to say thank you, want to help, or have an idea how to fix some things please write into this topic.
Also if you like my work, please consider a little a donation for me
After all, I am pretty sure now you want to try this on your own too, so here is the link for the Google-Code website. Download all the files and read the Wiki to know what to do.
http://code.google.com/p/kaiser-buntu/http://code.google.com/p/kaiser-buntu/
Link to RootFS:
http://www.megaupload.com/?d=ANRC94ON
Mirror (thanks to jmcbrother):
http://rapidshare.com/files/371631240/ubuntu_rootfs.rar
Mirror #2 (thanks to hoatienii):
http://www.mediafire.com/?uvytadoykyy
Want to be updated? Check out the project's Twitter page!
http://www.twitter.com/kaiserbuntu
Thank you,
DOMy
RESERVED for future additions
Reserved for future additions
great work . please upload link to test
Sweet that is great news! I can't wait to try it out!
Me wants the alfa link
This is so great!
Maybe we can find a solution at my hackersspace.
Great Work... Luv Linux.... Ported Android on Windows Mobile Device... Eager to port Ubuntu on Kaiser...
can you please share the Linux Beta link ...
Makes me almost wanna install Ubuntu on my PC.
Dukenukemx said:
Makes me almost wanna install Ubuntu on my PC.
Click to expand...
Click to collapse
me 2
oh……thank you……I wanna test……wait ……
Would it be destructive to flash it to nand at this point in the project?
I wouldn't count on it even remotely fitting on the NAND. Besides, you'll probably have to have half the apps on an SD card anyway...
how about a build that will work with the new nomorootfs installers so hose of us like me can try it without going back to winmo, Would like to install to ext2.img files or sdcard partitions.
And is this remotely close to the MER Linux build that progress seems to be halted on I was able to get it to work
working XWindow?
I wouldn't recommend installing it to NAND (it doesn't work so good, for example I didn't have time to test power/suspend).
Xwindows works perfectly (except the resolution issue).
DOMy
resolution issue. can you please explain that? (whats wrong in resolution) before i flash back to ,WM and try it
Michga said:
resolution issue. can you please explain that? (whats wrong in resolution) before i flash back to ,WM and try it
Click to expand...
Click to collapse
The problem is that the rootfs is not for the Kaiser and the Xserver uses some hardcoded resolution (that means there is no config file for it) so circa half of the windows are too big for the screen. It is not a big problem because you can move them around so it is easy to get to one of the corners and resize them so you can see the whole thing at once.
Fixing this is on my To-Do list
sorry for the dumb question but...
will this support phone???
no mention in the OP.
I assume no. (for now anyway)
mnjm9b said:
sorry for the dumb question but...
will this support phone???
no mention in the OP.
I assume no. (for now anyway)
Click to expand...
Click to collapse
Driver support is there, but AFAIK no frontend yet.
DOMy
mod: I found this: http://packages.ubuntu.com/hardy/comm/gsm-utils and this http://manpages.ubuntu.com/manpages/gutsy/man8/gsmctl.8.html perhaps I will try it later (or someone can try it and report)
This intrigues me muchly, but why ubuntu/debian based?
There are other, (and imho simpler), bases to build on, slackware springs to mind, and there are some tiny distros out there, which may also be worth looking at, to say nothing of the likes of Familiar, an interesting candidate for a non-android htc-linux.
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
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):
Hi,
I'm opening another testing thread for android development.
This thread aims at testing the diamond panel power up / down code that I've reworked.
It has been already tested on my DIAM100 with a sharp panel but I need some more tests on different diamonds. From what I've seen, the diamond 500 do not yet have any panel code but I need some diam500 users to confirm that with a small log.
THIS THREAD IS FOR PEOPLE WHO KNOW HOW TO USE ANDROID AND ADB.
Any feedback is welcome. If you're experiencing problems, please attach a dmesg log so that I can analyze the problem, otherwise I probably won't be able to do anything to help you.
People who wants to help but don't know how to make a dmesg log should start by searching for a guide on the forum. Once you've got adb working and know how to make a dmesg log, then follow the small instructions bellow.
Source tree : http://gitorious.org/~jbruneaux/lin...ux-msm-home-work/commits/htc-msm-2.6.27-panel
Logging instructions:
If you want to make a usefull dmesg log, then follow these few steps :
1/ Reboot your phone (that way, I can get the boot log, which contains tons of usefull debug outputs).
2/ Once the phone is booted into android, make a first dmesg log to ensure we have all the boot logging data
3/ Now, turn off / on 3 times the screen
4/ Make a new dmesg log
5/ Post the two dmesg logs along with a short description of the problem you encoutered (i.e screen does not power up or must be "forced" to be turn on by blind touching the unlock bar, ...).
Link to the kernel package : http://www.4shared.com/file/uIoHquR7/kernel_modules_diam_panel_2011.html
Just an idea: wouldn't you get a much broader reply if you create an initrd script that does all that logging stuft onto the FAT partition automatically?
virus if we lower screen resolution of diamond l480 x 640 in to 320 x 240 we can gain speed i dont know how to do it like james which is doing rhalp nand project did in ralp n gain speed as 36.5 in neocore like huawe u8150 hav same processor as diamond n running on 320 x 240 resolution ?? i was wondering if this is possible ppl tried but they are unable to find data sheet od diamond if u could help in this helicopter88 did lower but he dont know how to scale ?
xtremists said:
virus if we lower screen resolution of diamond l480 x 640 in to 320 x 240 we can gain speed i dont know how to do it like james which is doing rhalp nand project did in ralp n gain speed as 36.5 in neocore like huawe u8150 hav same processor as diamond n running on 320 x 240 resolution ?? i was wondering if this is possible ppl tried but they are unable to find data sheet od diamond if u could help in this helicopter88 did lower but he dont know how to scale ?
Click to expand...
Click to collapse
In fact, helicopter88 has already contacted me for this downscale but I don't have any clue on how it does work. Right now, my aim is not especially to get the diamond running faster but to improve the panel power on/off because I've got this fix for a long time now but before submitting it for the main tree, I must have some tests on different devices.
Maybe if helicopter88 or james have successfully reduced the resolution we can see how to make it available for all users if it really accelerate the global device speed.
Datasheet are not available for most of the components of our devices and qualcomm have protected all those stuffs with DNA and things like that. We have a few application notes but nothing really specific to one phone or one component. The only way we can work is with other official kernels and reverse engineering.
Regards, Jerome
I'd like to test this out,once i fix my phone...
No datasheet for our phone,is really hard to find what needs to be changed to scale the display..
this one consuming battery as i think and screen is pretty gud thn other kernls
hi Jerome
Nice work! thanks for looking in that matter ! That issue kept me from using android since it was quite a pain to wake the panel up !
Now the screen powers up pretty faster, even though i still see some glitches sometimes (but less than before) and seems like it's more difficult to power it on while it's sleeping (sleep mode is set on 1 in startup).
I'll do a dmesg later on, if I remember well, my diam has a toshiba panel..
DIAM100 using latest xdandroid FRX06
FRX06
mchh said:
hi Jerome
DIAM100 using latest xdandroid FRX06
Click to expand...
Click to collapse
Hi,
could you please tell me how to install xdandroid FRX06 on my diamond? On http://xdandroid.com i found only "ext2" zip package, i dont know how to use this...
thank you.
D/
Hi said:
http://xdandroid.com[/url] i found only "ext2" zip package, i dont know how to use this...
thank you.
D/
Click to expand...
Click to collapse
download http://files.xdandroid.com/FRX06_Full_Bundle_25.3.2011.zip
unzip in your SDCARD
select the startup for your device
and run haret
market
lqtdc said:
download http://files.xdandroid.com/FRX06_Full_Bundle_25.3.2011.zip
unzip in your SDCARD
select the startup for your device
and run haret
Click to expand...
Click to collapse
Thanks very much for bundle. I had some problems with running haret (it always does softreset after start..) but it seemed to be problem of energy rom, I flashed back stock rom and it works fine.
I had also problem with calibration but deleting calibration file solved id.
Now, android is running quite well, but I can't download anything from market. (It always says after while that download was unsuccesfull). I have google account, synchronizing with gmail works fine but market not.
Can you help me with that?
Thanks.