Database Develop

Linux BlueAngel WM5

i want setup Linux with my PPC.
i have some problem:
when I click haret-0.3.8.exe then Linux run.
Screen show stop at
Familiar login:root
and Password:rootme
~#
after login, i can't fdisk, because hard keyboard cant add "+31M" . "+" not show.
Who can help me add " + " charactor or telnet PC windows to PPC BlueAngel WM2005 by Haret?

How are you getting HAret to boot linux from WM2005?
From everything I've read and tried, it will only boot from WM2003.
If you have haret booting a kernel from 2005, what's in your default.txt file?

thingonaspring said:
From everything I've read and tried, it will only boot from WM2003.
Click to expand...
Click to collapse
It's not true for a long time. The problem was (as usual) the wince5 misreporting
device RAM size.
you need to set the ramsize variable (if haret does not know that BA uses 128M RAM) and use the "mem=128M" kernel command line parameter.

cr2 said:
It's not true for a long time. The problem was (as usual) the wince5 misreporting
device RAM size.
you need to set the ramsize variable (if haret does not know that BA uses 128M RAM) and use the "mem=128M" kernel command line parameter.
Click to expand...
Click to collapse
Yes I see, i add "mem=128M" haret Running good
after login by user : root
and pass : rootme
~# <== new command
Format SD-Card
Become root and create 2 partitions on the SD-Card
The first partition is for the kernel, startup scripts and bootloader. The second is for the GPE image. One of 30MB (for kernel and bootloader) and another (or rest of SD) for the GPE image.
fdisk /dev/sda
This exmaple assumes that /dev/sda is your sd card on your host.
If you only found /dev/sda1 insted of sda, that means that the card is already formated and contains a partition, in this case you need to delete this partition and create new ones
fdisk /dev/sda1
Press p to list the partitions and its numbers
Press d to delete a partition
Press w to save and exit
Then start creating the partitons on /dev/sda1
Press n to create new partition
Press p to choose type primary
Press enter to default to create partition starting from first cylinder for the first one, or right after it for the second one
Enter size of the new partiton ex: +30M
The first partition you crete (for kernel and bootloader) must be of type that windows understands, like FAT16 or FAT32, or else the card would not be read by the device at all
Press t to change the partition type from "83 Linux" to "c FAT32"
Press w to save and exit
Click to expand...
Click to collapse
i cant add " + "charactor of new partition +30M by hard key BlueAngel.

yoz what is the reason for linux on this...
phongred said:
Yes I see, i add "mem=128M" haret Running good
after login by user : root
and pass : rootme
~# <== new command
i cant add " + "charactor of new partition +30M by hard key BlueAngel.
Click to expand...
Click to collapse
Why would you want linux on a ppc, I mean I know apple just released their joke of a device in vegas (I was there) but what software are you going to use for linux on a BA? Is it to say that you have linux on your device, or? Do tell my brothas!

you are look here:
http://handhelds.org/moin/moin.cgi/BlueAngel

phongred said:
i cant add " + "charactor of new partition +30M by hard key BlueAngel.
Click to expand...
Click to collapse
You can save yourself a lot of trouble if you'll use an USB cardreader on a linux machine.

BA_Flash_GOD said:
Why would you want linux on a ppc
Click to expand...
Click to collapse
They are many reasons. Security, stability, access to >32MB RAM for
one process, etc.
what software are you going to use for linux on a BA?
Click to expand...
Click to collapse
The same i use on my Motorola A780,
which has Linux CoPilot GPS route planner by ALK preinstalled.

Now can you help me setup Linux with o2s wm5? begin to end. thanks

I'm a long-time unix/linux user and I've always been intrigued by this linux port. Does it do the following:
make calls
activesync (or other outlook sync)
wifi
gprs
VNC Client
SSH Client
If it does all of these, I might just be up for jumping aboard. Is the switch-over a one-way thing, or can you go back to Windows Mobile?
Finally, is this still under active development by anyone?

cr2 said:
They are many reasons. Security, stability, access to >32MB RAM for
one process, etc.
The same i use on my Motorola A780,
which has Linux CoPilot GPS route planner by ALK preinstalled.
Click to expand...
Click to collapse
Is that it, software wise.. and security?? Why would anyone want to hack into an aging BA? Not trying to offend just asking valid questions

