yashsingh1/xdaforums huggingface dataset:
[HTC Excalibur] phatmanxxl:
Mine did the same thing, the solution...turn it on silent and vibrate. I never did find a fix for it. You must be running kavana 6.1.
[HTC Excalibur] Jimmythebest:
That just happen to me when I put a mp3 ringtone, when It's windows' default tones that does not happen... I was running kavana but now I'm running EVO WM6.5

Is there anyway to set a mp3 as msg tone properly????
[HTC Excalibur] stylez:
If useing an .mp3 for message tone then you will have to edit it as WM devices play the whole tone on message...
[HTC Excalibur] Jimmythebest:
How do I do that stylez???
[HTC Excalibur] stylez:
With an Audio Editor a good free one Audacity so what you want to do is cut the sound down to a more reasonable time ;)
[HTC Excalibur] Jimmythebest:
Thanks... ah, I forgot to say that I kept repeting the tone many times, for me to stop that I had to turn the phone off...
[HTC Excalibur] LiverpoolFCfan:
It is probably due to Notifications from the AutoKeylock program that is installed by default.

Go to

Start-> All Programs -> Tools -> Auto Keylock

and uncheck Notifications.

This is basically a way to remind you repeatedly of any missed calls/messages/etc. If you like the idea of being notified, you can press the right soft-key for Options, and select Notifiications to configure them as you want.

Hope this helps
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
First reply!

this is relevant to my interests. I'll take a look. I remember seeing that Maemo was made on top of Gnome. Do you know if there's a chance to get Debian apps on here? That's the big thing for me to get me working on it-- some type of desktop compatibility. Having an X-server is perfect. Looks like you're saying the resolution issue is purely theme based? How open are the devs for it for suggestions and feedback?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] burtcom:
2nd reply :)

This does sound cool :cool:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ruizit0:
already made some read about this in the new nokia n900..

its cool.. it free.. but i dont like the ui :\

lets see where this goes.. but.. for now.. for me... android (L)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
Ok, just saw it's Jaunty based which is what I've been looking for in a phone.

Is there a list of features/bugs/issues and what's been developed so far? Seems like if the kernel brought to us in part by dzo will work maybe it won't be so hard to get wifi and other features working. A list is good.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] poly_poly-man:
I'll admit I haven't put much effort into it, but at this point X won't work, for one thing - probably have to change the resolution in a config somewhere.

Indeed, most of the hardware should be fine - I imagine, for example, once we are able to load the firmware, wifi should be good. Some code will have to change (a few things are built android-specific in the kernel), and some of the RIL stuff especially (phone, data, etc.) will have to be ported by someone who has that code and some time.

Indeed, Mer is Ubuntu-based, and so, according to their site, 95% of ubuntu apps should work perfectly. This is really nice for getting software on (aren't just limited to any applications in an app store or market.).

At this point, all we need to do is everything :D .

I'm going to try now to disable X and see if I can't get a few more things working.

EDIT: in response to your question about how open the mer-folk are to suggestions? The idea that I got from talking to them was that they are more than happy to get this extra help, and since they are trying to bring this to more devices, they are willing to put up with our requirements, to make this more readily available in general.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] poly_poly-man:
Alright, as I edited, I got some more success.

By removing the splash calls and the X starting, I can get a terminal. I edited the /etc/shadow file to have a password that I knew for root. Now, I can log in as root on the console (/dev/tty1).

I tried to start X, and I'm getting some strange framebuffer errors.

I'll keep you posted.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DaveTheTytnIIGuy:
Wow, if we could get this working, it'd be sick! Thanks for posting, formatting now.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] hypest:
with all the hard work already done for the Android port, seeing devs being interested in Mer is REALLY PROMISING! Waiting for Google to open up Android even more, is frustrating...

Porting Mer and thus having a REAL linux (kernel+software stack) is what we need to leverage the dev capacity of the great XDA community. At least, this is what I feel like :).

Owning both a Kaiser and 2 N800s, I'll probably try out the stuff posted here... I was keeping an eye on Mer for my N800s anyway, but using it on the Kaiser is more triggering ;)

so devs, have courage and good luck!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mysteryvortex:
Frame Buffer and X server

Unfortunately I've been quite busy lately and haven't been following the Android development as closely as I would like. (I don't think I've updated my git repo for months)

If I remember correctly, the frame buffer code in the kernel wasn't finished. That would prevent X from running. Can anyone say whether that was completed? I just wanted to mention this in order to avoid people wasting their time if it is in fact the problem.

It would be great to *eventually* see X running with hardware acceleration, can anyone point me to info about how DZO got that working? Was it reverse engineered, or did he figure out how to make some binary blob happy?

It will be nice to have some choice of Linux based distros the Kaiser and Vogue. Keep up the good work everybody, I appreciate it!

