yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] ajbopp:
Coreplayer used to work pretty well for me on my Vogue, but lately the video has become so choppy that it's unwatchable. It doesn't seem to matter much what video or resolution I'm watching. I have no idea what changed and I'm looking for some tips on what to look at. Currently I use RawFrameBuffer and pretty much everything else is, I think, the default.

The interesting thing (to me at least) is that the video is very smooth as long as I select Benchmark from the Tools menu. No dropped frames at all.

Anyone have a clue what I should try adjusting?
[General Questions and Answers] nir36:
If it changed all of a sudden maybe it's a device issue. are you running any new services or apps?
[General Questions and Answers] ajbopp:
I wish it were that simple. If anything I'm running fewer. I have fewer things going on now with my device than probably since I first bought it 14 months ago.
[General Questions and Answers] nir36:
So what you're saying is (just so i can understand) that you had the Vogue and everything went well with CorePlayer. And now, after 14 months of use, with few programs running, it's slower for no apparent reason?

Did you perform a hard reset/flash a rom since you first got it?
[General Questions and Answers] ajbopp:
Not exactly. I'm saying that something obviously changed, but I'm not sure what or when. I do remember that it behaved something like this when I first installed it 14 months ago, but I changed some settings and it worked better. But I've forgotten what those settings were, so I guess I'm asking for people's views on optimization.

As for hard resets, yes, I've had several, but always been able to restore from backup not more than two weeks old.
[General Questions and Answers] nir36:
when you restored from the backup.. did you also restore the same CorePlayer installation? i'm trying to figure out if it's a HW problem or with CorePlayer
[General Questions and Answers] ajbopp:
I believed I restored the coreplayer files and settings just about every time I've needed to do a restore. Coreplayer is on a storage card, and I've found that every so often WinMo corrupts the file system on the card, so I back up all of the Program Files folder there, as well as everthing in flash. Personally I think it's a software problem, or Coreplayer wouldn't be playing the moving fine in Benchmark mode.
[General Questions and Answers] Jed Dignazio:
Why wouldnt you just delete and reinstall coreplayer? Reseting all settings?
[General Questions and Answers] ajbopp:
Because I'm old and my memory is gone. Altzheimer's is creeping up on me. I do not remember what settings I changed or how to get good performance all those months ago, therefore reinstalling is not likely to have any positive effect. I already know that the default settings (for which there is a button to press in any case) will give me unfortunate performance.
[General Questions and Answers] sharonbacon:
Coreplayer 1.2.5 help playing wmv files from BBC Iplayer

Hi

Can you help with this think it's to with file associations .... am downloading wmv files (for portable devices) direct to my memory card from the BBC Iplayer (wmv) they play fine in WMP but when I try to play the same file in Coreplayer it won't play (pink screen with a circular thing in the middle).

Is this something to with the Media Usage rights for the files or a setting I should remember to tweak during the download or in Coreplayer itself?
[General Questions and Answers] FloatingFatMan:
Why not just download the latest version 1.3 from their site? Might perform better...
[8125, K-JAM, P4300, MDA Vario General] devil slime:
hey all these days my wizard would sync perfectly but today it jsut charges and doesn't sync i did a hard reset but still don't work .. i tried in a different computer and it doesn't even identify it

anyone have this problem???
[8125, K-JAM, P4300, MDA Vario General] tears.of.gods:
had the same problem. all days it worked and then suddenly just charging (no sync, no identification). I also did a hard reset but this changed nothing. then I did not use my wizard quite a while (about 3 months)...tried it again and it worked perfectly fine. i have no idea where the problem was...so mate I have no idea how to solve it but you see...there was a happy end ;)
[8125, K-JAM, P4300, MDA Vario General] biofidius:
I just got given a Wizard and it's got this problem too, charging but no sync. Problem with mine looks like a damaged mini USB connector. I can see that the plastic in front of one of the pins on the bottom of the phone is broken.

This thread http://xdaforums.com/showthread.php?t=300240 has some suggestions on where to get replacement connectors.
[8125, K-JAM, P4300, MDA Vario General] kurtslashmx:
how easy is to replace this connector.

i have replaced the screen and got all the way down to the MOBO but i didnt see that mini connector.

edit: i meant i did see the connector but its soldered to the MOBO so i was wondering if this can be replaced.