[Q] [BOOTANIMATION]Removing it and showing the standard linux kernel messages

Well like the title states, I would like to see the kernel messages instead of a boot animation. Just for the geeky look of course ^__^
So is there a way of doing that?
I'm using a German Vodafone Magic 32B, running Cyanogenmod 5.0.8.

I think you can't put the boot in verbose mode, you could do an animated sequence with PNG files to emulate the verbose mode but it won't be the real boot messages of course, just images

Yeah I'm using a boot animation that imitates the BIOS POST-screen on a PC, it's nice but the verbose mode is much cooler
The boot animation I'm using:
http://forum.xda-developers.com/showthread.php?t=648555
What I'm after:
http://www.youtube.com/watch?v=HQKfeDnMVQ8 (about 2 minutes into the video)
If there was a simple setting in a configuration file, it would be awesome, if it required modifing the boot loader, it would suck

From what I understand, you need to change the init.rc file in \
setprop ro.kernel.android.bootanim 0
setprop debug.sf.nobootanimation 1
or simply change export ANDROID_BOOTLOGO 1 to export ANDROID_BOOTLOGO 0 also in init.rc
However, all changes to init.rc are gone after restarting the phone....
Any ideas?

Hm, it seems like the init.rc we see in our rootfs is part of a ramdisk. A ramdisk created from an image in our boot image, i guess a modification of the boot image would help the cause, but that's way too much trouble

quazar666 said:
From what I understand, you need to change the init.rc file in \
setprop ro.kernel.android.bootanim 0
setprop debug.sf.nobootanimation 1
or simply change export ANDROID_BOOTLOGO 1 to export ANDROID_BOOTLOGO 0 also in init.rc
However, all changes to init.rc are gone after restarting the phone....
Any ideas?
Click to expand...
Click to collapse
I modified the boot.img with the first changes but it just broke it. Apparently the setprop method won't work. I'll try the export suggestion sometime in the next couple days and report back.

Awesome, thanks for trying

No problem. If I get it working I'll post a tutorial on how to rebuild the boot.img to do this. I'll also post a premade boot.img for the latest CM release candidate.

Any news ?

nattiii said:
Well like the title states, I would like to see the kernel messages instead of a boot animation. Just for the geeky look of course ^__^
So is there a way of doing that?
I'm using a German Vodafone Magic 32B, running Cyanogenmod 5.0.8.
Click to expand...
Click to collapse
What you want is this http://www.youtube.com/watch?v=7u6qNzsgbxY
As you indicated yourself.......they are messages from the kernel. You would need a kernel that's verbose instead of having a logo.rle. Kernels have specific headers & hashes so its really hard to just 'add' or 'remove' stuff inside. You would need to compile a special kernel to achieve this. I'm pretty sure the permissions & logo.rle are in the initrd which is 1/2 of the Boot.img alongside the zImage. Hope that helps

Any updates on this? This would be killer!

92drls said:
Any updates on this? This would be killer!
Click to expand...
Click to collapse
Try chainfire's "live dmesg" and " live logcat" boot animations, should be available on the market
Sent from my HTC Desire using XDA App

I just tried the live dmesg. That's absolutly brilliant! Thanks for the tip!
Sent from my XT894 using xda app-developers app

[Q] Screen calibration is way off - Have tried to delete calibration.txt

I installed the Android with the below version:
Android 2.0.1 Eclair (kernel13 (Topaz/Rhodium-only) by Markinus, composed by Shadowline on January 8th 2010)
Everything runs properly and able to boot up, but I do not get the screen calibration which everyone says that we have to tap 5 points (similar with Windows). And my screen now is way off. i.e. to hit "I", I must hit "K" in the keyboard.
Reading from other forum, I have tried to delete the calibration.txt but then it doesn't get recreated. Now, I don't have any calibration.txt anymore.
My default.txt is:
set MTYPE 2293
set KERNEL zImage
#set FBDURINGBOOT 0
set initrd initrd.gz
#pwf dm.txt 0x8e0000 0x20000
#pwf smem.txt 0x01f00000 0x100000
#msmts_calib=0x376.0x3c1.0x6a.0x8a
set cmdline "msmts_calib=0x395.0x3d5.0x79.0xa0 msmvkeyb_toggle=off WiFi.mac=00:23:76:0C:35:AD lcd.density=240 mddi.width=320 mddi.height=480 no_console_suspend"
#mddi.width=320 mddi.height=480
boot
In summary:
- No calibration screen during the first boot up
- Deleted calibration.txt in attempt to recreate a new one, still no calibration screen
- Deleted data.img, no calibration screen, it goes straight to the screen where you press Android (green color) and on the bottom showing Emergency and Next
- Tried other value for msmts_calib= from another thread that reports to be near perfect for Topaz, but not working on mine.
- Deleted the line msmts_calib=0x395.0x3d5.0x79.0xa0 from the default.txt but it made it worst, I can't tap on anything.