-Mysteryvortex
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] garringm:
I've been looking at the n900 for quite some time just waiting for its release to the US next month. I know nothing about developing but I am very excited about this one, and I hope that there is a quick start to the apps that are put out for it. I was curious myself as well at how this would port to the kaiser so I could get a good hands on before I went and bought one. I would be more than happy to be a tester. I bought an iphone cause cause the little green guy is really starting to piss me off and my tilt's about to give up the ghost. I quickly gave it to my wife as the signal strength and battery life just sucks so I hope this maemo can give me what I want
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
mysteryvortex, Android does not use an X server at all. This was my disappointment when issues arose trying to run Ubuntu in a chroot. This is different though. We should be looking at troubleshooting the X server as top priority I think. The rest should flow. Bear in mind the kernel for Android, like I said, has nothing to do with X compatibility since Android uses its own display so the kernel should need some serious work.

poly, is the build you linked to hardware specific? Looks like a generic one. If so, then the only outstanding difference should be the kernel and if that's the case we should be able to use this on any phone we happen to have a kernel for right?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] poly_poly-man:
The build has a kernel and stuff, but don't use it. Use the regular stuff from android (or build yourself from htc-vogue).

mdrobnak from irc got mer up on his raph - thanks to the vga screen, with a quick kernel patch and some xorg.conf modification, he got X working great.

Within the next few days, I'll do some tests of the data connection and such.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mysteryvortex:
Yes, that's correct. Android doesn't use X. Many, many months ago, it was mentioned that the framebuffer in the Vouge/Kaiser kernel (which X will use) was broken. Nobody was planning to fix it since Android doesn't need it. I was just trying to point people who have time to work on supporting our phones in the right direction.

poly_poly-man: Looks like the Raphael kernel is being developed on another branch, but it sounds like the FB patch helps us?

-Mysteryvortex
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Borkata81:
poly_poly-man,

I have setup my second partition of sdcard to 512MB and extracted there Mer preserving permissions.

What I did also is to modify the x config and change resolution and also resize the Mer-logo.jpg so it fits.

After I tried to boot I went successfully through all steps (at least I think so) and a blank screen appeared to me.

Can you tell me what was the parameter to output the Haret boot sequence to a file, so I can check what passes and what fails?

Another question: The following "mknod /dev/fb0 c 29" have to be performed on root of second permission, right? If so I think the command should be ""mknod ./dev/fb0 c 29", am I correct?

Regards,

Borkata
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] toasty_:
'./dev/fb0 c 29' does only work if you are in "/" (root of the filesystem) otherwise (and in all other cases) 'mknod /dev/fb0 c 29' is correct.

bye...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] poly_poly-man:
It seems that even set to the right resolution, our fb does not work with X. Needs more patching than just the patches I got from the other branch. We may need to move up to the other branch, I'm not sure.

the /dev/fb0 should be replaced with /path/to/sdcard/root/dev/fb0, of course. And it's better to just get rid of all the splash references - that way, you don't get the blank screen issue.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Borkata81:
Yes, but poly has written that user have to be in root so that was what I have asked ;)

Question: our fb driver is msm_fb?

poly can you share which patches you tried from raph branch?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] toasty_:
Oh yes, you're right. I should first read the full post before answering questions that havn't been asked
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] poly_poly-man:
http://people.openezx.org/tmzt/

the msmts and vres patch. Didn't work, because there are more problems in our older kernel.

I'm interested in finding out why we aren't on 2.6.27 already...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
Well, at the gitting tree they are still updating and some are backports from the 27 kernel. There's mention of trying and crashing with it on our phones and the focus has been to make a better working kernel before moving into an unstable area of develoment. On that note, any info on making a kernel for our phones that isn't via Android's SDK?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] poly_poly-man:
the kernel has never been done through the sdk... just git pull the source tree, and make. Make sure you have a cross-compiler (which the sdk can give).

The RIL is done through the sdk. We can't do a direct copy, because the API is going to be different (not that there is one for mer yet...). If we act now, we might be able to influence what it looks like :P

The manual data attempt I made the other day failed. I hope that I get that working somehow, just to prove I can.

And, if you're a dev and bored, please work on fb.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
I have the framebuffer almost working. X will start but only show through DDMS or VNC and will not update the device's screen. This is running on :0 meaning it's successfully taking over the main display and it's not running in a window like before. That may or may not be a big deal but I need help with that. At any rate, with a kernel I made, I'm this far:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] poly_poly-man:
First of all, make sure the X server is running at 320x240. It's better to have it work that way than to scale...

secondly, what you've done is great, many thanks.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
I don't think it's got a resolution defined (maybe) as it's not apparently respecting xorg.conf due to the errors. I think the screen is the size of the client connecting. On the device itself, all I got was the wait cursor and the background of the login screen but that was a single frame. The rest is all through VNC connecting to localhost:0 (forwarded to my desktop).