im having the same problem
[8125, K-JAM, P4300, MDA Vario General] biofidius:
In the forum link I posted above people have said that you can damage your MOBO easily if the PCB gets too hot when soldering.

I have access to a hot air tool used for SMD components, which lets me heat all the pins on the mini USB connector evenly. Using a soldering iron would be more difficult and increase the chances of damaging the MOBO.
[Touch HD Windows Mobile ROM Development] patp:
This thread is for development discussion only. If you are not actively working on the project, please go to the discussion thread where your contribution will be more valuable. By keeping this thread clean, we can hope to get Android working on our devices much quicker.​

Project Status:

We now have a 2.6.27 kernel which is capable of booting Angstrom and Android. Android looks good and is responsive, but most core functions are not there yet. Work is focused on kernel development to provide us with a stable base with working hardware. You can find test files in the second post.

We have a Wiki page where the project gets documented in some detail.

History

The development had a slow start while Orux worked out how to make the mdp talk to mddi to get a working display. We hope that progress will be faster now as there has been considerable work on the Diamond and Raphael hardware, which is quite similar to the Blackstone.

23Feb09

Screen problems fixed at last - many weeks work from Orux got the mdp talking to mddi and give us a working display.

03Mar09

Wow! So much progress in just a week! We now have working SD (some issues with brands of cards - under investigation), allowing booting direct from the SD card; working hardware buttons, and some GSM functionality (the network connects and reports of sending SMS successfully). Credit to Orux, Pichurri, Cybersalsero, Jonlar (and have I missed anyone out - not me, I have been spectating!). Pichurri has posted a full install package on teh wiki, go try it and give feedback in the testing thread.

(to be continued!)

Current tasks

Debugging SD card problems many ppl having

Getting our own version of Android (currently using builds optimised for Raph/Diam

More GSM functions - who will be first to make a call???

What can I do?

You tell us! First thing would be to get yourself set up with a development environment. You need Linux on your PC - either installed as the main OS or if you use Windows, in a virtual machine (eg Virtualbox). Then follow the instructions on the wiki to get the sources and latest diff.
[Touch HD Windows Mobile ROM Development] patp:
Reserved for files

Here you will find the up to date files related to the project.

Pichurri's full 2.6.27 install package is on the wiki here
[Touch HD Windows Mobile ROM Development] brumbrum:
You should correct the posts: 2.6.26 and 2.6.27 is the kernels used. More info: www.kernel.org
[Touch HD Windows Mobile ROM Development] orux:
We are using 2 kernels:

2.6.25 --> htc-msm-2.6.25 branch in git.linuxtogo.org. This is the kernel that we are testing in our machines these days.

2.6.27 --> htc-msm-2.6.27 branch in git.linuxtogo.org. Where we will stay in a few days. Better kernel, more improvements. Here is where people from other projects are working now.
[Touch HD Windows Mobile ROM Development] brumbrum:
Sorry, my mistake. Typed the message above late in the night.

But in the first and second post in this thread it says 2.2.65 and 2.2.67.
[Touch HD Windows Mobile ROM Development] patp:
Thanks, was posted in a rush, just pm me if you see more errors. We use the odd numbered dev kernels, they will always have the most recent stuff.
[Touch HD Windows Mobile ROM Development] orux:
A challenge for someone who likes graphic drivers:

I think linux is using ~10% of epson controller capabilities.

We have a lot of information about this controller, and open source code from epson.

Perhaps someone would like to work with this stuff.
[Touch HD Windows Mobile ROM Development] patp:
Do you mean things like picture-in-picture? Would be good later on in the gui - multiple desktops, that kind of thing. Also I noticed the Epson controller handles TV-out. Do we know if the out-connection exists for this, or have they just not connected it up?

Another thing to consider maybe USB on-the-go - the MSM72xx supports it; if (big if) the usb port has the right connections, it would be possible to mount external storage.

But I think it's more for later on - core functionality would be about making calls, sms, GPRS/3G. Let's see what we get from the latest kernel. Orux have you talked to the RAPH/DIAM guys on irc about merging?
[Touch HD Windows Mobile ROM Development] p3ngwin:
what makes you believe that?

whatever makes you believe it, share it!

if you have anything like docs,etc to share or point to lets have it ! :)
[Touch HD Windows Mobile ROM Development] orux:
Blackstone has got 2 graphic processors:

--->mdp, inside the chip. We have drivers in the kernel (mdp.c, mdp_ppp.c ...) I am not sure what capabilities are being used in current kernel. There are not good docs about mdp processor (I haven't got any useful).

--->epson controller. It can do:

• Picture in Picture, Transparency, Alpha Blending

• Image Rotation (90°, 180°, 270°) and Mirroring

• Scroll Assist

• AME (Auto Movie Enhancement)

• Supports up to three layers

• Image Doubling

• Bi-Cubic Scaling (1/2x ~ 8x)

• Over/Down Sampling Scaling (1/8x ~ 8x)

• Edge Enhancement

We don't have driver support in current kernel, but we have docs and source code from epson (link posted in discussion thread).

Htc Touch Pro has a tvout usb cable adapter, and seems to work in linux! I don't know if this cable works with our device.

USB on-the-go: interesting TODO.

Not yet; perhaps your (or pichurri, ...) task when we have a good .27 diff. I have too much language limitations for an on-line discussion :)
[Touch HD Windows Mobile ROM Development] patp:
OK, OK! These things take time - we all have other jobs I guess. We plan to get any open source docs online in a systematic way, we just need to figure out a reliable way - ie not RS etc. And we have to be careful of proprietry materials - we don't want copyright lawyers after us...

If anyone wants to offer us some rock solid webspace, that would be awesome.
[Touch HD Windows Mobile ROM Development] orux:
TODO: Investigate instability of screen

I think that problems with screen are caused by onscreen keyboard. This keyboard is an excellent hack, but it is not 100% integrated with android.

We need to test a kernel without it.
[Touch HD Windows Mobile ROM Development] xmoo:
Or use the cup cake version with the keyboard in android it self.
[Touch HD Windows Mobile ROM Development] Rewpparo:
Full doc of the epson controler : http://vdc.epson.com/index.php?option=com_docman&task=cat_view&gid=278&Itemid=40

Link is at the bottom of the wiki, add yours :)

I don't think we need to put all the docs at the same place, just add links at the bottom of the wiki, either hosted or link to website.

I can provide hosting if you need, just pm me.
[Touch HD Windows Mobile ROM Development] muld3r_fbi:
repository

what do you guys think about creating some kind of repository(git or svn) to upload and share our blackstone kernel? i think it would make development much easier if you could see changes of other people immediately. we could use github or sourceforge.
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
I also think the On-Screen Keyboard is a problem.

Earlyer today I was goofing around in Android and every time I moved the keyboard, the graphics started acting very weird.(scrolling, not updating etc.)

When I hit F5 on the OSK, it would refresh Android and go back to the home page and the screen would be normal again.

Maybe route the OSK to a pip on the epson?
[Touch HD Windows Mobile ROM Development] Rewpparo:
It's git for kernel dev, anyways svn sucks (inc troll)