Hey Bankir. Restore evrything from your root, which means all the stuff like command lines from startup.text etc. otherwise I could share the link of ADAndroid with you. ;-) With FRX04 they got nearly a completely working Android version 2.2.1!
http://forum.xda-developers.com/showthread.php?t=509493

[Q] Bad performance CWM Honeycomb Froyo V3

Hi,
I installed the above build on my Sony Ericsson X1,
Im getting really poor performance, after quite a while of trying I managed to install Android System Monitor, I notice my processor is running at 57.6Khz 100.2% of the time!
I read that this build is pretty quick...
within the frequency stats it shows:
-122.88Mhz 0.0% (0)
-245.76Mhz 0.0% (0)
-320.0Mhz 0.0% (0)
-480.0Mhz 0.0% (0)
-57.6Mhz 0.0% (100.02%)
I think this could be my problem....
in my startup.txt file I have the following:
set ramsize 0x8000000
set ramaddr 0x10000000
set mtype 2006
set INITRD_OFFSET 0x608000
set KERNEL zImage
set initrd initrd.gz
set cmdline "rel_path=npkboot fbcon=rotate:2 ro.sf.hwrotation=180 lcd.density=240 msmvkeyb_toggle=off msmts_calib=0x0366.0x04b.0x0c8.0x038e clock-wince.grp=0xa92 acpuclock.oc_freq_khz=650000 pmem.extra=1 no_console_suspend physkeyboard=kovsq msmsdcc_1bit msmsdcc_fmax=14000000 hw3d.force=1 acpuclock.force_turbo=1"
boot
Someone please help!
this is the exact thread i followed:
http://forum.xda-developers.com/showthread.php?t=1156421
Making sure I have created the partitions correctly.
the only thing I did change was the order in which the partitions, otherwise I couldnt access the fat32 partition to copy the files.
I did try the Turbo kernel which didnt make any difference.
I have tested the card and its fine, i have used this for other builds on a Touch pro 2 and it worked fine.
This was ran the same before I installed the gapps.zip using clockwork mod.
I managed to get it to boot up really quick once, it really was flying! then it rebooted..
since then it doesnt even boot, im trying to step the CPU down as much as possible. on the thread it recommends 614000khz but I have gone down less that 600 and its still crashing and re-booting.
I might leave it a while incase its a heat issue, and let the cpu cool...
Any help would be greatly appriciated!
thanks in advance.

acpuclock.oc_freq_khz=650000
you can make it small.576000-624000 is enough,and I didn't install gapps.
but my keyboard sometimes can't work, what about yours

Honeycomb Froyo V3
Had the same problem, massive heat problems and poor battery life with this build, now using NAND CM7 Gingerbread, much better, much more stable

compiling kernel for N920C. boot.img won't work