I'd post a diff for the kernel I'm working with but I don't see the point yet, same with Ubuntu Karmic that I've painstakingly installed Hildon/Mer on but it's coming together slowly.

I guess a wise move would be to first work on the module version issues. Xorg log and dmesg are attached. I made the functions that throw errors verbose and added printk's to show what is being called.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Magister2k7:
enatefox, try this kernel - X should work (tested on Xfbdev from Angstrom linux).

It's an older build (from 2009-08-24), with small fixes. If it's ok then I'll try to do the same with latest kernel and push changes into git.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Magister2k7:
Well, it's not working :(
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
So what's needed to add the ioctls? You said you had Linux already working before? I hadn't had time to test the kernel you posted but can you upload a diff? It shouldn't be impossible to add support to the driver but I'd need some help. I had no luck with Mer but installed the UI on Ubuntu Karmic which might give more flexibility.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Magister2k7:
Forget about ioctl's, I was wrong.

Here is a kernel, on which Xorg is working. I was able to run setup wizard (through controls were very-very huge!), but desktop closes just after showing "Mer" button.

A patch to current source is very simple:

diff --git a/drivers/video/msm/msm_fb.c b/drivers/video/msm/msm_fb.c
index f1804cc..7b221bd 100644
--- a/drivers/video/msm/msm_fb.c
+++ b/drivers/video/msm/msm_fb.c
@@ -618,10 +618,11 @@ static int msmfb_refresh_thread(void *v)
while (1) {
msleep(50);

- if (num_registered_fb > 0) {
+/* if (num_registered_fb > 0) {
fb = registered_fb[0];
msmfb_update(fb, 0, 0, fb->var.xres, fb->var.yres);
- }
+ }*/
+ msm_update_screen();
}

return 0;
@@ -681,7 +682,7 @@ static int msmfb_probe(struct platform_device *pdev)
info->var.xres = pi->width;
info->var.yres = pi->height;
info->var.xres_virtual = pi->width;
- info->var.yres_virtual = pi->height * 2;
+ info->var.yres_virtual = pi->height;
info->var.bits_per_pixel = 16;
info->var.accel_flags = 0;

--

Just pushed a patch to htc-vogue branch.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Magister2k7:
It's working!

It's working!

To make it run I had to set 640x480 resolution, and with my kernel it booted ok! With 320x240 Xorg starts up, but desktop crashes :(

Also, it is possible to enable rotation by editing xorg.conf, but then touchscreen works incorrectly.

Here are some screenshots, taken with builtin screenshooter.

And one more thing... it eats too much memory! From mine 64 Mb only 1-2 are free prior to X startup, so it's a bad idea to use Ubuntu as a base for embedded systems. I was forced to add a swap file to run this system.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] alextytan:
a noob question, because i'm new at linux...

how do you start mer?

from windows by run the default.txt in haret?(can i have a default.txt to see how it's configured), or from android? and how. thnx
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
Hmm, I manually applied those patches before but no go. Must have been user error then I also did a couple of other things too. Who knows.. also I was running X within a chroot as well and not Mer but Ubuntu with Hildon manually (you have no idea how much work that was) installed. Anyways, good job with getting it going.

I'll try it out and see what happens. Mer is rather heavy but I bet we can speed it up if it will "just work" first.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Magister2k7:
Maybe you just forgot to enable refresh thread in kernel config?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] alextytan:
default.txt

could sb share his default.txt?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Magister2k7:
So, I created runnable from SD card Mer linux package.

Unpack it to "mer" folder on SD card, and run haret.exe from it.

all files should be in a 'mer' folder, otherwise it won't work!

Download here
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] alextytan:
thnx a lot. it worked
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DaveTheTytnIIGuy:
Wow that's awesome, thanks! Even though a lot of stuff didn't work, this looks really promising and I hope to see future releases. Again, thanks for sharing
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Borkata81:
Hi there :)

Thanks for the framebuffer patch man ;) I was waiting long time for this one :)

I make tests with partitioned sd card, but would like to check your build that you have uploaded. The problem is that depositfiles are too slow and I am trying more than 10 times now to download, but connection often brakes and I cannot download. Can you please mirror the zip?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Magister2k7:
My build uses readonly squashfs rootfs image and read-write ext2 image combined together with unionfs (added a patch), plus touchscreen driver is pathed to allow screen rotation - so Mer works in landscape.

And about depositfiles - sorry, but I do not have unlimited internet for now, so ask someone else to mirror.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
Mirrored. I haven't tested it (yet) myself. I will keep updates and related files in that folder as people offer them or I can figure out things on my own. Thanks for the bundle, now I can hopefully do what I'm better at to help get this going further.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] czarnas:
Wow, awesome, actually testing it.