If we set up a git, we'll need a guy working as a maintainer and pulling from everyone. This may become usefull when people start working in many different areas of the kernel, but for now diffs are better as they can be easily shared, and there's a howto in the wiki.
[Touch HD Windows Mobile ROM Development] meandu229:
hey i have a servage account that i hardly use which has massive space and bandwidth i could give you a ftp account to and any sql servers you may need. let me know
[Touch HD Windows Mobile ROM Development] patp:
Agreed, the wiki is the best place for this. Would you be happy for me to mention your hosting offer on the front page (which will quite soon need a better structure I'm sure).
[Touch HD Windows Mobile ROM Development] patp:
Now that my friend, is a stunning idea (if it can be done simply). How does it relate to the Android OSK mentioned by xmoo? I guess the linux one is low level whereas the Android one is basically an app in the gui. Advantages to both, but if it works out of the box, the android one would mean we could essentially get rid of the linux one. We have ssh if we want to type in a console (or maybe android terminal app?).
[Touch HD Windows Mobile ROM Development] patp:
I had the same experience - first time hang, second time fine. I don't have the files here, but later I will check if something changes in the filesystem.
[Touch HD Windows Mobile ROM Development] xmoo:
I installed some other apps.

It runned 1 time. And now it just hangs :(
[Touch HD Windows Mobile ROM Development] orux:
It happens to me too.

Perhaps winmo memory usage. Perhaps haret doesn't found enough memory for the kernel; I'm not sure. Linux only try to use first bank of ram memory, this is a limitation.
[Touch HD Windows Mobile ROM Development] schreda:
if its a memory problem.. you could resotre ram with memmaid...

edit: i will try it the next times, when i start android and then we know if its a ram prob or not!

edit2: and if we change the 78mb to 94mb?.. would this make a difference
[Touch HD Windows Mobile ROM Development] pichurri:
5 button patch

I still don't know to who send the diff to upload it to the git repository, so here is the patch for 5 buttons:

http://www.gavero.com/pichurri/blackstone/pichurri_5button_2009-03-11.diff

Apply to an updated git repository, compile and enjoy. :)!
[Touch HD Windows Mobile ROM Development] xaoc747:
Anyone please help to try android on touch hd. I don't understand how it works. Is anyone can upload beta version of tmp and little bit instruction how to use it!?

I try to use one from Pichurri, but no effect...

My devise Touch HD + Transcend 8Gb SDHC...

Android 0,8 and 1,0 working, but just with non-working display:no touch, no call, no anything...

So please help!!!
[Touch HD Windows Mobile ROM Development] dwaradzyn:
You may ask dcordes to push changes to repository. I think you could also ask him to give you direct access to repository. It could be useful to have committed blackstone guy with access to repository. Its all up to you.

BTW thanks devs for your time and congratulations for successes so far.
[Touch HD Windows Mobile ROM Development] Caid444:
Just curious.

Would any of the devs be able to tell me how easy this project would be for a programmer to just pick up and go on. The reason I am asking is because I would like to hold a competition between programmers in the city where I am. I'm a teacher, not a programmer, however, a lot of my students know how to code.

The point I'm trying to make is, if I made all the resources of this project available to a group who's versed in this sort of thing, would they be able to get going easily?

Caid.

edit: by resources I mean sdk, kernal so far, and everything the devs here are using right now.
[Touch HD Windows Mobile ROM Development] brumbrum:
I dont think it would be impossible to get it to work since it is running perfect on simular devices (HTC Dream, aka G1).

The competition could be about getting the project to work perfect, be flashable and fully usable, making the HTC Blackstone a new Android-developer-phone, like Google Dev1 :-).

Since almost all code is GPL or Apache-licenced it is freely availeble for anyone to modify. Just put some dedicated students on the project and let them work 10 hours a day some weeks, and we will have one more fully working android-phone.
[Touch HD Windows Mobile ROM Development] orux:
Finally I was able to get information about smd_rpcrouter and get it working.

Attached a doc with local and remote servers enabled.

As you can see, there is no match between what linux offers, what linux needs and what remote enabled servers offer.

I need to investigate what enabled remote servers are doing.
[Touch HD Windows Mobile ROM Development] patp:
Is this about figuring out which of the remote servers (there are many) corresponds to e.g. the battery, and putting that address in to the #define? If so, is it safe to do by trial and error, or could that damage something?
[Touch HD Windows Mobile ROM Development] orux:
Not enough.

Must match PROGRAM + VERSION.

For example, snd.c looks for this server: 0x30000002:0x94756085 or 0x30000002:0xaa2b1a44 (depends on amss version).

We know that there is a remote snd program enabled: 0x30000002:0, but version is different. Different version implies different interface.

audmgr and adsp programs exist as remote endpoints, but with different version too.

battery does not exist as remote program.

linux kernel knows how it can deal with 6210, 6220 and 6225 amss versions, but I think we have a different amss version.

I´m going to try changing #define versions, but I'm sure it will not work.

more info about msm_rpc: http://wiki.xda-developers.com/index.php?pagename=MSM_RPC
[Touch HD Windows Mobile ROM Development] patp:
Thanks for explaining. From your log, we don't know what version we have right, just that there is a remote server at this address?

What can we know from the "0x94756085" etc? Is it a set of binary flags describing a sound format?
[Touch HD Windows Mobile ROM Development] orux:
We know version :0 (except [RR] o NEW_SERVER id=0:00000001 prog=3000000e:-787701030 )

Version value seems an identifier. It is not used before lookup the server.
[Touch HD Windows Mobile ROM Development] patp:
:0 must mean "not known" or "not yet identified"? They are almost all :0 but the versions referred to in the source code are Dwords. Where are these version codes described (eg for the ones in the source)?
[Touch HD Windows Mobile ROM Development] orux:
You have a good example with two local servers:

htc_battery.c creates server:

#define APP_BATT_PDEV_NAME	"rs30100001:00000000"

#define APP_BATT_PROG	0x30100001

#define APP_BATT_VER	0

but rpc_server_dog_keepalive.c creates server:

#if (CONFIG_MSM_AMSS_VERSION==6210)

#define DOG_KEEPALIVE_VERS 0

#elif (CONFIG_MSM_AMSS_VERSION==6220) || CONFIG_MSM_AMSS_VERSION==6225) || (CONFIG_MSM_AMSS_VERSION==7000) //ORUX

#define DOG_KEEPALIVE_VERS 0x731fa727

#else

#error "Unsupported AMSS version"

#endif

0 seems to be a normal version; but I'm not sure 100%
[Touch HD Windows Mobile ROM Development] TheDunedan:
Kernel sources for blackstone broken

Commit 55740d71abb60f32ef09c13a9756a467584dca6d to the linuxtogo kernel repository breaks compatibility with blackstone for me. A compiled kernel with the default config (which worked before this commit), hangs now on boot with the message:

"pc_clk_enable: enabling a clock that doesn't have an ena bit or ns-only offset: 20"
[Touch HD Windows Mobile ROM Development] dcordes:
let's wait for Joe to have a look.

could you put some referrence on making the debian images in the wiki? can't find simple instructions in the debian wiki. there is http://wiki.debian.org/ArmEabiHowto
[Touch HD Windows Mobile ROM Development] maejrep:
That clock id was not supported prior to the commit, and therefore could not have been broken by the commit. The clock API is not complete, so if you know how to enable clock 20, feel free to make a patch that supports it. If you think it's just an enable-bit, then adding the clock with that bit into the supported clocks table would be enough to return 0 and not an error status.

The only change that would have affected how that clock was handled would have been the change to return non-0, where previously it was returning 0 for every enable, regardless of if it was supported. If that's the case then the existing code was relying on the clock already being enabled (from wince), and returning a fake success result. In my opinion, that's what's really broken, and the fix is not to revert the clock API, but to add real support for that clock. I'll look into how that clock is supported in clkregime.

Edit: I think I was looking at a different ID. Looks like clock id 20 is SDC1_PCLK, which iirc, isn't actually enabled/disabled/set in any way in wince, spl, and looking now in amss. If that's the case, that there is no way to enable/disable that clock, then I think a new property of the table to ignore the clock (and return success status) would be the correct way to resolve it. However, I don't understand how that is causing blackstone to not boot... Raphael boots fine with it, and sdcc still works with no problems. Can you provide more details on what is actually happening with the device? If it's only a guess that it's the clock API causing it to not boot, you have to realize that just because it's the last line being printed during boot, does not mean that it's the reason it isn't booting. That message is printed for several (in fact, most) clocks, and there's a lot of code being executed between each printk, any lines of which could be causing the device to hang -- or even appear to hang.
[Touch HD Windows Mobile ROM Development] orux:
A kernel with last commits works OK in my blackstone.

There is not conflict with those added clocks.
[Touch HD Windows Mobile ROM Development] TheDunedan:
I tried a cross compiled kernel now and it works fine. Seems to be a problem with directly on blackstone built kernels.
[Touch HD Windows Mobile ROM Development] pichurri:
Works OK for me too.

Ps: The zImage of the 2009-03-10 that is up on the wiki, contains the clocks patch, and it works for lots of ppl.

Ps2. My laptop died last friday, I won't be able to apport much for some time...:(...I'll set up an envirnment at work when I have time
[Touch HD Windows Mobile ROM Development] dcordes:
I wonder how much time it would have taken to build all kernels I tried on the kaiser natively :D
[Touch HD Windows Mobile ROM Development] imtiyazee:
hi folks.

long time n no new breaking news...

I hope some one is seriously working on it.:D
[Touch HD Windows Mobile ROM Development] greg_dreyfus:
Same here

With all the current work going on around the new Topaz & Rhodium roms, I hope some have realised that Android is possibly an even better solution.

Consider what it is that everyone likes in these Roms, 95% resides inb the HTC's TouchFlo 3D interface or is skinned to look part of the interface. So I would be confident in saying that the are no actual aspects/features of Windows Mobile that make me personally want to keep it....apart from the vast choice of 3rd party apps out there .... but google have this now too.

More developers should get onboard with Android.....please

Greg