Hey guys,
I have been trying to compile the N920C 6.0.1 from the source. Just one time the kernel worked but only when I didn't change anything in menuconfig. If I change even a word in kernel it wont boot up. What am I doing wrong?
My source file : SM-N920C_SEA_MM_Opensource.zip
My firmware file : SM-N920C_N920CXXU2BPB6_CAM_HiepGia_Samsungviet.zip
I was using NDK for toolchain and Linaro. May there be something missing like a tool or may the toolchain be wrong??
"gcc-linaro-4.9-2015.02-3-x86_64_aarch64-linux-gnu.tar.xz" && "android-ndk-r11b-linux-x86_64.zip"
My Makefile setting was like:
Code:
ARCH ?= arm64
CROSS_COMPILE ?= /root/Desktop/ndk/toolchains/aarch64-linux-android-4.9/prebuilt/linux-x86_64/bin/aarch64-linux-android-
After make cmd the output file comes non-compressed called "Image" which is in "arch/arm64/boot/" . Does it make any difference since its not compressed like zImages ?
What is the correct process for converting Image file to boot.img. I have tried both "mkbootimage" and "abootimage" any other way to make boot.img ? Which one is more suitable for my situation?
The process I'm doing is:
Code:
1-)Copy toolchain and source to Kali
2-)Extract kernel source and edit Makefile(for cross_compile)
3-)make ARCH=arm64 ******.defconfig
4-)make menuconfig && save && exit
5-)make ARCH=arm64
6-)Copy "arch/arm64/boot/Image" to another directory
7-)Extract original boot.img from firmware file and then "./split_boot boot.img" with mkbootimg tool
8-)Replace the old kernel file from the boot.img with the new one
9-)Edit /ramdisk/default.prop ====> ro.secure=0 and save
10-)compress ramdisk to gzip
11-) ./mkbootimg --kernel /boot.img-kernel --ramdisk /boot.img-ramdisk.cpio.gz --board SYSMAGIC000KU --base 0x10000000 --pagesize 2048 --ramdiskaddr 0x11000000 -o newboot.img
12-)Tar the newbootimg to flashable zip
13-)Flash it with odin.... Voilaaaa phone won't boot up. Stuck at Samsung Galaxy Note 5 screen:)
What is wrong here?
Please don't tell me to search in forum I have read all of the threads about building kernel. Each one is different from the other so I wanna know what is more suitable in my situation
I know I have asked to many questions but I would appreciate if someone could help me through IRC or some instant messaging service

noone knows ?

Come on guys I have still been waiting for an answer. There are already kernels made by other people in this forum so it must be possible

dewctr said:
Come on guys I have still been waiting for an answer. There are already kernels made by other people in this forum so it must be possible
Click to expand...
Click to collapse
in my opinion it s a problem related to the 'initrd' file..i m diving into chime for now and stucking ; let s converge our efforts to fix all issues with kernel compilation, if u r intressted just pm me.
for info:
initrd provides the capability to load a RAM disk by the boot loader.
This RAM disk can then be mounted as the root file system and programs
can be run from it. Afterwards, a new root file system can be mounted
from a different device. The previous root (from initrd) is then moved
to a directory and can be subsequently unmounted.
initrd is mainly designed to allow system startup to occur in two phases,
where the kernel comes up with a minimum set of compiled-in drivers, and
where additional modules are loaded from initrd.
This document gives a brief overview of the use of initrd. A more detailed
discussion of the boot process can be found in [1].
Operation
---------
When using initrd, the system typically boots as follows:
1) the boot loader loads the kernel and the initial RAM disk
2) the kernel converts initrd into a "normal" RAM disk and
frees the memory used by initrd
3) if the root device is not /dev/ram0, the old (deprecated)
change_root procedure is followed. see the "Obsolete root change
mechanism" section below.
4) root device is mounted. if it is /dev/ram0, the initrd image is
then mounted as root
5) /sbin/init is executed (this can be any valid executable, including
shell scripts; it is run with uid 0 and can do basically everything
init can do).
6) init mounts the "real" root file system
7) init places the root file system at the root directory using the
pivot_root system call
8) init execs the /sbin/init on the new root filesystem, performing
the usual boot sequence
9) the initrd file system is removed
Note that changing the root directory does not involve unmounting it.
It is therefore possible to leave processes running on initrd during that
procedure. Also note that file systems mounted under initrd continue to
be accessible.
---------- Post added at 12:26 PM ---------- Previous post was at 12:18 PM ----------
did u try with latest ubertc toolchain with latest gcc 5.3 compiler?
pm me for info

it is nice to see that someone has also been interested in this thing. Even though Im interested in it, unfortunately, my knowledge is not even a half of yours. I'm not sure how I can be helpful for you but if you ask me things to do, I am ready to apply them. I can try to be helpful with your assistance
Do you want me to try with the toolchain and GCC you mentioned above?
BTW I got it working once without doing any change in defconfig but I don't remember which toolchain I compiled it with. I don't get why it doesn't work when I do changes.