I have little problem, dunno why, but touch is flipped. When i touch to right, cursor goes to left, and same up and down. Maybe i done something wrong?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Magister2k7:
Set htckaiser-ts.rotate=1 in yours default.txt istead of 3 and try again.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] casacristo:
I tried it but the 'mouse' behaves erratically, like the touch screen has both the X and Y axis inverted. If I touch on the lower left corner then pointer jumps to top right, etc
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Magister2k7:
Hm... then try to set Option "Rotation" "cw" instead of "Rotation" "ccw" in /etx/X11/xorg.conf - so screen will be rotated in another side.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
Magister2k7, thanks for all your help. I haven't gotten it to boot yet and been a little busy irl to go over it but when I have time I'll see what I can do.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] KeizerBAAS:
This look cool.

I noticed that opening the keyboard sets the x/y axis orientation oposite, closing the keyboard fixes it.

This is when the htckaiser-ts.rotate=1 in default.txt

Any progress or updates?

Mobile broadband connection failed after I tried to set it up and when installing it there was an error regarding wifi, so no connectivity...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] WM-Sef:
@Magister2k7

Can you make a version for the Topaz to? The zImage is allready there, so you just need to implement it. Are you down? Link (download the first package, I think all files you need are in there)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bambooo310:
Is it practiclly usable for day to day life, i wanted to try it on Kaiser.???

can somebody who have tried this answer please.:)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] garringm:
Not from what I have seen, all I get is the desktop with a weather app, no phone not data nothing. Looks great though can't wait for further development
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] JesusFreak316:
Anything new going on here? It's been over a month since the last post. I wanted to see if I could get this to work on my Fuze, but the downloads on the testing link are down. Would any of the stable releases work or maybe some of the .17 testing?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] idumych:
I am also very interested in this. I didn't even know anyone got X11 working on Kaiser!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] JesusFreak316:
Well, I downloaded Magister's package and am trying to figure out what to put in my default.txt I have the android startup.txt from Babijoee's work on Android for Raphael. However, I tried editing my ram size and mtype stuff in Magister's included default.txt for kaiser and haret just hangs at saying booting linux and I never got to the actual command line stuff. Would it be okay if I create a thread in the Raphael forum to try to continue this?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Borkata81:
As long as I know, nobody is working on this at the moment.

JesusFreak you have Kaiser or Raphael?

As long as I remember kernel with x11 support was first compiled for Raphael by someone.

Magister just did the work to apply patches and fix it to work for dzo's kernel.

If you want to test newer version of Mer you just need second partition formated to ext2 on your sdcard and extract content of rootfs tar there as described in first post of this thread. Then in the default.txt you have to set to boot from the second partition, i.e. add "root=/dev/mmcblk0p2 rootwait" to the kernel cmdline.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] garringm:
has there been anything new added since I tried all that was there then was a weather widget not even a dialer.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] JesusFreak316:
Yeah, I have a Raphael. I am interested as supposedly MDrobnak got it running on his Raph as Poly-Poly-Man said on page 2 of this thread. Maybe I'll try to get in contact with him. I would do what the first post on this thread says but the testing 0.16 rootfs gives a 404. I downloaded the stable version so hopefully that will work. I guess I'll just have to try it to find out. I'm gonna start a thread on the Raph forums; if anyone objects pm me or just post on the thread and I'll stop. Not sure why anyone would care, as I'll be giving credit where it is due, but just in case.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jwte:
Mer on x1

I can run the Q5 Mer on my xperia :):):)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] rckhndphil:
Bluetooth

Anyone know if the bluetooth in mer is working on the kaiser?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Borkata81:
No it's not working.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nooor7772000:
great work guys i manged to run it in my kaiser but

is that maemo??

it show me ubuntu 9,04 for arm v61

so what that mean???

and is there way to open my sd content in it ,,no file manger there??

is wifi?

gprs??

working????

if it were not maemo so how to use maemo in my kaiser?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] OndalfStardust:
You totally took wrong build then. This thread is for Mer (a test version of Maemo), which doesn't work according to posters here. You could only dream about WiFi and dataconnections since no-one is doing these currently since everyone is concentrating into Android. As I said, no way to run Maemo on your phone since even Meego hasn't been ported to run on Qualcomm processors. Or atleast, if ARMv6 boots or starts, it'll be slow since no accelerating processor extensions used. And there will be no TS, Wifi, etc. since no kernel adapted for Maemo yet afaik.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] love.me:
if my dream come true,,it'll become a miracle then ^^

use maemo on kaiser only dream after all
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nooor7772000:
thanks in advance but could you post me link for the source of maemo to run in kaiser,i will try it.and steps if you not mind

thanks